Hi James,

I've worked extensively on getting a similar CyberPower UPS (same IDs) to play
well with nut.

The conclusion I ultimately came to is that if this UPS is not connected to by
it's driver within about 20sec, it drops off the USB bus and re-enumerates. This
causes an endless cycle of the UPS attaching and detaching. In arch, I was able
to make it work by placing the nut daemon at the beginning of the rc scripts,
before everything else. This caused it to be attached to before it dropped from
the bus. Once it was attached, everything worked.

IMHO, If you can, return it and get a different unit.

johnea

On 2011-09-30 20:43, James wrote:
> I have a ups that doesn't always (sometimes it does) load NUT right.
> 
> I use Gentoo:
> *  sys-power/nut
>       Latest version available: 2.6.0-r1
>       Latest version installed: 2.6.0-r1
>       Size of files: 1,663 kB
>       Homepage:      http://www.networkupstools.org/
>       Description:   Network-UPS Tools
>       License:       GPL-2
> 
> The kernel is 3.0.4.
> 
> Here is the dmesg output:
> 
> generic-usb 0003:0764:0501.0005: claimed by neither input, hiddev nor hidraw
> usb 2-3: USB disconnect, device number 5
> usb 2-3: new low speed USB device number 6 using ohci_hcd
> usb 2-3: New USB device found, idVendor=0764, idProduct=0501
> usb 2-3: New USB device strings: Mfr=3, Product=1, SerialNumber=0
> usb 2-3: Product: CP550HG
> usb 2-3: Manufacturer: CPS
> 
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 
> ret
> -110
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 9 ret 
> -6
> 2
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 376 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 9 ret 
> -6
> 2
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 376 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 9 ret 
> -6
> 2
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 376 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 9 ret 
> -6
> 2
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 376 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 9 ret 
> -6
> 2
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 376 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 9 ret 
> -6
> 2
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 376 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 9 ret 
> -6
> 2
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 376 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 9 ret 
> -6
> 2
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 376 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 9 ret 
> -6
> 2
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 376 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 128 rq 6 len 255 
> ret
> -62
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 9 ret 
> -6
> 2
> usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 129 rq 6 len 376 
> ret
> -62
> 
> 
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

_______________________________________________
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Reply via email to