<div>Hello all,</div><div><br></div><div> 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. </div>
<div><br></div><div><div>Linux raspberrypi 3.2.27+ #160 PREEMPT Mon Sep 17 23:18:42 BST 2012 armv6l GNU/Linux</div></div><div><br></div><div><b>Version 2.6.5-1</b></div><div>USB communication subdriver 0.21</div><div> 0.000000 debug level is '5'</div>
<div> 0.008920 entering nutusb_open()</div><div> 0.013091 device 004 opened successfully</div><div> 0.015893 Can't claim POWERWARE USB interface: could not claim interface 0: Device or resource busy</div>
<div> 0.018484 Can't reset POWERWARE USB endpoint: could not clear/halt ep 129: Device or resource busy</div><div> 0.020807 device 004 opened successfully</div><div> 0.021753 Can't claim POWERWARE USB interface: could not claim interface 0: Device or resource busy</div>
<div> 0.022617 Can't reset POWERWARE USB endpoint: could not clear/halt ep 129: Device or resource busy</div><div> 0.023750 device 004 opened successfully</div><div> 0.024928 Can't claim POWERWARE USB interface: could not claim interface 0: Device or resource busy</div>
<div> 0.026070 Can't reset POWERWARE USB endpoint: could not clear/halt ep 129: Device or resource busy</div><div> 0.029099 device 004 opened successfully</div><div> 0.029412 Can't claim POWERWARE USB interface: could not claim interface 0: Device or resource busy</div>
<div> 0.029714 Can't reset POWERWARE USB endpoint: could not clear/halt ep 129: Device or resource busy</div><div> 0.030193 send_to_all: SETINFO device.type "ups"</div><div> 0.031387 send_to_all: SETINFO driver.version "2.6.4"</div>
<div> 0.031855 send_to_all: SETINFO driver.version.internal "0.26"</div><div> 0.032720 send_to_all: SETINFO <a href="http://driver.name">driver.name</a> "bcmxcp_usb"</div><div> 0.033757 send_read_command: (4 bytes) => ab 01 31 23</div>
<div> 0.034906 entering get_answer(31)</div><div> 0.035409 get_answer: (0 bytes) =></div><div> 0.036298 send_read_command: (4 bytes) => ab 01 31 23</div><div> 0.039485 entering get_answer(31)</div>
<div> 0.040038 get_answer: (0 bytes) =></div><div> 0.040289 send_read_command: (4 bytes) => ab 01 31 23</div><div> 0.041718 entering get_answer(31)</div><div> 0.042514 get_answer: (0 bytes) =></div>
<div> 0.043435 send_read_command: (4 bytes) => ab 01 31 23</div><div> 0.045095 entering get_answer(31)</div><div> 0.045885 get_answer: (0 bytes) =></div><div> 0.046158 send_read_command: (4 bytes) => ab 01 31 23</div>
<div> 0.050026 entering get_answer(31)</div><div> 0.050552 get_answer: (0 bytes) =></div><div> 0.050785 Communications with UPS lost: Error executing command</div><div> 0.051043 Could not communicate with the ups: Device or resource busy</div>
<div> 0.051271 CLOSING</div><div><br></div><div><b>Patched version</b></div><div>2.225863 => usb_interrupt_read -16</div><div> 2.226680 => packet_loop (0, 0)</div><div> 2.227534 => bytes_read (0)</div>
<div> 2.227857 => usb_interrupt_read -16</div><div> 2.228667 => packet_loop (0, 0)</div><div> 2.229701 => bytes_read (0)</div><div> 2.230028 => usb_interrupt_read -16</div><div> 2.230809 => packet_loop (0, 0)</div>
<div> 2.233160 => bytes_read (0)</div><div> 2.234230 => usb_interrupt_read -16</div><div> 2.234546 => packet_loop (0, 0)</div><div> 2.234763 => bytes_read (0)</div><div> 2.235573 => usb_interrupt_read -16</div>
<div> 2.236373 => packet_loop (0, 0)</div><div> 2.237285 => bytes_read (0)</div><div> 2.237620 => usb_interrupt_read -16</div><div> 2.238418 => packet_loop (0, 0)</div><div> 2.239706 => bytes_read (0)</div>
<br><div class="gmail_quote">On Fri, Sep 21, 2012 at 4:25 PM, Arnaud Quette <span dir="ltr"><<a href="mailto:aquette.dev@gmail.com" target="_blank">aquette.dev@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br><br><div class="gmail_quote">2012/9/21 Eugene Jurchenko <span dir="ltr"><<a href="mailto:jevgenious@gmail.com" target="_blank">jevgenious@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Massimo Gais <simosagi9 <at> <a href="http://gmail.com" target="_blank">gmail.com</a>> writes:<br>
<br>
><br>
> On Sun, Aug 12, 2012 at 5:11 AM, Greg Vickers <daehenoc <at> <a href="http://iinet.net.au" target="_blank">iinet.net.au</a>><br>
<div><div>wrote:<br>
> > On 11/08/12 06:58, Arnaud Quette wrote:<br>
> ><br>
> > Hi Massimo and Greg,<br>
> ><br>
> > @Greg: if you yet returned your unit, you now have a solution ;)<br>
> ><br>
> > I have not yet gotten rid of it, so thank you very much! It's a case of<br>
> > download, extract, apply patch, and compile on my RPi, correct?<br>
> ><br>
> > thanks for the effort for the patch!<br>
> ><br>
> > welcome ;)<br>
> ><br>
><br>
> Hello Greg,<br>
> yes you can compile it directly on the RPI. See anyway that if you<br>
> have the old deb package installed and you want to replace only the<br>
> recompiled driver, you may have some mismatch with the<br>
> pidpath/statepath directories (/var/state/ups vs /var/run/nut). I<br>
> tried to do it in a clean way by making a debian package on the RPi,<br>
> but it was requiring to install all the documentation tools, and I did<br>
> not have enough SD disk space for that.<br>
><br>
> Cheers,<br>
> Massimo<br>
><br>
<br>
</div></div>Greetings,<br></blockquote><div><br>Hi<br><br>thanks for the heads up, I just realized that I've not committed this patch! <br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Glad that I've found some info about the issue. I have same problem with the<br>
same UPS on RPi. Unfortunately link for the patch is no longer valid. Could you<br>
send it one more time or the compiled package for RPi would be more appreciable.<br>
Thank you<br></blockquote><div><br>you can find the thread, with compilation instructions and the patch, here:<br><a href="http://www.mail-archive.com/nut-upsuser@lists.alioth.debian.org/msg07278.html" target="_blank">http://www.mail-archive.com/nut-upsuser@lists.alioth.debian.org/msg07278.html</a><br>
<br>I'm waiting for your feedback + 1 (namely Rich Wrenn) to commit this.<br><br>cheers,<br>Arno<br>
</div></div>
</blockquote></div><br>