JhonScript Posted February 11, 2022 Share Posted February 11, 2022 (edited) 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 2 I 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-amd64 Already run these commands $ apt-get update $ apt-get upgrade $ apt update $ apt upgrade Also 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 sources Run 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 $ iwconfig lo no wireless extensions. eth0 no wireless extensions. $ lspci 00: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. Edited February 12, 2022 by JhonScript Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 (edited) This is the configuration of my virtual machine XML_Virtual_Machine.txt I found another command, I don't know if this can help $ modinfo iwlwifi modinfo iwlwifi.txt Edited February 12, 2022 by JhonScript Quote Link to comment
SimonF Posted February 12, 2022 Share Posted February 12, 2022 (edited) @JhonScript Which OS version are you running? For the wifi in Kali is it picking up the wifi module run this command but chane to 03:00.0 for you pci device. root@computenode:~# lspci -vs 05:00.0 05:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-V (rev 03) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7d25 Flags: bus master, fast devsel, latency 0, IRQ 18, IOMMU group 16 Memory at 50c00000 (32-bit, non-prefetchable) [size=1M] Memory at 50d00000 (32-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [70] MSI-X: Enable+ Count=5 Masked- Capabilities: [a0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number d8-bb-c1-ff-ff-8c-c9-b0 Capabilities: [1c0] Latency Tolerance Reporting Capabilities: [1f0] Precision Time Measurement Capabilities: [1e0] L1 PM Substates Kernel driver in use: igc Kernel modules: igc If 6.10rcx follow this post for Bluetooth. Edited February 12, 2022 by SimonF Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 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. Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 (edited) I forgot the exit message $ lspci -vs 03:00.0 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: <access denied> Kernel driver in use: iwlwifi Kernel modules: iwlwifi this was executed in the virtual machine with S.O Kali-Linux Edited February 12, 2022 by JhonScript Quote Link to comment
ghost82 Posted February 12, 2022 Share Posted February 12, 2022 (edited) 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. Edited February 12, 2022 by ghost82 Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 (edited) 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 # lspci 00: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.0 57: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-pci I'm curious that the output message is different if I run it in UnRaid Edited February 12, 2022 by JhonScript Quote Link to comment
ghost82 Posted February 12, 2022 Share Posted February 12, 2022 (edited) 11 minutes ago, JhonScript said: I'm curious that the output message is different if I run it in UnRaid 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). Edited February 12, 2022 by ghost82 Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 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 Quote Link to comment
ghost82 Posted February 12, 2022 Share Posted February 12, 2022 (edited) 4 minutes ago, JhonScript said: Capabilities: <access denied> Because you run it in a non sudo environment, unraid runs as sudo. Edited February 12, 2022 by ghost82 Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 (edited) 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.0 Already 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 Edited February 12, 2022 by JhonScript Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 I also wanted to share this, I see that the bluetooth is in another USB tree. I don't know if I'm correct. @ghost82 Quote Link to comment
ghost82 Posted February 12, 2022 Share Posted February 12, 2022 (edited) 8 minutes ago, JhonScript said: I see that the bluetooth is in another USB tree Not so expert, but I cannot find from your screenshot what usb port belongs to which usb controller. From this screenshot: you can clearly see that both 8087:0029 (bluetooth) and the kingston datatraveler (unraid) are connected to the same controller at 07:00.0. If you have a spare usb pendrive attach it to different ports and see to which usb controller it attaches; once you find that it attaches to a different controller, move the unraid pendrive to that port, boot, remove the bluetooth device passthrough, attach to vfio at boot the usb controller to which the bluetooth is attached and passthrough in your vm the entire usb controller. Edited February 12, 2022 by ghost82 Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 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 Quote attach to vfio at boot the usb controller to which the bluetooth is attached and passthrough in your vm the entire usb controller. Quote Link to comment
ghost82 Posted February 12, 2022 Share Posted February 12, 2022 (edited) 8 minutes ago, JhonScript said: but I have no idea how to make the full pass of the USB where the bluetooth is Once you move the unraid pendrive to a different usb controller you can share you diagnostics file to get more help on setting it. However, once you attach that usb controller to vfio (the one to which the bluetooth is attached) you should see it under or above the wifi 6 device, just put a check on it to pass it through (obviously you wont find any usb device in the "USB devices" that are attached to that controller, because all that devices will be automatically be in the vm): By "attaching to vfio at boot" I mean put a check for iommu group 16 (now it's greyed out because it can't be passed through, but it will become available once you move the unraid pendrive to a different controller) Note that you have other devices attached to that controller, so move them too if you need them in the host. Edited February 12, 2022 by ghost82 Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 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 Quote NOTE: 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 Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 it seems that nothing changed in the kali linux i will follow this Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 (edited) # modprobe -r btusb # modprobe-r bluetooth power 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? Edited February 12, 2022 by JhonScript Quote Link to comment
ghost82 Posted February 12, 2022 Share Posted February 12, 2022 (edited) I would say the setup on the host is correct and it's the best possible with the usb controller passthrough. For some reasons iwlwifi is failing to init the card. Are you dual booting unraid with windows? Edited February 12, 2022 by ghost82 Quote Link to comment
SimonF Posted February 12, 2022 Share Posted February 12, 2022 (edited) 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/ Edited February 12, 2022 by SimonF Quote Link to comment
ghost82 Posted February 12, 2022 Share Posted February 12, 2022 17 minutes ago, JhonScript said: How can I confirm bluetooth is working on kali linux? Check this video: worrying voice but should help 1 Quote Link to comment
ghost82 Posted February 12, 2022 Share Posted February 12, 2022 (edited) 22 minutes ago, ghost82 said: Are you dual booting unraid with windows? 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. Edited February 12, 2022 by ghost82 Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 (edited) 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_552 bluetooth 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. Quote 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. @ghost82 I currently have 3 virtual machines 2 windows 1 kalilinux A 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. Edited February 12, 2022 by JhonScript 1 Quote Link to comment
SimonF Posted February 12, 2022 Share Posted February 12, 2022 Have you checked rfkill to confirm the wireless card is not disabled? 1 Quote Link to comment
JhonScript Posted February 12, 2022 Author Share Posted February 12, 2022 1 minute ago, SimonF said: Have you checked rfkill to confirm the wireless card is not disabled? $ 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. 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.