Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently

Bug #2007875 reported by David Burke
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux-firmware (Ubuntu)
Fix Released
Undecided
Unassigned
Jammy
Fix Released
High
You-Sheng Yang
Kinetic
Fix Released
Undecided
Unassigned
Lunar
Fix Released
Undecided
Unassigned
oem-somerville-tentacool-meta (Ubuntu)
Invalid
Undecided
Unassigned
Jammy
Invalid
Undecided
Kai-Chuan Hsieh
Kinetic
Invalid
Undecided
Unassigned
Lunar
Invalid
Undecided
Unassigned

Bug Description

[SRU Justification]

[Impact]

backport-iwlwifi-dkms/kinetic is being built into hwe-5.19 kernel, and -73 firmware are supported bug missing. On one user reported issue, this fixes WiFi stability on 5G band.

[Fix]

New upstreamed firmware revision fixes this issue.

[Test Case]

1. Boot hwe-5.19 kernel
2. iwlwifi-so-a0-gf-a0-73.ucode firmware should be loaded
3. Browse the web, usually takes between 1 and 5 minutes
4. Networking will cut out

[Where problems could occur]

This affects only users need both backport-iwlwifi-dkms and hwe-5.19 kernel on WiFi stability.

[Other Info]

While Kinetic and above have them all, only Jammy is nominated.

========== original bug report ==========

I'm using the stock Dell Ubuntu 22.04 image on my XPS 13 Plus (9320). Recently I received some kernel updates, the 5.19 kernel used in 22.10 and a 6.0 oem kernel. Both updates break wifi. It seems to only do so on newer 5.7 GHz access points.

1. Boot latest 6.0 oem kernel
2. Browse the web, usually takes between 1 and 5 minutes.
3. Networking will cut out.

Disabling networking and starting again will fix it until it happens again in a few minutes. This will repeat indefinitely, essentially making wireless useless.

The attached dmesg log reliably shows up when it fails, showing iwlwifi failing and a (network?) hardware reset request.

It witnessed this happen months ago on 22.10, which led me to using the Dell stock 22.04 image. But it seems even the newer OEM kernel is affected.

A workaround is to select the older 5.15 kernel in grub. I find on this laptop, one must hit escape precisely 1 second after seeing the Dell logo on boot. Alternatively one could edit /etc/grub/default and set a longer timeout.

Let me know if this bug report would be better to go to Dell as a support request instead.

Revision history for this message
David Burke (bufke) wrote :
David Burke (bufke)
description: updated
Revision history for this message
Kai-Chuan Hsieh (kchsieh) wrote (last edit ):

Hello,

Could you try the latest pnvm file to see if it improves the issue?
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/tree/iwlwifi-so-a0-gf-a0.pnvm

Or copy the attached file to /lib/firmware and reboot.

Thanks,

Changed in oem-somerville-tentacool-meta (Ubuntu):
assignee: nobody → Kai-Chuan Hsieh (kchsieh)
tags: added: jellyfish-tentacool
Revision history for this message
Kai-Chuan Hsieh (kchsieh) wrote :

Attach firmware for #2.

622e1bc1a7a94deb424bbc3dde7fce37 iwlwifi-so-a0-gf-a0.pnvm

Rex Tsai (chihchun)
tags: added: ubuntu-certified
tags: added: regression-update
Revision history for this message
David Burke (bufke) wrote :

Hello, unfortunately that file did not help. I get the same error. To confirm I did this right

md5sum /lib/firmware/iwlwifi-so-a0-gf-a0.pnvm
622e1bc1a7a94deb424bbc3dde7fce37 /lib/firmware/iwlwifi-so-a0-gf-a0.pnvm

I rebooted with 6.0.0-1011-oem and got the same error with Loaded firmware version: 72.daa05125.0 so-a0-gf-a0-72.ucode in dmesg.

Revision history for this message
David Burke (bufke) wrote :

Another observation that maybe someone can help me clarify. I suspect that this bug only affects newer wifi routers, possibly only 6E. The problem always happens at my home router (Nest Wifi Pro with 6E) and not my work router (older, though does support 5Ghz).

I don't know how to get a more precise reading of the wifi router capabilities from Ubuntu. Both say "Link speed 5.7Ghz" in Wi-Fi settings. Let me know if there is anything further I could post to help debug.

Revision history for this message
Kai-Chuan Hsieh (kchsieh) wrote (last edit ):

Hello,

Could you install intel backport iwlwifi wifi on your system? and replace the firmware file by the attachment to /lib/firmware.

u@u-Precision:~/Workspace/iwlwifi-linux-firmware$ md5sum iwlwifi-so-a0-gf-a0-73.ucode
f374c4f9043c785f74a6574edea6db83 iwlwifi-so-a0-gf-a0-73.ucode
u@u-Precision:~/Workspace/iwlwifi-linux-firmware$ md5sum iwlwifi-so-a0-gf-a0.pnvm
890f1a5e9e62f355edc1900157d85c4b iwlwifi-so-a0-gf-a0.pnvm

You can install Intel backport-iwlwifi by
$ sudo apt install linux-modules-iwlwifi-generic-hwe-22.04
$ sudo reboot
You should see the kernel log that loads the -73 ucode.
Please be aware to boot into 5.19.0-32-generic.

Also, could you dump the country code setting on your machine by
$ iw reg get
The link info by
$ iwconfig
Phy capability info by
$ iw phy0 info => be aware you don't have other wifi card on your machine, otherwise the index might change.

Revision history for this message
Kai-Chuan Hsieh (kchsieh) wrote :

Attachment for #7.

Revision history for this message
David Burke (bufke) wrote :

Hello, so far so good. Wireless hasn't failed today. Using your provided files and 5.19.

Revision history for this message
Kai-Chuan Hsieh (kchsieh) wrote :

Did you install backport iwlwifi, linux-modules-iwlwifi-generic-hwe-22.04?

Revision history for this message
Kai-Chuan Hsieh (kchsieh) wrote :

reply #9,

The iwconfig seems empty, can you use command below instead, devname can be obtained by $ ip link
$ iw dev <devname> info

Revision history for this message
David Burke (bufke) wrote :

I installed the backport iwlwifi package.

$ sudo apt install linux-modules-iwlwifi-generic-hwe-22.04
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
linux-modules-iwlwifi-generic-hwe-22.04 is already the newest version (5.19.0.32.33~22.04.9).
0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded.
$ uname -a
Linux david-XPS-9320 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

I'll check the iw dev command later today.

Revision history for this message
David Burke (bufke) wrote :

$ iw dev wlp0s20f3 info
Interface wlp0s20f3
 ifindex 2
 wdev 0x1
 addr 14:75:5b:d2:87:f5
 ssid redacted
 type managed
 wiphy 0
 channel 149 (5745 MHz), width: 80 MHz, center1: 5775 MHz
 txpower 22.00 dBm
 multicast TXQ:
  qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
  0 0 0 0 0 0 0 0 0

Revision history for this message
Kai-Chuan Hsieh (kchsieh) wrote :

It seems you are connecting to the normal 5GHz band.

Can I have

$ iw dev <devname> station dump

Revision history for this message
Kai-Chuan Hsieh (kchsieh) wrote :

Hello,

Could you help to confirm that the updated bin file #8 solves your problem, so that we can proceed SRU for it.

Thanks,

Revision history for this message
David Burke (bufke) wrote :

Hello, yes it seems to solve the problem. Here's the iw command:

iw dev wlp0s20f3 station dump
Station 90:ca:fa:1f:e8:d2 (on wlp0s20f3)
 inactive time: 40 ms
 rx bytes: 7686448
 rx packets: 11478
 tx bytes: 502682
 tx packets: 3148
 tx retries: 143
 tx failed: 0
 beacon loss: 0
 beacon rx: 2062
 rx drop misc: 38
 signal: -39 [-41, -39] dBm
 signal avg: -44 dBm
 beacon signal avg: -39 dBm
 tx bitrate: 918.5 MBit/s 80MHz HE-MCS 10 HE-NSS 2 HE-GI 2 HE-DCM 0
 tx duration: 0 us
 rx bitrate: 6.0 MBit/s
 rx duration: 0 us
 authorized: yes
 authenticated: yes
 associated: yes
 preamble: long
 WMM/WME: yes
 MFP: no
 TDLS peer: no
 DTIM period: 2
 beacon interval:100
 short slot time:yes
 connected time: 356 seconds
 associated at [boottime]: 477.837s
 associated at: 1677686504168 ms
 current time: 1677686859397 ms

You-Sheng Yang (vicamo)
Changed in linux-firmware (Ubuntu Kinetic):
status: New → Fix Released
Changed in linux-firmware (Ubuntu Jammy):
status: New → Fix Released
Changed in oem-somerville-tentacool-meta (Ubuntu Kinetic):
status: New → Invalid
Changed in oem-somerville-tentacool-meta (Ubuntu Lunar):
status: New → Invalid
assignee: Kai-Chuan Hsieh (kchsieh) → nobody
Changed in oem-somerville-tentacool-meta (Ubuntu Jammy):
assignee: nobody → Kai-Chuan Hsieh (kchsieh)
Changed in linux-firmware (Ubuntu Jammy):
status: Fix Released → In Progress
importance: Undecided → High
assignee: nobody → You-Sheng Yang (vicamo)
Changed in linux-firmware (Ubuntu Lunar):
status: New → Fix Released
Revision history for this message
You-Sheng Yang (vicamo) wrote :
description: updated
Revision history for this message
You-Sheng Yang (vicamo) wrote :

Also included in https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/linux-firmware-staging version 20220329.git681281e4-0ubuntu3.10+exp.65.

Juerg Haefliger (juergh)
tags: added: kern-5946
Juerg Haefliger (juergh)
Changed in linux-firmware (Ubuntu Jammy):
status: In Progress → Fix Committed
Revision history for this message
David Burke (bufke) wrote :
Download full text (5.0 KiB)

Unfortunately, I had the same issue again today.

[88124.716563] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
[88124.716667] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[88124.716668] iwlwifi 0000:00:14.3: Transport status: 0x0000004A, valid: 6
[88124.716670] iwlwifi 0000:00:14.3: Loaded firmware version: 73.35c0a2c6.0 so-a0-gf-a0-73.ucode
[88124.716672] iwlwifi 0000:00:14.3: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL
[88124.716673] iwlwifi 0000:00:14.3: 0x00008210 | trm_hw_status0
[88124.716674] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
[88124.716675] iwlwifi 0000:00:14.3: 0x004DA772 | branchlink2
[88124.716676] iwlwifi 0000:00:14.3: 0x00013D26 | interruptlink1
[88124.716677] iwlwifi 0000:00:14.3: 0x00013D26 | interruptlink2
[88124.716678] iwlwifi 0000:00:14.3: 0x0000B860 | data1
[88124.716679] iwlwifi 0000:00:14.3: 0x00000010 | data2
[88124.716680] iwlwifi 0000:00:14.3: 0x00000000 | data3
[88124.716681] iwlwifi 0000:00:14.3: 0xCE0153BE | beacon time
[88124.716682] iwlwifi 0000:00:14.3: 0x5D30FC49 | tsf low
[88124.716683] iwlwifi 0000:00:14.3: 0x000008DB | tsf hi
[88124.716683] iwlwifi 0000:00:14.3: 0x00000000 | time gp1
[88124.716684] iwlwifi 0000:00:14.3: 0xBABFA40A | time gp2
[88124.716685] iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
[88124.716686] iwlwifi 0000:00:14.3: 0x00000049 | uCode version major
[88124.716687] iwlwifi 0000:00:14.3: 0x35C0A2C6 | uCode version minor
[88124.716688] iwlwifi 0000:00:14.3: 0x00000370 | hw version
[88124.716689] iwlwifi 0000:00:14.3: 0x00480002 | board version
[88124.716690] iwlwifi 0000:00:14.3: 0x80D7FC03 | hcmd
[88124.716691] iwlwifi 0000:00:14.3: 0x24020000 | isr0
[88124.716691] iwlwifi 0000:00:14.3: 0x00000000 | isr1
[88124.716692] iwlwifi 0000:00:14.3: 0x48F80002 | isr2
[88124.716693] iwlwifi 0000:00:14.3: 0x00C34C0C | isr3
[88124.716694] iwlwifi 0000:00:14.3: 0x00000000 | isr4
[88124.716695] iwlwifi 0000:00:14.3: 0x0557001C | last cmd Id
[88124.716696] iwlwifi 0000:00:14.3: 0x0000B860 | wait_event
[88124.716696] iwlwifi 0000:00:14.3: 0x00000080 | l2p_control
[88124.716697] iwlwifi 0000:00:14.3: 0x00010034 | l2p_duration
[88124.716698] iwlwifi 0000:00:14.3: 0x0000003F | l2p_mhvalid
[88124.716699] iwlwifi 0000:00:14.3: 0x00001800 | l2p_addr_match
[88124.716700] iwlwifi 0000:00:14.3: 0x00000009 | lmpm_pmg_sel
[88124.716701] iwlwifi 0000:00:14.3: 0x00000000 | timestamp
[88124.716701] iwlwifi 0000:00:14.3: 0x0000E8D8 | flow_handler
[88124.716812] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[88124.716812] iwlwifi 0000:00:14.3: Transport status: 0x0000004A, valid: 7
[88124.716813] iwlwifi 0000:00:14.3: 0x20003463 | ADVANCED_SYSASSERT
[88124.716815] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
[88124.716815] iwlwifi 0000:00:14.3: 0x8045F8F8 | umac branchlink2
[88124.716816] iwlwifi 0000:00:14.3: 0xC00814F8 | umac interruptlink1
[88124.716817] iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink2
[88124.716818] iwlwifi 0000:00:14.3: 0x5D30FC3B | umac data1
[88124.716819] iwlwifi 0000:00:14.3: 0xBABFA3FB | umac data2
[88124.716820] iwlwifi 0000:00:14.3: 0xA34AC3D6 | umac data3
[88124.716821] iwlwifi 0000:00:14.3: 0x00000049 | umac major
[88124.716821] i...

Read more...

Revision history for this message
Kai-Chuan Hsieh (kchsieh) wrote :

If the firmware still crash, please try the latest release from upstream by.

$ sudo apt install git make autoconf dkms
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git
$ cd backport-iwlwifi/
$ git checkout release/core72
$ make
$ sudo make install
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git
$ cd linux-firmware
$ git checkout iwlwifi-fw-2023-03-06
$ sudo cp iwlwifi-so-a0-gf-a0-74.ucode /lib/firmware/
$ sudo cp iwlwifi-so-a0-gf-a0.pnvm /lib/firmware/
$ sudo reboot

Check journalctl -k -b, should see info as attachment

Revision history for this message
David Burke (bufke) wrote :

I attempted this and booted into kernel 5.19.0-32-generic however I then had no wifi at all. The option to connect no longer existed in the top right corner.

Prior to this, it failed in the same way, with Microcode SW error detected, a second time today. It does seems like it happened less often but it's hard to prove that. I switched back to 5.15 for now so as to have a usable computer.

Revision history for this message
Kai-Chuan Hsieh (kchsieh) wrote :

Do you mean you are not able to install new driver firmware by step in #21? Did you disable secure boot? Since the step didn't include module signing, your system can't load it if the secure boot is enabled.

Revision history for this message
David Burke (bufke) wrote :

To the best of my knowledge, I followed the steps you outlined cloning both repos and installing/cp'ing the files. I've double checked the firmware files exist. When I run "update-grub" just to check, I see

Found linux image: /boot/vmlinuz-6.0.0-1012-oem
Found initrd image: /boot/initrd.img-6.0.0-1012-oem
Found linux image: /boot/vmlinuz-5.19.0-35-generic
Found initrd image: /boot/initrd.img-5.19.0-35-generic
Found linux image: /boot/vmlinuz-5.19.0-32-generic
Found initrd image: /boot/initrd.img-5.19.0-32-generic
Found linux image: /boot/vmlinuz-5.15.0-67-generic
Found initrd image: /boot/initrd.img-5.15.0-67-generic

When I boot, I pick 5.19.0-32-generic. That is what I should pick, right? I'm not familiar with how drivers are selected for each kernel nor how exactly the backport-iwlwifi make and make install actually work, but it looked successful.

Before running the commands, it appeared that kernel 5.19.0-32-generic would have the wifi error once a day or so. After I ran the commands and rebooted, I had no internet at all. That also made it difficult for me to look up any commands necessary to provide more information.

I can try other things if that is desired. This is my primary computer and I need to use kernel 5.15 to get work done, so it may take me a day or so to respond. This is the only device that has failed. My Android phone and other family Ubuntu computers do not have a problem with the same wifi router.

I wonder if it only fails when it happens to use the 6Gz frequency? Is it expected to see that when running iw dev wlp0s20f3 info? Does center1: 5775 MHz mean what a lay person would call "5Ghz" and the MHz would be above 6000MHz if it was using "6Gz"? Once the wifi crashes, I don't know what frequency it was recently using. Another perhaps less common thing about the Nest Wifi Pro is that it's a Mesh network with two access points.

Revision history for this message
Kai-Chuan Hsieh (kchsieh) wrote :

Actually, the $ sudo make install for backport-iwlwifi will only be installed into the kernel you build it, it will not install itself to all the kernel version.

To fix your firmware issue we usually try the latest firmware but it needs to update the driver to bump the ABI for loading the new firmware.

If it is okay, would you please try to build it on 5.19.0-35-generic and boot into 5.19.0-35-generic kernel. Of course, please do it when you are available, don't bother to do it immediately since you already have a stable 5.15 kernel for your daily work. The reason that I suggest you to try it is because I can't reproduce it with my Netgear Nighthawk AP.

Thanks for your understanding,

Revision history for this message
David Burke (bufke) wrote :

Thanks, I think I'm now using 5.19.0-35 with the new driver. I'll monitor for crashes. Is there anything in particular I should look for in "journalctl -k -b"?

Revision history for this message
Loic Martel (simarra) wrote :

Hello,
Just to tell I have the same issue, but do not get the technical skills to build kernels.

I attach journactl log if it may help....

Revision history for this message
Kai-Chuan Hsieh (kchsieh) wrote :

Reply #27

Could you try steps in #21 to see if it helps?
Please disable secure boot after reboot.

Thanks,

Revision history for this message
Loic Martel (simarra) wrote :

Reply #28

I am sorry, but this is my daily workstation (I'm Freelancer) and I don't want to take the risk to break it for the next days (lot of work to do! :) )... :/

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in oem-somerville-tentacool-meta (Ubuntu Jammy):
status: New → Confirmed
Revision history for this message
Kai-Chuan Hsieh (kchsieh) wrote :

reply #29

Would you like to try #7 and #8? it doesn't need to compile anything.

Revision history for this message
Timo Aaltonen (tjaalton) wrote : Please test proposed package

Hello David, or anyone else affected,

Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux-firmware/20220329.git681281e4-0ubuntu3.11 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
Loic Martel (simarra) wrote :

I have done an apt update on classical chanel 2 hours ago and it works like a charm now :) (even latencties problems are gone!)

But i have also installed a VPN wich had maybe changed things ion the config... I put log of the install in attachment.

Revision history for this message
Kai-Chuan Hsieh (kchsieh) wrote :

reply #34,

The linux-modules-iwlwifi-generic-hwe-22.04 just provide an alternative intel wifi driver which loads later Intel firmware for your system, I think install any userspace package won't impact it, unless you install new kernel without upgrading the package against the new kernel.

the firmware in #8 is in jammy-proposed now, please keep monitoring to see if you still suffer from the issue you met before.

Thanks,

tags: added: verification-done-jammy
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-firmware - 20220329.git681281e4-0ubuntu3.11

---------------
linux-firmware (20220329.git681281e4-0ubuntu3.11) jammy; urgency=medium

  * Add firmware for amdgpu products with GC 11.01 (LP: #2008113)
    - amdgpu: Add DCN 3.1.4 firmware
    - amdgpu: Add GC 11.0.1 firmware
    - amdgpu: Add SDMA 6.0.1 fimware
    - amdgpu: Add PSP 13.0.4 firmware
    - amdgpu: Add VCN 4.0.2 firmware
    - amdgpu: Update GC 11.0.1 firmware
  * Frequent wakeups on HP Pro x360 435 13.3 inch G9 using Qualcomm FastConnect 6900 (LP: #2006458)
    - WHENCE: ath11k: move regdb.bin before board-2.bin
    - ath11k: WCN6855 hw2.0: update board-2.bin
    - ath11k: WCN6855 hw2.0: update to WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23
  * Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently (LP: #2007875)
    - iwlwifi: add new FWs from core70-87 release
  * mt7921: add support of MTFG table (LP: #2009642)
    - linux-firmware: update firmware for MT7922 WiFi device

 -- Juerg Haefliger <email address hidden> Thu, 16 Mar 2023 11:47:07 +0100

Changed in linux-firmware (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Timo Aaltonen (tjaalton) wrote : Update Released

The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Loic Martel (simarra) wrote :

After an apt update && apt upgrade on stable chanel, and then reboot, the problem is still there...

Revision history for this message
Kai-Chuan Hsieh (kchsieh) wrote (last edit ):

Hello,

From the log, you are not using the fixed firmware which is 73 ucode, Could you check if you have linux-modules-iwlwifi-generic-hwe-22.04 installed?

How to check:
$ apt policy linux-modules-iwlwifi-generic-hwe-22.04
$ apt policy linux-firmware
Check your running kernel
$ uname -r
Please upload the full kernel log by $ journalctl -k -b.

Revision history for this message
Loic Martel (simarra) wrote :

Of course :)

Revision history for this message
Kai-Chuan Hsieh (kchsieh) wrote :

Reply #41

It shows that you didn't install linux-modules-iwlwifi-generic-hwe-22.04. please install it to load the latest firmware which is SRUed by this bug.

Revision history for this message
Loic Martel (simarra) wrote (last edit ):

Reply #42
It seems to be okay for the wifi since some days after the install of linux-modules-iwlwifi-generic-hwe-22.04. :)

Revision history for this message
Loic Martel (simarra) wrote :

Unfortunatly, my problem is still there...
linux-modules-iwlwifi-generic-hwe-22.04 is installed.
System is up to date.

Revision history for this message
Kai-Chuan Hsieh (kchsieh) wrote :

reply #44

Hello,

We've done the firmware update on 22.04, could you try to remove linux-modules-iwlwifi deb and use the in-tree kernel to see if you can still reproduce the issue.

Thanks,

Changed in oem-somerville-tentacool-meta (Ubuntu Jammy):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.