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

[Manuel Wolfshant]

On 06/19/2017 05:33 PM, Charles Lepple wrote:
> On Jun 19, 2017, at 4:27 AM, Manuel Wolfshant wrote:
>>    1.014501     [D2] Unable to get HID descriptor (Pipe error)
>>    1.014511     [D3] HID descriptor length (method 1) -1
> So at this point in the logs, the kernel USB HID driver is detached from the UPS HID interface (until the UPS USB cable is unplugged and reattached). If you run "lsusb -vvv -d 0463:ffff", does it print the HID report descriptor? (Normally, lsusb will only print descriptors for interfaces that are not claimed by a kernel driver or userspace library.)
>
> If so, then it is worth checking to see how usbutils is talking to the UPS.

This is what I get:

#lsusb -vvv -d 0463:ffff

Bus 002 Device 012: ID 0463:ffff MGE UPS Systems UPS
Device Descriptor:
   bLength                18
   bDescriptorType         1
   bcdUSB               1.10
   bDeviceClass            0 (Defined at Interface level)
   bDeviceSubClass         0
   bDeviceProtocol         0
   bMaxPacketSize0         8
   idVendor           0x0463 MGE UPS Systems
   idProduct          0xffff UPS
   bcdDevice            0.01
   iManufacturer           1
   iProduct                2
   iSerial                 0
   bNumConfigurations      1
   Configuration Descriptor:
     bLength                 9
     bDescriptorType         2
     wTotalLength           34
     bNumInterfaces          1
     bConfigurationValue     1
     iConfiguration          0
     bmAttributes         0xa0
       (Bus Powered)
       Remote Wakeup
     MaxPower               20mA
     Interface Descriptor:
       bLength                 9
       bDescriptorType         4
       bInterfaceNumber        0
       bAlternateSetting       0
       bNumEndpoints           1
       bInterfaceClass         3 Human Interface Device
       bInterfaceSubClass      0 No Subclass
       bInterfaceProtocol      0 None
       iInterface              0
         HID Device Descriptor:
           bLength                 9
           bDescriptorType        33
           bcdHID               1.10
           bCountryCode           33 US
           bNumDescriptors         1
           bDescriptorType        34 Report
           wDescriptorLength     549
           Warning: incomplete report descriptor
           Report Descriptor: (length is 9)
             Item(Main  ): (null), data=none
             Item(Main  ): (null), data=none
             Item(Main  ): (null), data=none
             Item(Main  ): (null), data=none
             Item(Main  ): (null), data=none
             Item(Main  ): (null), data=none
             Item(Main  ): (null), data=none
             Item(Main  ): (null), data=none
             Item(Main  ): (null), data=none
       Endpoint Descriptor:
         bLength                 7
         bDescriptorType         5
         bEndpointAddress     0x81  EP 1 IN
         bmAttributes            3
           Transfer Type            Interrupt
           Synch Type               None
           Usage Type               Data
         wMaxPacketSize     0x0008  1x 8 bytes
         bInterval              20
Device Status:     0x0001
   Self Powered

>
> If not (lsusb returns "Report Descriptors:" / "** UNAVAILABLE **"), it seems like the two options are to upgrade the kernel (which I understand is an issue),

unfortunately it is. If mandatory I guess I can do some tricks with cron 
to rollback a known good situation but given that I have no idea what 
failed during the previous attempt ( nothing got logged -- I suspect a 
kernel panic although I have no idea why would this happen ) I'd prefer 
to avoid, if possible.


>   or try to roll back the userspace tools to match what was current when the kernel was current.
>
I am afraid I did not understand this part...



Thanks for assistance

     M.