[Nut-upsuser] Tripp lite SMART1000LCD
k_dal2 at hotmail.com
Sun Jan 27 04:55:15 UTC 2008
I know the port should work as I have used it for other devices
so I reconnected the ups and used a usb hub in between and
I got it recognized in the kernel but the nut driver did not seem
to attach properly:
usb 4-2.1: new low speed USB device using ehci_hcd and address 100
usb 4-2.1: configuration #1 chosen from 1 choice
hiddev0: USB HID v1.10 Device [Tripp Lite TRIPP LITE UPS ] on usb-0000:00:10.3-2.1
Bus 004 Device 100: ID 09ae:2007 Tripp Lite
Bus 004 Device 099: ID 05e3:0605 Genesys Logic, Inc. USB 2.0 Hub [ednet]
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 002: ID 0430:0100 Sun Microsystems, Inc. 3-button Mouse
I followed the instructions in the INSTALL file but I may have missed something:
# /usr/local/ups/bin/upsdrvctl start
Network UPS Tools - UPS driver controller 2.2.1
Network UPS Tools: 0.29 USB communication driver - core 0.32 (2.2.1)
Using subdriver: TrippLite HID 0.2 (experimental)
Startup timer elapsed, continuing...
Is this an error ? Shouldn't the driver usbhid-ups be referenced here
when my conf file is:
# cat /usr/local/ups/etc/ups.conf
driver = usbhid-ups
port = auto
desc = "Tripp Lite SMART1000LCD USB"
Starting the daemon gives:
Network UPS Tools upsd 2.2.1
listening on 0.0.0.0 port 3493
Can't connect to UPS [SMART1000LCD] (usbhid-ups-SMART1000LCD): No such file or directory
> Date: Sat, 26 Jan 2008 16:16:32 -0500
> From: clepple at gmail.com
> To: k_dal2 at hotmail.com
> Subject: Re: [Nut-upsuser] Tripp lite SMART1000LCD
> CC: nut-upsuser at lists.alioth.debian.org
> On Jan 26, 2008 2:53 PM, Karl Dalen <k_dal2 at hotmail.com> wrote:
> > Charles,
> > Thanks for your information.
> > I've just compiled the latest NUT version nut-2.2.1.
> > When I plug in the USB cable from the ups it looks like
> > the device does not get recognized at all in the system.
> > Shouldn't there be some log info in /var/syslog or dmesg
> > when a device is plugged in? There was nothing there.
> > I'm running Linux kernel, 2.6.17 (mandriva 2007)
> Yes. You should see some messages, and it should be listed in the
> output of 'lsusb'.
> Note that some versions of Linux are changing permissions of certain
> devices when they are plugged in, so if in doubt, be sure to run lsusb
> as root. But you should still see some messages in dmesg.
> > # /usr/local/ups/bin/upsdrvctl start
> > Network UPS Tools - UPS driver controller 2.2.1
> > Network UPS Tools: 0.29 USB communication driver - core 0.32 (2.2.1)
> > No matching HID UPS found
> > Driver failed to start (exit status=1)
> > Am I missing some usb utility needed for hid devices to work in Linux ?
> No userspace utilities or packages, and the HID kernel module actually
> gets detached by most of the NUT drivers anyway. Also, that takes
> effect after the kernel has been able to identify the VID/PID as shown
> in lsusub.
> > My usb keyboard and mouse do work.
> If you see no trace of the UPS in dmesg or lsusb, it sounds like
> either a cable problem, an issue with the USB port itself, or maybe
> the UPS needs to be "reset". Some UPSes do not support both the USB
> and serial ports being active at the same time, so they need to be
> powered down completely in between. (This may not apply if the
> SMART1000LCD doesn't have a serial port.)
> > % rpm -qa | grep usb
> > libusb0.1_4-0.1.12-2mdv2007.0
> > libusb0.1_4-static-devel-0.1.12-2mdv2007.0
> > usbutils-0.72-1mdk
> > libusb0.1_4-devel-0.1.12-2mdv2007.0
> > % lsusb
> > Bus 004 Device 001: ID 0000:0000
> > Bus 003 Device 002: ID 0430:0100 Sun Microsystems, Inc. 3-button Mouse
> > Bus 003 Device 001: ID 0000:0000
> > Bus 002 Device 004: ID 0430:0005 Sun Microsystems, Inc. Type 6 Keyboard
> > Bus 002 Device 001: ID 0000:0000
> > Bus 001 Device 001: ID 0000:0000
> > ups.conf
> > -----------
> > [SMART1000LCD]
> > driver = usbhid-ups
> > port = auto
> > desc = "Tripp Lite SMART1000LCD USB"
> > Any suggestions would be appreciated.
> > /Karl D
> > > Date: Fri, 25 Jan 2008 08:11:44 -0500
> > > From: clepple at gmail.com
> > > To: k_dal2 at hotmail.com
> > > Subject: Re: [Nut-upsuser] Tripp lite SMART1000LCD
> > > CC: nut-upsuser at lists.alioth.debian.org
> > >
> > > On Jan 24, 2008 3:08 PM, Karl Dalen <k_dal2 at hotmail.com> wrote:
> > > > This model is supposed to be fully HID PD class compliant.
> > > > Should I use the usbhid-ups or tripplite_usb driver ?
> > >
> > > usbhid-ups
> > >
> > > The code in the trunk looks like it should recognize both 0x2005 as
> > > well as 0x2007 for the USB product ID. Which version of NUT are you
> > > using?
> > >
> > > > HID descriptor:
> > > > Descriptor Length:9, Type:33
> > > > Hid Class spec release: 110
> > > > Country Code: 0 (FYI 33 = US)
> > > > Number of class descriptors: 1
> > > > Class descriptor type: 34
> > > > Total size of Report Descriptor: 2049
> > > >
> > > > Don't know what I was doing wrong in reading the
> > > > HID descriptor (using another application) but
> > > > I got the length 2049, which does not match the true
> > > > length of the report descriptor (601) I get when reading it.
> > >
> > > There are two ways of getting the report descriptor: one is to fetch
> > > it explicitly, and the other is to look for it embedded after the
> > > interface descriptor. The code used by usbhid-ups (drivers/libusb.c)
> > > checks both methods, and picks the one that looks most likely. (You
> > > can see this in the debug messages if you pass several '-D' flags on
> > > the command line.)
> > >
> > > --
> > > - Charles Lepple
> > ________________________________
> > Express yourself instantly with MSN Messenger! MSN Messenger
> > _______________________________________________
> > Nut-upsuser mailing list
> > Nut-upsuser at lists.alioth.debian.org
> > http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
> - Charles Lepple
Express yourself instantly with MSN Messenger! Download today it's FREE!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Nut-upsuser