Hi Arnaud,

Arnaud Quette schrieb:
Hi Christoph,

2009/7/27 Christoph Loesch <i...@loesch.me>

    hi list,

    im running debian/testing(act. squeeze) with 2.6.26-2-amd64 kernel.
    first
    tried apcupsd what flawlessly worked but because i run nagios (needs nut
    running for 'check_ups'), im trying to run nut.

    dmesg and syslog show the device:
    Jul 27 00:08:06 kate kernel: [16001.477941] hiddev96hidraw0: USB HID
    v1.10
    Device [APC Back-UPS ES 700 FW:829.D3 .I USB FW:D3 ] on
    usb-0000:00:1d.1-1
    Jul 27 00:08:06 kate kernel: [16001.477941] usb 3-1: New USB device
    found,
    idVendor=051d, idProduct=0002
    Jul 27 00:08:06 kate kernel: [16001.477941] usb 3-1: New USB device
    strings: Mfr=3, Product=1, SerialNumber=2
    Jul 27 00:08:06 kate kernel: [16001.477941] usb 3-1: Product:
    Back-UPS ES
    700 FW:829.D3 .I USB FW:D3
    Jul 27 00:08:06 kate kernel: [16001.477941] usb 3-1: Manufacturer: APC
    Jul 27 00:08:06 kate kernel: [16001.477941] usb 3-1: SerialNumber:
    3B0908X39177

    lsusb doesnt show it. (maybe because usb is statically compiled in?)
    kate:/# grep -w CONFIG_USB /boot/config-`uname -r`
    CONFIG_USB=y
    but the hiddevice is there
    kate:/# ls -la /dev/hid*
    crw-rw-r-- 1 root root 180, 96 27. Jul 00:08 /dev/hiddev0
    crw-rw---- 1 root root 250,  0 27. Jul 00:08 /dev/hidraw0

    tried using usbhid-ups driver and even with setting the option variable
    "cable" to "940-0127E" i had no luck.
    genericups with all possible upstypes doesnt work either.

    any ideas?
    chris


NUT' USB drivers use the libusb, so the usbfs on Linux (ie /dev/bus/usb/XXX/YYY)

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.

to make a quick test, launch the driver as root, ie:
/path/to/usbhid-ups -u root -a upsname

it should acquire the connexion and talk to the device.
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 it should be sufficient for the "nut" user (the exact user name depends on the distro...)

cheers,
Arnaud

i have no /dev/bus but /dev/usb/:
usb1            usb4            usbdev1.1_ep00  usbdev2.1_ep00
usbdev3.1_ep00  usbdev3.4_ep00  usbdev4.1_ep00  usbdev5.1_ep00  usbmon1
        usbmon4
usb2            usb5            usbdev1.1_ep81  usbdev2.1_ep81
usbdev3.1_ep81  usbdev3.4_ep81  usbdev4.1_ep81  usbdev5.1_ep81  usbmon2
        usbmon5
usb3            usbdev1.1       usbdev2.1       usbdev3.1
usbdev3.4       usbdev4.1       usbdev5.1       usbmon0         usbmon3

i didnt touch udev but nut is there..
kate:/etc/nut# find /etc/udev/rules.d/ -name ??-nut*
/etc/udev/rules.d/52-nut-usbups.rules
kate:/etc/nut# find /lib/udev/rules.d/ -name ??-nut*
kate:/etc/nut#

libusb seems to be installed according to dpkg.
kate:/etc/nut# dpkg -l libusb* | grep ii
ii  libusb-0.1-4                                2:0.1.12-13
                    userspace USB programming library
ii  libusb-1.0-0                                2:1.0.0-1
                    userspace USB programming library

putting "auto" as the port value doesnt work either.
kate:/etc/nut# tail -n 10 ups.conf
# To find out if your driver supports any extra settings, start it with
# the -h option and/or read the driver's documentation.
[UPS]
        driver = usbhid-ups
#       driver = genericups
#       upstype=12
#       port = /dev/hiddev0
        port = auto
        desc = "APC Back-UPS ES 700"
#       cable = 940-0127E

kate:/etc/nut# upsdrvctl -u root start
Network UPS Tools - UPS driver controller 2.4.1
Network UPS Tools - Generic HID driver 0.34 (2.4.1)
USB communication driver 0.31
No matching HID UPS found
Driver failed to start (exit status=1)

kate:/etc/nut# /lib/nut/usbhid-ups -u root -a UPS
Network UPS Tools - Generic HID driver 0.34 (2.4.1)
USB communication driver 0.31
No matching HID UPS found

(no nut-entries in syslog after running upsdrvctl or the driver itself)

further recommendations?

regards,
chris

--
Christoph Loesch - http://Loesch.me
OpenSource IT-Concepts & Services


_______________________________________________
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Reply via email to