On Fri, Feb 27, 2009 at 1:37 PM, KP Kirchdoerfer <kap...@bering-uclibc.de> wrote: > Am Freitag, 27. Februar 2009 19:34:11 schrieb Kjell Claesson: >> fredag 27 februari 2009 19:09:27 skrev KP Kirchdoerfer: >> > Am Freitag, 27. Februar 2009 18:54:00 schrieben Sie: >> > > fredag 27 februari 2009 18:48:58 skrev KP Kirchdoerfer: >> >> 8<------------------------snip------------------------------- >> >> > If you ask me to run upsdrvctl with -D I'll don't geht more information >> > than before: >> > /sbin/upsdrvctl -D start compaq-ups >> > Network UPS Tools - UPS driver controller 2.2.2 >> > Starting UPS: compaq-ups >> > Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.2.2) >> > >> > No matching HID UPS found >> > Driver failed to start (exit status=1) >> >> You can rise the debug level by adding D. So try -DDD . >> I have not worked with the usbups_hid driver but it should give >> some more info. > > Yep; I tried that also, but didn't got more output....
There's a subtle difference here - adding '-D' to the upsdrvctl command line increases the verbosity of upsdrvctl, not the driver that it starts. For testing, you would want something like: /lib/nut/usbhid-ups -D -a compaq-ups As Kjell mentioned, the nut-upsdev list is a better place for usbsnoop logs and whatnot, if we can't figure it out with the basic debug output. -- - Charles Lepple _______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser