[OpenWrt-Devel] [PATCH] ath79: switch to kernel 5.4
bjorn at mork.no
Fri Apr 3 05:21:57 EDT 2020
David Bauer <mail at david-bauer.net> writes:
> As the reported major bugs are ironed out, switch to the new kernel to
> begin testing with a broader audience.
Hmm... I wonder if you might want to hold back on that for a while.
I have no useful info yet since I don't have console access on this
device, but I just lost network access to a UniFi AP AC PRO after trying
out current master (fcd14017007d).
I'll see what I can get out of it, but I don't promise anything if I
can't figure out a way to get network access. The AP is located
semi-outdoors so I don't really want to open it and break the seal..
The AP ran a similar arbitrary master checkout from January before
upgrading (b070101c506c), having a v4.19.93 kernel. I upgraded using
'sysupgrade -v ...' in a shell, keeping existing configs, as I usually
do unless told not to ;-)
The part of the upgrade which is visible via ssh looked fine:
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
OpenWrt SNAPSHOT, r11998-b070101c506c
root at unifiac2:~# sysupgrade -v http://owrt.mork.no/lede/r12793-fcd14017007d/targets/ath79/generic/openwrt-snapshot-ath79-generic-ubnt_unifiac-pro-squashfs-sysupgrade.bin
Connecting to 192.168.99.1:80
Writing to '/tmp/sysupgrade.img'
/tmp/sysupgrade.img 100% |*******************************| 5056k 0:00:00 ETA
Download completed (5178139 bytes)
Saving config files...
Commencing upgrade. Closing all shell sessions.
Connection to unifiac2 closed by remote host.
Connection to unifiac2 closed.
There isn't anything out of the ordinary in my configs AFAIK. The "main"
ethernet port is connected to an unmanaged media converter, using 3
tagged VLANs for AP management and two wlan bridges. The second ethernet
port is not connected. I've tried accessing 192.168.1.1 untagged, in
case the network config somehow reverted to default, but there wasn't
anything responding to arps there either.
Do you have any suggestions as to what could have gone wrong? It would
help to know if I should have expected some changes to the network
config - I can work with that. Also useful to know if there is a flash
related issue or some crash to be expected.
And no need to worry about me - I'm writing this FYI in case you want to
delay broadening the 5.4 testing.
only. I am pretty sure I can revive the AP by temporarily reverting to
vendor firmware using bootloader tftp. And then reinstall a known
working OpenWrt image. But this will obviously prevent any further
debugging, so I'll hold on for a while before doing that.
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
More information about the openwrt-devel