Aaron Turner via Nut-upsuser <[email protected]> writes:
> $ upsdrvctl start ups > Network UPS Tools upsdrvctl - UPS driver controller 2.8.3 release > Network UPS Tools 2.8.3 release - Generic HID driver 0.62 > USB communication driver (libusb 1.0) 0.50 > libusb1: Could not open any HID devices: no USB buses (or devices) found > No matching HID UPS found > Driver failed to start (exit status=1) > > Confused by this since I'm running the above command as root and > nut-scanner -U works fine? I run nut on NetBSD, but my UPS units have real serial ports (well, maybe TTL levels instead of true RS232), so I don't deal with USB bus enumeration with nut. However, I do have to worry about serial port permissions. So I'm guessing, but: This sounds like permissions. You said you ran it as root, but upsdrvctl (TIL that the rc.d scripts on NetBSD call upsdrvctl) seems to start the driver as nut. Eg., my driver is nut 12211 0.0 0.0 25264 1196 ? Ss Wed12PM 15:22.10 /usr/pkg/libexec/nut/bestfortress -a [redacted-ups-name] So, I would see if you can authorize the usbhid driver to deal with ugen and bus enumeration, or figure out how to let upsdrvctl start it up as root and drop privs if it does. _______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
