<br><br><div class="gmail_quote">2012/7/19 Håvard Rabbe <span dir="ltr"><<a href="mailto:hrabbe@me.com" target="_blank">hrabbe@me.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi!<br></blockquote><div> <br>Hi <span class="gD">Håvard,</span><br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Info<br>
OS: TinyCore Linux 4.5.6<br>
NUT version: 2.6.4<br>
NUT innstallation method: source tarball<br>
Device name: Eaton Ellipse ups eco 1600 usb din (EL1600USBDIN)<br>
<br>
/usr/local/ups/etc/ups.conf file:<br>
<br>
[eaton]<br>
driver = usbhid-ups<br>
port = auto<br>
<br>
<br>
When I run:<br>
<br>
root@Dalen:/usr/local/ups/bin/upsdrvctl start eaton<br>
I get this error message:<br>
<br>
Network UPS Tools - UPS driver controller 2.6.4<br>
Network UPS Tools - Generic HID driver 0.37 (2.6.4)<br>
USB communication driver 0.31<br>
No matching HID UPS found<br>
Driver failed to start (exit status=1)<br>
<br>
<br>
I then run usbhid-ups<br>
<br>
root@Dalen:/usr/local/ups/etc# /usr/local/ups/bin/usbhid-ups -u root -DD -a eaton<br>
Network UPS Tools - Generic HID driver 0.37 (2.6.4)<br>
USB communication driver 0.31<br>
0.000000 debug level is '2'<br>
0.001244 upsdrv_initups...<br>
0.076965 Checking device (1D6B/0002) (001/001)<br>
0.077890 - VendorID: 1d6b<br>
0.078385 - ProductID: 0002<br>
0.078756 - Manufacturer: Linux 3.0.3-tinycore ehci_hcd<br>
0.079166 - Product: EHCI Host Controller<br>
0.079544 - Serial Number: 0000:00:10.4<br>
0.079946 - Bus: 001<br>
0.080346 Trying to match device<br>
0.080791 Device does not match - skipping<br>
0.081272 Checking device (18A5/0302) (001/002)<br>
0.082755 - VendorID: 18a5<br>
0.083199 - ProductID: 0302<br>
0.083640 - Manufacturer: Verbatim<br>
0.084033 - Product: STORE N GO<br>
0.084415 - Serial Number: 0000000000000580<br>
0.084785 - Bus: 001<br>
0.085185 Trying to match device<br>
0.085505 Device does not match - skipping<br>
0.085689 Checking device (1D6B/0001) (002/001)<br>
0.086084 - VendorID: 1d6b<br>
0.086437 - ProductID: 0001<br>
0.086486 - Manufacturer: Linux 3.0.3-tinycore uhci_hcd<br>
0.086629 - Product: UHCI Host Controller<br>
0.086772 - Serial Number: 0000:00:10.0<br>
0.086824 - Bus: 002<br>
0.086998 Trying to match device<br>
0.087055 Device does not match - skipping<br>
0.087165 Checking device (1D6B/0001) (003/001)<br>
0.087542 - VendorID: 1d6b<br>
0.087908 - ProductID: 0001<br>
0.088049 - Manufacturer: Linux 3.0.3-tinycore uhci_hcd<br>
0.088192 - Product: UHCI Host Controller<br>
0.088238 - Serial Number: 0000:00:10.1<br>
0.088386 - Bus: 003<br>
0.088431 Trying to match device<br>
0.088585 Device does not match - skipping<br>
0.088692 Checking device (0463/FFFF) (003/005)<br>
0.543897 - VendorID: 0463<br>
0.544300 - ProductID: ffff<br>
0.544419 - Manufacturer: EATON<br>
0.544627 - Product: Ellipse ECO<br>
0.544675 - Serial Number: 000000000<br>
0.544719 - Bus: 003<br>
0.544783 Trying to match device<br>
0.544927 Device matches<br>
0.617937 HID descriptor length 909<br>
3.849957 Report Descriptor size = 909<br>
3.851661 Using subdriver: MGE HID 1.31<br>
3.896977 Path: UPS.BatterySystem.Battery.AudibleAlarmControl, Type: Feature, ReportID: 0x20, Offset: 0, Size: 8, Value: 2<br>
(...)<br></blockquote><div><br>your first issue, above, is a privilege one.<br>that is, the nut configured user has not enough rights to access the device in RW mode.<br>this is addressed on Linux through udev, and the helper files found in scripts/udev, in the source tree.<br>
just copy scripts/udev/52-nut-usbups.rules to /lib/udev/rules.d, and call <br>$ udevadm trigger --subsystem-match=usb --action=change<br><br>then unplug/replug your UPS USB cord, and everything should be fixed.<br><br></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> 8.060118 upsdrv_updateinfo...<br>
8.311936 libusb_get_interrupt: Connection timed out<br>
8.312133 Got 0 HID objects...<br>
<br>
<br>
It seems like the ups is detected, but not receiving any hid objects.<br></blockquote><div><br>nothing wrong there, it's just that the device has no change to report by itself, between the polling requests from the driver...<br>
</div>cheers,<br clear="all"></div>Arnaud<br>-- <br>Linux / Unix / Opensource Engineering Expert - Eaton - <a href="http://opensource.eaton.com" target="_blank">http://opensource.eaton.com</a><br>Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org" target="_blank">http://www.networkupstools.org</a><br>
Debian Developer - <a href="http://www.debian.org" target="_blank">http://www.debian.org</a><br>Free Software Developer - <a href="http://arnaud.quette.fr" target="_blank">http://arnaud.quette.fr</a><br><br>