On 1/12/19 6:03 PM, gone wrote:
On 1/12/19 1:44 AM, 'awokd' via qubes-users wrote:
gone wrote on 1/11/19 9:01 PM:
Hello,
I've tried to use different USB to Ethernet adapters with QubesOS but
without success. Is there a chance to make them usable?
I've seen some have been successful. Where is it not working? Have you
checked sys-usb's "ip addr" and journalctl after plugging one in?
Sorry for my unprecise way of asking.
It's not working on a Dell XPS Laptop with QubesOS booted from USB.
So far I have only used external USB memory media as removable devices
in QubesOS, which can be listed with qvm-block and can be perfectly used
and assigned to appVMs with the Devices Widget.
After plugging in the USB to ethernet adapter the following is shown:
$ journalctl | grep usb | tail -8
Jan 12 16:18:33 dom0 kernel: usb 2-1: USB disconnect, device number 7
Jan 12 16:19:49 dom0 kernel: usb 2-6: new SuperSpeed USB device number 8
using xhci_hcd
Jan 12 16:19:49 dom0 kernel: usb 2-6: New USB device found,
idVendor=0bda, idProduct=8153
Jan 12 16:19:49 dom0 kernel: usb 2-6: New USB device strings: Mfr=1,
Product=2, SerialNumber=6
Jan 12 16:19:49 dom0 kernel: usb 2-6: Product: USB 10/100/1000 LAN
Jan 12 16:19:49 dom0 kernel: usb 2-6: Manufacturer: Realtek
Jan 12 16:19:49 dom0 kernel: usb 2-6: SerialNumber: 000001000000
Jan 12 16:19:50 dom0 kernel: usb 2-6: reset SuperSpeed USB device number
8 using xhci_hcd
$ qvm-usb
BACKEND:DEVIDÂ DESCRIPTIONÂ USED BY
So the adapter is recognized on usb 2-6. This also works with a second
adapter of a different brand. And it works on different USB slots. I
haven't tried that with external USB hubs so far. I plugged them
directly into the Laptop.
The Devices Widget only shows local harddisk's partitions and the camera
owned by dom0.
There is no VM called "sys-usb". I read at
https://www.qubes-os.org/doc/usb/ that creating and using a USB cube
could kill functionality of the USB keyboard in a LUKS install. As this
combination is the case here (internal keyboard is USB) I don't think
creating one would be a good idea.
Thanks @awokd. I understand, that dom0 has no networking on purpose.
That's a good point. But even if it can't do it's networking job in
dom0, I still wonder why the adapter isn't visible in the Device Widget.
Shouldn't the USB part of it still be assignable to an appVM?
As I don't even know exactly the meaning of things like "usb 2-6", how
could I find out how many USB controllers the machine has and which one
the keyboard is assigned to? Is such an assignment static or somehow
dynamic? I'd really like to use LAN by cable but don't want to risk to
lock myself out.
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/8dd5a41a-991d-b63a-33db-493363f73008%40posteo.net.
For more options, visit https://groups.google.com/d/optout.
