nvidia-drivers failed [SOLVED]

Message

Nebetsu · Post by **Nebetsu** » Thu Nov 08, 2007 12:51 am

/bin/sh: scripts/genksyms/genksyms: No such file or directory
make[4]: *** [/var/tmp/portage/x11-drivers/nvidia-drivers-100.14.19/work/NVIDIA-Linux-x86-100.14.19-pkg0/usr/src/nv/nv.o] Error 1
make[3]: *** [_module_/var/tmp/portage/x11-drivers/nvidia-drivers-100.14.19/work/NVIDIA-Linux-x86-100.14.19-pkg0/usr/src/nv] Error 2
make[2]: *** [modules] Error 2
NVIDIA: left KBUILD.
nvidia.ko failed to build!
make[1]: *** [module] Error 1
make: *** [module] Error 2
 * 
 * ERROR: x11-drivers/nvidia-drivers-100.14.19 failed.
 * Call stack:
 *                         ebuild.sh, line 1695:  Called dyn_compile
 *                         ebuild.sh, line 1033:  Called qa_call 'src_compile'
 *                         ebuild.sh, line   44:  Called src_compile
 *   nvidia-drivers-100.14.19.ebuild, line  212:  Called linux-mod_src_compile
 *                  linux-mod.eclass, line  518:  Called die
 * The specific snippet of code:
 *                      emake HOSTCC="$(tc-getBUILD_CC)" CC="$(get-KERNEL_CC)" LDFLAGS="$(get_abi_LDFLAGS)" \
 *                                ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} \
 *                              || die "Unable to make ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}."
 *  The die message:
 *   Unable to make  IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/2.6.21-gentoo-r2/build clean module.
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-100.14.19/temp/build.log'.

I've been having a lot of things fail recently... >> This is one thing I can't really live without.

OmSai · Post by **OmSai** » Thu Nov 08, 2007 1:52 am

Code: Select all

/bin/sh: scripts/genksyms/genksyms: No such file or directory

The verdict in this thread was to try a manual kernel compile:
[topic=584825]nvidia-drivers compilation fails due to missing genksyms[/topic]

dev_zero · Post by **dev_zero** » Thu Nov 08, 2007 4:27 am

The nvidia drivers in portage is a joke if you ask me don't bother, i've had lots of troubles with it. I say download the driver from the nvidia homepage and compile it yourself and mask the nvidia drivers in portage. I tried 3 different versions from portage without any luck. I didn't get any errors like you, but still I'm never going to use the portage drivers again.

Nebetsu · Post by **Nebetsu** » Thu Nov 08, 2007 5:31 am

Man this portage think is seeming more and more like communism. Looks good on paper, but when put in use, it collapses... >>

dev_zero · Post by **dev_zero** » Thu Nov 08, 2007 5:39 am

Haha xD

Nebetsu · Post by **Nebetsu** » Thu Nov 08, 2007 5:44 am

Is this one of those problems that if I come back in a couple weeks and do a sync, it will resolve itself?

dev_zero · Post by **dev_zero** » Thu Nov 08, 2007 5:56 am

Wouldn't count on it, if you want it to work, without portage interfering, download the .run file from nvidia.com and take it from there.

i92guboj · Post by **i92guboj** » Thu Nov 08, 2007 6:06 am

Compile your kernel by hand, make sure you "make && make install modules_install" after configuring it. Then emerge nvidia-drivers.

It works ok. By downloading it and running manually outside portage you risk having problems later, because you will have the worst kind of cruft lying around uncontrolled by portage.

dev_zero · Post by **dev_zero** » Thu Nov 08, 2007 6:15 am

Well the "problems" you are reffering to here is caused by portage, when it still tries to install nvidia drivers from portage over the "manual" install. This is easily conquered by masking and putting the package in package.provided. In my case when I tried using the nvidia-driver from portage it installed an old driver which didn't work because newer was masked, and when i forced it to install the never it couldn't (lol) because checksum on the .run file emerge downloaded didn't match the checksum in portage. After that bullshit emerge can put the nvidia-drivers a certain place, because it worked like a charm when doing it the "manual" way.

Keynone · Post by **Keynone** » Thu Nov 08, 2007 5:26 pm

I am having a similar problem since upgrading the kernel, which I always do manually. I never use genkernel. I also have an AMD 64 BE-2350, with 2 gig RAM and 250 GB HD. I am using kernel 2.6.22-gentoo-r9. The last time it worked was with kernel 2.6.22-gentoo-r2.

Nebetsu · Post by **Nebetsu** » Thu Nov 08, 2007 8:11 pm

Ok. So I'm hearing a lot against using the nvidia drivers from the site. Are there any downsides to manually compiling the kernel? Does it have any negative effects on anything in portage?

i92guboj · Post by **i92guboj** » Thu Nov 08, 2007 10:10 pm

Nebetsu wrote:Ok. So I'm hearing a lot against using the nvidia drivers from the site. Are there any downsides to manually compiling the kernel? Does it have any negative effects on anything in portage?

There's no downside to manually compiling the kernel, you can just compile it in /usr/src where portage installs it. Just don't use genkernel. and make sure you fully make your kernel before attempting to emerge nvidia-drivers. That would be as simple as

Code: Select all

cd /usr/src/linux
make menuconfig
...
make
mount /boot
make install modules_install

Then emerge nvidia-drivers.

I have nvidia-drivers-100.14.19 working perfectly fine along with a 2.6.23.1 kernel. No problems at all.

If you install the drivers manually, then if X and opengl start acting funky, and you have problems getting dri to work, you will be alone. At a first try it will work, but it will probably break if you upgrade your kernel, and some libraries are forgotten on any place. If you install by hand, be sure you keep track of the files that a package adds into your system. Overall, if we are talking about shared libs or drivers.

EDIT, I don't know if the problem is genkernel or whatever. I just know that those work just fine. And I never ever used genkernel.

Keynone · Post by **Keynone** » Fri Nov 09, 2007 12:28 am

I found in this thread that in my situation where I was using nvidia-drivers 1.0.9639 because it is the last driver that supports the GeForce 4MX, that I needed to emerge nvidia-drivers-96.43.01, which worked successfully for me.

Nebetsu · Post by **Nebetsu** » Sun Nov 11, 2007 12:17 am

i92guboj wrote:
Nebetsu wrote:Ok. So I'm hearing a lot against using the nvidia drivers from the site. Are there any downsides to manually compiling the kernel? Does it have any negative effects on anything in portage?
There's no downside to manually compiling the kernel, you can just compile it in /usr/src where portage installs it. Just don't use genkernel. and make sure you fully make your kernel before attempting to emerge nvidia-drivers. That would be as simple as
Code: Select all
cd /usr/src/linux
make menuconfig
...
make
mount /boot
make install modules_install
Then emerge nvidia-drivers.

I have nvidia-drivers-100.14.19 working perfectly fine along with a 2.6.23.1 kernel. No problems at all.

If you install the drivers manually, then if X and opengl start acting funky, and you have problems getting dri to work, you will be alone. At a first try it will work, but it will probably break if you upgrade your kernel, and some libraries are forgotten on any place. If you install by hand, be sure you keep track of the files that a package adds into your system. Overall, if we are talking about shared libs or drivers.

EDIT, I don't know if the problem is genkernel or whatever. I just know that those work just fine. And I never ever used genkernel.

It's been a while since I've done it this way. I just compiled it and noticed there's no initramfs. How would I go about making one?

bunder · Post by **bunder** » Sun Nov 11, 2007 3:08 am

Nebetsu wrote:It's been a while since I've done it this way. I just compiled it and noticed there's no initramfs. How would I go about making one?

do you really need one? (ie: if you have modules you need at boot time... but that can be fixed by building them into the kernel itself)

cheers

Nebetsu · Post by **Nebetsu** » Sun Nov 11, 2007 5:46 am

Well that's how I've always done it... >> I don't really know how make it so you don't need one either.

jcat · Post by **jcat** » Sun Nov 11, 2007 5:56 am

This all sounds very strange. I use Genkernel and the latest nvidia drivers in portage nvidia-drivers-100.14.23 (available if you ad nvidia-drivers to /etc/portage/package.unmask).

I have no emerge issues, and I'm using mostly testing.

I'm sure there will be an underlying reason why you guys are having trouble. I don't believe the problem is related to portage in any way.

Cheers,
jcat

jcat · Post by **jcat** » Sun Nov 11, 2007 6:00 am

Nebetsu wrote:Well that's how I've always done it... >> I don't really know how make it so you don't need one either.

You would just need a differnet entry in grub.conf. Please see the docs:

http://www.gentoo.org/doc/en/handbook/h ... =1&chap=10

You have a much simpler "kernel" line like:

Code: Select all

kernel /path/to/kernel root=/dev/disk-device

...with appropriate substitutions.

Cheers,
jcat

Nebetsu · Post by **Nebetsu** » Sun Nov 11, 2007 6:11 pm

Cool. It worked. Problem is: Nvidia drivers still didn't.

There was an "access violation". Something to do with this:

open_wr: /usr/src/linux-2.6.23-gentoo-r1/null.gcda
open_wr: /usr/src/linux-2.6.23-gentoo-r1/null.gcda
open_wr: /usr/src/linux-2.6.23-gentoo-r1/null.gcda
open_wr: /usr/src/linux-2.6.23-gentoo-r1/null.gcda
open_wr: /usr/src/linux-2.6.23-gentoo-r1/null.gcda

i92guboj · Post by **i92guboj** » Sun Nov 11, 2007 6:16 pm

Nebetsu wrote:Cool. It worked. Problem is: Nvidia drivers still didn't.

There was an "access violation". Something to do with this:

open_wr: /usr/src/linux-2.6.23-gentoo-r1/null.gcda
open_wr: /usr/src/linux-2.6.23-gentoo-r1/null.gcda
open_wr: /usr/src/linux-2.6.23-gentoo-r1/null.gcda
open_wr: /usr/src/linux-2.6.23-gentoo-r1/null.gcda
open_wr: /usr/src/linux-2.6.23-gentoo-r1/null.gcda

FEATURES="-sandbox" emerge nvidia-drivers

Nebetsu · Post by **Nebetsu** » Sun Nov 11, 2007 6:23 pm

i92guboj wrote:
Nebetsu wrote:Cool. It worked. Problem is: Nvidia drivers still didn't.

There was an "access violation". Something to do with this:

open_wr: /usr/src/linux-2.6.23-gentoo-r1/null.gcda
open_wr: /usr/src/linux-2.6.23-gentoo-r1/null.gcda
open_wr: /usr/src/linux-2.6.23-gentoo-r1/null.gcda
open_wr: /usr/src/linux-2.6.23-gentoo-r1/null.gcda
open_wr: /usr/src/linux-2.6.23-gentoo-r1/null.gcda
FEATURES="-sandbox" emerge nvidia-drivers

Shouldn't I just put that in my USE or something so I don't have further problems in the future when I try to update or whatever?

i92guboj · Post by **i92guboj** » Sun Nov 11, 2007 6:27 pm

Nebetsu wrote:
i92guboj wrote:
Nebetsu wrote:Cool. It worked. Problem is: Nvidia drivers still didn't.

There was an "access violation". Something to do with this:

open_wr: /usr/src/linux-2.6.23-gentoo-r1/null.gcda
open_wr: /usr/src/linux-2.6.23-gentoo-r1/null.gcda
open_wr: /usr/src/linux-2.6.23-gentoo-r1/null.gcda
open_wr: /usr/src/linux-2.6.23-gentoo-r1/null.gcda
open_wr: /usr/src/linux-2.6.23-gentoo-r1/null.gcda
FEATURES="-sandbox" emerge nvidia-drivers
Shouldn't I just put that in my USE or something so I don't have further problems in the future when I try to update or whatever?

No, it is a really bad idea to globally disable the sandbox. For now, you will have to remember that in case that any future compilation of nvidia-drivers fail again with a sandbox violation. Indeed, this same workaround can be used to work around any sandbox violation, on any package, but this has some implications. In this concrete case, it is known that there will be no problem if you bypass the sandbox. But malicious and/or incorrect ebuilds can trash your whole system unless the sandbox is active.

It is a known bug that affects only some people. There are some threads about sandbox and nvidia-drivers on the forums.

Nebetsu · Post by **Nebetsu** » Sun Nov 11, 2007 8:47 pm

Ok. Nvidia's compiled and everything seems to be happy. Thanks! ^-^