On Monday, 6 June 2022 12:15:10 EDT Dave Williams wrote:
> IMHO adding to the logging to suggest pollonly would be a good start.
> I wouldnt advocate changing on the fly - thats likely to lead to
> instability or confusion.
>
> On my CP900EPFCLCD I need to run pollonly albeit when connected to
Hi,
Thanks for the followup.
A hint about pollonly option in the logs would be very helpful.
Automatically changing the mode could be hard to get right and may not
be the proper thing to do in some situations. It would also make
troubleshooting harder if the driver uses options contrary to what
IMHO adding to the logging to suggest pollonly would be a good start.
I wouldnt advocate changing on the fly - thats likely to lead to
instability or confusion.
On my CP900EPFCLCD I need to run pollonly albeit when connected to old
USB 1.5 ports. I thought it was the port not the UPS that was
According to issues discussed over the past year or so on github, seems so
- that at least some models and/or OSes and/or chipsets have a problem with
libusb interrupt mode; more often failing during device discovery than
after some successful uptime.
I don't think there was reliable statistics
Ubuntu 22.04
NUT 2.7.4
CYberPower CP1500AVRLCDa using usbhid-ups
Hello,
The above combination works well for a few minutes -- including shutdown on
pulling power or on upsmon -c fsd, notifications etc. Until the driver
starts reporting error in libusb_get_string, kernel messages on
