USB-C Ethernet LAN not working after attach to sys-net

User Support
1

Hi All,

As a niewbie - kindly requesting help with this issue.
I am using ThinkPad X390 and after a bit of struggle managed to install 4.03 version incluing standalone Win10.

As my built-in WiFi works like charm, I am not able to make the LAN work. This laptop comes without physical RJ45 port but has a special socket for Ethernet connection. I am not using it but a USB-C docking station that delivers all peripherals including net, additional displays, etc.

When I make my VM use net-usb then the network is accessible via smooth DHCP configuration. I do however would like to make it easier and to combine net access features in one qube - sys-net. For that purpoes I am trying to attach the USB network card to the sys-net. And this operation doesn’t work. I can see following log entries that indicate problmes, but have no idea how it could be fixed.

Hope to find someone experienced enough who could help me with that!
Thanks in advance,
T.

Log (sys-net):
[ 572.533096] usb 3-1: SetAddress Request (17) to port 0
[ 572.533128] usb 3-1: new SuperSpeed Gen 1 USB device number 17 using vhci_hcd
[ 572.549151] usb 3-1: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=31.00
[ 572.549189] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[ 572.549223] usb 3-1: Product: USB 10/100/1000 LAN
[ 572.549246] usb 3-1: Manufacturer: Realtek
[ 572.549264] usb 3-1: SerialNumber: 000000000000
[ 573.451132] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 574.338973] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 575.226891] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 576.115170] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 576.115216] r8152 3-1:1.0 (unnamed net_device) (uninitialized): Get ether addr fail
[ 576.115471] r8152 3-1:1.0 eth0: v1.09.9
[ 576.117755] usb 3-1: USB disconnect, device number 17
[ 577.019183] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 577.906984] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 577.907030] usb usb3-port1: attempt power cycle
[ 579.107133] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 579.995008] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[ 579.995055] usb usb3-port1: unable to enumerate USB device
[ 580.061330] audit: type=1106 audit(1608116240.446:162): pid=3463 uid=0 auid=4294967295 ses=4294967295 msg=‘op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_umask,pam_lastlog acct=“root” exe="/usr/lib/qubes/qrexec-agent" hostname=? addr=? terminal=? res=success’
[ 580.061375] audit: type=1104 audit(1608116240.446:163): pid=3463 uid=0 auid=4294967295 ses=4294967295 msg=‘op=PAM:setcred grantors=pam_rootok acct=“root” exe="/usr/lib/qubes/qrexec-agent" hostname=? addr=? terminal=? res=success’

2

For that purpoes I am trying to attach the USB network card to the sys-net.

That will likely not work. More complex USB devices often have issues
when used via USB proxy. What will work is if you combine sys-net and
sys-usb so that sys-net has access to the USB controller and fulfills
the function of sys-usb.

If your keyboard/mouse connect only via USB then be very very careful
what you do as to not lock yourself out!

1 Like
3

Thank you Sven,
that’s what I was actually afraid of. With a glimmer of hope that when I am able to attach a camera to any other qube this would be also very likely to do the same with the NIC. Will do as advised.

Cheers,
T.