[RESOLVED] WiFi disconnects, FW13 AMD, Fedora-KDE

Matthew_Shook · January 7, 2024, 1:18am

SOLVED TLDR: There was (for me) a kernel regression in 6.5 and above that caused intermittent wifi disconnects. It seems related to power settings but I was not able to resolve it by changing the power/performance settings. The 6.1 OEM kernel reccommended by FrameWork is what you need to stick with. After installing Ubuntu 22.04 I had to navigate through the grub menu to choose the 6.2 kernel to boot up with working wifi, and then use the guide’s instructions to download the OEM kernel.

For about 2 weeks I’ve had problems with intermittent WiFi disconnects on my FW13 running Fedora 39-KDE Spin. Typically, after using the laptop for 10-30 minutes, the wifi will disconnect then reconnect every few minutes. Eventually it disconnects and can no longer detect any nearby routers. Rebooting restores normal behavior.

I used Btrfs Assistant to restore a snapshot from 2 weeks ago and used GRUB to choose a 6.6.6 kernel to get my wifi working again. Later I did updates, and tried the 6.6.9 kernel which brought back the regression. I restored back, am using 6.6.7 (the 6.6.6 option disappeared). Things are currently back to normal. (More info on my system are at the end)

What now?
Do I periodically run the system update, cross my fingers that the regression’s fixed, and restore a snapshot if not? Do I report this to KDE and/or Fedora?

More info: I tried the officially supported KDE-Gnome live USB and the wifi worked fine. Interestingly I tried a Manjaro-KDE USB and it did have the wifi problem. I was curious and installed Manjaro on a microSD, updated it (including 6.6.8), and there were no wifi drops.

BUT the wifi on Manjaro was stable but slow. On Fedora my speedtest.net download is 1200Mbps but with Manjaro it was only 300Mbps. Maybe the fact Manjaro was running from a microSD was the reason. I’m not an expert on the various wifi protocols and Ghz but I’d be interested in an opinion on this. My router/modem is an Xfinity 6E model. I’m in an apartment complex with 10 networks visible.

My inxi -Fz is atttached below.
There are some screenshots (in reverse order) that show the final error when no networks are detected, then the recurrent “Authorization supplicant timed out.”
![Screenshot_20240105_110339-2|471x500]

(upload://9AmQP3fY0L4NLBtRivJ1R5A3nvK.png)

y inxi -Fz

SoldierSvejk · January 7, 2024, 2:03am

The fact that it initially works and then degrades suggests to me that the network manager is attempting to use an unsupported power saving option. Did you change any power management options in KDE? It is possible to set WiFi power saving features in the settings interface. I generally avoid playing with sleep, hibernate or any fancy power saving options on linux as the support is hit and miss.

Looks similar - ubuntu - Wireless interface Authorization supplicant failed kubuntu 20.04 - Unix & Linux Stack Exchange

Matthew_Shook · January 7, 2024, 6:22am

Thanks for the link. It sounds quite possible. I don’t think I had adjusted any of the settings. I clicked to reset the defaults in KDE System Settings’ Energy Saving tab. It looked like everything was already on the defaults.

It doesn’t appear the file
/etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
exists on my system. Do you think it would make sense to create one?

SoldierSvejk · January 7, 2024, 7:08am

Sure, you can see here, it should have some effect with Fedora (and the missing configuration file is normal too): Tip: Lower WiFi latency by disabling WiFi power management - Fedora Discussion

However, you can also see the options in KDE here (I think this is a GUI to the same conf…):

Matthew_Shook · January 7, 2024, 6:59pm

My system definitely did not like sticking that default-wifi-powersave-on.conf file in there. I restarted NetworkManager and my wifi device disappeared from my system. The KDE Connections settings only showed the lo device. I deleted the file and had to reboot for things to go back to normal.

I’ve read so much on this that I can’t remember where I saw it, but I think that config file might only be for Intel devices.

I did change settings on the Energy Savings tabs. For both AC power and battery I enabled the power management profiles and set them both to “Performance.” So far, so good. Thanks for sending me on the right direction, I hope.

It will be annoying if this doesn’t get fixed though. The wifi worked fine last month, and I imagine the Performance setting will decrease my battery life.

EDIT: Choosing the Performance setting on AC power and battery seems to have fixed the wifi issues. I would mark this solved, but I can’t figure out how.

Matthew_Shook · January 11, 2024, 4:13am

I wanted to update this after living with it for a few days. With the Performance setting, the wifi drops are far less frequent but still about once a day the wifi device disappears from the Connections settings and I have to reboot. This happens in KDE and Gnome.

Often if the system is awoken from sleep it takes over 30 seconds for the wifi to be “reactivated.” But it usually then works fine. Before the wifi connection would come back instantly after sleep.

It doesn’t seem to be connected to heavy CPU load or downloading. It happens on AC and battery as well.

It does seem to be connected to the power profile and turning on from a sleep state.

I just thought of something as I type. This may have started after I moved the USB-C/Charging port from the right to the left side. I’ll try switching that.`

Loell_Framework · January 11, 2024, 11:05am

Does network manager say anything?

journalctl -u NetworkManager -b 0

Matthew_Shook · January 14, 2024, 5:05pm

I’ve continued to have to have a failure to connect to wifi about half of the times I awake the laptop from sleep. In these cases I have to reboot. But I’ve not had a disconnect in the middle of using it for about a week. But it happened this morning.
Here’s the “journalctl -u NetworkManager -b 0” log, starting with when I wake it up and ending when I lost wifi 6 minutes later.

Am I reading it right, that it tries to authenticate and then fails and times out?
( This is the first time I’ve posted a lengthy log here. Please let me know if there’s a preferred way to post this)

Jan 14 08:37:27 mattsfw NetworkManager[431515]: <info>  [1705250247.8118] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jan 14 08:37:27 mattsfw NetworkManager[431515]: <info>  [1705250247.8121] device (wlp1s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 14 08:37:27 mattsfw NetworkManager[431515]: <info>  [1705250247.8430] device (wlp1s0): set-hw-addr: set MAC address to C2:33:FE:75:2E:7A (scanning)
Jan 14 08:37:27 mattsfw NetworkManager[431515]: <info>  [1705250247.8950] device (p2p-dev-wlp1s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 14 08:37:27 mattsfw NetworkManager[431515]: <info>  [1705250247.8954] manager: NetworkManager state is now DISCONNECTED
Jan 14 08:37:27 mattsfw NetworkManager[431515]: <info>  [1705250247.8955] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 14 08:37:27 mattsfw NetworkManager[431515]: <info>  [1705250247.8955] device (wlp1s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 14 08:37:27 mattsfw NetworkManager[431515]: <info>  [1705250247.9293] device (wlp1s0): set-hw-addr: reset MAC address to 14:AC:60:46:7F:FB (unmanage)
Jan 14 08:37:27 mattsfw NetworkManager[431515]: <info>  [1705250247.9859] device (p2p-dev-wlp1s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 14 08:37:27 mattsfw NetworkManager[431515]: <info>  [1705250247.9861] manager: NetworkManager state is now ASLEEP
Jan 14 08:37:31 mattsfw NetworkManager[431515]: <info>  [1705250251.0200] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jan 14 08:37:31 mattsfw NetworkManager[431515]: <info>  [1705250251.0202] device (wlp1s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 14 08:37:31 mattsfw NetworkManager[431515]: <info>  [1705250251.0777] device (p2p-dev-wlp1s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 14 08:37:31 mattsfw NetworkManager[431515]: <info>  [1705250251.0780] manager: NetworkManager state is now DISCONNECTED
Jan 14 08:37:31 mattsfw NetworkManager[431515]: <info>  [1705250251.0970] device (wlp1s0): supplicant interface state: internal-starting -> disconnected
Jan 14 08:37:31 mattsfw NetworkManager[431515]: <info>  [1705250251.0971] device (p2p-dev-wlp1s0): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Jan 14 08:37:31 mattsfw NetworkManager[431515]: <info>  [1705250251.0974] Wi-Fi P2P device controlled by interface wlp1s0 created
Jan 14 08:37:31 mattsfw NetworkManager[431515]: <info>  [1705250251.0975] manager: (p2p-dev-wlp1s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/7)
Jan 14 08:37:31 mattsfw NetworkManager[431515]: <info>  [1705250251.0977] device (p2p-dev-wlp1s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 14 08:37:31 mattsfw NetworkManager[431515]: <info>  [1705250251.0978] device (wlp1s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Jan 14 08:37:31 mattsfw NetworkManager[431515]: <info>  [1705250251.0982] device (p2p-dev-wlp1s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Jan 14 08:37:36 mattsfw NetworkManager[431515]: <info>  [1705250256.4880] policy: auto-activating connection 'xfmaps' (6b9918d4-2e7e-40eb-b8ac-58ab27d01465)
Jan 14 08:37:36 mattsfw NetworkManager[431515]: <info>  [1705250256.4885] device (wlp1s0): Activation: starting connection 'xfmaps' (6b9918d4-2e7e-40eb-b8ac-58ab27d01465)
Jan 14 08:37:36 mattsfw NetworkManager[431515]: <info>  [1705250256.4885] device (wlp1s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 14 08:37:36 mattsfw NetworkManager[431515]: <info>  [1705250256.4886] manager: NetworkManager state is now CONNECTING
Jan 14 08:37:36 mattsfw NetworkManager[431515]: <info>  [1705250256.4888] device (wlp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 14 08:37:36 mattsfw NetworkManager[431515]: <info>  [1705250256.4891] device (wlp1s0): Activation: (wifi) access point 'xfmaps' has security, but secrets are required.
Jan 14 08:37:36 mattsfw NetworkManager[431515]: <info>  [1705250256.4892] device (wlp1s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jan 14 08:37:36 mattsfw NetworkManager[431515]: <info>  [1705250256.5054] device (wlp1s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 14 08:37:36 mattsfw NetworkManager[431515]: <info>  [1705250256.5057] device (wlp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 14 08:37:36 mattsfw NetworkManager[431515]: <info>  [1705250256.5061] device (wlp1s0): Activation: (wifi) connection 'xfmaps' has security, and secrets exist.  No new secrets needed.
Jan 14 08:37:36 mattsfw NetworkManager[431515]: <info>  [1705250256.5063] Config: added 'ssid' value 'xfmaps'
Jan 14 08:37:36 mattsfw NetworkManager[431515]: <info>  [1705250256.5063] Config: added 'scan_ssid' value '1'
Jan 14 08:37:36 mattsfw NetworkManager[431515]: <info>  [1705250256.5063] Config: added 'bgscan' value 'simple:30:-65:300'
Jan 14 08:37:36 mattsfw NetworkManager[431515]: <info>  [1705250256.5063] Config: added 'key_mgmt' value 'SAE FT-SAE'
Jan 14 08:37:36 mattsfw NetworkManager[431515]: <info>  [1705250256.5063] Config: added 'auth_alg' value 'OPEN'
Jan 14 08:37:36 mattsfw NetworkManager[431515]: <info>  [1705250256.5064] Config: added 'psk' value '<hidden>'
Jan 14 08:37:36 mattsfw NetworkManager[431515]: <info>  [1705250256.5064] Config: added 'ieee80211w' value '2'
Jan 14 08:37:36 mattsfw NetworkManager[431515]: <info>  [1705250256.5487] device (wlp1s0): supplicant interface state: disconnected -> authenticating
Jan 14 08:37:36 mattsfw NetworkManager[431515]: <info>  [1705250256.5488] device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> authenticating
Jan 14 08:37:41 mattsfw NetworkManager[431515]: <info>  [1705250261.5905] device (wlp1s0): supplicant interface state: authenticating -> disconnected
Jan 14 08:37:41 mattsfw NetworkManager[431515]: <info>  [1705250261.5906] device (p2p-dev-wlp1s0): supplicant management interface state: authenticating -> disconnected
Jan 14 08:37:41 mattsfw NetworkManager[431515]: <info>  [1705250261.7024] device (wlp1s0): supplicant interface state: disconnected -> scanning
Jan 14 08:37:41 mattsfw NetworkManager[431515]: <info>  [1705250261.7024] device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> scanning
Jan 14 08:37:42 mattsfw NetworkManager[431515]: <info>  [1705250262.1490] device (wlp1s0): supplicant interface state: scanning -> authenticating
Jan 14 08:37:42 mattsfw NetworkManager[431515]: <info>  [1705250262.1491] device (p2p-dev-wlp1s0): supplicant management interface state: scanning -> authenticating
Jan 14 08:37:42 mattsfw NetworkManager[431515]: <info>  [1705250262.1817] device (wlp1s0): supplicant interface state: authenticating -> associating
Jan 14 08:37:42 mattsfw NetworkManager[431515]: <info>  [1705250262.1817] device (p2p-dev-wlp1s0): supplicant management interface state: authenticating -> associating
Jan 14 08:37:42 mattsfw NetworkManager[431515]: <info>  [1705250262.2410] device (wlp1s0): supplicant interface state: associating -> 4way_handshake
Jan 14 08:37:42 mattsfw NetworkManager[431515]: <info>  [1705250262.2410] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> 4way_handshake
Jan 14 08:37:42 mattsfw NetworkManager[431515]: <info>  [1705250262.3333] device (wlp1s0): supplicant interface state: 4way_handshake -> completed
Jan 14 08:37:42 mattsfw NetworkManager[431515]: <info>  [1705250262.3333] device (wlp1s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "xfmaps"
Jan 14 08:37:42 mattsfw NetworkManager[431515]: <info>  [1705250262.3334] device (p2p-dev-wlp1s0): supplicant management interface state: 4way_handshake -> completed
Jan 14 08:37:42 mattsfw NetworkManager[431515]: <info>  [1705250262.3457] device (wlp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 14 08:37:42 mattsfw NetworkManager[431515]: <info>  [1705250262.3463] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Jan 14 08:37:42 mattsfw NetworkManager[431515]: <info>  [1705250262.3736] dhcp4 (wlp1s0): state changed new lease, address=10.0.0.192
Jan 14 08:37:42 mattsfw NetworkManager[431515]: <info>  [1705250262.3742] policy: set 'xfmaps' (wlp1s0) as default for IPv4 routing and DNS
Jan 14 08:37:42 mattsfw NetworkManager[431515]: <info>  [1705250262.3918] device (wlp1s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 14 08:37:42 mattsfw NetworkManager[431515]: <info>  [1705250262.4183] device (wlp1s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 14 08:37:42 mattsfw NetworkManager[431515]: <info>  [1705250262.4184] device (wlp1s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 14 08:37:42 mattsfw NetworkManager[431515]: <info>  [1705250262.4186] manager: NetworkManager state is now CONNECTED_SITE
Jan 14 08:37:42 mattsfw NetworkManager[431515]: <info>  [1705250262.4190] device (wlp1s0): Activation: successful, device activated.
Jan 14 08:37:42 mattsfw NetworkManager[431515]: <info>  [1705250262.5536] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 14 08:37:43 mattsfw NetworkManager[431515]: <info>  [1705250263.5596] dhcp6 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Jan 14 08:37:43 mattsfw NetworkManager[431515]: <info>  [1705250263.5600] policy: set 'xfmaps' (wlp1s0) as default for IPv6 routing and DNS
Jan 14 08:37:43 mattsfw NetworkManager[431515]: <info>  [1705250263.5665] dhcp6 (wlp1s0): state changed new lease, address=2601:1c0:4c02:2940::cda5
Jan 14 08:43:01 mattsfw NetworkManager[431515]: <info>  [1705250581.0948] device (wlp1s0): supplicant interface state: completed -> authenticating
Jan 14 08:43:01 mattsfw NetworkManager[431515]: <info>  [1705250581.0951] device (p2p-dev-wlp1s0): supplicant management interface state: completed -> authenticating
Jan 14 08:43:06 mattsfw NetworkManager[431515]: <info>  [1705250586.1383] device (wlp1s0): supplicant interface state: authenticating -> disconnected
Jan 14 08:43:06 mattsfw NetworkManager[431515]: <info>  [1705250586.1384] device (p2p-dev-wlp1s0): supplicant management interface state: authenticating -> disconnected
Jan 14 08:43:06 mattsfw NetworkManager[431515]: <info>  [1705250586.2473] device (wlp1s0): supplicant interface state: disconnected -> scanning
Jan 14 08:43:06 mattsfw NetworkManager[431515]: <info>  [1705250586.2474] device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> scanning
Jan 14 08:43:14 mattsfw NetworkManager[431515]: <info>  [1705250594.4466] device (wlp1s0): supplicant interface state: scanning -> authenticating
Jan 14 08:43:14 mattsfw NetworkManager[431515]: <info>  [1705250594.4467] device (p2p-dev-wlp1s0): supplicant management interface state: scanning -> authenticating
Jan 14 08:43:14 mattsfw NetworkManager[431515]: <info>  [1705250594.4529] device (wlp1s0): supplicant interface state: authenticating -> associating
Jan 14 08:43:14 mattsfw NetworkManager[431515]: <info>  [1705250594.4529] device (p2p-dev-wlp1s0): supplicant management interface state: authenticating -> associating
Jan 14 08:43:15 mattsfw NetworkManager[431515]: <info>  [1705250595.4461] device (wlp1s0): supplicant interface state: associating -> disconnected
Jan 14 08:43:15 mattsfw NetworkManager[431515]: <info>  [1705250595.4462] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> disconnected
Jan 14 08:43:15 mattsfw NetworkManager[431515]: <info>  [1705250595.9516] device (wlp1s0): supplicant interface state: disconnected -> scanning
Jan 14 08:43:15 mattsfw NetworkManager[431515]: <info>  [1705250595.9517] device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> scanning
Jan 14 08:43:16 mattsfw NetworkManager[431515]: <info>  [1705250596.3116] device (wlp1s0): supplicant interface state: scanning -> authenticating
Jan 14 08:43:16 mattsfw NetworkManager[431515]: <info>  [1705250596.3117] device (p2p-dev-wlp1s0): supplicant management interface state: scanning -> authenticating
Jan 14 08:43:21 mattsfw NetworkManager[431515]: <warn>  [1705250601.0418] device (wlp1s0): link timed out.
Jan 14 08:43:21 mattsfw NetworkManager[431515]: <info>  [1705250601.0420] device (wlp1s0): state change: activated -> failed (reason 'supplicant-timeout', sys-iface-state: 'managed')
Jan 14 08:43:21 mattsfw NetworkManager[431515]: <info>  [1705250601.0422] manager: NetworkManager state is now DISCONNECTED
Jan 14 08:43:21 mattsfw NetworkManager[431515]: <info>  [1705250601.0947] device (wlp1s0): set-hw-addr: set MAC address to BE:B9:3D:0D:44:96 (scanning)
Jan 14 08:43:21 mattsfw NetworkManager[431515]: <warn>  [1705250601.3289] device (wlp1s0): Activation: failed for connection 'xfmaps'
Jan 14 08:43:21 mattsfw NetworkManager[431515]: <info>  [1705250601.3293] device (wlp1s0): supplicant interface state: authenticating -> interface_disabled
Jan 14 08:43:21 mattsfw NetworkManager[431515]: <info>  [1705250601.3293] device (p2p-dev-wlp1s0): supplicant management interface state: authenticating -> interface_disabled
Jan 14 08:43:21 mattsfw NetworkManager[431515]: <info>  [1705250601.3357] device (wlp1s0): supplicant interface state: interface_disabled -> scanning
Jan 14 08:43:21 mattsfw NetworkManager[431515]: <info>  [1705250601.3357] device (p2p-dev-wlp1s0): supplicant management interface state: interface_disabled -> scanning
Jan 14 08:43:21 mattsfw NetworkManager[431515]: <info>  [1705250601.3361] device (wlp1s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jan 14 08:43:21 mattsfw NetworkManager[431515]: <info>  [1705250601.3365] dhcp4 (wlp1s0): canceled DHCP transaction
Jan 14 08:43:21 mattsfw NetworkManager[431515]: <info>  [1705250601.3365] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Jan 14 08:43:21 mattsfw NetworkManager[431515]: <info>  [1705250601.3365] dhcp4 (wlp1s0): state changed no lease
Jan 14 08:43:21 mattsfw NetworkManager[431515]: <info>  [1705250601.3366] dhcp6 (wlp1s0): canceled DHCP transaction
Jan 14 08:43:21 mattsfw NetworkManager[431515]: <info>  [1705250601.3366] dhcp6 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Jan 14 08:43:21 mattsfw NetworkManager[431515]: <info>  [1705250601.3366] dhcp6 (wlp1s0): state changed no lease
Jan 14 08:43:47 mattsfw NetworkManager[431515]: <info>  [1705250627.5872] device (wlp1s0): supplicant interface state: scanning -> disconnected
Jan 14 08:43:47 mattsfw NetworkManager[431515]: <info>  [1705250627.5874] device (p2p-dev-wlp1s0): supplicant management interface state: scanning -> disconnected
type or paste code here

Matt_Hartley · January 16, 2024, 7:11pm

Absolutely the best course of action is to file a kernel bug with Fedora. It’s not something I have experienced myself, but, clearly a regression is happening.

Just out of curiosity, what is the last line of output from:

sudo dnf install iw -y && for interface in $(iw dev | awk '/Interface/ {print $2}'); do iw dev "$interface" get power_save; done

Curious what your power save status is.

We did have some updates hit with Fedora dealing with the bug described here. This dealt with a different issue, I wonder if this change is reflected in what you’re experiencing. This bug fix dealt with slow wifi issues with the Mediatek card.

Now, all of this aside, you have clearly shown the change if the kernel creates or resolves the issue. Please file a bug report with Fedora, tag me here once this is done and I will then ping the needed folks to be aware of this.

Matthew_Shook · January 16, 2024, 8:27pm

Pasting that command doesn’t give an output, just a blank line with the cursor in the middle of the line. I’ve let it run for a few minutes and I have to ^c to get out of it. Oddly, it doesn’t ask for a sudo auth.

I had switched my power management option in KDE settings to “performance.” I think this does reduce the problem, but not eliminate it. I’ve gotten kind of sick of doing the updates and restores, hoping for improvement. I’m going to install Ubuntu LTS to an SD card and try my luck with that. I’ll file a Fedora bug in the near future.

Matt_Hartley · January 16, 2024, 10:11pm

Hmm, regardless of desktop, on Fedora, it absolutely should have worked fine. Appreciate the update on events. For this to simply stop like that tells me something is definitely wrong with the configuration.

SD card behavior should work, however I’d avoid suspending on it as this is untested on SD. Likely won’t resume.

Do make sure to follow the guide, ensuring your on the absolutely correct kernel (very important) and all the steps are followed step by step. From this link, steps 1 and 2 are important.

Ideally, we want folks using Fedora Workstation (GNOME) using the guide, or as you have indicated, using Ubuntu LTS using the guide steps.

Matthew_Shook · January 17, 2024, 3:17am

I realized the problem with the command you suggested. I’m using fish as my shell and bash scripting isn’t compatible. Running the command under bash gives the last line:
Power save: on
I plugged in to AC and the output was the same.

I installed Ubuntu 22.04 on my SD card and I liked it a lot more than Fedora Gnome. I did make sure to follow all those guides. I used Ubuntu for about an hour without any wifi problems. I think there’s a good chance I will replace Fedora KDE on my NVME.

You were right about suspend with the SD card. It wasn’t a problem with Fedora GNOME but on Ubuntu after waking the login screen was glitchy and wouldn’t let me enter a password. The TTY was throwing a bunch of errors about files being read-only. I’ll assume this won’t be an issue on the SSD.

The Fedora Bugzilla instructions were a bit complicated and I probably won’t sign up for that if I switch to Ubuntu.

Matthew_Shook · January 17, 2024, 10:12pm

I did an install of Ubuntu 22.04 on my NVME, formatting the Fedora partition and keeping the Windows partition.

The wifi seemed fine on the Ubuntu live USB, and and I went ahead with the install choosing the option to include installing needed updates with the install. Looking back at the guide, that might not have been recommended. The fresh install of Ubuntu 22.04 was horrible. The disconnect/reconnect cycle started immediately and got to the stage where there were no detected networks within a few minutes. I was never able to complete the OEM kernel command. The NetworkManager log is below.

As recommended by the ticket I started, I am using Windows as my daily driver today. It seems to be fine for the last 30 minutes.

In summary, wifi was great on Fedora 39-KDE until mid-December. Then something happened and I started having wifi drops using Fedora-KDE, Fedora-GNOME, Manjaro-KDE, and Ubuntu-GNOME. The live USBs for all of those worked fine, implying to me there was a regression last month in something shared by those distros. Windows seems fine. That sounds like a software problem but I don’t get the impression other people are having this problem.

I’ll hang out on Windows for awhile but I’ll retry the Ubuntu 22.04 install and try doing the OEM kernel before doing the updates.

`Jan 17 01:21:12 mattlappy systemd[1]: Starting Network Manager...
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.5317] NetworkManager (version 1.36.6) is starting... (for the first time)
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.5317] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (run: 10-globally-managed-devices.conf) (etc: default-wifi-powersave-on.conf)
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.5364] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Jan 17 01:21:12 mattlappy systemd[1]: Started Network Manager.
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.5382] manager[0x55a7b72e6000]: monitoring kernel firmware directory '/lib/firmware'.
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.5382] monitoring ifupdown state file '/run/network/ifstate'.
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6120] hostname: hostname: using hostnamed
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6120] hostname: static hostname changed from (none) to "mattlappy"
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6121] dns-mgr[0x55a7b72c54a0]: init: dns=systemd-resolved rc-manager=unmanaged (auto), plugin=systemd-resolved
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6127] manager[0x55a7b72e6000]: rfkill: Wi-Fi hardware radio set enabled
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6127] manager[0x55a7b72e6000]: rfkill: WWAN hardware radio set enabled
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6136] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-adsl.so)
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6153] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-bluetooth.so)
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6163] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-team.so)
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6168] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-wifi.so)
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6171] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-wwan.so)
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6173] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6173] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6173] manager: Networking is enabled by state file
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6178] settings: Loaded settings plugin: ifupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-settings-plugin-ifupdown.so")
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6178] settings: Loaded settings plugin: keyfile (internal)
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6178] ifupdown: management mode: unmanaged
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6178] ifupdown: interfaces file /etc/network/interfaces doesn't exist
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6188] dhcp-init: Using DHCP client 'internal'
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6188] device (lo): carrier: link connected
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6189] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6191] failed to open /run/network/ifstate
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6197] manager: startup complete
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.6208] modem-manager: ModemManager available
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.7609] device (wlan0): driver supports Access Point (AP) mode
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.7613] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/2)
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.7617] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:02.2/0000:01:00.0/ieee80211/phy0/rfkill1) (driver mt7921e)
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.7907] device (wlan0): interface index 2 renamed iface from 'wlan0' to 'wlp1s0'
Jan 17 01:21:12 mattlappy NetworkManager[611]: <info>  [1705483272.7956] device (wlp1s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 17 01:21:13 mattlappy NetworkManager[611]: <info>  [1705483273.3510] device (wlp1s0): supplicant interface state: internal-starting -> disconnected
Jan 17 01:21:13 mattlappy NetworkManager[611]: <info>  [1705483273.3511] Wi-Fi P2P device controlled by interface wlp1s0 created
Jan 17 01:21:13 mattlappy NetworkManager[611]: <info>  [1705483273.3512] manager: (p2p-dev-wlp1s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/3)
Jan 17 01:21:13 mattlappy NetworkManager[611]: <info>  [1705483273.3512] device (p2p-dev-wlp1s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 17 01:21:13 mattlappy NetworkManager[611]: <info>  [1705483273.3514] device (wlp1s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Jan 17 01:21:13 mattlappy NetworkManager[611]: <info>  [1705483273.3516] device (p2p-dev-wlp1s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Jan 17 01:21:14 mattlappy NetworkManager[611]: <info>  [1705483274.4554] agent-manager: agent[a2aecb7534122b12,:1.41/org.gnome.Shell.NetworkAgent/128]: agent registered
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.4810] policy: auto-activating connection 'xfmaps' (f1b92ee8-0bac-40a2-b78b-340be33f071b)
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.4813] device (wlp1s0): Activation: starting connection 'xfmaps' (f1b92ee8-0bac-40a2-b78b-340be33f071b)
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.4813] device (wlp1s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.4814] manager: NetworkManager state is now CONNECTING
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.4815] device (wlp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.4816] device (wlp1s0): Activation: (wifi) access point 'xfmaps' has security, but secrets are required.
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.4817] device (wlp1s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.4820] device (wlp1s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.4821] device (wlp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.4822] device (wlp1s0): Activation: (wifi) connection 'xfmaps' has security, and secrets exist.  No new secrets needed.
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.4822] Config: added 'ssid' value 'xfmaps'
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.4822] Config: added 'scan_ssid' value '1'
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.4822] Config: added 'bgscan' value 'simple:30:-70:86400'
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.4822] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.4823] Config: added 'auth_alg' value 'OPEN'
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.4823] Config: added 'psk' value '<hidden>'
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.6546] device (wlp1s0): supplicant interface state: disconnected -> authenticating
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.6546] device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> authenticating
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.6998] device (wlp1s0): supplicant interface state: authenticating -> associating
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.6999] device (p2p-dev-wlp1s0): supplicant management interface state: authenticating -> associating
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.7650] device (wlp1s0): supplicant interface state: associating -> 4way_handshake
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.7651] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> 4way_handshake
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.9194] device (wlp1s0): supplicant interface state: 4way_handshake -> completed
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.9194] device (wlp1s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "xfmaps"
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.9194] device (p2p-dev-wlp1s0): supplicant management interface state: 4way_handshake -> completed
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.9195] device (wlp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.9198] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.9621] dhcp4 (wlp1s0): state changed new lease, address=10.0.0.192
Jan 17 01:21:15 mattlappy NetworkManager[611]: <info>  [1705483275.9678] device (wlp1s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 17 01:21:16 mattlappy NetworkManager[611]: <info>  [1705483276.0072] device (wlp1s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 17 01:21:16 mattlappy NetworkManager[611]: <info>  [1705483276.0073] device (wlp1s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 17 01:21:16 mattlappy NetworkManager[611]: <info>  [1705483276.0074] manager: NetworkManager state is now CONNECTED_LOCAL
Jan 17 01:21:16 mattlappy NetworkManager[611]: <info>  [1705483276.0077] manager: NetworkManager state is now CONNECTED_SITE
Jan 17 01:21:16 mattlappy NetworkManager[611]: <info>  [1705483276.0077] policy: set 'xfmaps' (wlp1s0) as default for IPv4 routing and DNS
Jan 17 01:21:16 mattlappy NetworkManager[611]: <info>  [1705483276.0080] device (wlp1s0): Activation: successful, device activated.
Jan 17 01:21:16 mattlappy NetworkManager[611]: <info>  [1705483276.1523] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 17 01:21:47 mattlappy NetworkManager[611]: <info>  [1705483307.8670] agent-manager: agent[b647d8257c487946,:1.88/org.gnome.Shell.NetworkAgent/1000]: agent registered
Jan 17 01:22:09 mattlappy NetworkManager[611]: <info>  [1705483329.6382] device (wlp1s0): supplicant interface state: completed -> authenticating
Jan 17 01:22:09 mattlappy NetworkManager[611]: <info>  [1705483329.6382] device (p2p-dev-wlp1s0): supplicant management interface state: completed -> authenticating
Jan 17 01:22:09 mattlappy NetworkManager[611]: <info>  [1705483329.6385] device (wlp1s0): ip:dhcp4: restarting
Jan 17 01:22:09 mattlappy NetworkManager[611]: <info>  [1705483329.6386] dhcp4 (wlp1s0): canceled DHCP transaction
Jan 17 01:22:09 mattlappy NetworkManager[611]: <info>  [1705483329.6387] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Jan 17 01:22:09 mattlappy NetworkManager[611]: <info>  [1705483329.6387] dhcp4 (wlp1s0): state changed no lease
Jan 17 01:22:09 mattlappy NetworkManager[611]: <info>  [1705483329.6387] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Jan 17 01:22:15 mattlappy NetworkManager[611]: <info>  [1705483335.6994] device (wlp1s0): supplicant interface state: authenticating -> disconnected
Jan 17 01:22:15 mattlappy NetworkManager[611]: <info>  [1705483335.6995] device (p2p-dev-wlp1s0): supplicant management interface state: authenticating -> disconnected
Jan 17 01:22:15 mattlappy NetworkManager[611]: <info>  [1705483335.8045] device (wlp1s0): supplicant interface state: disconnected -> scanning
Jan 17 01:22:15 mattlappy NetworkManager[611]: <info>  [1705483335.8046] device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> scanning
Jan 17 01:22:31 mattlappy NetworkManager[611]: <warn>  [1705483351.0215] device (wlp1s0): link timed out.
Jan 17 01:22:31 mattlappy NetworkManager[611]: <info>  [1705483351.0217] device (wlp1s0): state change: activated -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jan 17 01:22:31 mattlappy NetworkManager[611]: <info>  [1705483351.0220] manager: NetworkManager state is now DISCONNECTED
Jan 17 01:22:31 mattlappy NetworkManager[611]: <warn>  [1705483351.0223] device (wlp1s0): Activation: failed for connection 'xfmaps'
Jan 17 01:22:31 mattlappy NetworkManager[611]: <info>  [1705483351.0227] device (wlp1s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jan 17 01:22:31 mattlappy NetworkManager[611]: <info>  [1705483351.0743] dhcp4 (wlp1s0): canceled DHCP transaction
Jan 17 01:22:44 mattlappy NetworkManager[611]: <info>  [1705483364.1693] device (wlp1s0): supplicant interface state: scanning -> disconnected
Jan 17 01:22:44 mattlappy NetworkManager[611]: <info>  [1705483364.1693] device (p2p-dev-wlp1s0): supplicant management interface state: scanning -> disconnected
Jan 17 01:22:44 mattlappy NetworkManager[611]: <info>  [1705483364.1695] policy: auto-activating connection 'xfmaps' (f1b92ee8-0bac-40a2-b78b-340be33f071b)
Jan 17 01:22:44 mattlappy NetworkManager[611]: <info>  [1705483364.1699] device (wlp1s0): Activation: starting connection 'xfmaps' (f1b92ee8-0bac-40a2-b78b-340be33f071b)
Jan 17 01:22:44 mattlappy NetworkManager[611]: <info>  [1705483364.1700] device (wlp1s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 17 01:22:44 mattlappy NetworkManager[611]: <info>  [1705483364.1702] manager: NetworkManager state is now CONNECTING
Jan 17 01:22:44 mattlappy NetworkManager[611]: <info>  [1705483364.1704] device (wlp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 17 01:22:44 mattlappy NetworkManager[611]: <info>  [1705483364.1707] device (wlp1s0): Activation: (wifi) access point 'xfmaps' has security, but secrets are required.
Jan 17 01:22:44 mattlappy NetworkManager[611]: <info>  [1705483364.1707] device (wlp1s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jan 17 01:22:44 mattlappy NetworkManager[611]: <info>  [1705483364.1713] device (wlp1s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 17 01:22:44 mattlappy NetworkManager[611]: <info>  [1705483364.1714] device (wlp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 17 01:22:44 mattlappy NetworkManager[611]: <info>  [1705483364.1715] device (wlp1s0): Activation: (wifi) connection 'xfmaps' has security, and secrets exist.  No new secrets needed.
Jan 17 01:22:44 mattlappy NetworkManager[611]: <info>  [1705483364.1715] Config: added 'ssid' value 'xfmaps'
Jan 17 01:22:44 mattlappy NetworkManager[611]: <info>  [1705483364.1715] Config: added 'scan_ssid' value '1'
Jan 17 01:22:44 mattlappy NetworkManager[611]: <info>  [1705483364.1715] Config: added 'bgscan' value 'simple:30:-70:86400'
Jan 17 01:22:44 mattlappy NetworkManager[611]: <info>  [1705483364.1715] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Jan 17 01:22:44 mattlappy NetworkManager[611]: <info>  [1705483364.1715] Config: added 'auth_alg' value 'OPEN'
Jan 17 01:22:44 mattlappy NetworkManager[611]: <info>  [1705483364.1715] Config: added 'psk' value '<hidden>'
Jan 17 01:22:44 mattlappy NetworkManager[611]: <info>  [1705483364.1822] device (wlp1s0): supplicant interface state: disconnected -> scanning
Jan 17 01:22:44 mattlappy NetworkManager[611]: <info>  [1705483364.1822] device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> scanning
Jan 17 01:23:09 mattlappy NetworkManager[611]: <warn>  [1705483389.0199] device (wlp1s0): Activation: (wifi) association took too long, failing activation
Jan 17 01:23:09 mattlappy NetworkManager[611]: <info>  [1705483389.0200] device (wlp1s0): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jan 17 01:23:09 mattlappy NetworkManager[611]: <info>  [1705483389.0203] manager: NetworkManager state is now DISCONNECTED
Jan 17 01:23:09 mattlappy NetworkManager[611]: <warn>  [1705483389.0206] device (wlp1s0): Activation: failed for connection 'xfmaps'
Jan 17 01:23:09 mattlappy NetworkManager[611]: <info>  [1705483389.0208] device (wlp1s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jan 17 01:23:09 mattlappy NetworkManager[611]: <info>  [1705483389.0227] device (wlp1s0): supplicant interface state: scanning -> disconnected
Jan 17 01:23:09 mattlappy NetworkManager[611]: <info>  [1705483389.0227] device (p2p-dev-wlp1s0): supplicant management interface state: scanning -> disconnected
`

Matt_Hartley · January 18, 2024, 7:33pm

The experience feels like behavior symptomatic of old BIOS. Specifically, 3.02. Do we know for sure the following:

Fresh ISO of Ubuntu 22.04**.3** (older ISOs of Ubuntu 22.04 are really, really rough on the later hardware - almost impossible to install).
Checking you are on the correct BIOS? You should be on 3.03.
Make sure to use a standard, default shell for copy/paste as Fish will be a bad time for this type of work. Fish is awesome, but not for this sort of thing.

I use Ubuntu 22.04.3 (GNOME desktop) every day. Setup correctly, on the 3.03 BIOS, guide steps followed, runs like a treat.

If Windows is meeting your needs instead, this works too.

Matthew_Shook · January 20, 2024, 6:56am

Sorry, it seems to be getting worse. I confirmed the 3.03 bios, I confirmed I had the 22.04.3 iso and reinstalled. The install connected to my wifi fine. After the first boot into the new system the wifi now isn’t working at all. “No Networks”

I don’t have a great way to get the NetworkManager log onto my phone, so here’s a pic.

I’ll update my support ticket as well. I’m wondering if replacing my WiFi card would help.

Matthew_Shook · January 20, 2024, 7:59am

SUCCESS?
I think I may have finally gotten to the bottom of this!
I had a working Fedora install using the default kernel. Around the 6.5 or 6.6 upgrade, there was a waxing and waning wifi regression.

Live USBs (presumably running an old kernel) worked, but the installed systems did not after updating. The regression was so bad in Ubuntu 22.04.3 that I couldn’t download the OEM kernel.

BUT I looked closer at the GRUB menu (it’s really hard to read) and saw the option to boot a 6.2 kernel, rather than the default 6.5. (Maybe 6.2 is what is on the live USB?). Wifi works with the 6.2 kernel! I followed the instructions for installing the OEM kernel, then when I rebooted I clicked through the grub options to find 6.1.0-1028-oem. So far, the wifi seems stable! I was about to give up.

So in review, for future users with this problem: Fedora and Ubuntu 22.03 are installing 6.5+ kernels that cause a wifi regression, at least for me. For Ubuntu, use the grub options to boot the 6.2 kernel, then install the OEM kernel as directed.

I really don’t like GNOME, so I’ll probably look into KDE or Cinnamon options in the future. But now I know that higher kernel versions are to be ignored. You can mark this solved for now.

Pierre_van_Male · January 24, 2024, 3:49pm

Hi,

Not sure it is related, but I have a similar problem. I am running Ubuntu 22.04 LTS with Gnome and the kernel 6.5.0-14-generic. The wifi is disconnecting on a regular basis. When disconnected, the “Select network” window only shows the wifi I am using and no any other available. If I switch the wifi off and on again, the available wifis reappear and the computer reconnect within a few seconds.

It seems to me that this was not happening at the beginning (mid-Dec. '23) and therefore I suspect it may be related to the kernel and the issue explained here.

Best regards,
Pierre

Matthew_Shook · January 25, 2024, 12:50am

I would definitely try installing the 6.1.0-1028-oem kernel as outlined in this guide:

github.com

FrameworkComputer/linux-docs/blob/main/ubuntu-22.04-amd-fw13.md

# This is for AMD Ryzen 7040 Series configuration on the Framework Laptop 13 ONLY.

### OEM kernel and recommended configuration

- [Install OEM D kernel](#step-1)
- [Allow both CPU and platform drivers to be simultaneously active](#step-4)
- [Suspend with lid while attached to power workaround](#step-6)
- [Prevent graphical artifacts from appearing](#step-5)


### Optional and only if needed - current AMD Ryzen 7040 Series workarounds to common issues
- [MediaTek WiFi Dropout on WiFi 6E routers fix](#mediatek-wifi-dropout-on-wifi-6e-routers)
- [Buzzing sound from headphone jack](#buzzing-sound-from-headphone-jack)


## Install OEM D kernel 


### This will:

This file has been truncated. show original

There is a nice response in this other thread outlining the rationale behind using it.

To update this saga, I installed Cinnamon as an additional option for Ubuntu 22.04. The night before last I had 2 brief wifi drops while running Cinnamon and watching a video streamed on my LAN. I’m going run GNOME for a couple more days to see if it happens again.

Matt_Hartley · January 25, 2024, 1:23am

Do keep us posted. There are wifi driver updates coming, but in the short term we may have to turn off power saving if it continues.

Matthew_Shook · February 1, 2024, 12:33am

TLDR : Kernels higher than 6.2, combined with an unstable ISP-provided router, combined with stress related to power settings and sleep/wake cycles, was a recipe for headaches. The 6.1-oem kernel and a better router have eliminated my problem. I think it’s related to the Ubuntu kernel-firmware bug linked below.

This big isn’t affecting me on a daily basis now, but I think I’ve narrowed down some information. At some point around when I started having problems in December, my Xfinity cable modem has been very sluggish making connections. Wifi as well as ethernet connections take 30-45 seconds to start. This isn’t noticible on smartphones but this week my son mentioned his TV’s ethernet connection takes 45 seconds to start working, or the ethernet will fail and wifi will connect as a backup. He hadn’t mentioned it, but it had been annoying him for weeks. I have also noticed the Framework’s wifi takes longer to connect after login than it used to but was happy it was working at all. Every few days there will be a 30-45 second drop with a timeout noted in the logs. But it’s good compared to before.

I found I could fix all these problems by by plugging a spare Wifi router into the cable modem and connecting the TV’s ethernet and Framework’s wifi to that. The TV and the Framework are working much more smoothly with a stable router. Obviously a wifi card shouldn’t respond to a few timeouts by refusing to search for any network, but that was the issue with the newer kernel.

Looking at a pending firmware update in Synaptic, I saw this bug fix that sounds quite relevant:
“WCN6856 Wi-FI Unavailable and no function during suspend stress”

It seems to me, that if this is the issue, most people with normally-functioning wifi networks would never encounter this. (I’m not sure if it even refers to the right hardware). Now that I have everything working so well, I’m hesitant to try to call Xfinity for troubleshooting or upgrade to the newest linux-firmware package.