public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Adam Carter <adamcarter3@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 23:13:54 +1100	[thread overview]
Message-ID: <AANLkTi=9+SOFm38xuq17AUwuhLcj38TJBXHFUUEwzEdQ@mail.gmail.com> (raw)
In-Reply-To: <4D32D400.8050409@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 762 bytes --]

>
>
>>
>>
>
> I have compiled a kernel for 2.6.37 but I have not booted it yet.  I'll set
> the link to the new kernel, emerge nvidia and see what happens when I boot
> the new kernel.
>
> In the past, I was on x86 on my old rig.  Maybe it is the arch that affects
> something.  I'm not sure but will test later on today.  Sort of in the
> middle of a download at the moment.
>
>
Interested. I *thought* what Dale's saying worked too. The no kernel config
error sounds more like you havent done make oldconfig/menuconfig whatever to
create the .config file. So maybe the problem is not that you have to be
running the kernel you want to build for, but that you have at least created
the .config file for the kernel you want to build for. I'm guessing
obviously.

[-- Attachment #2: Type: text/html, Size: 1191 bytes --]

  reply	other threads:[~2011-01-16 12:16 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 [this message]
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='AANLkTi=9+SOFm38xuq17AUwuhLcj38TJBXHFUUEwzEdQ@mail.gmail.com' \
    --to=adamcarter3@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