mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brian <hiryuu@envisiongames.net>
To: Mike Harrold <mharrold@cas.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ATHLON HELP ME ON THIS PLZ!!!!
Date: Tue, 01 Jan 2002 17:57:37 -0500	[thread overview]
Message-ID: <0GPA001897RYFT@mtaout45-02.icomcast.net> (raw)
In-Reply-To: <200201012107.QAA10138@mah21awu.cas.org>
In-Reply-To: <200201012107.QAA10138@mah21awu.cas.org>

On Tuesday 01 January 2002 04:07 pm, Mike Harrold wrote:
> Actually, I'm interested in this as well. The only thing stopping me
> from buying a dual Athlon MP is the problems I keep reading about here
> on lkml. I don't want to spend the money only to have problems.
>
> So, if anyone is running dual Athlon MPs *flawlessly*, I'd appreciate a
> hardware listing (MB, Bios version, RAM type & manufacturer, etc.).

We have 8 running dual-Athlons which are basically Einux 1200s 
(http://www.einux.com/A1200.html).  We have our first pair of MP1700-based 
systems going in this week, so I can't say much about those yet.

We had some trouble with a couple of bad boards from Tyan's first batch or 
so.  Also, more than 2 Kentron 256MB modules didn't work well together.  
Those first couple weeks were rough, but we switched to 512MB modules and 
they have been rock solid ever since.

The XP processors may or may not work, but I would have a tough time 
justifying it to customers if we had system problems from us cheaping out 
on unsupported configs.

	-- Brian

  parent reply	other threads:[~2002-01-02  2:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-01 19:42 Astinus
2002-01-01 21:07 ` Mike Harrold
2002-01-01 21:19   ` Shaya Potter
2002-01-01 21:38   ` Daniel Freedman
2002-01-01 22:57   ` Brian [this message]
2002-01-02  3:32     ` Andre Hedrick
2002-01-03 17:50 ` Andreas Bombe

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=0GPA001897RYFT@mtaout45-02.icomcast.net \
    --to=hiryuu@envisiongames.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mharrold@cas.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

all inboxes | Powered by JetHome®