nvidia-drivers vs linux-2.6.33 [SOLVED]

[Muso]

A new gentoo-sources appeared during today's emerge --sync (2.6.33). The kernel built fine, but trying to emerge nvidia-drivers against that kernel failed. I then emerged a vanilla-2.6.33 and nvidia-drivers failed to build against it as well.

*** Unable to determine the target kernel version. ***

Linux headers need updating?
_________________
"You can lead a horticulture but you can't make her think" ~ Dorothy Parker
2021 is the year of the Linux Desktop!

[geki]

for such things about nvidia-drivers check

http://nvnews.net/vbulletin/forumdisplay.php?f=14

you can find this thread for example

http://nvnews.net/vbulletin/showthread.php?t=142794&page=2
http://nvnews.net/vbulletin/showpost.php?p=2164440&postcount=20
_________________
hear hear

[duryodhana]

you have to unmask nvidia-drivers-195.36.03 for successful compiling with 2.6.33 kernel

[DrAgOnTuX]

or try this: https://bugs.gentoo.org/show_bug.cgi?id=301318

[Muso]

[NathanZachary]

Marked as [SOLVED] per user request. Just so you know, you can edit your initial post in the thread to say [SOLVED].
_________________
“Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio---

[Muso]

[Aarin]

I have exactly the same problem described in the first post, but the merging the nvidia-drivers.195.36.03 doesn't work either...

The same *** Unable to determine the target kernel version. *** appears.

[yoosty69]

[Shining Arcanine]

Aarin, is /usr/src/linux pointing to the correct directory for your kernel sources? Also, how are you building the kernel?

[depontius]

Is there a legacy driver for 2.6.33, also? (nvidia-drivers-173.xx.xx)
_________________
.sigs waste space and bandwidth

[Shining Arcanine]

[qfly]

[seenxu]

unmask nvidia-drivers-195.36.03 solves the problem, thx.

[Shining Arcanine]

I dread the answer to this question, but how are you guys unmasking nvidia-drivers-195.36.03 when it is a hardmasked package?

[depontius]

/etc/portage/package.unmask to remove the hard mask
/etc/portage/package.keywords to accept the ~arch mask
_________________
.sigs waste space and bandwidth

[Shining Arcanine]

Ah, cool. I thought people were removing it from /usr/portage/profiles/package.mask, which was a frightening thought.

[Shining Arcanine]

[Muso]

[billmil]

Hi,

As a follow up I have an older graphics card (Quadro NVS 400, fwiw ).

Over the last year or so, I've set package.mask as follows to get the drivers to work:
>=x11-drivers/nvidia-drivers-97.00

I understood that later nvidia drivers would not/do not work with this older card.

What's the best way to solve this problem? (2.6.33 requires a newer driver version; newer driver versions don't work with the older card)

thanks,

bill

[NeddySeagoon]

billmil,

There is a patch for the new nvidia-driver on bugs.gentoo.org
It will need to be back ported to the older drivers.
_________________
Regards,

NeddySeagoon

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

[geki]

billmil
this thread states that version 96.43.16 should do with recent kernels.
http://www.nvnews.net/vbulletin/showthread.php?p=2175900
_________________
hear hear

[DevOne]

[NeddySeagoon]

DevOne,

Make a directory called /usr/local/portage
Add PORTDIR_OVERLAY="/usr/local/portage" to the bottom of your /etc/make.conf

Now you have an empty overlay and portage knows where to find it.

Fetch the file x11-drivers.bz2 from http://dev.gentoo.org/~neddyseagoon/ and put it in your overlay.
Unpack it with tar -jpf x11-drivers.bz2.

It contains, among other things, an ebuild called nvidia-drivers-190.53-r101.ebuild, which applies the required patch to nvidia-drivers-190.53-r1.ebuild, so it builds with 2.6.33.

That ebuild has KEYWORDS="-* ~amd64 ~x86 ~x86-fbsd" so you will need to add it to package.keywords if you normally run stable.

[DevOne]