FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 07-15-2010, 04:04 AM
Dale
 
Default sys-power/nut-2.4.3-r2 fails to compile driver

Hi folks,

I'm trying to upgrade nut to the latest stable version. I have the
driver set in make.conf and according to the website, it is the correct
driver. I also while searching around noticed I need to make sure I
have the driver in /lib/nut and sure enough, it is there. In make.conf
I have this:


NUT_DRIVERS="cyberpower"

This is the error I am getting:

make[1]: Entering directory
`/var/tmp/portage/sys-power/nut-2.4.3-r2/work/nut-2.4.3/drivers'

make[1]: *** No rule to make target `cyberpower', needed by `all-am'. Stop.
make[1]: Leaving directory
`/var/tmp/portage/sys-power/nut-2.4.3-r2/work/nut-2.4.3/drivers'

make: *** [all-recursive] Error 1
* ERROR: sys-power/nut-2.4.3-r2 failed:
* emake failed
*
* Call stack:
* ebuild.sh, line 48: Called src_compile
* environment, line 2904: Called _eapi2_src_compile
* ebuild.sh, line 640: Called die
* The specific snippet of code:
* emake || die "emake failed"
*
* If you need support, post the output of 'emerge --info
=sys-power/nut-2.4.3-r2',
* the complete build log and the output of 'emerge -pqv
=sys-power/nut-2.4.3-r2'.
* The complete build log is located at
'/var/log/portage/elog/sys-power:nut-2.4.3-r2:20100715-034546.log'.
* The ebuild environment file is located at
'/var/tmp/portage/sys-power/nut-2.4.3-r2/temp/environment'.

* S: '/var/tmp/portage/sys-power/nut-2.4.3-r2/work/nut-2.4.3'

>>> Failed to emerge sys-power/nut-2.4.3-r2, Log file:

>>> '/var/log/portage/elog/sys-power:nut-2.4.3-r2:20100715-034546.log'
*
* The following package has failed to build or install:
*
* ('ebuild', '/', 'sys-power/nut-2.4.3-r2', 'merge'), Log file:
* '/var/log/portage/elog/sys-power:nut-2.4.3-r2:20100715-034546.log'
*
root@smoker / #

Any idea why it can't make my driver when it is the right one and is set
in make.conf? What am I missing? Oh, this is connected to my serial
port, NOT the USB port.


Thanks.

Dale

:-) :-)
 
Old 07-15-2010, 12:25 PM
"Arttu V."
 
Default sys-power/nut-2.4.3-r2 fails to compile driver

On 7/15/10, Dale <rdalek1967@gmail.com> wrote:
> Hi folks,
>
> I'm trying to upgrade nut to the latest stable version. I have the
> driver set in make.conf and according to the website, it is the correct
> driver. I also while searching around noticed I need to make sure I
> have the driver in /lib/nut and sure enough, it is there. In make.conf
> I have this:
>
> NUT_DRIVERS="cyberpower"
>
> This is the error I am getting:
>
> make[1]: Entering directory
> `/var/tmp/portage/sys-power/nut-2.4.3-r2/work/nut-2.4.3/drivers'
> make[1]: *** No rule to make target `cyberpower', needed by `all-am'. Stop.
> make[1]: Leaving directory
> `/var/tmp/portage/sys-power/nut-2.4.3-r2/work/nut-2.4.3/drivers'
> make: *** [all-recursive] Error 1
> * ERROR: sys-power/nut-2.4.3-r2 failed:
> * emake failed
> *
> * Call stack:
> * ebuild.sh, line 48: Called src_compile
> * environment, line 2904: Called _eapi2_src_compile
> * ebuild.sh, line 640: Called die
> * The specific snippet of code:
> * emake || die "emake failed"
> *
> * If you need support, post the output of 'emerge --info
> =sys-power/nut-2.4.3-r2',
> * the complete build log and the output of 'emerge -pqv
> =sys-power/nut-2.4.3-r2'.
> * The complete build log is located at
> '/var/log/portage/elog/sys-power:nut-2.4.3-r2:20100715-034546.log'.
> * The ebuild environment file is located at
> '/var/tmp/portage/sys-power/nut-2.4.3-r2/temp/environment'.
> * S: '/var/tmp/portage/sys-power/nut-2.4.3-r2/work/nut-2.4.3'
>
> >>> Failed to emerge sys-power/nut-2.4.3-r2, Log file:
>
> >>> '/var/log/portage/elog/sys-power:nut-2.4.3-r2:20100715-034546.log'
> *
> * The following package has failed to build or install:
> *
> * ('ebuild', '/', 'sys-power/nut-2.4.3-r2', 'merge'), Log file:
> * '/var/log/portage/elog/sys-power:nut-2.4.3-r2:20100715-034546.log'
> *
> root@smoker / #
>
> Any idea why it can't make my driver when it is the right one and is set
> in make.conf? What am I missing? Oh, this is connected to my serial
> port, NOT the USB port.

Wrong driver combined with outdated website info or other docs?

I have no idea of their driver model but a hunch from the basis of
cups and a quick grep would lead me to suggest that cyberpower driver
possibly no longer exists. It might have been replaced by powerpanel:

drivers/powerpanel.c: * powerpanel.c - Model specific routines for
CyberPower text/binary

--
Arttu V. -- Running Gentoo is like running with scissors
 
Old 07-15-2010, 05:09 PM
Dale
 
Default sys-power/nut-2.4.3-r2 fails to compile driver

Arttu V. wrote:

On 7/15/10, Dale<rdalek1967@gmail.com> wrote:


Hi folks,

I'm trying to upgrade nut to the latest stable version. I have the
driver set in make.conf and according to the website, it is the correct
driver. I also while searching around noticed I need to make sure I
have the driver in /lib/nut and sure enough, it is there. In make.conf
I have this:

NUT_DRIVERS="cyberpower"

This is the error I am getting:

make[1]: Entering directory
`/var/tmp/portage/sys-power/nut-2.4.3-r2/work/nut-2.4.3/drivers'
make[1]: *** No rule to make target `cyberpower', needed by `all-am'. Stop.
make[1]: Leaving directory
`/var/tmp/portage/sys-power/nut-2.4.3-r2/work/nut-2.4.3/drivers'
make: *** [all-recursive] Error 1
* ERROR: sys-power/nut-2.4.3-r2 failed:
* emake failed
*
* Call stack:
* ebuild.sh, line 48: Called src_compile
* environment, line 2904: Called _eapi2_src_compile
* ebuild.sh, line 640: Called die
* The specific snippet of code:
* emake || die "emake failed"
*
* If you need support, post the output of 'emerge --info
=sys-power/nut-2.4.3-r2',
* the complete build log and the output of 'emerge -pqv
=sys-power/nut-2.4.3-r2'.
* The complete build log is located at
'/var/log/portage/elog/sys-power:nut-2.4.3-r2:20100715-034546.log'.
* The ebuild environment file is located at
'/var/tmp/portage/sys-power/nut-2.4.3-r2/temp/environment'.
* S: '/var/tmp/portage/sys-power/nut-2.4.3-r2/work/nut-2.4.3'

>>> Failed to emerge sys-power/nut-2.4.3-r2, Log file:

>>> '/var/log/portage/elog/sys-power:nut-2.4.3-r2:20100715-034546.log'
*
* The following package has failed to build or install:
*
* ('ebuild', '/', 'sys-power/nut-2.4.3-r2', 'merge'), Log file:
* '/var/log/portage/elog/sys-power:nut-2.4.3-r2:20100715-034546.log'
*
root@smoker / #

Any idea why it can't make my driver when it is the right one and is set
in make.conf? What am I missing? Oh, this is connected to my serial
port, NOT the USB port.


Wrong driver combined with outdated website info or other docs?

I have no idea of their driver model but a hunch from the basis of
cups and a quick grep would lead me to suggest that cyberpower driver
possibly no longer exists. It might have been replaced by powerpanel:

drivers/powerpanel.c: * powerpanel.c - Model specific routines for
CyberPower text/binary



That's what I was thinking but when I saw it still listed on the website
I thought it would still be the right one. Maybe you are right tho, the
website is out of date or something. It does list power panel too tho.
I'll give it a try.


Thanks.

Dale

:-) :-)
 
Old 07-15-2010, 08:42 PM
Dale
 
Default sys-power/nut-2.4.3-r2 fails to compile driver

Dale wrote:


That's what I was thinking but when I saw it still listed on the
website I thought it would still be the right one. Maybe you are
right tho, the website is out of date or something. It does list
power panel too tho. I'll give it a try.


Thanks.

Dale

:-) :-)


Well this doesn't make much sense to me. I did get nut to compile by
changing to the *experimental* driver powerpanel. It then wanted to
overwrite everything in my config file back to the defaults. Not that
it appears the style or settings change but just back to where nothing
is set at all. I got past that, mostly anyway. I got all the services
restarted, twice I might add. Now it tells me stuff that I know is not
even possible. Check out this mess:


root@smoker / # upsc ups@smoker
battery.charge: 205
battery.charge.low: 45
device.mfr: CyberPower
device.model: rO43
device.serial: [unknown]
device.type: ups
driver.name: powerpanel
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ttyS0
driver.version: 2.4.3
driver.version.internal: 0.25
input.frequency: 62.8
input.frequency.nominal: 60
input.transfer.high: 147
input.transfer.low: 88
input.voltage: 120
input.voltage.nominal: 120
output.voltage: 0
output.voltage.nominal: 120
ups.beeper.status: enabled
ups.delay.shutdown: 0
ups.delay.start: 45
ups.firmware: 3.100
ups.load: 22
ups.mfr: CyberPower
ups.model: rO43
ups.serial: [unknown]
ups.status: OL
ups.temperature: 143
root@smoker / #

OK. According to this mess, my 24 volt battery is charged to about 50
volts or so. I think I would see smoke by now. ;-) Then again, it
says the battery is low, 45% charge. Hmmmmm. < Dale scratches his head
on this one > The frequency of the line voltage is at 62.8 Hz, that's
odd. I also doubt the temp of the UPS is 143F either. I got a fan on
it and it usually runs at about 85 to 90 or so.


I think I'm going to go back to the old version of nut unless someone
has a better plan. This new version may compile and install but it
appears to need some more work on the coding end. I wish I could get
powstatd to work. I used it when I was using Mandrake and it was
wonderful. It was small, not to bad to configure and it just plain
worked. I could *easily* set it to shutdown when power had been gone
for more than 10 minutes too. Out here, if the lights are off more than
5 minutes or so, you may as well cut the puter off. It's going to be a
hour or two at least.


Thoughts?

Dale

:-) :-)
 

Thread Tools




All times are GMT. The time now is 03:45 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org