The log entries in sys-net are filled with a bunch of messages

[gdr...@gmail.com]

Hi,

I created a new sys-net (sys-net2) as network VM to use a wireless USB adapter.

The sys-net2 dmesg logs (guest-sys-net2.log) are filled with a bunch of messages (4878 lines) like the following:

---%<------
First lines
---%<------
[ 0.000000] Linux version 4.14.57-2.pvops.qubes.x86_64 (user@build-fedora4) (gcc version 6.4.1 20170727 (Red Hat 6.4.1-1) (GCC)) #1 SMP Tue Aug 14 14:43:33 UTC 2018
[ 0.000000] Command line: root=/dev/mapper/dmroot ro nomodeset console=hvc0 rd_NO_PLYMOUTH rd.plymouth.enable=0 plymouth.enable=0 nopat
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[...]
[ 11.129065] usb 2-1: new high-speed USB device number 2 using vhci_hcd
[ 11.246132] usb 2-1: SetAddress Request (2) to port 0
[ 11.286211] usb 2-1: New USB device found, idVendor=13b1, idProduct=002f
[ 11.286284] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 11.286369] usb 2-1: Product: Linksys AE1000
[ 11.286429] usb 2-1: Manufacturer: Linksys
[ 12.303201] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 13.191197] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 14.079202] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 14.967200] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 14.967389] ieee80211 phy0: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x1000 with error -19
[ 14.967496] ieee80211 phy0: rt2800_probe_rt: Error - Invalid RT chipset 0x0000, rev 0000 detected
[ 14.967594] ieee80211 phy0: rt2x00lib_probe_dev: Error - Failed to allocate device
[ 14.967788] usbcore: registered new interface driver rt2800usb
[ 14.968575] usb 2-1: USB disconnect, device number 2
[...]

Additionally and deliberately focus is made on my wireless USB adapter.

In contrast, my main sys-net with internal Ethernet port does not display anything.

Any help and advice would be greatly appreciated.

Best regards.

GD Rub

[GDRUB]

In the fact that I am not the only one :
https://github.com/QubesOS/qubes-issues/issues/3778

but no solution found ... :-(

[awokd]

GDRUB wrote on 10/3/18 4:54 PM:

No solution, but you could try the workaround of assigning an entire USB
controller if you have one to spare.