From: Mark Knecht <markknecht@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3D video card recommendations
Date: Fri, 4 Nov 2005 07:10:27 -0800 [thread overview]
Message-ID: <5bdc1c8b0511040710q4a4ce3eend6edc2b4027e33b0@mail.gmail.com> (raw)
In-Reply-To: <1131112605.14381.34.camel@localhost.localdomain>
On 11/4/05, Steven Rostedt <rostedt@goodmis.org> wrote:
> I'm currently putting together (ordering parts for) another machine. It
> will be a AMD64 X2. Now I'm looking into a video card for this. Up till
> now, I've always used NVidia. But I also want to test 3D acceleration
> under Ingo's -rt patch. So now I need something that does not have a
> priority module.
>
> I'm not much of a gamer, although I do play every so often. So I don't
> need the highest quality card, but I also want something that is still
> pretty good. For example, I currently have a NVidia GeForce 6800 GT
> card. So I'm hoping to get something equivalent.
>
> I'm looking at the ATI Radeons.
>
> Any recommendations? (links to info would also be nice ;-)
>
> Thanks,
>
> -- Steve
Not a recommendation. Just a point to be aware of. The ATI Radeons, to
get the best acceleration, seem to require that you use the ATI closed
source drivers. Currently I haven't found an ATI closed source driver
that supports 2.6.14. so I'm forced to use the Xorg radeon driver. I
have no idea if this is very good. I don't think so as my glxgear
numbers are pretty low. Much lower than the ATI driver running on
2.6.13-X.
NOTE: I'm horrible at setting up all the 3D stuff as I don't
understand what to chose and what to avoid. This could be far better
than the results I get!
- Mark
next prev parent reply other threads:[~2005-11-04 15:10 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 13:56 Steven Rostedt
2005-11-04 15:10 ` Mark Knecht [this message]
2005-11-04 15:14 ` Paweł Sikora
2005-11-04 15:22 ` Steven Rostedt
[not found] ` <ec92bc30511040730g2ad412ddsb3ac63f701de6c97@mail.gmail.com>
2005-11-04 15:39 ` Anshuman Gholap
2005-11-06 23:46 ` Nix
2005-11-07 7:42 ` Arjan van de Ven
2005-11-07 12:42 ` Steven Rostedt
2005-11-07 12:55 ` Hugo Mills
2005-11-07 14:22 ` Paweł Sikora
2005-11-07 15:07 ` Paweł Sikora
2005-11-07 14:51 ` Ville Syrjälä
2005-11-07 15:50 ` Jerome Glisse
2005-11-07 16:24 ` Gerhard Mack
2005-11-07 16:35 ` Ian Romanick
2005-11-07 16:41 ` Ville Syrjälä
2005-11-07 14:24 ` Alan Cox
2005-11-07 13:59 ` Xavier Bestel
2005-11-07 16:17 ` Gerhard Mack
2005-11-07 15:20 ` Toon van der Pas
2005-11-07 15:31 ` Arjan van de Ven
2005-11-07 17:35 ` Steven Rostedt
2005-11-08 22:08 ` Matthias Andree
2005-11-08 22:18 ` John Stoffel
2005-11-08 22:37 ` Tue, 8 Nov 2005 23:37:43 +0100
2005-11-09 1:34 ` Alan Cox
2005-11-07 17:00 ` Diego Calleja
2005-11-07 17:30 ` Steven Rostedt
2005-11-07 17:44 ` Gerhard Mack
2005-11-07 17:53 ` Steven Rostedt
2005-11-07 17:56 ` Gerhard Mack
2005-11-07 18:01 ` Mark Knecht
2005-11-07 18:15 ` Steven Rostedt
2005-11-07 18:31 ` Mark Knecht
2005-11-07 19:08 ` Gerhard Mack
2005-11-07 19:09 ` Mark Knecht
2005-11-07 19:05 ` Lee Revell
2005-11-07 19:23 ` Mark Knecht
2005-11-07 19:47 ` Steven Rostedt
2005-11-12 9:11 ` Lee Revell
2005-11-07 18:19 ` Joel Jaeggli
2005-11-08 18:59 ` Stefan Seyfried
2005-11-08 19:06 ` Lennart Sorensen
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=5bdc1c8b0511040710q4a4ce3eend6edc2b4027e33b0@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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®