Anyone having problems with Nvidia's latest .6111 driver and the
2.6.8.1 kernel?

I'd been using the driver on a 2.4.26 machine with no problems. Then,
I built a vanilla 2.6.8.1 kernel, rebooted, installed the Nvidia
driver for the new kernel, and checked xorg.conf. (No changes were
needed since it was already setup correctly.)

When I ran startx, X came up, minus the Nvidia splash screen and with
X writing a "cannot find Nvidia driver" line to its log. If it could
not find the Nvidia driver, I'm not sure what driver it did, in fact,
use. My experience has been that X does not run when it cannot find
the specified dirver; it does not "fall back" to another driver.

In any case, I double-checked things. The driver was exactly where it
should be. I uninstalled the driver for 2.4.26. Regardless, the
behavior remained and the only error logged was that line about the
"missing" driver.

This is on a Slackware 10 (now current) machine running Slack's Xorg
driver.

wg wrote:

> Anyone having problems with Nvidia's latest .6111 driver and the
> 2.6.8.1 kernel?

Nope works fine, make sure your running under the new kernel when you
install the driver or it will end up in the wrong place and wont work

--
While having never invented a sin, I'm trying to perfect several.

In <8d755520.0409080351.3ebe5ff4@posting.google.com >, wg wrote:

> Anyone having problems with Nvidia's latest .6111 driver and the 2.6.8.1
> kernel?
>
> I'd been using the driver on a 2.4.26 machine with no problems. Then, I
> built a vanilla 2.6.8.1 kernel, rebooted, installed the Nvidia driver
> for the new kernel, and checked xorg.conf. (No changes were needed since
> it was already setup correctly.)
>
> When I ran startx, X came up, minus the Nvidia splash screen and with X
> writing a "cannot find Nvidia driver" line to its log. If it could not
> find the Nvidia driver, I'm not sure what driver it did, in fact, use.
> My experience has been that X does not run when it cannot find the
> specified dirver; it does not "fall back" to another driver.
>

I had a similar problem on a system I just upgraded to 2.6. Try loading
the nvidia kernel driver manually before starting X; that fixed it for me.
I don't know why it wouldn't load the driver automatically when X starts
with 2.6, but it doesn't seem to. If it works then, you can just add
something to your startup scripts to load it at boot time.

--
Not to have been a dupe, that will have been my best possesion, my best
deed, to have been a dupe, wishing I wasn't, thinking I wasn't, knowing
I was, not being a dupe of not being a dupe.
--Samuel Beckett, The Unnamable

"wg" <enloop@yahoo.com> wrote in message
news:8d755520.0409080351.3ebe5ff4@posting.google.c om...

> Anyone having problems with Nvidia's latest .6111 driver and the
> 2.6.8.1 kernel?
>
> I'd been using the driver on a 2.4.26 machine with no problems. Then,
> I built a vanilla 2.6.8.1 kernel, rebooted, installed the Nvidia
> driver for the new kernel, and checked xorg.conf. (No changes were
> needed since it was already setup correctly.)
>
> When I ran startx, X came up, minus the Nvidia splash screen and with
> X writing a "cannot find Nvidia driver" line to its log. If it could
> not find the Nvidia driver, I'm not sure what driver it did, in fact,
> use. My experience has been that X does not run when it cannot find
> the specified dirver; it does not "fall back" to another driver.
>
> In any case, I double-checked things. The driver was exactly where it
> should be. I uninstalled the driver for 2.4.26. Regardless, the
> behavior remained and the only error logged was that line about the
> "missing" driver.
>
> This is on a Slackware 10 (now current) machine running Slack's Xorg
> driver.

Not sure, but could this have anything to do with conflicts between the
nVIDIA driver and Riva frame-buffer support?
Try compiling a custom kernel, with Riva frame-buffer support disabled (it
sits under the "Console drivers" --> "Frame-buffer support" heading of the
kernel configuration process); works for me every time.

--Luc.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 8 Sep 2004 04:51:45 -0700, wg wrote:
> Anyone having problems with Nvidia's latest .6111 driver and the
> 2.6.8.1 kernel?
>
> I'd been using the driver on a 2.4.26 machine with no problems. Then,
> I built a vanilla 2.6.8.1 kernel, rebooted, installed the Nvidia
> driver for the new kernel, and checked xorg.conf. (No changes were
> needed since it was already setup correctly.)
>
> When I ran startx, X came up, minus the Nvidia splash screen and with
> X writing a "cannot find Nvidia driver" line to its log. If it could
> not find the Nvidia driver, I'm not sure what driver it did, in fact,
> use. My experience has been that X does not run when it cannot find
> the specified dirver; it does not "fall back" to another driver.
>
> In any case, I double-checked things. The driver was exactly where it
> should be. I uninstalled the driver for 2.4.26. Regardless, the
> behavior remained and the only error logged was that line about the
> "missing" driver.
>
> This is on a Slackware 10 (now current) machine running Slack's Xorg
> driver.

I ran into a similar problem last night, I decided to give 2.6.8.1
(with latest acpi and voluntary-preempt patches) a try and I
couldn't start X with the nvidia (.6111) module even though it was the same
xorg.conf file that worked with 2.6.7.

Strangely, what worked for me was adding:
Option "NvAGP" "1"
to the Section "Device" section of xorg.conf. Why it seems strange,
is that dmesg shows:
NVRM: not using NVAGP, AGPGART is loaded!!
NVRM: not using NVAGP, AGPGART is loaded!!

But X loads now...not 100% happy, but it works.

Also Slackware 10/current on a Dell Inspiron 5150 with
NVidia GeForce FX Go5200 (1600x1200)

Brad



-----BEGIN PGP SIGNATURE-----

iD8DBQFBQPljkDp4KjYna1ARAjB9AJ9jcNiaqeRBoFzLJtlhW7 Zh3rPWcACeLibj
HenJ5TDES2tLFjO0O9HYCss=
=YWBd
-----END PGP SIGNATURE-----