Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
nvidia driver ERROR; no .config found in /usr/src/linux
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
Phredus
n00b
n00b


Joined: 07 Feb 2013
Posts: 47

PostPosted: Sun Jun 08, 2014 3:32 am    Post subject: nvidia driver ERROR; no .config found in /usr/src/linux Reply with quote

[topic=]
ERROR: x11-drivers/nvidia-drivers-334.21-r3::gentoo failed (setup phase):
Kernel not configured; no .config found in /usr/src/linux
[/topic]

[post=]
I am stuck with this issue for a while any help would be greatly appreciated. Thank you
[/post]



Code:
minig ~ # emerge --update --deep --with-bdeps=y --newuse world                  Calculating dependencies... done!

The following packages are causing rebuilds:

  (x11-base/xorg-server-1.15.0::gentoo, ebuild scheduled for mege) causes rebuilds for:
    (x11-drivers/xf86-input-mouse-1.9.0::gentoo, ebuild scheduled for merge)
    (x11-drivers/xf86-input-keyboard-1.7.0::gentoo, ebuild scheduled for merge)
    (x11-drivers/xf86-video-vesa-2.3.3::gentoo, ebuild scheduled for merge)
    (x11-drivers/xf86-video-fbdev-0.4.4::gentoo, ebuild scheduled for merge)
    (x11-drivers/xf86-video-nv-2.1.20-r1::gentoo, ebuild scheduled for merge)

>>> Verifying ebuild manifests
>>> Running pre-merge checks for x11-drivers/nvidia-drivers-334.21-r3
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     3.12.21-gentoo-r1
 * Checking for suitable kernel configuration options...                 [ ok ]
>>> Running pre-merge checks for sys-devel/llvm-3.3-r3
 * Checking for at least 550 MiB disk space at "/var/tmp/portage/sys-devel/llvm-3.3-r3/temp" ...                                                         [ ok ]
>>> Running pre-merge checks for x11-base/xorg-server-1.15.0
>>> Running pre-merge checks for kde-base/kdelibs-4.12.5
>>> Running pre-merge checks for x11-drivers/xf86-input-synaptics-1.7.4
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     3.12.21-gentoo-r1
>>> Running pre-merge checks for x11-drivers/xf86-input-evdev-2.8.2
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     3.12.21-gentoo-r1
 * Checking for suitable kernel configuration options...                 [ ok ]

>>> Emerging (1 of 73) x11-drivers/nvidia-drivers-334.21-r3
 * NVIDIA-Linux-x86-334.21.run SHA256 SHA512 WHIRLPOOL size ;-) ...      [ ok ]
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     3.12.21-gentoo-r1
 * Could not find a usable .config in the kernel source directory.
 * Please ensure that /usr/src/linux points to a configured set of Linux sources.
 * If you are using KBUILD_OUTPUT, please set the environment var so that
 * it points to the necessary object directory so that it might find .config.
 * ERROR: x11-drivers/nvidia-drivers-334.21-r3::gentoo failed (setup phase):
 *   Kernel not configured; no .config found in /usr/src/linux
 *
 * Call stack:
 *                         ebuild.sh, line  93:  Called pkg_setup
 *   nvidia-drivers-334.21-r3.ebuild, line 124:  Called linux-mod_pkg_setup
 *                  linux-mod.eclass, line 570:  Called require_configured_kernel
 *                 linux-info.eclass, line 294:  Called die
 * The specific snippet of code:
 *              die "Kernel not configured; no .config found in ${KV_OUT_DIR}"
 *
 * If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-334.21-r3::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-334.21-r3::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-334.21-r3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-334.21-r3/temp/die.env'.
 * Working directory: '/usr/lib/portage/pym'
 * S: '/var/tmp/portage/x11-drivers/nvidia-drivers-334.21-r3/work/'

>>> Failed to emerge x11-drivers/nvidia-drivers-334.21-r3, Log file:

>>>  '/var/tmp/portage/x11-drivers/nvidia-drivers-334.21-r3/temp/build.log'

 * Messages for package x11-drivers/nvidia-drivers-334.21-r3:

 * Could not find a usable .config in the kernel source directory.
 * Please ensure that /usr/src/linux points to a configured set of Linux sources.
 * If you are using KBUILD_OUTPUT, please set the environment var so that
 * it points to the necessary object directory so that it might find .config.
 * ERROR: x11-drivers/nvidia-drivers-334.21-r3::gentoo failed (setup phase):
 *   Kernel not configured; no .config found in /usr/src/linux
 *
 * Call stack:
 *                         ebuild.sh, line  93:  Called pkg_setup
 *   nvidia-drivers-334.21-r3.ebuild, line 124:  Called linux-mod_pkg_setup
 *                  linux-mod.eclass, line 570:  Called require_configured_kernel
 *                 linux-info.eclass, line 294:  Called die
 * The specific snippet of code:
 *              die "Kernel not configured; no .config found in ${KV_OUT_DIR}"
 *
 * If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-334.21-r3::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-334.21-r3::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-334.21-r3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-334.21-r3/temp/die.env'.
 * Working directory: '/usr/lib/portage/pym'
 * S: '/var/tmp/portage/x11-drivers/nvidia-drivers-334.21-r3/work/'
minig ~ #


Last edited by Phredus on Sun Jun 08, 2014 4:33 am; edited 1 time in total
Back to top
View user's profile Send private message
russK
l33t
l33t


Joined: 27 Jun 2006
Posts: 618

PostPosted: Sun Jun 08, 2014 3:58 am    Post subject: Reply with quote

Is 3.12.21-gentoo-r1 the kernel that you booted? Did you ever build the 3.12.21-gentoo-r1 kernel?

Code:
# uname -r


If that returns kernel 3.12.21-gentoo-r1, you could probably do this:

Code:
zcat /proc/config.gz > /usr/src/linux/.config


and then try the emerge again.

Otherwise, you might be able to use 'eselect' to set the kernel back to the one you are running and then emerge.
Back to top
View user's profile Send private message
Phredus
n00b
n00b


Joined: 07 Feb 2013
Posts: 47

PostPosted: Sun Jun 08, 2014 9:48 am    Post subject: I did and it seems to be working Reply with quote

I ran eselect and selected the older version, which is the one that is running then ran emerge again.

emerge is still running. I will post again with results tomorrow.

Thank you for your help

minig ~ # eselect kernel list
Available kernel symlink targets:
[1] linux-3.10.7-gentoo-r1 *
[2] linux-3.10.17-gentoo
[3] linux-3.12.13-gentoo
[4] linux-3.12.21-gentoo-r1
minig ~ # uname -r
3.10.7-gentoo-r1
minig ~ #
Back to top
View user's profile Send private message
cboldt
l33t
l33t


Joined: 24 Aug 2005
Posts: 829

PostPosted: Sun Jun 08, 2014 5:40 pm    Post subject: Reply with quote

If you are running an older kernel, copy .config from its source directory, into the new source directory, then run `make oldconfig`.

emerge nvidia-drivers will look to whatever directory /usr/src/linux points to, so, if you run more than one kernel, you need to run `emerge nvidia-drivers` for each kernel.

Code:
cd /usr/src/linux-3.12.21-gentoo-r1
cp ../linux-3.12.20-gentoo/.config .
make oldconfig
cd /usr/src
ln -sf linux-3.12.21-gentoo-r1 linux
emerge nvidia-drivers
Back to top
View user's profile Send private message
Phredus
n00b
n00b


Joined: 07 Feb 2013
Posts: 47

PostPosted: Mon Jun 09, 2014 4:01 am    Post subject: I tried solution, here is where i'm at now. Reply with quote

I cleaned up and was able to do a complete emerge without errors.

I cannot get the linux-3.12.21-gentoo-r1 kernel to run altho it is selected in eselect it still shows 3.10.7-gentoo-r1 in uname -r.

Please help

Code:

minig ~ # eselect kernel list
Available kernel symlink targets:
  [1]   linux-3.12.21-gentoo-r1 *
minig ~ # uname -r
3.10.7-gentoo-r1
minig ~ #
Back to top
View user's profile Send private message
cboldt
l33t
l33t


Joined: 24 Aug 2005
Posts: 829

PostPosted: Mon Jun 09, 2014 9:24 am    Post subject: Reply with quote

You have to reboot for the new kernel to take effect. I think the only thing that `eselect kernel` does, is to make the desired softlink. With regard to the nvidia-drivers package, the softlink is used for some driver compiling functions, and the softlink is also used to put the resulting nvidia driver file in the (/lib/modules) directory tree associated with that kernel.

For a reboot to use a different/new kernel, you also have to prepare the boot loader to recognize the new kernel. I use lilo, so preparing the boot loader includes editing /etc/lilo.con, and running the command `lilo` afterwards. Only then (assuming the new kernel and its modules are in place) will the machine be ready to boot into the new kernel.

emerging the source code does not make the kernel ready. The kernel and modules have to be configured, compiled, and put in appropriate places, and the boot loader (lilo or grub) has to be informed too.

Apologies if you knew all of that already, but your question suggests that you thought "eselect kernel", without more, would affect the `uname -a` report.
Back to top
View user's profile Send private message
russK
l33t
l33t


Joined: 27 Jun 2006
Posts: 618

PostPosted: Mon Jun 09, 2014 8:37 pm    Post subject: Reply with quote

If you're still looking for some insttructions, it might be a good idea to look at Sections 6 and 10 of the handbook
Back to top
View user's profile Send private message
Phredus
n00b
n00b


Joined: 07 Feb 2013
Posts: 47

PostPosted: Fri Jun 13, 2014 10:45 pm    Post subject: Solved, Thank you very much guys. Reply with quote

All the fixes that were suggested were needed and helped but the last thing i tried was looking for "startkde".
I noticed startkde was missing from the system. I don't know if I missed it or somehow it was removed.
I emerged kdebase-startkde.
I now have a beautiful "kdegreet" :lol: login screen followed by a beautiful kde fully operational desktop.
the logs are clear of any errors other than minor warnings.
YOU GUYS ARE TERRIFIC. ESPECIALLY: russK, cboldt.
THANK YOU FOR ALL THE HELP DURING THIS MADNESS.
Code:
  # emerge kdebase-startkde

All fixed and happy now!!!!!! :lol: :lol: :lol: "I Love Gentoo"
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
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