[Nut-upsuser] bcmxcp_usb can not communicate with Eaton Powerware 5110

[Arnaud Quette]

2012/8/1 Greg Vickers <daehenoc at iinet.net.au>

>  Hi Arnaud,
>

Hi Greg,


> On 31/07/12 01:02, Arnaud Quette wrote:
>
> Hi Greg,
>
> 2012/7/29 Greg Vickers <daehenoc at iinet.net.au>
>
>> On 22/07/12 20:14, Greg Vickers wrote:
>>
>>> Hi Arnaud,
>>>
>>> On 18/07/12 20:59, Arnaud Quette wrote:
>>>
>>>> I've just made a quick test on an Opengear ACM 50004-2 (ARM supervision
>>>> appliance).
>>>> For the record:
>>>> - uname -a: Linux acm5004-2 2.6.30.2-uc0 #1 Tue Feb 15 09:30:54 EST
>>>> 2011 armv4tl unknown
>>>> - nut version: 2.4.3 (so bcmxcp_usb 0.23)
>>>> - tried with a PW5110 (ups.firmware: Cont:00.50 Inve:01.50)
>>>>
>>>> and everything worked like a charm.
>>>> That said, Charles and Kjell comments are fully valid.
>>>> That is, try with the latest version (2.6.4). It has at least more
>>>> debug traces to help getting visibility.
>>>>
>>> I've tested with nut 2.6.4, with the same result, i.e. this driver can't
>>> communicate with the UPS.
>>>
>>> What switches should I use with the driver to provide you the debug
>>> information?  More -D switches?
>>>
>>>> Could you perhaps test the 5110 on your Ubuntu system, with a recent
>>>> NUT?
>>>>
>>> OK, tested on the Ubuntu system and it works just fine!  My PW5110 has
>>> the same firmware versions as yours, and the Ubuntu system I tested on has
>>> kernel 3.2.0 on it and nut 2.6.3.  I'll see if I can get kernel 3.2.0 on
>>> the RaspberryPi and report back.
>>>
>>
>>  I've got kernel 3.2.0 on the RaspberryPi and nut 2.6.4 and the
>> bcmxcp_usb driver reports the same problem :(
>>
>
> damn, this would lead me to also think about a kernel or libusb issue.
>
> just to be sure, is bcmxcp_usb linked against libusb *0.1* and not
> 1.0-compat?
>
> $ ldd bcmxcp_usb
>     /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so (0x401b4000)
>     libusb-0.1.so.4 => /lib/arm-linux-gnueabihf/libusb-0.1.so.4
> (0x4014f000)
>     libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0
> (0x40068000)
>     libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0x401bd000)
>     /lib/arm-linux-gnueabihf/ld-linux.so.3 => /lib/ld-linux-armhf.so.3
> (0x40037000)
>
> So yes, looks like it's linked to libusb 0.1.
>

yes, I confirm it.

>   I'm going to go with the last option I have, and will replace this UPS
>> with one that works with this combination of architecture and OS! :)
>
>
> yup, still an option ;)
>
> Thanks for your help!
>

welcome!

cheers,
Arnaud
-- 
Linux / Unix / Opensource Engineering Expert - Eaton -
http://opensource.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120801/c9e852f3/attachment.html>