public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marvin Justice <mjustice@austin.rr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: What Athlon chipset is most stable in Linux?
Date: Tue, 13 Nov 2001 21:19:49 -0600	[thread overview]
Message-ID: <01111321194902.00746@bozo> (raw)
In-Reply-To: <Pine.LNX.4.30.0111131559580.8219-100000@rtlab.med.cornell.edu> <200111132137.fADLbdW01289@demai05.mw.mediaone.net> <20011113.183256.15406047.davem@redhat.com>
In-Reply-To: <20011113.183256.15406047.davem@redhat.com>

We've acutally had next to no hangs on the Thunder K7 using a FireGL2 card 
--- if you don't mind spending $1000+ for high end 3D graphics :-) Stay away 
from nVidia for now; though I understand they're working on fixes for this 
chipset for their next driver release. 

On Tuesday 13 November 2001 08:32 pm, David S. Miller wrote:
>    From: Brian <hiryuu@envisiongames.net>
>    Date: Tue, 13 Nov 2001 16:37:28 -0500
>
>    We've tried a number of boards for our application servers and the only
> UP AMD DDR board I trust right now is the Gigabyte GA-7DX.  They are rock
> solid.
>
> Try to use the AGP slot with a Radeon of GeForce card, do something
> as simple as playing some quake with com_maxfps > 85 and the machine
> will hang solidly.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Marvin Justice
Software Developer
BOXX Technologies, Inc.
www.boxxtech.com
512-235-6318 (V)
512-835-0434 (F)

  parent reply	other threads:[~2001-11-14  3:15 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-13 13:19 What Athlon chipset is most stable in Linux? 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 [this message]
2001-11-14 13:27         ` Chris Meadors
2001-11-14 15:28           ` Marvin Justice
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
  -- strict thread matches above, loose matches on Subject: below --
2001-11-13 17:29 Giles Tyson
2001-11-13 18:00 ` Paul G. Allen
2001-11-13 22:41   ` Alan Cox
     [not found] <3B6867E6CB09B24385A73719A50C7C9A797750@athena.boxxtech.com>
2001-11-14 17:24 ` Marvin Justice

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=01111321194902.00746@bozo \
    --to=mjustice@austin.rr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox