[Nut-upsuser] Problem connecting to eaton ups. No matching HID UPS found. Driver failed to start(exit status=1)
Arnaud Quette
aquette.dev at gmail.com
Fri Jul 20 11:25:58 UTC 2012
Hi
> I have now placed the 52-nut-usbups.rules in /lib/udev/rules.d and
> called $ udevadm trigger --subsystem-match=usb --action=change, but with no
> luck.
> I get the same error after unplug/replug of usb cable.
>
> If I do this it will work:
>
> root at Dalen:/dev/bus/usb/003# lsusb
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd
> Bus 003 Device 002: ID 0463:ffff MGE UPS Systems UPS
>
> chmod 0777 /dev/bus/usb/003/002
>
> after this upsdrvctl will start. And so far upsd and upsmon is working.
>
>
> So its definitely a permission problem.
>
indeed
> Any ideas why $ udevadm trigger --subsystem-match=usb --action=change is
> not working?
>
you may try to unplug the usb cable, then use "udevadm control
--reload-rules", then replug the usb cable.
note that depending on your exact udev version, rules files may be located
either in /etc/udev/rules.d or /lib/udev/rules.d
cheers,
Arnaud
--
Linux / Unix / Opensource Engineering Expert - Eaton -
http://opensource.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120720/fef20d0a/attachment.html>
More information about the Nut-upsuser
mailing list