[Nut-upsuser] Nut and PowerWare 5115

Greg greg_roll at hotmail.com
Thu May 28 12:41:38 UTC 2009


Hi Arnaud,


From: Arnaud Quette 
Sent: Wednesday, May 27, 2009 12:42 AM
To: Greg 
Cc: Kjell Claesson ; nut-upsuser at lists.alioth.debian.org 
Subject: Re: [Nut-upsuser] Nut and PowerWare 5115


Greg,


2009/5/26 Arnaud Quette <aquette.dev at gmail.com>

  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 missed to add that I'm also interested in this one: "unset USB_DEBUG && lsusb -d06da:0002 -v" on your 9.04. I can't find it back in the thread.

Here is the output (the QNAP has the same output except the line 'idProduct 0x0002' is missing UPS on the QNAP)
===========================================

Bus 002 Device 004: ID 06da:0002 Phoenixtec Power Co., Ltd UPS

Device Descriptor:

bLength 18

bDescriptorType 1

bcdUSB 1.10

bDeviceClass 0 (Defined at Interface level)

bDeviceSubClass 0 

bDeviceProtocol 0 

bMaxPacketSize0 8

idVendor 0x06da Phoenixtec Power Co., Ltd

idProduct 0x0002 UPS

bcdDevice 1.00

iManufacturer 4 Powerware

iProduct 24 Powerware UPS

iSerial 0 

bNumConfigurations 1

Configuration Descriptor:

bLength 9

bDescriptorType 2

wTotalLength 34

bNumInterfaces 1

bConfigurationValue 1

iConfiguration 0 

bmAttributes 0x80

(Bus Powered)

MaxPower 60mA

Interface Descriptor:

bLength 9

bDescriptorType 4

bInterfaceNumber 0

bAlternateSetting 0

bNumEndpoints 1

bInterfaceClass 255 Vendor Specific Class

bInterfaceSubClass 0 

bInterfaceProtocol 0 

iInterface 0 

** UNRECOGNIZED: 09 21 00 01 00 01 22 00 00

Endpoint Descriptor:

bLength 7

bDescriptorType 5

bEndpointAddress 0x81 EP 1 IN

bmAttributes 3

Transfer Type Interrupt

Synch Type None

Usage Type Data

wMaxPacketSize 0x0008 1x 8 bytes

bInterval 20

Device Status: 0x0000

(Bus Powered)

 


===========================================

@Kjell: do you see anything that could lead to that kind of "regression"?
I'm not sure that it's on our side though.

@Greg: can you fill the following and perhaps do some more testing (note that you only need to exec the driver):
- is 2.2.2 working on 9.04? (simply get the source, configure using the instructions at the bottom of this mail and then compile as usual)

I didn't have much luck after compiling the driver as upsdrvctl was missing. So I just installed the .deb file from the repository.

    yes 2.2.2 works on 9.04. (upsdrvctl and bcmxcp_usb)
    2.2.2 also works on 8.10 (upsdrvctl and bcmxcp_usb)

- is 2.4.1 working on 8.10?
    no 2.4.1 does not work on 8.10. (upsdrvctl loads and returns to command prompt, does not display UPS firmware version etc, bcmxcp_usb works)
    no 2.4.1 does not work on 9.04. (upsdrvctl loads and returns to command prompt, does not display UPS firmware version etc, bcmxcp_usb works)

So it looks like for me 2.4.1 is broken on 8.10 and 9.04. Running 'upsdrvctl start' does not return any errors or display the firmware version.
Running 'upsdrvctl start' on 2.2.2 displays the firmware version. 

When running bcmxcp_usb on 9.04. upsmon is then able to pick up the UPS driver as running. It seems to be some issue with upsdrvcrl.

My kernel on 9.04 is
============
Linux Ubuntu9 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux

===========


- I would need more tech info on your qnap (arch, linux version, libusb version, USB path ie /proc or /dev, verbose lsusb as told above)

arch: arm
linux version: Linux THEBOX 2.6.21.1-qnap #5 Wed Mar 18 15:19:23 CST 2009 armv5tejl unknown
libusb version: 0.1.12
usb path: /proc
lsusb: same as above except the line 'idProduct 0x0002' is missing UPS on the QNAP.

* configure line
----------------------
configure --prefix=/usr \
--exec-prefix=/ \
--sysconfdir=/etc/nut \
--mandir=/usr/share/man \
--libdir=/lib \
--includedir=/usr/include \
--without-all \
--enable-static \
--with-statepath=/var/run/nut \
--with-altpidpath=/var/run/nut \
--with-drvpath=/lib/nut \
--with-pidpath=/var/run/nut \
--datadir=/usr/share/nut \
--with-pkgconfig-dir=/usr/lib/pkgconfig \
--with-user=nut --with-group=nut


__________ Information from ESET Smart Security, version of virus signature database 4109 (20090527) __________

The message was checked by ESET Smart Security.

http://www.eset.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20090528/462963dd/attachment.htm>


More information about the Nut-upsuser mailing list