[Nut-upsuser] libusb_get_interrupt: error reading from interrupt endpoint /dev/ugen0.1

John Bayly freebsd.ports at tipstrade.net
Thu Mar 24 17:31:13 UTC 2011

On 24/03/2011 13:01, Charles Lepple wrote:
>>> How do things work if you add the "pollonly" option to the
>>> configuration file?
>> I've just tried this, and the USB debug messages stopped on restart.
>> Really appreciate the help.
> Be sure that the measured values shown in upsc are updating as well.
> With the "pollonly" flag, they should be explicitly requested via
> control messages, and you should see error messages if those control
> messages fail, but that's making a lot of assumptions about the USB
> stack.
Thanks for pointing that out. Just did some timing and found that with 
and without the "pollonly" flag set, the ups.load value was changing 
when applying and removing additional load. I did however notice that 
the time taken to register the load change could be between 0 and 20 
seconds, thought this could be down to the UPS itself, and not the drivers.
I've seen no errors being reported, so I'll cross my fingers!

More information about the Nut-upsuser mailing list