Hi Greg,
2009/5/21 Greg <greg_roll at hotmail.com>
> Hi Arnaud,
>
> Any luck with the latest subversion trunk?
>
sorry for the lag... too many things, not enough time.
I'm preparing a version with some more debug info, but I'm still puzzled
with your issue.
in the meantime, can you retry the debug test on your 9.04, ie
export USB_DEBUG=3 && /lib/nut/bcmxcp_usb -u root -DDDDD -a PowerWare
if you end up with "Can't set POWERWARE USB configuration", then
we should
have an msg from libusb like "could not set config..." with the exact
errno...
I'll then ping you for the updated driver.
> *From:* Greg <greg_roll at hotmail.com>
> *Sent:* Wednesday, May 13, 2009 10:34 PM
> *To:* Greg <greg_roll at hotmail.com> ; Arnaud Quette <aquette.dev
at gmail.com>
> *Cc:* Kjell Claesson <kjell.claesson at epost.tidanet.se> ;
> nut-upsuser at lists.alioth.debian.org
> *Subject:* Re: [Nut-upsuser] Nut and PowerWare 5115
>
> Hi Arnaud,
>
> Some more testing on Ubuntu 9.04.
>
> Here is the output of bcmxcp_usb and lsusb
>
> ===========================================>
> root at Ubuntu9:/lib/nut# ./bcmxcp_usb -a PowerWare -u root
>
> Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1)
>
> USB communication subdriver 0.17
>
> usb_set_debug: Setting debugging level to 3 (on)
>
> usb_os_init: Found USB VFS at /dev/bus/usb
>
> usb_os_find_busses: Found 001
>
> usb_os_find_busses: Found 002
>
> usb_os_find_devices: Found 001 on 001
>
> usb_os_find_devices: Found 003 on 002
>
> skipped 1 class/vendor specific interface descriptors
>
> usb_os_find_devices: Found 002 on 002
>
> usb_os_find_devices: Found 001 on 002
>
> error obtaining child information: Inappropriate ioctl for device
>
> root at Ubuntu9:/lib/nut# lsusb
>
> usb_set_debug: Setting debugging level to 3 (on)
>
> usb_os_init: Found USB VFS at /dev/bus/usb
>
> usb_os_find_busses: Found 001
>
> usb_os_find_busses: Found 002
>
> usb_os_find_devices: Found 001 on 001
>
> usb_os_find_devices: Found 003 on 002
>
> skipped 1 class/vendor specific interface descriptors
>
> usb_os_find_devices: Found 002 on 002
>
> usb_os_find_devices: Found 001 on 002
>
> error obtaining child information: Inappropriate ioctl for device
>
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> Bus 002 Device 003: ID 06da:0002 Phoenixtec Power Co., Ltd UPS
>
> Bus 002 Device 002: ID 0e0f:0002
>
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>
> ==========================================>
> *From:* Greg <greg_roll at hotmail.com>
> *Sent:* Thursday, May 07, 2009 9:22 PM
> *To:* Arnaud Quette <aquette.dev at gmail.com>
> *Cc:* Kjell Claesson <kjell.claesson at epost.tidanet.se> ;
> nut-upsuser at lists.alioth.debian.org
> *Subject:* Re: [Nut-upsuser] Nut and PowerWare 5115
>
> Hi Arnaud,
>
> *From:* Arnaud Quette <aquette.dev at gmail.com>
> *Sent:* Thursday, May 07, 2009 6:50 AM
> *To:* Greg <greg_roll at hotmail.com>
> *Cc:* Kjell Claesson <kjell.claesson at epost.tidanet.se> ;
> nut-upsuser at lists.alioth.debian.org
> *Subject:* Re: [Nut-upsuser] Nut and PowerWare 5115
>
> Hi Greg,
>
> 2009/5/4 Greg <greg_roll at hotmail.com>
>
>> Hi guys,
>>
>> I installed Nut 2.4.1_4 on Ubuntu 9.04 and I have similar issues. If I
run
>> upsdrvctl start I get
>>
>>
>
> 2.4.1-2ubuntu4 you mean (the one that is available in the distro)?
> have you tried to unplug and plug back the USB cord of the UPS? otherwise,
> try this and relaunch upsdrvctl or bcmxcp_usb
> Sorry yes I installed the package from the distro. I have unplugged and
> plugged back in the UPS but get the same issue.
>
> I am creating a new install of Ubuntu 9.04 and will test again.
>
> =============================>>
>> Can't set POWERWARE USB configuration
>> Unable to find POWERWARE UPS device on USB bus
>> Things to try:
>>
>> - Connect UPS device to USB bus
>>
>> - Run this driver as another user (upsdrvctl -u or 'user=...'
in
>> ups.conf).
>> See upsdrvctl(8) and ups.conf(5).
>>
>> Fatal error: unusable configuration
>> CLOSING
>>
>> =============================>>
>> I am unable to run /lib/nut/bcmxcp_usb -a PowerWare -u root as none of
the
>> files in /lib/nut appear as executable.
>>
>> Any thoughts?
>>
>>
>
> I've just checked again, and all the files in /lib/nut are executable
in a
> fresh jaunty install.
> otherwise, you wouldn't have been able to run the driver nor get the
above
> output!
> so I found this strange, you should check again... it's probably the
> devices privileges mentioned above.
> and this one is possibly due to a bug in the package.
>
> we seem to face a completely different issue here than the one on the QNAP.
> I'd first like to be sure that you're unit is working (or not) in
jaunty
> before getting back to the QNAP.
>
> I've just checked the code (which has been revamped), and the specific
part
> seem similar (can't be 100% sure though). now, I'll have to add
some more
> trace to get more visibility.
> I'll probably ping you tomorrow to test the latest subversion trunk. ok
> with that method?
> Yes that will be fine. I will be away from home the next 3 days but I will
> test when I return.
>
> Thanks again for your help.
>
>
> Arnaud
>
cheers,
Arnaud
--
Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20090526/b0c8f8cb/attachment.htm>