@@ -673,6 +673,30 @@ the symptoms for the problem look like this:
673
673
[ 126.825775] hid-generic 0003:0463:FFFF.000B: timeout initializing reports
674
674
[ 132.527809] usb 1-6: USB disconnect, device number 10
675
675
676
+ A similar report on the driver side may look like:
677
+
678
+ usbhid-ups[4554]: libusb_get_report: Input/output error
679
+ upsd[4591]: Data for UPS [eaton] is stale - check driver
680
+ usbhid-ups[4554]: Can't claim USB device [0463:ffff]: No such file or directory
681
+ upsd[4591]: Can't connect to UPS [eaton] (usbhid-ups-eaton): No such file or directory
682
+ upsmon[5148]: Poll UPS [eaton@localhost] failed - Driver not connected
683
+ upsmon[5148]: Communications with UPS eaton@localhost lost
684
+
685
+ Other similar looking issues may include improper setup of udev, upower
686
+ and similar frameworks to hand over the device from the OS to a driver
687
+ daemon; competition with other software probing USB devices (ModemManager
688
+ was mentioned in this context), including running several copies of the
689
+ NUT drivers trying to use same port (e.g. one started by services and
690
+ another manually as you tried to debug the problems).
691
+
692
+ Software quirks aside, please do test with a different USB cable and/or port
693
+ on the computer. These were known to cause grief beyond what can be fixed
694
+ with a few key words ;)
695
+
696
+ Finally, sometimes the issue is on the OS side (and/or USB chipset), to
697
+ the point that the USB driver can not be unloaded and re-attached until
698
+ you power cycle the system.
699
+
676
700
== Why doesn't my package work?
677
701
678
702
Or a variation like...
0 commit comments