Hello all, Sorry for delay. I've been away for a while. Back to testing. I've tried regular version 2.6.5-1 and patched. Main thing is that both versions work until I reboot the OS, after that starting the nut fails with messages below. To make it run again I've to re-plug the usb cable. Hard-resetting the ups doesn't help either. Considering the fact to remotely monitor the devices it is quite inconvenient. Suppose there is I power fault and ups is drained out of power then the system won't come back online after power is restored. I've tried searching for a working way to model the "usb cable re-plug" on OS level with no luck. Any help would be appreciated.
Linux raspberrypi 3.2.27+ #160 PREEMPT Mon Sep 17 23:18:42 BST 2012 armv6l GNU/Linux *Version 2.6.5-1* USB communication subdriver 0.21 0.000000 debug level is '5' 0.008920 entering nutusb_open() 0.013091 device 004 opened successfully 0.015893 Can't claim POWERWARE USB interface: could not claim interface 0: Device or resource busy 0.018484 Can't reset POWERWARE USB endpoint: could not clear/halt ep 129: Device or resource busy 0.020807 device 004 opened successfully 0.021753 Can't claim POWERWARE USB interface: could not claim interface 0: Device or resource busy 0.022617 Can't reset POWERWARE USB endpoint: could not clear/halt ep 129: Device or resource busy 0.023750 device 004 opened successfully 0.024928 Can't claim POWERWARE USB interface: could not claim interface 0: Device or resource busy 0.026070 Can't reset POWERWARE USB endpoint: could not clear/halt ep 129: Device or resource busy 0.029099 device 004 opened successfully 0.029412 Can't claim POWERWARE USB interface: could not claim interface 0: Device or resource busy 0.029714 Can't reset POWERWARE USB endpoint: could not clear/halt ep 129: Device or resource busy 0.030193 send_to_all: SETINFO device.type "ups" 0.031387 send_to_all: SETINFO driver.version "2.6.4" 0.031855 send_to_all: SETINFO driver.version.internal "0.26" 0.032720 send_to_all: SETINFO driver.name "bcmxcp_usb" 0.033757 send_read_command: (4 bytes) => ab 01 31 23 0.034906 entering get_answer(31) 0.035409 get_answer: (0 bytes) => 0.036298 send_read_command: (4 bytes) => ab 01 31 23 0.039485 entering get_answer(31) 0.040038 get_answer: (0 bytes) => 0.040289 send_read_command: (4 bytes) => ab 01 31 23 0.041718 entering get_answer(31) 0.042514 get_answer: (0 bytes) => 0.043435 send_read_command: (4 bytes) => ab 01 31 23 0.045095 entering get_answer(31) 0.045885 get_answer: (0 bytes) => 0.046158 send_read_command: (4 bytes) => ab 01 31 23 0.050026 entering get_answer(31) 0.050552 get_answer: (0 bytes) => 0.050785 Communications with UPS lost: Error executing command 0.051043 Could not communicate with the ups: Device or resource busy 0.051271 CLOSING *Patched version* 2.225863 => usb_interrupt_read -16 2.226680 => packet_loop (0, 0) 2.227534 => bytes_read (0) 2.227857 => usb_interrupt_read -16 2.228667 => packet_loop (0, 0) 2.229701 => bytes_read (0) 2.230028 => usb_interrupt_read -16 2.230809 => packet_loop (0, 0) 2.233160 => bytes_read (0) 2.234230 => usb_interrupt_read -16 2.234546 => packet_loop (0, 0) 2.234763 => bytes_read (0) 2.235573 => usb_interrupt_read -16 2.236373 => packet_loop (0, 0) 2.237285 => bytes_read (0) 2.237620 => usb_interrupt_read -16 2.238418 => packet_loop (0, 0) 2.239706 => bytes_read (0) On Fri, Sep 21, 2012 at 4:25 PM, Arnaud Quette <aquette....@gmail.com>wrote: > > > 2012/9/21 Eugene Jurchenko <jevgeni...@gmail.com> > >> Massimo Gais <simosagi9 <at> gmail.com> writes: >> >> > >> > On Sun, Aug 12, 2012 at 5:11 AM, Greg Vickers <daehenoc <at> >> iinet.net.au> >> wrote: >> > > On 11/08/12 06:58, Arnaud Quette wrote: >> > > >> > > Hi Massimo and Greg, >> > > >> > > @Greg: if you yet returned your unit, you now have a solution ;) >> > > >> > > I have not yet gotten rid of it, so thank you very much! It's a case >> of >> > > download, extract, apply patch, and compile on my RPi, correct? >> > > >> > > thanks for the effort for the patch! >> > > >> > > welcome ;) >> > > >> > >> > Hello Greg, >> > yes you can compile it directly on the RPI. See anyway that if you >> > have the old deb package installed and you want to replace only the >> > recompiled driver, you may have some mismatch with the >> > pidpath/statepath directories (/var/state/ups vs /var/run/nut). I >> > tried to do it in a clean way by making a debian package on the RPi, >> > but it was requiring to install all the documentation tools, and I did >> > not have enough SD disk space for that. >> > >> > Cheers, >> > Massimo >> > >> >> Greetings, >> > > Hi > > thanks for the heads up, I just realized that I've not committed this > patch! > > Glad that I've found some info about the issue. I have same problem with >> the >> same UPS on RPi. Unfortunately link for the patch is no longer valid. >> Could you >> send it one more time or the compiled package for RPi would be more >> appreciable. >> Thank you >> > > you can find the thread, with compilation instructions and the patch, here: > > http://www.mail-archive.com/nut-upsuser@lists.alioth.debian.org/msg07278.html > > I'm waiting for your feedback + 1 (namely Rich Wrenn) to commit this. > > cheers, > Arno >
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
