From: Andreas Bombe <bombe@informatik.tu-muenchen.de>
To: Shaya Potter <spotter@opus.cs.columbia.edu>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Dual athlon XP 1800 problems
Date: Thu, 3 Jan 2002 17:53:22 +0100 [thread overview]
Message-ID: <20020103165321.GA737@bombe.modem.informatik.tu-muenchen.de> (raw)
In-Reply-To: <3C311B00.FFB58648@get2chip.com> <20020101032335.A11129@suse.de> <1009868304.27412.2.camel@zaphod>
In-Reply-To: <1009868304.27412.2.camel@zaphod>
On Tue, Jan 01, 2002 at 01:58:23AM -0500, Shaya Potter wrote:
> I missed the original message, I'm running a dual athlon 1800+ XP system
> (actually both CPU for some reason get identified as MPs, but they are
> retail XP chips).
The identification string is written by the BIOS. Yours didn't know
about XPs so it misidentified them as MPs. Upgrade your BIOS if this
bugs you.
If ID string contradicts what you think you bought, don't trust the ID
string.
--
Andreas Bombe <bombe@informatik.tu-muenchen.de> DSA key 0x04880A44
next prev parent reply other threads:[~2002-01-03 16:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-01 2:12 ccroswhite
2002-01-01 3:23 ` Dave Jones
2002-01-01 3:40 ` Jeffrey H. Ingber
2002-01-01 4:46 ` Adam Schrotenboer
2002-01-01 6:58 ` Shaya Potter
2002-01-03 16:53 ` Andreas Bombe [this message]
2002-01-03 17:07 ` Dave Jones
2002-01-03 19:07 ` Shaya Potter
2002-01-03 17:48 ` H. Peter Anvin
2002-01-03 18:02 ` Dave Jones
2002-01-04 0:36 ` H. Peter Anvin
2002-01-04 2:15 ` Andreas Bombe
2002-01-01 15:21 Dr. David Alan Gilbert
2002-01-03 17:08 ` Andreas Bombe
2002-11-15 10:31 David Crooke
2002-11-15 11:55 ` Alastair MacGregor
2002-11-15 14:54 ` Alan Cox
2002-11-15 14:40 ` Dave Jones
2002-11-15 17:19 ` Willy Tarreau
2002-11-15 18:38 ` erich
2002-11-15 17:26 ` Ken Witherow
2002-11-15 17:40 ` steve roemen
2002-11-15 18:21 ` Ken Witherow
2002-11-15 18:51 ` Alastair MacGregor
2002-11-16 3:04 ` Alan Cox
2002-11-16 15:11 Kevin Brosius
2002-11-16 15:14 ` Kevin Brosius
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=20020103165321.GA737@bombe.modem.informatik.tu-muenchen.de \
--to=bombe@informatik.tu-muenchen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=spotter@opus.cs.columbia.edu \
/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®