[Nut-upsuser] Support for Tripp Lite SmartOnline SU1000XLA?
Charles Lepple
clepple at gmail.com
Mon May 10 12:51:06 UTC 2010
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
More information about the Nut-upsuser
mailing list