Framework 13 has issues connecting to the internet

Framework Laptop 13 Linux
1

Which Linux distro are you using?
Fedora Linux (KDE Plasma)

Which release version?
41

Which kernel are you using?
6.12.8-200.fc41

Which BIOS version are you using?
3.05

Which Framework Laptop 13 model are you using? (AMD Ryzen™ 7040 Series, Intel® Core™ Ultra Series 1, 13th Gen Intel® Core™ , 12th Gen Intel® Core™, 11th Gen Intel® Core™)
AMD Ryzen™ 7040 Series with the 7640U

Hi, recently my laptop has experienced issues connecting to the internet as in the wifi widget in Plasma no networks are listed.

Furthermore, the laptop would sometimes completely freeze and the caps lock would begin blinking forcing me to power cycle it. Upon the next boot the wifi issues would continue, but they wouldn’t always lead to a freeze again.

This issue has occurred both on all of the three latest stable versions of the kernel that fedora provides.

Sometimes this issues occurred in my home with internet, and sometimes it would occur when out in places without internet (though is seems to me like the latter happens more than the former).

Worst of all is that this issue is not consistent. Some days it seems to be working fine, and other it complete fails.

When checking dmesg I found a loop of failures for a “driver own” to occur as well as the wifi chip requesting a disconnection. Also when this issue occurs the wireless chip (wlp1s0) will sometimes be missing from the output of $ ip link.

The full logs are available at https://drive.google.com/drive/folders/1F3UXreG3PutV06dO02h0Qial8hgitkkT?usp=drive_link. The one on Jan 12 was taken at home with internet connection on boot, and the one on Jan 14 was taken out in public without internet connection on boot.

Any help fixing this would be much appreciated!

2

Hello Eris,

  1. Is this happening on Ubuntu as well or just Fedora?
  2. The fact that the card is not showing up in that output seems like it could be an issue with the card. Can you confirm that the antennas are fully connected and such?
3
  1. I have only tried it on Fedora both the version I installed as well as the live boot from my flash drive. On the live version the problem did seem to happen with respect to it not being able to find any networks, but I’m fairly certain I didn’t end up checking the logs to verify the same messages were present.
  2. I just checked and both antennas are fully seated into the wireless card and both seem to be routed correctly into the back of the laptop.
4

From the logs that you shared I do see these messages:

[ 4044.974087] wlp1s0: Driver requested disconnection from AP 00:00:00:00:00:00
[ 4048.038003] mt7921e 0000:01:00.0: Message 00020001 (seq 13) timeout
[ 4049.266542] mt7921e 0000:01:00.0: driver own failed
[ 4050.503598] mt7921e 0000:01:00.0: driver own failed
[ 4051.785788] mt7921e 0000:01:00.0: Timeout for driver own
[ 4053.047927] mt7921e 0000:01:00.0: driver own failed
[ 4054.363012] mt7921e 0000:01:00.0: Timeout for driver own
[ 4055.637061] mt7921e 0000:01:00.0: driver own failed
[ 4056.940372] mt7921e 0000:01:00.0: Timeout for driver own
[ 4058.129109] mt7921e 0000:01:00.0: driver own failed
[ 4059.394898] mt7921e 0000:01:00.0: Timeout for driver own
[ 4060.673674] mt7921e 0000:01:00.0: driver own failed
[ 4061.979951] mt7921e 0000:01:00.0: Timeout for driver own
[ 4063.265599] mt7921e 0000:01:00.0: driver own failed
[ 4064.566257] mt7921e 0000:01:00.0: Timeout for driver own
[ 4065.762732] mt7921e 0000:01:00.0: driver own failed
[ 4067.023302] mt7921e 0000:01:00.0: Timeout for driver own
[ 4068.238100] mt7921e 0000:01:00.0: driver own failed
[ 4069.525868] mt7921e 0000:01:00.0: Timeout for driver own
[ 4070.762854] mt7921e 0000:01:00.0: driver own failed
[ 4072.020388] mt7921e 0000:01:00.0: Timeout for driver own
[ 4073.202393] mt7921e 0000:01:00.0: driver own failed
[ 4074.526362] mt7921e 0000:01:00.0: Timeout for driver own
[ 4074.526385] mt7921e 0000:01:00.0: chip reset failed

Since there are issues in the live disk I suspect you may have a bad Wi-Fi card or a driver issue (need a new kernel update). I would open a support ticket when you can.

5

At this point I would agree. Thank you for your help!

6

Glad to help!

7

Hi @Eris_F,

Based on this:

This

and

and

Bundle the above with what @ahoneybun pointed out from the logs. this is shaping up to be ticket worthy.

Let’s do this, as I lack the available cycles to help much on the forums right now. We will want

  • Download and run this wi-fi testing tool
    The initial results will give you a base line of a working environment. Locate the created wifi_diagnosis.log file. Keep this file.

  • Open a ticket here. Be sure to include a link to this thread in the ticket. When they reply, provide the logs (I know it may feel redundant) they request and include your wifi_diagnosis.log file.

  • They may also ask for photos of your wifi card installation (looking for pinched wires, etc).

  • Please be sure to indicate if this is a vanilla install of Fedora 41 (Plasma) and clarify if you have made any changes to your default provided linux-firmware.

1 Like
8

Will do, I’ve just recently opened a ticket.

Thank you for your reply!

1 Like