On Wed, 5 Feb 2003 08:48:53 -0600
Curtis L. Olson [EMAIL PROTECTED] wrote:
Richard Keech writes:
support for 3D capabilities of NVIDIA cards is not open
source. you
will need binary-only kernel modules (from nvidia) to
make this
work. many report good success with these drivers,
however
On Wed, 05 Feb 2003 10:26:24 -0500,
brett holcomb [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
On Wed, 5 Feb 2003 08:48:53 -0600
Curtis L. Olson [EMAIL PROTECTED] wrote:
Richard Keech writes:
support for 3D capabilities of NVIDIA cards is not open
source. you will need
On Wednesday 05 February 2003 10:26 am, brett holcomb wrote:
On Wed, 5 Feb 2003 08:48:53 -0600
Curtis L. Olson [EMAIL PROTECTED] wrote:
Richard Keech writes:
support for 3D capabilities of NVIDIA cards is not open
source. you
will need binary-only kernel modules (from nvidia) to
make
I am still mystified about the NVidia/AMD problem if it is such. I have
read and done everything mentioned on the SuSE site. On SuSE 8.1 with
the SuSE kernels, including the recent SuSE internal 2.4.21, there are
no problems. On the 2.4.20 kernel from ftp.kernel.org, I get everything
up
On 5 Feb 2003, Sid Boyce wrote:
I am still mystified about the NVidia/AMD problem if it is such. I have
read and done everything mentioned on the SuSE site. On SuSE 8.1 with
the SuSE kernels, including the recent SuSE internal 2.4.21, there are
no problems. On the 2.4.20 kernel from
Sid, I think if you go back to earlier kernels, 2.4.10ish would
certainly do it, you'd have a better chance of experiencing
the problem.
Jon, the AMD problem was a known bug that AMD MS put out fixes
for.
---Original Message---
From: Jon Stockill [EMAIL PROTECTED]
Sent: 02/05/03 11:21
On Wed, 05 Feb 2003 13:43:54 -0500
John Check [EMAIL PROTECTED] wrote:
On Wednesday 05 February 2003 10:26 am, brett holcomb
wrote:
On Wed, 5 Feb 2003 08:48:53 -0600
First, who cares if it's binary. Yes, RS and his group
will squawk and yes, I like and use Opensource wherever
I
can but in
Tony Peden writes:
Sid, I think if you go back to earlier kernels, 2.4.10ish would
certainly do it, you'd have a better chance of experiencing
the problem.
Jon, the AMD problem was a known bug that AMD MS put out fixes
for.
And the problem on the Linux side was that the wording of the
