Wifi regularly stops working until restart on System76 Oryx Pro Pop OS/Ubuntu
If you open up settings it will say, subtly in the window’s top bar:
Wi-Fi
Unavailable
With recent regressions in the icons in the main top bar, no longer accurately showing the status of wifi, i don’t know if there’d be a clearer indication up there that something is broken.
There’s suggestive errors in /var/log/syslog though, like:
iwlwifi 0000:03:00.0: Error, can not clear persistence bit
In the long sequence reproduced below i noted the Bluetooth-related errors, which was of concern because i am forcing Bluetooth to stay disabled, because all it does is cause trouble. So i tried turning it on to see if that would fix the wifi in some bizarro way, and it didn’t, of course, but all that’s shown in the logs.
Oct 21 23:04:09 oryx /usr/lib/gdm3/gdm-x-session[2481]: (II) modeset(0): Modeline "3840x2160"x0.0 526.91 3840 3888 3920 3956 2160 2162 2167 2220 -hsync -vsync (133.2 kHz eP)
Oct 21 23:04:28 oryx bluetoothd[1602]: Failed to set mode: Blocked through rfkill (0x12)
Oct 21 23:04:28 oryx gnome-control-c[30025]: Error setting property 'Powered' on interface org.bluez.Adapter1: GDBus.Error:org.bluez.Error.Blocked: Blocked through rfkill (g-io-error-quark, 36)
Oct 21 23:04:28 oryx dbus-daemon[2491]: [session uid=1000 pid=2491] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.7537' (uid=1000 pid=30025 comm="gnome-control-center " label="unconfined")
Oct 21 23:04:28 oryx systemd[2452]: Starting Bluetooth OBEX service...
Oct 21 23:04:28 oryx obexd[30050]: OBEX daemon 5.50
Oct 21 23:04:28 oryx dbus-daemon[2491]: [session uid=1000 pid=2491] Successfully activated service 'org.bluez.obex'
Oct 21 23:04:28 oryx systemd[2452]: Started Bluetooth OBEX service.
Oct 21 23:04:29 oryx Tor[1431]: Failed to find node for hop #1 of our path. Discarding this circuit.
Oct 21 23:04:31 oryx gnome-control-c[30025]: gtk_main_quit: assertion 'main_loops != NULL' failed
Oct 21 23:05:11 oryx NetworkManager[353]: <info> [1571713511.5274] manager: rfkill: Wi-Fi hardware radio set disabled
Oct 21 23:05:11 oryx NetworkManager[353]: <info> [1571713511.5276] audit: op="radio-control" arg="wireless-enabled" pid=2759 uid=1000 result="success"
Oct 21 23:05:11 oryx NetworkManager[353]: <info> [1571713511.5291] manager: rfkill: Wi-Fi now disabled by radio killswitch
Oct 21 23:05:33 oryx NetworkManager[353]: <info> [1571713533.7045] manager: rfkill: Wi-Fi hardware radio set enabled
Oct 21 23:05:33 oryx NetworkManager[353]: <warn> [1571713533.7049] platform-linux: do-change-link[3]: failure changing link: failure 1 (Operation not permitted)
Oct 21 23:05:33 oryx NetworkManager[353]: <info> [1571713533.7053] audit: op="radio-control" arg="wireless-enabled" pid=2759 uid=1000 result="success"
Oct 21 23:05:33 oryx kernel: [84964.464527] iwlwifi 0000:03:00.0: Error, can not clear persistence bit
Oct 21 23:05:33 oryx NetworkManager[353]: <info> [1571713533.7098] manager: rfkill: Wi-Fi now enabled by radio killswitch
Oct 21 23:05:33 oryx NetworkManager[353]: <warn> [1571713533.7105] platform-linux: do-change-link[3]: failure changing link: failure 1 (Operation not permitted)
Oct 21 23:05:33 oryx kernel: [84964.470087] iwlwifi 0000:03:00.0: Error, can not clear persistence bit
But anyway anything Bluetooth is probably a red herring.
The key errors appear to be:
NetworkManager[353]: <info> [1571713533.7045] manager: rfkill: Wi-Fi hardware radio set enabled
NetworkManager[353]: <warn> [1571713533.7049] platform-linux: do-change-link[3]: failure changing link: failure 1 (Operation not permitted)
NetworkManager[353]: <info> [1571713533.7053] audit: op="radio-control" arg="wireless-enabled" pid=2759 uid=1000 result="success"
kernel: [84964.464527] iwlwifi 0000:03:00.0: Error, can not clear persistence bit