Hi Christoph,<br><br><div class="gmail_quote">2009/7/27 Christoph Loesch <span dir="ltr"><info@loesch.me></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
hi list,<br>
<br>
im running debian/testing(act. squeeze) with 2.6.26-2-amd64 kernel. first<br>
tried apcupsd what flawlessly worked but because i run nagios (needs nut<br>
running for 'check_ups'), im trying to run nut.<br>
<br>
dmesg and syslog show the device:<br>
Jul 27 00:08:06 kate kernel: [16001.477941] hiddev96hidraw0: USB HID v1.10<br>
Device [APC Back-UPS ES 700 FW:829.D3 .I USB FW:D3 ] on usb-0000:00:1d.1-1<br>
Jul 27 00:08:06 kate kernel: [16001.477941] usb 3-1: New USB device found,<br>
idVendor=051d, idProduct=0002<br>
Jul 27 00:08:06 kate kernel: [16001.477941] usb 3-1: New USB device<br>
strings: Mfr=3, Product=1, SerialNumber=2<br>
Jul 27 00:08:06 kate kernel: [16001.477941] usb 3-1: Product: Back-UPS ES<br>
700 FW:829.D3 .I USB FW:D3<br>
Jul 27 00:08:06 kate kernel: [16001.477941] usb 3-1: Manufacturer: APC<br>
Jul 27 00:08:06 kate kernel: [16001.477941] usb 3-1: SerialNumber:<br>
3B0908X39177<br>
<br>
lsusb doesnt show it. (maybe because usb is statically compiled in?)<br>
kate:/# grep -w CONFIG_USB /boot/config-`uname -r`<br>
CONFIG_USB=y<br>
but the hiddevice is there<br>
kate:/# ls -la /dev/hid*<br>
crw-rw-r-- 1 root root 180, 96 27. Jul 00:08 /dev/hiddev0<br>
crw-rw---- 1 root root 250, 0 27. Jul 00:08 /dev/hidraw0<br>
<br>
tried using usbhid-ups driver and even with setting the option variable<br>
"cable" to "940-0127E" i had no luck.<br>
genericups with all possible upstypes doesnt work either.<br>
<br>
any ideas?<br>
chris<br>
</blockquote><div><br></div></div>NUT' USB drivers use the libusb, so the usbfs on Linux (ie /dev/bus/usb/XXX/YYY)<br><br>depending on your exact distro version, the udev rule is located in /etc/udev/rules.d (old path) or /lib/udev/rules.d (new path). Generally, putting "auto" as the port value is sufficient.<br>
<br>to make a quick test, launch the driver as root, ie:<br>/path/to/usbhid-ups -u root -a upsname<br><br>it should acquire the connexion and talk to the device.<br>if it's ok, also try lsusb as root, you should see your device. then check the devices permissions, with the info from lsusb (Bus XXX, Device YYY) on /dev/bus/usb/XXX/YYY<br>
it should be sufficient for the "nut" user (the exact user name depends on the distro...)<br><br>cheers,<br>Arnaud<br>-- <br>Linux / Unix Expert R&D - Eaton - <a href="http://www.eaton.com/mgeops">http://www.eaton.com/mgeops</a><br>
Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/">http://www.networkupstools.org/</a><br>Debian Developer - <a href="http://www.debian.org">http://www.debian.org</a><br>Free Software Developer - <a href="http://arnaud.quette.free.fr/">http://arnaud.quette.free.fr/</a><br>
<br>