JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 54 minutes ago, ghost82 said: I'm asking this because booting another os can leave some devices in an undefined state and the driver will be unable to properly initialize the device. I have an example in my build for my wifi usb adapter: I have 3 vms, mac os, windows 11 and kali. If I boot into kali after booting mac os wifi is not detected; I need to boot into windows, then boot into kali to have the wifi detected. Mac os leaves that wifi in an undefined state that the linux driver is unable to reinitialize. On the contrary, windows (with fast boot disabled) leaves the wifi in a state such that the linux driver knows what to do. -- If you are dual booting with windows, check to disable fast boot/fast startup in windows, disable fast boot also in the bios. If it's not disabled it may cause unexpected behaviors as described. look in the manual of the board this configuration and found this https://www.gigabyte.com/co/Motherboard/B550-VISION-D-rev-10/support#support-manual I haven't really moved that, but I'm going to turn off the server and confirm that it really is disabled Quote Link to comment
SimonF Posted February 12, 2022 Share Posted February 12, 2022 2 minutes ago, JhonScript said: $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no NOTE: execute this in Kali Linux, because in UNRAID it does not execute the command I don't know if something about wifi should appear here. Yes was meant to run in VM as the PCI is passed through. Its like the Kali doesnt have the drivers. Quote Link to comment
ghost82 Posted February 12, 2022 Share Posted February 12, 2022 That's really strange Shutdown your pc. Boot to your pc bios (not the vm bios), disable fast boot if it's enabled and apply changes, shutdown. Unplug power chord and wait 2-3 minutes. Boot unraid and run the linux vm, do not start any windows vm before. See if you get wifi. Quote Link to comment
SimonF Posted February 12, 2022 Share Posted February 12, 2022 1 hour ago, JhonScript said: # modprobe -r btusb # modprobe-r bluetooth Also did you blacklist these as will be reloaded if you reboot unraid. 1 Quote Link to comment
ghost82 Posted February 12, 2022 Share Posted February 12, 2022 (edited) 14 minutes ago, SimonF said: Its like the Kali doesnt have the drivers I don't think it's an issue with lacking of drivers, because iwlwifi is loaded and attached to the card. It's an issue with the initialization, something like if the card is an in undefined state that couldn't be initialized by iwlwifi driver. Edited February 12, 2022 by ghost82 1 Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 5 minutes ago, SimonF said: Also did you blacklist these as will be reloaded if you reboot unraid. just run this line, because the path "/boot/config/modprobe.d/" already exists. # echo -e 'blacklist btusb\nblacklist bluetooth' > /boot/config/modprobe.d/bluetooth.conf and when reviewing the file with the "nano" command, it looked like this. 7 minutes ago, ghost82 said: That's really strange Shutdown your pc. Boot to your pc bios (not the vm bios), disable fast boot if it's enabled and apply changes, shutdown. Unplug power chord and wait 2-3 minutes. Boot unraid and run the linux vm, do not start any windows vm before. See if you get wifi. ok... I'm going to do it, I'm already getting scared Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 (edited) 3 hours ago, ghost82 said: Hope it helps in some way.. firmware: direct-loading firmware iwlwifi-cc-a0-63.ucode This means that a0-66, 65 and 64 failed to load but a0-63 is successfully loaded, and you can see in your latest screenshot the iwlwifi driver attached to it. My thought is that since it's a composite device (wifi+bluetooth) you need to passthrough also the bluetooth part: this can be tricky, since the bluetooth is attached to usb. Best option is to passthrough to the vm the wifi+the entire usb controller (not the single device) to which bluetooth is attached; however it seems you attached the bluetooth to the same controller where you have the unraid usb pendrive, so it cannot be passed through... Also follow SimonF link to prevent unraid from using the bluetooth. I am curious that the firmware "0a-63" is loaded, and according to intel, the firmware of the Wi Fi 6 ax 200 card is "0a-46" 23 hours ago, JhonScript said: already inside the virtual machine in the path /lib/firmware, the drivers of the network card are seen according to the intel page https://www.intel.la/content/www/xl/es/support/articles/000005511/wireless.html $ cd /lib/firmware $ ls Quote ok... I'm going to do it, I'm already getting scared I already did the whole procedure but I continue without Wi Fi, bluetooth continues to work Edited February 12, 2022 by JhonScript Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 (edited) 28 minutes ago, ghost82 said: disable fast boot if it's enabled and apply changes, shutdown. I forgot to mention, fast boot was always disabled my photos captured with my Pocophone f1 Edited February 12, 2022 by JhonScript Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 23 hours ago, JhonScript said: $ dmesg | grep iwl [ 15.382319] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-66.ucode (-2) [ 15.382329] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-66.ucode failed with error -2 [ 15.383055] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-65.ucode (-2) [ 15.383059] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-65.ucode failed with error -2 [ 15.383082] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-64.ucode (-2) [ 15.383084] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-64.ucode failed with error -2 [ 15.403082] iwlwifi 0000:03:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-63.ucode [ 15.403103] iwlwifi 0000:03:00.0: api flags index 2 larger than supported by driver [ 15.403121] iwlwifi 0000:03:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37 [ 15.403538] iwlwifi 0000:03:00.0: loaded firmware version 63.c04f3485.0 cc-a0-63.ucode op_mode iwlmvm [ 15.403576] iwlwifi 0000:03:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2) [ 18.983389] iwlwifi 0000:03:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 19.082095] iwlwifi 0000:03:00.0: retry init count 0 [ 19.082122] iwlwifi 0000:03:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 19.179096] iwlwifi 0000:03:00.0: retry init count 1 [ 19.179125] iwlwifi 0000:03:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 19.274692] iwlwifi 0000:03:00.0: retry init count 2 Why can these retries be generated? Quote Link to comment
ghost82 Posted February 12, 2022 Share Posted February 12, 2022 (edited) Not many ideas left.... I see that the newest version of the firmware you have in /lib/firmware/ is a0-63. If I'm not wrong the latest available version should be a0-68. <-- Wrong, they are completely different firmwares, not updates. Maybe the issue is a faulty firmware. Try to clone the linux-firmware repo and copy iwlwifi-cc-a0-68.ucode into /lib/firmware, then try to load it instead of a0-63. <-- Non sense. the firmware is for a different device. Edited February 13, 2022 by ghost82 Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 (edited) 23 minutes ago, ghost82 said: Not many ideas left.... I see that the newest version of the firmware you have in /lib/firmware/ is a0-63. If I'm not wrong the latest available version should be a0-68. Maybe the issue is a faulty firmware, fixed with newer updates. Try to clone the linux-firmware github repo and copy iwlwifi-cc-a0-68.ucode into /lib/firmware, then try to load it instead of a0-63. , I don't know how to clone the repository of iwlwifi-cc-a0-68.ucode, i only found this repo https://github.com/thesofproject/linux-firmware/blob/master/iwlwifi-cc-a0-46.ucode I found this page but I'm not sure how to download the file. in the lower right corner there is a "txt" link, it downloads a file and I can change the extension to ucode. I don't know if that is the correct way. https://chromium.googlesource.com/chromiumos/third_party/linux-firmware/+/master/iwlwifi-cc-a0-68.ucode run this command without the "iwl" filter, and you see more errors, there is one with bluetooth. $ sudo dmesg [ 5.220842] Intel(R) Wireless WiFi driver for Linux [ 5.232576] alg: No test for fips(ansi_cprng) (fips_ansi_cprng) [ 5.236686] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-66.ucode (-2) [ 5.236693] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [ 5.236695] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-66.ucode failed with error -2 [ 5.242185] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-65.ucode (-2) [ 5.242193] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-65.ucode failed with error -2 [ 5.242228] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-64.ucode (-2) [ 5.242229] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-64.ucode failed with error -2 [ 5.264416] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-63.ucode [ 5.264430] iwlwifi 0000:04:00.0: api flags index 2 larger than supported by driver [ 5.264443] iwlwifi 0000:04:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37 [ 5.264760] iwlwifi 0000:04:00.0: loaded firmware version 63.c04f3485.0 cc-a0-63.ucode op_mode iwlmvm [ 5.264797] iwlwifi 0000:04:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2) [ 5.403841] kvm: Nested Virtualization enabled [ 5.403846] SVM: kvm: Nested Paging enabled [ 6.121171] iwlwifi 0000:04:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 6.175294] Bluetooth: Core ver 2.22 [ 6.175328] NET: Registered PF_BLUETOOTH protocol family [ 6.175329] Bluetooth: HCI device and connection manager initialized [ 6.175806] Bluetooth: HCI socket layer initialized [ 6.175810] Bluetooth: L2CAP socket layer initialized [ 6.175814] Bluetooth: SCO socket layer initialized [ 6.209357] usbcore: registered new interface driver btusb [ 6.222749] iwlwifi 0000:04:00.0: retry init count 0 [ 6.222775] iwlwifi 0000:04:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 6.241936] bluetooth hci0: firmware: failed to load intel/ibt-20-0-0.sfi (-2) [ 6.316319] iwlwifi 0000:04:00.0: retry init count 1 [ 6.316345] iwlwifi 0000:04:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 6.407028] iwlwifi 0000:04:00.0: retry init count 2 [ 6.859124] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 6.859128] Bluetooth: BNEP filters: protocol multicast [ 6.859132] Bluetooth: BNEP socket layer initialized [ 6.925160] NET: Registered PF_ALG protocol family [ 9.107940] Bluetooth: RFCOMM TTY layer initialized [ 9.107949] Bluetooth: RFCOMM socket layer initialized [ 9.107957] Bluetooth: RFCOMM ver 1.11 [ 796.123854] TeamViewer_Desk[4345]: segfault at 7f66d4f4c76f ip 00007f66d7bb0188 sp 00007ffed8dea020 error 4 in libgcc_s.so.1[7f66d7ba3000+12000] [ 796.123871] Code: f1 ff ff 48 8b 44 24 08 49 89 84 24 a0 00 00 00 e9 36 fe ff ff 0f 1f 44 00 00 49 8b 94 24 98 00 00 00 49 8b 84 24 90 00 00 00 <80> 3a 48 0f 85 6f ff ff ff 48 b9 c7 c0 0f 00 00 00 0f 05 48 39 4a [ 6.241936] bluetooth hci0: firmware: failed to load intel/ibt-20-0-0.sfi (-2) Edited February 12, 2022 by JhonScript Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 4 minutes ago, JhonScript said: i only found this repo https://github.com/thesofproject/linux-firmware/blob/master/iwlwifi-cc-a0-46.ucode It seems that they have different weight, I will do tests. Quote NOTE: left, downloaded from intel. right, downloaded from github Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 3 minutes ago, JhonScript said: It seems that they have different weight, I will do tests. copy the new file, restart the kali. I don't change anything. Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 1 hour ago, JhonScript said: only this output appears. I don't know if I should do something with this Feb 12 10:50:32 kali bluetoothd[2149]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. Feb 12 10:50:32 kali bluetoothd[2149]: sap-server: Operation not permitted (1) Feb 12 10:50:32 kali bluetoothd[2149]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/sbc Feb 12 10:50:32 kali bluetoothd[2149]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/sbc Feb 12 10:50:32 kali bluetoothd[2149]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/sbc_xq_453 Feb 12 10:50:32 kali bluetoothd[2149]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/sbc_xq_453 Feb 12 10:50:32 kali bluetoothd[2149]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/sbc_xq_512 Feb 12 10:50:32 kali bluetoothd[2149]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/sbc_xq_512 Feb 12 10:50:32 kali bluetoothd[2149]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/sbc_xq_552 Feb 12 10:50:32 kali bluetoothd[2149]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/sbc_xq_552 @ghost82, @SimonF, Do you know if these messages are normal? Quote Link to comment
SimonF Posted February 12, 2022 Share Posted February 12, 2022 39 minutes ago, JhonScript said: @ghost82, @SimonF, Do you know if these messages are normal? Look ok to me, but dont run BT on my systems. Quote Link to comment
ghost82 Posted February 12, 2022 Share Posted February 12, 2022 (edited) Please keep calm JhonScript To avoid issue download the attachment, unzip it and put it in /lib/firmware/ Check dmesg and see if this a0-68 firmware is loaded or not. <-- Nonsense, the firmware is for different devices iwlwifi-cc-a0-68.ucode.zip Edited February 13, 2022 by ghost82 Quote Link to comment
ghost82 Posted February 12, 2022 Share Posted February 12, 2022 (edited) 15 hours ago, JhonScript said: copy the new file, restart the kali. I don't know how this thing works, but from your dmesg: [ 5.236686] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-66.ucode (-2) [ 5.236693] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [ 5.236695] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-66.ucode failed with error -2 [ 5.242185] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-65.ucode (-2) [ 5.242193] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-65.ucode failed with error -2 [ 5.242228] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-64.ucode (-2) [ 5.242229] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-64.ucode failed with error -2 [ 5.264416] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-63.ucode it seems it tries to load higher version numbers , starting from 66, 65, 64: since they are not in the folder it cannot load them, then it searches for 63 and it loads it. If you replace the 46 it doesn't change anything because the same 63 is loaded. Put the 68 in that folder and see if it gets detected, if the same 63 is loaded you can try to delete 66, and rename that 68 to 66 and check if it loads. <-- Nonsense, a0-68 firmware is for different devices Edited February 13, 2022 by ghost82 Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 (edited) 2 hours ago, ghost82 said: if the same 63 is loaded you can try to delete 66, and rename that 68 to 66 and check if it loads. I don't know if you mean that it replaces 63, because 66 doesn't exist. What I did was copy 68 to /lib/firmware folder and restart Kali. but the result was the same. the Kali continued looking for file 66 until file 63. After that i renamed file 68 to 66 and got below output with dmesg command. $ sudo dmesg | grep iwl [ 5.627642] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-66.ucode [ 5.627657] iwlwifi 0000:04:00.0: api flags index 2 larger than supported by driver [ 5.627665] iwlwifi 0000:04:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37 [ 5.627670] iwlwifi 0000:04:00.0: Driver unable to support your firmware API. Driver supports v66, firmware is v68. [ 5.628029] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-65.ucode (-2) [ 5.628033] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-65.ucode failed with error -2 [ 5.628052] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-64.ucode (-2) [ 5.628054] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-64.ucode failed with error -2 [ 5.642753] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-63.ucode [ 5.642786] WARNING: CPU: 2 PID: 45 at drivers/net/wireless/intel/iwlwifi/iwl-drv.c:1145 iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.642800] Modules linked in: drbg(E+) ansi_cprng(E) iwlwifi(E) ecdh_generic(E+) intel_rapl_msr(E) ecc(E) intel_rapl_common(E) iTCO_wdt(E) joydev(E) intel_pmc_bxt(E) pcspkr(E) sg(E) serio_raw(E) cfg80211(E) efi_pstore(E) iTCO_vendor_support(E) watchdog(E) virtio_console(E) rfkill(E) qemu_fw_cfg(E) evdev(E) fuse(E) configfs(E) sunrpc(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) hid_generic(E) usbhid(E) sd_mod(E) t10_pi(E) hid(E) crc_t10dif(E) crct10dif_generic(E) crct10dif_pclmul(E) crct10dif_common(E) crc32_pclmul(E) crc32c_intel(E) ghash_clmulni_intel(E) virtio_net(E) net_failover(E) failover(E) ahci(E) libahci(E) libata(E) aesni_intel(E) crypto_simd(E) qxl(E) drm_ttm_helper(E) cryptd(E) ttm(E) scsi_mod(E) xhci_pci(E) scsi_common(E) psmouse(E) i2c_i801(E) drm_kms_helper(E) i2c_smbus(E) xhci_hcd(E) lpc_ich(E) cec(E) virtio_pci(E) rc_core(E) virtio_pci_modern_dev(E) usbcore(E) virtio(E) usb_common(E) virtio_ring(E) drm(E) [ 5.642862] RIP: 0010:iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.662038] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-62.ucode [ 5.662076] WARNING: CPU: 2 PID: 45 at drivers/net/wireless/intel/iwlwifi/iwl-drv.c:1145 iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.662093] Modules linked in: drbg(E+) ansi_cprng(E) iwlwifi(E) ecdh_generic(E+) intel_rapl_msr(E) ecc(E) intel_rapl_common(E) iTCO_wdt(E) joydev(E) intel_pmc_bxt(E) pcspkr(E) sg(E) serio_raw(E) cfg80211(E) efi_pstore(E) iTCO_vendor_support(E) watchdog(E) virtio_console(E) rfkill(E) qemu_fw_cfg(E) evdev(E) fuse(E) configfs(E) sunrpc(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) hid_generic(E) usbhid(E) sd_mod(E) t10_pi(E) hid(E) crc_t10dif(E) crct10dif_generic(E) crct10dif_pclmul(E) crct10dif_common(E) crc32_pclmul(E) crc32c_intel(E) ghash_clmulni_intel(E) virtio_net(E) net_failover(E) failover(E) ahci(E) libahci(E) libata(E) aesni_intel(E) crypto_simd(E) qxl(E) drm_ttm_helper(E) cryptd(E) ttm(E) scsi_mod(E) xhci_pci(E) scsi_common(E) psmouse(E) i2c_i801(E) drm_kms_helper(E) i2c_smbus(E) xhci_hcd(E) lpc_ich(E) cec(E) virtio_pci(E) rc_core(E) virtio_pci_modern_dev(E) usbcore(E) virtio(E) usb_common(E) virtio_ring(E) drm(E) [ 5.662156] RIP: 0010:iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.662399] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-61.ucode (-2) [ 5.662404] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-61.ucode failed with error -2 [ 5.662429] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-60.ucode (-2) [ 5.662432] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-60.ucode failed with error -2 [ 5.683709] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-59.ucode [ 5.683752] WARNING: CPU: 2 PID: 45 at drivers/net/wireless/intel/iwlwifi/iwl-drv.c:1145 iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.683766] Modules linked in: sha512_generic(E+) drbg(E+) ansi_cprng(E) iwlwifi(E) ecdh_generic(E+) intel_rapl_msr(E) ecc(E) intel_rapl_common(E) iTCO_wdt(E) joydev(E) intel_pmc_bxt(E) pcspkr(E) sg(E) serio_raw(E) cfg80211(E) efi_pstore(E) iTCO_vendor_support(E) watchdog(E) virtio_console(E) rfkill(E) qemu_fw_cfg(E) evdev(E) fuse(E) configfs(E) sunrpc(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) hid_generic(E) usbhid(E) sd_mod(E) t10_pi(E) hid(E) crc_t10dif(E) crct10dif_generic(E) crct10dif_pclmul(E) crct10dif_common(E) crc32_pclmul(E) crc32c_intel(E) ghash_clmulni_intel(E) virtio_net(E) net_failover(E) failover(E) ahci(E) libahci(E) libata(E) aesni_intel(E) crypto_simd(E) qxl(E) drm_ttm_helper(E) cryptd(E) ttm(E) scsi_mod(E) xhci_pci(E) scsi_common(E) psmouse(E) i2c_i801(E) drm_kms_helper(E) i2c_smbus(E) xhci_hcd(E) lpc_ich(E) cec(E) virtio_pci(E) rc_core(E) virtio_pci_modern_dev(E) usbcore(E) virtio(E) usb_common(E) [ 5.683818] RIP: 0010:iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.683936] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-58.ucode (-2) [ 5.683939] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-58.ucode failed with error -2 [ 5.683955] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-57.ucode (-2) [ 5.683957] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-57.ucode failed with error -2 [ 5.684868] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-56.ucode (-2) [ 5.684873] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-56.ucode failed with error -2 [ 5.716313] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-55.ucode [ 5.716355] WARNING: CPU: 2 PID: 45 at drivers/net/wireless/intel/iwlwifi/iwl-drv.c:1145 iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.716372] Modules linked in: sha512_ssse3(E+) sha512_generic(E) drbg(E+) ansi_cprng(E) iwlwifi(E) ecdh_generic(E+) intel_rapl_msr(E) ecc(E) intel_rapl_common(E) iTCO_wdt(E) joydev(E) intel_pmc_bxt(E) pcspkr(E) sg(E) serio_raw(E) cfg80211(E) efi_pstore(E) iTCO_vendor_support(E) watchdog(E) virtio_console(E) rfkill(E) qemu_fw_cfg(E) evdev(E) fuse(E) configfs(E) sunrpc(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) hid_generic(E) usbhid(E) sd_mod(E) t10_pi(E) hid(E) crc_t10dif(E) crct10dif_generic(E) crct10dif_pclmul(E) crct10dif_common(E) crc32_pclmul(E) crc32c_intel(E) ghash_clmulni_intel(E) virtio_net(E) net_failover(E) failover(E) ahci(E) libahci(E) libata(E) aesni_intel(E) crypto_simd(E) qxl(E) drm_ttm_helper(E) cryptd(E) ttm(E) scsi_mod(E) xhci_pci(E) scsi_common(E) psmouse(E) i2c_i801(E) drm_kms_helper(E) i2c_smbus(E) xhci_hcd(E) lpc_ich(E) cec(E) virtio_pci(E) rc_core(E) virtio_pci_modern_dev(E) usbcore(E) virtio(E) [ 5.716432] RIP: 0010:iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.716557] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-54.ucode (-2) [ 5.716561] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-54.ucode failed with error -2 [ 5.736923] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-53.ucode [ 5.736964] WARNING: CPU: 2 PID: 45 at drivers/net/wireless/intel/iwlwifi/iwl-drv.c:1145 iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.736981] Modules linked in: sha512_ssse3(E) sha512_generic(E) drbg(E+) ansi_cprng(E) iwlwifi(E) ecdh_generic(E+) intel_rapl_msr(E) ecc(E) intel_rapl_common(E) iTCO_wdt(E) joydev(E) intel_pmc_bxt(E) pcspkr(E) sg(E) serio_raw(E) cfg80211(E) efi_pstore(E) iTCO_vendor_support(E) watchdog(E) virtio_console(E) rfkill(E) qemu_fw_cfg(E) evdev(E) fuse(E) configfs(E) sunrpc(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) hid_generic(E) usbhid(E) sd_mod(E) t10_pi(E) hid(E) crc_t10dif(E) crct10dif_generic(E) crct10dif_pclmul(E) crct10dif_common(E) crc32_pclmul(E) crc32c_intel(E) ghash_clmulni_intel(E) virtio_net(E) net_failover(E) failover(E) ahci(E) libahci(E) libata(E) aesni_intel(E) crypto_simd(E) qxl(E) drm_ttm_helper(E) cryptd(E) ttm(E) scsi_mod(E) xhci_pci(E) scsi_common(E) psmouse(E) i2c_i801(E) drm_kms_helper(E) i2c_smbus(E) xhci_hcd(E) lpc_ich(E) cec(E) virtio_pci(E) rc_core(E) virtio_pci_modern_dev(E) usbcore(E) virtio(E) [ 5.737041] RIP: 0010:iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.737166] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-52.ucode (-2) [ 5.737169] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-52.ucode failed with error -2 [ 5.737186] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-51.ucode (-2) [ 5.737187] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-51.ucode failed with error -2 [ 5.762891] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-50.ucode [ 5.762933] WARNING: CPU: 2 PID: 45 at drivers/net/wireless/intel/iwlwifi/iwl-drv.c:1145 iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.762949] Modules linked in: jitterentropy_rng(E+) sha512_ssse3(E) sha512_generic(E) drbg(E) ansi_cprng(E) iwlwifi(E) ecdh_generic(E+) intel_rapl_msr(E) ecc(E) intel_rapl_common(E) iTCO_wdt(E) joydev(E) intel_pmc_bxt(E) pcspkr(E) sg(E) serio_raw(E) cfg80211(E) efi_pstore(E) iTCO_vendor_support(E) watchdog(E) virtio_console(E) rfkill(E) qemu_fw_cfg(E) evdev(E) fuse(E) configfs(E) sunrpc(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) hid_generic(E) usbhid(E) sd_mod(E) t10_pi(E) hid(E) crc_t10dif(E) crct10dif_generic(E) crct10dif_pclmul(E) crct10dif_common(E) crc32_pclmul(E) crc32c_intel(E) ghash_clmulni_intel(E) virtio_net(E) net_failover(E) failover(E) ahci(E) libahci(E) libata(E) aesni_intel(E) crypto_simd(E) qxl(E) drm_ttm_helper(E) cryptd(E) ttm(E) scsi_mod(E) xhci_pci(E) scsi_common(E) psmouse(E) i2c_i801(E) drm_kms_helper(E) i2c_smbus(E) xhci_hcd(E) lpc_ich(E) cec(E) virtio_pci(E) rc_core(E) virtio_pci_modern_dev(E) [ 5.763018] RIP: 0010:iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.763141] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-49.ucode (-2) [ 5.763144] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-49.ucode failed with error -2 [ 5.786945] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-48.ucode [ 5.786984] WARNING: CPU: 2 PID: 45 at drivers/net/wireless/intel/iwlwifi/iwl-drv.c:1145 iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.787000] Modules linked in: jitterentropy_rng(E) sha512_ssse3(E) sha512_generic(E) drbg(E) ansi_cprng(E) iwlwifi(E) ecdh_generic(E) intel_rapl_msr(E) ecc(E) intel_rapl_common(E) iTCO_wdt(E) joydev(E) intel_pmc_bxt(E) pcspkr(E) sg(E) serio_raw(E) cfg80211(E) efi_pstore(E) iTCO_vendor_support(E) watchdog(E) virtio_console(E) rfkill(E) qemu_fw_cfg(E) evdev(E) fuse(E) configfs(E) sunrpc(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) hid_generic(E) usbhid(E) sd_mod(E) t10_pi(E) hid(E) crc_t10dif(E) crct10dif_generic(E) crct10dif_pclmul(E) crct10dif_common(E) crc32_pclmul(E) crc32c_intel(E) ghash_clmulni_intel(E) virtio_net(E) net_failover(E) failover(E) ahci(E) libahci(E) libata(E) aesni_intel(E) crypto_simd(E) qxl(E) drm_ttm_helper(E) cryptd(E) ttm(E) scsi_mod(E) xhci_pci(E) scsi_common(E) psmouse(E) i2c_i801(E) drm_kms_helper(E) i2c_smbus(E) xhci_hcd(E) lpc_ich(E) cec(E) virtio_pci(E) rc_core(E) virtio_pci_modern_dev(E) [ 5.787062] RIP: 0010:iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.787178] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-47.ucode (-2) [ 5.787181] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-47.ucode failed with error -2 [ 5.807576] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-46.ucode [ 5.807609] WARNING: CPU: 2 PID: 45 at drivers/net/wireless/intel/iwlwifi/iwl-drv.c:1145 iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.807624] Modules linked in: fat(E) jitterentropy_rng(E) sha512_ssse3(E) sha512_generic(E) drbg(E) ansi_cprng(E) iwlwifi(E) ecdh_generic(E) intel_rapl_msr(E) ecc(E) intel_rapl_common(E) iTCO_wdt(E) joydev(E) intel_pmc_bxt(E) pcspkr(E) sg(E) serio_raw(E) cfg80211(E) efi_pstore(E) iTCO_vendor_support(E) watchdog(E) virtio_console(E) rfkill(E) qemu_fw_cfg(E) evdev(E) fuse(E) configfs(E) sunrpc(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) hid_generic(E) usbhid(E) sd_mod(E) t10_pi(E) hid(E) crc_t10dif(E) crct10dif_generic(E) crct10dif_pclmul(E) crct10dif_common(E) crc32_pclmul(E) crc32c_intel(E) ghash_clmulni_intel(E) virtio_net(E) net_failover(E) failover(E) ahci(E) libahci(E) libata(E) aesni_intel(E) crypto_simd(E) qxl(E) drm_ttm_helper(E) cryptd(E) ttm(E) scsi_mod(E) xhci_pci(E) scsi_common(E) psmouse(E) i2c_i801(E) drm_kms_helper(E) i2c_smbus(E) xhci_hcd(E) lpc_ich(E) cec(E) virtio_pci(E) rc_core(E) virtio_pci_modern_dev(E) [ 5.807673] RIP: 0010:iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.807774] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-45.ucode (-2) [ 5.807777] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-45.ucode failed with error -2 [ 5.807792] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-44.ucode (-2) [ 5.807793] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-44.ucode failed with error -2 [ 5.807808] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-43.ucode (-2) [ 5.807809] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-43.ucode failed with error -2 [ 5.807822] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-42.ucode (-2) [ 5.807845] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-42.ucode failed with error -2 [ 5.807860] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-41.ucode (-2) [ 5.807861] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-41.ucode failed with error -2 [ 5.807876] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-40.ucode (-2) [ 5.807877] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-40.ucode failed with error -2 [ 5.807889] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-39.ucode (-2) [ 5.807891] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-39.ucode failed with error -2 [ 5.807892] iwlwifi 0000:04:00.0: minimum version required: iwlwifi-cc-a0-39 [ 5.807894] iwlwifi 0000:04:00.0: maximum version supported: iwlwifi-cc-a0-66 [ 5.807895] iwlwifi 0000:04:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git I don't know if I should delete file 63 I'm thinking of creating a bootable USB with Kali Linux. to test without the S.O UnRaid and rule out that it really is an error when passing the wifi card. Edited February 12, 2022 by JhonScript Quote Link to comment
ghost82 Posted February 12, 2022 Share Posted February 12, 2022 In real I think it's not an issue with the passthrough, but with the driver. Tomorrow I will have a better look at that log and think something. Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 (edited) 3 minutes ago, ghost82 said: In real I think it's not an issue with the passthrough, but with the driver. Tomorrow I will have a better look at that log and think something. Thanks @ghost82. @ghost82, Can you do me the favor of passing me the 66 file to do the test? I'm curious that it starts searching from file 66 and not from file 68. maybe the error is that firmware 66 is not really loaded. Edited February 12, 2022 by JhonScript Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 (edited) Rename file 46 to 66 and copy file "66" to /lib/firmware folder, run dmesg command and get this output [ 5.491948] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-66.ucode [ 5.491968] iwlwifi 0000:04:00.0: Found debug destination: EXTERNAL_DRAM [ 5.491969] iwlwifi 0000:04:00.0: Found debug configuration: 0 [ 5.492245] iwlwifi 0000:04:00.0: loaded firmware version 46.177b3e46.0 cc-a0-66.ucode op_mode iwlmvm [ 5.651527] iwlwifi 0000:04:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 5.749474] iwlwifi 0000:04:00.0: retry init count 0 [ 5.749507] iwlwifi 0000:04:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 5.849701] iwlwifi 0000:04:00.0: retry init count 1 [ 5.849728] iwlwifi 0000:04:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 5.936719] iwlwifi 0000:04:00.0: retry init count 2 After loading the driver it keeps trying to detect the wifi card. Edited February 12, 2022 by JhonScript Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 (edited) after doing this. 40 minutes ago, JhonScript said: Rename file 46 to 66 and copy file "66" to /lib/firmware folder, run dmesg command and get this output i did this again, step by step 5 hours ago, ghost82 said: That's really strange Shutdown your pc. Boot to your pc bios (not the vm bios), disable fast boot if it's enabled and apply changes, shutdown. Unplug power chord and wait 2-3 minutes. Boot unraid and run the linux vm, do not start any windows vm before. See if you get wifi. The image is edited, it is working correctly. $ rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth hci0 unblocked unblocked 1 wlan phy0 unblocked unblocked $ iwconfig lo no wireless extensions. eth0 no wireless extensions. wlan0 IEEE 802.11 ESSID:"EXAMPLE" Mode:Managed Frequency:2.437 GHz Access Point: FF:FF:FF:00:00:00 Bit Rate=26 Mb/s Tx-Power=22 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=70/70 Signal level=-24 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:7 Missed beacon:0 sudo dmesg | grep iwl [ 3.970022] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-66.ucode [ 3.970035] iwlwifi 0000:04:00.0: Found debug destination: EXTERNAL_DRAM [ 3.970036] iwlwifi 0000:04:00.0: Found debug configuration: 0 [ 3.970174] iwlwifi 0000:04:00.0: loaded firmware version 46.177b3e46.0 cc-a0-66.ucode op_mode iwlmvm [ 5.769813] iwlwifi 0000:04:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 5.781915] iwlwifi 0000:04:00.0: Applying debug destination EXTERNAL_DRAM [ 5.782199] iwlwifi 0000:04:00.0: Allocated 0x00400000 bytes for firmware monitor. [ 5.871900] iwlwifi 0000:04:00.0: Detected RF HR B3, rfid=0x10a100 [ 5.931647] iwlwifi 0000:04:00.0: base HW address: 8c:c6:81:ef:ba:a5 [ 7.062842] iwlwifi 0000:04:00.0: Applying debug destination EXTERNAL_DRAM [ 7.206552] iwlwifi 0000:04:00.0: FW already configured (0) - re-configuring [ 7.239315] iwlwifi 0000:04:00.0: Applying debug destination EXTERNAL_DRAM [ 7.384031] iwlwifi 0000:04:00.0: FW already configured (0) - re-configuring I don't understand why this happens. There must be a way to force it to look for file 46 directly and not have to do this. but well it works and I'm happy. I thank you very much for the time you spent @ghost82, @SimonF. I hope if someone has come across this. at least this solution will work. Edited February 12, 2022 by JhonScript 2 Quote Link to comment
ghost82 Posted February 13, 2022 Share Posted February 13, 2022 (edited) Nice that you got it working. Linux is not bug free, without debugging the issue in details it's not possible to know what happened, maybe the driver, maybe the kernel, maybe the firmware, who knows..sometimes "old" is better then "new". 15 hours ago, JhonScript said: I don't understand why this happens. There must be a way to force it to look for file 46 directly and not have to do this Reading more about this, firmware named a0-xx are not the same firmware for the same device(s), that's why you got an error when you renamed a0-68 to a0-66 and try to force load it: ax200 should load the a0-46; it's iwlwifi driver that should look for the a0-46 firmware, but it is looking for other firmwares, in my opinion the issue is with iwlwifi driver, not with the firmware, or with the kernel which is misdetecting the wifi card and tells to iwlwifi to load a wrong firmware. In particular this current kernel is looking for firmware a0-66 going down till a0-39: [ 5.807892] iwlwifi 0000:04:00.0: minimum version required: iwlwifi-cc-a0-39 [ 5.807894] iwlwifi 0000:04:00.0: maximum version supported: iwlwifi-cc-a0-66 For the kernel that wifi card can be used with that range of firmwares. If you delete all iwlwifi-cc-a0-XX.ucode in your /lib/firmware/ and put only iwlwifi-cc-a0-46.ucode (without renaming it), the kernel should start looking for a0-66 going down till it finds a file in the range a0-66 --> a0-39. And I'm quite sure it will load the correct a0-46, because it's in the range of allowed firmwares and it's the only one available in /lib/firmware/. If I were you, I would go this way, delete all, and put only a0-46. If you stick with the "firmware renamed solution", remember that if you update the linux-firmware package (if you have it installed), your renamed firmware could be overwritten (replaced with the real a0-66) and your wifi won't work again, if it will be the case, just repeat the steps you did. Devices like this have the firmware loaded in the device ram during boot, if a wrong firmware is wrongly loaded you may need to power cycle it to be able to load another firmware on it. Edited February 13, 2022 by ghost82 Quote Link to comment
JhonScript Posted February 13, 2022 Author Share Posted February 13, 2022 7 hours ago, ghost82 said: Devices like this have the firmware loaded in the device ram during boot, if a wrong firmware is wrongly loaded you may need to power cycle it to be able to load another firmware on it. this makes sense, regarding the procedure of turning off and disconnecting the power supply from power. 7 hours ago, ghost82 said: If you stick with the "firmware renamed solution", remember that if you update the linux-firmware package (if you have it installed), your renamed firmware could be overwritten (replaced with the real a0-66) and your wifi won't work again, if it will be the case, just repeat the steps you did. Got it, I'm going to work on that solution today. I will also confirm that the VFIO process is completely necessary. Thank you very much for everything, really. Quote Link to comment
Solution JhonScript Posted February 14, 2022 Author Solution Share Posted February 14, 2022 (edited) I tell you that during the day I did the following: PCIe ACS override: Multi-function I removed bluetooth.conf file from path /boot/config/modprobe.d/ I created a new virtual machine with O.O Kali Linux and just passed the WiFi device which was marked for VFIO on boot Quote NOTE: With the creation of a new machine we would discard all the configurations that were made within the virtual machine Everything works within Kali. The image is edited Quote The screenshots show that the bluetooth (Intel Corp. (8087:0029)) is not found, but I already verified that I can associate it to the virtual machine without having to associate the entire IOMMU group or another different device $ sudo iwconfig lo no wireless extensions. eth0 no wireless extensions. wlan0 IEEE 802.11 ESSID:"MyESSID" Mode:Managed Frequency:2.437 GHz Access Point: FF:FF:FF:00:00:00 Bit Rate=52 Mb/s Tx-Power=22 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on Link Quality=70/70 Signal level=-20 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:7 Missed beacon:0 $ rfkill ID TYPE DEVICE SOFT HARD 0 wlan phy0 unblocked unblocked $ sudo dmesg | grep iwl [ 8.558540] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-64.ucode (-2) [ 8.558554] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-64.ucode failed with error -2 [ 8.561580] iwlwifi 0000:03:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-63.ucode [ 8.561598] iwlwifi 0000:03:00.0: api flags index 2 larger than supported by driver [ 8.561614] iwlwifi 0000:03:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37 [ 8.561936] iwlwifi 0000:03:00.0: loaded firmware version 63.c04f3485.0 cc-a0-63.ucode op_mode iwlmvm [ 8.561970] iwlwifi 0000:03:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2) [ 8.691723] iwlwifi 0000:03:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 8.826471] iwlwifi 0000:03:00.0: Detected RF HR B3, rfid=0x10a100 [ 8.894397] iwlwifi 0000:03:00.0: base HW address: 00:00:00:FF:FF:FF Quote With the dmesg output message, in this installation you can see that part of the firmware 64. It should be noted that this installation is with the ISO "kali-linux-2021.4a-installer-amd64.iso", the iso of the previous tests was "kali-linux-2022-W06-installer-amd64.iso" $ cd /lib/firmware/ $ ls Quote NOTE: In this installation I did not copy any file, and it is observed that there is firmware from 46 (this is the firmware of the WiFi 6 ax200 card) to firmware 63, which is the one that is shown loaded in the output messages of the "dmesg" command. So far the solution seems to have been: 1. Changed USB port to UNRAID OS Bootable USB 2. have gone through the process of shutting down the physical machine and disconnecting it from power for 2-3 minutes 3. have booted the physical machine and run the Kali Linux virtual machine without running any other virtual machines that make use of the WiFi device I'm guessing you also need to have Fastboot disabled in the BIOS of the physical machine. (In my case it was always disabled) In the next few days I will rule out the need to move the UNRAID OS boot usb to another USB port. I don't know if I missed something we did. but I think that would be the summary until I drop point number 1, God willing . Edited February 14, 2022 by JhonScript Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.