On 07/06/2017 02:18 AM, Charles Lepple wrote:> On Jul 5, 2017, at 5:34 PM, Ambrogio Coletti <ambrojohn at gmail.com > <mailto:ambrojohn at gmail.com>> wrote: >> >> From section 4.23 of the Developer Guide: >> >> "There are a few USB UPS devices that are not HID devices. These >> devices typically implement some version of the manufacturer?s >> serial protocol over USB (which is a really dumb idea, by the way). >> An example is the Tripplite USB. Such devices are not supported by >> the usbhid-ups driver, and are not covered in this document." >> >> I guess that applies to me? > > No, but my original comment does: > > "The Protocol 1330 support was added after 2.7.4 was released. You > might be able to use a 2.7.4 tarball with "productid = 1330" in > ups.conf, but voltages might be off by a factor of 10. *You will also > need to adjust the udev files manually to fix /dev/bus/usb permissions.*" > > Manuel: did you happen to regenerate the udev files, or use one of the > Buildbot tarballs? We typically don't bother to do that until "make > dist" before a release (since the rules files are generated from *.in > files based on configure parameters), so your package might still have > the rules file from 2.7.4 (which does not include protocol 1330).yes, the package installed by Mr. Coletti includes the new rules: # TrippLite [...] # e.g. TrippLite ECO550UPS - usbhid-ups ATTR{idVendor}=="09ae", ATTR{idProduct}=="1010", MODE="664", GROUP="dialout" # e.g. TrippLite SU3000LCD2UHV - usbhid-ups ATTR{idVendor}=="09ae", ATTR{idProduct}=="1330", MODE="664", GROUP="dialout" # e.g. TrippLite OMNI1000LCD - usbhid-ups ATTR{idVendor}=="09ae", ATTR{idProduct}=="2005", MODE="664", GROUP="dialout" [...] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170706/166c328d/attachment.html>
On 07/06/2017 02:23 AM, Manuel Wolfshant wrote:> On 07/06/2017 02:18 AM, Charles Lepple wrote: >> On Jul 5, 2017, at 5:34 PM, Ambrogio Coletti <ambrojohn at gmail.com >> <mailto:ambrojohn at gmail.com>> wrote: >>> >>> From section 4.23 of the Developer Guide: >>> >>> "There are a few USB UPS devices that are not HID devices. These >>> devices typically implement some version of the manufacturer?s >>> serial protocol over USB (which is a really dumb idea, by the way). >>> An example is the Tripplite USB. Such devices are not supported by >>> the usbhid-ups driver, and are not covered in this document." >>> >>> I guess that applies to me? >> >> No, but my original comment does: >> >> "The Protocol 1330 support was added after 2.7.4 was released. You >> might be able to use a 2.7.4 tarball with "productid = 1330" in >> ups.conf, but voltages might be off by a factor of 10. *You will also >> need to adjust the udev files manually to fix /dev/bus/usb >> permissions.*" >> >> Manuel: did you happen to regenerate the udev files, or use one of >> the Buildbot tarballs? We typically don't bother to do that until >> "make dist" before a release (since the rules files are generated >> from *.in files based on configure parameters), so your package might >> still have the rules file from 2.7.4 (which does not include protocol >> 1330). > yes, the package installed by Mr. Coletti includes the new rules: > > # TrippLite > [...] > # e.g. TrippLite ECO550UPS - usbhid-ups > ATTR{idVendor}=="09ae", ATTR{idProduct}=="1010", MODE="664", > GROUP="dialout" > # e.g. TrippLite SU3000LCD2UHV - usbhid-ups > ATTR{idVendor}=="09ae", ATTR{idProduct}=="1330", MODE="664", > GROUP="dialout" > # e.g. TrippLite OMNI1000LCD - usbhid-ups > ATTR{idVendor}=="09ae", ATTR{idProduct}=="2005", MODE="664", > GROUP="dialout" > [...]I forgot to mention that the above is a quote from /lib/udev/rules.d/62-nut-usbups.rules -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170706/f3a8f849/attachment-0001.html>
On Jul 5, 2017, at 7:23 PM, Manuel Wolfshant wrote:> >> Manuel: did you happen to regenerate the udev files, or use one of the Buildbot tarballs? We typically don't bother to do that until "make dist" before a release (since the rules files are generated from *.in files based on configure parameters), so your package might still have the rules file from 2.7.4 (which does not include protocol 1330). > yes, the package installed by Mr. Coletti includes the new rules:Thanks for checking. (I really should set up a Fedora VM and/or learn how to use alien to check on things like this.) Does udev automatically reload when the rules files change? The Debian/Ubuntu packages are supposed to run "udevadm trigger --subsystem-match=usb --action=change" as part of the postinst. (I think udev rescans the rules when a device is plugged in, so unplugging and re-plugging the USB cable should work, too.)
On 07/06/2017 02:38 AM, Charles Lepple wrote:> On Jul 5, 2017, at 7:23 PM, Manuel Wolfshant wrote: >>> Manuel: did you happen to regenerate the udev files, or use one of the Buildbot tarballs? We typically don't bother to do that until "make dist" before a release (since the rules files are generated from *.in files based on configure parameters), so your package might still have the rules file from 2.7.4 (which does not include protocol 1330). >> yes, the package installed by Mr. Coletti includes the new rules: > Thanks for checking. (I really should set up a Fedora VM and/or learn how to use alien to check on things like this.)I was tempted to say that alien sucks donkey balls but that would not be polite, would it ? Beware that despite the heavy backporting done by RH, fedora is far ahead of RHEL 7 and very far ahead of RHEL 6 ( especially in terms of libraries )> > Does udev automatically reload when the rules files change? The Debian/Ubuntu packages are supposed to run "udevadm trigger --subsystem-match=usb --action=change" as part of the postinst.I've stolen from the fedora package the following gem which , AFAIK ( I am no udev wizard.. ) does the same thing: postinstall scriptlet (using /bin/sh): /sbin/ldconfig udevadm control --reload ||:> (I think udev rescans the rules when a device is plugged in, so unplugging and re-plugging the USB cable should work, too.)you are 100% right here, AFAIK