From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Tips for saving power needed... particulary on laptops
Date: Fri, 6 Apr 2012 13:17:47 -0400 [thread overview]
Message-ID: <CA+czFiDB8SSZFYf5ptSisXw788rZBk9S5aDe-ivRvpWgVV3M=g@mail.gmail.com> (raw)
In-Reply-To: <20120406170532.GA3488@eisen.lan>
On Fri, Apr 6, 2012 at 1:05 PM, Frank Steinmetzger <Warp_7@gmx.de> wrote:
> On Mon, Apr 02, 2012 at 01:22:50AM -0400, Walter Dnes wrote:
>
>> > > Hi,
>> > >
>> > > admin of a colo-center keeps complaining my server is going
>> > > a little over power-limit (which they have set as ~120W per
>> > > 24h/avg, while my server needs ~130-135W). So I need to find
>> > > a way to save at least those 15W, or I will be moved to
>> > > higher tarif (which means higher costs for server-housing).
>> […]
>> The following may seem obvious, but here goes...
>>
>> * remove unnecessary video cards, and drivers. Most colo machines
>> should do OK with just a text console running on the onboard GPU.
>> Dump all video driver stuff "/dev/agpgart (AGP Support)" and
>> "Direct Rendering Manager". This assumes you're not running X on
>> your colo machines. mc (Midnight Commander) is a great text-based
>> tool, along the lines of ye olde Norton Commander.
>>
>> * disable sound cards/chips in BIOS and remove drivers and kernel
>> support.
>
> As a follow-up question that’s been on my mind for a long time: can I always
> assume that when there is no driver loaded, the device is really (physically)
> off, so it doesn't use any power (at all)? Or are there exceptions to that
> rule (like hardware known to be buggy)?
The hardware will be energized, but won't typically consume as much
energy as it would were it under active use and load.
> My concern comes from having an
> ageing laptop whose battery I want to preserve as well as I can.
>
> In my case, that would be bluetooth, ethernet, possibly even the optical
> drive, and even the touchpad. I can switch the latter off using Fn+F9, which
> even works on the tty. But does that really switch it off, or does the kernel
> merely ignore its input then?
For wireless devices, I believe the radio is switched off if you use
the hardware or software switches, but controlling hardware would
still be energized.
For ethernet, you probably want the driver installed, so you can
access any power-saving modes available to it. (Ditto most other
things)
Regarding touchpad...no idea.
Most of this is probably very case-by-case. Check the kernel configs.
Perhaps even measure power consumption changes after doing things like
disabling devices via sysfs.
--
:wq
next prev parent reply other threads:[~2012-04-06 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-01 15:04 [gentoo-user] Tips for saving power needed Jarry
2012-04-01 15:24 ` Michael Hampicke
2012-04-01 15:56 ` Volker Armin Hemmann
2012-04-02 5:22 ` Walter Dnes
2012-04-06 17:05 ` [gentoo-user] Tips for saving power needed... particulary on laptops Frank Steinmetzger
2012-04-06 17:17 ` Michael Mol [this message]
2012-04-02 9:55 ` [gentoo-user] Tips for saving power needed Robert David
2012-04-02 11:57 ` Pandu Poluan
2012-04-02 12:10 ` Michael Mol
2012-04-02 14:17 ` Simon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+czFiDB8SSZFYf5ptSisXw788rZBk9S5aDe-ivRvpWgVV3M=g@mail.gmail.com' \
--to=mikemol@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox