Hello I am trying to install the NUT on CentOS 6 (2.6.32-696.3.1.el6.x86_64). First I installed it using: yum install epel-release --enablerepo=extras yum install nut And when I run it by: sbin/upsdrvctl start (that's where it installed it using the package) I had the following message: "This TrippLite device (09ae:1330) is not (or perhaps not yet) supported by usbhid-ups. [...]" but my device (SU2200RTXLCD2U) is supported, as clearly state here <http://networkupstools.org/stable-hcl.html>. Then I thought I needed the last src code (2.7.4), hence I built it for my machine, but when I run it by: /usr/local/ups/sbin/upsdrvctl start I had, in order, this message "writepid: fopen /var/state/ups/usbhid-ups-trippliteups.pid: Permission denied" and...the same message above about the not supported device! What's wrong in there? Regards Ambrogio P.S. I also performed the installation notes for the driver in here <http://networkupstools.org/docs/man/usbhid-ups.html>. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170623/10a99997/attachment.html>
On 06/24/2017 12:50 AM, Ambrogio Coletti wrote:> Hello > > I am trying to install the NUT on CentOS 6 (2.6.32-696.3.1.el6.x86_64). > > First I installed it using: > yum install epel-release --enablerepo=extras > yum install nut > > And when I run it by: > sbin/upsdrvctl start > (that's where it installed it using the package) > > I had the following message: > "This TrippLite device (09ae:1330) is not (or perhaps not yet) > supported by usbhid-ups. [...]" > but my device (SU2200RTXLCD2U) is supported, as clearly state here > <http://networkupstools.org/stable-hcl.html>. > > Then I thought I needed the last src code (2.7.4), hence I built it > for my machine, but when I run it by: > /usr/local/ups/sbin/upsdrvctl start > > I had, in order, this message > "writepid: fopen /var/state/ups/usbhid-ups-trippliteups.pid: > Permission denied"the permissions used by the driver are not those set on the directory where it tries to write for testing purposes you could try to run it as root in order to avoid conflicts, if you did not already do that, please also remove the package installed from EPEL prior to testing.> and...the same message above about the not supported device! > > What's wrong in there? >the fact that on a package-managed distribution you are using self-compiled applications, without using the correct settings at compile time :). If you are not willing to use the packages I provide, at least take inspiration from the spec file included in https://wolfy.fedorapeople.org/nut/nut-2.7.4-4.el6.wolfy.1.src.rpm ( the %build and %install sections ). Although you'd better rebuild that src.rpm if you are afraid to use the binaries directly. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170624/10112e02/attachment.html>
On Jun 23, 2017, at 5:50 PM, Ambrogio Coletti <ambrojohn at gmail.com> wrote:> > "This TrippLite device (09ae:1330) is not (or perhaps not yet) supported by usbhid-ups. [...]" > but my device (SU2200RTXLCD2U) is supported, as clearly state here.No, the HCL also mentions "protocol 4001". For Tripp-Lite, a USB PID other than 0001 is generally the protocol number. So your SU2200* model is different. https://github.com/networkupstools/nut/issues/64> Then I thought I needed the last src code (2.7.4), hence I built it for my machine, but when I run it by: > /usr/local/ups/sbin/upsdrvctl startThe 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. If you do choose to build using the latest source code from Git, be aware that you will need more tools, as specified in the Developer Guide: http://networkupstools.org/docs/developer-guide.chunked/ar01s03.html#building It may be easier to use the 2.7.4 tarball, and add the patch which introduces Protocol 1330 support to the RPM spec file: https://github.com/networkupstools/nut/commit/4eff5b7068e9873ce11b5a296f403e8cdf0e3580
On 06/24/2017 04:52 AM, Charles Lepple wrote:> On Jun 23, 2017, at 5:50 PM, Ambrogio Coletti <ambrojohn at gmail.com> wrote: >> "This TrippLite device (09ae:1330) is not (or perhaps not yet) supported by usbhid-ups. [...]" >> but my device (SU2200RTXLCD2U) is supported, as clearly state here. > No, the HCL also mentions "protocol 4001". For Tripp-Lite, a USB PID other than 0001 is generally the protocol number. So your SU2200* model is different. > > https://github.com/networkupstools/nut/issues/64 > >> Then I thought I needed the last src code (2.7.4), hence I built it for my machine, but when I run it by: >> /usr/local/ups/sbin/upsdrvctl start > 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. > > If you do choose to build using the latest source code from Git, be aware that you will need more tools, as specified in the Developer Guide: http://networkupstools.org/docs/developer-guide.chunked/ar01s03.html#building > > It may be easier to use the 2.7.4 tarball, and add the patch which introduces Protocol 1330 support to the RPM spec file: https://github.com/networkupstools/nut/commit/4eff5b7068e9873ce11b5a296f403e8cdf0e3580I've uploaded to http://wolfy.fedorapeople.org/nut a new set of packages based on the latest source code from git. Unfortunately they do not include any man pages, I did not have time to find a workaround for the hard requirement of newer versions for the tools used by the build process to create the man pages. I will fix that in a later set of packages.