nvidia kernel module does not load

Kresp · Tux's lil' helper Joined: 17 Oct 2016 Posts: 77

My GPU is NVidia GT 9800. Nouveau works fine, but I need proprietary driver ATM.

I removed nouveau driver from kernel at all for the time being and installed nvidia-drivers-340.102 (340 is the last driver that supports this GPU).

Nvidia drivers don't compile cleanly on 4.10 kernel. Patches for the latest driver from Ubuntu/Arch don't apply to 340 so I added this patch to portage:

Roman_Gruber · Posted: Tue Apr 04, 2017 5:01 pm Post subject:

I had previous a Asus g70sg notebook. in the early days i had to patch my kernel. I did not use the patch command, i used an editor and manually changed those affected code lines.

Most of the time, in my experience, the kernel symbols were just changed.

I suggest, you open the patch in one window, see what should be changed, and change those lines by hand with an editor, with search, manually replace, and verifiy if there are other lines affected.

I did that for quite a while when my notebook was brand new => wrong memory bars for the nvidia gpu. later some other issues, adn end of life, two years ago, patch so the binary driver works.

Also when you have such dated gpu, you should try to stay at a dated kernel. so it makes things easier for you.

--

well

https://www.msi.com/Motherboard/X370-XPOWER-GAMING-TITANIUM.html#productFeature-section

Any reason why you are not getting something more power efficent from second hand? your gpu is, i assume wihtout checking 8 year old gpu. your mainboard is brand new.

--

you need to check which kernels symbols what else has changed over htose kernel versions to get the binary driver working. I also expect issues with the xorg server maybe ...

Kresp · Tux's lil' helper Joined: 17 Oct 2016 Posts: 77

genterminl · Posted: Tue Apr 04, 2017 5:49 pm Post subject:

I don't know if this deserves a separate thread, but I get the same (or very similar) errors. This happened after I upgraded nvidia-drivers from 340-101.r1 to 340.102. Reverting (and reboot) and everything works fine again.

My GPU is: NVIDIA Corporation G84GL [Quadro FX 1700] (rev a1). I did not notice any compile errors when emerging the new driver. I am currently on gentoo-sources 4.9.6-r1, but will shortly try 4.9.16, to see if it makes any difference.

I also find it odd that lspci -k shows nvidia in use for the card, but lsmod does NOT show anything relevant.

In case it helps, this shows two attempts to load the module

Kresp · Tux's lil' helper Joined: 17 Oct 2016 Posts: 77

Roman_Gruber · Posted: Wed Apr 05, 2017 9:02 am Post subject:

Did you rebuild the kernel, boot it, with CONFIG_LOCALVERSION="your stuff of choice" and CONFIG_LOCALVERSION_AUTO=y ?

genterminl · Posted: Wed Apr 05, 2017 3:31 pm Post subject:

Why are those relevant? However, yes, I have both of those set. Note that when I upgraded nvidia-drivers, I did not change kernel at that time. Now, I have compiled a new kernel, the older nvidia-driver works fine with it, but I will have to wait until I have enough time to test the newer nvidia-driver with the new kernel - hopefully in a day or two.

genterminl · Posted: Wed Apr 05, 2017 9:38 pm Post subject:

Still no luck. gentoo-sources-4.9.16 selected with eselect kernel. nvidia-drivers-340-102 emerged, no apparent errors. recompiled kernel and modules and reinstalled. rebooted. Still get the same errors. At one point (but not sure exactly what triggered it) I got API mismatch: the client has the version 340.102 but this kernel module has the version 340.101. At the moment, 340.101 is only installed for the two previous kernels, but not this one, and I see no evidence of any 101 under /lib. rmmod nvidia says it is not loaded. lspci -k says nvidia is the module being used for the card.
Any suggestions what else I might try?

Roman_Gruber · Posted: Wed Apr 05, 2017 9:49 pm Post subject:

every rebuild kernel should have a different name. e.g. I use date code
file should be named accordingly

uname -a

grub should be edited by hand, and should use human readable names there.

genterminl · Posted: Thu Apr 06, 2017 2:41 am Post subject:

Well, I'm not sure how embarrassed to feel here. I simply forgot, and didn't notice, that I had previously applied a user user patch to nvidia-drivers-340-101 (with or without -r1) and once I applied that same patch to 102, it worked just fine. At this point, I don't remember where I got the patch, but I've now seen it in more than one place out on the web. The patch basically adds DRIVER_LEGACY to .driver_features in kernel/nv-drm.c, wrapped in an appropriate #if on the kernel version. Once I confirm this seems stable, I'll probably file a bug against nvidia-drivers-340.102 when compiled with kernel 3.9.x.

Edit: corrected typo in nvidia-drivers version.

genterminl · Posted: Sun Apr 09, 2017 10:49 pm Post subject:

It's never as simple as it sometimes seems. I shut down the PC while I was away for a few days, and when I just started it up, I got those same errors trying to start X. Fortunately, I figured this one out fairly quickly. I have a grub entry for the most recently compiled kernel - pointing to the root drive as the same as / and pointing to the compiled kernel where it is left by "make all" before doing a "make install." Once I am happy, I do the "make install" and put a specific entry in grub.conf with root pointing to the ./boot partition. However, there turns out to be a difference, although the reasons are buried in history I can't remember. The command line for the most recently compiled kernel includes "iommu=memaper=3" and the custom line does not. That is the only difference I can find. My motherboard/CPU (Asus M2N4-SLI, AMD Athlon(tm) 64 X2 Dual Core Processor 4000+) does not have iommu, but I really can't remember why I put this line in. In any case, without it, I get the errors, but not with it. This is for nvidia-drivers 340.102 and a 4.9.x kernel. As far as I can tell, though, the patch I mentioned above IS also needed.

skazi · Posted: Sun Apr 16, 2017 8:14 pm Post subject:

@Kresp
Try this two patches:

orionbelt · Apprentice Joined: 05 Apr 2006 Posts: 178

skazi, i also have the GeForce 8600 GT video card, and came across this problem. I don't know if any Gentoo devs follow this thread, but i am wondering: What is the wisdom of having a thousand users apply this patch individually rather than applying it once and for all centrally at the repository level? The reason seems to be that "it's the maintainer's policy not to apply patches to address kernel compatibility issues as this is often a moving target". Why is it reasonable to expect the Gentoo user to apply the patches (i don't see any other reasonable option) but it is unreasonable to have them applied by Gentoo maintainers?

tld · Veteran Joined: 09 Dec 2003 Posts: 1845

I have a GeForce 6200 card on my old x86 system that's also limited to the 304 version drivers. I'm currently using x11-drivers/nvidia-drivers-304.134 with kernel sys-kernel/gentoo-sources-4.9.6-r1 with no problem using this patch:

Clad in Sky · l33t Joined: 04 May 2007 Posts: 894 Location: Germany

Does this problem only affect older NVidia gpus/ the 340... driver? Or would I run into the same problem with a GTX 1060 using the latest nvidia-drivers?
_________________
Kali Ma
Now it's autumn of the aeons
Dance with your sword
Now it's time for the harvest

Maxxx · Guru Joined: 12 Jan 2016 Posts: 595 Location: Italia

I have GTX 1070 with 378.13 driver version, in a 4.9.16 kernel, and i haven't any problems.

tld · Veteran Joined: 09 Dec 2003 Posts: 1845

Yea, this is specific to anything that can only use "legacy" drivers. nVidia is pretty good as far as getting new kernel support working for the current drivers, but for the legacy ones like 304, not so much.

Tom

ChrisJumper · Advocate Joined: 12 Mar 2005 Posts: 2400 Location: Germany

I have trouble with the Kernel 4.9.36 and the nvidia-drivers-340.102-r1. There are some Patches for 4.9 and 4.11. Is there a patch available that work for modern Kernel-Sources?

Got there and try the Patch: pastebin.com/raw/stBSENAk
This is the Post for 340.102, but it was the same as for 340.102-r1:

soloslinger · n00b Joined: 13 Oct 2006 Posts: 44

Skazi's post/patches solved my issue for the following card: