Nut upsuser - May 2010 - Support for Tripp Lite SmartOnline SU1000XLA?

Hi,

I'm running the latest stable nut (2.4.3).  It doesn't appear to provide
support for the Tripp Lite SmartOnline SU1000XLA.

[sups]
    driver = usbhid-ups
    port = auto
    vendorid = 09ae
    productid = 4004

4337# upsdrvctl start
Network UPS Tools - UPS driver controller 2.4.3
Network UPS Tools - Generic HID driver 0.34 (2.4.3)
USB communication driver 0.31
Using subdriver: TrippLite HID 0.4
libusb_get_report: could not claim interface 0: Device or resource busy
Got disconnected by another driver: Device or resource busy
Can't initialize data from HID UPS
Driver failed to start (exit status=1)

I did an 'fuser -m -v /dev/usb/hiddev0' just prior, and the file was
unused by any other process, so the error report is a little odd.

(Another oddity is that the file _was_ earlier claimed by encfs, when I
had an encrypted file system mounted, where no USB was involved at all.
Don't understand that.  I unmounted that before running upsdrvctl.)

I'm running Debian Lenny amd64, FWIW.

I don't have a serial port on the computer I'm using, so to make this
work I need to use USB.  Any chance this unit will be supported soon?

Best regards,

Ron

Kernel version 2.6.32.11, btw.

-Ron-

2010-05-09_20:45:42-0400 Ron Peterson <rpeterso at
mtholyoke.edu>:
> Hi,
> 
> I'm running the latest stable nut (2.4.3).  It doesn't appear to
provide
> support for the Tripp Lite SmartOnline SU1000XLA.
> 
> [sups]
>     driver = usbhid-ups
>     port = auto
>     vendorid = 09ae
>     productid = 4004
> 
> 4337# upsdrvctl start
> Network UPS Tools - UPS driver controller 2.4.3
> Network UPS Tools - Generic HID driver 0.34 (2.4.3)
> USB communication driver 0.31
> Using subdriver: TrippLite HID 0.4
> libusb_get_report: could not claim interface 0: Device or resource busy
> Got disconnected by another driver: Device or resource busy
> Can't initialize data from HID UPS
> Driver failed to start (exit status=1)
> 
> I did an 'fuser -m -v /dev/usb/hiddev0' just prior, and the file
was
> unused by any other process, so the error report is a little odd.
> 
> (Another oddity is that the file _was_ earlier claimed by encfs, when I
> had an encrypted file system mounted, where no USB was involved at all.
> Don't understand that.  I unmounted that before running upsdrvctl.)
> 
> I'm running Debian Lenny amd64, FWIW.
> 
> I don't have a serial port on the computer I'm using, so to make
this
> work I need to use USB.  Any chance this unit will be supported soon?
> 
> Best regards,
> 
> Ron
> 
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

On Sun, May 9, 2010 at 8:45 PM, Ron Peterson <rpeterso at mtholyoke.edu>
wrote:
> Hi,
>
> I'm running the latest stable nut (2.4.3). ?It doesn't appear to
provide
> support for the Tripp Lite SmartOnline SU1000XLA.
>
> [sups]
> ? ?driver = usbhid-ups
> ? ?port = auto
> ? ?vendorid = 09ae
> ? ?productid = 4004
>
> 4337# upsdrvctl start
> Network UPS Tools - UPS driver controller 2.4.3
> Network UPS Tools - Generic HID driver 0.34 (2.4.3)
> USB communication driver 0.31
> Using subdriver: TrippLite HID 0.4
> libusb_get_report: could not claim interface 0: Device or resource busy
> Got disconnected by another driver: Device or resource busy
> Can't initialize data from HID UPS
> Driver failed to start (exit status=1)
>
> I did an 'fuser -m -v /dev/usb/hiddev0' just prior, and the file
was
> unused by any other process, so the error report is a little odd.
Unfortunately, USB devices are not easily represented in the standard
Unix way where one physical device maps to one /dev node. The first
Linux hiddev driver couldn't cope with the complexity of the USB HID
reports coming in from UPSes (and the hiddev API is Linux-specific),
so NUT uses libusb directly (which uses /dev/bus/usb nodes instead of
/dev/usb/hiddev*).
> (Another oddity is that the file _was_ earlier claimed by encfs, when I
> had an encrypted file system mounted, where no USB was involved at all.
> Don't understand that. ?I unmounted that before running upsdrvctl.)
>
> I'm running Debian Lenny amd64, FWIW.
>
> I don't have a serial port on the computer I'm using, so to make
this
> work I need to use USB. ?Any chance this unit will be supported soon?
We have a couple of outstanding email threads about apparently
spurious "Device or resource busy" messages, but to my knowledge, none
of the NUT developers own a device which is exhibiting this problem.

http://thread.gmane.org/gmane.comp.monitoring.nut.user/5541

http://article.gmane.org/gmane.comp.monitoring.nut.devel/4771 (might
not be same root cause)

-- 
- Charles Lepple

On May 9, 2010, at 8:45 PM, Ron Peterson wrote:
> Network UPS Tools - UPS driver controller 2.4.3
> Network UPS Tools - Generic HID driver 0.34 (2.4.3)
> USB communication driver 0.31
> Using subdriver: TrippLite HID 0.4
> libusb_get_report: could not claim interface 0: Device or resource  
> busy
> Got disconnected by another driver: Device or resource busy
> Can't initialize data from HID UPS
> Driver failed to start (exit status=1)
Ron,

it sounds like the error on the libusb_get_report line can be avoided  
with the following patch:

http://boxster.ghz.cc/projects/nut/changeset/2407?format=diff&new=2407

That error is subtly different from the error that James is seeing  
("USB problems" thread) earlier on in the driver startup sequence,  
relating to permissions.

Have you rebuilt a .deb from source before? If not, I can walk you  
through some of the steps.

You might also want to file a bug with Debian, since this seems to be  
affecting a number of people.

-- 
Charles Lepple