Nvidia and kernel-2.6.33

stormtracknole · 03-02-2010, 12:41 AM

I know that current just pushed kernel 2.6.33 down, but has anyone been successful in building the nvidia drivers against this new kernel? I'm not having any success with the 190 driver and the 195 beta driver. There are some patches that I found on the nvidia forum, but so far, nothing is working. Any ideas? Thanks ahead of time!

GrapefruiTgirl · 03-02-2010, 12:45 AM

http://www.nvnews.net/vbulletin/show...0&postcount=20

I'm going to guess that these patches at the above link, are among the ones you have tried unsuccessfully? Last I read, they worked for the 33-rc kernel according to another LQ member (sorry cannot remember who at this time) but if you have NOT tried the patch(es) at this link, or the ones you DID try are different than these ones, please do tell

As yet, I haven't delved into rebuilding my nvidia driver on a .33 kernel since I'm still on 32.x whatever the latest x is, so cannot comment from direct experience yet.

ponce · 03-02-2010, 12:51 AM

this one should work with 2.6.33: supported hardware is here.
I guess some patches could be found on nvidia linux forum for legacy drivers with 2.6.33 (but I haven't looked).

stormtracknole · 03-02-2010, 01:37 AM

GrapefruitGirl, yes, those were the patches that I used!

Ponce, I tried your link, and downloaded the latest beta. At least this time, the script can find my kernel source. However, I keep getting these errors:

Code:

ERROR: Unable to open                                                        
         '/usr/X11R6/lib/xorg/modules/extensions/libglx.so.190.42' for reading 
         (No such file or directory)

ERROR: Unable to open '/usr/X11R6/lib/xorg/modules/extensions/libglx.so' for 
         reading (No such file or directory

ERROR: Unable to open '/usr/lib/xorg/modules/extensions/libglx.so.190.42'    
         for reading (No such file or directory)

I'm not sure if the problem lies with the new kernel or the latest xorg.

bathory · 03-02-2010, 02:05 AM

You should use nvidia drivers version 190.53 or 195.30 with these patches
You might take a look at this same thread.

Regards

sahko · 03-02-2010, 02:28 AM

Quote:

Originally Posted by bathory

You should use nvidia drivers version 190.53 or 195.30 with these patches
You might take a look at this same thread.

Regards

This thread started and ended 1 day before a newer version was released though..
Im with ponce but havent upgraded yet to make sure it works ok for me.

bathory · 03-02-2010, 02:33 AM

Well, it works with 2.6.33

Code:

# uname -r
2.6.33

# cat /proc/driver/nvidia/version
NVRM version: NVIDIA UNIX x86 Kernel Module  190.53  Tue Dec  8 18:51:41 PST 2009
GCC version:  gcc version 4.4.3 (GCC)

botnet · 03-02-2010, 03:17 AM

im stuck with vesa drivers right now

NVIDIA-Linux-x86_64-195.36.08-pkg0.run

gives me invalid module format errors on agpgart.ko and nvidia.ko

NVIDIA-Linux-x86_64-190.53-pkg2.run

does not compile due to unable to determine kernel source versions

not using any xorg.conf gives me a garbled X (is that the nv driver or nouveau)

going to try the patch shortly...(once i figure out this libpng thing...)

the patch doesnt work for me, gives me the same invalid module format errors (libpng still is not giving me icons either--i have to use chrome to post this since firefox has no submit buttons)

bathory · 03-02-2010, 04:15 AM

Quote:

NVIDIA-Linux-x86_64-195.36.08-pkg0.run
gives me invalid module format errors on agpgart.ko and nvidia.ko

You have to configure the kernel with something like:

Quote:

CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set

CONFIG_AGP=m
CONFIG_AGP_INTEL=m
CONFIG_AGP_NVIDIA=m

FYI the latest nvidia--195.36.0 does not need patching for 2.6.33 kernel.

Regards

botnet · 03-02-2010, 04:27 AM

Quote:

Originally Posted by bathory

the latest nvidia--195.36.0 does not need patching for 2.6.33 kernel.

the latest nvidia 195.36.08 gives invalid module format errors when starting X

bathory · 03-02-2010, 04:39 AM

You have to recompile your kernel with the above options (maybe you don't need agp_intel if don't have an intel chipset as I do) prior building the nvidia module.

sahko · 03-02-2010, 06:12 AM

Quote:

Originally Posted by bathory

You have to recompile your kernel with the above options (maybe you don't need agp_intel if don't have an intel chipset as I do) prior building the nvidia module.

The 2.6.32.7 kernel didnt have this as a module either. What changed?

PS. Someone should tell Pat to enable it.

GrapefruiTgirl · 03-02-2010, 10:31 AM

# Bathory -- In your post above (#9) are you saying that the PREEMPTIBLE kernel option(s) will not work with the new driver? Or were you mainly pointing at the CONFIG_AGP options in that post?

I'mma have to fiddle with this today

since I almost always run the latest kernel and latest nV driver.. We'll see...

Sasha

stormtracknole · 03-02-2010, 02:12 PM

Quote:

Originally Posted by bathory

You have to configure the kernel with something like:

FYI the latest nvidia--195.36.0 does not need patching for 2.6.33 kernel.

Regards

Ok, so I tried your changes and recompiled the kernel again. The driver finally compiled, but I still ran into a bit of a snag. The "NOUVEAU" driver was enabled to load as a module. When that happens, you won't be able to install the nvidia driver. So, there are two things one can do, you can either rebuild the kernel and comment out the nouveau driver or add the following to /etc/modprobe.d/blacklist.conf:

Code:

blacklist nouveau

Reboot and run the nvidia script to install the driver.

For the record, here's my preempt section on my .config file:

Code:

CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set

Thanks everyone for the help!

bathory · 03-02-2010, 02:58 PM

Quote:

Originally Posted by GrapefruiTgirl

# Bathory -- In your post above (#9) are you saying that the PREEMPTIBLE kernel option(s) will not work with the new driver? Or were you mainly pointing at the CONFIG_AGP options in that post?

Yup, with CONFIG_PREEMPT set, you'll get the invalid module format.

Quote:

I'mma have to fiddle with this today

since I almost always run the latest kernel and latest nV driver.. We'll see.

That makes two of us

Cheers