All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul G. Allen" <pgallen@randomlogic.com>
To: "Linux kernel developer's mailing list"  <linux-kernel@vger.kernel.org>
Subject: Re: What Athlon chipset is most stable in Linux?
Date: Tue, 13 Nov 2001 10:00:01 -0800	[thread overview]
Message-ID: <3BF15FA1.94DFE0F5@randomlogic.com> (raw)
In-Reply-To: <4BC5D32775F0D311963F0090276DD12E07817A@SYNX10>

Giles Tyson wrote:
> 
> -----Original Message-----
> From: Jeffrey W. Baker [mailto:jwbaker@acm.org]
> >On Tue, 2001-11-13 at 05:19, Martin Eriksson wrote:
> >> I'm hearing rumours about my University wanting to set up a cluster with
> AMD
> >> Athlon XP+DDR computers, so I wonder what chipset is most stable under
> >> Linux?
> >>
> >> I assume it's the AMD DDR chipset, but I want to be pretty sure.
> 
> >I have no problems with the 1400MHz Athlon on AMD 760, including DRI
> >using the AGP bridge.
> 
> It's my understanding that among boards with the same chipset, some may work
> while others do not.  I have tested an Iwill KK266+Raid, with KT133A, and it
> would not run with athlon optimizations.  I also have tried an Epox 8KHA+,
> with KT266A, and it has been perfectly stable so far, for three days.

I have yet to try the latest kernels, but I have an Asus A7V133 (PC133,
not DDR) and a Tyan K7 Thunder (dual). Both are running 1.4GHz Athlons
and both have had problems. In both cases the IDE has been a problem. On
the Tyan, I've had to turn off DMA or it will lock up. I have not messed
with the Asus system yet to see exactly where the problem is.

I'm looking forward to seeing how a newer kernel works (I am running
2.4.9ac10 on my Tyan and a stock Red Hat 7.1 kernel on the Asus until I
upgrade it)

PGA
-- 
Paul G. Allen
UNIX Admin II/Programmer
Akamai Technologies, Inc.
www.akamai.com

  reply	other threads:[~2001-11-13 18:00 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-13 17:29 What Athlon chipset is most stable in Linux? Giles Tyson
2001-11-13 18:00 ` Paul G. Allen [this message]
2001-11-13 22:41   ` Alan Cox
     [not found] <3B6867E6CB09B24385A73719A50C7C9A797750@athena.boxxtech.com>
2001-11-14 17:24 ` Marvin Justice
  -- strict thread matches above, loose matches on Subject: below --
2001-11-13 13:19 Martin Eriksson
2001-11-13 16:06 ` Pascal Schmidt
2001-11-13 17:12 ` Jeffrey W. Baker
2001-11-13 21:08 ` Calin A. Culianu
2001-11-13 21:37   ` Brian
2001-11-13 22:18     ` Paul G. Allen
2001-11-13 22:39       ` Calin A. Culianu
2001-11-14  1:27       ` Stuart Young
2001-11-14 20:08         ` Calin A. Culianu
2001-11-14  2:32     ` David S. Miller
2001-11-14  3:05       ` Dan Hollis
2001-11-14  3:11         ` David S. Miller
2001-11-14  3:11       ` Brian
2001-11-14  2:55         ` Joel Jaeggli
2001-11-14 20:04           ` Calin A. Culianu
2001-11-14  3:13         ` David S. Miller
2001-11-14 14:23           ` Mike Dresser
2001-11-14  3:11       ` Dan Hollis
2001-11-14  3:16         ` David S. Miller
2001-11-14 16:54           ` Ion Badulescu
2001-11-15  1:03           ` Paul G. Allen
2001-11-15  1:15             ` Dan Hollis
2001-11-15  1:23             ` Stuart Young
2001-11-15  1:51               ` Paul G. Allen
     [not found]             ` <20011116144835.A22537@weta.f00f.org>
2001-11-20  7:43               ` Paul G. Allen
2001-11-20 16:49                 ` Gérard Roudier
2001-11-15  0:45         ` Stuart Young
2001-11-15  9:58           ` David S. Miller
2001-11-14  3:19       ` Marvin Justice
2001-11-14 13:27         ` Chris Meadors
2001-11-14  6:38   ` DevilKin
2001-11-13 21:19 ` Dan Hollis
2001-11-14  2:29   ` David S. Miller
2001-11-14 10:51     ` Alan Cox
2001-11-14 10:48       ` David S. Miller
2001-11-15 19:57       ` Marek Mentel
2001-11-15 13:04         ` David S. Miller

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=3BF15FA1.94DFE0F5@randomlogic.com \
    --to=pgallen@randomlogic.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.