Just want to mention the system(firmware, etc.) is brand new, so many issues might be lack of support.
On 4/14/20 1:28 AM, 'awokd' via qubes-users wrote: > 'Max Andersen' via qubes-users: > >> I can actually put in an older wireless usb in the machine, and it sees it >> with lsusb in dom0, but I Dont know how To enable it in vm > In dom0, use qvm-usb to try to attach that device to sys-net. Some USB > devices don't passthrough very well, though. qvm-usb shows no output: [max@dom0 ~]$ qvm-usb BACKEND:DEVID DESCRIPTION USED BY [max@dom0 ~]$ lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter Bus 001 Device 005: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 046d:c318 Logitech, Inc. Illuminated Keyboard Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [max@dom0 ~]$ >> Tried qvm-pci >> >> It showed usb controller on that? >> >> When runming qvm-pci a sys-net-clone-1 dom0:00_14.0 it failed with got empty >> response from qubesd and hung > You might be trying to attach the USB controller itself to > sys-net-clone-1. This can work, if you're sure nothing else is on it > (like your keyboard & mouse). Many systems only have one controller > though, so try USB passthrough first. That was probably what I did and it failed :). Sincerely Max -- 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/e1f5bbea-d78a-80a7-fd58-bc3349efbf64%40militant.dk.
