From: Johannes Erdfelt <johannes@erdfelt.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: Andre Tomt <andre@tomt.net>, linux-kernel@vger.kernel.org
Subject: Re: SMP Support for AMD Athlon MP motherboards
Date: Sun, 5 Aug 2001 01:38:37 -0400 [thread overview]
Message-ID: <20010805013835.T3126@sventech.com> (raw)
In-Reply-To: <002b01c11d62$73e65540$8405000a@slurv> <20010805173024.C20716@weta.f00f.org>
In-Reply-To: <20010805173024.C20716@weta.f00f.org>; from cw@f00f.org on Sun, Aug 05, 2001 at 05:30:24PM +1200
On Sun, Aug 05, 2001, Chris Wedgwood <cw@f00f.org> wrote:
> On Sun, Aug 05, 2001 at 05:55:22AM +0200, Andre Tomt wrote:
>
> I recently got my hands on a unreleased evaluation AthlonMP
> ^^^^^^^^^^^^^^^^^^^^^
> motherboard with two 1.1Ghz Athlon CPU's. First thing I tried was
> of course Linux. I ran into some problems, however.
>
> Linux does support this, and people are using it --- with no
> major problems.
>
> Maybe your board is busted? If you think that not the case, please
> try 2.4.7+ and report specifically what the problems are in more
> detail if you can (ie. supply dmesg from boot, etc).
All of the 2.4 kernels that worked on PIII systems worked on my Dual
Athlon.
> Anyhow, you 2.2.x you need something very recent, maybe 2.2.20+ I
> think.
Only for SMP. Atleast all of the later 2.2 kernels worked fine with the
Tyan MP Athlon board with the UP kernel.
To get SMP working you need to apply the patches I created. They just
got to Alan and I don't think they're in 2.2.20pre yet, but it sounds
like they'll be in there soon.
Anyway, it sounds like a hardware problem.
JE
next prev parent reply other threads:[~2001-08-05 5:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-05 3:55 SMP Support for AMD Athlon MP motherboards Andre Tomt
2001-08-05 5:30 ` Chris Wedgwood
2001-08-05 5:38 ` Johannes Erdfelt [this message]
2001-08-05 11:18 ` Andre Tomt
2001-08-05 8:35 ` Paul G. Allen
[not found] <no.id>
2001-08-05 13:04 ` Alan Cox
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=20010805013835.T3126@sventech.com \
--to=johannes@erdfelt.com \
--cc=andre@tomt.net \
--cc=cw@f00f.org \
--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;
as well as URLs for NNTP newsgroup(s).