On Mon, Oct 08, 2018 at 07:27:23PM -0700, Alex Winter wrote: > Here are the usb controllers when I type in 'sudo lspci -v' > > 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family > USb xHCI (Rev 05) (prog-if 30 [XHCI]) > Subsystem: Micro-Star International Co., Ltd. [MSI] Device 10ec > Flags: bus master, medium devsel, latency 0, IRQ 57 > Memory at f7b00000 (64-bit, non-prefetchable) [size=64k] > Capabilities: [70] Power Management version 2 > Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ > Kernel driver in use: xhci_hcd > Kernel modules: xhci_pci > > 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family > USb EHCI #2 (Rev 05) (prog-if 20 [EHCI]) > Subsystem: Micro-Star International Co., Ltd. [MSI] Device 10ec > Flags: bus master, medium devsel, latency 0, IRQ 16 > Memory at f7b18000 (32-bit, non-pcopy and pasterefetchable) [size=1k] > Capabilities: [50] Power Management version 2 > Capabilities: [58] Debug port: BAR=1 offset=00a0 > Capabilities: [98] PCI Advanced Features > Kernel driver in use: ehci-pci > Kernel modules: ehci_pci > > 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family > USb EHCI #1 (Rev 05) (prog-if 20 [EHCIReciever]) > Subsystem: Micro-Star International Co., Ltd. [MSI] Device 10ec > Flags: bus master, medium devsel, latency 0, IRQ 23 > Memory at f7b17000 (32-bit, non-prefetchable) [size=1k] > Capabilities: [50] Power Management version 2 > Capabilities: [58] Debug port: BAR=1 offset=00a0 > Capabilities: [98] PCI Advanced Features > Kernel driver in use: ehci-pci > Kernel modules: ehci_pci > > when I type in 'sudo lsusb -v' Here are the buses. > > Bus 002 Device 002: ID 8087:8000 Intel Corp. > > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > iProduct 2 EHCI Host Controller > iSerial 1 0000:00:1d.0 > > Bus 001 Device 002: ID 8087:8008 Intel Corp. > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > iproduct 2 EHCI Host Controller > iSerial 1 0000:00:1a.0 > > Bus 004 Device 002: ID 04e8:61f5 Samsung Electronics Co., Ltd > > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > iProduct 2 xHCI Host Controller > iSerial 1 0000:00:14.0 > > Bus 003 Device 007: ID 1770:ff00 > > Bus 003 Device 005: ID 8087:07dc Intel Corp. > > Bus 003 Device 004: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 > receiver > > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > iProduct 2 xHCI Host Controller > iSerial 1 0000:00:14.0 >
Without knowing your laptop or exact setup I'm working a bit blind. I think you say you have a usbVM and are running qubes from a USB stick - is that right? You haven't said *which* controller your ports all use. >From the listing it's clear you have usb2 and usb3 controllers, and it may be that ALL your ports are 2/3. More info needed please. I'll throw out some wild suggestions: Hide one of the controllers on the kernel command line(say the xhci). Disable ehci in usbVM, and use only USB3 devices with the usbVM. It might be possible to delete one of the devices in dom0, and still have it available in qubes. (I mean literally rm /dev/bus/usb/001) You could unbind a pci device early in boot. I've done this with Xen before, to have one port in dom0 and the rest available to xen-pciback, but haven't tried it with Qubes. You could use udev to block two of the ports in dom0, so that they are only available in the usbVM. unman -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20181010141825.hstxmzkgm6sdh3x3%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
