I finally solved it, if anyone else has a tripplite: use the following method on freebsd:
First, you have to recompile the kernel to NOT use usbhid. http://www.freebsd.org/doc/en/books/handbook/kernelconfig-building.html Install the kernel, reboot the system. Create the following config files: /usr/local/etc/nut/ups.conf [tripplite] driver = usbhid-ups port = auto vendorid = 09ae desc "Igor" copy the upsd.conf.sample to upsd.conf file, change the 'listen' address to appropriate values chown the file to uucp (the default user that upsd becomes) edit the /usr/local/etc/rc.d/nut configuration file to start the driver thingy as root (to get around the problem of driver permissions) change the nut_prestart to have -u root edit the /etc/rc.conf file to start nut: nut_enable="yes" On Wed, Aug 12, 2009 at 3:37 AM, Thomas Munn <symgr...@gmail.com> wrote: > I did recompile the kernel, per advice, but I still don't see any drivers > (I removed usbhid from my kernel)...the device now looks like: > > addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), > Intel(0x0000), rev 1.00 > port 1 powered > port 2 addr 2: low speed, self powered, config 1, TRIPP LITE UPS(0x4003), > Tripp Lite(0x09ae), rev 0.00 > > My ups.conf: > > [tripplite] > driver=usbhid-ups > port=auto > desc="igor" > vendorid=09ae > > So any other ideas welcome. I invoke usbhid-ups with the following: > > ./usbhid-ups -a tripplite -x explore -u root > > I added -x vendorid=09ae and changed the vendorid to 4003 as well. No luck. > Any ideas? > > Thomas > > On Wed, Aug 12, 2009 at 1:17 AM, Daniel O'Connor <docon...@gsoft.com.au>wrote: > >> On Wed, 12 Aug 2009, Thomas Munn wrote: >> >> > >> > I am having a devil of a time getting nut to work on freebsd. Here is >> > what I have done. I am trying to load the drivers, and here is my >> > ups.conf file: >> > >> > [tripplite] >> > driver=trippliteesu >> > port=auto >> > >> > When I dmesg on freebsd 7.1 for my usb device: >> > >> > uhid0: <Tripp Lite TRIPP LITE UPS, class 0/0, rev 1.10/0.00, addr 2> >> > on uhub0 >> >> I would bet the problem is that uhid is picking it up and the NUT driver >> uses libusb which requires ugen to attach to it (except in 8.0 where >> libusb is part of base and can attach to any device). >> >> A quick test would be to not load uhid and plug the UPS in, you should >> then see ugen grab it. After that NUT should work (you will need to >> chown the device node for it though as NUT runs as non-root by >> default). >> >> If that does work then do a send-pr with your usbdevs -v output and ask >> for the UPS to be blacklisted from uhid. >> >> -- >> Daniel O'Connor software and network engineer >> for Genesis Software - http://www.gsoft.com.au >> "The nice thing about standards is that there >> are so many of them to choose from." >> -- Andrew Tanenbaum >> GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C >> > > > > -- > ----------------------- > Two Wheels Good, Four Wheels Bad > -- ----------------------- Two Wheels Good, Four Wheels Bad
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser