Framework desktop can only connect to 2.4 networks

Framework Desktop
1

Hey there. I am a Linux neophyte, so please bear with me. I am running Fedora Workstation 44 on a AMD RYZEN AI MAX+ 395 with 128GB of ram.

When I updated to Fedora 44 from 43, I began to experience a wifi issue where any time I attempt to connect to any network frequency 5GHz or above I just get the user name/password prompt over and over with no ability to connect.

Second, I see my WIFI network listed twice. I actually have more than one router setup as access points using the same SSID. Previously (and on all other devices as well as the previous 43 install on this device and the current Bazzite install), the different access points using the same SSID and password all appeared as a single WIFI access point.

I don’t know if or how these two issues are related, but they manifested concurrently and seem to both represent some inability of the system to resolve the WIFI networks correctly. Why 2.4 GHz is unaffected, I cannot say.

I am able to connect to 2.4 GHz just fine from my Fedora 44 install, and all frequencies worked just fine on Fedora 43. Moreover, I am running a dual boot with Bazzite on another disc and Bazzite is still able to connect to all networks with the same credentials.

So the hardware is physically fine, there’s just something going on with the Fedora 44 install that is causing me issues. I have searched endlessly trying to solve the issue, as well as attempting to update daily to see if the issue resolves, but so far, no luck.

Worth mentioning, in the Software app, I get a System Update indication every time I check, even directly after updating. I am not sure what this is about. When i attempt to update via DNF from the CLI, everything seems up to date.

My sincere thanks to anyone who can help. It’s not the end of the world, but I’d like to be able to connect to my other networks.

2

What is the output of
’ sudo iw reg get ’

(without the single quotes) when put into a terminal window?

3

Run dmesg on your console - this lists recent system messages. See if there is anything in there that looks like an error. It should not have anything sensitive in there, so you can post here if you want, though some people like to anonymise serial numbers and MAC/IP addresses.

4

With respect, I’m not sure that’s the best advice for a neophyte. The hundreds (or 1000s) of lines that will output are mostly gobbledygook if you’re unfamiliar with the behaviour of the sub-systems that produce them.

Something like:
$ dmesg | grep -Ev ' \[UFW [A-Z]+\] ' | grep -Ei '(wi-*fi|wlp166s0|error)'

will focus the output on the potentially interesting stuff.

I’m unfamiliar with Fedora but I’m pretty sure it won’t use the adapter name wlp166s0. Hopefully someone who knows Fedora can chime in with advice on how to determine its name.

edit: fixed the copy-paste-broken regex (somehow we lost the backslashes).

1 Like
5

I saw this same exact problem on Bazzite (monolithic boot, no secondary OS) starting a bit over a month ago. No longer would connect to my wifi7 AP ability --only saw it as an AX network, and it wouldn’t connect. And it doesn’t see my normie 5gHz AC SSID at all. The 2.4gHz wasn’t even full bandwidth. The wifi ran like a dream for 3 months on the box, until it didn’t

I plugged in a LAN cable and didn’t bother. I’ve seen so many wifi cards go bad (even Intel AX ones), and this one is a MediaTek to boot, I just moved on. I should go and bug test it, but I have the cable in place now, and cables have always been more reliable than wifi.

With respect, I’m not sure that’s the best advice for a neophyte. The hundreds (or 1000s) of lines that will output are mostly gobbledygook if you’re unfamiliar with the behaviour of the sub-systems that produce them.

Something like:
$ dmesg | grep -Ev ' [UFW [A-Z]+] ' | grep -Ei '(wi-*fi|wlp166s0|error)'

will focus the output on the potentially interesting stuff.

I’m unfamiliar with Fedora but I’m pretty sure it won’t use the adapter name wlp166s0. Hopefully someone who knows Fedora can chime in with advice on how to determine its name.

Here’s what I return

[    2.289538] i8042 i8042: probe with driver i8042 failed with error -5
[    2.424484] RAS: Correctable Errors collector initialized.
[    3.665735] ucsi_acpi USBC000:00: unknown error 256
[    4.186762] ucsi_acpi USBC000:00: unknown error 256
[ 8257.592590] critical target error, dev sr0, sector 64 op 0x0:(READ) flags 0x880700 phys_seg 1 prio class 2
[ 8257.592607] I/O error, dev sr0, sector 64 op 0x0:(READ) flags 0x800000 phys_seg 1 prio class 2
[ 8257.592609] Buffer I/O error on dev sr0, logical block 64, async page read
[ 8257.592614] I/O error, dev sr0, sector 65 op 0x0:(READ) flags 0x800000 phys_seg 1 prio class 2
[ 8257.592615] Buffer I/O error on dev sr0, logical block 65, async page read
[ 8257.592617] I/O error, dev sr0, sector 66 op 0x0:(READ) flags 0x800000 phys_seg 1 prio class 2
[ 8257.592617] Buffer I/O error on dev sr0, logical block 66, async page read
[ 8257.592619] I/O error, dev sr0, sector 67 op 0x0:(READ) flags 0x800000 phys_seg 1 prio class 2
[ 8257.592619] Buffer I/O error on dev sr0, logical block 67, async page read
[ 8257.592620] I/O error, dev sr0, sector 68 op 0x0:(READ) flags 0x800000 phys_seg 1 prio class 2
[ 8257.592621] Buffer I/O error on dev sr0, logical block 68, async page read
[ 8257.592622] I/O error, dev sr0, sector 69 op 0x0:(READ) flags 0x800000 phys_seg 1 prio class 2
[ 8257.592623] Buffer I/O error on dev sr0, logical block 69, async page read
[ 8257.592624] I/O error, dev sr0, sector 70 op 0x0:(READ) flags 0x800000 phys_seg 1 prio class 2
[ 8257.592624] Buffer I/O error on dev sr0, logical block 70, async page read
[ 8257.592626] I/O error, dev sr0, sector 71 op 0x0:(READ) flags 0x800000 phys_seg 1 prio class 2
[ 8257.592626] Buffer I/O error on dev sr0, logical block 71, async page read
[ 8257.592630] I/O error, dev sr0, sector 64 op 0x0:(READ) flags 0x800000 phys_seg 1 prio class 2
[ 8257.592630] Buffer I/O error on dev sr0, logical block 64, async page read
[ 8257.592632] Buffer I/O error on dev sr0, logical block 65, async page read
Marc@bazzite:/var/home/Marc$