[solved] cfg80211 not loaded & iwlwifi-8265-33.ucode load fails

cfr · 2017-10-13 22:30:47

I am trying to follow the wiki section on 'respecting the regulatory domain' at https://wiki.archlinux.org/index.php/Wi … ory_domain.

I installed crda and rebooted as instructed. I then tried

dmesg | grep cfg80211

which returns nothing. I also checked the journal. Again, nothing.

The only mention of 80211 I can find is

kernel: ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'

The lines immediately following say

kernel: (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
kernel: thermal thermal_zone3: failed to read out thermal zone (-5)

which appears to be a problem, but one to do with temperature sensors rather than wireless, as far as I can tell.

dmesg | grep iw does not say that the domain is being set in firmware, but it does complain that the firmware cannot be loaded in the first place:

[   28.434144] iwlwifi 0000:03:00.0: enabling device (0000 -> 0002)
[   28.437393] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-8265-33.ucode failed with error -2
[   28.437406] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-8265-32.ucode failed with error -2

However, I'm not sure this is the problem as it then says that it loads some firmware OK (though not 'direct'ly?):

[   28.443166] iwlwifi 0000:03:00.0: loaded firmware version 31.532993.0 op_mode iwlmvm
[   28.461370] iwlwifi 0000:03:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230
[   28.519248] iwlwifi 0000:03:00.0: base HW address: XX:XX:XX;XX;XX:XX
[   28.611237] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[   33.314657] iwlwifi 0000:03:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
[   33.314658] iwlwifi 0000:03:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
[15187.474790] iwlwifi 0000:03:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
[15187.474794] iwlwifi 0000:03:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP

I'm not sure what to expect exactly, but the output of iw list | grep -A 15 Frequencies looks more-or-less as I'd expect after setting the regulatory domain for the UK.

                Frequencies:
                        * 2412 MHz [1] (22.0 dBm)
                        * 2417 MHz [2] (22.0 dBm)
                        * 2422 MHz [3] (22.0 dBm)
                        * 2427 MHz [4] (22.0 dBm)
                        * 2432 MHz [5] (22.0 dBm)
                        * 2437 MHz [6] (22.0 dBm)
                        * 2442 MHz [7] (22.0 dBm)
                        * 2447 MHz [8] (22.0 dBm)
                        * 2452 MHz [9] (22.0 dBm)
                        * 2457 MHz [10] (22.0 dBm)
                        * 2462 MHz [11] (22.0 dBm)
                        * 2467 MHz [12] (22.0 dBm)
                        * 2472 MHz [13] (22.0 dBm)
                        * 2484 MHz [14] (disabled)
        Band 2:
--
                Frequencies:
                        * 5180 MHz [36] (22.0 dBm) (no IR)
                        * 5200 MHz [40] (22.0 dBm) (no IR)
                        * 5220 MHz [44] (22.0 dBm) (no IR)
                        * 5240 MHz [48] (22.0 dBm) (no IR)
                        * 5260 MHz [52] (22.0 dBm) (no IR, radar detection)
                        * 5280 MHz [56] (22.0 dBm) (no IR, radar detection)
                        * 5300 MHz [60] (22.0 dBm) (no IR, radar detection)
                        * 5320 MHz [64] (22.0 dBm) (no IR, radar detection)
                        * 5340 MHz [68] (disabled)
                        * 5360 MHz [72] (disabled)
                        * 5380 MHz [76] (disabled)
                        * 5400 MHz [80] (disabled)
                        * 5420 MHz [84] (disabled)
                        * 5440 MHz [88] (disabled)
                        * 5460 MHz [92] (disabled)

In particular, 13 channels are enabled for the first band, which I believe to be correct.

iw reg get gives me a 'global' result and a 'self-managed' one. I'm not sure if this is correct or not, but it doesn't seem entirely unreasonable. Clearly my configuration has done *something*, at least.

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)

phy#0 (self-managed)
country GB: 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 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
        (5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
        (5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
        (5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
        (5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
        (5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
        (5290 - 5310 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
        (5310 - 5330 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
        (5490 - 5510 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
        (5510 - 5530 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
        (5530 - 5550 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
        (5550 - 5570 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
        (5570 - 5590 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
        (5590 - 5610 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
        (5610 - 5630 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
        (5630 - 5650 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, 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 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
        (5755 - 5775 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
        (5775 - 5795 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
        (5795 - 5815 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
        (5815 - 5835 @ 20), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-HT40PLUS, NO-80MHZ, NO-160MHZ, PASSIVE-SCAN

Should the cfg80211 module be loaded, as the wiki says and, if so, how can I ensure that happens?

Last edited by cfr (2017-11-03 00:40:07)

seth · 2017-10-14 07:46:45

Firmware "errors" are normal - it tries until it finds a match.

lsmod | grep cfg80211

The dmesg output is only expected when you want to edit the regdomain (what that article is about) what you do NOT have to do to obey to it (that should™ happen automatically and seems the case for you) but when you want to mess around with it (thus see the instructions for installing crda etc)

giostark · 2017-11-02 18:08:30

I would not say stupid stuffs but I suppose that is missing something other. The wifi work but the bluetooth of this wifi card didnt do the same. I dont understand why it say the firmware loaded is the 33 but then it report loaded the 31.
The firmware is still missing something.

[ios@ios ~]$ modinfo iwlwifi | grep 8265
firmware: iwlwifi-8265-33.ucode
[ios@ios ~]$ dmesg | grep iwl
[ 3.400043] iwlwifi 0000:71:00.0: Direct firmware load for iwlwifi-8265-33.ucode failed with error -2
[ 3.400051] iwlwifi 0000:71:00.0: Direct firmware load for iwlwifi-8265-32.ucode failed with error -2
[ 3.403539] iwlwifi 0000:71:00.0: loaded firmware version 31.532993.0 op_mode iwlmvm
[ 3.443730] iwlwifi 0000:71:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230
[ 3.498559] iwlwifi 0000:71:00.0: base HW address: f8:59:71:42:09:e6
[ 3.589192] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[ 3.589822] iwlwifi 0000:71:00.0 wlp113s0: renamed from wlan0
[ 12.212427] iwlwifi 0000:71:00.0 wlp113s0: disabling HT/VHT due to WEP/TKIP use
[ios@ios ~]$ dmesg | grep cfg80211
[ios@ios ~]$
[ios@ios ~]$ uname -r
4.13.10-1-ARCH
[root@ios ios]# rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tried changing device class in /etc/bluetooth/main.conf as following:
# Default device class. Only the major and minor device class bits are
# considered.
#Class = 0x000100 (from default config)
Class = 0x100100
Nothing changed.

Maybe we just have to wait for a better firmware added in the next kernel.
Here Seth told that is because the 33 is not provided officially by Intel so the first useful is the 31, but? Really?
https://bugs.launchpad.net/ubuntu/+sour … ug/1720891
Any way the problem of crf could not be so easy to solve ...

seth · 2017-11-02 20:13:47

That's not me ;-)
And he doesn't exactly say that either (just that *some* are not officially supported)

Also I'm not sure that cfr actually has a problem? (As pointed out, this module is only require if you want to tamper with the reg domain - what you do not have to do so and may be even illegal) - phy#0 is bound to GB which so far Wales is still a part of (we'll see about 2019 ;-)

cfr · 2017-11-03 00:46:32

Sorry. I forgot to mark this as solved. I was just confused by the wiki and thought I needed crda in order to respect the regulatory domain. I didn't want to use a different one - only to make sure I was using the correct one. That's why I said that the actual output looked plausibly OK, though I wasn't quite sure whether I was supposed to have the 'global' config in the output, as well as the regulatory-domain-specific one.

GB is, indeed, correct, since I am in Wales.

This reminds me that I meant to uninstall crda.

I didn't say anything about bluetooth not working. I haven't actually got around to trying to use it, but certainly bluetooth is recognised, can be enabled etc. just fine.

The failure to remove keys is an issue, though. I see this every time. However, it is not related to this thread, as far as I know. Or to bluetooth, for that matter.

Last edited by cfr (2017-11-03 00:51:08)

giostark · 2017-11-03 08:10:38

Ok sorry Seth and crf , I supposed wrong stuffs. Ill try to check how to make this card work properly . Maybe ill open a new 3d for face my bluetooth problem. Ill stop the OT :-)

Last edited by giostark (2017-11-03 08:11:21)

Arch Linux

#1 2017-10-13 22:30:47

[solved] cfg80211 not loaded & iwlwifi-8265-33.ucode load fails

#2 2017-10-14 07:46:45

Re: [solved] cfg80211 not loaded & iwlwifi-8265-33.ucode load fails

#3 2017-11-02 18:08:30

Re: [solved] cfg80211 not loaded & iwlwifi-8265-33.ucode load fails

#4 2017-11-02 20:13:47

Re: [solved] cfg80211 not loaded & iwlwifi-8265-33.ucode load fails

#5 2017-11-03 00:46:32

Re: [solved] cfg80211 not loaded & iwlwifi-8265-33.ucode load fails

#6 2017-11-03 08:10:38

Re: [solved] cfg80211 not loaded & iwlwifi-8265-33.ucode load fails

Board footer