On Wednesday, January 8, 2020 at 3:14:03 PM UTC-5, brend...@gmail.com wrote:
> 1. Qubes has pcie hotplug disabled in the dom0 kernel, which TB uses for > PCIe-based thunderbolt devices. This is disabled for security reasons. > 2. The TB alternate mode that supports USBs might not instantiate the PCIe > USB controller it connects through *until a USB device is connected to that > port*. > 3. Therefore...depending on BIOS support...you *might* be able to have a > USB device seen by qubes if the USB device is plugged in at power-on. Even > if that works, it might be on a USB PCIe controller that is not already > attached to your sys-usb (if you have one). > 4. If it does work, you might want to create a sys-usb-c which you run > only after connecting a device to the port at boot time, and assign the > (usually hidden) PCIe USB controller that that VM only. > > > Thanks for the reply! I took a break in the middle of typing my own reply, for a meeting, so your message came in as I was completing it. All of your points seem to line up with what I discovered poking around. Yes, I can get usb-c seen if device connected at power on. Thanks for the idea of an secondary sys-usb for usb-c! I had not considered that. If I discover I really need something Usb-c, which seems likely in time, I will probably do that. For now it's really just my new yubikey, which I am going to give to someone else and replace with a USB-A/NFC. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/aad044cc-2da8-44b9-b515-367edc7490b3%40googlegroups.com.
