Bugzilla – Bug 1219192
On the intel AX200 WiFi there is an issue with 5 GHz (2.4 GHz is fine)
Last modified: 2024-01-30 14:50:47 UTC
There is no way to connect to WiFi at 5 GHz (2.4 GHz is fine), there is a "configuration interface" and that's it. When I boot older - 6.6.11 kernel, everything seems fine.. issues are on newer - 6.7.1 kernel. > lspci | grep Network 04:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) > zypper se -is iwlwifi kernel-default NetworkManager S | Name | Type | Version | Arch | Repository ---+----------------------------------+---------+--------------+--------+------------------ i+ | kernel-default | package | 6.6.11-1.1 | x86_64 | (System Packages) i+ | kernel-default | package | 6.6.10-1.1 | x86_64 | (System Packages) i+ | kernel-default | package | 6.7.1-1.1 | x86_64 | repo-oss i | kernel-default-devel | package | 6.6.11-1.1 | x86_64 | (System Packages) i | kernel-default-devel | package | 6.6.10-1.1 | x86_64 | (System Packages) i | kernel-default-devel | package | 6.7.1-1.1 | x86_64 | repo-oss i | kernel-firmware-iwlwifi | package | 20240115-1.1 | noarch | repo-oss i | libKF5NetworkManagerQt6 | package | 5.114.0-1.1 | x86_64 | repo-oss i+ | NetworkManager | package | 1.44.2-4.2 | x86_64 | repo-oss i | NetworkManager-bluetooth | package | 1.44.2-4.2 | x86_64 | repo-oss i | NetworkManager-branding-openSUSE | package | 42.1-6.1 | noarch | repo-oss i | NetworkManager-dns-dnsmasq | package | 1.0-1.2 | noarch | repo-oss i | NetworkManager-openconnect | package | 1.2.10-2.1 | x86_64 | repo-oss i | NetworkManager-openvpn | package | 1.10.2-3.1 | x86_64 | repo-oss i | NetworkManager-pptp | package | 1.2.12-2.2 | x86_64 | repo-oss i | NetworkManager-tui | package | 1.44.2-4.2 | x86_64 | repo-oss i | NetworkManager-wwan | package | 1.44.2-4.2 | x86_64 | repo-oss >> 2.4GHz connected, then I tried switch to 5GHz. >> When it couldn't do that, it connected to 2.4 again. >> here dmesg about that. [ 2116.959020] wlp4s0: AP is in CSA process, reject auth [ 2132.615435] wlp4s0: AP is in CSA process, reject auth [ 2143.199413] wlp4s0: AP is in CSA process, reject auth [ 2159.041293] wlp4s0: 80 MHz not supported, disabling VHT [ 2159.061350] wlp4s0: authenticate with b0:4e:26:80:7f:03 (local address=b0:7d:64:63:f2:59) [ 2159.062684] wlp4s0: send auth to b0:4e:26:80:7f:03 (try 1/3) [ 2159.094116] wlp4s0: authenticated [ 2159.098723] wlp4s0: associate with b0:4e:26:80:7f:03 (try 1/3) [ 2159.108670] wlp4s0: RX AssocResp from b0:4e:26:80:7f:03 (capab=0x411 status=0 aid=2) [ 2159.176913] wlp4s0: associated [ 4993.544199] wlp4s0: deauthenticating from b0:4e:26:80:7f:03 by local choice (Reason: 3=DEAUTH_LEAVING) [ 4994.135435] wlp4s0: AP is in CSA process, reject auth [ 4997.149938] wlp4s0: AP is in CSA process, reject auth [ 4998.975834] wlp4s0: AP is in CSA process, reject auth [ 5000.552059] wlp4s0: AP is in CSA process, reject auth [ 5010.486930] wlp4s0: AP is in CSA process, reject auth [ 5020.067885] wlp4s0: AP is in CSA process, reject auth [ 5032.642366] wlp4s0: AP is in CSA process, reject auth [ 5045.645518] wlp4s0: AP is in CSA process, reject auth [ 5056.675184] wlp4s0: AP is in CSA process, reject auth [ 5073.646655] wlp4s0: AP is in CSA process, reject auth [ 5084.415274] wlp4s0: AP is in CSA process, reject auth [ 5099.885612] wlp4s0: 80 MHz not supported, disabling VHT [ 5099.908004] wlp4s0: authenticate with b0:4e:26:80:7f:03 (local address=b0:7d:64:63:f2:59) [ 5099.909377] wlp4s0: send auth to b0:4e:26:80:7f:03 (try 1/3) [ 5099.941025] wlp4s0: authenticated [ 5099.946520] wlp4s0: associate with b0:4e:26:80:7f:03 (try 1/3) [ 5099.965937] wlp4s0: RX AssocResp from b0:4e:26:80:7f:03 (capab=0x411 status=0 aid=2) [ 5100.034375] wlp4s0: associated > dmesg | grep iwlwifi [ 7.297412] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002) [ 7.311782] iwlwifi 0000:04:00.0: Detected crf-id 0x3617, cnv-id 0x100530 wfpm id 0x80000000 [ 7.311820] iwlwifi 0000:04:00.0: PCI dev 2723/0084, rev=0x340, rfid=0x10a100 [ 7.346507] iwlwifi 0000:04:00.0: api flags index 2 larger than supported by driver [ 7.346525] iwlwifi 0000:04:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37 [ 7.346760] iwlwifi 0000:04:00.0: loaded firmware version 77.ad46c98b.0 cc-a0-77.ucode op_mode iwlmvm [ 7.528107] iwlwifi 0000:04:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 7.693344] iwlwifi 0000:04:00.0: Detected RF HR B3, rfid=0x10a100 [ 7.769562] iwlwifi 0000:04:00.0: base HW address: b0:7d:64:63:f2:59 [ 7.790114] iwlwifi 0000:04:00.0 wlp4s0: renamed from wlan0 [ 9.613899] iwlwifi 0000:04:00.0: Registered PHC clock: iwlwifi-PTP, with index: 0
*** Bug 1219193 has been marked as a duplicate of this bug. ***
It could be the known regression https://lore.kernel.org/linux-wireless/CAJvGw%2BDQhBk_mHXeu6RTOds5iramMW2FbMB01VbKRA4YbHHDTA@mail.gmail.com/ I'm building a test kernel with the recently posted fix patches. It's being built in OBS home:tiwai:bsc1219192 repo. Once after the build finishes (takes an hour or so), the package will appear at http://download.opensuse.org/repositories/home:/tiwai:/bsc1219192/standard/ Please give it a try later.
(In reply to Takashi Iwai from comment #2) > It could be the known regression > > https://lore.kernel.org/linux-wireless/ > CAJvGw%2BDQhBk_mHXeu6RTOds5iramMW2FbMB01VbKRA4YbHHDTA@mail.gmail.com/ > > I'm building a test kernel with the recently posted fix patches. > It's being built in OBS home:tiwai:bsc1219192 repo. Once after the build > finishes (takes an hour or so), the package will appear at > http://download.opensuse.org/repositories/home:/tiwai:/bsc1219192/standard/ > > Please give it a try later. It has been almost 5 hours since the building process, however the package does not appear at http://download.opensuse.org/repositories/home:/tiwai:/bsc1219192/standard/ or https://build.opensuse.org/project/show/home:tiwai:bsc1219192
Hm, by some reason, the build on OBS didn't start properly. I re-triggered the build again now. Let's cross fingers.
Still nothing there...
There was a typo in the repo name, now available at: http://download.opensuse.org/repositories/home:/tiwai:/bsc121919/standard/
Yes, this kernel fixed 5GHz (at least on my intel AX200) Thank you very much.
I'm pretty sure, this was testing kernel... but I probably should say that my nvidia couldn't load with that kernel. Just in case..
You might need to re-install Nvidia package.
> inxi -G Graphics: Device-1: NVIDIA TU116M [GeForce GTX 1660 Ti Mobile] driver: N/A Device-2: AMD Renoir [Radeon RX Vega 6 ] driver: amdgpu v: kernel Device-3: IMC Networks Integrated Camera driver: uvcvideo type: USB Display: wayland server: X.org v: 1.21.1.11 with: Xwayland v: 23.2.4 compositor: kwin_wayland driver: X: loaded: modesetting unloaded: fbdev,vesa dri: radeonsi gpu: amdgpu resolution: 1920x1080 API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast platforms: gbm,wayland,x11,surfaceless,device API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.3.4 renderer: AMD Radeon Graphics (radeonsi renoir LLVM 17.0.6 DRM 3.56 6.7.2-1.gc8716c9-default) API: Vulkan v: 1.3.275 drivers: N/A surfaces: xcb,xlib,wayland > I mean really N/A...
This is after re-install.
I also confirm that kernel 6.7.2-1.gc8716c9-default fixes the 5G Wifi connection on my Intel Dual Band Wireless-AC 7265.
OK, good to hear that the patches address the WiFi problem. I submitted a PR including this fix, so the fix will be included to stable git branch sooner or later, destined to TW kernel. Possibly together with 6.7.3 update.