Ycarus has quit [Remote host closed the connection]
vincejv has quit [Remote host closed the connection]
Daanct12 has quit [Quit: WeeChat 4.4.3]
vincejv has joined #openwrt-devel
goliath has joined #openwrt-devel
robimarko has joined #openwrt-devel
awgh_ has joined #openwrt-devel
awgh has quit [Ping timeout: 480 seconds]
n3ph has joined #openwrt-devel
ScrewDriver1337 has quit [Ping timeout: 480 seconds]
<robimarko>
Ok, I might have gone to the bottom of CONFIG_SECCOMP issue
n3ph has quit [Quit: WeeChat 4.4.3]
<robimarko>
As far as I can tell, buildroot is evaluating it as y since the symbol is not visible at all since it depends on certains archs
<robimarko>
So since qoriq and some others do not satisfy that dependency symbol is not set at all in .config
n3ph has joined #openwrt-devel
<robimarko>
And for some reason this makes KConfig(Or whoever) to evaluate undefined symbols as y
<robimarko>
Ahh, its because the default is set to y
<robimarko>
KConfig even documents this
<robimarko>
Or not, that is valid for symbols that are not visible to users
<robimarko>
While CONFIG_SECCOMP is visible but dependencies are not satisfied
<robimarko>
Ugh, even when CONFIG_SECCOMP is visible and set to n our buildsystem still sees it as y somehow
<robimarko>
So, I have a feeling that something is fundamentaly broken
<robimarko>
And that the default-packages.mk is also working by accident
<robimarko>
Since CONFIG_USE_APK will always be evaluated as y as well
<robimarko>
Well, it seems that we have some kind of a symbol conflict
<robimarko>
As renaming CONFIG_SECCOMP to CONFIG_USE_SECCOMP now clearly evaluates to n
<dviola>
I want to apologize for being a bit stubborn on the 4/32 device, I didn't realize how I came across, I'll flash the latest supported version on that device while I look for a new one
Mangix has quit [Read error: Connection reset by peer]
Mangix has joined #openwrt-devel
totkeks has joined #openwrt-devel
efahl is now known as Guest697
efahl has joined #openwrt-devel
Guest697 has quit [Ping timeout: 480 seconds]
skynet2 has joined #openwrt-devel
skynet2_ has joined #openwrt-devel
dviola has quit [Read error: Connection reset by peer]
skynet2 has quit [Ping timeout: 480 seconds]
diego has joined #openwrt-devel
diego has quit []
dviola has joined #openwrt-devel
<dviola>
managed to update to 19.07.10 at least, sysupdate process worked
<dviola>
factory image is 3.8M and sysupgrade 3.6M
<dviola>
s/sysupdate/sysupgrade/
<dviola>
I'm confused how the sysupgrade process worked at all, shouldn't it have been possible given that I only have 4MB of flash?
<dviola>
surprised how smooth that went, my first ever and it just worked
<dviola>
first build*
lucenera has quit [Read error: Connection reset by peer]
lucenera has joined #openwrt-devel
diego has joined #openwrt-devel
diego has left #openwrt-devel [#openwrt-devel]
goliath has quit [Quit: SIGSEGV]
dviola has quit [Ping timeout: 480 seconds]
dviola has joined #openwrt-devel
<dviola>
think I'm going to do another custom build without luci
lucenera has quit [Remote host closed the connection]
lucenera has joined #openwrt-devel
ScrewDriver1337 has joined #openwrt-devel
valku has joined #openwrt-devel
<chris218>
Hi guys, how hard is it to build openwrt for not officially supported hardware/platform? The device has Qualcomm IPQ5018 so it would use ath11k from what i found
<dviola>
chris218: I've been looking to do the same thing as in the last few days, and what I found is that you'll have to create a target for it, i.e. figure out the DTS/DTSI for your router
<dviola>
then check if the router is also able to handle openwrt in terms of flash/RAM capacity
<dviola>
I'm still learning about it so maybe also wait for an answer from a more experienced person
<chris218>
Looks like it just barely has enough in terms of RAM :)
<dviola>
true, most routers seem to be like that
lucenera has quit [Remote host closed the connection]
lucenera has joined #openwrt-devel
<dviola>
that's a lot better than mine, mine has 32M only
<chris218>
Tbh i would just be happy with getting something with ssh, iptables, and something to configure Wi-Fi
n3ph has quit [Ping timeout: 480 seconds]
<dviola>
yeah, I would like to do something similar, I would like to be able to run latest openwrt and do everything from the CLI, as of right now my main problem is the limited capacity and lack of support in ath79
<dviola>
openwrt is working fine on my router but it's running an old version: 19.07.10, not bad for a 2016 router
Yusupoff has joined #openwrt-devel
<Yusupoff>
hi
<dviola>
I'm still shocked how stable openwrt is even on this router with limited resources, the stock firmware was making it crash two times a day, didn't need to reboot even once since I flashed it with openwrt
<dviola>
makes me curious to see what sort of things they put on those images
<robimarko>
chris218: There is no ipq5018 support
<chris218>
:(
<dviola>
robimarko: I've just built an image (ath79-tiny), end result 4.8M (current git)
<dviola>
I see now
<dviola>
no luci
skynet2_ has quit []
n3ph has joined #openwrt-devel
lucenera has quit [Read error: Connection reset by peer]
lucenera has joined #openwrt-devel
<dviola>
my /dev/root is 3.0M and use is 100%
<dviola>
tmpfs says I have 13.3M available, I wonder if that's the reason why I was able to update
n3ph has quit [Ping timeout: 480 seconds]
<totkeks>
i am not sure how it works, but I thought it puts the new image in memory and then boots into that and overwrites the flash. because overwriting the flash while running doesn't work, right?
<dviola>
like I said before, the stability and performance of openwrt is very evident compared to the proprietary firmware, does anyone know what kind of things cause the proprietary firmware to lag behind compared to openwrt? is it outdated drivers and things like that?
<dviola>
just curious, not that I plan to go back
<dviola>
but I mean, the proprietary firmware is also linux right?
<totkeks>
i'd say yes. monetary constraints on initial development and support.
Acinonyx has quit [Quit: Peer reset by connector]
Tapper has quit [Read error: Connection reset by peer]
<mrkiko>
dviola: well, it's a simple yet complicated questions to answer in a precise way.
Tapper has joined #openwrt-devel
<Tapper>
dviola OEM FW is made up of verry old kernel and openwrt code that they rip off and call there own. It's shit and made of bull shit and paper clips!
<Tapper>
dviola Just stick with OpenWrt and any router you can flash it to. I have bin messing around with OpenWrt since I found out that I could flash it to my old WRT54 v2
<Tapper>
I am blind and use a screen reader and some times OEM FW will not even let me read what's on the page with my screen reader. Hence just one more reason for me to stick with OpenWrt
<Tapper>
Some times the proprietary firmware, will run faster speeds on the Wifi but there is no use being fastest kid around the block if you trip and fall over your feet every 10 paces!
<dviola>
s/lag behind compared to openwrt/lag behind openwrt/
<dviola>
mrkiko: I see
<dviola>
Tapper: that's a very impressive use of openwrt, glad it works for you :)
<dviola>
I've heard and known of things like openwrt and dd-wrt for a long time, but was always under the impression that flashing was too complicated and that's why I didn't bother with it anymore, _sigh_
sorinello has quit [Ping timeout: 480 seconds]
<damo22>
i cant seem to unlock the extra bands on my qualcomm 4108 (mdm9607) usb device