On Sun, 23 Nov 2008 16:39:11 -0000, Charles Lepple <[EMAIL PROTECTED]> wrote:
> On Sun, Nov 23, 2008 at 5:01 AM, Barb Smith <[EMAIL PROTECTED]> > wrote: >> On Sun, 23 Nov 2008 15:03:53 -0000, Charles Lepple <[EMAIL PROTECTED]> >> wrote: >> >>> On Sat, Nov 22, 2008 at 9:37 PM, Barb Smith <[EMAIL PROTECTED]> >>> wrote: >>>> >>>> >>>> On Sun, 23 Nov 2008 00:49:32 -0000, Charles Lepple <[EMAIL PROTECTED]> >>>> wrote: >>>> >>>>> On Sat, Nov 22, 2008 at 12:14 PM, Barb Smith <[EMAIL PROTECTED]> >>>>> wrote: >>>>> >>>>>> Bus 002 Device 003: ID 09ae:1007 Tripp Lite >>>>> >>>>> Aha, this says that Tripp Lite changed the USB ID of this device. >>>>> >>>>> The tripplite_usb driver only knows about product ID 0001, and 1007 >>>>> isn't one of the known IDs in usbhid-ups (as of v2.2.2). >>>>> >>>>> In our development version, there is an entry for 09ae:1007, but it >>>>> says "AVR750U". >>>>> >>>>> To try and see if this might work, please change the ups.conf entry >>>>> back to "driver = usbhid-ups", and add the line "productid = 1007". >>>>> >>>>> Then, start the driver as follows: >>>>> >>>>> /lib/nut/usbhid-ups -u root -a omni100 -D >>>>> >>>>> Let it run for a few minutes, then kill it with Ctrl-C. >>>>> >>>>> Please capture the log messages, and gzip them before sending to the >>>>> list. >>>>> >>>> >>>> I couldn't really find anything in dmesg or syslog so I put the output >>>> into >>>> a log file and I'm attaching it. >>> >>> The critical flag here is "-D" (capital D), to enable debug output to >>> the console (so nothing extra should go to syslog). >>> >>> I mentioned gzip since the output tends to be verbose. >>> >>> Here's the first few lines on an older APC setup: >>> >>> # /lib/nut/usbhid-ups -a apc -D >>> Network UPS Tools: 0.29 USB communication driver - core 0.32 (2.2.1-) >>> >>> debug level is '1' >>> upsdrv_initups... >>> Using subdriver: APC HID 0.92 >>> Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x01, >>> Offset: 0, Size: 8, Value: 1.000000 >>> Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: 0x02, >>> Offset: 0, Size: 8, Value: 2.000000 >>> ... >>> >> >> >> gentoo mystified # /lib/nut/usbhid-ups -a apc -D >> Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.2.2) >> >> Error: Section apc not found in ups.conf > > Sorry for the confusion - the name after "-a" must match the UPS name > in *your* ups.conf file, and I guess I was a little hasty with the > copy-and-paste. > > Assuming your ups.conf looks like this: > > ########## > > [omni1000] > driver = usbhid-ups > port = auto > desc = "Omni UPS" > > ########## > > Try this command line (still starting it as root): > > /lib/nut/usbhid-ups -u root -a omni1000 -D > > What I was trying to explain in the last email is that you should see > more than just the version string. With one "-D" on the command line, > it should say "debug level is '1'" and print out some more > information. > Kjell told me to change a udev rule and now I'm getting this: gentoo mystified # /etc/init.d/upsdrv start * Starting UPS drivers ... Network UPS Tools - UPS driver controller 2.2.2 Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.2.2) Using subdriver: TrippLite HID 0.2 (experimental) [ ok ] -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/ _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
