2012/2/13 Zach La Celle <[email protected]>: > On 02/07/2012 10:58 AM, Zach La Celle wrote: >> On 02/07/2012 10:41 AM, Arnaud Quette wrote: >>> >>> that's what I was suspecting. >>> >>> I've never seen that one before, though! >>> >>> a driver debug output, Ie: >>> $ /lib/nut/usbhid-ups -DDDDD -a rack1ups >>> >>> please, compress the result or sent in a reference to the file. >>> >>> I would also be interested in a 2nd run, calling "export USB_DEBUG=3", >>> before starting usbhid-ups. >>> we should get some visibility from libusb. >>> >>> cheers, >>> Arnaud >> >> I've put up two files: one without USB_DEBUG=3, and one with USB_DEBUG=3. >> >> Without: >> http://db.tt/55mUqzJA >> >> With: >> http://db.tt/Rcf2Phv6 >> >> I hope this helps! >> >> -Zach >> >> _______________________________________________ >> Nut-upsuser mailing list >> [email protected] >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser > > I'm back in the office, and can collect more information for you if it > will help. Is there anything else you need?
quite frankly, I still have no clue on what could be happening. have you tried on another USB port? is there anything else cabled on the same USB bus? would you be able to test this device on another system, with different OS? cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
