I don't follow what you're saying, but here's the output of the requested command.
# ps -elf | grep usbhid-ups 1 S nut 1508 1 0 80 0 - 4159 - 00:45 ? 00:00:07 /lib/nut/usbhid-ups -a cyberpower 1 S nut 1677 1 0 80 0 - 4180 - 00:58 ? 00:00:10 /lib/nut/usbhid-ups -a cyberpower 1 S nut 1719 1 0 80 0 - 4180 - 01:35 ? 00:00:06 /lib/nut/usbhid-ups -a cyberpower 1 S nut 1732 1 0 80 0 - 4180 - 01:35 ? 00:00:03 /lib/nut/usbhid-ups -a cyberpower 0 S root 2073 2068 0 80 0 - 1887 - 09:06 pts/0 00:00:00 grep usbhid-ups On Sun, 17 Oct 2010 11:20 +0200, "Arnaud Quette" <aquette....@gmail.com> wrote: Hi 2010/10/17 you wrote: Debian Squeeze 2.6.32-5-amd64 nut 2.4.3-1.1 CyberPower 625HG UPS via usb Dell PowerEdge R210 When usb.conf is configured to use driver "usbhid-ups", and port=auto, functions are proper except syslog & local consoles are filled with the messages below. As mentioned previously, local consoles are rendered useless unless nut service is stopped prior to use. (By issuing the following command: /etc/init.d/nut stop) I cannot set the usb.conf to use driver "cyberpower", as it's been removed from the package over lack of maintenance support from the vendor. When I set the usb.conf to use alternate driver "powerpanel", and port=auto, the service cannot start and returns "Unable to open auto: No such file or directory" error message. the 2 above drivers are (or were) serial drivers, requiring a serial port like /dev/ttyS0. I don't see the link with the present bug! can you please shed some light? Excerpt of "usbhis-ups" errors: Oct 17 00:58:42 Planck kernel: [ 827.184548] usb 2-1.1: usbfs: process 1677 (usbhid-ups) did not claim interface 0 before use Oct 17 00:58:45 Planck usbhid-ups[1690]: libusb_get_interrupt: error submitting URB: Device or resource busy Oct 17 00:58:45 Planck kernel: [ 830.234307] usb 2-1.1: usbfs: process 1690 (usbhid-ups) did not claim interface 0 before use Oct 17 00:58:45 Planck kernel: [ 830.234418] usb 2-1.1: usbfs: process 1690 (usbhid-ups) did not claim interface 0 before use Oct 17 00:58:45 Planck usbhid-ups[1690]: libusb_get_report: error sending control message: Device or resource busy Oct 17 00:58:45 Planck usbhid-ups[1690]: Got disconnected by another driver: Device or resource busy Oct 17 00:58:48 Planck usbhid-ups[1677]: libusb_get_interrupt: error submitting URB: Device or resource busy Oct 17 00:58:48 Planck usbhid-ups[1677]: libusb_get_report: error sending control message: Device or resource busy Oct 17 00:58:48 Planck usbhid-ups[1677]: Got disconnected by another driver: Device or resource busy Oct 17 00:58:48 Planck kernel: [ 833.177178] usb 2-1.1: usbfs: process 1677 (usbhid-ups) did not claim interface 0 before use Oct 17 00:58:48 Planck kernel: [ 833.177289] usb 2-1.1: usbfs: process 1677 (usbhid-ups) did not claim interface 0 before use looking at the above, you have a driver fight: you have probably 2 usbhid-ups drivers instances, fighting to get the device connexion. which in turns generate the above noise in your syslog. please confirm this by issuing a "ps -elf | grep usbhid-ups" cheers Arno -- Network UPS Tools (NUT) Project Leader - [1]http://www.networkupstools.org/ Debian Developer - [2]http://www.debian.org Free Software Developer - [3]http://arnaud.quette.free.fr/ References 1. http://www.networkupstools.org/ 2. http://www.debian.org/ 3. http://arnaud.quette.free.fr/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
