[Nut-upsdev] tripplite smart2000rmxl2u product id 3014

[Arjen de Korte]

Citeren teh at phy.anl.gov:

> Adding the -x productid=3014 as you suggested did not work.  Here's what
> the driver dumps out.
>
> [root at fugue ups]# bin/usbhid-ups -a ups01 -DD -x productid=3014
> Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.2.2)
>
> debug level is '2'
> upsdrv_initups...
>
> ...<snip>...
>
> Checking device (09AE/3014) (002/002)
> - VendorID: 09ae
> - ProductID: 3014
> - Manufacturer: unknown
> - Product: unknown
> - Serial Number: unknown
> - Bus: 002
> Trying to match device
> Device matches
> failed to claim USB device, trying 2 more time(s)...
> detaching kernel driver from USB device...
> failed to detach kernel driver from USB device...
> trying again to claim USB device...
> failed to claim USB device, trying 1 more time(s)...
> detaching kernel driver from USB device...
> failed to detach kernel driver from USB device...
> trying again to claim USB device...
> failed to claim USB device, trying 0 more time(s)...
> detaching kernel driver from USB device...
> failed to detach kernel driver from USB device...
> trying again to claim USB device...
> Unable to get HID descriptor (error sending control message: Operation not
> permitted)
> HID descriptor length 1145
> Unable to get Report descriptor: Operation not permitted
> No appropriate HID device found
> No matching HID UPS found
> [root at fugue ups]#
>
> Why does it fail to claim the device?  Is another driver or process own
> it?  If so, which?

Add '-u root' to the startup commandline to rule out a permissions  
problem. Chances are that you need to setup hotplug/udev to allow the  
driver access to the UPS when it drops privileges. Since this is a new  
VID:PID combination, this won't work as it is. Running the driver as  
root successfully should confirm this.

Best regards, Arjen
-- 
Please keep list traffic on the list