<olmari>
What would be the latest openwrt that I can use with WDR4900 and expect it to work? And if there are some bootloader replacements, I am willing to test / do, I need TTL-serial anyway
<olmari>
to recover from current mishap :D
rua has quit [Remote host closed the connection]
rua has joined #openwrt-devel
<olmari>
hmm.. id DOES seem master from yesterday DID wen into the device just fine, despite me not reaching it remotely... TTL console shows openwrt running just fine
xes has quit [Read error: No route to host]
xes has joined #openwrt-devel
valku has joined #openwrt-devel
<olmari>
So it must be either some very old network config copied that doesn't work, or something else, still debugging, but this looks more promising that I initially thought :)
<PaulFertser>
olmari: with bad bootloader serial adapter won't help.
<olmari>
PaulFertser: I can understand that too, but apparently s**t on better condition and more of other infra error than WDR4900 itself
<olmari>
I was expecting device to be either totally bricked or bootloader yelling "help" or whatever, but it indeed seems to be very alive and well
minimal has joined #openwrt-devel
<PaulFertser>
olmari: I mean if bootloader replacement goes bad serial won't be the way to recover
<olmari>
PaulFertser: then it would be JTAG thing, or finally throw the thing over the shoulder
<olmari>
Sad thing is that otherwise device still performs so effing awesome in the context, things done by openwrt devs to make it still bootable with whatever the bootloader deficiency is, is so lovely
<olmari>
PaulFertser: Let's start from beginning, it seems to boot very fine right into openwrt
<olmari>
"just" not reachable over network, which can be any number of PEBKAC too
Borromini has quit [Ping timeout: 480 seconds]
<olmari>
I thought I bricked it because of upgrade from remote, but apparently it is not as bricked at all
<PaulFertser>
olmari: are you able to initiate "generic failsafe"?
<olmari>
Probably? I mean it boots all the way into openwrt, so in that sense nothing is wrong
<olmari>
(hooked in TTL)
<olmari>
it might not help that I baked in network config for the device in buildroot :P
<olmari>
At the moment IDK what is exactly wrong, network config in general seems to be okay, ifconfig shows interfaces, but no traffic flows
rua has quit [Remote host closed the connection]
rua has joined #openwrt-devel
<olmari>
a-ha, deleting nework config and letting owrt generate new one from scratch I see there is not some additional configs... now data flows.. this is easily salvageable now! :)
<olmari>
..I do wonder why luci always complains not compatible to upgrade, but that is also "whatever" as long as shit keeps working :P
<olmari>
I mean I could understand it between major things changed, like ar71xx and ath79 (or so), but IDK what is this one about, especially between master from yesterday and today =)
<olmari>
..maybe it is/was the network config things..
schwicht has joined #openwrt-devel
<olmari>
umm.. under this new DSA thing (I think), how do I define VLANs?
<olmari>
LUCI doesn't have switch config anymore, and /e/c/network nor the LUCI interface thing is not immediately clear :)
<olmari>
oh... immediately after asking, I did found "add device configuration" -page :D
schwicht has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<olmari>
Yeah, This is coming along just fine now, thank you :P
schwicht has joined #openwrt-devel
rua has quit [Quit: Leaving.]
schwicht has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
schwicht has joined #openwrt-devel
rua has joined #openwrt-devel
schwicht has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<hurricos>
stintel: Perhaps you could look at an ath79 device port for me? :^)
<hurricos>
I've been digging for a reviewer for a few weeks now, and I really want to make the 23.xx fork
<robimarko>
I agree, this is one of those where somebody bothered to really fix the issue
<robimarko>
I think that ath79 tiny sysupgrade issues are well known, probably not enough space
<shibboleth>
did not, you mean? also, this is not an issue of not enough "free" space on rootfs_data /dev/mtdblock5 884.0K 80.0K 804.0K 9% /overlay
<f00b4r0>
shibboleth: a few items in that proposal strike me as impractical or downright wrong. Moving to 64K for all for instance would make the device useless. Remember that each change in jffs2 happens in EB increments.
<f00b4r0>
shibboleth: if it's not a freespace issue, it's a blocksize mismatch. The build recipe must be fixed.
<f00b4r0>
that's item 2. in the email you linked :)
hgl_ has quit [Ping timeout: 480 seconds]
<shibboleth>
sure, but is it as easy as adjusting the makefile used to build for testing?
schwicht has joined #openwrt-devel
<f00b4r0>
for testing it's as easy as that yes. For committing you'll have to document the change as it may cause breakage for existing config (assuming they aren't already hosed anyway)
<shibboleth>
so adjust blocksize 4k->64k in makefile, build test image, apply this patch going forward until someone fixes it globally?
<f00b4r0>
the other way around would be preferred if possible
<f00b4r0>
make 4K consistent where applicable, only using 64K when 4K isn't supported.
<shibboleth>
ok, and would it be possible to add device exceptions based on user feedback? re the mailinglist and this device, if a user reports a device to be affected, add exception to master/stable?
schwicht has quit []
<f00b4r0>
i'm not sure what you mean by "exceptions"?
<shibboleth>
64k/4k
<shibboleth>
per-device exceptions for the buildroot
<shibboleth>
in menuconfig, for example
<f00b4r0>
well as I said (and as is mentioned in the email that you linked), it's a matter of whether or not a device supports 4K EB. If they do, they should use that (speaking in a "tiny" context of course), if they don't they should use 64K. There isn't really a need for exceptions of any kind, it's down to hardware support.
schwicht has joined #openwrt-devel
<shibboleth>
exactly, but the -tiny default is 4k
<shibboleth>
and add exceptions to that based per-device based on feedback
<f00b4r0>
sounds sensible
robimarko_ has joined #openwrt-devel
robimarko has quit [Read error: Connection reset by peer]
robimarko_ has quit [Quit: Leaving]
bluew_ has joined #openwrt-devel
bluew has quit [Read error: Connection reset by peer]
shibboleth has quit [Quit: shibboleth]
schwicht has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
djfe_ has joined #openwrt-devel
djfe has quit [Ping timeout: 480 seconds]
<olmari>
To all who has seen the trouble to keep the WDR4900 usable with openwrt, big thank you all :)
djfe_ has quit [Read error: Connection reset by peer]
<hurricos>
olmari: The saga isn't quite over, but it's not far from
<olmari>
hurricos: Well, it was "supposed" to be over many versions ago, so I am jsut happy it _still_ is working and my issue was mere PEBKAC :D
<hurricos>
well. OK. WDR4900v1 will be fine w/ okli. I'm suffering over other mpc85xx boards. The bootloaders on the target suck
<olmari>
When it's over, then it's over, I'm still so grateful it still works :)
<hurricos>
I guess I should be thankful for that :(
<hurricos>
the most recent fix for ap3825i broke SMP and is driving the CPU at 1GHz instead of 800MHz, which worries me for stability
<Znevna>
djfe: did you test that resize script by any chance? on our ax53u
cbeznea has quit [Quit: Leaving.]
Borromin1 has quit [Quit: Lost terminal]
gch9812136 has joined #openwrt-devel
swegener has quit [Quit: leaving]
swegener has joined #openwrt-devel
gch981213 has quit [Ping timeout: 480 seconds]
gch9812136 is now known as gch981213
hgl has joined #openwrt-devel
<philipp64>
how do you change the name of a downloaded PKG_SOURCE locally? the tarball for beanstalkd is just called v$(PKG_VERSION).tar.gz which is broken...
<philipp64>
should I clone was zoneinfo does?
hgl has quit [Ping timeout: 480 seconds]
xutaxkamay has quit [Ping timeout: 480 seconds]
<nick[m]12>
Can I somehow checkout linux-wireles-next for the mac80211 in openwrt? Probably, I have to run through the backport package creation, but is this easily doable with some script?
<olmari>
Just setup monthly donation to openwrt :) While I don't care to get any bragging rights, I feel this needs to be said so that others who also uses this awesone thing
<olmari>
TBH equally not between opnsense and openwrt, for very different usecases and reasons, both equally important to me <3
hgl has joined #openwrt-devel
<olmari>
... minus "not" xD
zer0def has quit [Ping timeout: 480 seconds]
schwicht has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]