Hi<br><br><div class="gmail_quote">2011/6/7 <span dir="ltr"><<a href="mailto:nut@johnea.net">nut@johnea.net</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Hello,<br>
<br>
I've had this same model CyberPower connected to a linux server and a<br>
freebsd server.<br>
<br>
[root@sensor003 menon]# lsusb<br>
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
Bus 003 Device 004: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS<br>
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br>
<br>
When the nut daemons start attempting to monitor the UPS, the device<br>
begins a cycle of disconnecting and reconnecting every 20sec.<br>
<br>
Running 'usbhid-ups -a nexups' manually, yields permissions issues:<br>
<br>
[root@sensor003 menon]# usbhid-ups -a nexups<br>
Network UPS Tools - Generic HID driver 0.34 (2.4.3)<br>
USB communication driver 0.31<br>
Using subdriver: CyberPower HID 0.3<br>
libusb_get_report: could not claim interface 0: Device or resource busy<br>
Got disconnected by another driver: Device or resource busy<br></blockquote><div><br>this msg is typical of multiple driver instances running, and fighting to get the hand on the device.<br>you can confirm this with an 'ls', and fix it by stopping / killing everything, then starting the driver using upsdrvctl.<br>
 </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Can't initialize data from HID UPS<br>
<br>
[root@sensor003 network-ups-tools]# ls -l /dev/bus/usb/003/<br>
total 0<br>
crw-rw-r-- 1 root root 189, 256 Jun  7 10:55 001<br>
crw-rw---- 1 root nut  189, 270 Jun  7 11:58 015<br>
<br>
There is a udev rule to set permissions on this device:<br>
<br>
[root@sensor003 menon]# cat /etc/udev/rules.d/91-local.rules<br>
# set permissions for CyberPower UPS -jea 2010-06-02<br>
SUBSYSTEM=="usb", ATTRS{idVendor}=="0764", GROUP="nut", MODE="0660"<br></blockquote><div><br>there should already be a set of rules generated by NUT and named 52-nut-usbups.rules and located in /lib/udev/rules.d<br>
 </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
The group and permissions show that this has been applied.<br>
<br>
I'm not a linux-usb developer, and I don't quite get the depth of this,<br>
but it seems the system hid driver is attaching to this device as it<br>
enumerates, preventing the nut driver from attaching.<br>
<br>
This device was finally attached before (nut 2.4) after applying the<br>
patch mentioned here:<br>
<br>
<a href="http://www.mail-archive.com/nut-upsuser@lists.alioth.debian.org/msg05550.html" target="_blank">http://www.mail-archive.com/nut-upsuser@lists.alioth.debian.org/msg05550.html</a><br>
<br>
This corrected for this low speed device not providing packets greater<br>
than 8 bytes in length.<br>
<br>
This patch didn't apply directly to the nut 2.6 source.<br>
<br>
Can anyone confirm if this 8byte low speed device buffer size limit is<br>
applied in 2.6?<br>
</blockquote></div><br>2.6.1 has a smarter fix for this, since having a hard-coded 8 bytes length caused regressions on some other devices.<br><br>cheers<br>Arnaud<br>-- <br>Linux / Unix Expert R&D - Eaton - <a href="http://powerquality.eaton.com" target="_blank">http://powerquality.eaton.com</a><br>
Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/" target="_blank">http://www.networkupstools.org/</a><br>Debian Developer - <a href="http://www.debian.org" target="_blank">http://www.debian.org</a><br>
Free Software Developer - <a href="http://arnaud.quette.free.fr/" target="_blank">http://arnaud.quette.free.fr/</a><br><br>