Re: UPS on USB not detected
On Sun, Nov 07, 2010 at 12:19:12PM -0600, Hugo Vanwoerkom wrote:
> lee wrote:
> >Hi,
> >
> >my UPS (HP T750 intl) which is plugged into an USB port with the
> >supplied USB cable is not detected. Nothing happens when I plug it out
> >or in, and I tried different USB ports. It´s the only USB device
> >connected, and lsusb only shows the host controllers but no USB
> >devices.
>
>
> <snip>
>
> You're in luck. NUT in its stable compat supports the HP T750 intl
> with driver usbhid-ups.
That probably only works when the USV is detected as an USB device
first.
> Install NUT and you're all set.
I´ve nut installed, but it doesn´t work:
root@yun:~# lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
root@yun:~# /lib/nut/usbhid-ups -D -D -a myups
Network UPS Tools - Generic HID driver 0.34 (2.4.3)
USB communication driver 0.31
0.000000 debug level is '2'
0.000990 upsdrv_initups...
0.001382 Checking device (1D6B/0002) (003/001)
0.001446 - VendorID: 1d6b
0.001458 - ProductID: 0002
0.001468 - Manufacturer: unknown
0.001478 - Product: unknown
0.001487 - Serial Number: unknown
0.001496 - Bus: 003
0.001505 Trying to match device
0.001533 Device does not match - skipping
0.001550 Checking device (1D6B/0002) (002/001)
0.001582 - VendorID: 1d6b
0.001593 - ProductID: 0002
0.001602 - Manufacturer: unknown
0.001611 - Product: unknown
0.001620 - Serial Number: unknown
0.001629 - Bus: 002
0.001638 Trying to match device
0.001649 Device does not match - skipping
0.001662 Checking device (1D6B/0003) (001/001)
0.001693 - VendorID: 1d6b
0.001703 - ProductID: 0003
0.001712 - Manufacturer: unknown
0.001721 - Product: unknown
0.001731 - Serial Number: unknown
0.001740 - Bus: 001
0.001748 Trying to match device
0.001759 Device does not match - skipping
0.001774 No appropriate HID device found
0.001787 No matching HID UPS found
As you can see, the USV is not detected. It´s plugged in, though.
Reply to: