Hello Charles,
Thank you for your suggestion, however it didn't help. I was running it as
root but I went ahead and added the -u root anyways. Nothing changed. So
part or all the problem is that I don't have the "libhidups or
libhid.usermap" files that the man page talks about:
You also need to install manually the legacy hotplug files (libhidups and
libhid.usermap, generally in /etc/hotplug/usb/), or the udev file
(nut-usbups.rules, generally in /etc/udev/rules.d/) to address the
permission settings problem. For more information, refer to the README file
in nut/scripts/hotplug or nut/scripts/udev.
How can I get them and do I really need them?
I copied and modified "/lib/udev/rules.d/52-nut-usbups.rules" and
added the
following:
e.g. TrippLite INTERNET350U - usbhid-ups
ATTR{idVendor}=="09ae", ATTR{idProduct}=="2010",
MODE="664", GROUP="nut"
Thank you for your time and Patience
On Fri, Jun 13, 2014 at 8:59 PM, Charles Lepple <clepple at gmail.com>
wrote:
> On Jun 13, 2014, at 4:45 PM, Bossard wrote:
>
> > No matching HID UPS found
> >
> >
> > Driver failed to start (exit status=1)
> >
> >
> > So I tried 'usbhid-ups -x productid=2010' and received the
same error.
>
> Same exact error?
>
> I suspect it's a permissions error the second time. Add "-u
root" to the
> command line - since this was not a known VendorID:ProductID pair at
> release time, the udev/hotplug files don't adjust the permissions
> automatically, which can cause the "No matching HID UPS found
error".
>
> A better solution for the long term: you could copy one of the other
> 09ae:xxxx lines in your NUT udev configuration. (You'll need to unplug
and
> re-plug the USB cable for it to take effect.)
>
> --
> Charles Lepple
> clepple at gmail
>
>
>
>
--
Cya
Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140614/c3231648/attachment.html>
On Jun 14, 2014, at 8:06 PM, Bossard wrote:> Hello Charles, > > Thank you for your suggestion, however it didn't help. I was running it as root but I went ahead and added the -u root anyways.The way to think about the "-u root" flag is "stay running as root". When started as root, NUT runs the drivers under an unprivileged system user ID (usually "nut", unless the "-u" flag is passed). Unfortunately, if "-u root" did not make a difference, then the udev rules aren't going to help, either (they set up the permissions for the unprivileged "nut" user). Can you post the exact output of "usbhid-ups -u root -x productid=2010 -DD -a <UPS-name>"?> Nothing changed. So part or all the problem is that I don't have the "libhidups or libhid.usermap" files that the man page talks about: > > You also need to install manually the legacy hotplug files (libhidups and libhid.usermap, generally in /etc/hotplug/usb/), or the udev file (nut-usbups.rules, generally in /etc/udev/rules.d/) to address the permission settings problem. For more information, refer to the README file in nut/scripts/hotplug or nut/scripts/udev. > > How can I get them and do I really need them?udev replaced the functionality of hotplug (with different syntax), so if you are running udev, you don't need to worry about the hotplug files. Theoretically, the package for NUT should only include the relevant files for your distribution. Since NUT 2.4.3 is getting a little old, I'm not entirely sure what Linux distribution you are running (and thus, whether we should be worrying about hotplug). Can you provide some more information on that? Distribution and version would be good; bonus points for versions of things like udev, libusb, the kernel, etc.> I copied and modified "/lib/udev/rules.d/52-nut-usbups.rules" and added the following: > > e.g. TrippLite INTERNET350U - usbhid-ups > ATTR{idVendor}=="09ae", ATTR{idProduct}=="2010", MODE="664", GROUP="nut" > > > > Thank you for your time and Patience > > > > On Fri, Jun 13, 2014 at 8:59 PM, Charles Lepple <clepple at gmail.com> wrote: > On Jun 13, 2014, at 4:45 PM, Bossard wrote: > > > No matching HID UPS found > > > > > > Driver failed to start (exit status=1) > > > > > > So I tried 'usbhid-ups -x productid=2010' and received the same error. > > Same exact error? > > I suspect it's a permissions error the second time. Add "-u root" to the command line - since this was not a known VendorID:ProductID pair at release time, the udev/hotplug files don't adjust the permissions automatically, which can cause the "No matching HID UPS found error". > > A better solution for the long term: you could copy one of the other 09ae:xxxx lines in your NUT udev configuration. (You'll need to unplug and re-plug the USB cable for it to take effect.) > > -- > Charles Lepple > clepple at gmail > > > > > > > -- > Cya > > Eric-- Charles Lepple clepple at gmail -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140615/330fc27e/attachment.html>
On Jun 21, 2014, at 10:21 AM, Bossard <ebossard at gmail.com> wrote:> On Sun, Jun 15, 2014 at 10:19 AM, Charles Lepple <clepple at gmail.com> wrote: >> usbhid-ups -u root -x productid=2010 -DD -a <UPS-name> > > Hello Charles, > > Sorry it took me so long to post: > > (The output of:) /lib/nut/usbhid-ups -u root -x productid=2010 -DD -a tripplite > > Network UPS Tools - Generic HID driver 0.34 (2.4.3) > > USB communication driver 0.31 > > 0.000000 debug level is '2' > 0.000700 upsdrv_initups... > 0.130746 Checking device (1D6B/0001) (005/001) > 0.130824 - VendorID: 1d6b > 0.130836 - ProductID: 0001 > 0.130845 - Manufacturer: Linux 2.6.32-5-686 uhci_hcd^ What Linux distribution are you running?> 0.148284 Checking device (09AE/2010) (002/113) > 0.181081 - VendorID: 09ae > 0.181104 - ProductID: 2010 > 0.181114 - Manufacturer: Tripp Lite > 0.181124 - Product: Tripp Lite UPS > 0.181135 - Serial Number: unknown > 0.181145 - Bus: 002 > 0.181154 Trying to match device > 0.181242 Device does not match - skippingI really don't see how this could happen when specifying that productid option. I don't remember any recent bug fixes that could cause things to work differently if you add "productid=2010" to the ups.conf file, but that was reported to work with 2.4.3 in this email: http://lists.alioth.debian.org/pipermail/nut-upsuser/2011-March/006695.html That email also confirms that the 2010 productid does, in fact, work out-of-the-box with 2.6.0. Other than trying the ups.conf route, I would recommend getting a newer version of NUT (this version is over four years old), either through your distribution's "backports" system, or by building from source. Again, since you haven't mentioned what system you are running, I don't have any more specific recommendations than that. -- Charles Lepple clepple at gmail