From: Hal MacArgle <haltec@kvinet.com>
To: linux-newbie@vger.kernel.org
Subject: Re: Linux detection of processor speed - accurate?
Date: Sat, 4 Oct 2003 09:42:59 -0400 [thread overview]
Message-ID: <20031004134259.GA536@lnx2.w8mch.ampr.org> (raw)
In-Reply-To: <5.2.1.1.0.20031003150225.034167f8@no.incoming.mail>
On 10-03, Jeff Woods wrote:
> At 10/3/2003 02:33 PM -0500, James Miller wrote:
> >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?
>
> In my experience, yes, the processor can run faster than the BIOS knows how
> to report the speed.
>
> --
> Jeff Woods <kazrak+kernel@cesmail.net>
Greetings: Being parochial about Linux I would trust what it reports
above anything else.. Linux developers "care." M$'s MSD program still
reports a 1Ghz processor as a "486", whatever. <grin>
You must be familiar with the 'bogomips' report either run alone or
check dmesg.. I find that a clue as to what really goes on... Someone
may know it's not really accurate either and I suspect that's why
it's called "bogus million operations a second." <grin> At least we're
forewarned and disclaimed.. Keep busy.
Cheers,
Hal - in Terra Alta, WV - Slackware GNU/Linux 9.0 (2.4.20)
Proprietary Formats Unacceptable
.
-
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
prev parent reply other threads:[~2003-10-04 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 19:33 Linux detection of processor speed - accurate? James Miller
2003-10-03 22:04 ` Jeff Woods
2003-10-04 13:42 ` Hal MacArgle [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=20031004134259.GA536@lnx2.w8mch.ampr.org \
--to=haltec@kvinet.com \
--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