From: James Miller <jamtat@mailsnare.net>
To: Linux-Newbie list <linux-newbie@vger.kernel.org>
Subject: Linux detection of processor speed - accurate?
Date: Fri, 3 Oct 2003 14:33:35 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0310031421150.1378@homenet> (raw)
This is more of a general hardware question than a Linux question, but
there *is* a Linux component. Here goes. I've recently put newer
processors in a couple of older motherboards. In one case, a BIOS upgrade
had been performed on the machine at some point since it's manufacture, in
the other case, I'm not sure. In any case, following directions I found
at Tom's hardware for one of them, I put in a 500Mhz processor - but the
BIOS would only show a 400Mhz processor in its report (I'm sure I set the
jumpers right: I double and triple checked it). In the other, I put a
1.4Ghz processor - but the BIOS report would show only an 800Mhz
processor. Now, here's where Linux part comes in: despite what the BIOS
report shows about processor speed, Linux's bootup report shows the
correct processor speed - 499Mhz in one case, 1390.xxMhz in the other.
So, who's right - the BIOS report or Linux's bootup record? Can the OS
use the processor's full speed, even though the BIOS doesn't seem to
recognize it?
Thanks for any input on this marginally Linux question.
James
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next reply other threads:[~2003-10-03 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 19:33 James Miller [this message]
2003-10-03 22:04 ` Linux detection of processor speed - accurate? Jeff Woods
2003-10-04 13:42 ` Hal MacArgle
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=Pine.LNX.4.58.0310031421150.1378@homenet \
--to=jamtat@mailsnare.net \
--cc=linux-newbie@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