R8152 USB NIC had to be re plugged several times to be detected

super488

New Member
Apr 7, 2023
9
0
1
I'm using UE300 TP-Link USB NIC and whenever system was restarted or I unplugged the NIC and replug again, I had to re-plug the USB around 2 - 3 times in order for R8152 driver to detect them. This is very inconvenient for me to come and replug it every time the system restarted. The dmesg -w when I'm plugging in the USB is shown below.

Bash:
[628730.267221] usb 1-5: new full-speed USB device number 43 using xhci_hcd
[628730.395231] usb 1-5: device descriptor read/64, error -71
[628730.631204] usb 1-5: device descriptor read/64, error -71
[628730.875156] usb 1-5: new full-speed USB device number 44 using xhci_hcd
[628731.007212] usb 1-5: device descriptor read/64, error -71
[628731.247177] usb 1-5: device descriptor read/64, error -71
[628731.355267] usb usb1-port5: attempt power cycle
[628731.767180] usb 1-5: new full-speed USB device number 45 using xhci_hcd
[628731.767338] usb 1-5: Device not responding to setup address.
[628731.975292] usb 1-5: Device not responding to setup address.
[628732.183161] usb 1-5: device not accepting address 45, error -71
[628732.311171] usb 1-5: new full-speed USB device number 46 using xhci_hcd
[628732.311339] usb 1-5: Device not responding to setup address.
[628732.523328] usb 1-5: Device not responding to setup address.
[628732.731148] usb 1-5: device not accepting address 46, error -71
[628732.731230] usb usb1-port5: unable to enumerate USB device
[628733.683170] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[628737.787144] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[628739.394297] vmbr0: the hash_elasticity option has been deprecated and is always 16    0.011301] ACPI: SSDT 0x00000000BBFCC000 000734 (v01 HPQOEM PtidDevc 00001000 INT
[628739.669929] vmbr1: the hash_elasticity option has been deprecated and is always 16    0.011304] ACPI: SSDT 0x00000000BBFCA000 0017AE (v02 CpuRef CpuSsdt  00003000 INT
[628742.211064] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[628747.090949] usb 1-5: new full-speed USB device number 48 using xhci_hcd
[628747.222938] usb 1-5: device descriptor read/64, error -71
[628747.466951] usb 1-5: device descriptor read/64, error -71
[628747.702924] usb 1-5: new full-speed USB device number 49 using xhci_hcd
[628747.838948] usb 1-5: device descriptor read/64, error -71
[628748.078941] usb 1-5: device descriptor read/64, error -71
[628748.187048] usb usb1-port5: attempt power cycle
[628748.602919] usb 1-5: new full-speed USB device number 50 using xhci_hcd
[628748.603070] usb 1-5: Device not responding to setup address.
[628748.811079] usb 1-5: Device not responding to setup address.
[628749.022921] usb 1-5: device not accepting address 50, error -71
[628749.154926] usb 1-5: new full-speed USB device number 51 using xhci_hcd
[628749.155060] usb 1-5: Device not responding to setup address.
[628749.367047] usb 1-5: Device not responding to setup address.
[628749.574944] usb 1-5: device not accepting address 51, error -71
[628749.575024] usb usb1-port5: unable to enumerate USB device
[628750.498960] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[628754.175458] vmbr0: the hash_elasticity option has been deprecated and is always 16    0.011342] ACPI: ASF! 0x00000000BBFC0000 0000A0 (v32 HPQOEM  UYA     00000001 TFS
[628754.466845] vmbr1: the hash_elasticity option has been deprecated and is always 16    0.011346] ACPI: FPDT 0x00000000BBFBF000 000044 (v01 HPQOEM EDK2     00000002   
[628754.922855] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[628761.430814] usb 2-2: new SuperSpeed USB device number 7 using xhci_hcd
[628761.455427] usb 2-2: New USB device found, idVendor=2357, idProduct=0601, bcdDevice=30.00                  ove [mem 0x000a0000-0x000fffff] usable
[628761.455438] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[628761.455443] usb 2-2: Product: USB 10/100/1000 LAN
[628761.455447] usb 2-2: Manufacturer: TP-Link
[628761.455450] usb 2-2: SerialNumber: 000001
[628761.459218] cdc_ether 2-2:2.0 eth0: register 'cdc_ether' at usb-0000:00:14.0-2, CDC Ethernet Device, 28:87:ba:6c:32:a3
[628761.460242] cdc_ether 2-2:2.0 eth0: unregister 'cdc_ether' usb-0000:00:14.0-2, CDC Ethernet Device         pages for direct mapping
[628761.607031] r8152-cfgselector 2-2: reset SuperSpeed USB device number 7 using xhci_hcd                     [mem 0x30c69000-0x3462bfff]
[628761.652872] r8152 2-2:1.0: load rtl8153a-4 v2 02/07/20 successfully
[628761.679290] r8152 2-2:1.0 eth0: v1.12.13
[628761.713178] r8152 2-2:1.0 enx2887ba6c32a3: renamed from eth0

As you can see I've re-plug the USB 3 times for it to be actually working. I think it might have something to do with usb 1-5: device descriptor read/64, error -71 ?
 
I've noticed that all the failed attempt at enabling the NIC seems to have the incorrect USB Port. The actual port is USB 2-2 but all the failed attempt showed that the port is USB 1-5
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!