Launchpad has imported 44 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=220085.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2025-05-04T12:28:36+00:00 hcording_96 wrote: Created attachment 308081 Hopefully useful outputs from various commands The G605CX Intel BE201 WiFi 7 card is not functional under Linux. I tested this on Fedora 41 and 42, using various Kernels: 6.11, 6.13, 6.14.2, 6.14.4, 6.14.2-rog_cachyos (latest ROG kernel from asus- linux.org). The attached files are for Fedora 41, 6.14.4, linux-firmware 20250410-1.fc41. I understand this might be a vendor specific issue, since Intel has already added the drivers and they are being loaded, as seen in sudo journalctl -k -b | grep wifi: "RFIm is deactivated, reason = 4" and "BIOS contains WGDS but no WRDS". I am happy to provide more information. Thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/0 ------------------------------------------------------------------------ On 2025-05-04T13:09:52+00:00 hcording_96 wrote: Edit: GU605CX, not G605CX Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/1 ------------------------------------------------------------------------ On 2025-05-04T17:51:21+00:00 hcording_96 wrote: I have done additional research and I think the issue relates to the regulatory domain settings enforced by LAR. iw reg get: global country DE: DFS-ETSI ... phy#0 (self-managed) country 00: DFS-UNSET (2412 - 2413 @ 1), (6, 22), (N/A) Furthermore, `iw phy0 channels` shows that all channels are disabled. Since lar_disable doesn't work since Kernel 5.4, I'm unsure how to proceed. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/2 ------------------------------------------------------------------------ On 2025-05-11T19:29:33+00:00 emmanuel.grumbach wrote: Please try to load iwlwifi with debug=0x4001 as a module parameter for iwlwifi. Do you have the .pnvm file installed? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/3 ------------------------------------------------------------------------ On 2025-05-11T19:52:40+00:00 hcording_96 wrote: Created attachment 308112 iwlwifi debug output Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/4 ------------------------------------------------------------------------ On 2025-05-11T19:53:31+00:00 hcording_96 wrote: Hi, thanks for your reply! I've added the module parameter, attached is the new output for journalctl -b | grep iwlwifi after rebooting (see iwlwifi debug output above). I'm not sure what .pnvm files are, but based on the output, some pnvm thing is being loaded. I have these related files in /lib/firmware: /lib/firmware/iwlwifi-bz-b0-fm-c0.pnvm.xz /lib/firmware/iwlwifi-bz-b0-gf-a0.pnvm.xz /lib/firmware/iwlwifi-gl-c0-fm-c0.pnvm.xz /lib/firmware/iwlwifi-ma-b0-gf4-a0.pnvm.xz /lib/firmware/iwlwifi-ma-b0-gf-a0.pnvm.xz /lib/firmware/iwlwifi-so-a0-gf4-a0.pnvm.xz /lib/firmware/iwlwifi-so-a0-gf-a0.pnvm.xz /lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm.xz I think the first one is relevant, since the driver in use is iwlwifi- bz-b0-fm-c0-96.ucode. By the way, I am now on Fedora 42 with Kernel 6.14.5 and linux-firmware 20250410-1.fc42. No changes since updating. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/5 ------------------------------------------------------------------------ On 2025-05-11T20:00:03+00:00 emmanuel.grumbach wrote: So what does iw reg get say now? You can't connect to any access point? Even in 2.4GHz? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/6 ------------------------------------------------------------------------ On 2025-05-11T20:06:26+00:00 hcording_96 wrote: (In reply to Emmanuel Grumbach from comment #6) > So what does iw reg get say now? > > You can't connect to any access point? Even in 2.4GHz? Correct, no APs are found in the search. My router supports 2,4 and 5 GHz. iw reg get global country DE: DFS-ETSI (2400 - 2483 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS (5725 - 5875 @ 80), (N/A, 13), (N/A) (5945 - 6425 @ 320), (N/A, 23), (N/A), NO-OUTDOOR (57000 - 66000 @ 2160), (N/A, 40), (N/A) phy#0 (self-managed) country 00: DFS-UNSET (2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, NO-160MHZ (2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ (2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ (5170 - 5190 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN (5190 - 5210 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN (5210 - 5230 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN (5230 - 5250 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN (5250 - 5270 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN (5270 - 5290 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN (5290 - 5310 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN (5310 - 5330 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN (5490 - 5510 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN (5510 - 5530 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN (5530 - 5550 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN (5550 - 5570 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN (5570 - 5590 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN (5590 - 5610 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN (5610 - 5630 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN (5630 - 5650 @ 240), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN (5650 - 5670 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN (5670 - 5690 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN (5690 - 5710 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN (5710 - 5730 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN (5735 - 5755 @ 160), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN (5755 - 5775 @ 160), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN (5775 - 5795 @ 160), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN (5795 - 5815 @ 160), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN (5815 - 5835 @ 160), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN (5835 - 5855 @ 160), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN (5855 - 5875 @ 160), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN (5875 - 5895 @ 160), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/7 ------------------------------------------------------------------------ On 2025-05-14T11:37:25+00:00 ajgallego wrote: I have the exact same problem with the same hardware, and I'm also experiencing the issue with WiFi. Here are the outputs I'm getting: $ iw reg get global country 00: DFS-UNSET (755 - 928 @ 2), (N/A, 20), (N/A), PASSIVE-SCAN (2402 - 2472 @ 40), (N/A, 20), (N/A) (2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN (5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN (57240 - 63720 @ 2160), (N/A, 0), (N/A) phy#0 (self-managed) country 00: DFS-UNSET (2412 - 2413 @ 1), (6, 22), (N/A) When I run iw phy phy0 channels, it shows a huge list of disabled channels — everything is disabled across all bands (1, 2, and 4). Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/8 ------------------------------------------------------------------------ On 2025-05-16T12:29:48+00:00 emmanuel.grumbach wrote: can you please record tracing for this? Disable wifi then do: sudo trace-cmd record -e mac80211 -e cfg80211 -e iwlwifi -e iwlwifi_dbg then, reproduce the failure to connect, then stop the recording. This will create a trace.dat file that you can compress and send to us (or attach to this bug). Thanks Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/9 ------------------------------------------------------------------------ On 2025-05-16T12:44:32+00:00 ajgallego wrote: Created attachment 308133 trace.dat Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/10 ------------------------------------------------------------------------ On 2025-05-16T12:47:09+00:00 ajgallego wrote: Hi, I've done the trace as requested. You can download the file from the following link: https://bugzilla.kernel.org/attachment.cgi?id=308133 Please let me know if you need anything else. Thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/11 ------------------------------------------------------------------------ On 2025-05-22T06:08:46+00:00 emmanuel.grumbach wrote: Thank for the data. I just noticed that you're all using 6.14 and below. We have a new driver for this device in 6.15. I'd be very interested in knowing if the problem persists there. The easiest is problem to use our backport tree that contains the latest fixes: https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/ Let me know if things work for you using that. Thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/12 ------------------------------------------------------------------------ On 2025-05-22T06:54:39+00:00 hcording_96 wrote: (In reply to Emmanuel Grumbach from comment #12) > Thank for the data. > I just noticed that you're all using 6.14 and below. > We have a new driver for this device in 6.15. > I'd be very interested in knowing if the problem persists there. > > The easiest is problem to use our backport tree that contains the latest > fixes: > https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/ > > Let me know if things work for you using that. > Thanks! Hi, thanks for the update! I compiled the backports and dmesg shows that it's now using iwlwifi-bz-b0-fm-c0-98.ucode, instead of 96: > May 22 08:36:30 nostromo kernel: iwlwifi 0000:00:14.3: iwl_request_firmware > attempting to load firmware 'iwlwifi-bz-b0-fm-c0-101.ucode' > May 22 08:36:30 nostromo kernel: iwlwifi 0000:00:14.3: Direct firmware load > for iwlwifi-bz-b0-fm-c0-101.ucode failed with error -2 > May 22 08:36:30 nostromo kernel: iwlwifi 0000:00:14.3: iwl_request_firmware > attempting to load firmware 'iwlwifi-bz-b0-fm-c0-100.ucode' > May 22 08:36:30 nostromo kernel: iwlwifi 0000:00:14.3: Direct firmware load > for iwlwifi-bz-b0-fm-c0-100.ucode failed with error -2 > May 22 08:36:30 nostromo kernel: iwlwifi 0000:00:14.3: iwl_request_firmware > attempting to load firmware 'iwlwifi-bz-b0-fm-c0-99.ucode' > May 22 08:36:30 nostromo kernel: iwlwifi 0000:00:14.3: Direct firmware load > for iwlwifi-bz-b0-fm-c0-99.ucode failed with error -2 > May 22 08:36:30 nostromo kernel: iwlwifi 0000:00:14.3: iwl_request_firmware > attempting to load firmware 'iwlwifi-bz-b0-fm-c0-98.ucode' > May 22 08:36:30 nostromo kernel: iwlwifi 0000:00:14.3: iwl_req_fw_callback > Loaded firmware file 'iwlwifi-bz-b0-fm-c0-98.ucode' (1925092 bytes). However, I still don't find any networks, and the output of iw reg get and iw phy phy0 channels is still the same (all channels disabled). Perhaps I didn't install the backports correctly? I have this: > modinfo -n iwlwifi > > /lib/modules/6.14.6-300.fc42.x86_64/updates/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko and > modinfo iwlwifi | grep ver > version: iwlwifi-stack-public:master:13805:a65f3e22 > srcversion: 20B598E6BB1C558CD3BECC1 > vermagic: 6.14.6-300.fc42.x86_64 SMP preempt mod_unload Happy to provide more info. Thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/13 ------------------------------------------------------------------------ On 2025-05-23T07:29:28+00:00 ajgallego wrote: The exact same thing happened to me. I also tried updating to the latest mainline kernel, but unfortunately, it only allowed me to go up to 6.14.8. Sadly, that didn’t help at all—in fact, it just caused more things to break and misconfigure, so I didn’t get any improvement from it. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/14 ------------------------------------------------------------------------ On 2025-06-04T17:14:04+00:00 ajgallego wrote: Any update about this? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/15 ------------------------------------------------------------------------ On 2025-06-05T17:54:32+00:00 kolyabodo wrote: To add to this, I am having the same issue on the Zephyrus G16 2025 model, GU605CR. I've tried on Debian, Debian Sid with latest kernel, Fedora, Arch based distros, and in none of them I was able to have any wireless connection available although the Intel BE201 card was being recognized. Hopefully this can be solved, as is affecting everyone on the latest G16 2025 models and no workaround has been found to date. Let us know if any update on the issue, thank you! Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/16 ------------------------------------------------------------------------ On 2025-06-05T21:32:56+00:00 clement wrote: Created attachment 308210 trace from Asus GU605CR with kernel 6.15.0 trace-cmd record -e iwlwifi -e mac80211 -e cfg80211 -e iwlwifi_msg Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/17 ------------------------------------------------------------------------ On 2025-06-05T21:34:28+00:00 clement wrote: Hello, I have attached another trace, from an Zephyrus G16 2025 model, GU605CW. I'm on NixOS, linux_latest (6.15.0). Let me know if I can provide any additional info. Thanks you. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/18 ------------------------------------------------------------------------ On 2025-06-08T09:53:51+00:00 william.bakshi wrote: Hello, I have a very similar issue on my Asus Vivobook S14 S5406SA, with one small difference: on Ubuntu + kernel 6.11.26, which reports loading the FW correctly in dmesg but also "RFIm is deactivated, reason = 4" message, I have it barely functional, not showing an available adapter, but not all PHY channels are disabled and using awkward controls I can get it to scan and to connect to networks. Perhaps the difference is that I'm not getting "BIOS contains WGDS but no WRDS" in dmesg, so there is some (incomplete) functionality. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/22 ------------------------------------------------------------------------ On 2025-06-08T17:23:21+00:00 soumitrashtl9 wrote: Plus one here with the 2025 Zephyrus G16 running Ubuntu 24.04 LTS. The regulatory domain is set to CN and cannot change to US no matter what I try. WiFi chip is detected but does not show visible networks. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/23 ------------------------------------------------------------------------ On 2025-06-09T06:11:52+00:00 william.bakshi wrote: Freshly confirming - mainline kernel 6.15.1 resolves everything and WiFi becomes fully operational(In reply to Emmanuel Grumbach from comment #12) > Thank for the data. > I just noticed that you're all using 6.14 and below. > We have a new driver for this device in 6.15. > I'd be very interested in knowing if the problem persists there. > > The easiest is problem to use our backport tree that contains the latest > fixes: > https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/ > > Let me know if things work for you using that. > Thanks! Update - I've just upgraded the kernel to 6.15.1 (mainline) and WiFi works fully, despite still reporting DFS-UNSET regions. Can be enabled, disabled, networks selected and connected normally. Thanks a lot! Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/24 ------------------------------------------------------------------------ On 2025-06-09T09:59:58+00:00 hcording_96 wrote: (In reply to william.bakshi from comment #21) > Freshly confirming - mainline kernel 6.15.1 resolves everything and WiFi > becomes fully operational(In reply to Emmanuel Grumbach from comment #12) > > Thank for the data. > > I just noticed that you're all using 6.14 and below. > > We have a new driver for this device in 6.15. > > I'd be very interested in knowing if the problem persists there. > > > > The easiest is problem to use our backport tree that contains the latest > > fixes: > > > https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/ > > > > Let me know if things work for you using that. > > Thanks! > > Update - I've just upgraded the kernel to 6.15.1 (mainline) and WiFi works > fully, despite still reporting DFS-UNSET regions. Can be enabled, disabled, > networks selected and connected normally. Thanks a lot! This is only on the Vivobook S14 S5406SA, correct? I just want to avoid confusion since this thread focuses on the Zephyrus G16 GU605C Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/25 ------------------------------------------------------------------------ On 2025-06-09T10:03:25+00:00 nick wrote: > This is only on the Vivobook S14 S5406SA, correct? I just want to avoid > confusion since this thread focuses on the Zephyrus G16 GU605C +1 for this because I am running 6.15.1 on the GU605CR and Wi-Fi is still broken. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/26 ------------------------------------------------------------------------ On 2025-06-09T10:07:41+00:00 william.bakshi wrote: (In reply to hcording_96 from comment #22) > (In reply to william.bakshi from comment #21) > > Freshly confirming - mainline kernel 6.15.1 resolves everything and WiFi > > becomes fully operational(In reply to Emmanuel Grumbach from comment #12) > > > Thank for the data. > > > I just noticed that you're all using 6.14 and below. > > > We have a new driver for this device in 6.15. > > > I'd be very interested in knowing if the problem persists there. > > > > > > The easiest is problem to use our backport tree that contains the latest > > > fixes: > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/ > > > > > > Let me know if things work for you using that. > > > Thanks! > > > > Update - I've just upgraded the kernel to 6.15.1 (mainline) and WiFi works > > fully, despite still reporting DFS-UNSET regions. Can be enabled, disabled, > > networks selected and connected normally. Thanks a lot! > > This is only on the Vivobook S14 S5406SA, correct? I just want to avoid > confusion since this thread focuses on the Zephyrus G16 GU605C Correct. The configuration for which it works is Vivobook S14 S5406SA with Ubuntu. The only spotted difference seemed to be in the lack of "BIOS contains WGDS but no WRDS" message on my side. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/27 ------------------------------------------------------------------------ On 2025-06-09T17:39:42+00:00 clement wrote: Hello, Confirming that upgrading to 6.15.1 did not fix it on a GU605CW. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/28 ------------------------------------------------------------------------ On 2025-06-12T08:27:41+00:00 johannes wrote: We think that all of this is related to FW/PNVM incompatibility - does it go away when you revert all the files as here? https://lore.kernel.org/linux- wireless/dm3ppf63a6024a9415c3a590026c051a7a2a3...@dm3ppf63a6024a9.namprd11.prod.outlook.com/ https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/578 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/29 ------------------------------------------------------------------------ On 2025-06-12T11:50:44+00:00 clement wrote: Hello, I tried building my system with the following commit : https://gitlab.com/kernel-firmware/linux- firmware/-/commit/0d92efb540f49e0aa254f0685b8a71b82608f5c1 It didn't solve the issue. I noticed though that the driver my system load (bz-b0-fm-c0-98) was not affected by the merge request you linked to: [ 4.683094] iwlwifi 0000:00:14.3: loaded firmware version 98.d661c37c.0 bz-b0-fm-c0-98.ucode op_mode iwlmld Did I misunderstand something ? Can I provide additional info ? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/30 ------------------------------------------------------------------------ On 2025-06-13T07:08:11+00:00 xecho wrote: Hi, I'm having the same issue on my 2025 GU605CR, however many of my outputs seem to differ from some other posts here. I physically verified that the chip is the same Intel BE201, but when look for certain key substrings in the kernel output (via sudo dmesg | grep -i <string>), I get no output at all for the following substrings: rfim, wgds, wrds, iwl. I'm not sure if that is concerning, although the Wi-Fi works fine on the Windows 11 installation that came with the system. The Bluetooth is working well on my Linux install. I'm currently running kernel version 6.15.1, although I also tried 6.14.10 and neither versions work. My output for 'iw reg get' also differs, as follows: global country 00: DFS-UNSET (2402 - 2472 @ 40), (6, 20), (N/A) (2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN (5170 - 5250 @ 80), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (5250 - 5330 @ 80), (6, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN (5490 - 5730 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN (5735 - 5835 @ 80), (6, 20), (N/A), PASSIVE-SCAN (57240 - 63720 @ 2160), (N/A, 0), (N/A) This seems to be mostly the same as Javi's output but I don't have the phy#0 section of the output. My output for 'modinfo -n iwlwifi' is: /lib/modules/6.15.1_1/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko.zst and my output for 'modinfo iwlwifi | grep ver' is: filename: /lib/modules/6.15.1_1/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko.zst description: Intel(R) Wireless WiFi driver for Linux vermagic: 6.15.1_1 SMP preempt mod_unload Any help with this would be greatly appreciated; thank you very much in advance for your consideration. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/31 ------------------------------------------------------------------------ On 2025-06-13T08:53:39+00:00 johannes wrote: (In reply to Clément BUCHART from comment #27) > Hello, > > I tried building my system with the following commit : > https://gitlab.com/kernel-firmware/linux-firmware/-/commit/ > 0d92efb540f49e0aa254f0685b8a71b82608f5c1 > > It didn't solve the issue. Hmm, OK. I'll go try to > I noticed though that the driver my system load (bz-b0-fm-c0-98) was not > affected by the merge request you linked to: > [ 4.683094] iwlwifi 0000:00:14.3: loaded firmware version 98.d661c37c.0 > bz-b0-fm-c0-98.ucode op_mode iwlmld > > Did I misunderstand something ? > > Can I provide additional info ? Well, that file wasn't affected, but the PNVM file was affected, and - assuming you installed all the files from the MR - it should have loaded the older PNVM file that (supposed to be) compatible with the FW -98 version, and we were hoping it'd fix the issue. Trying this myself though, I see iwlwifi 0000:00:00.0: 0x20000DE0 | ADVANCED_SYSASSERT when I use the new PNVM file with the older firmware version, so possibly this is something else. So ... I did some more experiments with 6.14.4 now (though on simulated hardware, I didn't have a machine with Bz/Fm I could install 6.14.4 on), and now I'm unsure what you're even reporting, because it _appears_ to mostly work for me? Without the revert I linked to, I do indeed get the DE0 assert, so that would be very very obvious, and results in not even loading the driver to the point of having an interface to scan with. With FW 96 and the matching PNVM, I get Band 1: * 2412 MHz [1] Maximum TX power: 22.0 dBm Channel widths: 20MHz HT40+ ... * 2484 MHz [14] (disabled) Band 2: * 5180 MHz [36] Maximum TX power: 22.0 dBm No IR Channel widths: 20MHz HT40+ VHT80 VHT160 ... * 5905 MHz [181] (disabled) Band 4: * 5955 MHz [1] (disabled) * 5975 MHz [5] (disabled) * 5995 MHz [9] (disabled) ... so all the 6 GHz channels are disabled, some of the 5 GHz channels are disabled, and channels 1-13 on 2.4 GHz are available. "iw reg get" would seem to match what someone pasted above. So now I'm not sure what mean by "all channels are disabled"? Can someone clarify? Or is the bug really "scan doesn't find anything" and you're indeed seeing the same behaviour wrt. channel flags? (FWIW, on the simulation I currently get a simulation crash when trying to scan, so I'm not getting that far, unfortunately.) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/32 ------------------------------------------------------------------------ On 2025-06-13T09:39:02+00:00 clement wrote: Hello, Thanks for your assistance. I kept logs from before building linux-firware from the commit and after and in both case i have "loaded PNVM version 752be616" Regarding the specific problem : at least for me, there is no visible issue, neither in the driver loading process, neither from any command that I know of. The only problem is that any attempt to scan instantly returns with no result. I tried a lot of tools / implementation (wpa_supplicant, network manager, iwd...). I bought a wifi usb dongle to be able to connect to wireless network pending this is resolved. As soon as I power off the intel chipset, i can scan and connect to network without issues (i guess if it's powered on, it takes priority and all scan fails) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/33 ------------------------------------------------------------------------ On 2025-06-13T11:35:05+00:00 johannes wrote: Ouch, sorry to hear you had to resort to that. Looking at the trace, I see the firmware reject it immediately because there are no "valid" channels in the scan command, however, there are many from the driver POV, of course. According to the prior regulatory data received, the channels should be valid though. I'll keep digging, but for now I guess I don't need more info. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/34 ------------------------------------------------------------------------ On 2025-06-13T14:40:19+00:00 andreas wrote: Hi, I'd like to add that on my G605CX I am able to configure a monitor interface using the BE201 card and see traffic sent in my home network. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/35 ------------------------------------------------------------------------ On 2025-06-17T09:25:59+00:00 clement wrote: Hello, Some additional information in case it can help with the diagnostic : I tried to replace the wifi chipset with an AX210NGW I had. I didn't spend much time testing, but i didn't manage to connect. iwctl station wlan0 scan return "Argument type is wrong" The iwlwifi logs ``` clement@medrengard:~/ > sudo dmesg | grep iwlwifi [ 21.487509] iwlwifi 0000:2c:00.0: enabling device (0000 -> 0002) [ 21.525416] iwlwifi 0000:2c:00.0: Detected crf-id 0x400410, cnv-id 0x400410 wfpm id 0x80000000 [ 21.525505] iwlwifi 0000:2c:00.0: PCI dev 2725/0024, rev=0x420, rfid=0x10d000 [ 21.525508] iwlwifi 0000:2c:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz [ 21.530058] iwlwifi 0000:2c:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.42 [ 21.531855] iwlwifi 0000:2c:00.0: loaded firmware version 89.7f71c7f4.0 ty-a0-gf-a0-89.ucode op_mode iwlmvm [ 21.735100] iwlwifi 0000:2c:00.0: BIOS contains WGDS but no WRDS [ 21.905891] iwlwifi 0000:2c:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20 [ 21.905927] iwlwifi 0000:2c:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f [ 21.905936] iwlwifi 0000:2c:00.0: WFPM_AUTH_KEY_0: 0x90 [ 21.905946] iwlwifi 0000:2c:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0 [ 21.906035] iwlwifi 0000:2c:00.0: Detected RF GF, rfid=0x10d000 [ 21.906948] iwlwifi 0000:2c:00.0: loaded PNVM version f8766ebf [ 21.993307] iwlwifi 0000:2c:00.0: base HW address: c4:ff:99:ce:e9:ec [ 23.514483] iwlwifi 0000:2c:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20 [ 23.514531] iwlwifi 0000:2c:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f [ 23.514574] iwlwifi 0000:2c:00.0: WFPM_AUTH_KEY_0: 0x90 [ 23.514583] iwlwifi 0000:2c:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0 [ 23.609244] iwlwifi 0000:2c:00.0: Registered PHC clock: iwlwifi-PTP, with index: 1 ``` I don't know if it because the card isn't whitelisted by the BIOS and i'm not supposed to just change it like that, if this indicates that this was a BIOS issue all along (hope not, since Asus already rejected all my request for support because "linux") or if there is an entirely other problem. Don't hesitate to ignore all this if it's obviously irrelevant. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/37 ------------------------------------------------------------------------ On 2025-06-17T09:27:27+00:00 clement wrote: (I should add there is a diagnostic tool in the BIOS that could scan and connect to my network with the BE201 and fails with the AX210, but again, might be totally irrelevant) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/38 ------------------------------------------------------------------------ On 2025-06-18T13:40:30+00:00 johannes wrote: UEFI is probably unrelated, but how knows :) Could you collect a firmware state image? https://wireless.docs.kernel.org/en/latest/en/users/drivers/iwlwifi/debugging.html#firmware- debugging describes how, though we'll want to have the fw_nmi instead of fw_dbg_collect, I think, to capture the entire memory space of the device. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/39 ------------------------------------------------------------------------ On 2025-06-24T06:34:15+00:00 rahul wrote: Sorry to clutter the thread more. I have a Zenbook Duo 2025 (UX8406CA) AFAICS it has the same BE201 wifi card in question. My Wifi works on 6.14.7 but doesn't 6.15+ (freshly compiled 6.15.3 tested) I tried the commits listed above and they didn't work. I haven't compiled a debug mode kernel but I get a Input/Output error when attempting to modprobe iwlmld. I tried with linux-firmware 061325 (including the commit above) and 20250509, both didn't work. I'm on Linux From Scratch I can get the firmware blob tomorrow. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/40 ------------------------------------------------------------------------ On 2025-06-24T06:43:38+00:00 rahul wrote: > I can get the firmware blob tomorrow. Scratch that my module load isn't even getting far enough to bind the card to iwlwifi Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/41 ------------------------------------------------------------------------ On 2025-06-24T07:48:29+00:00 emmanuel.grumbach wrote: @Rahul, please open a new bug if you have valuable data to share. This bug is on a different issue completely. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/42 ------------------------------------------------------------------------ On 2025-06-24T07:54:06+00:00 rahul wrote: @Emmanuel Okay! I need to collect more data before I do that, building a debug kernel right now. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/43 ------------------------------------------------------------------------ On 2025-06-25T21:49:10+00:00 romgrk.cc wrote: I have the same hardware (Asus GU505CM with BE201) and issue, if @ClémentBuchard can't provide a firmware image I'll build a debug kernel overnight and provide one tomorrow. @Johannes The debugging link above gives an example with mvm rather than mld, is one of those options preferred? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/44 ------------------------------------------------------------------------ On 2025-06-26T07:08:28+00:00 johannes wrote: Sorry, we just haven't updated the docs for mld - you don't get a choice between iwlmvm/iwlmld, so you'll have to adjust for iwlmld instead of iwlmvm. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/45 ------------------------------------------------------------------------ On 2025-06-27T20:49:12+00:00 romgrk.cc wrote: Update: I tried building the `linux-mainline` kernel from the archlinux AUR but couldn't get v6.16-rc2 booting past systemd properly. I tried to build the v6.15-1 kernel (using the `linux-mainline` PKGBUILD set to that version) but couldn't get the `linux-mainline-headers` package to build (some issue with Rust files). I'm running on `linux-mainline` v6.15-1 now but (maybe due to the headers issue?) can't see any output from `iwlwifi` after it's been activated/enabled/re-enabled. I'm also running `linux-firmware-git`, including the PR linked above. The only `dmesg` output I get is: ``` [ 4498.808314] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 4498.808431] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 4498.808496] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600' [ 4498.808532] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 4498.808534] cfg80211: failed to load regulatory.db [ 4498.816920] Intel(R) Wireless WiFi driver for Linux ``` Anyway, this is somewhat unrelated to the issue at hand. I'll try to give it another try in the next days or as soon as v6.16 is released, the kernel build issues prevent me from providing the debug output. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/46 ------------------------------------------------------------------------ On 2025-07-01T06:45:21+00:00 senique wrote: I had try kernel 6.11.0,6.12.3, but can't work. This kernel works: System: Ubuntu 24.04.2 LTS Kernel: Linux 6.14.11-061411-generi Log: iwlwifi ...: enabling device (0000 -> 0002) iwlwifi ...: Detected crf-id 0x2001910, cnv-id 0x80930 wfpm id 0x80005b20 iwlwifi ...: PCI dev 7740/00e4, rev=0x461, rfid=0x20112200 iwlwifi ...: Detected Intel(R) Wi-Fi 7 BE201 320MHz iwlwifi ...: Direct firmware load for iwlwifi-bz-b0-fm-c0-96.ucode failed with error -2 iwlwifi ...: Direct firmware load for iwlwifi-bz-b0-fm-c0-95.ucode failed with error -2 iwlwifi ...: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.4.191 iwlwifi ...: loaded firmware version 94.62990553.0 bz-b0-fm-c0-94.ucode op_mode iwlmvm iwlwifi ...: Detected RF FM, rfid=0x20112200 iwlwifi ...: RFIm is deactivated, reason = 4 iwlwifi ...: loaded PNVM version 35c04ca8 iwlwifi ...: base HW address: 40:c7:3c:cf:43:f6 iwlwifi ... wlp0s20f3: renamed from wlan0 iwlwifi ...: RFIm is deactivated, reason = 4 iwlwifi ...: Registered PHC clock: iwlwifi-PTP, with index: 1 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2113477/comments/47 ** Changed in: linux Status: Unknown => Incomplete ** Changed in: linux Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2113477 Title: Intel BE201 wifi stopped working after linux-firmware 20250606.git3b75d677-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2113477/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
