public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shaya Potter <spotter@cs.columbia.edu>
To: Dave Jones <davej@suse.de>
Cc: Andreas Bombe <bombe@informatik.tu-muenchen.de>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Dual athlon XP 1800 problems
Date: 03 Jan 2002 14:07:50 -0500	[thread overview]
Message-ID: <1010084872.23187.3.camel@zaphod> (raw)
In-Reply-To: <Pine.LNX.4.33.0201031806360.11961-100000@Appserv.suse.de>
In-Reply-To: <Pine.LNX.4.33.0201031806360.11961-100000@Appserv.suse.de>

On Thu, 2002-01-03 at 12:07, Dave Jones wrote:
> On Thu, 3 Jan 2002, Andreas Bombe wrote:
> 
> > 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.
> 
> x86info, and 2.5.2-dj11 both have code to correctly determine XP / MP.

Just getting linux up and running on this machine, so with the original
debian kernel (2.2.20 UP) and x86info from its unstable, these retail
XPs were identified as MPs

trillian:/home/spotter# uname -a
Linux trillian 2.2.20 #1 Sun Nov 4 15:44:23 EST 2001 i686 unknown
trillian:/home/spotter# x86info 
x86info v1.7.  Dave Jones 2001
Feedback to <davej@suse.de>.

Found 1 CPU, but found 2 CPUs in MPTable.
/dev/cpu/0/cpuid: No such device
Family: 6 Model: 6 Stepping: 2 [Athlon MP]
Processor name string: AMD Athlon(tm) MP Processor 1800+

PowerNOW! Technology information
Available features:
	Temperature sensing diode present.

prehaps 2.4.17 (compiling now) will make a difference, or does one need
your kernel + x86info to do it correctly?

thanks,

shaya

-- 
spotter@{cs.columbia.edu,yucs.org}
http://yucs.org/~spotter/


  reply	other threads:[~2002-01-03 19:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-01  2:12 Dual athlon XP 1800 problems 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
2002-01-03 17:07       ` Dave Jones
2002-01-03 19:07         ` Shaya Potter [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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=1010084872.23187.3.camel@zaphod \
    --to=spotter@cs.columbia.edu \
    --cc=bombe@informatik.tu-muenchen.de \
    --cc=davej@suse.de \
    --cc=linux-kernel@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