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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2007875 Title: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently Status in linux-firmware package in Ubuntu: Fix Released Status in oem-somerville-tentacool-meta package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in oem-somerville-tentacool-meta source package in Jammy: New Status in linux-firmware source package in Kinetic: Fix Released Status in oem-somerville-tentacool-meta source package in Kinetic: Invalid Status in linux-firmware source package in Lunar: Fix Released Status in oem-somerville-tentacool-meta source package in Lunar: Invalid 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2007875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
