<br><br><div class="gmail_quote">2009/8/12 Thomas Munn <span dir="ltr"><<a href="mailto:symgryph@gmail.com">symgryph@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
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:<br><br>addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00<br>
port 1 powered<div class="im"><br> port 2 addr 2: low speed, self powered, config 1, TRIPP LITE UPS(0x4003), Tripp Lite(0x09ae), rev 0.00<br><br></div>My ups.conf:<br><br>[tripplite]<br>driver=usbhid-ups<br>port=auto<br>
desc="igor"<br>
vendorid=09ae<br><br>So any other ideas welcome. I invoke usbhid-ups with the following:<br><br>./usbhid-ups -a tripplite -x explore -u root<br><br>I added -x vendorid=09ae and changed the vendorid to 4003 as well. No luck. Any ideas?<br>
</blockquote><div><br>this device (09ae:4003) is supported in 2.4.1 by usbhid-ups.<br>now, I'd like to see a driver debug output, ie<br>/path/to/usbhid-ups -DDDDD -a tripplite<br><br>using your above tripplite entry in ups.conf<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div class="h5"><br><div class="gmail_quote">On Wed, Aug 12, 2009 at 1:17 AM, Daniel O'Connor <span dir="ltr"><<a href="mailto:doconnor@gsoft.com.au" target="_blank">doconnor@gsoft.com.au</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>On Wed, 12 Aug 2009, Thomas Munn wrote:<br>
<br>
><br>
> I am having a devil of a time getting nut to work on freebsd. Here is<br>
> what I have done. I am trying to load the drivers, and here is my<br>
> ups.conf file:<br>
><br>
> [tripplite]<br>
> driver=trippliteesu<br>
> port=auto<br>
><br>
> When I dmesg on freebsd 7.1 for my usb device:<br>
><br>
> uhid0: <Tripp Lite TRIPP LITE UPS, class 0/0, rev 1.10/0.00, addr 2><br>
> on uhub0<br>
<br>
</div>I would bet the problem is that uhid is picking it up and the NUT driver<br>
uses libusb which requires ugen to attach to it (except in 8.0 where<br>
libusb is part of base and can attach to any device).<br>
<br>
A quick test would be to not load uhid and plug the UPS in, you should<br>
then see ugen grab it. After that NUT should work (you will need to<br>
chown the device node for it though as NUT runs as non-root by<br>
default).<br>
<br>
If that does work then do a send-pr with your usbdevs -v output and ask<br>
for the UPS to be blacklisted from uhid.<br>
<font color="#888888"><br>
--<br>
Daniel O'Connor software and network engineer<br>
for Genesis Software - <a href="http://www.gsoft.com.au" target="_blank">http://www.gsoft.com.au</a><br>
"The nice thing about standards is that there<br>
are so many of them to choose from."<br>
-- Andrew Tanenbaum<br>
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C<br>
</font></blockquote></div><br><br clear="all"><br></div></div><div><div></div><div class="h5">-- <br>-----------------------<br>Two Wheels Good, Four Wheels Bad<br>
</div></div><br>_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@lists.alioth.debian.org">Nut-upsuser@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser" target="_blank">http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser</a><br></blockquote></div><br><br>