[Nut-upsuser] Emerson/Liebert GXT3
clepple at gmail.com
Thu Oct 30 03:49:22 UTC 2014
On Oct 29, 2014, at 5:08 PM, Marcelo Fernandez <marcelo.fidel.fernandez at gmail.com> wrote:
> I've bought a Liebert GXT3 UPS and I'm trying to use it with nut. I'm
> using Ubuntu 14.04, but I'm having troubles (similar to this thread
> ) using the standard "nut" package from the Ubuntu repositories.
> After some more searching, I've found this very recent thread in this
> list ("Return on experience with an Emerson/Liebert GXT3" ), and
> from my humble understanding, you finally pushed some upstream changes
> in the end which should made this UPS to work.
At the time you read that thread, the changes were still in a branch (there was still some cleanup to do). I just merged it to master.
> I'm a newbie using nut, but not so cloning a repository and compiling
> software. Is there something that I have to take into account to make
> this UPS to work from upstream?
There is a good bit of integration with the startup/shutdown sequence in the Debian/Ubuntu packages of NUT, so since you only need the newer driver, I would do one of the following:
1) configure NUT with the same --prefix and other paths that Ubuntu uses. You can use --with-drivers=usbhid-ups to avoid compiling all of the other drivers you don't need (and if you do need them, the ones from the 2.7.2 .debs should be new enough)
2) download the debian/ directory from NUT 2.7.2, and update it for a 188.8.131.52 snapshot. You may want to run "apt-get build-dep nut" (or similar) first.
In the first case, you will want to keep an eye out for updates - if there were a security update to 2.7.2, it would overwrite your driver, and you would need to re-run 'make install'.
The snapshots have slightly fewer dependencies (autotools, mostly) than building straight from Git. They are generated automatically on each Git push, and are available from the [tarball] links here: http://buildbot.networkupstools.org/snapshots
> After building and installing into /usr/local , should I edit
> /etc/nut/ups.conf like this:
If you configure using "--with-user=nut", it will match the Ubuntu package, and you can simplify the configuration:
port = auto # (can be any string; driver matches based on USB VID:PID)
No productid is needed with the merged code.
clepple at gmail
More information about the Nut-upsuser