[Nut-upsuser] Eaton PW5110 + nut-2.4.1 + OpenBSD

Dimitris Mandalidis mandas at mandas.org
Sat Feb 20 08:25:57 UTC 2010


> I forgot to mention that the above output was from the latest repository
> revision (last Sunday). Howver, I updated to the latest revision but it
> didn't work either.
> 
> root at fox ~/nut-2.4.1 # USB_DEBUG=3 drivers/bcmxcp_usb -DDD -a myups
> Network UPS Tools - BCMXCP UPS driver 0.23 (2.4.1)
> USB communication subdriver 0.18
>    0.000000     debug level is '3'
> usb_set_debug: Setting debugging level to 3 (on)
> usb_os_find_busses: Found /dev/usb0
> usb_os_find_busses: Found /dev/usb1
> usb_os_find_busses: Found /dev/usb2
> usb_os_find_devices: Found /dev/ugen0 on /dev/usb2
> usb_control_msg: 128 6 512 0 0xcfbdcdc8 8 1000
> usb_control_msg: 128 6 512 0 0x82de0380 34 1000
> skipped 1 class/vendor specific interface descriptors
>    0.037629     device /dev/ugen0 opened successfully
> usb_control_msg: 0 7 772 0 0xcfbdcce0 4 1000
>    0.042291     entering get_answer(31)
> USB error: error reading from interrupt endpoint /dev/ugen0.01: Resource
> temporarily unavailable
> usb_control_msg: 0 7 772 0 0xcfbdcce0 4 1000
>    0.047288     entering get_answer(31)
> USB error: error reading from interrupt endpoint /dev/ugen0.01: Resource
> temporarily unavailable
> usb_control_msg: 0 7 772 0 0xcfbdcce0 4 1000
>    0.051286     entering get_answer(31)
> USB error: error reading from interrupt endpoint /dev/ugen0.01: Resource
> temporarily unavailable
> usb_control_msg: 0 7 772 0 0xcfbdcce0 4 1000
>    0.055285     entering get_answer(31)
> USB error: error reading from interrupt endpoint /dev/ugen0.01: Resource
> temporarily unavailable
> usb_control_msg: 0 7 772 0 0xcfbdcce0 4 1000
>    0.059284     entering get_answer(31)
> USB error: error reading from interrupt endpoint /dev/ugen0.01: Resource
> temporarily unavailable
>    0.061284     Communications with UPS lost: Error executing command
>    0.061734     Could not communicate with the ups: Resource temporarily
> unavailable
>    0.062152     CLOSING
> 
> usb_os_close: closing endpoint 5

I still haven't solved this, I also tried today with 2.4.2 with no luck.

-----------------------------------------------
# USB_DEBUG=3 drivers/bcmxcp_usb -DDD -a myups           
Network UPS Tools - BCMXCP UPS driver 0.23 (2.4.2)
USB communication subdriver 0.18
   0.000000     debug level is '3'
usb_set_debug: Setting debugging level to 3 (on)
usb_os_find_busses: Found /dev/usb0
usb_os_find_busses: Found /dev/usb1
usb_os_find_busses: Found /dev/usb2
usb_os_find_devices: Found /dev/ugen0 on /dev/usb2
usb_control_msg: 128 6 512 0 0xcfbe8b48 8 1000
usb_control_msg: 128 6 512 0 0x8addd100 34 1000
skipped 1 class/vendor specific interface descriptors
   0.035250     device /dev/ugen0 opened successfully
usb_control_msg: 0 7 772 0 0xcfbe8a60 4 1000
   0.039919     entering get_answer(31)
USB error: error reading from interrupt endpoint /dev/ugen0.01: Resource
temporarily unavailable
usb_control_msg: 0 7 772 0 0xcfbe8a60 4 1000
   0.044918     entering get_answer(31)
USB error: error reading from interrupt endpoint /dev/ugen0.01: Resource
temporarily unavailable
usb_control_msg: 0 7 772 0 0xcfbe8a60 4 1000
   0.048915     entering get_answer(31)
USB error: error reading from interrupt endpoint /dev/ugen0.01: Resource
temporarily unavailable
usb_control_msg: 0 7 772 0 0xcfbe8a60 4 1000
   0.052916     entering get_answer(31)
USB error: error reading from interrupt endpoint /dev/ugen0.01: Resource
temporarily unavailable
usb_control_msg: 0 7 772 0 0xcfbe8a60 4 1000
   0.056915     entering get_answer(31)
USB error: error reading from interrupt endpoint /dev/ugen0.01: Resource
temporarily unavailable
   0.058914     Communications with UPS lost: Error executing command
   0.059347     Could not communicate with the ups: Resource temporarily
unavailable
   0.059754     CLOSING

usb_os_close: closing endpoint 5
---------------------------------------------

Can I assume that this is driver problem or there are other things that I
could check first.

Thanks
D.



More information about the Nut-upsuser mailing list