derpuma
-
Posts
97 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by derpuma
-
-
Thx for your reply!
AX210,AX211, etc. eg. Cards working very well in Sonoma, regarding to this github:
https://github.com/perez987/Intel-AX210-wifi6-on-macOS-Sonoma
This is my card.
Wifi is running with the kext linked on github above. So I guess that there is no Issue with passthrough of the card.The only part not working is Bluetooth. I am not sure what is wrong in my setup. I tried all possible kext kombinations, others reported as working.
So far no luck here on Sonoma.
I am currently on 14.3.1, I updated to 14.4Beta, to see if this fixes the problem, but now my macOS does not boot up anymore.
Have to go back to my 14.3.1 backup. Not sure why 14.4Beta is not booting after the update.
-
03:00.0 8086 2725 8086 0024 Disabl Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz Network controller Network controller /pci8086,2725@0 pci8086,2725 PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)Looking for a Wi-Fi solution that does not require disabled SIP (e.g. Intel AX210), I found this on Github.
I bought a Wi-Fi 6 AX210/AX211/AX411 160MHz card from Amazon, and pass through the card into Sonoma:
<hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </source> <alias name='hostdev6'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </hostdev>
Then I prepared my OpenCore bootloader with all the necessary kext and config.plist settings.
Boting in Sonoma, the Wifi Cardworks just fine:
Unfortunately Bluetooth does not work and I am not able to pair any device. I double checked the kext, but as far as I see, I don't miss anything.
Anyone else out there who tried Intel Wifi/BT on Sonoma and had also success with Bluetooth?I used this three kext in EFI/OC/Kext:
IntelBTPatcher.kext V2.4.0
IntelBluetoothFirmware.kext V2.4.0
BlueToolFixup.kext V2.6.9And I deleted:
BrcmBluetoothInjector.kext form EFI/OC/Kext.
This should be basically enough to get Bluetooth up and running, but here it dont.
Any Idea? What am I missing out?I guess the passthrough has no errors, as my Windows 10 runs flawless (wifi and Bluetooth) with the same XML code I posted above.
Help would be nice!
-
Is there a way, to bring a script to the UNRAID top menu bar? Let's say a menu item witch by pressing runs a user script for a VM cycle?
-
24 minutes ago, wgstarks said:
There is currently a bug in samba.
https://bugzilla.samba.org/show_bug.cgi?id=15143
veto files isn’t working until this bug is fixed.
Thanks for the hint. So I guess hide files isn'T working too.
This might be also the reason for my Samba syslog errors...
Oct 12 13:09:49 Tower smbd[11653]: =============================================================== Oct 12 13:09:49 Tower smbd[11653]: [2022/10/12 13:09:49.358392, 0] ../../lib/util/fault.c:174(smb_panic_log) Oct 12 13:09:49 Tower smbd[11653]: INTERNAL ERROR: smbd_scavenger_parent_dead in pid 11653 (4.17.0) Oct 12 13:09:49 Tower smbd[11653]: [2022/10/12 13:09:49.358403, 0] ../../lib/util/fault.c:178(smb_panic_log) Oct 12 13:09:49 Tower smbd[11653]: If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting Oct 12 13:09:49 Tower smbd[11653]: [2022/10/12 13:09:49.358411, 0] ../../lib/util/fault.c:183(smb_panic_log) Oct 12 13:09:49 Tower smbd[11653]: =============================================================== -
Adding
veto files = /._*/.DS_Store/._.DS_Store/
hide files = /._*/.DS_Store/._.DS_Store/
delete veto files = yes
to my smb-extra.conf does not give me the desired result.
I still see the files I want to hide on my array and unassigned devices.
Even after array restart and server reboot.
Any ideas why?
My smb-extra.conf looks like that:
#unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end veto files = /._*/.DS_Store/._.DS_Store/ hide files = /._*/.DS_Store/._.DS_Store/ delete veto files = yes [rootshare] path = /mnt/user comment = browseable = yes valid users = admin write list = admin vfs objects = -
18 minutes ago, Squid said:
I think both you and the OP meant to say "Disabled" which makes everything faster
Yes I did, sorry for the missundertanding. Of course I meant mitigations="off"...
-
I used the mitigations plugin in 6.9.2 without any problems regarding to my macOS VMs.
After upgrading to 6.11/6.11.1 I had boot problems into my macOS VMs (several random opencore kernel panics, syslog shows amdgpu errors) and I am not able to boot into the macOS VMs. Windows works fine.
I have a verdict, causing the problem. I suspect the boot problems could be related to the mitigations plugin, as it looks like the problem only accures at the time mitigations are enabled.
I can reproduce the error, every time I rebuild my flash to 6.9.2 from backup with mitigations enabled, everthing works fine. Updating 6.9.2 to 6.11 or 6.11.1, the mitigations are still enabled and I am not able to boot into the macOS VMs.
Any advice from your side, what I could check to see if there is defenitly any relation?
I like the mitigations enabled, as my macOS is round about 20-25% faster with them turned on. -
My Catalina and Monterey Vms are running fine under 6.9.2.
After the update to 6.11 the do not boot up. Monterey hangs in a endless bootloop.
Any ideas? As far as I can see IOMMU Groups are exactly the same in 6.9.2 and 6.11.
-
I disabled bonding and did a few boot ups.
But it still takes some time till network is up and running. Maybe a little bit faster like with bonding activated.
Maybe this is just the way it is whithout a dedicated NIC for my VM and I have to live with that.
What bothered me, was the fact, that network sometimes is there immediatly and sometimes not.
-
I have a problem, that my VMs (either MacOS, Windows or Linux have a problem with network being present right after boot into OS, in probably 3 to 4 times out of 10. Usually I have full network access (internet and local network to NAS and other computers) right after booting into OS. But sometimes network is not present and it takes up to 1.5 and 2 minutes before it is available.
Any Idea what could cause this behaviour?
It is the onboard controller at my Gigabyte Aeorus Pro which is also used by unraid:
06:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
I have also a 10GBe Ethernetcard with two ports. This network never shows that behaviour.
-
I did the update from 6.9.2 to 6.11 and now Unraid freezes and does not react when I shutdown a MacOS VM.
GUI does not load, also I am not able to ping the Unraid server. I have a AMD 5700XT and AMD RX480 (known for the vendor reset bug) in my system, but never had this problems under 6.9.2.
Even Force stop of the VM freezes Unraid and I am not able to use it. Only way is to power off and reeboot the system.
Any Ideas? -
1 hour ago, ghost82 said:
Ok, can you attach:
1. a ioreg file with the dongle connected to usb-c with the adapter (matisse)
2. a ioreg file with the dongle connected to usb type A port without usb-c adapter (matisse)
Before saving the ioreg files better to disconnect all usb devices you can, disconnect hub(s), webcam, usb storages, etc.
I'd want to try to inject the usb map kext.
I'm not confident that it will work with the hub, nor with the usb plugin (not because of the plugin but because of the emulated controller), but there could be some hope for the other usb type A ports.
Do the other type A ports work with usb pendrives?
We are ot here, sorry Simon
Yes of course, will send you the files tomorrow. We can switch to PM until the problem is solved if you'd like to!-
1
-
-
No need for sorries!
1) The dongle is a regular usb dongle. I connect it via USB - USB-C adapter to the USB-C port of my board, as this was the only way to get it working.
2) yes, the headset can run wireless and via cable. and yes, connects fine both via dongle and usb cable to the usb c port. I am not sure if the usb-c is part of the matisse controller.
Copy of my IOMMU groups attatched.
Best would be if it could work on any other USB port (hub or board manually or with usb plugin manager).
If the dongle is connected via USB-C (working) it shows up as this device.
If the dongle is connected on the hub which is passthrough (not working) it looks like that (it sorts in one cat deeper in the usb tree).
The device is listed as:
CORSAIR VIRTUOSO SE Wireless Gaming Headset:
Produkt-ID: 0x0a46
Hersteller-ID: 0x1b1c (CORSAIR MEMORY INC.)
Version: 0.00
Seriennummer: 142b6156000700da
Geschwindigkeit: Bis zu 12 MBit/s
Hersteller: Corsair
Standort-ID: 0x06311000 / 16
Verfügbare Stromstärke (mA): 500
Erforderliche Stromstärke (mA): 500
Zusätzlicher Betriebsstrom (mA): 0
-
5 minutes ago, ghost82 said:
A kext works if it's loaded, doesn't matter if it's injected or loaded from /L/E or S/L/E.
When I was talking about the usb map kext I was referring to a kext to map the usb ports of the controller, and manually giving power values.
Sorry but maybe I didn't understand, please reply to the following questions:
1. does the dongle works in the mac os vm if connected to a usb port (no hub), by passing through the usb device only (no usb controller passthrough)?
2. are you passing through a usb controller in the vm?if so, does the dongle works if connected to one of these ports (no hub)?
Note: by "works", I mean only if it's detected by the os.
1) The headset (dongle and connection via usb cable) works fine out of the box on a real mac without any additional software.
2) The headset (dongle and usb cable) does not work on any usb port which is passed through exclusivly on that port.
3) The headset (dongle and usb cable) does not work on any a onboard controller port which is passed through vfio IOMMU group. In my case this is a AMD Matisse USB 3.0 Host Controller | USB controller (09:00.1). On this controller I use a usb hub. The headset also does not work on any of the hubs ports.
4) The headset (dongle and cable) does work out of the box on the USB-C port of the mainboard. I did not configure this usb-c port extra via vfio iommu. My guess is, it belongs to the AMD Matisse USB 3.0 Host Controller.
5 ) The headset does not show up at all, while I trying to attatch it via usb plugin manager. It shows as connectet via plugin interface, but the device does not pop up under MacOs sound settings.
Not works means: If connected on both sides, meaning mic and sound are activated in sound settings, the headset does not work. Sound stutters, also recording.
When only one part is active in sound settings, the single selected function works just fine.
So if sound is on and mic not selected, sound works. Also vice versa, if headset sound is off, speakers on and headset mic is selected for recording, it records just fine.
It seems that there is a problem to seperate the two funtions sound and recording.
-
4 hours ago, ghost82 said:
I would say...maybe...if the usb 3 controller is compatible and that dongle too with usb 3 (it seems it is since it works on the usb c port), there should be no issue. Maybe there is the need of a usb map kext injected in opencore. Third parties USB hubs don't play well with mac os too, even in official macs..
Very good point!
This specific USB Dongle from Corsair indeed has a kext which installs into /L/E via Corsair iCUE Software. There is a <key>idProductArray</key> in info.plist and <key>idVendor</key> <integer>6940</integer> for Corsair itself. I packed the kext down below.
But on my Macbook Pro, where no Corsair iCUE Software is installed, the kext is missing and the Dongle works out of the box with MacOS.You think I should give it a try and put the kext into opencore to inject from there rather then /L/E and see if this changes anything? I guess this specific kext has nothing to do with the function of the headset and dongle.
-
On 5/20/2022 at 1:44 AM, KnF said:
It's me again. I'm having some issues, but I will not ask you to solve them. I'm going to try help you improve this plugin which is already awesome. I'm a 15 year experience dev so I think I can try to debug the issues that I'm having, but I might need your help from time to time.
I've been trying to pinpoint an issue. Most of the times it works just fine, but sometimes it doesn't.
I'm gonna explain my setup so you get more context.
I have a Ugreen USB 3.0 Switch which has 4 "devices" ports and 2 "computer" ports. When you press the button on top of it, it disconnects the 4 "devices" from PC 1 and connects them into PC 2. You click again and the same thing happens but in reverse. So far so good. Never had any issues even though PC 1 is a PC (Unraid now) and PC 2 is a Macbook Pro (work laptop).
I only have 3 devices connected to it.
- K70 Keyboard.
- Corsair Dongle for Headphones
- Logitech USB wireless receiver for mouse.
Whenever I press the button to switch from PC 2 to PC 1 this is what I see in the syslog (time and host removed):
Bear in mind that I deleted all the rules!
kernel: usb 2-7: new SuperSpeed USB device number 40 using xhci_hcd kernel: hub 2-7:1.0: USB hub found kernel: hub 2-7:1.0: 4 ports detected kernel: usb 1-4.4: new high-speed USB device number 52 using xhci_hcd usb_manager: Info: rc.usb_manager usb_add GenesysLogic_USB3.1_Hub /dev/bus/usb/002/040 002 040 kernel: hub 1-4.4:1.0: USB hub found kernel: hub 1-4.4:1.0: 4 ports detected usb_manager: Info: rc.usb_manager Autoconnect No Mapping found GenesysLogic_USB3.1_Hub /dev/bus/usb/002/040 002 040 port 2-7 usb_manager: Info: rc.usb_manager usb_add GenesysLogic_USB2.0_Hub /dev/bus/usb/001/052 001 052 usb_manager: Info: rc.usb_manager Autoconnect No Mapping found GenesysLogic_USB2.0_Hub /dev/bus/usb/001/052 001 052 port 1-4.4 kernel: usb 1-4.4.2: new full-speed USB device number 53 using xhci_hcd kernel: input: Corsair Corsair K70R Gaming Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.2/1-4.4.2:1.0/0003:1B1C:1B09.0175/input/input485 kernel: hid-generic 0003:1B1C:1B09.0175: input,hidraw2: USB HID v1.11 Keyboard [Corsair Corsair K70R Gaming Keyboard] on usb-0000:00:14.0-4.4.2/input0 kernel: input: Corsair Corsair K70R Gaming Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.2/1-4.4.2:1.1/0003:1B1C:1B09.0176/input/input486 kernel: hid-generic 0003:1B1C:1B09.0176: input,hidraw3: USB HID v1.11 Device [Corsair Corsair K70R Gaming Keyboard] on usb-0000:00:14.0-4.4.2/input1 kernel: input: Corsair Corsair K70R Gaming Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.2/1-4.4.2:1.2/0003:1B1C:1B09.0177/input/input487 kernel: hid-generic 0003:1B1C:1B09.0177: input,hidraw4: USB HID v1.11 Keyboard [Corsair Corsair K70R Gaming Keyboard] on usb-0000:00:14.0-4.4.2/input2 kernel: usb 1-4.4.3: new full-speed USB device number 54 using xhci_hcd usb_manager: Info: rc.usb_manager usb_add Corsair_Corsair_K70R_Gaming_Keyboard /dev/bus/usb/001/053 001 053 kernel: input: Corsair CORSAIR VIRTUOSO SE Wireless Gaming Headset as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.3/1-4.4.3:1.3/0003:1B1C:0A3E.0178/input/input488 kernel: input: Corsair CORSAIR VIRTUOSO SE Wireless Gaming Headset Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.3/1-4.4.3:1.3/0003:1B1C:0A3E.0178/input/input489 kernel: input: Corsair CORSAIR VIRTUOSO SE Wireless Gaming Headset as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.3/1-4.4.3:1.3/0003:1B1C:0A3E.0178/input/input490 kernel: hid-generic 0003:1B1C:0A3E.0178: input,hiddev98,hidraw5: USB HID v1.11 Device [Corsair CORSAIR VIRTUOSO SE Wireless Gaming Headset] on usb-0000:00:14.0-4.4.3/input3 kernel: hid-generic 0003:1B1C:0A3E.0179: hiddev99,hidraw6: USB HID v1.11 Device [Corsair CORSAIR VIRTUOSO SE Wireless Gaming Headset] on usb-0000:00:14.0-4.4.3/input4 kernel: usb 1-4.4.4: new full-speed USB device number 55 using xhci_hcd usb_manager: Info: rc.usb_manager usb_add Corsair_CORSAIR_VIRTUOSO_SE_Wireless_Gaming_Headset_16addd87000400da /dev/bus/usb/001/054 001 054 kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.4/1-4.4.4:1.0/0003:046D:C539.017A/input/input491 kernel: hid-generic 0003:046D:C539.017A: input,hidraw7: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-4.4.4/input0 kernel: input: Logitech USB Receiver Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.4/1-4.4.4:1.1/0003:046D:C539.017B/input/input492 kernel: input: Logitech USB Receiver Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.4/1-4.4.4:1.1/0003:046D:C539.017B/input/input493 kernel: input: Logitech USB Receiver System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.4/1-4.4.4:1.1/0003:046D:C539.017B/input/input494 kernel: hid-generic 0003:046D:C539.017B: input,hiddev100,hidraw8: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-4.4.4/input1 kernel: hid-generic 0003:046D:C539.017C: hiddev101,hidraw9: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-4.4.4/input2 usb_manager: Info: rc.usb_manager Autoconnect Parent 1-4.4 usb_manager: Info: rc.usb_manager Autoconnect No Mapping found Corsair_Corsair_K70R_Gaming_Keyboard /dev/bus/usb/001/053 001 053 port 1-4.4.2 usb_manager: Info: rc.usb_manager Autoconnect Parent 1-4.4 usb_manager: Info: rc.usb_manager Autoconnect No Mapping found Corsair_CORSAIR_VIRTUOSO_SE_Wireless_Gaming_Headset_16addd87000400da /dev/bus/usb/001/054 001 054 port 1-4.4.3 usb_manager: Info: rc.usb_manager usb_add Logitech_USB_Receiver /dev/bus/usb/001/055 001 055 usb_manager: Info: rc.usb_manager Autoconnect Parent 1-4.4 usb_manager: Info: rc.usb_manager Autoconnect No Mapping found Logitech_USB_Receiver /dev/bus/usb/001/055 001 055 port 1-4.4.4
Notice how usb_manager tries to map things as soon as they're detected.
Now, I created a rule for the hub 1-4.4 so it attaches to the VM on plug and vm start. This is the log for the transition when I press the button (reconnection):
kernel: usb 2-7: new SuperSpeed USB device number 44 using xhci_hcd kernel: hub 2-7:1.0: USB hub found kernel: hub 2-7:1.0: 4 ports detected kernel: usb 1-4.4: new high-speed USB device number 70 using xhci_hcd kernel: hub 1-4.4:1.0: USB hub found kernel: hub 1-4.4:1.0: 4 ports detected usb_manager: Info: rc.usb_manager usb_add GenesysLogic_USB3.1_Hub /dev/bus/usb/002/044 002 044 usb_manager: Info: rc.usb_manager Autoconnect No Mapping found GenesysLogic_USB3.1_Hub /dev/bus/usb/002/044 002 044 port 2-7 usb_manager: Info: rc.usb_manager usb_add GenesysLogic_USB2.0_Hub /dev/bus/usb/001/070 001 070 usb_manager: Info: rc.usb_manager Autoconnect No Mapping found GenesysLogic_USB2.0_Hub /dev/bus/usb/001/070 001 070 port 1-4.4 kernel: usb 1-4.4.2: new full-speed USB device number 71 using xhci_hcd kernel: input: Corsair Corsair K70R Gaming Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.2/1-4.4.2:1.0/0003:1B1C:1B09.01A3/input/input546 kernel: hid-generic 0003:1B1C:1B09.01A3: input,hidraw2: USB HID v1.11 Keyboard [Corsair Corsair K70R Gaming Keyboard] on usb-0000:00:14.0-4.4.2/input0 kernel: input: Corsair Corsair K70R Gaming Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.2/1-4.4.2:1.1/0003:1B1C:1B09.01A4/input/input547 kernel: hid-generic 0003:1B1C:1B09.01A4: input,hidraw3: USB HID v1.11 Device [Corsair Corsair K70R Gaming Keyboard] on usb-0000:00:14.0-4.4.2/input1 kernel: input: Corsair Corsair K70R Gaming Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.2/1-4.4.2:1.2/0003:1B1C:1B09.01A5/input/input548 kernel: hid-generic 0003:1B1C:1B09.01A5: input,hidraw4: USB HID v1.11 Keyboard [Corsair Corsair K70R Gaming Keyboard] on usb-0000:00:14.0-4.4.2/input2 kernel: usb 1-4.4.3: new full-speed USB device number 72 using xhci_hcd usb_manager: Info: rc.usb_manager usb_add Corsair_Corsair_K70R_Gaming_Keyboard /dev/bus/usb/001/071 001 071 kernel: input: Corsair CORSAIR VIRTUOSO SE Wireless Gaming Headset as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.3/1-4.4.3:1.3/0003:1B1C:0A3E.01A6/input/input549 kernel: input: Corsair CORSAIR VIRTUOSO SE Wireless Gaming Headset Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.3/1-4.4.3:1.3/0003:1B1C:0A3E.01A6/input/input550 kernel: input: Corsair CORSAIR VIRTUOSO SE Wireless Gaming Headset as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.3/1-4.4.3:1.3/0003:1B1C:0A3E.01A6/input/input551 kernel: hid-generic 0003:1B1C:0A3E.01A6: input,hiddev98,hidraw5: USB HID v1.11 Device [Corsair CORSAIR VIRTUOSO SE Wireless Gaming Headset] on usb-0000:00:14.0-4.4.3/input3 kernel: hid-generic 0003:1B1C:0A3E.01A7: hiddev99,hidraw6: USB HID v1.11 Device [Corsair CORSAIR VIRTUOSO SE Wireless Gaming Headset] on usb-0000:00:14.0-4.4.3/input4 kernel: usb 1-4.4.4: new full-speed USB device number 73 using xhci_hcd usb_manager: Info: rc.usb_manager usb_add Corsair_CORSAIR_VIRTUOSO_SE_Wireless_Gaming_Headset_16addd87000400da /dev/bus/usb/001/072 001 072 kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.4/1-4.4.4:1.0/0003:046D:C539.01A8/input/input552 kernel: hid-generic 0003:046D:C539.01A8: input,hidraw7: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-4.4.4/input0 kernel: input: Logitech USB Receiver Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.4/1-4.4.4:1.1/0003:046D:C539.01A9/input/input553 kernel: input: Logitech USB Receiver Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.4/1-4.4.4:1.1/0003:046D:C539.01A9/input/input554 kernel: input: Logitech USB Receiver System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4/1-4.4.4/1-4.4.4:1.1/0003:046D:C539.01A9/input/input555 kernel: hid-generic 0003:046D:C539.01A9: input,hiddev100,hidraw8: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-4.4.4/input1 kernel: hid-generic 0003:046D:C539.01AA: hiddev101,hidraw9: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-4.4.4/input2 usb_manager: Info: rc.usb_manager Autoconnect Parent 1-4.4 usb_manager: Info: rc.usb_manager Autoconnect Parent vm state:running Corsair_Corsair_K70R_Gaming_Keyboard running 001 071 port 1-4.4.2 usb_manager: Info: rc.usb_manager Autoconnect Parent 1-4.4 usb_manager: Info: rc.usb_manager Autoconnect Parent vm state:running Corsair_CORSAIR_VIRTUOSO_SE_Wireless_Gaming_Headset_16addd87000400da running 001 072 port 1-4.4.3 acpid: input device has been disconnected, fd 13 acpid: input device has been disconnected, fd 14 usb_manager: Info: rc.usb_manager usb_add Logitech_USB_Receiver /dev/bus/usb/001/073 001 073 usb_manager: usb_manager virsh called KnF 1 71 Device attached successfully usb_manager: usb_manager virsh called KnF 1 72 error: Failed to attach device from /tmp/libvirthotplugusbbybusKnF.xml error: Requested operation is not valid: USB device 001:072 is in use by driver QEMU, domain KnF usb_manager: Info: rc.usb_manager Autoconnect Parent 1-4.4 usb_manager: Info: rc.usb_manager Autoconnect Parent vm state:running Logitech_USB_Receiver running 001 073 port 1-4.4.4 acpid: input device has been disconnected, fd 15 acpid: input device has been disconnected, fd 16 acpid: input device has been disconnected, fd 17 usb_manager: usb_manager virsh called KnF 1 73 Device attached successfully
As you can see, there's 3 usb devices (71, 72 and 73) two of them attach successfully and there's one that fails to attach (the headset). Problem is that even though 71 (keyboard) attached successfully it doesn't work. When the keyboard works it shows in the device manager (inside the VM) as 3 "HID Keyboards"
and when it doesn't it only shows up once.
If I disconnect the keyboard from the switch and re-connect it, it works perfectly again....
What I think it's happening is that when the /tmp/libvirthotplugusbbybusKnF.xml file is being generated and passed to virsh it's too soon and there might be a race condition that's causing the issue. I'm gonna try to edit the files of the plugin and add a little delay to the execution of the virsh command. Maybe that's all it needs. I'll report back.
Did you find a solution for this problem?
I also use the Corsair Dongle for a Headset which does not work with the USB Manager Plugin at MacOS.
Bit it looks like it is not a Dongle connection problem, cause the same behaviour shows up while connectet via USB cable.
I am able to attatch it to the VM, but the device does not show up under MacOS.
The dongle only works on Mac at the USB-C Port of my mainboard which seems to be internaly connected with this USB Host controller:
It works exlusivly while conneted via this single USB-C Port (sound and mic without any flaws).
Directly connected to the HUB I use at this USB Host controller Headset sound is working, but mic is quirky and records with gaps and hickups. When I go to the mic prefs in system>audiopreferences every Video I play starts to stutter.
Headset sound alone works fine at all, while mic is off.
Under Windows VM Dongle and cable are working without any problems while Headset is attatched via USB Manager Plugin.
My Board is a 570Z Aeorus Pro.
Any Ideas how to adress the problem under MacOS? -
1 hour ago, itimpi said:
Check under Settings->Unassigned Devices that you actually have it set to make SMB shares from UD visible on the network.
I did not set the 'No' to 'Public' as I thought 'No' ment no security and public access which is oviously not the case.
Switching to public did it! Thanks a lot for guiding me through this!
-
I have a problem with the UD plugin, not beeing able to mount any of my Unassigned shared Disks from /mnt/disks aka /mnt/remotes under windows and MacOS.
Under Unraid, via browser I can open them up.
I am not sure how to get access to /mnt/shares as I think I switched everything needed on under settings. Via Krusader, I see everything (screenshots att.) Any help?
-
I have a problem with the plugin. I updated the user scripts plugin and afterwards it disappeared from my unraid menu and if I try to open it via the plugins > installed plugins tab and click on it, I get a black screen. Reinstall did not fix the problem.
I am on Unraid Version: 6.10.0-rc1
Any ideas? -
On 2/22/2021 at 7:51 AM, glennv said:
I have it finaly working after also almost guving up.
Build a latest 6.9.0 rc2 kernel with the latest gnif/vendor-reset patch and now zero issues anymore with Macos or Windows VM and passthru. Can restart the VM at will , even force kill.
check this thread
https://forums.unraid.net/topic/92865-support-ich777-nvidiadvbzfsiscsimft-kernel-helperbuilder-docker/Same here with my 5700XT and RX480. Both cards run as they should after vendor-reset patch.
-
21 hours ago, mSedek said:
NO, I havent sold my 5700XT yet. my issues are none related to the cards or macOS, my 5700XT works perfect in Catalina and BIG SUR, the problem is that at the moment BIG SUR has no support for JAVA 8 and IF i sell my 5700XT to get a 6800 (which is highly available here in my country) just to have a RESET BUG free experience, then I lose my ability to develop in macOS as 6000 series ONLY works in BIG SUR.. either way im screwed lol..
Is there already driver support for big navi 6000 series in MacOS? Thought there are still no 6800, 6800XT, 6900 XT drivers available for MacOS?
-
Today I also tried to passthrough my Wacom Display with Drawing support via USB:
Bus 005 Device 003:ID 056a:00c6 Wacom Co., Ltd DTZ-1200W [Cintiq 12WX]
It does not work either as a single USB device passthrough neither on my USB Port passthrough.Same problem as described above.
Any other ideas about that?
-
19 hours ago, giganode said:
The vendor-reset got an update for navi users. I tested it on my system.
I have no broken audio anymore after resets. For me this is a real breakthrough!
I don't need the old navi patch anymore now.
I can now boot between Windows 10 20H2, macOS Big Sur 11.1 and Ubuntu 20.10.
For all navi user who wanna try it out:
- Force update the docker
-
Edit the docker and add a variable like this:
- Try and hopefully enjoy!
Keep in mind, this only fixes the specific audio issue for navi users.
Please report your expierences here.
Special Thanks to @ich777 for that fast edit.
I also can confirm, that the latest vendor-reset for the audio fixed the problem with my Powercolor 5700 XT. It never reseted properly after an OS shutdown, or VM stop via UNRAID. NOW EVERYTHING WORKS LIKE A CHARM as it is supposed to be. Finally I will be a happy 5700 XT user. So kudos to @ajmadsen @gnif from github and also to @ICH777 for making it easy to bring all stuff to the UNRAID stick with use of the kernel helper docker!
-
1
-
10 hours ago, ChromeFocus said:
When I try to follow the guides directly I always have a problem some where. It's never user friendly enough for my liking. I wish there was more information on certain things I'm trying to accomplish. But that's just my own stupidity. I'm not comparing it to anything. I'm just too dumb to figure things out when they fail.
Explaining exactly what the problem is should be enough in my opinion but you're right. My GPU isn't being recognized. It bothers me. I apologize. I get so frustrated trying to figure these things out.
What are IOMMU groups? How do I access PCIE override settings in VM Manager? My GPU has no other function that I know of yet. Yes my VM works only in VNC mode. When ever I add the graphics card the VM won't function at all. I'm tired of doing all the steps of setting up the VM. So I'm looking for information to end my madness. It's incredibly frustrating and is turning me off to this whole thing.
Okay, no problem that you are a beginner. Everybody started from zero. So a short round up. Virtualisation and especially Hardware passthrough needs equivalent hardware which you have. Your mainboard groups your hardware, in your case your gpu in several groups, called IOMMU groups. If you GPU is grouped with other hardware passthrough will not be possible. To get your gpu separated, you can use the Virtual Manager in Unraid and setup to split your hardware. The settings there are done at the pcie override tab which gives you several options you should try and see what setting will give you the best result in case of separating. Separation is the basic point to achieve gpu passthrough. If this is not setup correctly, it will not work.
If done right and you setup you gpu as a multifunctional device, all should work just fine. I am not 100% sure about your gpu model, as you said you have an rx570 lite. I know for sure a regular rx570 works nativly under macOS, not so sure about the lite, but I guess it should. I revommend you to read the Unraid Virtualisation Wiki step by step and follow the guides to prepare your Unraid setting. The try to finalize your macOS VM.
https://wiki.unraid.net/UnRAID_6/VM_Management
My advise, dont give up too early.It looks more complicated then it is and when you are fine with the settings you wonder how logical and easy a setup is, compared to a linux kvm installation via console.
Wi-Fi 6 Intel AX210 on macOS Sonoma
in VM Engine (KVM)
Posted
From my running macOS Monterey i've updated to Sonoma 14.3.1.
With the help of @ghost82 I updated all the necessary OpenCore kext and config.plist to the newest version, replaced the old OpenCore image and was able to boot in Sonoma.