| View previous topic :: View next topic |
| Author |
Message |
lyallp
Veteran
Joined: 15 Jul 2004
Posts: 1599
Location: Adelaide/Australia
|
 Posted: Wed Jan 19, 2011 12:00 am Post subject: [SOLVED!!!]Cant compile nvidia-drivers-260.19.36 |
 |
|
I have this problem every now and then.
I update my kernel, try install nvidia-drivers, and it decides it can't determine my kernel version.
I have 2 kernels on my system, 2.6.35-gentoo-r15, which is my current kernel whereby I have successfully managed to install nvidia-drivers in the past.
The second kernel is 2.6.36-r5, which I have built and install but have completely failed to have nvidia-drivers install against.
Now I have screwed myself over right and proper by attempting to uninstall nvidia-drivers and now I can't re-install.
I use eselect kernel to create the symlink.
The /usr/src/linux is being found, contains a completely built kernel.
I have linux-headers-2.6.30-r1 installed.
I have a similar problem building virtualbox-modules.
I have tried doing a | Code: | | rm -fr /lib64/modules/2.6.35-gentoo-15 && make clean && make && make modules_install && make install && emerge nvidia-drivers |
to no avail
In the past, I found that changing ownership of the entire source tree of the kernel to portage:portage seemed to help but not at this point.
I am completely unable to install nvidia-drivers and have no idea why.
| Code: | * Package: x11-drivers/nvidia-drivers-260.19.29
* Repository: gentoo
* Maintainer: cardoe@gentoo.org jer@gentoo.org,spock@gentoo.org
* USE: acpi amd64 elibc_glibc gtk kernel_linux multilib userland_GNU
* Determining the location of the kernel source code
* Found kernel source directory:
* /usr/src/linux
* Found kernel object directory:
* /lib/modules/2.6.35-gentoo-r15/build
* Found sources for kernel version:
* 2.6.35-gentoo-r15
* Checking for MTRR support ...
[ ok ]
>>> Unpacking source...
>>> Unpacking NVIDIA-Linux-x86_64-260.19.29.run to /tmp/portage/portage/x11-drivers/nvidia-drivers-260.19.29/work
>>> Source unpacked in /tmp/portage/portage/x11-drivers/nvidia-drivers-260.19.29/work
>>> Preparing source in /tmp/portage/portage/x11-drivers/nvidia-drivers-260.19.29/work ...
* Applying 256.35-unified-arch.patch ...
[ ok ]
* Converting /kernel/Makefile.kbuild to use M= instead of SUBDIRS= ...
[ ok ]
>>> Source prepared.
>>> Configuring source in /tmp/portage/portage/x11-drivers/nvidia-drivers-260.19.29/work ...
>>> Source configured.
>>> Compiling source in /tmp/portage/portage/x11-drivers/nvidia-drivers-260.19.29/work ...
* Preparing nvidia module
make -j8 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/2.6.35-gentoo-r15/build HOST_CC=x86_64-pc-linux-gnu-gcc clean module
If you are using a Linux 2.4 kernel, please make sure
you either have configured kernel sources matching your
kernel or the correct set of kernel headers installed
on your system.
If you are using a Linux 2.6 kernel, please make sure
you have configured kernel sources matching your kernel
installed on your system. If you specified a separate
output directory using either the "KBUILD_OUTPUT" or
the "O" KBUILD parameter, make sure to specify this
directory with the SYSOUT environment variable or with
the equivalent nvidia-installer command line option.
Depending on where and how the kernel sources (or the
kernel headers) were installed, you may need to specify
their location with the SYSSRC environment variable or
the equivalent nvidia-installer command line option.
*** Unable to determine the target kernel version. ***
make: *** [select_makefile] Error 1
emake failed
* ERROR: x11-drivers/nvidia-drivers-260.19.29 failed:
* Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/2.6.35-gentoo-r15/build HOST_CC=x86_64-pc-linux-gnu-gcc clean module
*
* Call stack:
* ebuild.sh, line 56: Called src_compile
* environment, line 4203: Called linux-mod_src_compile
* environment, line 3104: Called die
* The specific snippet of code:
* eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" CROSS_COMPILE=${CHOST}- LDFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}";
*
* If you need support, post the output of 'emerge --info =x11-drivers/nvidia-drivers-260.19.29',
* the complete build log and the output of 'emerge -pqv =x11-drivers/nvidia-drivers-260.19.29'.
* The complete build log is located at '/var/log/emerge/x11-drivers:nvidia-drivers-260.19.29:20110118-234200.log'.
* The ebuild environment file is located at '/tmp/portage/portage/x11-drivers/nvidia-drivers-260.19.29/temp/environment'.
* S: '/tmp/portage/portage/x11-drivers/nvidia-drivers-260.19.29/work/'
|
_________________
...Lyall
Last edited by lyallp on Mon Feb 28, 2011 11:30 pm; edited 4 times in total |
|
| Back to top |
|
 |
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Wed Jan 19, 2011 1:29 am Post subject: |
|
|
I would guess something got joggled during an update or depclean between compiling the 35-r15 and 36-r5. I would try:
| Code: | uname -a #make sense?
emerge --sync
emerge portage
emerge -uND world
perl-cleaner all
python-updater # 2.6x selected , 3.1x available
lafilefixer --justfixit
revdep-rebuild
emerge linux-headers
emerge =gentoo-sources-2.6.35-r15
eselect kernel set linux-2.6.35-gentoo-r15
cd /usr/src
ls -l linux # valid symlink?
cd linux
make menuconfig # scan for validity
emerge -av xorg-server $(qlist -IC x11-drivers) #get lucky?
|
If no luck: emerge -e world
_________________
Defund the FCC. |
|
| Back to top |
|
|
dmpogo
Advocate
Joined: 02 Sep 2004
Posts: 3468
Location: Canada
|
| Posted: Wed Jan 19, 2011 2:42 am Post subject: |
|
|
I wonder how nvidia-drivers determines target kernel version.
Could it be it uses /proc/version and you don't have /proc enabled or something like that ? |
|
| Back to top |
|
|
Jaglover
Watchman
Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana
|
| Posted: Wed Jan 19, 2011 2:50 am Post subject: |
|
|
| Quote: | | *** Unable to determine the target kernel version. *** |
I've been using latest nVidia driver for some time now and every now and then things break with very same error. There are a couple of bugs filed. Usually switching to a newer kernel version fixes it.
_________________
My Gentoo installation notes.
Please learn how to denote units correctly! |
|
| Back to top |
|
|
lyallp
Veteran
Joined: 15 Jul 2004
Posts: 1599
Location: Adelaide/Australia
|
| Posted: Wed Jan 19, 2011 3:01 am Post subject: |
|
|
I have tried reinstalling kernel headers, completely deleting the kernel sources and re-installing.
I regularly do the and when I am upgrading, I copy the .config file and do a
I use | Code: | | eselect kernel set n |
to create the linux symlink
Nothing to
/proc/version is fine.
It's a new install of Gentoo amd64 (about 2 weeks old).
nvidia-drivers determines the kernel version by compiling a little program.
My main issue is that I have successfully installed on previous occasions, on this machine.
Worse, virtualbox-modules, which also builds kernel modules, is having similar problems, it won't install, although, it reports a different error.
_________________
...Lyall |
|
| Back to top |
|
|
Jaglover
Watchman
Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana
|
| Posted: Wed Jan 19, 2011 3:21 am Post subject: |
|
|
IMO, kernel headers are used only for building glibc.
Doing make oldconfig is not the best thing to do, it is not recommended by Gentoo developers either. It is safe only when upgrading between patchlevels. See Gentoo docs for more.
Anyhow, it may be something else. Are you sure your symlink is pointing to correct sources? Are you sure your /boot was mounted before installing new kernel? In other words, are you sure you are running the kernel you think you are running?
Sorry if this sounds a little silly, but ...
What error you are getting with VirtualBox? Knowing this may help to diagnose the problem.
_________________
My Gentoo installation notes.
Please learn how to denote units correctly! |
|
| Back to top |
|
|
lyallp
Veteran
Joined: 15 Jul 2004
Posts: 1599
Location: Adelaide/Australia
|
| Posted: Wed Jan 19, 2011 4:02 am Post subject: |
|
|
I only use 'make oldconfig' when I am changing kernel versions.
/boot is mounted, it's where the sources are. I accidentally made /boot 2G instead of 200M so I figure I might as well keep the sources in the /boot system and update /usr/src to be a symlink to /boot/src. I generally keep my kernel sources on other gentoo systems in /usr/local/src as I dislike writing to /usr if it is not necessary.
I only have 2 versions of kernel in /boot and only one in /lib64/modules.
VirtualBox modules complained that KERN_DIR (/usr/src/linux) does not point to a directory, well, of course it's not, it's a symlink but it is pointing to the correct directory as I use to get to the linux build directory where I do | Code: | | make -j8 && make modules_install && make install |
_________________
...Lyall |
|
| Back to top |
|
|
dmpogo
Advocate
Joined: 02 Sep 2004
Posts: 3468
Location: Canada
|
| Posted: Wed Jan 19, 2011 4:19 am Post subject: |
|
|
Can you just show as 'ls -l' of relevant directories ?
/boot /usr/src ?
does eselect work correctly if /usr/src is a symlink ? |
|
| Back to top |
|
|
lyallp
Veteran
Joined: 15 Jul 2004
Posts: 1599
Location: Adelaide/Australia
|
| Posted: Wed Jan 19, 2011 4:37 am Post subject: |
|
|
Tried moving source tree back into /usr/local/src, rather than /boot/src, updated the /usr/src symlink
Rebuilt 2.6.36 and re-installed, re-booted to the New 2.6.36 version (which I don't want because it doesn't play well with my laptop, no brightness controls).
eselect kernel set 1 (2.6.35-r15)
Re-built 2.6.35-r15 and re-installed.
Attempted re-install of nvidia-drivers, success.
I will try later, with sources back in /boot/src, it's my preferred location, but this will do.
It appears I need to be in a different version of the kernel to get nvidia-drivers to build.
| Code: | root@pearcely2 src
# ls -la /usr
total 432
drwxr-xr-x 13 root root 4096 Jan 19 14:47 .
drwxr-xr-x 22 root root 4096 Jan 2 10:50 ..
drwxr-xr-x 2 root root 73728 Jan 19 09:47 bin
drwxr-xr-x 3 games root 16 Jan 3 23:30 games
drwxr-xr-x 338 root root 40960 Jan 17 15:19 include
-rw-r--r-- 1 root root 0 Nov 18 12:10 .keep
lrwxrwxrwx 1 root root 5 Dec 23 14:56 lib -> lib64
drwxr-xr-x 30 root root 28672 Jan 19 09:47 lib32
drwxr-xr-x 123 root root 118784 Jan 19 09:47 lib64
drwxr-xr-x 12 root root 8192 Jan 13 16:08 libexec
drwxr-xr-x 11 root root 141 Jan 19 08:59 local
drwxr-xr-x 9 root root 83 Dec 26 15:56 NX
drwxr-xr-x 2 root root 8192 Jan 19 09:01 sbin
drwxr-xr-x 190 root root 8192 Jan 13 15:43 share
lrwxrwxrwx 1 root root 14 Jan 19 14:47 src -> /usr/local/src
lrwxrwxrwx 1 root root 8 Dec 23 14:58 tmp -> /var/tmp
drwxr-xr-x 6 root root 59 Nov 18 14:48 x86_64-pc-linux-gnu
root@pearcely2 src
# |
| Code: | root@pearcely2 src
# ls -la
total 236
drwxr-xr-x 5 root root 4096 Jan 19 14:46 .
drwxr-xr-x 11 root root 141 Jan 19 08:59 ..
-rw-r--r-- 1 root root 0 Nov 18 12:10 .keep
lrwxrwxrwx 1 root root 22 Jan 19 14:29 linux -> linux-2.6.36-gentoo-r5
drwxr-xr-x 24 portage portage 4096 Jan 19 14:03 linux-2.6.35-gentoo-r15
drwxr-xr-x 24 portage portage 4096 Jan 19 14:50 linux-2.6.36-gentoo-r5
-rw-rw-r-- 1 root root 73800 Dec 27 17:19 LyallsConfig-nouveau.txt
-rw-r----- 1 root root 71479 Jan 19 13:27 LyallsConfig-nvidia-35.txt
-rw-r----- 1 root root 71254 Jan 19 13:28 LyallsConfig-nvidia-36.txt
drwxrwxrwx 4 pearcely 449 4096 Jan 18 12:58 pkcs11-dump-0.3.3
root@pearcely2 src
# |
| Code: | # ls -la /boot
total 26552
drwxr-xr-x 5 root root 4096 Jan 19 14:35 .
drwxr-xr-x 22 root root 4096 Jan 2 10:50 ..
lrwxrwxrwx 1 root root 1 Dec 23 14:56 boot -> .
-rw-rw-r-- 1 root root 71479 Jan 19 14:03 config-2.6.35-gentoo-r15
-rw-rw-r-- 1 root root 71479 Jan 19 10:38 config-2.6.35-gentoo-r15.old
-rw-rw-r-- 1 root root 71254 Jan 19 14:35 config-2.6.36-gentoo-r5
drwxr-xr-x 2 root root 4096 Jan 18 15:52 grub
drwxrwxr-x 8 root root 136 Jan 13 18:05 initramfs
-rw-r----- 1 root root 3643726 Dec 27 15:41 initramfs_gentoo_crypt_cpio.backup.gz
-rw-r----- 1 root root 3682444 Jan 13 18:05 initramfs_gentoo_crypt_cpio.gz
-rw-r--r-- 1 root root 0 Dec 24 14:48 .keep
drwxr-x--- 2 root root 6 Jan 19 14:46 src
-rw-rw-r-- 1 root root 2174276 Jan 19 14:03 System.map-2.6.35-gentoo-r15
-rw-rw-r-- 1 root root 2174276 Jan 19 10:38 System.map-2.6.35-gentoo-r15.old
-rw-rw-r-- 1 root root 2197331 Jan 19 14:35 System.map-2.6.36-gentoo-r5
lrwxrwxrwx 1 root root 24 Jan 19 14:35 vmlinuz -> vmlinuz-2.6.36-gentoo-r5
-rw-rw-r-- 1 root root 4419632 Jan 19 14:03 vmlinuz-2.6.35-gentoo-r15
-rw-rw-r-- 1 root root 4419632 Jan 19 10:38 vmlinuz-2.6.35-gentoo-r15.old
-rw-rw-r-- 1 root root 4223072 Jan 19 14:35 vmlinuz-2.6.36-gentoo-r5
lrwxrwxrwx 1 root root 25 Jan 19 14:03 vmlinuz.old -> vmlinuz-2.6.35-gentoo-r15
root@pearcely2 src
# |
_________________
...Lyall |
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Wed Jan 19, 2011 4:54 am Post subject: |
|
|
| Code: | umount /boot
ls -l /boot |
Anything returned other than total 0? If so you have occasionally written to /boot when the /boot partition was not mounted. If so, you should | Code: | mkdir /wrongboot
mv /boot/* /wrongboot/ |
with the /boot partition NOT MOUNTED to clean up. Then | Code: | ls -l /boot #to check it empty
mount /boot |
and move any useful files from /wrongboot to /boot. Remove /wrongboot when convenient.
Why not rm the symlinks and put your files where they belong?
Then use gparted to shrink the boot partition to 200M, apply the operation, move the next file on the right (swap?) to claim the empty space, apply the operation, move the next partition on the right (root?) to claim the empty space, apply the operation, expand that file to use the empty space, apply the operation.
_________________
Defund the FCC. |
|
| Back to top |
|
|
lyallp
Veteran
Joined: 15 Jul 2004
Posts: 1599
Location: Adelaide/Australia
|
| Posted: Wed Jan 19, 2011 5:33 am Post subject: |
|
|
I have method in my madness and mistakes.
I can resize the boot partition but I don't think I can add that size to the other partition on my disk.
You see, it's a single encrypted partition, on which LVM has been configured for all my other partitions, including swap.
Rather than risk losing the lot, I simply figured I would make use of the mistake and kernel sources seemed like a good choice.
Regarding boot, I have /boot automount.
/boot is fine.
I managed to install the virtualbox-modules and nvidia-drivers by completely removing all versions of the kernel, installing a different version to what I want to run in, booting it, reverting my /usr/src/linux link back to the version I want to use, build and install then emerge nvidia-drivers.
_________________
...Lyall |
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Wed Jan 19, 2011 5:39 am Post subject: |
|
|
from https://bugs.gentoo.org/show_bug.cgi?id=27636
| Quote: | I don't exactly see the problem here. The kernel headers in your /usr/src/...
directory should match the kernel you are building, and the headers in
/usr/include should ideally match those you built glibc with. There is no link
between the two. |
| Quote: | Anyways, from my understanding, part of what allows this odd mix of kernel
versions and header versions is the fact that /usr/include/linux and /usr/include/asm
are not symlinks to their respective directories in /usr/src/linux/include*,
but that /usr/include/{linux,asm} are real directories with copies of the
headers in them. I believe we are one of the few distributions to implement
this specific setup (correct me if wrong), so it's safe to have any random
version of a kernel in /usr/src/linux, or not even have a /usr/src/linux
symlink, as glibc will readily find it's desired header files already in
/usr/include. |
The moral being: if you do something unusual and something weird happens there is sometimes a connection from one to the other.
_________________
Defund the FCC. |
|
| Back to top |
|
|
lyallp
Veteran
Joined: 15 Jul 2004
Posts: 1599
Location: Adelaide/Australia
|
| Posted: Mon Feb 07, 2011 11:57 pm Post subject: |
|
|
The problem has resurfaced.
Every time there is an update to the nvidia-drivers, I end up with the | Code: | | *** Unable to determine the target kernel version. *** |
error.
Having to boot different versions of kernel just to build the new nvidia-drivers is insane.
I can re-build my nvidia-drivers of the version I currently have installed, no problems.
Stupid... mumble... mumble...
_________________
...Lyall |
|
| Back to top |
|
|
Jaglover
Watchman
Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana
|
| Posted: Tue Feb 08, 2011 12:06 am Post subject: |
|
|
| Quote: | | Having to boot different versions of kernel just to build the new nvidia-drivers is insane. |
AFAIK drivers are built against sources that linux symlink points to. Only when /usr/src/linux is not present it will attempt to build against running kernel.
_________________
My Gentoo installation notes.
Please learn how to denote units correctly! |
|
| Back to top |
|
|
Anon-E-moose
Watchman
Joined: 23 May 2008
Posts: 6215
Location: Dallas area
|
| Posted: Tue Feb 08, 2011 12:30 am Post subject: |
|
|
what does "uname -r" return
what does "ls -l /lib/modules/`uname -r`/build" return
what does "ls -l /usr/src/linux" return
_________________
UM780, 6.12 zen kernel, gcc 13, openrc, wayland |
|
| Back to top |
|
|
lyallp
Veteran
Joined: 15 Jul 2004
Posts: 1599
Location: Adelaide/Australia
|
| Posted: Tue Feb 08, 2011 12:34 am Post subject: |
|
|
| Code: | # uname -a
Linux pearcely2 2.6.35-gentoo-r15 #4 SMP Mon Feb 7 15:51:09 CST 2011 x86_64 Intel(R) Core(TM) i7 CPU M 620 @ 2.67GHz GenuineIntel GNU/Linux
|
| Code: | # ls -l /lib/modules/`uname -r`/build
lrwxrwxrwx 1 root root 33 Jan 21 10:01 /lib/modules/2.6.35-gentoo-r15/build -> /boot/src/linux-2.6.35-gentoo-r15
|
| Code: | # ls -la /usr/src
lrwxrwxrwx 1 root root 9 Jan 21 09:55 /usr/src -> /boot/src
|
| Code: | # eselect kernel list
Available kernel symlink targets:
[1] linux-2.6.35-gentoo-r15 *
[2] linux-2.6.36-gentoo-r5 |
| Code: | # ls -la /usr/src/linux
lrwxrwxrwx 1 root root 23 Jan 19 14:57 /usr/src/linux -> linux-2.6.35-gentoo-r15
|
_________________
...Lyall |
|
| Back to top |
|
|
Anon-E-moose
Watchman
Joined: 23 May 2008
Posts: 6215
Location: Dallas area
|
| Posted: Tue Feb 08, 2011 1:02 am Post subject: |
|
|
If you point /usr/src/linux to 36-r5 and reboot in the 36-r5 kernel
what do the commands above return?
_________________
UM780, 6.12 zen kernel, gcc 13, openrc, wayland |
|
| Back to top |
|
|
Section_8
l33t
Joined: 22 May 2004
Posts: 627
|
| Posted: Tue Feb 08, 2011 1:13 am Post subject: |
|
|
| Just grasping at straws here - maybe having /usr/src a symlink screws something up. Have you tried a bind mount instead? |
|
| Back to top |
|
|
Anon-E-moose
Watchman
Joined: 23 May 2008
Posts: 6215
Location: Dallas area
|
| Posted: Tue Feb 08, 2011 1:22 am Post subject: |
|
|
| Section_8 wrote: | | Just grasping at straws here - maybe having /usr/src a symlink screws something up. Have you tried a bind mount instead? |
I thought about that, but the nvidia config finds things by looking at the running kernel (I think) to get the name
then the /lib/modules directory to find what the build symlink points at.
_________________
UM780, 6.12 zen kernel, gcc 13, openrc, wayland |
|
| Back to top |
|
|
Jaglover
Watchman
Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana
|
| Posted: Tue Feb 08, 2011 1:28 am Post subject: |
|
|
I just pointed the symlink to old sources and it definitely follows the link, not the running kernel which is 2.6.37-gentoo.
| Code: | >>> Emerging (1 of 1) x11-drivers/nvidia-drivers-260.19.36
* NVIDIA-Linux-x86_64-260.19.36.run RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* Package: x11-drivers/nvidia-drivers-260.19.36
* Repository: gentoo
* Maintainer:
* USE: acpi amd64 elibc_glibc gtk kernel_linux multilib userland_GNU
* FEATURES: ccache preserve-libs sandbox
* Determining the location of the kernel source code
* Found kernel source directory:
* /usr/src/linux
* Found kernel object directory:
* /lib/modules/2.6.36-gentoo-r6/build
* Found sources for kernel version:
* 2.6.36-gentoo-r6
* Checking for MTRR support ... [ ok ]
>>> Unpacking source...
|
_________________
My Gentoo installation notes.
Please learn how to denote units correctly!
Last edited by Jaglover on Tue Feb 08, 2011 1:30 am; edited 1 time in total |
|
| Back to top |
|
|
lyallp
Veteran
Joined: 15 Jul 2004
Posts: 1599
Location: Adelaide/Australia
|
| Posted: Tue Feb 08, 2011 1:29 am Post subject: |
|
|
nvidia-drivers would not compile when booted under the new kernel, whichever one was eselected.
I have not tried a bind mount, I will have to research how to do that.
What get's me is I can compile my existing nvidia-drivers version just fine, it's on upgrade that I have the issue.
Last time I ended up deleting all modules and the entire kernel source tree, and re-installing the kernel and nvidia-drivers from scratch - I even needed to be booted into a different version of the kernel.
I will try the mount option.
| Code: | 2.6.36-gentoo-r5
lrwxrwxrwx 1 root root 32 Feb 8 11:47 /lib/modules/2.6.36-gentoo-r5/build -> /boot/src/linux-2.6.36-gentoo-r5
drwxr-x--- 4 root root 4096 Feb 8 11:51 .
drwxr-xr-x 5 root root 4096 Feb 8 11:47 ..
lrwxrwxrwx 1 root root 22 Feb 8 11:51 linux -> linux-2.6.36-gentoo-r5
drwxr-xr-x 23 portage portage 4096 Feb 8 11:43 linux-2.6.35-gentoo-r15
drwxr-xr-x 24 portage portage 4096 Feb 8 11:47 linux-2.6.36-gentoo-r5
-rw-rw-r-- 1 root root 73800 Dec 27 17:19 LyallsConfig-nouveau.txt
-rw-r----- 1 root root 71479 Jan 19 13:27 LyallsConfig-nvidia-35.txt
-rw-r----- 1 root root 71254 Jan 19 13:28 LyallsConfig-nvidia-36.txt
|
_________________
...Lyall |
|
| Back to top |
|
|
Anon-E-moose
Watchman
Joined: 23 May 2008
Posts: 6215
Location: Dallas area
|
| Posted: Tue Feb 08, 2011 1:33 am Post subject: |
|
|
what does "emerge -pv nvidia-drivers" return and are you using custom flags for it.
You shouldn't have to completely delete everything, something is misconfigured, just not sure what.
edit to add: it may be some interaction between
SYSSRC=/usr/src/linux SYSOUT=/lib/modules/2.6.35-gentoo-r15/build
though they should ultimately point to the same place
_________________
UM780, 6.12 zen kernel, gcc 13, openrc, wayland |
|
| Back to top |
|
|
lyallp
Veteran
Joined: 15 Jul 2004
Posts: 1599
Location: Adelaide/Australia
|
| Posted: Tue Feb 08, 2011 1:45 am Post subject: |
|
|
| Code: | | mount --bind /boot/src /usr/src |
did not make any difference.
I did a full eselect/clean/compile/install/modules_install of my current 2.6.35 kernel prior to attempting an install of nvidia-drivers.
nvidia-drivers still fails to compile.
When I could be bothered, I will do what I did last time, which is boot to another version of the kernel, completely delete everything of the target version (2.6.35), re-install it all and rebuild it all with the new nvidia-drivers.
_________________
...Lyall |
|
| Back to top |
|
|
Anon-E-moose
Watchman
Joined: 23 May 2008
Posts: 6215
Location: Dallas area
|
| Posted: Tue Feb 08, 2011 1:48 am Post subject: |
|
|
Doing a little googling finds others with problems similar to you and many were using non-standard places for the kernel sources.
So I'm guessing some interaction with symlinks is your problem.
But I don't know what the solution is.
Edit to add: From the gentoo nvidia guide
Kernel module packages use the /usr/src/linux symlink to determine which kernel they should build against. If this link is already correct, move on to Required Kernel Settings.
Usually kernel modules should be built against the currently running kernel, so find out what that is by running:
I'm guessing that even though eselect sets /usr/src/linux properly, the ebuild is getting confused when it comes to resolving against /boot/src/*
_________________
UM780, 6.12 zen kernel, gcc 13, openrc, wayland |
|
| Back to top |
|
|
dwbowyer
Apprentice
Joined: 18 Apr 2008
Posts: 155
|
| Posted: Tue Feb 08, 2011 2:32 am Post subject: |
|
|
For 6 months now, I've been getting this same problem with linux sources in /usr/src.
I can rebuild the existing nvidia-drivers, but not upgrade without first rebooting to another kernel.
My feeling has been that more recent nvidia-drivers are not respecting the /usr/src/linux symlink.
I also suspect there may be some relation to "emerge --depclean" having removed sources to the
running (and symlinked) kernel sources which forced me to then reinstall that version before building
new nvidia-drivers. I've not been happy that upgrading nvidia-drivers had been forcing me to reboot.
So orginal poster is not the only one being hit by this. and his /boot/src, may likely have NOTHING
to do with the issue. |
|
| Back to top |
|
|
|
Kernel & Hardware
