Didn’t produce any output at all.
I see some “failed” and “disconnected” entries.
Same.
WiFI enabled by radio killswitch. WWAN enabled by radio killswitch. Networking enabled.
The indicator in the notifications tray shows disconnected. WiFI settings panel is still missing from general settings.
I had not left it off for so long before, but I did try a couple of restarts with the switch off. This time, waiting 1+ minute still did not solve it.
Purism could beta test updates with a group of users who are game to go along. Specify the functions to run, and let those who want run a few pet functions of their own. Even a one-day test could save a lot of people a lot of time. (Maybe they do already.)
Most wouldn’t volunteer but surely some diehards would.
— Privacy, yay.
At least I have the ethernet adapter on the way. 
I’m surprised the restore didn’t help me, though. Isn’t that what backups are for? Lol!
You can implement that yourself by not installing updates on the first day they appear 
I actually do this, not purely with that intention, but sometimes also due to laziness 
I’d suggest looking at the logs around the area of the “failed” and “disconnected” entries to see if they relate to the card and hopefully they’ll give some more detail as why it’s failed and been disconnected.
You can dump the whole lot to a text file then use a text editor to search through it. That is probably the easiest way as unfortunately the pager/more on the phone is either a little broken or not yet fully implemented as it only goes forward and search doesn’t work.
To dump the whole lot to a file…
sudo journalctl -xb > nowifi.log
That will produce a nowifi.log file in the current directory (the ‘x’ option just adds a little more detail to each entry where available), you can then open that in a text editor and search for terms like “redpine”, “failed”, “disconnected” etc…
You can do the same with dmesg but but you’re more likely to get more detail out of journalctl. To dump dmesg to a file…
sudo dmesg > dmesg.nowifi.log
All updates go through an incubation period in amber-phone-staging repository, which usually is 7 days long. Rest assured that this has been tested by several people on multiple devices (and I’m using 5.11 kernels myself since December).
It doesn’t look related to the update then. Have you tried turning the phone off to cool down? Some users reported that WiFi doesn’t always show up for them after toggling a killswitch or rebooting when the phone is warm.
I must tell that I usually have my phone off (to save battery time) so it is pretty cool. Usually I have WiFi up and connected within 30 seconds after switching the phone on. That is fairly stable now. The C7 router is about three meters away behind a wooden wall and the signal strength is Good (all this with 5.11). I have very few apps installed.
Even after sitting overnight with power off, the WiFi hasn’t come back. I’ll see what happens with the ethernet adapter that is arriving today. Maybe there are some updates waiting that will affect WiFi.
P.S. The saved backup I restored to was from a week ago, before the WiFi issue started, just for info.
You don’t need to have a dedicated USB ethernet adapter. Ethernet over USB works pretty well.
It looks like I’m not getting a network connection when I plug the phone into my laptop.
Is an ethernet setting supposed to appear on the L5?
There seems to be some regression in 5.11 at least, I just experienced something similar. (Wifi not being available on boot that is, not performance degradation - though I haven’t tested wifi performance yet.)
Happened after upgrading the kernel package from 5.9 to 5.11; that was the only package with upgrades available when I checked this morning. Rebooted several times, and each time I had to flip the hardware kill switch off and on before the wifi card would become available. Switched back to the 5.9 kernel and rebooted, wifi came up immediately on boot.
(I have an Evergreen.)
No, it connects via DHCP to whatever network it finds.
Do you have a 5GHz Wifi or “just” 2.4GHz?
In the last couple days I haven’t been able to get Wifi to turn on at all. 5.9 vs 5.11 doesn’t seem to matter. Rebooting and toggling the switch doesn’t matter. The UI acts like the wifi switch is off reguardless of where it is, although looking at the logs seems to indicate that it’s seeing the wifi hardware.
Same here. No WiFI, no bluetooth. No matter 5.9 or 5.11. Killswitch has no discernible effect.
I connected with a USB-C-to-ethernet adapter just now and was able to download waiting updates, but still no WiFI.
I have both, on two different SSIDs. Been connecting to the 2.4 GHz network since I’ve heard it drains less power on the L5.
I would think that if the logs detail the presence of the WiFi card, then the logs probably also have some details and results of the system attempting to bring the card up, loading firmware, initialiing etc,?
Pretty funny … today my WiFi was operational after booting, without toggling the killswitch. Perhaps the kernel needs to adapt to the hardware
Is there a list of fixes somewhere on the web? Honestly I didn’t notice a big improvement.
Where is this update? Only on command line? Because I just checked the PureOs store app and shown my L5 updated, although uname -r shows 5.9.0.