A more elegant solution would probably be using the per-package module from portage-bashrc-ng.

The following is redundant!

The version of the driver is 8756, I also tried the stable version and the 8178. I also tried installed 8174 from nvidia.com manually with a patch I got from nvnews forums issuing exactly this situation.

I tried it back with 2.6.16-r4, but suddenly, that didn't work out either, and also 2.6.15-r8.

The kernel sources symlink was always correct and the driver compiled cleanly, except for some warnings concerning that problem:

where the latter is analog to the warning, and both refer to the missing symbols. What bothers me most it that neither the kernel nor this Makefile has changed since it worked last (at least when switching back to 2.6.16-r4).

Every thread I found here and on other boards was solved by using a 15-kernel or a newer driver version, which didn't work for me.

Last edited by tek0 on Mon Aug 28, 2006 2:01 pm; edited 3 times in total

Kernel 2.6.15-r1 + nvidia-kernel-1.0.8756 working fine!
new kernel comes out so I try that out and emerging the nvidia-kernel causes those missing symbols error
I carry on using working combo

New nvidia-kernel comes out (nvidia-kernel-1.0.8762) trying that against kernel-2.6.15-r1 results in the missinh symbols
so I try to go back to nvidia-kernel-1.0.8756 but that produces the same missing symbols
WTF!!! that was a previously working combination tha tis now broken!!!!

I re-compile my kernel and try to re-emerge nvidia-kernel and it still produces that error!!!

ONLY way I am able to get a working desktop is to issue this
sh /usr/portage/distfiles/NVIDIA-Linux-x86-1.0-8762-pkg1.run
ie run the NVIDIA-script directly! now since portage uses the nvidia-script and using portage does not work, portage MUST be doing something to break the compiling of the nvidia-module

THIS has been like this now for a good couple of months, the alias was the closest thing to a working solution BUT it doesnt work
I have opened a bug

https://bugs.gentoo.org/show_bug.cgi?id=137000
[b]_________________the table is made from wood. forget what you learnt, the table is made from carbon. forget what you learnt, the table is made from protons. forget what you learnt, the table is made from quarks. forget what you learnt, the table is good for shagging on

Kernel 2.6.15-r1 + nvidia-kernel-1.0.8756 working fine!
new kernel comes out so I try that out and emerging the nvidia-kernel causes those missing symbols error
I carry on using working combo

New nvidia-kernel comes out (nvidia-kernel-1.0.8762) trying that against kernel-2.6.15-r1 results in the missinh symbols
so I try to go back to nvidia-kernel-1.0.8756 but that produces the same missing symbols
WTF!!! that was a previously working combination tha tis now broken!!!!

I re-compile my kernel and try to re-emerge nvidia-kernel and it still produces that error!!!

Yep, something's terribly wrong with the whole thing. I also didn't wanna accept that reverting the changes didn't make things work again. Strange though, that the alias thing did the trick for me, but I could imagine that portage b0rked these aliases *somehow*...what's even more odd is that hell lot of people are having exactly this issue, but they always fixed it by using a ~nvidia-kernel.

Naib wrote:

ONLY way I am able to get a working desktop is to issue this
sh /usr/portage/distfiles/NVIDIA-Linux-x86-1.0-8762-pkg1.run
ie run the NVIDIA-script directly! now since portage uses the nvidia-script and using portage does not work, portage MUST be doing something to break the compiling of the nvidia-module

This is, again, curious, because I also manually installed several versions of the package. I also noticed that the second symbol problem, remap_page_range, appeared only sporadically...even on subsequent merges!
maybe the best thing to do is like `while emerge nvidia-kernel|grep 'unknown symbol'; do true; done;'

Same problem here almost exactly. Same kernels and going back doesn't help.
Haven't had them run the NVIDIA-Linux script instead of using portage, didn't find this
until too late to do that today. Hopefully maybe tomorrow.

I'm using 2.6.15-gentoo-r1 & nvidia-kernel-1.0.8174-r1 right now and after seeing their
problem and you guys, glad I haven't upgraded those two in awhile._________________Missouri Legislators trying to kill the Middle Class one bill at a time.
Eric Burlison, Tim Jones, Bill Lant, Holly Render, Nick Marshal, Peter Kinder

It may seem unrelated, but that alias thing worked for me again...When installing the 2.6.17 kernel, I remerged nvidia-kernel and, how could it be different, he complained about that page_range thing. As I didn't have that problem the last time I merged, I added that alias to modules.d/nvidia, and again, the module registered correctly. It may be some sort of placebo, but otherwise that problem would be totally random...

That may be teh case now, but the problem still exists whether you use the nvidia-* or nvidia-drivers ebuild
ccache borks it_________________the table is made from wood. forget what you learnt, the table is made from carbon. forget what you learnt, the table is made from protons. forget what you learnt, the table is made from quarks. forget what you learnt, the table is good for shagging on

I upgraded to ~x86 nvidia driver and works for me..
I vote for nvidia to free or work behind xorg instaed of xorg behind nvidia, is a pain what propietary software is doing, having all this people always waiting for them...
and still somepeople belives that propietary is ethical... they really dont care a crap about FOSS if they did they will had release a fix to the font issue and xorg 7.1 long time a go... rather they have all using xorg 7.1 downgrade to 7.0 sometimes I really think that some people is right that WE SHOULD not
relay so much on propietary software... we always loose.
_________________http://www.dailyradical.orghttp://www.binaryfreedom.info
use jabber!!! sing on now, register an account:
http://jabber.binaryfreedom.info