[please use reply-all to include the list, as the list does not override the Reply-To header.]
On Jun 7, 2015, at 5:02 PM, Greg Hersch <[email protected]> wrote: > Here is the driver debug log. If I just let it run, it pops up with > libusb_get_string_invalid argument over and over again, mixed in the > debug output. seems to be several issues reported in the log, but they > arent easily interpreted. Does the libusb_get_string error occur only every 30 seconds or so? > 1.164089 Path: UPS.ffff0015.[1].ffff00c5, Type: Feature, > ReportID: 0x9b, Offset: 0, Size: 16, Value: 3 > 1.172696 libusb_get_report: Value too large for defined data type > 1.172928 Can't retrieve Report c2: Value too large for defined data type The entries with hex numbers in the path aren't important - the driver tries to dump them once at startup, then does not refer to them again. > 3.402389 libusb_get_string: Invalid argument I think this is from trying to retrieve the value corresponding to "device.part" - which should also only be attempted once at startup. Try the attached patch? Also, I would be interested in the output of "lsusb -vvv -d 09ae:" for your UPS. -- Charles Lepple clepple@gmail
tripplite_device_path.patch
Description: Binary data
_______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
