Hi Miguel, On Sunday, 11 February 2024 16:03:20 CET Miguel A. Rojas wrote: > I forgot to include you the dmesg as promised: > > [ 2.235947] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002) > [ 2.237778] iwlwifi 0000:00:14.3: Detected crf-id 0x1300504, cnv-id > 0x80401 wfpm id 0x80000030 > [ 2.237805] iwlwifi 0000:00:14.3: PCI dev 7a70/0074, rev=0x430, > rfid=0x10a100 > [ 2.237845] iwlwifi 0000:00:14.3: firmware: failed to load > iwlwifi-so-a0-hr-b0-83.ucode (-2) > [ 2.237867] iwlwifi 0000:00:14.3: firmware: failed to load > iwlwifi-so-a0-hr-b0-83.ucode (-2) > ... more firmware load failures > [ 2.238098] iwlwifi 0000:00:14.3: Direct firmware load for > iwlwifi-so-a0-hr-b0-73.ucode failed with error -2 > [ 2.241012] iwlwifi 0000:00:14.3: firmware: direct-loading firmware > iwlwifi-so-a0-hr-b0-72.ucode While 'annoying', this is expected behavior. It tries to load the newest (-83) and when it can't find that, it tries an older one and ends up with '-72'. > [ 2.247819] iwlwifi 0000:00:14.3: api flags index 2 larger than > supported by driver > [ 2.247832] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: > 0.0.2.36 > [ 2.248049] iwlwifi 0000:00:14.3: firmware: failed to load > iwl-debug-yoyo.bin (-2) <------------------------------------------------- > [ 2.248067] iwlwifi 0000:00:14.3: firmware: failed to load > iwl-debug-yoyo.bin (-2) <------------------------------------------------- This 'iwl-debug-yoyo.bin' is a familiar one, but this file is NOT available in the upstream linux-firmware repo. It could be it wouldn't be shown if it had already found one of the earlier logged firmware files. I might look into this particular issue at some later date. > [ 2.248078] iwlwifi 0000:00:14.3: loaded firmware version > 72.daa05125.0 so-a0-hr-b0-72.ucode op_mode iwlmvm Bit confused about that version number, but looks like success ... > [ 2.653952] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201 > 160MHz, REV=0x430 > [ 2.769070] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f > [ 2.769102] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f > [ 2.769110] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90 > [ 2.769118] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10 > [ 2.769154] iwlwifi 0000:00:14.3: Detected RF HR B3, rfid=0x10a100 > [ 2.834751] iwlwifi 0000:00:14.3: base HW address: bc:09:1b:d3:e2:ee > [ 2.849492] iwlwifi 0000:00:14.3 wlp0s20f3: renamed from wlan0 > [ 6.570171] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f > [ 6.570263] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f > [ 6.570275] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90 > [ 6.570307] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10 > [ 6.644756] iwlwifi 0000:00:14.3: Registered PHC clock: iwlwifi-PTP, > with index: 0 > [ 6.809353] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x3f > [ 6.809386] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f > [ 6.809397] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90 > [ 6.809408] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10 ... and from this it seems the device appears to be working properly? If that's indeed the case then this bug would essentially be a request for a new upstream version. Cheers, Diederik
Attachment:
signature.asc
Description: This is a digitally signed message part.