[semi-solved] nvidia-drivers can't determine kernel version

ticho · Last edited by ticho on Sun May 09, 2010 10:57 am; edited 1 time in total

I know there have already been several threads with similar issue, but I haven't found solution that would work for me in any of them.

Basically, I can't get to emerge any recent nvidia-drivers ebuild. I suspect toolchain/environment misconfiguration, as nvidia-drivers-190.42-r3 used to emerge correctly against the kernel I'm using (2.6.31-gentoo-r6), until one day it stopped. Now I can't get any 190.x or newer version to emerge on 2.6.31-gentoo-r6, or 2.6.33-gentoo.

By looking at list of emerged packages between last succesful install of 190.42-r3 and first failed one, I haven't found any obvious, or less obvious culprits. I have a crosscompile gcc profile installed (but not active), mipsel-unknown-linux-uclibc-4.3.4, in case that's relevant.

Can anyone please spare some time and try to point me the right way in order to solve this? TIA.

d2_racing · Posted: Sun Apr 25, 2010 1:10 pm Post subject:

There is something wrong :

ticho · Posted: Sun Apr 25, 2010 1:26 pm Post subject:

I don't think that's the issue here, I've been using this setting for over two years now.
_________________
The more you depend on forces outside yourself, the more you are dominated by them.

d2_racing · Posted: Sun Apr 25, 2010 1:33 pm Post subject:

Can you run this on your box :

ticho · Posted: Sun Apr 25, 2010 1:37 pm Post subject:

Seems fine:

d2_racing · Posted: Sun Apr 25, 2010 1:43 pm Post subject:

Ok, didn't know that core2 was compatible with 32 bits, I tought that prescott was 32 bits and nocona/core2 was 64 bits.

My bad.

d2_racing · Posted: Sun Apr 25, 2010 1:44 pm Post subject:

With kernel 2.6.33, is this working and do you update your sym link when you try kernel 2.6.33 ?

Can you retry with kernel 2.6.33 plz and post this just before you run emerge -av nvidia :

NeddySeagoon · Posted: Sun Apr 25, 2010 1:55 pm Post subject:

ticho,

At kernel 2.6.33 the files used by the nvidia driver to identify the kernel were moved/renamed, so the nvidia driver became broken against 2.6.33 and later. nVidia fixed that in the 195. series drivers.

There is a patch for some earlier drivers.

All external kernel modules follow the /usr/src/linux symlink to determine the kernel you want them to build against. This must point to a properly configured kernel tree.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

MarcusXP · Posted: Sun Apr 25, 2010 5:00 pm Post subject:

You need to unmask nvidia-drivers to use 195 version.
190 has a problem with newer kernel versions.
I had same issue as you.. and this fixed it.

ticho · Posted: Sun Apr 25, 2010 8:12 pm Post subject:

ticho · Posted: Sun Apr 25, 2010 8:13 pm Post subject:

ticho · Posted: Sun Apr 25, 2010 8:16 pm Post subject:

One thing I forgot to mention in my original post (sorry about that) was that manually running the same command in the correct directory within PORTAGE_TMPDIR works fine:

ticho · Posted: Sun May 09, 2010 10:56 am Post subject:

OK, after some tinkering and unclean hackery of nvidia's conftest.sh, I found out that the emerge was failing because it was running as user portage:portage, while my /lib/modules/<kernelversion> is of course root:root and not readable by world. After removing "userpriv" from FEATURES in make.conf, the package emerges just fine.

Is this something that should be reported? I tried deleting /lib/modules/<kernelversion> and reinstalling the kernel modules (make modules_install) to check that permissions are as they should be, but they're still 0750.
I also tried adding "usersandbox" to FEATURES, with no visible change.

For now, I guess I will be updating nvidia-drivers package with `FEATURES="-userpriv" emerge nvidia-drivers`.
_________________
The more you depend on forces outside yourself, the more you are dominated by them.