Re: [Nut-upsuser] Nut and PowerWare 5115
Hi Arnaud, From: Arnaud Quette Sent: Tuesday, May 26, 2009 11:53 PM To: Greg Cc: Kjell Claesson ; nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] Nut and PowerWare 5115 Hi Greg, 2009/5/21 Greg greg_r...@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 -D -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. Running the above on both 8.10 and 9.04 gives the following output. The command prompt is not returned. bcmxcp_usb keeps running - r...@ubuntu9:~# export USB_DEBUG=3 /lib/nut/bcmxcp_usb -u root - -a PowerWare Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) USB communication subdriver 0.17 debug level is '4' 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 004 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 Length of meter map: 81 Index Offset Format NUT 0021 f0 None 0023 0004 f0 ups.power 0027 0008 52 output.frequency 0028 0012 52 input.frequency 0033 0016 52 battery.voltage 0034 0020 f0 battery.charge 0035 0024 e2 battery.runtime 0056 0028 f0 input.voltage 0059 0032 f0 None 0062 0036 f0 ambient.temperature 0065 0040 41 output.current 0068 0044 41 output.current.nominal 0071 0048 f0 None 0078 0052 f0 output.voltage Length of alarm map: 27 Index Alarm Supported -001 INVERTER_AC_OVER_VOLTAGE No -001 INVERTER_AC_UNDER_VOLTAGE No -001 INVERTER_OVER_OR_UNDER_FREQ No -001 BYPASS_AC_OVER_VOLTAGE No -001 BYPASS_AC_UNDER_VOLTAGE No -001 BYPASS_OVER_OR_UNDER_FREQ No INPUT_AC_OVER_VOLTAGE Yes 0001 INPUT_AC_UNDER_VOLTAGE Yes 0002 INPUT_UNDER_OR_OVER_FREQ Yes -001 OUTPUT_OVER_VOLTAGE No -001 OUTPUT_UNDER_VOLTAGE No -001 OUTPUT_UNDER_OR_OVER_FREQ No -001 REMOTE_EMERGENCY_PWR_OFF No -001 REMOTE_GO_TO_BYPASS No -001 BUILDING_ALARM_6 No -001 BUILDING_ALARM_5 No -001 BUILDING_ALARM_4 No -001 BUILDING_ALARM_3 No -001 BUILDING_ALARM_2 No -001 BUILDING_ALARM_1 No -001 STATIC_SWITCH_OVER_TEMP No -001 CHARGER_OVER_TEMP No -001 CHARGER_LOGIC_PWR_FAIL No -001 CHARGER_OVER_VOLTAGE_OR_CURRENT No -001 INVERTER_OVER_TEMP No 0003 OUTPUT_OVERLOAD Yes -001 RECTIFIER_INPUT_OVER_CURRENT No -001 INVERTER_OUTPUT_OVER_CURRENT No -001 DC_LINK_OVER_VOLTAGE No -001 DC_LINK_UNDER_VOLTAGE No -001 RECTIFIER_FAILED No 0004 INVERTER_FAULT Yes -001 BATTERY_CONNECTOR_FAIL No -001 BYPASS_BREAKER_FAIL No 0005 CHARGER_FAIL Yes -001 RAMP_UP_FAILED No -001 STATIC_SWITCH_FAILED No -001 ANALOG_AD_REF_FAIL No -001 BYPASS_UNCALIBRATED No -001 RECTIFIER_UNCALIBRATED No -001 OUTPUT_UNCALIBRATED No -001 INVERTER_UNCALIBRATED No -001 DC_VOLT_UNCALIBRATED No -001 OUTPUT_CURRENT_UNCALIBRATED No -001 RECTIFIER_CURRENT_UNCALIBRATED No -001 BATTERY_CURRENT_UNCALIBRATED No -001 INVERTER_ON_OFF_STAT_FAIL No -001 BATTERY_CURRENT_LIMIT No -001 INVERTER_STARTUP_FAIL No -001 ANALOG_BOARD_AD_STAT_FAIL No -001 OUTPUT_CURRENT_OVER_100 No -001 BATTERY_GROUND_FAULT No -001 WAITING_FOR_CHARGER_SYNC No -001 NV_RAM_FAIL No -001 ANALOG_BOARD_AD_TIMEOUT No 0006 SHUTDOWN_IMMINENT Yes 0007 BATTERY_LOW Yes 0008 UTILITY_FAIL Yes -001 OUTPUT_SHORT_CIRCUIT No 0009 UTILITY_NOT_PRESENT Yes -001 FULL_TIME_CHARGING No -001 FAST_BYPASS_COMMAND No -001 AD_ERROR No -001 INTERNAL_COM_FAIL No -001 RECTIFIER_SELFTEST_FAIL No -001 RECTIFIER_EEPROM_FAIL No -001 RECTIFIER_EPROM_FAIL No -001 INPUT_LINE_VOLTAGE_LOSS No -001 BATTERY_DC_OVER_VOLTAGE No -001 POWER_SUPPLY_OVER_TEMP No -001 POWER_SUPPLY_FAIL No -001 POWER_SUPPLY_5V_FAIL No -001 POWER_SUPPLY_12V_FAIL No -001 HEATSINK_OVER_TEMP No -001 HEATSINK_TEMP_SENSOR_FAIL No -001 RECTIFIER_CURRENT_OVER_125 No -001 RECTIFIER_FAULT_INTERRUPT_FAIL No -001 RECTIFIER_POWER_CAPASITOR_FAIL No -001 INVERTER_PROGRAM_STACK_ERROR No -001 INVERTER_BOARD_SELFTEST_FAIL No -001 INVERTER_AD_SELFTEST_FAIL No -001 INVERTER_RAM_SELFTEST_FAIL No -001 NV_MEMORY_CHECKSUM_FAIL No -001 PROGRAM_CHECKSUM_FAIL No -001 INVERTER_CPU_SELFTEST_FAIL No -001 NETWORK_NOT_RESPONDING No -001 FRONT_PANEL_SELFTEST_FAIL No -001 NODE_EEPROM_VERIFICATION_ERROR No -001 OUTPUT_AC_OVER_VOLT_TEST_FAIL No -001 OUTPUT_DC_OVER_VOLTAGE No -001 INPUT_PHASE_ROTATION_ERROR No -001 INVERTER_RAMP_UP_TEST_FAILED No -001 INVERTER_OFF_COMMAND
Re: [Nut-upsuser] Nut and PowerWare 5115
Kjell, 2009/5/26 Kjell Claesson kjell.claes...@epost.tidanet.se Greg and Arnaud 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. @Kjell: do you see anything that could lead to that kind of regression? I'm not sure that it's on our side though. I can not set the finger on what it is. My PW3105 is running fine on nut-2.4.1. so does the 5115 I have underhand. tested with both 2.4.1 (ubuntu vanilla) and the trunk! I know that there have been changes to the nut_usb.c file, and I made a comment to Arjen about it. Because it was breaking the switch between Powerware and Phoenixtec. But that is fixed. yup, I've checked the code 2 times, since many things have moved around. but I don't see any possible break here. And the problem on my side is that I don't have any ups with the Phoenixtec Power Co usb interface. I've cc'ed Tatu. Maybe he can arrange a remote access to such a device. If I get some time I can put ubuntu on a computer and test if the nut package is working on the pw3105. Arnaud, do you have any problems running PW5115 with nut-2.4.1 ? yes, as stated above. that's why I'm interested in the verbose lsusb (check if bConfigurationValue == 1) and the kernel version (some 2.6.28 have broken USB, irrc -3 and another one). as told previously, I'm more inclined in thinking that this issue comes from outside of NUT. something between libusb and the kernel, since the device is working otherwise, and particularly with an older NUT release. testing 2.2.2 on Greg's jaunty would confirm that (if it doesn't work!). cheers, Arnaud -- Linux / Unix Expert RD - 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/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Nut and PowerWare 5115
Hi Greg, 2009/5/21 Greg greg_r...@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 -D -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_r...@hotmail.com *Sent:* Wednesday, May 13, 2009 10:34 PM *To:* Greg greg_r...@hotmail.com ; Arnaud Quette aquette@gmail.com *Cc:* Kjell Claesson kjell.claes...@epost.tidanet.se ; nut-upsuser@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 r...@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 r...@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_r...@hotmail.com *Sent:* Thursday, May 07, 2009 9:22 PM *To:* Arnaud Quette aquette@gmail.com *Cc:* Kjell Claesson kjell.claes...@epost.tidanet.se ; nut-upsuser@lists.alioth.debian.org *Subject:* Re: [Nut-upsuser] Nut and PowerWare 5115 Hi Arnaud, *From:* Arnaud Quette aquette@gmail.com *Sent:* Thursday, May 07, 2009 6:50 AM *To:* Greg greg_r...@hotmail.com *Cc:* Kjell Claesson kjell.claes...@epost.tidanet.se ; nut-upsuser@lists.alioth.debian.org *Subject:* Re: [Nut-upsuser] Nut and PowerWare 5115 Hi Greg, 2009/5/4 Greg greg_r...@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 RD - Eaton - http://www.eaton.com/mgeops Network
Re: [Nut-upsuser] Nut and PowerWare 5115
Greg and Arnaud 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. @Kjell: do you see anything that could lead to that kind of regression? I'm not sure that it's on our side though. I can not set the finger on what it is. My PW3105 is running fine on nut-2.4.1. I know that there have been changes to the nut_usb.c file, and I made a comment to Arjen about it. Because it was breaking the switch between Powerware and Phoenixtec. But that is fixed. And the problem on my side is that I don't have any ups with the Phoenixtec Power Co usb interface. If I get some time I can put ubuntu on a computer and test if the nut package is working on the pw3105. Arnaud, do you have any problems running PW5115 with nut-2.4.1 ? /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Nut and PowerWare 5115
Hi Arnaud, Any luck with the latest subversion trunk? From: Greg Sent: Wednesday, May 13, 2009 10:34 PM To: Greg ; Arnaud Quette Cc: Kjell Claesson ; nut-upsuser@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 r...@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 r...@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 Sent: Thursday, May 07, 2009 9:22 PM To: Arnaud Quette Cc: Kjell Claesson ; nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] Nut and PowerWare 5115 Hi Arnaud, From: Arnaud Quette Sent: Thursday, May 07, 2009 6:50 AM To: Greg Cc: Kjell Claesson ; nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] Nut and PowerWare 5115 Hi Greg, 2009/5/4 Greg greg_r...@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 __ Information from ESET Smart Security, version of virus signature database 4063 (20090508) __ The message was checked by ESET Smart Security. http://www.eset.com ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser __ Information from ESET Smart Security, version of virus signature database 4063 (20090508) __ The message was checked by ESET Smart Security. http://www.eset.com __ Information from ESET Smart Security, version of virus signature database 4070 (20090513) __ The message was checked by ESET Smart Security. http://www.eset.com __ Information from ESET Smart Security, version of virus signature database 4093 (20090521
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 r...@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 r...@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 Sent: Thursday, May 07, 2009 9:22 PM To: Arnaud Quette Cc: Kjell Claesson ; nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] Nut and PowerWare 5115 Hi Arnaud, From: Arnaud Quette Sent: Thursday, May 07, 2009 6:50 AM To: Greg Cc: Kjell Claesson ; nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] Nut and PowerWare 5115 Hi Greg, 2009/5/4 Greg greg_r...@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 __ Information from ESET Smart Security, version of virus signature database 4063 (20090508) __ The message was checked by ESET Smart Security. http://www.eset.com ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser __ Information from ESET Smart Security, version of virus signature database 4063 (20090508) __ The message was checked by ESET Smart Security. http://www.eset.com __ Information from ESET Smart Security, version of virus signature database 4070 (20090513) __ The message was checked by ESET Smart Security. http://www.eset.com ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Nut and PowerWare 5115
Hi Arnaud, From: Arnaud Quette Sent: Thursday, May 07, 2009 6:50 AM To: Greg Cc: Kjell Claesson ; nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] Nut and PowerWare 5115 Hi Greg, 2009/5/4 Greg greg_r...@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 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Nut and PowerWare 5115
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 == 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? From: Greg Sent: Tuesday, April 28, 2009 10:16 PM To: Arnaud Quette Cc: Kjell Claesson ; nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] Nut and PowerWare 5115 Hi Arnaud and Kjell, Sorry for the slow reply. From: Arnaud Quette Sent: Friday, April 24, 2009 7:59 PM To: Greg Cc: Kjell Claesson ; nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] Nut and PowerWare 5115 Greg, 2009/4/23 Greg greg_r...@hotmail.com Hi Arnaud and Kjell, Please find answers below. I also re-compiled 2.4.1 myself on Ubuntu and still got the same issues/errors. ok, I think I've got it: how did you tried this one: recompiling the deb package or the source. there is a udev change in 2.4.1 that is targeted to Jaunty. udev rules were previously in /etc/udev/rules.d, and is now is /lib/udev/rules.d this means that the privileges won't be set correctly if you use such a package on pre jaunty. if you went from source, well I'm not sure. I compiled from source but running on Ubuntu 8.10 I just did a clean compile of 2.4.1 on Ubuntu 8.10 from source and after running ./configure make and make install. upsdrvctl is not available. It exists in /usr/local/ups/bin but I cannot run it. Very weird. So I would say my issues with the previous timeouts was due to installing the DEB package and it not completely being removed. If you have anything you would like run or if there is any other debugging I am happy to compile/run it. yep, I'm interested in a simple 'lsusb' then, validates the privileges for both 2.2.2 and 2.4.1 with the data from lsubs (Bus and Dev) by doing an ls -l /dev/bus/usb/XXX/YYY (and/or /proc/bus... equivalent). Here is the output of lsusb and ls on Ubuntu 8.10 running nut 2.2.2 = Bus 002 Device 002: ID 0c45:63fa Microdia Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 0e0f:0002 Bus 001 Device 004: ID 06da:0002 Phoenixtec Power Co., Ltd UPS Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub crw-rw-r-- 1 root nut 189, 3 2009-04-28 21:14 /dev/bus/usb/001/004 === I can't get an output of 2.4.1 as it wont compile now on Ubuntu 8.10. Here is the output of lsusb and ls on my QNAP running nut = Bus 001 Device 005: ID 06da:0002 Phoenixtec Power Co., Ltd. Bus 001 Device 004: ID 04a9:10a5 Canon Inc. Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Bus 001 Device 001: ID : Virtual Hub After plugging in device -rw-r--r--1 adminadminist 52 Apr 28 22:11 /proc/bus/usb/001/005 I think changed the permissions to... -rw-rw-r--1 adminadminist 52 Apr 28 22:11 /proc/bus/usb/001/005 = After changing the permissions on my QNAP above I still get the same output = Network UPS Tools - UPS driver controller 2.4.1 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 /proc/bus/usb usb_os_find_busses: Found 001 usb_os_find_busses: Skipping non bus directory devices usb_os_find_devices: Found 005 on 001 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 004 on 001 usb_os_find_devices: Found 002 on 001 usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device Communications with UPS lost: Receive error (data): got 32 bytes instead of 116!!! USB error: error sending control message: Connection timed out Communications with UPS lost: Receive error (Request command): BLOCK: 0, COMMAND: 31! USB error: error sending control message: Broken pipe Communications with UPS lost: Receive error (Request command): BLOCK: 0, COMMAND: 31! USB error: error sending control message: Broken pipe Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE usb_os_find_busses: Found 001 usb_os_find_busses: Skipping non bus directory devices usb_os_find_devices: Found 005 on 001 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 004
Re: [Nut-upsuser] Nut and PowerWare 5115
Hi Arnaud and Kjell, Sorry for the slow reply. From: Arnaud Quette Sent: Friday, April 24, 2009 7:59 PM To: Greg Cc: Kjell Claesson ; nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] Nut and PowerWare 5115 Greg, 2009/4/23 Greg greg_r...@hotmail.com Hi Arnaud and Kjell, Please find answers below. I also re-compiled 2.4.1 myself on Ubuntu and still got the same issues/errors. ok, I think I've got it: how did you tried this one: recompiling the deb package or the source. there is a udev change in 2.4.1 that is targeted to Jaunty. udev rules were previously in /etc/udev/rules.d, and is now is /lib/udev/rules.d this means that the privileges won't be set correctly if you use such a package on pre jaunty. if you went from source, well I'm not sure. I compiled from source but running on Ubuntu 8.10 I just did a clean compile of 2.4.1 on Ubuntu 8.10 from source and after running ./configure make and make install. upsdrvctl is not available. It exists in /usr/local/ups/bin but I cannot run it. Very weird. So I would say my issues with the previous timeouts was due to installing the DEB package and it not completely being removed. If you have anything you would like run or if there is any other debugging I am happy to compile/run it. yep, I'm interested in a simple 'lsusb' then, validates the privileges for both 2.2.2 and 2.4.1 with the data from lsubs (Bus and Dev) by doing an ls -l /dev/bus/usb/XXX/YYY (and/or /proc/bus... equivalent). Here is the output of lsusb and ls on Ubuntu 8.10 running nut 2.2.2 = Bus 002 Device 002: ID 0c45:63fa Microdia Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 0e0f:0002 Bus 001 Device 004: ID 06da:0002 Phoenixtec Power Co., Ltd UPS Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub crw-rw-r-- 1 root nut 189, 3 2009-04-28 21:14 /dev/bus/usb/001/004 === I can't get an output of 2.4.1 as it wont compile now on Ubuntu 8.10. Here is the output of lsusb and ls on my QNAP running nut = Bus 001 Device 005: ID 06da:0002 Phoenixtec Power Co., Ltd. Bus 001 Device 004: ID 04a9:10a5 Canon Inc. Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Bus 001 Device 001: ID : Virtual Hub After plugging in device -rw-r--r--1 adminadminist 52 Apr 28 22:11 /proc/bus/usb/001/005 I think changed the permissions to... -rw-rw-r--1 adminadminist 52 Apr 28 22:11 /proc/bus/usb/001/005 = After changing the permissions on my QNAP above I still get the same output = Network UPS Tools - UPS driver controller 2.4.1 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 /proc/bus/usb usb_os_find_busses: Found 001 usb_os_find_busses: Skipping non bus directory devices usb_os_find_devices: Found 005 on 001 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 004 on 001 usb_os_find_devices: Found 002 on 001 usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device Communications with UPS lost: Receive error (data): got 32 bytes instead of 116!!! USB error: error sending control message: Connection timed out Communications with UPS lost: Receive error (Request command): BLOCK: 0, COMMAND: 31! USB error: error sending control message: Broken pipe Communications with UPS lost: Receive error (Request command): BLOCK: 0, COMMAND: 31! USB error: error sending control message: Broken pipe Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE usb_os_find_busses: Found 001 usb_os_find_busses: Skipping non bus directory devices usb_os_find_devices: Found 005 on 001 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 004 on 001 usb_os_find_devices: Found 002 on 001 usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device USB error: could not set config 1: Broken pipe 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 Driver failed to start (exit status=1) = my guess is that it's a permission issue. and you can validate it by running the driver as root (ie bcmxcp_usb -u root
Re: [Nut-upsuser] Nut and PowerWare 5115
Hi Arnaud and Kjell, Please find answers below. I also re-compiled 2.4.1 myself on Ubuntu and still got the same issues/errors. If you have anything you would like run or if there is any other debugging I am happy to compile/run it. Is there anything else you can think of that I can try to get nut 2.2.2 working on my QNAP?? From: Arnaud Quette Sent: Wednesday, April 22, 2009 9:31 PM To: Greg ; Kjell Claesson Cc: nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] Nut and PowerWare 5115 Greg, I forgot to add that I'm interested in an upsc output of the working version (ubuntu 8.10 with 2.2.2...) Here you go = r...@ubuntuvmp:~# upsc powerw...@localhost ambient.temperature: 42 battery.charge: 100 battery.runtime: 2334 battery.voltage: 13.47 driver.name: bcmxcp_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.2.2 driver.version.internal: 0.14 input.frequency: 50.34 input.voltage: 249 output.current: 0.0 output.frequency: 50.34 output.phases: 1 output.voltage: 249 output.voltage.nominal: 240 ups.firmware: Cont:01.00 Inve:10.04 ups.load: 10.2 ups.model: 51150500A 500VA ups.power.nominal: 500 ups.serial: UY196A0229 ups.status: OL = thanks (and sorry for top posting) Arnaud 2009/4/22 Arnaud Quette aquette@gmail.com Greg, Kjell, 2009/4/21 Kjell Claesson kjell.claes...@epost.tidanet.se tisdag 21 april 2009 14:43:28 skrev Greg: Hi Kjell, Hi Greg, Sorry for the late reply been doing a lot of testing. No problem. I got the package from http://ipkg.nslu2-linux.org/feeds/optware/cs05q3armel/cross/stable/nut_2.4. 1-1_arm.ipk It pretty much pre-compiled which are then extracted to the device on installation. OK. I tested nut and the 5115 under Ubuntu 8.10. Ubuntu comes with nut 2.2.2 by default which works fine. I installed 2.4.1 which does not work either. This is not so good. Then we may have a bug introduced to the nut_usb. I cc this mail to Arnaud. Arnaud can you run some tests on the PW5115 with NUT 2.4.1 ? We may have broken something from version 2.2.2. But it may be the package also but I think Arnaud is working on that to. well, the packages (and ipk are iirc kinda simplified debs) are quite straighforward. the nut package (for example on Ubuntu) includes the core and the serial/usb drivers, with the udev file and so on. the hal support is in another packages that is conflicting with the nut one (in order to avoid runtime conflict between the classic and hal drivers). The error: USB error: could not set config 1: Device or resource busy Can't set POWERWARE USB configuration Unable to find POWERWARE UPS device on USB bus Is indicating that something is already running. Did you check that the debug run was the only thing running at the moment. yup, 2nded. Greg: can you try again this test please. Yes it was the only thing running. I even restarted a few times and tried a few more times. So I compiled and installed 2.2.2 on my QNAP device and it still doesn't work. 2.2.2 was compiled on my QNAP without HAL support just USB support. Yes, and I see that you get the same error as you get on 2.4.1 on the QNAP. The problem is that I don't have any 5115 to test this on. So I hope that Arnaud can test this. My PW3105 is running fine on usb on 2.4.1. I've just made some test on PW5115 500i (500VA), nut 2.4.1(-2 ; packaged) on an Ubuntu 8.10. Everything was fine. same goes for 2.2.2 (from source this time) the firmwares are: - USB: 01.00 - Main:10.04 This is the only 5115 I have underhand, but what is puzzling me is the exact model name: - mine (with 2.2.2) displays Model = PW5115 500i 500VA - while Greg's displaysModel = 51150500A 500VA a subtle difference! though the 2 firmwares (USB and main) are identical. iirc, this value (the name) can be changed. Have you done so Greg? I was unaware about changing the name of the UPS. I have not done this. I'm still learning PW, and will have to check with the PW people there. more info soon cheers, Arnaud -- Linux / Unix Expert RD - 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/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Nut and PowerWare 5115
Hi Arnaud and Kjell, One more thing. One thing I noticed is the QNAP find usb devices in /proc/bus/usb and Ubuntu find them in /dev/bus/usb. Could this have any effect? Thanks Greg From: Greg Sent: Thursday, April 23, 2009 6:56 PM To: Arnaud Quette ; Kjell Claesson Cc: nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] Nut and PowerWare 5115 Hi Arnaud and Kjell, Please find answers below. I also re-compiled 2.4.1 myself on Ubuntu and still got the same issues/errors. If you have anything you would like run or if there is any other debugging I am happy to compile/run it. Is there anything else you can think of that I can try to get nut 2.2.2 working on my QNAP?? From: Arnaud Quette Sent: Wednesday, April 22, 2009 9:31 PM To: Greg ; Kjell Claesson Cc: nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] Nut and PowerWare 5115 Greg, I forgot to add that I'm interested in an upsc output of the working version (ubuntu 8.10 with 2.2.2...) Here you go = r...@ubuntuvmp:~# upsc powerw...@localhost ambient.temperature: 42 battery.charge: 100 battery.runtime: 2334 battery.voltage: 13.47 driver.name: bcmxcp_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.2.2 driver.version.internal: 0.14 input.frequency: 50.34 input.voltage: 249 output.current: 0.0 output.frequency: 50.34 output.phases: 1 output.voltage: 249 output.voltage.nominal: 240 ups.firmware: Cont:01.00 Inve:10.04 ups.load: 10.2 ups.model: 51150500A 500VA ups.power.nominal: 500 ups.serial: UY196A0229 ups.status: OL = thanks (and sorry for top posting) Arnaud 2009/4/22 Arnaud Quette aquette@gmail.com Greg, Kjell, 2009/4/21 Kjell Claesson kjell.claes...@epost.tidanet.se tisdag 21 april 2009 14:43:28 skrev Greg: Hi Kjell, Hi Greg, Sorry for the late reply been doing a lot of testing. No problem. I got the package from http://ipkg.nslu2-linux.org/feeds/optware/cs05q3armel/cross/stable/nut_2.4. 1-1_arm.ipk It pretty much pre-compiled which are then extracted to the device on installation. OK. I tested nut and the 5115 under Ubuntu 8.10. Ubuntu comes with nut 2.2.2 by default which works fine. I installed 2.4.1 which does not work either. This is not so good. Then we may have a bug introduced to the nut_usb. I cc this mail to Arnaud. Arnaud can you run some tests on the PW5115 with NUT 2.4.1 ? We may have broken something from version 2.2.2. But it may be the package also but I think Arnaud is working on that to. well, the packages (and ipk are iirc kinda simplified debs) are quite straighforward. the nut package (for example on Ubuntu) includes the core and the serial/usb drivers, with the udev file and so on. the hal support is in another packages that is conflicting with the nut one (in order to avoid runtime conflict between the classic and hal drivers). The error: USB error: could not set config 1: Device or resource busy Can't set POWERWARE USB configuration Unable to find POWERWARE UPS device on USB bus Is indicating that something is already running. Did you check that the debug run was the only thing running at the moment. yup, 2nded. Greg: can you try again this test please. Yes it was the only thing running. I even restarted a few times and tried a few more times. So I compiled and installed 2.2.2 on my QNAP device and it still doesn't work. 2.2.2 was compiled on my QNAP without HAL support just USB support. Yes, and I see that you get the same error as you get on 2.4.1 on the QNAP. The problem is that I don't have any 5115 to test this on. So I hope that Arnaud can test this. My PW3105 is running fine on usb on 2.4.1. I've just made some test on PW5115 500i (500VA), nut 2.4.1(-2 ; packaged) on an Ubuntu 8.10. Everything was fine. same goes for 2.2.2 (from source this time) the firmwares are: - USB: 01.00 - Main:10.04 This is the only 5115 I have underhand, but what is puzzling me is the exact model name: - mine (with 2.2.2) displays Model = PW5115 500i 500VA - while Greg's displaysModel = 51150500A 500VA a subtle difference! though the 2 firmwares (USB and main) are identical. iirc, this value (the name) can be changed. Have you done so Greg? I was unaware about changing the name of the UPS. I have not done this. I'm still learning PW, and will have to check with the PW people there. more info soon cheers, Arnaud -- Linux / Unix Expert RD - 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
Re: [Nut-upsuser] Nut and PowerWare 5115
Greg, I forgot to add that I'm interested in an upsc output of the working version (ubuntu 8.10 with 2.2.2...) thanks (and sorry for top posting) Arnaud 2009/4/22 Arnaud Quette aquette@gmail.com Greg, Kjell, 2009/4/21 Kjell Claesson kjell.claes...@epost.tidanet.se tisdag 21 april 2009 14:43:28 skrev Greg: Hi Kjell, Hi Greg, Sorry for the late reply been doing a lot of testing. No problem. I got the package from http://ipkg.nslu2-linux.org/feeds/optware/cs05q3armel/cross/stable/nut_2.4 . 1-1_arm.ipk It pretty much pre-compiled which are then extracted to the device on installation. OK. I tested nut and the 5115 under Ubuntu 8.10. Ubuntu comes with nut 2.2.2 by default which works fine. I installed 2.4.1 which does not work either. This is not so good. Then we may have a bug introduced to the nut_usb. I cc this mail to Arnaud. Arnaud can you run some tests on the PW5115 with NUT 2.4.1 ? We may have broken something from version 2.2.2. But it may be the package also but I think Arnaud is working on that to. well, the packages (and ipk are iirc kinda simplified debs) are quite straighforward. the nut package (for example on Ubuntu) includes the core and the serial/usb drivers, with the udev file and so on. the hal support is in another packages that is conflicting with the nut one (in order to avoid runtime conflict between the classic and hal drivers). The error: USB error: could not set config 1: Device or resource busy Can't set POWERWARE USB configuration Unable to find POWERWARE UPS device on USB bus Is indicating that something is already running. Did you check that the debug run was the only thing running at the moment. yup, 2nded. Greg: can you try again this test please. So I compiled and installed 2.2.2 on my QNAP device and it still doesn't work. 2.2.2 was compiled on my QNAP without HAL support just USB support. Yes, and I see that you get the same error as you get on 2.4.1 on the QNAP. The problem is that I don't have any 5115 to test this on. So I hope that Arnaud can test this. My PW3105 is running fine on usb on 2.4.1. I've just made some test on PW5115 500i (500VA), nut 2.4.1(-2 ; packaged) on an Ubuntu 8.10. Everything was fine. same goes for 2.2.2 (from source this time) the firmwares are: - USB: 01.00 - Main:10.04 This is the only 5115 I have underhand, but what is puzzling me is the exact model name: - mine (with 2.2.2) displays Model = PW5115 500i 500VA - while Greg's displaysModel = 51150500A 500VA a subtle difference! though the 2 firmwares (USB and main) are identical. iirc, this value (the name) can be changed. Have you done so Greg? I'm still learning PW, and will have to check with the PW people there. more info soon cheers, Arnaud -- Linux / Unix Expert RD - 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/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Nut and PowerWare 5115
No 0016AMBIENT_OVER_TEMP Yes -001CABINET_DOOR_OPEN No -001CABINET_DOOR_OPEN_VOLT_PRESENT No -001AUTO_SHUTDOWN_PENDING No -001TAP_SWITCHING_REALY_PENDING No -001UNABLE_TO_CHARGE_BATTERIES No -001STARTUP_FAILURE_CHECK_EPO No -001AUTOMATIC_STARTUP_PENDING No -001MODEM_FAILEDNo -001INCOMING_MODEM_CALL_STARTED No -001OUTGOING_MODEM_CALL_STARTED No -001MODEM_CONNECTION_ESTABLISHEDNo -001MODEM_CALL_COMPLETED_SUCCESSNo dstate_init: sock /var/run/nut/bcmxcp_usb-PowerWare open on fd 5 == I compiled 2.4.1 myself without HAL support and got the following == [/opt/bin] # bcmxcp_usb - -a PowerWare -u admin Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) USB communication subdriver 0.17 debug level is '4' usb_set_debug: Setting debugging level to 3 (on) usb_os_init: Found USB VFS at /proc/bus/usb usb_os_find_busses: Found 001 usb_os_find_busses: Skipping non bus directory devices usb_os_find_devices: Found 013 on 001 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 003 on 001 usb_os_find_devices: Found 002 on 001 usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device Communications with UPS lost: Receive error (data): got 4 bytes instead of 116!!! USB error: error sending control message: Connection timed out Communications with UPS lost: Receive error (Request command): BLOCK: 0, COMMAND: 31! USB error: error sending control message: Broken pipe Communications with UPS lost: Receive error (Request command): BLOCK: 0, COMMAND: 31! USB error: error sending control message: Broken pipe Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE usb_os_find_busses: Found 001 usb_os_find_busses: Skipping non bus directory devices usb_os_find_devices: Found 013 on 001 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 003 on 001 usb_os_find_devices: Found 002 on 001 usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device USB error: could not set config 1: Broken pipe 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 == Hope all of the above helps! Thanks once again for all your help. Regards Greg -- From: Kjell Claesson kjell.claes...@epost.tidanet.se Sent: Saturday, April 18, 2009 8:54 PM To: Greg greg_r...@hotmail.com Cc: nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] Nut and PowerWare 5115 fredag 17 april 2009 15:36:24 skrev Greg: Hi Kjell, Hi. Sorry for the delay. Thanks for the follow up. Answers below... OK Greg, I can not locate the package you used for installing NUT, but the device should be capable of running NUT. I was thinking if HAL is enabled in the package so the 'hotplug' find the ups on the bus and start the hal driver. Then it gives a conflict. But I got a nice advise from our master Arnaud to enable debug for the libusb. If you do 'export USB_DEBUG=3' you get some debugging info from the libusb in your log. This may help to track down what happens. One thing that is bothering me is that we may have a bug that I can't test. The PW5115 is using a different way of handling the usb endpoint. This is fixed a while back. But there may have been changes to the nut_usb.c that have broken this. I can not see any wrong in the code, but as I don't have a PW5115 with usb, I can not test this. But I know that we have some users running the 5115 on usb, and I have not seen any bug report yet. If you can test it on the Ubuntu installation we can rule out any buggs. Regards /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Nut and PowerWare 5115
tisdag 21 april 2009 14:43:28 skrev Greg: Hi Kjell, Hi Greg, Sorry for the late reply been doing a lot of testing. No problem. I got the package from http://ipkg.nslu2-linux.org/feeds/optware/cs05q3armel/cross/stable/nut_2.4. 1-1_arm.ipk It pretty much pre-compiled which are then extracted to the device on installation. OK. I tested nut and the 5115 under Ubuntu 8.10. Ubuntu comes with nut 2.2.2 by default which works fine. I installed 2.4.1 which does not work either. This is not so good. Then we may have a bug introduced to the nut_usb. I cc this mail to Arnaud. Arnaud can you run some tests on the PW5115 with NUT 2.4.1 ? We may have broken something from version 2.2.2. But it may be the package also but I think Arnaud is working on that to. The error: USB error: could not set config 1: Device or resource busy Can't set POWERWARE USB configuration Unable to find POWERWARE UPS device on USB bus Is indicating that something is already running. Did you check that the debug run was the only thing running at the moment. So I compiled and installed 2.2.2 on my QNAP device and it still doesn't work. 2.2.2 was compiled on my QNAP without HAL support just USB support. Yes, and I see that you get the same error as you get on 2.4.1 on the QNAP. The problem is that I don't have any 5115 to test this on. So I hope that Arnaud can test this. My PW3105 is running fine on usb on 2.4.1. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Nut and PowerWare 5115
fredag 17 april 2009 15:36:24 skrev Greg: Hi Kjell, Hi. Sorry for the delay. Thanks for the follow up. Answers below... OK Greg, I can not locate the package you used for installing NUT, but the device should be capable of running NUT. I was thinking if HAL is enabled in the package so the 'hotplug' find the ups on the bus and start the hal driver. Then it gives a conflict. But I got a nice advise from our master Arnaud to enable debug for the libusb. If you do 'export USB_DEBUG=3' you get some debugging info from the libusb in your log. This may help to track down what happens. One thing that is bothering me is that we may have a bug that I can't test. The PW5115 is using a different way of handling the usb endpoint. This is fixed a while back. But there may have been changes to the nut_usb.c that have broken this. I can not see any wrong in the code, but as I don't have a PW5115 with usb, I can not test this. But I know that we have some users running the 5115 on usb, and I have not seen any bug report yet. If you can test it on the Ubuntu installation we can rule out any buggs. Regards /Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Nut and PowerWare 5115
Hi Kjell, Thanks for the follow up. Answers below... Greg -- From: Kjell Claesson kjell.claes...@epost.tidanet.se Sent: Friday, April 17, 2009 3:17 PM To: Greg greg_r...@hotmail.com Cc: nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] Nut and PowerWare 5115 fredag 17 april 2009 01:09:58 skrev Greg: Hi Kjell, OK Greg, Thanks for the quick responce. I have removed the baud_rate. My bcmxcp_usb is located in /opt/bin. (structure of the QNAP device). The QNAP does not have a root user but an admin user so I ran the command with -u admin. Running the command I got the same output i think. 8-snip-- Yep it is the same result. Communications with UPS lost: Receive error (data): got 33 bytes instead of 116!!! It looks like the usb-bus stop. But it have fund the device. Communications with UPS lost: Receive error (Request command): COMMAND: 31 And it chokes on the first command. (Line 1040 in bcmxcp.c) and loose connection to the device. RECONNECT USB DEVICE It try to reconnect to the device. Can't set POWERWARE USB configuration Unable to find POWERWARE UPS device on USB bus But now it can not find it on the bus. Can you tell me something more about the setup. I'm not so familiar with QNAP. Based on Linux or FreeBSD ? Everything on the net appears to say Linux. uname -a output is Linux THEBOX 2.6.21.1-qnap #5 Wed Mar 18 15:19:23 CST 2009 armv5tejl unknown What version of the usblib is installed? The closest thing I could find was libusb. It is version 0.1.12-1. IPKG lists libusb as a dependency for NUT Is other devices using usblib working? To the best of my knowledge no. Do you have a serial port on the device ? No unfortunately its just USB And if you have any link so i can read something more on QNAP devices. This is the model I have http://www.qnap.com/pro_detail_feature.asp?p_id=85 And this is information about the ipkg installer which i used to install NUT http://www.handhelds.org/moin/moin.cgi/Ipkg Over the weekend I will install NUT on ubuntu 8.10 just to make sure it can connect to my UPS fine. The Windows software can connect so I know my UPS is functioning. Once again thank you for your help. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Nut and PowerWare 5115
torsdag 16 april 2009 02:25:58 skrev Greg: Hi everyone, Hi Greg, Been searching like crazy to find an answer to this. I have even read some of the source code but cannot figure this one out. I have installed nut 2.4.1 on my QNAP 409 Pro. (command: ipkg install nut) I have configured the ups.conf, upsd.conf and upsd.users. When i run upsdrvctl start I get the following error messages and output. Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) USB communication subdriver 0.17 Communications with UPS lost: Receive error (data): got 33 bytes instead of 116!!! Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE Can't set POWERWARE USB configuration Unable to find POWERWARE UPS device on USB bus This looks like a access rights problem. Can you try the following. Start the driver in debug mode like this. /path/to/bcmxcp_usb -DD -a PowerWare -u root Normal the path is /lib/nut but check where the bcmxcp_usb is located. This should spit out some debug info. Stop it by hitting ctrl-c. Send me (and the list) the output. 8-snip My ups.conf looks like this user=admin [PowerWare] driver = bcmxcp_usb port = auto desc = PowerWare 5115 UPS #pollinterval=1 baud_rate = 9600 You can remove the baud_rate. It is only for the serial part of the driver. Regards Kjell (Driver author) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Nut and PowerWare 5115
Hi Kjell, Thanks for the quick responce. I have removed the baud_rate. My bcmxcp_usb is located in /opt/bin. (structure of the QNAP device). The QNAP does not have a root user but an admin user so I ran the command with -u admin. Running the command I got the same output i think. == [/opt/bin] # bcmxcp_usb -DD -a PowerWare -u admin Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) USB communication subdriver 0.17 debug level is '2' Communications with UPS lost: Receive error (data): got 33 bytes instead of 116!!! Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE 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 == Hopefully this might still be useful. Thanks for you help, Greg -- From: Kjell Claesson kjell.claes...@epost.tidanet.se Sent: Friday, April 17, 2009 1:58 AM To: nut-upsuser@lists.alioth.debian.org Cc: Greg greg_r...@hotmail.com Subject: Re: [Nut-upsuser] Nut and PowerWare 5115 torsdag 16 april 2009 02:25:58 skrev Greg: Hi everyone, Hi Greg, Been searching like crazy to find an answer to this. I have even read some of the source code but cannot figure this one out. I have installed nut 2.4.1 on my QNAP 409 Pro. (command: ipkg install nut) I have configured the ups.conf, upsd.conf and upsd.users. When i run upsdrvctl start I get the following error messages and output. Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) USB communication subdriver 0.17 Communications with UPS lost: Receive error (data): got 33 bytes instead of 116!!! Communications with UPS lost: Receive error (Request command): COMMAND: 31 RECONNECT USB DEVICE Can't set POWERWARE USB configuration Unable to find POWERWARE UPS device on USB bus This looks like a access rights problem. Can you try the following. Start the driver in debug mode like this. /path/to/bcmxcp_usb -DD -a PowerWare -u root Normal the path is /lib/nut but check where the bcmxcp_usb is located. This should spit out some debug info. Stop it by hitting ctrl-c. Send me (and the list) the output. 8-snip My ups.conf looks like this user=admin [PowerWare] driver = bcmxcp_usb port = auto desc = PowerWare 5115 UPS #pollinterval=1 baud_rate = 9600 You can remove the baud_rate. It is only for the serial part of the driver. Regards Kjell (Driver author) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
