public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: invalid argument when trying to modprobe nvidia module
Date: Wed, 26 Jan 2011 00:41:38 +0200	[thread overview]
Message-ID: <201101260041.38767.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <ihn8du$qkk$1@dough.gmane.org>

Apparently, though unproven, at 21:31 on Tuesday 25 January 2011, walt did 
opine thusly:

> On 01/15/2011 06:34 PM, covici@ccs.covici.com wrote:
> > Hi.  I am trying to use my unstable gentoo on kernel 2.6.36-gentoo-r6
> > and when I emerge nvidia-drivers, I get invalid argument when I try to
> > modprobe the module.
> 
> Forgive me if I'm repeating something already posted in this very long
> thread. I just had the same problem for no obvious reason. I finally
> recompiled the kernel and the problem disappeared (for no obvious reason).
> 
> Or, it might have been the chicken I sacrificed in front of the computer.

Nope, it was the three pirouettes you did in the pale moonlight. That beats 
dead chickens any day.

But most likely your problem was something like /usr/src/linux pointing to the 
wrong place last time you emerged the drivers, or something in a similar vein. 
Perhaps you even configured the kernel and forgot to build-install it, but 
were convinced you did.

The sure certain way to avoid these issues is to always when upgrading out-of-
tree drivers:

- make sure /usr/src/linux point to current running kernel, or the kernel you 
plan to use if different
- build & install that kernel
- build & install drivers

then the usual rmmod && modprobe. If that still doesn't work, reboot. You may 
need this if you rebuilt the kernel after making deep config changes.


-- 
alan dot mckinnon at gmail dot com



  reply	other threads:[~2011-01-25 22:43 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
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 [this message]
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=201101260041.38767.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@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