public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: peter@hoeg.com
Cc: Jos Hulzink <josh@stack.nl>, linux-kernel@vger.kernel.org
Subject: Re: misdetection of pentium2 - very strange
Date: Thu, 21 Feb 2002 11:39:53 +0100 (MET)	[thread overview]
Message-ID: <200202211039.LAA21757@cave.bitwizard.nl> (raw)
In-Reply-To: <1014285431.3c74c477274c4@www.hoeg.home> from "peter@hoeg.com" at "Feb 21, 2002 05:57:11 pm"

peter@hoeg.com wrote:
> > > prerelease)) #3 Thu Feb 21 19:21:37 SGT 2002
> > > Initializing CPU#0
> > > Detected 133.225 MHz processor.
> > > Calibrating delay loop... 265.42 BogoMIPS

> > It seems your CPU is actually running at 133 MHz. If I am right, the

> the compaq setup utility (bios setup program) reports a 333mhz with
> a bus speed of 66, so if something makes it enter a low-power mode
> it should be linux. but no apm/acpi support is compiled in/as
> modules.

There has been a scam where the "133" in the BIOS was replaced by
"333" and the resulting machines were sold as faster than they
actually were... 

You can count on it that with the above output, your CPU is running at
133 when Linux boots. It could be that the CPU is put in "slow" mode
if you run on the batteries. (Is it a laptop? I missed the beginning
of this thread). 

			Roger. 

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots. 
* There are also old, bald pilots. 

      reply	other threads:[~2002-02-21 10:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-21  7:22 misdetection of pentium2 - very strange peter
2002-02-21  8:56 ` Jos Hulzink
2002-02-21  9:57   ` peter
2002-02-21 10:39     ` Rogier Wolff [this message]

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=200202211039.LAA21757@cave.bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=josh@stack.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@hoeg.com \
    /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