[solved] sys-power/nut compile problem (newhidups)

Message

eXess · Post by **eXess** » Mon Sep 28, 2009 10:18 am

Hi all,

I have huge problems emerging NUT to control my MGE Ellipse 300 USB. I did run (I had installed everything mainly using this : http://forums.gentoo.org/viewtopic-t-372153.html). When updating to 2.4.1-r1, compile fails and now I don't have newhidups driver anymore.

When starting up the system (or restarting upsd manually) I get this :

Code: Select all

* Starting UPS drivers... 
Network UPS Tools - UPS driver controller 2.4.1
Can't start /lib/nut/newhidups: No such file or directory
* Failed to start UPS drivers!                                   [ !! ]

Here is what I get when compiling :

Code: Select all

# emerge -aDv sys-power/nut

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   ] sys-power/nut-2.4.1-r1  USE="ssl usb xml -bash-completion -cgi -hal -snmp" 0 kB

Total: 1 package (1 reinstall), Size of downloads: 0 kB

Would you like to merge these packages? [Yes/No] -> y

(blah...)

Making all in drivers
make[1]: Entering directory `/var/tmp/portage/sys-power/nut-2.4.1-r1/work/nut-2.4.1/drivers'
make[1]: *** No rule to make target `newhidups', needed by `all-am'.  Stop.
make[1]: Leaving directory `/var/tmp/portage/sys-power/nut-2.4.1-r1/work/nut-2.4.1/drivers'
make: *** [all-recursive] Error 1
 *
 * ERROR: sys-power/nut-2.4.1-r1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2747:  Called _eapi2_src_compile
 *               ebuild.sh, line  634:  Called die
 * The specific snippet of code:
 *              emake || die "emake failed"
 *  The die message:
 *   emake failed

 (blah...)

Here are my config file (relevant parts at least) :

Code: Select all

# cat /etc/nut/nut.conf
MODE = standalone

Code: Select all

# cat /etc/nut/ups.conf
[mge]
driver = newhidups
port = auto
desc = "MGE Ellipse 300 USB"
pollinterval = 15

Code: Select all

# cat upsd.users
[upsuser]
password = *******
allowfrom = localhost
upsmon  master

Code: Select all

# cat upsmon.conf
FINALDELAY 5
MONITOR mge@localhost 1 upsuser ******* master

upsd.conf is default

Please note that I did emerge libusb manually, to no avail.
Does anyone have a clue ?
Thanks...

cctsurf · Post by **cctsurf** » Mon Sep 28, 2009 12:34 pm

I ran into a number of problems when moving to nut 2.4, one thing to note is that the newhidups driver has become usbhid-ups. I've forgotten what all I had to do, but building with newhidups seems to be breaking your build.

cctsurf · Post by **cctsurf** » Mon Sep 28, 2009 12:49 pm

One more thought, I would suggest using the regular ebuild, instead of the ones on that forum, I've had no problems with them for quite a while (you did notice they were talking about nut-2.0.1), we're working with nut 2.4.1. Hope that helps

keyson · Post by **keyson** » Mon Sep 28, 2009 3:40 pm

Hi,

Think you have set the NUT_DRIVERS="newhidups" in your /etc/make.conf.

As cctsurf say the newhidups driver is removed and the usbhid-ups driver is the one to use.
It have the mge-hid subdriver that should drive your ups.

eXess · Post by **eXess** » Mon Sep 28, 2009 8:20 pm

cctsurf wrote:(...)one thing to note is that the newhidups driver has become usbhid-ups. I've forgotten what all I had to do(...)

That's the information I needed. Here's what I did:

Edit /etc/make.conf > NUT_DRIVERS="usbhid-ups" (instead of NUT_DRIVERS="newhidups")
Edit /etc/nut/ups.conf so that "driver = newshidups" is replaced with "driver = usbhid-ups" wherever necessary

Then :

Code: Select all

# /etc/init.d/upsdrv restart
 * Starting UPS drivers ...
Network UPS Tools - UPS driver controller 2.4.1
Network UPS Tools - Generic HID driver 0.34 (2.4.1)
USB communication driver 0.31
Using subdriver: MGE HID 1.12                                                                                                                           [ ok ]

That's cool !

Code: Select all

# /etc/init.d/upsmon restart
 * Starting upsmon ...
Network UPS Tools upsmon 2.4.1
Using power down flag file /etc/killpower

UPS: mge@localhost (master) (power value 1)                                                                                                             [ ok ]

Even better !

Code: Select all

 # /etc/init.d/upsd start
 * Starting upsd ...
Network UPS Tools upsd 2.4.1
listening on 127.0.0.1 port 3493
not listening on ::1 port 3493                                                                                                                          [ !! ]

Yikes !

So I did restart and... I guess udev needed just that.
Works without problems.

Sorry for not posting earlier but the forum (or my browser?) seemed to be buggy this afternoon.
Anyway...

xdarma · Post by **xdarma** » Tue Sep 29, 2009 5:42 am

eXess wrote: That's the information I needed. Here's what I did:
Edit /etc/make.conf > NUT_DRIVERS="usbhid-ups" (instead of NUT_DRIVERS="newhidups")

Edit /etc/nut/ups.conf so that "driver = newshidups" is replaced with "driver = usbhid-ups" wherever necessary

Before modify of /etc/make.conf you dont'have a driver named usbhid-ups under /lib/nut ?
Or, can you post the output of:

Code: Select all

ls -aFl /lib/nut/

Thanks.

eXess · Post by **eXess** » Tue Sep 29, 2009 6:05 am

Don't know (I only saw the compile error and adjusted make.conf according to indications) and now it's up and running, so I'll have the dreiver in /lib/nut of course... and I won't emerge -C just to check...

xdarma · Post by **xdarma** » Tue Sep 29, 2009 9:21 am

eXess wrote: so I'll have the dreiver in /lib/nut of course... and I won't emerge -C just to check... ;)

Is the only driver on /lib/nut ?
Of course, if is not broken, dont'fix :-)

eXess · Post by **eXess** » Tue Sep 29, 2009 9:47 am

Code: Select all

# ls -alF /lib/nut/
total 164
drwxr-xr-x 2 root root   4096 Sep 28 15:39 ./
drwxr-xr-x 9 root root   4096 Sep 18 15:21 ../
-rwxr-xr-x 1 root root  30248 Sep 28 15:38 skel*
-rwxr-xr-x 1 root root  17888 Sep 28 15:38 upsdrvctl*
-rwxr-xr-x 1 root root 100668 Sep 28 15:38 usbhid-ups*

xdarma · Post by **xdarma** » Tue Sep 29, 2009 9:06 pm

Thank you for answer, on my systen I don't set the NUT_DRIVERS="usbhid-ups" in my /etc/make.conf, so I have about 40 driver.
Maybe a local USE to build a given driver will be useful.

eXess · Post by **eXess** » Tue Sep 29, 2009 9:25 pm

A local USE flag will first have to be built in the ebuild, because as of now, the variable used in make.conf is not USE but the proprietary NUT_DRIVERS, un fortunately. But I agree, being able to USE-flag-choose which driver(s) should be built would be a serious plus for the package...

keyson · Post by **keyson** » Wed Sep 30, 2009 3:46 pm

Hi,

The USE flag system is good. But I think the NUT_DRIVER in the make.conf is the best choice.
Like the APACHE_MODULES, INPUT_DEVICES and VIDEO_CARDS.

The USE flag system should be cluttered with to many things.

Look at the driver list in NUT.

SERIAL_DRIVERLIST = apcsmart bcmxcp belkin belkinunv bestfcom \
bestfortress bestuferrups bestups cyberpower dummy-ups etapro everups \
gamatronic genericups isbmex liebert masterguard megatec metasys \
mge-shut mge-utalk microdowell newmge-shut oneac optiups powercom rhino \
safenet skel solis tripplite tripplitesu upscode2 victronups powerpanel \
blazer_ser clone ivtscd
SNMP_DRIVERLIST = snmp-ups
USB_LIBUSB_DRIVERLIST = usbhid-ups bcmxcp_usb tripplite_usb megatec_usb \
blazer_usb richcomm_usb

xdarma · Post by **xdarma** » Thu Oct 01, 2009 7:13 pm

keyson wrote:The USE flag system is good. But I think the NUT_DRIVER in the make.conf is the best choice.
Like the APACHE_MODULES, INPUT_DEVICES and VIDEO_CARDS.

Yes, you are right.
I'm thinking about a sort of pass-trough for ./configure, something like USE="custom-driver=my_ups_driver".
Just to keep off from /etc/make.conf settings that aren't global, doesn't really matter.