Thomas, did you try running the driver with "-D"? Were there any kernel log messages?
-- - Charles Lepple On Thu, Aug 13, 2009 at 8:39 PM, Charles Lepple<[email protected]> wrote: > Were there any kernel log entries about USB errors? I'm not sure what > FreeBSD does in this regard, but if the cable disconnected completely, there > will probably be an enumeration message. > For usbhid-ups, you can kill the driver and start it from the command line > with an extra "-D" to enable debugging. However, the driver will run in the > foreground. > On Aug 13, 2009, at 8:12 PM, Thomas Munn wrote: > > I am using usbhid-ups > > > On Thu, Aug 13, 2009 at 8:11 PM, Charles Lepple <[email protected]> wrote: >> >> On Aug 13, 2009, at 3:46 PM, Thomas Munn wrote: >> >>> I have successfully compiled NUT, and have noticed usb weirdness. The >>> machine disconnected at 10:25 this morning tripplite was claiming 'stale >>> data'. I noticed it this morning after trying to look at things. I >>> 'replugged' the ups back into the usb port and it was fine. I am running >>> 2.4.1, freebsd, tripplite Su2200XLA. I did notice that the usb cable was a >>> little wobbly. Any other ways to see whats going on? here are a few of my >>> log entries: >> >> Which driver are you using? > > _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

