linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Clark <michael@metaparadigm.com>
To: Elladan <elladan@eskimo.com>
Cc: felix.seeger@gmx.de, "David S. Miller" <davem@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: System very unstable
Date: Sun, 29 Sep 2002 13:50:36 +0800	[thread overview]
Message-ID: <3D9694AC.9020907@metaparadigm.com> (raw)
In-Reply-To: 20020929000056.GB19765@eskimo.com

On 09/29/02 08:00, Elladan wrote:
> On Sat, Sep 28, 2002 at 07:13:57PM +0800, Michael Clark wrote:
> 
>>On 09/28/02 18:35, David S. Miller wrote:
>>
>>>  From: Felix Seeger <felix.seeger@gmx.de>
>>>  Date: Sat, 28 Sep 2002 12:33:21 +0200
>>>  
>>>  What card is good (performance for games and 
>>>  a acceptable licenze for kernel developers)?
>>>
>>>ATI Radeon is pretty fast and all except the very latest chips have
>>>opensource drivers.
>>
>>Radeon 7500 is currently the fastest board with an opensource
>>driver that supports 3D. 8500 XFree support is currently 2D only,
>>although apparently work on the opensource GL driver is underway.
> 
> 
> Unfortunately, in my experience the open source Radeon 7500 drivers are
> so unstable as to be basically unusable.  Plus, they seem to still be
> basically incompatible with a lot of 3d software.

Don't know what version of X you've been running, but i haven't
had a problem for over 8 months (since XFree86 4.2). Before then,
the 4.1.99 CVS was needed for radeon support which was of course
a developer branch, although i never experienced the sort of problems
you describe.

Definately rock solid and stable on my 7500 mobility.

~mc


  reply	other threads:[~2002-09-29  5:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-28  9:15 System very unstable Felix Seeger
2002-09-28  9:32 ` Alan Cox
2002-09-28  9:34   ` Felix Seeger
2002-09-28  9:50     ` Thunder from the hill
2002-09-28  9:55       ` Felix Seeger
2002-09-28  9:59         ` David S. Miller
2002-09-28 10:10           ` Thunder from the hill
2002-09-28 10:04             ` David S. Miller
2002-09-28 10:33           ` Felix Seeger
2002-09-28 10:35             ` David S. Miller
2002-09-28 11:02               ` FD Cami
2002-09-28 10:48                 ` David S. Miller
2002-09-28 11:13               ` Michael Clark
2002-09-29  0:00                 ` Elladan
2002-09-29  5:50                   ` Michael Clark [this message]
2002-09-29  7:37                     ` Elladan
2002-09-29 12:12                 ` Simon Fowler
2002-09-28 11:35               ` Thunder from the hill
2002-09-28 11:34                 ` David S. Miller
2002-09-29  0:42                   ` Kristofer T. Karas
2002-09-28 10:08         ` Alan Cox
2002-09-28 10:36           ` Felix Seeger
2002-09-28 12:46         ` Krzysztof Halasa
2002-09-29 18:06           ` Felix Seeger
2002-09-28 10:23     ` Marc Giger
2002-09-28 10:31       ` Felix Seeger
2002-09-29  5:41 Dieter Nützel
2002-09-30  6:47 ` Kristofer T. Karas
2002-10-01 12:32   ` Dieter Nützel

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=3D9694AC.9020907@metaparadigm.com \
    --to=michael@metaparadigm.com \
    --cc=davem@redhat.com \
    --cc=elladan@eskimo.com \
    --cc=felix.seeger@gmx.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;
as well as URLs for NNTP newsgroup(s).