[SOLVED] New -current kernel and Nvidia 304.xx driver issue
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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
New -current kernel and Nvidia 304.xx driver issue
I just installed the new slackware-current (3.7.10 kernel) on one of my older computers (Athlon64-X2 4600 with GeForce 7300 video card) and have discovered a possible problem with the Nvidia 304.84 driver. When I exit X back to the console, I just get a black screen. The previous driver (304.64) won't build with the new kernel. The problem was duplicated on an older machine running 64-13.1 with a Geforce 6200 card. Is there a parameter I can add to fix this, or is this another Nvidia oops?
Hi, I had the same problem. 304.84 driver seems to be buggy. If you want to use older driver (304.64) with current kernel (I use it with recent 3.9-rc2), you need to patch it. Patches are available here: http://www.lwfinger.com/nvidia_patches/. The one you need is http://www.lwfinger.com/nvidia_patch...60.run_for_3.7. You also have to make symlink using command:
ln -s /usr/src/linux-3.7.10/include/generated/uapi/linux/version.h /usr/src/linux-3.7.10/include/linux/version.h
Tried the patch, and failed with a different error: the 3.7.10 kernel is now a "Xen" kernel. Apparently the 304.84 driver added Xen support, which I suspect is where some of its problems lie.
I guess for now on this machine I can either stick to the nouveau driver or go with the new prop driver knowing I will have to reboot when I exit X.
FYI, just tried with 304.84 and -current's 3.7.10 using SBo scripts (just cutted the two libnvidia-encode lines from nvidia-driver.Slackbuild because they are for the 310.xx series) and everything went fine without any patch.
Just to confirm that I see the same problem of a blank screen on exit from X with nVidia 304.84 driver, X Server 1.14.0 and 3.7.10 kernel with my GeForce 7300 LE.
The patched nVidia 304.64 driver did build with the addition of the symlink posted by m23 in post #2 but fails to load when starting X due to the ABI in X Server 1.14.0 being too new. Using the option "IgnoreABI" "true" in the ServerFlags section of xorg.conf bypassed the ABI check, but X failed to start with segfault errors in /var/log/Xorg.0.log
It appears that a newer driver is not available for this nVidia GPU.