Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
emerge nvidia-drivers fails to determine the kernel version
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
jagdpanther
Apprentice
Apprentice


Joined: 22 Nov 2003
Posts: 219

PostPosted: Tue Feb 05, 2013 9:37 pm    Post subject: emerge nvidia-drivers fails to determine the kernel version Reply with quote

This works:
vanilla-sources-3.7.5 and nvidia-drivers-313.18

I tried to upgrade to vanilla-sources-3.7.6 which compiles and boots without issue. Then I try to emerge the nvidia-drivers:

ACCEPT_KEYWORDS='~amd64' emerge nvidia-drivers
Code:
*** Unable to determine the target kernel version. ***

make: *** [select_makefile] Error 1
 * ERROR: x11-drivers/nvidia-drivers-313.18 failed (compile phase):
 *   emake failed


Any ideas on what could cause this?


Code:
>>> Verifying ebuild manifests
>>> Running pre-merge checks for x11-drivers/nvidia-drivers-313.18
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found kernel object directory:
 *     /lib/modules/3.7.6-rr01/build
 * Found sources for kernel version:
 *     3.7.6-rr01
 * Checking for suitable kernel configuration options...
 [ ok ]

>>> Emerging (1 of 1) x11-drivers/nvidia-drivers-313.18
 * NVIDIA-Linux-x86_64-313.18.run SHA256 SHA512 WHIRLPOOL size ;-) ...   [ ok ]
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found kernel object directory:
 *     /lib/modules/3.7.6-rr01/build
 * Found sources for kernel version:
 *     3.7.6-rr01
>>> Unpacking source...
>>> Unpacking NVIDIA-Linux-x86_64-313.18.run to /dev/shm/portage/x11-drivers/nvidia-drivers-313.18/work
>>> Source unpacked in /dev/shm/portage/x11-drivers/nvidia-drivers-313.18/work
>>> Preparing source in /dev/shm/portage/x11-drivers/nvidia-drivers-313.18/work ...
 * Converting /kernel/Makefile.kbuild to use M= instead of SUBDIRS= ...
 [ ok ]
>>> Source prepared.
>>> Configuring source in /dev/shm/portage/x11-drivers/nvidia-drivers-313.18/work ...
>>> Source configured.
>>> Compiling source in /dev/shm/portage/x11-drivers/nvidia-drivers-313.18/work ...
 * Preparing nvidia module
make -j12 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' ARCH=x86_64 IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/3.7.6-rr01/build 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
 * ERROR: x11-drivers/nvidia-drivers-313.18 failed (compile phase):
 *   emake failed


Code:
                        System Settings
=================================================================
System uname: Linux-3.7.6-rr01-x86_64-Intel-R-_Core-TM-_i7_CPU_X_980_@_3.33GHz-with-gentoo-2.1
Timestamp of tree: Tue, 05 Feb 2013 20:15:01 +0000
ld GNU ld (GNU Binutils) 2.22
app-shells/bash:          4.2_p37
dev-java/java-config:     2.1.12-r1
dev-lang/python:          2.7.3-r2, 3.2.3
dev-util/cmake:           2.8.9
dev-util/pkgconfig:       0.27.1
sys-apps/baselayout:      2.1-r1
sys-apps/openrc:          0.11.8
sys-apps/sandbox:         2.5
sys-devel/autoconf:       2.13, 2.69
sys-devel/automake:       1.9.6-r3, 1.11.6
sys-devel/binutils:       2.22-r1
sys-devel/gcc:            4.6.3
sys-devel/gcc-config:     1.7.3
sys-devel/libtool:        2.4-r1
sys-devel/make:           3.82-r4
sys-kernel/linux-headers: 3.6 (virtual/os-headers)
sys-libs/glibc:           2.15-r3
Repositories: gentoo
ACCEPT_KEYWORDS="amd64 ~amd64"
ACCEPT_LICENSE="*"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -O2 -fomit-frame-pointer -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/config /usr/share/gnupg/qualified.txt /var/bind"
CONFIG_PROTECT_MASK="${EPREFIX}/etc/gconf /etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php5.4/ext-active/ /etc/php/cgi-php5.4/ext-active/ /etc/php/cli-php5.4/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-march=native -O2 -fomit-frame-pointer -pipe"
DISTDIR="/usr/portage/distfiles"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="http://distfiles.gentoo.org"
LANG="en_US.UTF-8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j12"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_EXTRA_OPTS="--timeout=100"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/dev/shm"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
USE="X Xaw3d a52 aac acl acpi alsa amd64 apache2 audiofile bash-completion bcmath berkdb bzip2 cairo caps cdparanoia cdr clamav cli cracklib crypt ctype cups cxx dbus dga directfb dri dts dv dvd dvdr encode esd ffmpeg fftw flac foomaticdb fortran gcj gd gdbm gif glut gnutls gphoto2 gpm gtk iconv imagemagick imap imlib ipv6 javascript jpeg kde lm_sensors lzo mad mikmod mjpeg mmx mng modules mp3 mpeg mplayer mudflap multilib musepack mysql mysqli nas ncurses nls nptl offensive ogg openal openexr opengl openmp oss pam pcre pdf perl plasma plotutils png policykit portaudio posix ppds python qt3support qt4 quicktime readline sasl sdl session slp sndfile sockets sox speex spell sse sse2 ssl svg syslog tcl tcpd theora threads tiff tk truetype udev unicode usb vhosts vorbis wmf x264 xml xmp xpm xulrunner xvid zlib" ABI_X86="64" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ubx" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" LINGUAS="en en_US" PHP_TARGETS="php5-3" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_2" RUBY_TARGETS="ruby18 ruby19" USERLAND="GNU" VIDEO_CARDS="nv nvidia vesa" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, USE_PYTHON

=================================================================
                        Package Settings
=================================================================

x11-drivers/nvidia-drivers-313.18 was built with the following:
USE="X acpi (multilib) tools -pax_kernel"
Back to top
View user's profile Send private message
John R. Graham
Administrator
Administrator


Joined: 08 Mar 2005
Posts: 7397
Location: Somewhere over Atlanta, Georgia

PostPosted: Tue Feb 05, 2013 9:49 pm    Post subject: Reply with quote

Is it as simple as a missing symlink? I believe the nvidia-drivers package depends on the /usr/src/linux symlink existing and pointing to the source of the running kernel.

- John
_________________
This space intentionally left blank.
Back to top
View user's profile Send private message
jagdpanther
Apprentice
Apprentice


Joined: 22 Nov 2003
Posts: 219

PostPosted: Tue Feb 05, 2013 10:01 pm    Post subject: Reply with quote

I pointed the symlink /usr/src/linux at the new kernel just before I compiled it.
Thanks for the reply, any other suggestions?
Back to top
View user's profile Send private message
ulenrich
Veteran
Veteran


Joined: 10 Oct 2010
Posts: 1122

PostPosted: Tue Feb 05, 2013 10:43 pm    Post subject: Reply with quote

http://forums.gentoo.org/viewtopic-p-7239256.html#7239256
_________________
fun2gen2
Back to top
View user's profile Send private message
jagdpanther
Apprentice
Apprentice


Joined: 22 Nov 2003
Posts: 219

PostPosted: Tue Feb 05, 2013 11:23 pm    Post subject: Reply with quote

Fixed.

Thanks Ulenrich.

The following symbolic link refered to in
http://forums.gentoo.org/viewtopic-p-7239256.html#7239256 fixes the issue:

Code:
ln -s /usr/src/linux/include/generated/uapi/linux/version.h /usr/src/linux/include/linux/version.h
Back to top
View user's profile Send private message
init_6
Apprentice
Apprentice


Joined: 22 Jun 2008
Posts: 162

PostPosted: Wed Feb 06, 2013 4:14 pm    Post subject: Reply with quote

Ok so this is vanilla bug… so nice
Back to top
View user's profile Send private message
Yuriy Dmitriev
n00b
n00b


Joined: 06 Feb 2013
Posts: 1

PostPosted: Wed Feb 06, 2013 6:38 pm    Post subject: Reply with quote

John R. Graham wrote:
Is it as simple as a missing symlink? I believe the nvidia-drivers package depends on the /usr/src/linux symlink existing and pointing to the source of the running kernel.

- John


Same problem and build messages. Symlink is set up correctly.
Back to top
View user's profile Send private message
jagdpanther
Apprentice
Apprentice


Joined: 22 Nov 2003
Posts: 219

PostPosted: Wed Feb 06, 2013 6:50 pm    Post subject: Reply with quote

I had this issue on both of my Gentoo systems. Adding the symbolic link fixed both.
I don't know if the order is important but I added the symbolic link AFTER I compiled the kernel and after I booted into 3.7.6.
(I have no idea if you add this symbolic link before you compile the kernel if it will change anything.)
Back to top
View user's profile Send private message
ulenrich
Veteran
Veteran


Joined: 10 Oct 2010
Posts: 1122

PostPosted: Wed Feb 06, 2013 9:34 pm    Post subject: Reply with quote

@Yuriy, John spoke about the symlink /usr/src/linux
But we go deeper now ...
_________________
fun2gen2
Back to top
View user's profile Send private message
ExecutorElassus
l33t
l33t


Joined: 11 Mar 2004
Posts: 729
Location: Stuttgart, Germany

PostPosted: Thu Feb 07, 2013 10:23 am    Post subject: Reply with quote

same problem, same solution.

Thanks, y'all! <3
Back to top
View user's profile Send private message
ssuominen
Developer
Developer


Joined: 30 Sep 2005
Posts: 2000
Location: Finland

PostPosted: Thu Feb 07, 2013 11:04 am    Post subject: Reply with quote

I had the exact same warning/error because I had `chmod` of /usr/src 700 for my own user account and there was no obvious "Permission denied." errors. Took a while to figure that out.
Back to top
View user's profile Send private message
baldrs
n00b
n00b


Joined: 25 Jan 2013
Posts: 7

PostPosted: Thu Feb 07, 2013 10:14 pm    Post subject: Reply with quote

jagdpanther wrote:
Fixed.

Thanks Ulenrich.

The following symbolic link refered to in
http://forums.gentoo.org/viewtopic-p-7239256.html#7239256 fixes the issue:

Code:
ln -s /usr/src/linux/include/generated/uapi/linux/version.h /usr/src/linux/include/linux/version.h


Thanks! That's the fix that helped me.
Back to top
View user's profile Send private message
daniel.santos
n00b
n00b


Joined: 05 Jun 2007
Posts: 27

PostPosted: Mon Feb 11, 2013 1:55 pm    Post subject: Reply with quote

jagdpanther wrote:
Code:
ln -s /usr/src/linux/include/generated/uapi/linux/version.h /usr/src/linux/include/linux/version.h
Thank you!
Back to top
View user's profile Send private message
chris972
Tux's lil' helper
Tux's lil' helper


Joined: 02 Mar 2012
Posts: 97

PostPosted: Mon Feb 25, 2013 8:19 pm    Post subject: Reply with quote

Doesn't work for me :(

Code:
# ls -l /usr/src/linux/include/generated/uapi/linux/version.h /usr/src/linux/include/linux/version.h
-rw-r--r-- 1 root root 97 25 févr. 12:24 /usr/src/linux/include/generated/uapi/linux/version.h
lrwxrwxrwx 1 root root 53 25 févr. 16:08 /usr/src/linux/include/linux/version.h -> /usr/src/linux/include/generated/uapi/linux/version.h


Code:
# uname -a
Linux medion 3.7.9-gentoo #1 SMP Mon Feb 25 12:35:12 AST 2013 x86_64 Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz GenuineIntel GNU/Linux


Code:
# eselect kernel list
Available kernel symlink targets:
  [1]   linux-3.6.11-gentoo
  [2]   linux-3.7.9-gentoo *


Code:
# cat /etc/portage/package.mask
# recommandé par portage
>=x11-drivers/nvidia-drivers-305.0.0

because of my graphic card (suggested by portage himself when tried to update)

Code:
# emerge -a1 nvidia-drivers

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] x11-drivers/nvidia-drivers-304.64 [304.64]

Would you like to merge these packages? [Yes/No]

>>> Verifying ebuild manifests
>>> Running pre-merge checks for x11-drivers/nvidia-drivers-304.64
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found kernel object directory:
 *     /lib/modules/3.7.9-gentoo/build
 * Found sources for kernel version:
 *     3.7.9-gentoo
 * Checking for suitable kernel configuration options...                                                                        [ ok ]

>>> Emerging (1 of 1) x11-drivers/nvidia-drivers-304.64 from x-portage
 * NVIDIA-Linux-x86_64-304.64.run SHA256 SHA512 WHIRLPOOL size ;-) ...                                                          [ ok ]
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found kernel object directory:
 *     /lib/modules/3.7.9-gentoo/build
 * Found sources for kernel version:
 *     3.7.9-gentoo
 * Gentoo supports kernel's which are supported by NVIDIA
 * which are limited to the following kernels:
 * <sys-kernel/gentoo-sources-3.7
 * <sys-kernel/vanilla-sources-3.7
 *
 * You are on your own
>>> Unpacking source...
>>> Unpacking NVIDIA-Linux-x86_64-304.64.run to /other/tmp/portage/x11-drivers/nvidia-drivers-304.64/work
>>> Source unpacked in /other/tmp/portage/x11-drivers/nvidia-drivers-304.64/work
>>> Preparing source in /other/tmp/portage/x11-drivers/nvidia-drivers-304.64/work ...
 * Converting /kernel/Makefile.kbuild to use M= instead of SUBDIRS= ...                                                         [ ok ]
 * Applying nvidia-drivers-304.64-kernel-3.7.patch ...                                                                          [ ok ]
>>> Source prepared.
>>> Configuring source in /other/tmp/portage/x11-drivers/nvidia-drivers-304.64/work ...
>>> Source configured.
HOSTS: localhost/4 serveur2.novazur.fr/2 cored.novazur.fr/2 compaq.novazur.fr/2, MAKEOPTS: -j10
>>> Compiling source in /other/tmp/portage/x11-drivers/nvidia-drivers-304.64/work ...
 * Preparing nvidia module
make -j10 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' ARCH=x86_64 IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/3.7.9-gentoo/build 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


I don't know what to try else.

(Bad english so explain very simple please ;) )
Back to top
View user's profile Send private message
gienah
Developer
Developer


Joined: 24 Nov 2010
Posts: 99
Location: AU

PostPosted: Tue Feb 26, 2013 1:32 am    Post subject: Reply with quote

I tried searching with Google for a different patch for you to try, there is one here:

http://slackblogs.blogspot.com.au/2012/12/linux-kernel-37-vmware-workstation-and.html

Edit: Hmm, I'm not sure that helps at all, maybe you are already using that patch.
Back to top
View user's profile Send private message
chris972
Tux's lil' helper
Tux's lil' helper


Joined: 02 Mar 2012
Posts: 97

PostPosted: Tue Feb 26, 2013 4:27 am    Post subject: Reply with quote

Thanks a lot for your help.
I'll try this patch, even if I can't understand (after reading it) how it could solve my problem of kernel sources.
Back to top
View user's profile Send private message
gienah
Developer
Developer


Joined: 24 Nov 2010
Posts: 99
Location: AU

PostPosted: Tue Feb 26, 2013 10:50 am    Post subject: Reply with quote

It compiled for me with sys-kernel/gentoo-sources-3.8.0.

I have placed 2 patches in this tarball here (these are unsupported, I'm just trying to help):

http://dev.gentoo.org/~gienah/unsupported/etc-portage-patches-x11-drivers-nvidia-drivers-304-64-and-313-18-for-kernel-3-8-0.tar.gz

For:

x11-drivers/nvidia-drivers-304.64
x11-drivers/nvidia-drivers-313.18

If anyone wants to try them, the procedure to install the patches to first move any other conflicting
user nvidia-drivers patches out of the way, then:

Code:

cd /
tar xvf etc-portage-patches-x11-drivers-nvidia-drivers-304-64-and-313-18-for-kernel-3-8-0.tar.gz


There is some chance they may work with other nvidia driver versions, you could create symlinks in
/etc/portage/patches/x11-drivers if you wanted to try.

And that's it. The uapi/linux/version.h symlink is not required for these patches (they patch the
kernel/conftest.sh so the nvidia driver can find the version.h header instead).
Back to top
View user's profile Send private message
chris972
Tux's lil' helper
Tux's lil' helper


Joined: 02 Mar 2012
Posts: 97

PostPosted: Tue Feb 26, 2013 1:48 pm    Post subject: Reply with quote

Great great great job !
I did the trick for me.
I'm actually trying if all works fine with 3.7.9 kernel and X.
Thank you very much
Back to top
View user's profile Send private message
depontius
Advocate
Advocate


Joined: 05 May 2004
Posts: 2384

PostPosted: Wed Feb 27, 2013 4:50 pm    Post subject: Reply with quote

I have 2 systems that are tied to the 173-series and 1 system tied to the 304-series of legacy drivers. The last half-dozen or so times when a kernel update has broken nvidia-drivers, the leading driver gets fixed first, and the legacy drivers follow. Any idea when this is going to happen?
_________________
.sigs waste space and bandwidth
Back to top
View user's profile Send private message
gienah
Developer
Developer


Joined: 24 Nov 2010
Posts: 99
Location: AU

PostPosted: Thu Feb 28, 2013 1:56 am    Post subject: Reply with quote

There is a proposed patch for the 173-series in:

https://bugs.gentoo.org/show_bug.cgi?id=447566
Back to top
View user's profile Send private message
knob-creek
n00b
n00b


Joined: 28 Jul 2008
Posts: 8
Location: Germany

PostPosted: Sun Mar 03, 2013 4:07 pm    Post subject: Not very nice... Reply with quote

When i sync-ed the 2nd of my two machines with nvidia graphics today, i couldn't help to notice that nvidia-drivers do not build against kernel 3.7.10 any longer. This was no problem just two days ago and comparing the portage files revealed that the support was intentionally dropped.

The "missing link" mentioned above would probably have helped, as did down-dating to the march-1st state still present on the first machine. However: why was that patch enabling the compilation against 3.7 kernels dropped? Especially stabilizing 3.7 kernels in a rapid pace (and removing older 3.7 ones immediately afterwards) and dropping nvidia support shortly afterwards was not very friendly to the unsuspecting users.
Back to top
View user's profile Send private message
dobbs
Tux's lil' helper
Tux's lil' helper


Joined: 20 Aug 2005
Posts: 88
Location: Wenatchee, WA

PostPosted: Mon Mar 04, 2013 2:54 am    Post subject: Reply with quote

I too would like answers to knob-creek's questions. But also, if nvidia-drivers isn't meant to build on kernels >=3.7, why doesn't it block those kernels?

I stumbled onto this via an "emerge -DavuN world" (my standard update command). After a day of building and revep-rebuilding and modifying configuration files, this kind of thing damages my mood.
Back to top
View user's profile Send private message
Navar
Apprentice
Apprentice


Joined: 20 Aug 2012
Posts: 222

PostPosted: Mon Mar 04, 2013 10:09 am    Post subject: Reply with quote

chris972 wrote:
Doesn't work for me :(
>>> Emerging (1 of 1) x11-drivers/nvidia-drivers-304.64 from x-portage


Your own overlay copy causing you issues perhaps?

Appears as though you weren't using the ebuild from portage with an epatch setup in /etc/portage/patches/x11-drivers/nvidia-304.64/kernel-3.7.9.patch? See the nvidia driver closed bug below for lots more info if you're determined.

That and the link in the generated path mentioned were all I needed to make work for me. It also worked for 3.7.10. This was on x86 architecture though.

And while it's somewhat of a headache as you're all mentioning, I'm with the (former?) Gentoo dev Doug Goldstein on this that it is probably better to package.mask kernel sources =>3.7 until Nvidia officially states support. The only thing I sort of questioned was why the nvidia-drivers didn't block bringing in kernel >=3.7 so most users could mostly and blissfully unaware ignore the issue until it was ok.

@knob-creek & dobbs: short answer, triage and rabbit holes, as in Alice. As in how far do you want to go? See how far patience is tested in this recent nvidia-drivers closed bug and kernel side.

Summary: you were supposed to gleam and know that kernel issues come foremost over secondary driver issues. Kernel team is dealing with multiple patch issues, including a recent important security vulnerability fix affecting many kernels and end of life from upstream for others (which means unlikely for upstream patch support)--they did what they needed to do. Doug, who was handling nvidia-drivers, warned you that regardless of the current highest stable kernel available that you were taking a risk trying to get the unsupported upstream (Nvidia) existing drivers to work. That is essentially all that should be expected from a Gentoo developer regarding a binary blob from upstream. It was better to mask out kernel >=3.7, resync, re-emerge and rebuild the existing lower patched kernels to fix vulnerabilities and keep proper nvidia support of said available drivers built against that. Some people refused to see reason on official stance/support and the rest just took their chances as the ebuild elog stated that you were 'on your own' if you wished to make it work regardless (which I have no issue with, but that shouldn't have been Doug's problem).

I think it's great that the community tried so hard to make this work with whatever bandaids they threw at it. But I find it unfortunate that someone like Doug who gave up a lot of time and effort in a courteous and professional manner to explain official decisions made was treated poorly. Scaring off your volunteer developers (especially ones that communicate) will cause the Gentoo community far too much harm. Many other distributions don't even put forth that kind of effort for their users. Please keep that in mind.
Back to top
View user's profile Send private message
gienah
Developer
Developer


Joined: 24 Nov 2010
Posts: 99
Location: AU

PostPosted: Tue Mar 05, 2013 6:22 am    Post subject: Reply with quote

I guess I'd comment on the bug 447566 but its closed and I can't login at the moment.
Since its closed, I'm thinking it seems ok for me to commit these 2 patches, as I have
tested they both compile, I run 313-18 with kernel 3.8.0, and at least one user
ported that the patch for 304-64 works with kernel 3.7.9.

http://dev.gentoo.org/~gienah/unsupported/etc-portage-patches-x11-drivers-nvidia-drivers-304-64-and-313-18-for-kernel-3-8-0.tar.gz

I haven't tested this one for nvidia-drivers-173.14.36:

https://bugs.gentoo.org/attachment.cgi?id=340010

It would be neat if anyone would like to test these and report the results.
Back to top
View user's profile Send private message
jagdpanther
Apprentice
Apprentice


Joined: 22 Nov 2003
Posts: 219

PostPosted: Tue Mar 05, 2013 1:17 pm    Post subject: Reply with quote

Originally I had this issue with vanilla-sources-3.7.6 and nvidia-drivers-313.18 then the issue went away with subsequent kernel source packages.

The 'fails to determine kernel version' issue is back with vanilla-sources-3.7.10 and nvidia-drivers-313.18. Same symbolic link addition above fixes the issue. I have not switched to vanilla-sources-3.8.x yet.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum