On 05/03/2011, at 20:16, Arjen de Korte wrote:
We search for a VendorID / ProductID combination. The one you
posted earlier
idVendor = 0x0463
idProduct = 0x
is one of the combinations that are supported by the usbhid-ups
driver (it is used for all MGE / Eaton devices
Citeren Frederic Praca frederic.pr...@freebsd-fr.org:
I wondered how the USB UPS are detected and if my UPS is described in
the source code. Any idea of where I should take a look ?
We search for a VendorID / ProductID combination. The one you posted earlier
idVendor = 0x0463
idProduct =
Great !! It worked.
In fact, the '-u' parameter you gave me allowed me to test as root and
see it working.
Changing owner to /dev/usb/4.2.* seemed to be insufficient and after
changing the owner of the /dev/ugen4.2.* link, it finally got detected.
Finally, it was easier than I thought and I should
On 05/03/2011, at 20:16, Arjen de Korte wrote:
We search for a VendorID / ProductID combination. The one you posted earlier
idVendor = 0x0463
idProduct = 0x
is one of the combinations that are supported by the usbhid-ups driver (it is
used for all MGE / Eaton devices with USB HID
Citeren frederic.pr...@free.fr:
I have to manage an Eaton Ellipse ASR 750 VA UPS under a FreeBSD 8.2 server.
I used nut from ports collection but I'm unable to detect the UPS by
USB cable.
[...]
Any idea of how to make it works ?
Did you follow the FreeBSD installation HOWTO that's
On 04/03/2011, at 21:16, Arjen de Korte wrote:
Any idea of how to make it works ?
Did you follow the FreeBSD installation HOWTO that's mentioned in the
documentation?
http://people.freebsd.org/~thierry/nut_FreeBSD_HowTo.txt
I don't think this will work due to the change to a new USB
As I feared, changing the group for ugen4.2 had no effect.
I used to try 'usbhid-ups' by hand under root account.
So the message still remains the same :
# ./usbhid-ups -a eaton
Network UPS Tools - Generic HID driver 0.35 (2.6.0)
USB communication driver 0.31
No matching HID UPS found
I wondered
7 matches
Mail list logo
