Nut Eaton UPS "unable to enumerate USB device" after power comes back on

[robertoamd]

Hi Everyone,
I have an issue with my proxmox mini pc (beelink EQ12) server and usb-ups connection.
I have installed and configured the NUT suit to manage my UPS EATON ECO 650, and it works.
When the power goes out the shutdown routine starts, the proxmos server correctly turns off the VM and CT, and after that turns itself down, and after this procedure the ups cuts the power, so It works as designed.

When the power comes back on, the ups starts to supply, and the mini pc starts (it has auto power on, on bios).
At the beginning the UPS usb does not connect to the mini PC with this error on System Log:

May 27 14:24:39 pve kernel: usb 1-1: device descriptor read/64, error -71
May 27 14:24:39 pve kernel: igc 0000:02:00.0 enp2s0: renamed from eth1
May 27 14:24:39 pve kernel: usb 1-1: device descriptor read/64, error -71
May 27 14:24:39 pve kernel: usb 1-1: new full-speed USB device number 3 using xhci_hcd
May 27 14:24:39 pve kernel: usb 1-1: device descriptor read/64, error -71
May 27 14:24:39 pve kernel: usb 1-1: device descriptor read/64, error -71
May 27 14:24:39 pve kernel: usb usb1-port1: attempt power cycle
May 27 14:24:39 pve kernel: usb 1-1: new full-speed USB device number 4 using xhci_hcd
May 27 14:24:39 pve kernel: usb 1-1: Device not responding to setup address.
May 27 14:24:39 pve kernel: usb 1-1: Device not responding to setup address.
May 27 14:24:39 pve kernel: usb 1-1: device not accepting address 4, error -71
May 27 14:24:39 pve kernel: usb 1-1: new full-speed USB device number 5 using xhci_hcd
May 27 14:24:39 pve kernel: usb 1-1: Device not responding to setup address.
May 27 14:24:39 pve kernel: usb 1-1: Device not responding to setup address.
May 27 14:24:39 pve kernel: usb 1-1: device not accepting address 5, error -71
May 27 14:24:39 pve kernel: usb usb1-port1: unable to enumerate USB device

The comand lsusb does not show the UPS.
To re-connect my ups I must unplug and plug the usb cable, no other action works. After that i can see the ups on lsusb, and i can re start the NUT server.

May 27 15:01:08 pve kernel: usb 1-3: new full-speed USB device number 8 using xhci_hcd
May 27 15:01:09 pve kernel: usb 1-3: New USB device found, idVendor=0463, idProduct=ffff, bcdDevice= 1.00
May 27 15:01:09 pve kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=4
May 27 15:01:09 pve kernel: usb 1-3: Product: Ellipse ECO
May 27 15:01:09 pve kernel: usb 1-3: Manufacturer: EATON
May 27 15:01:09 pve kernel: usb 1-3: SerialNumber: 000000000

I have found the some problem in issues related to raspberry pi, where a user have suggested a workaround, put an USB hub between UPS and the server, this solution work for me, but I want to understand the problem!

Thanks

 

[inagy]

Hi robertoamd!

Did you find a solution for this? I have the exact same problem, with a Beelink S12 Mini Pro (Intel N100) and an Eaton 5E Gen2 700 USB.
Adding an extra USB2.0 hub in-between indeed fixes the issue. Although I don't see anything different in dmesg about the way Linux detects the USB HID device offered by the UPS.

The strange thing is, I've just tested the UPS and NUT configuration beforehand with a Raspberry Pi 4, and it was working correctly there after a cold boot, every time. So it must be some kind of incompatibility with the Beelink. My hunch is that the UPS doesn't really like being on a USB3 port, and the hub forcing it to be USB2 fixes it somehow. On the Pi I was connecting it to the USB2 ports.

There's also a bunch of options in the BIOS.
Maybe one of these could solve it? (it's not mine, I've grabbed it from this video. I don't have the patience right now to move all stuff next a monitor in another room to further experiment)