2012/4/5 Peter Tuhársky <[email protected]> > Hi, >
Hi Peter I tested productid=0x1fe7 for usbhid-ups and it did not help. Do I need to > compile a development version of NUT first? > > Or what should I do? > mea culpa: the productID was obviously missing, but the VendorID too. I've just committed the patch in trunk (r3525) which adds USB/HID (Eaton mode) support for HP: http://trac.networkupstools.org/projects/nut/changeset/3525 (the changeset should be available in ~1h) there are still a few TODO and tests needed, but I've been retaining this commit for too long now. >From there, you can either use the trunk or simply patch your version with the above... Dňa 31.03.2012 20:40, Arnaud Quette wrote / napísal(a): > > 2012/3/30 Peter Tuhársky<[email protected]> >> >> Hi, Arnaud >>> >>> >> Hi Peter >> >> Thank You for Your kind answer. >> >>> >>> I attempted to use USB, as You suggested. After connecting the cable, >>> kernel detects HP R 5000 as HID like this: >>> >>> [ 1701.100025] usb 2-1: new full speed USB device using ohci_hcd and >>> address 2 >>> [ 1701.324982] usb 2-1: New USB device found, idVendor=03f0, >>> idProduct=1fe7 >>> [ 1701.324985] usb 2-1: New USB device strings: Mfr=1, Product=2, >>> SerialNumber=4 >>> [ 1701.324989] usb 2-1: Product: HP R5000 >>> [ 1701.324991] usb 2-1: Manufacturer: HP >>> [ 1701.324992] usb 2-1: SerialNumber: 3C81520083 >>> [ 1701.325147] usb 2-1: configuration #1 chosen from 1 choice >>> [ 1701.391326] usbcore: registered new interface driver hiddev >>> [ 1701.433359] generic-usb: probe of 0003:03F0:1FE7.0001 failed with >>> error >>> -22 >>> [ 1701.433395] usbcore: registered new interface driver usbhid >>> [ 1701.433460] usbhid: v2.6:USB HID core driver >>> >>> Although generic-usb fails with error -22, I hope this should not be a >>> problem, since next lines, usbcore and usbhid show no no sign of trouble. >>> >>> >> not sure why you get this. I'll have to go back to the kernel soon... >> >> >> I set ups.conf like this: >>> >>> protocol = usbhid-ups >>> port = auto >>> >>> However, starting upsdrvctl shows this error: >>> >>> Network UPS Tools - UPS driver controller 2.4.3 >>> Network UPS Tools - Generic HID driver 0.34 (2.4.3) >>> USB communication driver 0.31 >>> No matching HID UPS found >>> Driver failed to start (exit status=1) >>> >>> >>> Should I use some exact vendor specification in ups.conf and if, what >>> should it be? Or is there other source of trouble? >>> >>> >> R5000 (USB productID 0x1fe7) is part of my (still underway) patch :-/ >> adding "productid=0x1fe7" to your usp.conf will indeed fix it. >> >> note that I've still a few fixes staging and tests needed on my side, even >> for HID. >> so expect to see a few buggy values, like for battery.temperature. >> >> cheers, >> Arnaud >> >> cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/
_______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
