From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
Date: Sun, 16 Jan 2011 04:48:45 -0600 [thread overview]
Message-ID: <4D32CD0D.3090606@gmail.com> (raw)
In-Reply-To: <201101160918.06073.peter@humphrey.ukfsn.org>
Peter Humphrey wrote:
> On Sunday 16 January 2011 03:25:41 covici@ccs.covici.com wrote:
>
>> Adam Carter<adamcarter3@gmail.com> wrote:
>>
>>> Did you remember to repoint the /usr/src/linux link? IIRC the
>>> module is built to suit whatever kernel that is pointing to. If
>>> its not set correctly you'll need to re-emerge nvidia-drivers.
>>>
>> linux is pointing correctly and it was after I emerged the
>> nvidia-drivers that I got the invalid argument.
>>
> You can't emerge nvidia-drivers if /usr/src/linux points to a kernel
> version other than the currently running one - it complains it can't find
> a valid kernel config. This means that, after emerging a new kernel
> version, it's necessary to reboot with the new kernel (and fail to start
> X) before it's possible to remerge nvidia-drivers to suit the new kernel
> - you can't do it in advance.
>
> On this ~amd64 multilib box, 260.19.29 has run trouble-free with gentoo-
> sources 2.6.36-r5, 2.6.36-r6 and 2.6.37. Perhaps your -multilib USE flag
> is causing trouble.
>
>
In the past when I do a kernel upgrade, I have linked to the new kernel,
emerged nvidia drivers then rebooted to the new kernel. It worked fine
for me. I haven't done that in a while since I just built a new rig but
I have done that in the past many times.
Is this something new?
Dale
:-) :-)
next prev parent reply other threads:[~2011-01-16 10:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 2:34 [gentoo-user] invalid argument when trying to modprobe nvidia module covici
2011-01-16 2:48 ` Mark Knecht
2011-01-16 2:56 ` covici
2011-01-16 4:15 ` Mark Knecht
2011-01-16 3:18 ` Adam Carter
2011-01-16 3:25 ` covici
2011-01-16 9:18 ` Peter Humphrey
2011-01-16 10:48 ` Dale [this message]
2011-01-16 11:06 ` Peter Humphrey
2011-01-16 11:18 ` Dale
2011-01-16 12:13 ` Adam Carter
2011-01-16 15:16 ` Peter Humphrey
2011-01-17 1:56 ` Dale
2011-01-17 2:28 ` Dale
2011-01-17 10:40 ` Peter Humphrey
2011-01-17 2:50 ` covici
2011-01-17 3:05 ` Dale
2011-01-17 3:28 ` covici
2011-01-16 12:55 ` Neil Bothwick
2011-01-16 12:25 ` covici
2011-01-16 12:44 ` Adam Carter
2011-01-16 12:54 ` Alan McKinnon
2011-01-16 15:18 ` Peter Humphrey
2011-01-16 15:32 ` Alan McKinnon
2011-01-17 10:42 ` Peter Humphrey
2011-01-25 17:05 ` Bill Longman
2011-01-25 17:33 ` Peter Humphrey
2011-01-25 22:43 ` Alan McKinnon
2011-01-25 23:47 ` Peter Humphrey
2011-01-26 0:10 ` Alan McKinnon
2011-01-25 19:31 ` [gentoo-user] " walt
2011-01-25 22:41 ` Alan McKinnon
2011-01-25 23:48 ` Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D32CD0D.3090606@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox