public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Egger <degger@fhm.edu>
To: Gianni Tedesco <gianni@ecsc.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: any brand recomendation for a linux laptop ?
Date: 18 Jan 2003 11:49:12 +0100	[thread overview]
Message-ID: <1042886952.24291.15.camel@sonja> (raw)
In-Reply-To: <1042820273.8935.2.camel@lemsip>

[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]

Am Fre, 2003-01-17 um 17.17 schrieb Gianni Tedesco:

> I have a G4 667 powerbook titanium III and the battery life is very poor
> (around 2hrs) it gets very hot, I think its a kernel problem. Which
> kernel do you use, could you send me your config off list perhaps?

I'm using 2.4.x and 2.5.x kernels; no special version. 

A few pointers:
You might want to check /proc/sys/kernel/powersave-nap is "1".
Any suspicious messages on bootlog? (Post if in doubt)

What CPU does it have (post /proc/cpuinfo).
What clocks does it support according to /proc/cpufreq?
What does the pmu say? (see /proc/pmu)
What does the APM emulation say (need to run pmud to get reliable
results)?
Are the infos from the battery accurate? I need to completely empty
the battery without pmud every now and then to make the infos realistic.

Normally Motorola cpus turn of unused units to save power,
you might want to check that your system is really idle;
when running setiathome for instance my notebook also gets
warm and the battery is draining much faster (intersting 
fact actually, since common belief is that the current drawn
by processor is far less that the sum of all other components).



-- 
Servus,
       Daniel

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-01-18 10:42 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-16 10:00 any brand recomendation for a linux laptop ? Nicolas Turro
2003-01-16 10:41 ` jw schultz
2003-01-16 14:14   ` Andrew Walrond
2003-01-16 14:40     ` Larry McVoy
2003-01-16 15:37       ` Jan-Benedict Glaw
2003-01-16 15:40         ` Larry McVoy
2003-01-16 15:56           ` K.R. Foley
2003-01-17  3:38           ` daveman
2003-01-17 19:32           ` Panu Matilainen
2003-01-18 22:59             ` Jan-Benedict Glaw
2003-01-18 23:08               ` J.A. Magallon
2003-01-16 16:14         ` Daniel Egger
2003-01-16 17:18           ` Richard B. Johnson
2003-01-17 13:54           ` Henning P. Schmiedehausen
2003-01-18 11:31             ` Daniel Egger
2003-01-17 16:17           ` Gianni Tedesco
2003-01-18 10:49             ` Daniel Egger [this message]
2003-01-23 13:19               ` Pavel Machek
2003-01-24 17:01               ` Gianni Tedesco
2003-01-26 23:26                 ` Daniel Egger
2003-01-27 10:23                   ` Gianni Tedesco
2003-01-16 16:05       ` Matthew J. Fanto
2003-01-16 11:38 ` Dave Jones
2003-01-28 16:00   ` Serguei Miridonov
2003-01-30 16:30     ` Hirling Endre
2003-01-30 17:41       ` Serguei Miridonov
2003-01-30 18:20       ` Alan Cox
2003-01-16 13:32 ` Tim Walberg
2003-01-16 13:45 ` Ducrot Bruno
2003-01-16 16:32 ` Kent Borg
2003-01-16 18:19 ` Andreas Jellinghaus

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=1042886952.24291.15.camel@sonja \
    --to=degger@fhm.edu \
    --cc=gianni@ecsc.co.uk \
    --cc=linux-kernel@vger.kernel.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