JhonScript
-
Posts
88 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by JhonScript
-
-
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 2Why can these retries be generated?
-
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
-
3 hours ago, ghost82 said:
Hope it helps in some way..
firmware: direct-loading firmware iwlwifi-cc-a0-63.ucodeThis 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
Quoteok... 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
-
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.confand 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
-
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
-
1 minute ago, SimonF said:
Have you checked rfkill to confirm the wireless card is not disabled?
$ rfkill list all0: hci0: Bluetooth Soft blocked: no Hard blocked: noNOTE: execute this in Kali Linux, because in UNRAID it does not execute the commandI don't know if something about wifi should appear here.
-
51 minutes ago, ghost82 said:
Mira este vídeo:
voz preocupante pero debería ayudar
bluetooth now works great.
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_552bluetooth works fine on kali, and works after reboot. Thank you very much for the video.
I'm still without Wifi, but I have a feeling that this is on the right track.
QuoteIf 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.
I currently have 3 virtual machines
2 windows
1 kalilinuxA while ago I assigned bluetooth and wifi to one of the windows machines and took this screenshot confirming that they work.
I don't understand when they refer to boot issues.
Do I have to make any configuration in the BIOS of the virtual machines?
or in the physical machine BIOS?
Or do you mean if I had two partitions in the "Kali" virtual machine with two operating systems? (This is not the case)
I already did the test of turning on the windows virtual machine with wifi and bluetooth. turn it off, and turn on kali linux
but the wifi is still not working in the kali.
please tell me more about bios settings @ghost82
https://www.gigabyte.com/co/Motherboard/B550-VISION-D-rev-10/support#support-manual
my BIOS is updated to F14
53 minutes ago, SimonF said:Have you installed Bluez?
sudo apt install bluez, Also have you set the Daemon to start if loaded?
I dont use Kali so not sure what is required.
https://www.kali.org/tools/bluez/
Also may want to check rfkill
https://thehacktoday.com/how-to-install-and-use-rfkill-in-kali-linux/
@SimonF I did not have any bluetooth driver installed, nor the services running. With the video that I put @ghost82 , those configurations were made, the bluetooth is working very well.
Again, thank you both very much for helping me. It seems that there is little left to finish configuring this.
-
1
-
-
# modprobe -r btusb # modprobe-r bluetoothpower off the virtual machine and run these commands in UNRAID. which according to what I understand from the other thread, disables the bluetooth drivers in UNRAID.
but the Wifi still does not work in Kali Linux
@SimonF o @ghost82 Does anything else occur to you? or something i did wrong?
How can I confirm bluetooth is working on kali linux?
-
it seems that nothing changed in the kali linux
i will follow this
-
LOL, it seems that I had already done this process to pass the WiFi device, thanks for the patience.
Now I understand th e concept you were referring to. Thanks.
switch PCIe ACI override
but I do not separate the bluetooth
QuoteNOTE: when I checked the VFIO pool and restarted the server, I forgot to unmap the virtual machine's bluetooth. and I had to go through the process of unchecking the pool, rebooting, going back to the virtual machine and unchecking bluetooth. redial the group and reboot again.
All this because when I already had the group marked, it would no longer let me modify the virtual machine to assign the VFIO group.
I could have saved myself all this if I knew how to modify the XML, but I'd rather be sure.
After marking the group the devices disappeared and this appeared
Now I see this in the virtual machine
I'm going to do tests in kali linux
VFIO-PCI Log.txt server-diagnostics-20220212-1000.zip XML_Virtual_Machine without _bluetooth.txt XML_Virtual_Machine with _VFIO.txt
-
I am going to move the USB, but I have no idea how to make the full pass of the USB where the bluetooth is
Quoteattach to vfio at boot the usb controller to which the bluetooth is attached and passthrough in your vm the entire usb controller.
-
I also wanted to share this, I see that the bluetooth is in another USB tree. I don't know if I'm correct.
-
15 minutes ago, ghost82 said:
Because you run it in a non sudo environment, unraid runs as sudo.
I'm sorry I still don't have those basic concepts in linux, Thanks @ghost82
already knowing that, then the output message would be this
$ sudo lspci -vs 03:00.0Already knowing that, then the output message in Kali Linux would be this
03:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) Subsystem: Intel Corporation Wi-Fi 6 AX200NGW Physical Slot: 0-2 Flags: bus master, fast devsel, latency 0, IRQ 22 Memory at 98200000 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [14c] Latency Tolerance Reporting Kernel driver in use: iwlwifi Kernel modules: iwlwifi -
4 minutes ago, ghost82 said:
Not sure I understand correctly...but it's perfectly fine: if you run lspci command in unraid you will see that the host (unraid) binds the pcie device to the vfio-driver and you see the source address at 57:00.0 (bus 57, slot 0, function 0), if you run lspci command in the vm you will see that the guest (your vm) binds the pcie device to the wifi driver and you see the target address at 03:00.0 (bus 3, slot 0, function 0), since you have this in your xml:
<hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x57' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev>
Since you have several usb controllers, I would try to attach the unraid pendrive to another port, belonging to another usb controller (different from that to which the bluetooth is attached), and passthrough to the vm the usb controller to which the bluetooth is attached, instead of passing through the single usb device (bluetooth).
:), really thank you very much. I'm going to start testing by moving the usb.
when I meant that the output was different, it is that in the output message of kali it shows this
Capabilities: <access denied>
and in the output message of the non-assaulted, this appears
Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates -
At the moment I am only interested in solving this problem, I don't know if I am revealing sensitive information by showing this output of my UnRaid
# lspci00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:03.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 07:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43ee 07:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43eb 07:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43e9 08:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea 08:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea 08:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea 09:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) 0a:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) 0a:01.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) 0a:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) 0a:04.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) 0b:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018] (rev 06) 2e:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] (rev 06) 51:00.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port 52:01.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port 52:03.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port 52:05.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port 52:07.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port 55:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) 56:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) 57:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) 58:00.0 VGA compatible controller: NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] (rev a1) 58:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller (rev a1) 58:00.2 USB controller: NVIDIA Corporation TU116 USB 3.1 Host Controller (rev a1) 58:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU116 USB Type-C UCSI Controller (rev a1) 59:00.0 VGA compatible controller: NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] (rev a1) 59:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller (rev a1) 59:00.2 USB controller: NVIDIA Corporation TU116 USB 3.1 Host Controller (rev a1) 59:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU116 USB Type-C UCSI Controller (rev a1) 5a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function 5b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP 5b:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP 5b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller 5b:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller# lspci -vs 57:00.057:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) Subsystem: Intel Corporation Device 0084 Flags: bus master, fast devsel, latency 0, IRQ 38, IOMMU group 21 Memory at eb500000 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel driver in use: vfio-pciI'm curious that the output message is different if I run it in UnRaid
-
I forgot the exit message
$ lspci -vs 03:00.003:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) Subsystem: Intel Corporation Wi-Fi 6 AX200NGW Physical Slot: 0-2 Flags: bus master, fast devsel, latency 0, IRQ 22 Memory at 98200000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: iwlwifi Kernel modules: iwlwifi
this was executed in the virtual machine with S.O Kali-Linux
-
Hello, thank you very much for answering @SimonF.
if the question is what is the version of unraid is 6.9.2
if the question is what is the version of kali, it is that I have tried with these two versions
The screenshots in the post are from "kali-linux-2022-W06-installer-amd64"
I'm going to take a look at the bluetooth post.
I don't know if I need to assign another device to the virtual machine.
-
This is the configuration of my virtual machine
I found another command, I don't know if this can help
$ modinfo iwlwifi -
When you pass the GPU to the virtual machine, literally unraid stops seeing the video card. therefore, it can only be on one machine at a time. it cannot perform both tasks simultaneously.
Note that you can assign the GPU to different virtual machines, but you can only start one virtual machine at a time
-
I forgot to mention that to assign a static IP to the virtual machine you can do it through your router.
Just find the mac of your virtual machine in the virtual machine settings.
Finally make the configuration in your router to assign a static IP through the MAC.
In the worst case, if you don't have access to the router, your router's dhcp shouldn't frequently change assigned internal IPs.
and if that is your case i would just change the wake on lan script or the app config
another option is to make this configuration in the virtual machine... I am assuming that it has OS windows 10
-
use the UNRAID store app "Virtual Machine Wake On Lan", you can find a way to run the wake on lan command from another PC with a shortcut https://www.depicus.com/wake-on-lan/wake -is-lan -cmd.
or some android app.
https://play.google.com/store/apps/details?id=co.uk.mrwebb.wakeonlan&hl=es_CO&gl=US
If you want them to connect remotely you can use Parsec
Here is a much more detailed guide. I really don't know if you require everything that is in the guide.
https://forums.serverbuilds.net/t/guide-remote-gaming-on-unraid/4248
-
Did you pass the gpu to the vm or did you connect via vnc remote?
-
I have a Vision D B550 board, which has a Wi fi 6 ax 200 m2, which is accompanied by bluetooth 5.0
Intel® Wi-Fi 6 AX200
WIFI a, b, g, n, ac with wave 2 features, ax, supporting 2.4/5 GHz Dual-Band
BLUETOOTH 5
Support for 11ax 160MHz wireless standard and up to 2.4 Gbps data rate
* Actual data rate may vary depending on environment and equipment.https://www.gigabyte.com/Motherboard/B550-VISION-D-rev-10/sp#sp
The virtual machine configuration is
Additional in the system devices the following is marked
Wifi
Bluetooth
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
but when i run dmesg command this is the output
$ 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 2I tried to fix this with the following forum, but it doesn't seem to have anything to do with the problem
[ 15.403576] iwlwifi 0000:03:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)https://forums.debian.net/viewtopic.php?t=149817
also try following various tutorials on youtube, to install kernel headers. But it does not work.
$ uname -r 5.15.0-kali3-amd64Already run these commands
$ apt-get update $ apt-get upgrade$ apt update $ apt upgradeAlso run this, but it doesn't work
$ apt-get install --target-release=buster-backports firmware-iwlwifi Reading package lists... Done E: The value 'buster-backports' is invalid for APT::Default-Release as such a release is not available in the sourcesRun this, but package was already installed
$ apt-get install firmware-iwlwifi Reading package lists... Done Building dependency tree... Done Reading state information... Done firmware-iwlwifi is already the newest version (20210818-1+kali2). 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.Wi-Fi networks do not appear
$ iwconfiglo no wireless extensions. eth0 no wireless extensions.$ lspci00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller 00:01.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual graphic card (rev 05) 00:02.0 PCI bridge: Red Hat, Inc. QEMU PCIe Root port 00:02.1 PCI bridge: Red Hat, Inc. QEMU PCIe Root port 00:02.2 PCI bridge: Red Hat, Inc. QEMU PCIe Root port 00:02.3 PCI bridge: Red Hat, Inc. QEMU PCIe Root port 00:07.0 USB controller: Red Hat, Inc. QEMU XHCI Host Controller (rev 01) 00:1f.0 ISA bridge: Intel Corporation 82801IB (ICH9) LPC Interface Controller (rev 02) 00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02) 01:00.0 Ethernet controller: Red Hat, Inc. Virtio network device (rev 01) 02:00.0 Communication controller: Red Hat, Inc. Virtio console (rev 01) 03:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)I don't know what other output message can help me troubleshoot.
-
On 11/17/2021 at 8:50 PM, LSDTripp said:
FIXED - worked for 2 different Servers. intel i7-6950X and amd 5950x
Edit the VM XML (XML VIEW)
STEP 1.
add
<kvm> <hidden state='on'/> </kvm>
before </features>
Step 2.
add
<feature policy='disable' name='hypervisor'/>
before </cpu>
*do not delete or replace, only add*
Example
<features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> <kvm> <hidden state='on'/> </kvm> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='8' threads='2'/> <cache mode='passthrough'/> <feature policy='disable' name='hypervisor'/> </cpu>
Thanks
Does anyone know how to pass through the Wi Fi 6 ax200 network card to a virtual machine with Kali Linux OS?
in VM Engine (KVM)
Posted · Edited by JhonScript
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)