From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: John M Collins <jmc@xisl.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Exploit in 2.6 kernels
Date: Thu, 14 Apr 2005 14:46:31 +0200 [thread overview]
Message-ID: <425E6627.9080405@aitel.hist.no> (raw)
In-Reply-To: <20050413125921.GN17865@csclub.uwaterloo.ca>
Lennart Sorensen wrote:
>On Wed, Apr 13, 2005 at 11:47:46AM +0200, Helge Hafting wrote:
>
>
>>You're not. Complain to nvidia - using both email and snailmail.
>>If everybody with such problems did that, chances are they see
>>the light someday. Oh, and complain to the guy handing out
>>nvidia cards like confetti, state your preference for some other
>>card. Perhaps that is easier to achieve.
>>
>>
>
>What card would you recomend to people?
>
>
If all else fail - an *old* card. This wasn't a problem before,
therefore it doesn't have to be now. Unless you want to run
very new software that won't perform on those older cards.
Todays faster cpus may help though.
Look to http://dri.freedesktop.org/wiki/ for information about
which cards have open drivers and how well they work.
Some cards have specs available, others are reverse-engineered
to the extent that a driver have been written.
>
>
>>Whats wrong with tainting? It is just a message, telling you that
>>the kernel is unsupported. In this case because you're running a
>>closed-source module. The tainting message itself does not do
>>anything bad. There is a way - which is to write an open nvidia
>>driver. To do that, you'll need to get the specs out of nvidia or
>>figure it out by reverse-engineering some other nvidia driver. Either
>>approach is hard, so people generally find it cheaper to just buy
>>a supported card.
>>
>>
>
>It is becoming harder and harder to find supported cards it seems.
>Finding a card with decent 2D drivers for X can still be done, but 3D is
>just not really an option it seems. Even 2D seems to be a problem on
>many cards if you don't use a binary only driver.
>
>
I have the impression that 2D is fine with ATI cards, even those
that doesn't have open 3D drivers. And even a really old low-end
card performs fine for 2D work. Even the unaccelerated
framebuffer drivers seems to have enough performance
for 2D in most cases. The cpu is fast these days. :-)
Helge Hafting
next prev parent reply other threads:[~2005-04-14 12:42 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 9:34 John M Collins
2005-04-12 12:24 ` Baruch Even
2005-04-12 15:00 ` John M Collins
2005-04-12 21:08 ` Chris Wright
2005-04-12 21:32 ` John M Collins
2005-04-13 5:28 ` Valdis.Kletnieks
2005-04-13 9:47 ` Helge Hafting
2005-04-13 12:59 ` Lennart Sorensen
2005-04-13 13:06 ` Lars Marowsky-Bree
2005-04-13 13:23 ` Lennart Sorensen
2005-04-13 14:01 ` John M Collins
2005-04-16 2:32 ` Adrian Bunk
2005-04-13 15:22 ` Chris Friesen
2005-04-14 14:01 ` Helge Hafting
2005-04-20 18:17 ` nVidia stuff again Doug Ledford
2005-04-20 23:12 ` Dave Airlie
2005-04-21 11:23 ` Helge Hafting
2005-04-21 12:15 ` Doug Ledford
2005-04-21 12:54 ` Dave Airlie
2005-04-21 13:35 ` Lennart Sorensen
2005-04-21 14:43 ` Manu Abraham
2005-04-21 21:17 ` J.A. Magallon
2005-04-22 14:44 ` Arjan van de Ven
2005-04-15 15:00 ` Exploit in 2.6 kernels Alan Cox
2005-04-15 16:06 ` Dave Airlie
2005-04-15 16:19 ` Duncan Sands
2005-04-14 12:46 ` Helge Hafting [this message]
2005-05-05 22:00 ` Olaf Titz
2005-04-13 13:02 ` Lennart Sorensen
2005-04-13 14:26 ` Eric Rannaud
2005-04-13 14:41 ` Lennart Sorensen
2005-04-14 20:02 ` Greg Folkert
2005-04-14 22:27 ` John M Collins
2005-05-09 18:37 ` Alessandro Salvatori
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=425E6627.9080405@aitel.hist.no \
--to=helge.hafting@aitel.hist.no \
--cc=jmc@xisl.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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®