[Nut-upsuser] Re: RE Powerware 5115 and USB
> > If bcmxcp_usb just needs libusb: is there any way to make sure that my > > libusb does indeed work as expected? Now I'm in the situation that I > > don't know whether my USB subsystem is broken, whether there is a bug > > in nut 2.0.3 or the Powerware 5115 is not supported via USB. Any hints? > you can try "export USB_DEBUG=3" to trace libusb internal routines. Now I get: botticelli:/usr/local/ups/bin# ./bcmxcp_usb - -u root -a botticelli-ups Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.3) debug level is '4' usb_set_debug: Setting debugging level to 5 (on) usb_os_init: Found USB VFS at /proc/bus/usb usb_os_find_busses: Found 005 usb_os_find_busses: Found 004 usb_os_find_busses: Found 003 usb_os_find_busses: Found 002 usb_os_find_busses: Found 001 usb_os_find_busses: Skipping non bus directory devices usb_os_find_devices: Found 001 on 005 usb_os_find_devices: Found 001 on 004 usb_os_find_devices: Found 001 on 003 usb_os_find_devices: Found 002 on 002 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 002 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 001 on 001 Can't open POWERWARE USB device, retrying ... Can't open POWERWARE USB device Unable to find POWERWARE UPS device on USB bus [...] The UPS is device 2 on bus 2 indeed: botticelli:/usr/local/ups/bin# lsusb Bus 005 Device 001: ID : Bus 004 Device 001: ID : Bus 003 Device 001: ID : Bus 002 Device 002: ID 06da:0002 Phoenixtec Power Co., Ltd Bus 002 Device 001: ID : Bus 001 Device 001: ID : Is there any way to change the "class/vendor specific interface descriptor" into something that bcmxcp_usb understands? Best, Georg -- Georg Rehm [EMAIL PROTECTED] SFB 441, Tübingen University +49 (0)7071 29-77155 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Re: RE Powerware 5115 and USB
> > ./bcmxcp_usb -DDD -u root -a upsname > Subscribe to the list, report the above debug (-DDD) output. Ok, here we go (I snipped most of the "Can't ..." lines): --- botticelli:/usr/local/ups/bin# ./bcmxcp_usb -DDD -u root -a botticelli-ups Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.3) debug level is '3' Can't open POWERWARE USB device, retrying ... Can't open POWERWARE USB device, retrying ... [...] Can't open POWERWARE USB device, retrying ... Can't open POWERWARE USB device, retrying ... Can't open POWERWARE USB device 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 botticelli:/usr/local/ups/bin# --- So, is it really true that I do *not* need a working hiddev subsystem to get this Powerware 5115 to work over USB? If I no longer need hiddev, why does 2.0.3's configure still allow to specify the path to hiddev.h? If bcmxcp_usb just needs libusb: is there any way to make sure that my libusb does indeed work as expected? Now I'm in the situation that I don't know whether my USB subsystem is broken, whether there is a bug in nut 2.0.3 or the Powerware 5115 is not supported via USB. Any hints? Best, Georg -- Georg Rehm [EMAIL PROTECTED] SFB 441, Tübingen University +49 (0)7071 29-77155 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Re: RE Powerware 5115 and USB
Looks like Georg and I have the same problem w/ different Powerware UPSes... I get the same error :-P ken __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] SOS : Help needed for UPS Centralion Blazer 2000VAUSB
Hi, There is a slight difference between the bcmxcp_usb driver and this ups. If you look at the descriptor it tell you that the protocol is reported on the interface level. The interface level say HID device. If you look at the bcmxcp_usb driver it say vendor protocol on the interface level. So this should follow the usb hid device rules on the interface. Regards Kjell - Original Message - From: "Arnaud Quette" <[EMAIL PROTECTED]> To: "Carlos Rodrigues" <[EMAIL PROTECTED]> Cc: Sent: Wednesday, April 12, 2006 7:48 PM Subject: Re: [Nut-upsuser] SOS : Help needed for UPS Centralion Blazer 2000VAUSB Hi Carlos, 2006/4/12, Carlos Rodrigues <[EMAIL PROTECTED]>: > That hardware doesn't have a serial port right? > > I think that UPS could be supported if only one could configure a > "ttyUSB" with that serial-usb converter. > > I (temporarily) have a model with an USB port here, and I would like > to see if I could get it to work with "megatec"/"powermust" without > resorting to some HID/USB magic... > > The protocol used seems to be the same, so the only thing needed is to > configure a emulated serial port. Anyone has any ideas? isn't bcmxcp_usb built on the same idea? iirc, they were just encaps'ing the serial protocol over usb (not sure about hid). Another example of "strange hid approach" is energizerups, but it's hiddev only. Anyway, all this might give you some ideas ;-) Arnaud ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] bcmxcp_usb "Can't open POWERWARE USB device"
Hi all, To Arnaud. Yes the 5115 is talking bcmxcp but it is not working with the bcmxcp_usb driver. I got some help from a Australian guy to test this. But it look's like the first try of usb from powerware was flaky. Even the windows driver loses contact to the ups. It is usb ver1.1 so i made a small test program that i can change the timeout in. But it would not help. But i'm on to it. The 5115 is talkin bcmxcp on the serial port and the 3110 is a generic contact closure on the dsub. So if the computer is equiped with a serial port it is still possible to get it to run. We also have the 'new' udev that take over the cold and hotplug function. And we have the 'hal' that i think overlapping some of the functions. And i think the documentation is not up to date to get this to run. And the about the device. It is safer to have it running on auto. If you set the '/proc/bus/usb/00x/00x' for the port and then plug in some other usb device, it is not shure that it is pointing on the right device when it restarts. Then i have a problem. My computer is down due to a faulty mainboard, so i can't test anything, and do any coding. Hopfully i be back in the end of the week. (Sneaked in on one of my son's computer to get my mail) This comes in a bad time as i hade some time to spare to catch up on this. Regards Kjell - Original Message - From: "Ken Yee" <[EMAIL PROTECTED]> To: Sent: Wednesday, April 12, 2006 5:18 AM Subject: [Nut-upsuser] bcmxcp_usb "Can't open POWERWARE USB device" > I tried switching to the USB version of bcmxcp_usb and > get this error when I try starting up upsdrvctl or > bcmxcp_usb like so: > /etc/nut/bcmxcp_usb - -a powerware -u nut > > I used this for ups.conf: > [powerware] > driver = bcmxcp_usb > port = auto > > With the serial/usb dongle, I used this successfully: > [powerware] > driver = bcmxcp > port = /dev/ttyUSB0 > > What devices does "auto" look for? I don't have a > /dev/usb, but I do have /proc/bus/usb, so I tried > setting the port to /proc/bus/usb/002/003 which > is what it shows up as in dmesg when I plug it in, > but I get the same error msgs as when I set the > port to "auto" :-P > > ken > > > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > ___ > Nut-upsuser mailing list > Nut-upsuser@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] SOS : Help needed for UPS Centralion Blazer 2000VA USB
Hi Carlos, 2006/4/12, Carlos Rodrigues <[EMAIL PROTECTED]>: > That hardware doesn't have a serial port right? > > I think that UPS could be supported if only one could configure a > "ttyUSB" with that serial-usb converter. > > I (temporarily) have a model with an USB port here, and I would like > to see if I could get it to work with "megatec"/"powermust" without > resorting to some HID/USB magic... > > The protocol used seems to be the same, so the only thing needed is to > configure a emulated serial port. Anyone has any ideas? isn't bcmxcp_usb built on the same idea? iirc, they were just encaps'ing the serial protocol over usb (not sure about hid). Another example of "strange hid approach" is energizerups, but it's hiddev only. Anyway, all this might give you some ideas ;-) Arnaud ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] SOS : Help needed for UPS Centralion Blazer 2000VA USB
That hardware doesn't have a serial port right? I think that UPS could be supported if only one could configure a "ttyUSB" with that serial-usb converter. I (temporarily) have a model with an USB port here, and I would like to see if I could get it to work with "megatec"/"powermust" without resorting to some HID/USB magic... The protocol used seems to be the same, so the only thing needed is to configure a emulated serial port. Anyone has any ideas? On 4/11/06, Guillaume JAOUEN <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > > Hello, > > I leave a mail here because I can't find any solution in order to get the > nut working with this UPS despite I search everywhere on the net. > > I've bought this UPS recently after that an MGE-UPS Ellipse 1200 USB burn. > > I've those information about the UPS : > > Reseller link : http://www.alpha-power-technologie.com/images/GPi-usb.pdf > > In his catalogue, the product is called Global Power GPi-2000BZ > > This UPS has monitoring software called Winpower > 2.0(http://www.ups-software-download.com/) which is developed by > Centralion. > > My system is a Debian Sarge 3.1 with a 2.4.32 kernel and built-in HID USB > support. (this kernel was working perfectly well with the MGE-UPS HID UPS > Ellipse 1200 and nut driver newhidups) > > I've tried to set up winpower under debian but get an RMI server failure at > boot. I also see that the setup script wasn't set correctly for Debian, > even > after fixed PATH variables and right rc.d scripts... > > So I went back on nut and tried to solve this problem. > > On the Centralion Web site I found an UPS that seems to be the same as mine > (blazer 2000VA Spec. > http://www.centralion.com/html/product/back-Product-ups-blazer1000-spec.htm > and brochure > http://www.centralion.com/dm-download/Blazer1-2K/Blazer1K-2K.zip) > > This UPS use megatec protocol over USB I think. Below are details catch > from the console : > > When I plug the UPS on the USB port I get : > # lsusb > Bus 003 Device 005: ID 0665:5161 > > If I do cat /dev/usb/hiddev0 the system seems to be reading on the device > but no characters appears on the console... > > If I unplug the UPS the cat /dev/usb/hiddev0 command stop working so I > think the system see the UPS on this device. > > The usbview show me this on the device : > > USB to Serial > Manufacturer: Cypress Semiconductor > Speed: 1,5 Mb/s (low) > USB Version: 1.10 > Device Class: 00(ifc ) > Device Subclass: 00 > Device Protocol: 00 > Maximum Default Endpoint Size: 8 > Number of Configurations: 1 > Vendor Id: 0665 > Product Id: 5161 > Revision Number:0.02 > > Config Number: 1 > Number of Interfaces: 1 > Attributes: 80 > MaxPower Needed: 100mA > > Interface Number: 0 > Name: hid > Alternate Number: 0 > Class: 03(HID ) > Sub Class: 0 > Protocol: 0 > Number of Endpoints: 1 > > Endpoint Adderss: 81 > Direction: in > Attribute: 3 > Type: Int. > Max Packet Size: 8 > Interval: 32ms > > If someone could help me, it'll be really nice, as I've tried newhidups - > fentoups - energized drivers without success. > > I think my problem come from the USB to serial chipset from Cypress which > is not included into newhidups but it's out of what I can manage. > > Best regards, > > Guillaume JAOUEN. > > -BEGIN PGP SIGNATURE- > Version: PGP Desktop 9.0.2 (Build 2424) > > iQIVAwUBRDvh/IBhxpjgV9LlAQHhohAAjMCjEVWlbDSiCQohipHPVZ0sEplQX6Ef > VhgwxadPwC1oPJ1HHlOiUelOAx1GQ9IDhxizBI7bGd4N5+njRbzRAw+aGZjXH4jA > IPAoz9aNpEuirBunA1etk10o4eIiiYH3rAoCiWhDLzNnoIa7tAyr9RPVLR6ff4HY > VzUDve6INIuKOzH1LaLvgYab3ZzzoG//A2eyoA03a7dRsXfgVwqL5nYYDXQdWVDm > R/hru9NP14/SquT5I9jKjqoASnyJG0+p93b/7y3JvkC6ELARqNCzvQXozDlf8InE > r0WOPiBh43lMH3OXTD6EF2/JViRfOG4Ybt0Cb+HO0BRQQ1MIeigjUIs17ivvZxFI > KEvSV03LHhmbGPUqgiyCow6jRB1bxhaA8bDHj2GnyoYUfLFxsHtEbAJ9ZAQwygUA > o88KxCRpvB9v4RRE+ZB4dJerlGPpZ42pUbtm+rxV3U9IDzaK85t83VJlJpeBczo9 > 8BlS9rtC21ocpi3B6fKo1FnEnSiGVozfmLzYi7lFruGNvu5iA38F6nFrp/p9mt8I > ZC1OPzy0cXdXyDZHP3C7Kt4j/A+pyDTqA9H7y3Cy1x1YUWleqW/xMMcVLziKSMQp > yXnbLytjJWmblRvQSdvc6+1IlKWZuiYKiOd4w/MOdDPdZTqL54pPkVyydzyfY8NN > y749+rz/+aY= > =Gya8 > -END PGP SIGNATURE- > > > > ___ > Nut-upsuser mailing list > Nut-upsuser@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser > -- Carlos Rodrigues ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] bcmxcp_usb "Can't open POWERWARE USB device"
I tried switching to the USB version of bcmxcp_usb and get this error when I try starting up upsdrvctl or bcmxcp_usb like so: /etc/nut/bcmxcp_usb - -a powerware -u nut I used this for ups.conf: [powerware] driver = bcmxcp_usb port = auto With the serial/usb dongle, I used this successfully: [powerware] driver = bcmxcp port = /dev/ttyUSB0 What devices does "auto" look for? I don't have a /dev/usb, but I do have /proc/bus/usb, so I tried setting the port to /proc/bus/usb/002/003 which is what it shows up as in dmesg when I plug it in, but I get the same error msgs as when I set the port to "auto" :-P ken __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Re: RE Powerware 5115 and USB
[please keep the list cc'ed Georg, and remember that I'm not the powerware support, so the only info I have about that is the developer's feedback and my knowledges...] 2006/4/12, Georg Rehm <[EMAIL PROTECTED]>: > Hi Arnaud, > > > you need nut 2.0.3 (deb available in unstable, simply need to rebuild on > > sarge) and the bcmxcp_usb driver (use "port = auto" as the automagic device > > path) > > sorry, but 2.0.3 does not work either. I found the 2.0.3 release yesterday > night but the real problem seems to be that the hiddev subsystem on this > machine might be broken: cat /proc/bus/usb/devices reports a "Driver=(none)" > for the Powerware 5115 USB device but I don't have the slightest idea why > that might be: > > T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 > D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > P: Vendor=06da ProdID=0002 Rev= 1.00 > S: Manufacturer=Powerware > S: Product=Powerware UPS > C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 60mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) > E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=20ms > > My current kernel is a 2.6.15.4 SMP (AMD Opetron). The hiddev subsystem > should work: > > CONFIG_USB_HID=y > CONFIG_USB_HIDINPUT=y > CONFIG_USB_HIDDEV=y > > After fiddling with /etc/udev I now get the correct (I hope) device: > > botticelli:~# ls -l /dev/usb/hiddev2 > crw-rw 1 root root 189, 129 2006-04-12 00:35 /dev/usb/hiddev2 > all these hiddev thingies are only useful for the old hidups. all the new usb drivers use libusb... > I wrote Tore yesterday who suggested to mail Kjell. Kjell in turn > suggested to do a > > ./bcmxcp_usb -DDD -u root -a upsname > > (with "port=auto") but it only reports "Can't open POWERWARE USB > device, retrying ...". According to Kjell the protocol that's used > by the 5115 over USB is pure BCMXCP, so the bcmxcp_usb driver should > work. Do you happen to have any idea as to how to fix a broken hiddev > subsystem? Is it possible to activate the hid driver for the UPS USB > device manually? Are there any tools that help with debugging hiddev > problems? Would a kernel upgrade to a 2.6.16-5 (?) do the trick? > I can't tell more than that. Subscribe to the list, report the above debug (-DDD) output. Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Re: RE Powerware 5115 and USB
2006/4/12, Georg Rehm <[EMAIL PROTECTED]>: > > > ./bcmxcp_usb -DDD -u root -a upsname > > > Subscribe to the list, report the above debug (-DDD) output. > > Ok, here we go (I snipped most of the "Can't ..." lines): > > --- > > botticelli:/usr/local/ups/bin# ./bcmxcp_usb -DDD -u root -a botticelli-ups > Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.3) > > debug level is '3' > Can't open POWERWARE USB device, retrying ... > Can't open POWERWARE USB device, retrying ... > [...] > Can't open POWERWARE USB device, retrying ... > Can't open POWERWARE USB device, retrying ... > Can't open POWERWARE USB device > 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 > botticelli:/usr/local/ups/bin# > > --- > > So, is it really true that I do *not* need a working hiddev subsystem > to get this Powerware 5115 to work over USB? If I no longer need hiddev, > why does 2.0.3's configure still allow to specify the path to hiddev.h? because the old hiddev is still there, and will only be removed for 2.2. as previously, nut as always a migration path, no rude switch > If bcmxcp_usb just needs libusb: is there any way to make sure that my > libusb does indeed work as expected? Now I'm in the situation that I > don't know whether my USB subsystem is broken, whether there is a bug > in nut 2.0.3 or the Powerware 5115 is not supported via USB. Any hints? you can try "export USB_DEBUG=3" to trace libusb internal routines. what is sure is that it's not a permissions problem (you're running it as root), so I'm more thinking about either a device problem, or the driver not supporting it. But once more, I don't have the needed knowledges on this subject. Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] SOS : Help needed for UPS Centralion Blazer 2000VA USB
bonjour Guillaume, 2006/4/11, Guillaume JAOUEN <[EMAIL PROTECTED]>: > -BEGIN PGP SIGNED MESSAGE- > > Hello, > > I leave a mail here because I can't find any solution in order to get the > nut working with this UPS despite I search everywhere on the net. > > I've bought this UPS recently after that an MGE-UPS Ellipse 1200 USB burn. 2 questions: - what do you mean exactly by "bum"? - were unsatisfied with Ellipse, and more generally with MGE, to switch to another brand? > I've those information about the UPS : > > Reseller link : http://www.alpha-power-technologie.com/images/GPi-usb.pdf > > In his catalogue, the product is called Global Power GPi-2000BZ > > This UPS has monitoring software called Winpower > 2.0(http://www.ups-software-download.com/) which is developed by > Centralion. > > My system is a Debian Sarge 3.1 with a 2.4.32 kernel and built-in HID USB > support. (this kernel was working perfectly well with the MGE-UPS HID UPS > Ellipse 1200 and nut driver newhidups) > > I've tried to set up winpower under debian but get an RMI server failure at > boot. I also see that the setup script wasn't set correctly for Debian, > even > after fixed PATH variables and right rc.d scripts... > > So I went back on nut and tried to solve this problem. > > On the Centralion Web site I found an UPS that seems to be the same as mine > (blazer 2000VA Spec. > http://www.centralion.com/html/product/back-Product-ups-blazer1000-spec.htm > and brochure > http://www.centralion.com/dm-download/Blazer1-2K/Blazer1K-2K.zip) > > This UPS use megatec protocol over USB I think. Below are details catch > from the console : > > When I plug the UPS on the USB port I get : > # lsusb > Bus 003 Device 005: ID 0665:5161 > > If I do cat /dev/usb/hiddev0 the system seems to be reading on the device > but no characters appears on the console... > > If I unplug the UPS the cat /dev/usb/hiddev0 command stop working so I > think the system see the UPS on this device. > > The usbview show me this on the device : > > USB to Serial > Manufacturer: Cypress Semiconductor > Speed: 1,5 Mb/s (low) > USB Version: 1.10 > Device Class: 00(ifc ) > Device Subclass: 00 > Device Protocol: 00 > Maximum Default Endpoint Size: 8 > Number of Configurations: 1 > Vendor Id: 0665 > Product Id: 5161 > Revision Number:0.02 > > Config Number: 1 > Number of Interfaces: 1 > Attributes: 80 > MaxPower Needed: 100mA > > Interface Number: 0 > Name: hid > Alternate Number: 0 > Class: 03(HID ) > Sub Class: 0 > Protocol: 0 > Number of Endpoints: 1 > > Endpoint Adderss: 81 > Direction: in > Attribute: 3 > Type: Int. > Max Packet Size: 8 > Interval: 32ms > > If someone could help me, it'll be really nice, as I've tried newhidups - > fentoups - energized drivers without success. for serial, there is a blazer driver that will be replaced by megatec (only available from subversion). for usb, you might try newhidups in generic mode (-x generic), with debug enabled (-DDD) Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] RE Powerware 5115 and USB
Hi Georg, > one question with regard to a Powerware 5115 UPS connected to a Debian 3.1 > Sarge box via USB: I downloaded and compiled nut 2.0.2 but I am unable to > configure the USB subsystem so that upsdrvctl recognizes the UPS. > > My /usr/local/ups/etc/ups.conf contains: > > [bla] >driver = bcmxcp >port = /dev/usbdev2.2 >desc = "bla bla ..." > > Yesterday it took me about 10 minutes to configure an APC Smart UPS 1500 > on another Sarge box (using apcupsd), but the combination of nut, USB > and this Powerware 5115 UPS seems to be really tricky. Is it obligatory > to use something like /dev/usb/hiddev0 in the port statement in ups.conf? > (The apcupsd on the other machine is configured with a simple "usb" > statement and automagically finds the correct UPS. Does something like > this exist for nut?) What kind of "port" statement is needed in ups.conf? > I don't know why but I cannot get this machine to use /dev/usb/hiddev*. The > relevant components are compiled into the kernel and it _should_ work, but > doesn't. Any help would be really appreciated! you need nut 2.0.3 (deb available in unstable, simply need to rebuild on sarge) and the bcmxcp_usb driver (use "port = auto" as the automagic device path) Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
