SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It looks as if that version of the nvidia driver will not build on 2.6.30+
I found this blurb on the interweb. I have no idea if the fix works.
Code:
According to lkml.org [1] proc_dir_entry::owner field was removed in
2.6.30, so for now you can fix it by simply removing or commenting all
the lines using proc_dir_entry::owner in nv.c.
Krzesimir Nowak
[1] http://lkml.org/lkml/2009/1/26/342
you need to download a more recent package from the nvidia site
It looks as if that version of the nvidia driver will not build on 2.6.30+
I could not build the 180.29 kernel module with the 2.6.30 kernel. I did not pursue further because I was only testing my on-board NIC, which had lock-up problems with the 2.6.29.x kernels. However, as vonbiber shared, apparently more recent nvidia releases compile with the newer kernels.
Yes, I can confirm that the latest drivers work on kernels 2.6.30 - and definitely on kernels > 2.6.25 (because I'm using a custom compiled 2.6.25-20 on my debian box).
As a general rule, whenever possible I download the latest drivers and compile them. In the rare occasion that it does break support for a newer kernel, I revert to the earlier version.
IT WORKED... downloading the new drivers from nvidia (185.18.14 i think) did the trick! i rebuilt the nvidia-kernel and nvidia-driver packages from sbo.
thank you all for all your help. the amount of knowledge and willingness to help on these forums is amazing. thank you all again.
1. I don't know what the SBo script does for the nvidia driver, I would not use it since nvidia have their own script that seems to always work
2. There is actually a -devel package in Slackware just for the kernel, d/kernel-headers is the package and it installs kernel includes into /usr/include specific to the version that is used by glibc
3. You now have 2 different versions of the kernel headers on your system and depending on what is going on this could break
1. I don't know what the SBo script does for the nvidia driver, I would not use it since nvidia have their own script that seems to always work
it makes a package around the binary is the way i see it... makes it easier to uninstall... i like sbo packages...
Quote:
Originally Posted by wildwizard
2. There is actually a -devel package in Slackware just for the kernel, d/kernel-headers is the package and it installs kernel includes into /usr/include specific to the version that is used by glibc
wasn't aware of any devel packages in slackware... but then again i am not aware and that doesn't mean much
Quote:
Originally Posted by wildwizard
3. You now have 2 different versions of the kernel headers on your system and depending on what is going on this could break
but i have /usr/src/linux pointing to the current running kernel... shouldn't that be ok?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.