Printable View
Please follow this method instead of the OP's method .. installing from a ppa/deb file will always work with dkms which is needed if there are any kernel updates. Plus its easier to remove and change to another driver version if you need to.Quote:
Originally Posted by anonymous_user
I'm actually very heavily against DKMS, but that is just for my own personal reasons.Quote:
Originally Posted by el-mar01
Infact, I'll just quote what has already been said by an affiliate several months ago.
The automatic upgrading of the NViDIA drivers is included in this HowTO, in the form of a small script that is kept in /etc/kernel/postinst.dQuote:
I admit that I am biased because I think DKMS is completely pointless. I'm happy to point people at very simple ways to keep nvidia, vbox, ALSA, v4l, etc. up to date on kernel updates. They all consist of 10-20 line scripts that are readable, understandable, and work without any "magic". It's quite obvious what they are trying to do and many hundreds (thousands (no, millions)) of kernels have been installed using these methods. The link I've pointed to twice us literally the method in which grub updates itself. Kernel updates for proprietary drivers have never been broken. DKMS tries to fix something that was never a problem in the first place.
IMO, I prefer to have a collect of my own small scripts, as it is my own warranty that they won't break on me.
Regards
Iain
Does anyone know if this driver is compatible with kernel 2.6.30-rc3?
Great guide btw :)
Thanks!
Working great on my Dell d620 :)
2.6.30 is out already??Quote:
Originally Posted by KhaaL
Oh man, I'm so behind the times. ;)
I will pull the git and test it out for you tonight.
Regards
Iain
Much appriciated! If you're lazy like me, there are .debs here.Quote:
Originally Posted by tinivole
Nah ... I don't trust them ;)Quote:
Originally Posted by KhaaL
Anyway, I have some good news and some bad news.
Good News:
W00t!!! It works!!!
Bad News:
It won't compile *as is*.
After a review of the error output after the first time I tried, and a comparison between the 2.6.28 and 2.6.29/30 kernel sources, I found that they had infact removed an element from the struct proc_dir_entry that NViDIA uses (yet another coincidence?).
Although, it is nothing to worry about, I created a patch to supplement the change. ;)
[SNIP]
After finding out about/reviewing the new beta, it appears that the nv-devs are aware of this breakage and have already fixed it in their own way.
I'll update the HowTO to cover this later this today.
[UPDATE]
Changed! Included the download links to the newest beta drivers - which are compatible with the 2.6.29 and .30 kernels - in the original post.
Although, may I point out that although I've split the '185.19' and the '185.18.04' downloads between the pre-2.6.28 and the post-2.6.29 kernels, the newest driver (185.18.04) from what I've reviewed is just a minor upgrade to fix the compatibility issues with newer kernels, and should work just fine on the earlier versions too.
In due time I may update this, but I will have to test it first though.
Regards
Iain
When I do Ctrl+Alt+F1 the screen just goes blank and I have to reboot.
Im running ubuntu studio 9.04 fresh install.
Also I tried the other way adding the repositories, but can someone explain the last bit "Now the drivers will be available in jockey (Restricted Drivers Manager)."
How do I do that?
Did you try any of the other tty terminals?Quote:
Originally Posted by aquanuke
Ctrl+Alt+F2 through to Ctrl+Alt+F6 ?
Your GUI workspace is on Ctrl+Alt+F7, just so you know in the future... there is no need to reboot.
I think he means System->Administration->Hardware DriversQuote:
Also I tried the other way adding the repositories, but can someone explain the last bit "Now the drivers will be available in jockey (Restricted Drivers Manager)."
How do I do that?
Regards
Iain
Thanks Ive kind of got around that now X is dead. But problem now is I get kernel error when compiling the nvidia driver due to ubuntu-studio using the low latency kernel.
Anyone know what I need to do to get around that?