[SOLVED] Is anyone succesfully running 2.6.32 with the proprietary NVIDIA driver?
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Is anyone succesfully running 2.6.32 with the proprietary NVIDIA driver?
I've been trying to figure out the cause of system hangs with slack 13 for a a week or so. I get random total freezes with the keyboard LED's blinking at me and the only solution is to do a hard-reset. I was using a self-compiled 188.8.131.52 kernel on 32bit Slack with similar results, but thought it had more to do with several bad starts as I got used to Slack's way of doing things... eventually I decided I'd made enough bad starts with that installation and after reading a bit about _current fixing some stability issues added another installation to my machine using Slackware64 and upgrading to _current. It worked great, then I installed the NVIDIA proprietary driver. The system hangs are back.
Sometimes they happen quickly, sometimes they take hours, sometimes while I'm working, sometimes when the machine has been idle for hours. For a couple of days I've been going back and forth between the NVIDIA propreitary and the nv driver. I've run memtest86 for 4.5 hours and not a single error, I'm running this on a new HD, I even upgraded the case fan (the old one was starting to complain!).
I've also installed different versions of the driver 185.x.x, 190.42.x. I've used slackbuilds, I've used "sh NVIDA.xxx.RUN" I've said "yes" to everything the installer asked, I've said "no".
So far no hangs with the nv driver. I've been leaving one or the other running at all times and no hangs with the nv driver, but within hours with the proprietary driver.
All that is to say I'm confident the issue is with the NVIDIA proprietary driver, OR something in my kernel options that only shows up when I'm using the NVIDIA driver.
Is anyone else running this successfully?
SLACKWARE64 kernel 2.6.32 (same behavior on 32bit with 184.108.40.206)
compiled kernel with "make oldconfig" then "make localmodconfig" BEFORE the NVIDIA driver was installed.
ext3 filesystem (same behavior with ext4 on previous installation)
Not having a xorg.conf only works with opensource drivers. That means all the xf86-video-*'s
Understood. When I've installed the driver, I then set an xorg.conf file in order to load the NVIDIA driver. When I getanother system freeze and I realize that I still have not fixed the issue, then I use the above method to do away with whatever NVIDIA driver that I was using so that I can startx with the nv driver since I never know if I'm 2 minutes or 12 hours from a system freeze with the NVIDIA driver.
I'm not sure if this will help you or not, but I had some weird problems with older versions of the kernel & the proprietary driver - many random freezes (sometimes when I was on, sometimes when I wasn't using the system), and the freezes always happened in X.
I think the NVIDIA-XXXXXX-pkg-run script from their site is good for fixing your xconfig (it will back up the old one), it will also search for and replace /disable the old nvidiafb modules and it also does a very good job at removing any wierd opengl/mesagl libs/dependencies and replacing them with nonconflicting ones.... their installer code is pretty awseome. I do not recommend using a pre-built package of the NVIDIA drivers.
just grab the kernel source and unpack it to /usr/src/linux-kernelversion (or if you install it from a repository/package it will do it for you) then run the nvidia installer from runlevel 3 (X, or Xlogin like KDM not started)
don't have to worry about much configuration then. In like 4 years i never had a problem doing it this way...
also there were some command line arguments to pass to the PKG-run script from NVidia that would unpack that and put a folder with some docs and let you make/compile your own module for your kernel, in those docs is just about everything you can check to see what could be causing your probs...
I'm currently running 220.127.116.11 KDE4 no problems
Last edited by flayzernax; 12-16-2009 at 12:22 PM.
Thanks for all of the replies. I'm not sure where things stand at the moment as I'm testing again. I'm trying passing kernel options from the post above at the moment. I am fairly sure that my problems arise from 1 of 2 sources: I'm missing something when I configure my own kernels or perhaps the video card is experiencing a slow and at least for me PAINFUL death! LOL
On the bright side I've earned some good experience with compiling/recompiling kernels
setting up dkms
getting around without X
how to pass kernel options at boot
AND I haven't had to redo a Slackbuild on this entire installation (hey, it was a slow start with slack LOL)
It works fine.
Did you removepkg the slackbuilds driver before installing the Nvidia-XX.run driver?
EDIT: Just patched to 18.104.22.168 and works here too.
I have to ask.....what path did you take to your current kernel? Were there intermediate kernels between the stock kernel and current? What make target did you use? I've tried 22.214.171.124 and 2.6.32. and I've tried multiple builds. Most recently I did
from the 126.96.36.199 that doesn't fail and just held enter at the new options.
I've followed alien BOB'S slackware kernel roll to the letter, even a seperate build directory at /kernelbuild. I am just stumped. I have yet to get 188.8.131.52 to hang, and I can't get 2.6.32 to hang when I run without the NVIDIA proprietary driver.
I just compiled 184.108.40.206 and I'm running the latest nvidia drivers with no problems. One thing that I always do when compiling a new kernel, I copy the .config file from the stock Slackware kernel into the new one. For example:
Thanks to PTrenholme at http://www.linuxquestions.org/questi...cpugpu-776169/ pointing me towards the bios again.
I am running on the latest stable kernel with no crashes for 15 hours now! I feel like I should have caught this 2 weeks ago when I looked in the bios but the setting "pci express frequency = auto" looked innocuous enough, but setting it manually seems to have been the answer all along.
I'm still not sure what changed between 220.127.116.11 and 18.104.22.168 that caused the bios setting to no longer work, any ideas or pointers on figuring that one out are appreciated.
On the bright side I am a much smarter noob today than I was 2 weeks ago with all the things I learned that DIDN'T WORK! LOL