[Nut-upsuser] Problem connecting to eaton ups. No matching HID UPS found. Driver failed to start(exit status=1)
Håvard Rabbe
hrabbe at me.com
Thu Jul 19 23:33:00 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.
Any ideas why $ udevadm trigger --subsystem-match=usb --action=change is not working?
Regards,
Håvard Rabbe
On Jul 19, 2012, at 11:03 AM, Arnaud Quette wrote:
>
>
> 2012/7/19 Håvard Rabbe <hrabbe at me.com>
> Hi!
>
> Hi Håvard,
>
> Info
> OS: TinyCore Linux 4.5.6
> NUT version: 2.6.4
> NUT innstallation method: source tarball
> Device name: Eaton Ellipse ups eco 1600 usb din (EL1600USBDIN)
>
> /usr/local/ups/etc/ups.conf file:
>
> [eaton]
> driver = usbhid-ups
> port = auto
>
>
> When I run:
>
> root at Dalen:/usr/local/ups/bin/upsdrvctl start eaton
> I get this error message:
>
> Network UPS Tools - UPS driver controller 2.6.4
> Network UPS Tools - Generic HID driver 0.37 (2.6.4)
> USB communication driver 0.31
> No matching HID UPS found
> Driver failed to start (exit status=1)
>
>
> I then run usbhid-ups
>
> root at Dalen:/usr/local/ups/etc# /usr/local/ups/bin/usbhid-ups -u root -DD -a eaton
> Network UPS Tools - Generic HID driver 0.37 (2.6.4)
> USB communication driver 0.31
> 0.000000 debug level is '2'
> 0.001244 upsdrv_initups...
> 0.076965 Checking device (1D6B/0002) (001/001)
> 0.077890 - VendorID: 1d6b
> 0.078385 - ProductID: 0002
> 0.078756 - Manufacturer: Linux 3.0.3-tinycore ehci_hcd
> 0.079166 - Product: EHCI Host Controller
> 0.079544 - Serial Number: 0000:00:10.4
> 0.079946 - Bus: 001
> 0.080346 Trying to match device
> 0.080791 Device does not match - skipping
> 0.081272 Checking device (18A5/0302) (001/002)
> 0.082755 - VendorID: 18a5
> 0.083199 - ProductID: 0302
> 0.083640 - Manufacturer: Verbatim
> 0.084033 - Product: STORE N GO
> 0.084415 - Serial Number: 0000000000000580
> 0.084785 - Bus: 001
> 0.085185 Trying to match device
> 0.085505 Device does not match - skipping
> 0.085689 Checking device (1D6B/0001) (002/001)
> 0.086084 - VendorID: 1d6b
> 0.086437 - ProductID: 0001
> 0.086486 - Manufacturer: Linux 3.0.3-tinycore uhci_hcd
> 0.086629 - Product: UHCI Host Controller
> 0.086772 - Serial Number: 0000:00:10.0
> 0.086824 - Bus: 002
> 0.086998 Trying to match device
> 0.087055 Device does not match - skipping
> 0.087165 Checking device (1D6B/0001) (003/001)
> 0.087542 - VendorID: 1d6b
> 0.087908 - ProductID: 0001
> 0.088049 - Manufacturer: Linux 3.0.3-tinycore uhci_hcd
> 0.088192 - Product: UHCI Host Controller
> 0.088238 - Serial Number: 0000:00:10.1
> 0.088386 - Bus: 003
> 0.088431 Trying to match device
> 0.088585 Device does not match - skipping
> 0.088692 Checking device (0463/FFFF) (003/005)
> 0.543897 - VendorID: 0463
> 0.544300 - ProductID: ffff
> 0.544419 - Manufacturer: EATON
> 0.544627 - Product: Ellipse ECO
> 0.544675 - Serial Number: 000000000
> 0.544719 - Bus: 003
> 0.544783 Trying to match device
> 0.544927 Device matches
> 0.617937 HID descriptor length 909
> 3.849957 Report Descriptor size = 909
> 3.851661 Using subdriver: MGE HID 1.31
> 3.896977 Path: UPS.BatterySystem.Battery.AudibleAlarmControl, Type: Feature, ReportID: 0x20, Offset: 0, Size: 8, Value: 2
> (...)
>
> your first issue, above, is a privilege one.
> that is, the nut configured user has not enough rights to access the device in RW mode.
> this is addressed on Linux through udev, and the helper files found in scripts/udev, in the source tree.
> just copy scripts/udev/52-nut-usbups.rules to /lib/udev/rules.d, and call
> $ udevadm trigger --subsystem-match=usb --action=change
>
> then unplug/replug your UPS USB cord, and everything should be fixed.
>
> 8.060118 upsdrv_updateinfo...
> 8.311936 libusb_get_interrupt: Connection timed out
> 8.312133 Got 0 HID objects...
>
>
> It seems like the ups is detected, but not receiving any hid objects.
>
> nothing wrong there, it's just that the device has no change to report by itself, between the polling requests from the driver...
>
> 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/707a2cf5/attachment.html>
More information about the Nut-upsuser
mailing list