[Nut-upsuser] Unable to use nut-2.7.4 with Eaton 5E1500I USB

[Manuel Wolfshant]

On 06/19/2017 11:02 AM, Manuel Wolfshant wrote:
> Thank a lot !
> Now, conclusions after attempting builds ( with no docs included since 
> attempting to enable them triggers the errors related to missing or 
> too old tools mentioned by me in an earlier message )
> - building against libsub 1.0 triggers the following 2 errors :
> nutdrv_qx-nutdrv_qx.o: In function `ippon_command':
> /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:679: 
> undefined reference to `libusb_strerror'
> /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:692: 
> undefined reference to `libusb_strerror'
> nutdrv_qx-nutdrv_qx.o: In function `fabula_command':
> /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:907: 
> undefined reference to `libusb_strerror'
> nutdrv_qx-nutdrv_qx.o: In function `krauler_command':
> /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:770: 
> undefined reference to `libusb_strerror'
> nutdrv_qx-nutdrv_qx.o: In function `sgs_command':
> /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:542: 
> undefined reference to `libusb_strerror'
> nutdrv_qx-nutdrv_qx.o:/builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/nutdrv_qx.c:568: 
> more undefined references to `libusb_strerror' follow
> [...]
> libusb1.o: In function `nut_libusb_strerror':
> /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:484: 
> undefined reference to `libusb_strerror'
> /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:469: 
> undefined reference to `libusb_strerror'
> /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:479: 
> undefined reference to `libusb_strerror'
> libusb1.o: In function `nut_libusb_open':
> /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:181: 
> undefined reference to `libusb_strerror'
> /builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:282: 
> undefined reference to `libusb_strerror'
> libusb1.o:/builddir/build/BUILD/nut-v2.7.4-418-gb1314c62.7.4.1/drivers/libusb1.c:289: 
> more undefined references to `libusb_strerror' follow

I did some more digging. It turns out that the version of libusb 1.0 ( 
1.0.9 ) included by RH in RHEL 6 misses the libusr_strerror function 
completely. I bypassed that by building against libusbx ( oldish but 
good enough, I think -- 1.0.19). Unfortunately there not much gain as 
the usbhid driver still cannot access that f*ing interface:

[root at belgrade ~]# usbhid-ups -DDDD -u root -x explore -x 
vendorid="0463" -a eaton
Network UPS Tools - Generic HID driver 0.42 (v2.7.4-418-gb1314c62.7.4.1)
USB communication driver (libusb 1.0) 0.02
    0.000000     [D1] debug level is '4'
    0.001696     [D1] upsdrv_initups...
    0.011580     [D2] Checking device (0463/FFFF)
    1.012644     [D2] - VendorID: 0463
    1.012669     [D2] - ProductID: ffff
    1.012681     [D2] - Manufacturer: unknown
    1.012693     [D2] - Product: unknown
    1.012767     [D2] - Serial Number: unknown
    1.012777     [D2] - Bus: 002
    1.012786     [D2] - Device release number: 0001
    1.012797     [D2] Trying to match device
    1.012836     [D2] Device matches
    1.012842     [D2] Reading first configuration descriptor
    1.012851     [D2] auto detached kernel driver from USB device
    1.013972     [D2] Claimed interface 0 successfully
    1.013983     [D3] nut_usb_set_altinterface: skipped 
libusb_set_interface_alt_setting(udev, 0, 0)
    1.014501     [D2] Unable to get HID descriptor (Pipe error)
    1.014511     [D3] HID descriptor length (method 1) -1
    1.014517     [D4] i=0, extra[i]=09, extra[i+1]=21
    1.014525     [D3] HID descriptor, method 2: (9 bytes) => 09 21 10 01 
21 01 22 25 02
    1.014532     [D3] HID descriptor length (method 2) 549
    1.014538     [D2] HID descriptor length 549
    1.015007     [D2] Unable to get Report descriptor: Resource 
temporarily unavailable


Short of updating the kernel, anything else I can do ?