mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: cw@f00f.org (Chris Wedgwood)
To: Daniel Harvey <daniel@amristar.com.au>
Cc: linux-laptop@mobilix.org, linux-kernel@vger.kernel.org
Subject: Re: Linux SLOW on Compaq Armada 110 PIII Speedstep
Date: Mon, 2 Jul 2001 04:42:52 +1200	[thread overview]
Message-ID: <20010702044252.B14170@weta.f00f.org> (raw)
In-Reply-To: <NEBBJDBLILDEDGICHAGAEENECFAA.daniel@amristar.com.au>
In-Reply-To: <NEBBJDBLILDEDGICHAGAEENECFAA.daniel@amristar.com.au>

On Sun, Jul 01, 2001 at 11:36:51PM +0800, Daniel Harvey wrote:

> The Compaq Armada doesn't appear to have a BIOS setting for the
> power settings.

> I still don't get the fact that one kernel will run fast, while the
> rest do the real SLOW thing.

Not answering your question, but you might want to try:

Download the source-RPM for the 'fast' kernel, and also the virgin
version of the same kernel, and then diff them to see what changes
have been made.

If you are lucky, the RPM itself my have the virgin data and diffs, I
don't know much about RPMS, but I'm pretty sure this is possible.


You are looking for changes outside of linux/drivers/, probably in
linux/archo/i386 or linux/kernel. Hopefully there aren't too many of
these.

Also, you want the .config file that was used, try using that against
a virgin kernel first, and see if that changes anything, if not, then
do diff the above (diff -Nur virgin-kernel/ redhat-kernel/) and see
what falls out.



   --cw

  reply	other threads:[~2001-07-01 16:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-01 15:36 Daniel Harvey
2001-07-01 16:42 ` Chris Wedgwood [this message]
2001-07-01 16:50   ` Daniel Harvey
  -- strict thread matches above, loose matches on Subject: below --
2001-07-01 14:51 Daniel Harvey
2001-07-01 14:56 ` Jeff Garzik
2001-07-02 14:43   ` Paul Jakma

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=20010702044252.B14170@weta.f00f.org \
    --to=cw@f00f.org \
    --cc=daniel@amristar.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-laptop@mobilix.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

all inboxes | Powered by JetHome®