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