[gentoo-user] invalid argument when trying to modprobe nvidia module

[gentoo-user] invalid argument when trying to modprobe nvidia module

[covici]

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.  I could not find a bug anywhere -- is this a too
recent kernel for him?

Any assistance would be appreciated.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Mark Knecht]

On Sat, Jan 15, 2011 at 6: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.  I could not find a bug anywhere -- is this a too
> recent kernel for him?
>
> Any assistance would be appreciated.
>
> --
> Your life is like a penny.  You're going to lose it.  The question is:
> How do
> you spend it?
>
>         John Covici
>         covici@ccs.covici.com

What error? What nvidia device?

I'm running 2.6.37 here with nvidia-drivers so it can basically work.

k2 ~ # uname -a
Linux k2 2.6.37-gentoo #1 SMP PREEMPT Sun Jan 9 10:38:01 PST 2011
x86_64 Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz GenuineIntel GNU/Linux
k2 ~ # eix -Ic nvidia
[I] media-video/nvidia-settings (260.19.29@12/19/10): NVIDIA Linux X11
Settings Utility
[I] x11-drivers/nvidia-drivers (260.19.29@01/09/11): NVIDIA X11 driver
and GLX libraries
[1] "pentoo" /var/lib/layman/pentoo

Found 2 matches.
k2 ~ # lspci | grep VGA
02:00.0 VGA compatible controller: nVidia Corporation G96 [GeForce
9500 GT] (rev a1)
k2 ~ #

Cheers,
Mark

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[covici]

Mark Knecht <markknecht@gmail.com> wrote:

> On Sat, Jan 15, 2011 at 6: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.  I could not find a bug anywhere -- is this a too
> > recent kernel for him?
> >
> > Any assistance would be appreciated.
> >
> > --
> > Your life is like a penny.  You're going to lose it.  The question is:
> > How do
> > you spend it?
> >
> >         John Covici
> >         covici@ccs.covici.com
> 
> What error? What nvidia device?
> 
> I'm running 2.6.37 here with nvidia-drivers so it can basically work.
> 
> k2 ~ # uname -a
> Linux k2 2.6.37-gentoo #1 SMP PREEMPT Sun Jan 9 10:38:01 PST 2011
> x86_64 Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz GenuineIntel GNU/Linux
> k2 ~ # eix -Ic nvidia
> [I] media-video/nvidia-settings (260.19.29@12/19/10): NVIDIA Linux X11
> Settings Utility
> [I] x11-drivers/nvidia-drivers (260.19.29@01/09/11): NVIDIA X11 driver
> and GLX libraries
> [1] "pentoo" /var/lib/layman/pentoo
> 
> Found 2 matches.
> k2 ~ # lspci | grep VGA
> 02:00.0 VGA compatible controller: nVidia Corporation G96 [GeForce
> 9500 GT] (rev a1)
> k2 ~ #

Here is my nvidia drivers version:
Installed versions:  260.19.29!s(09:14:27 PM 01/15/2011)(acpi gtk
kernel_linux -custom-cflags -multilib)

I am using gentoo-x86 and the card is 01:00.0 VGA compatible controller:
nVidia Corporation G86 [GeForce 8400 GS] (rev a1) and I get invalid
argument when I use the command
modprobe nvidia

Thanks for your quick response.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Adam Carter]

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

On Sun, Jan 16, 2011 at 1: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.
>

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.

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

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[covici]

Adam Carter <adamcarter3@gmail.com> wrote:

> On Sun, Jan 16, 2011 at 1: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.
> >
> 
> 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.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Mark Knecht]

On Sat, Jan 15, 2011 at 6:56 PM,  <covici@ccs.covici.com> wrote:
<SNIP>
>
> Here is my nvidia drivers version:
> Installed versions:  260.19.29!s(09:14:27 PM 01/15/2011)(acpi gtk
> kernel_linux -custom-cflags -multilib)
>
> I am using gentoo-x86 and the card is 01:00.0 VGA compatible controller:
> nVidia Corporation G86 [GeForce 8400 GS] (rev a1) and I get invalid
> argument when I use the command
> modprobe nvidia
>
> Thanks for your quick response.
>

According to these nvidia pages the GeForce 8400GS is supported by
both the 173 series as well as the 260 series drivers:

http://www.nvidia.com/object/linux-display-ia32-173.14.28-driver.html

http://www.nvidia.com/object/linux-display-ia32-260.19.29-driver.html

Assuming I'm not making a mistake in my reading have you tried them
both, rebuilding each for your current kernel? It may be that you need
a specific one for the kernel you are running.

Good luck,
Mark

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Peter Humphrey]

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.

-- 
Rgds
Peter.          Linux Counter 5290, 1994-04-23.

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Dale]

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

:-)  :-)

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Peter Humphrey]

On Sunday 16 January 2011 10:48:45 Dale wrote:
> Peter Humphrey wrote:

> > 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.

> 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?

It could easily be, yes. I remember being surprised once last year when 
it happened, and since then it's been every time - enough that I've 
written a tiny script to remerge drivers and vbox, then restart xdm. The 
difference may be my ~amd64 system and consequent later versions of 
nvidia-drivers.

-- 
Rgds
Peter.          Linux Counter 5290, 1994-04-23.

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Dale]

Peter Humphrey wrote:
> On Sunday 16 January 2011 10:48:45 Dale wrote:
>    
>> Peter Humphrey wrote:
>>      
>>> 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.
>>>        
>> 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?
>>      
> It could easily be, yes. I remember being surprised once last year when
> it happened, and since then it's been every time - enough that I've
> written a tiny script to remerge drivers and vbox, then restart xdm. The
> difference may be my ~amd64 system and consequent later versions of
> nvidia-drivers.
>
>    

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.

Dale

:-)  :-)

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Adam Carter]

[-- 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 --]

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[covici]

Peter Humphrey <peter@humphrey.ukfsn.org> 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.

I am using x86 rather than 64 and I did emerge it after rebooting to the
new kernel, but I got invalid argument when issuing the modprobe
command.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Adam Carter]

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

>
> I am using x86 rather than 64 and I did emerge it after rebooting to the
> new kernel, but I got invalid argument when issuing the modprobe
> command.
>
>
Can you cut/paste the command and output? and also the command "modinfo
nvidia" and its output?

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

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Alan McKinnon]

Apparently, though unproven, at 11:18 on Sunday 16 January 2011, Peter 
Humphrey did opine thusly:

> 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.

That's nonsense.

The nvidia-driver ebuild will build modules for whatever kernel /usr/src/linuc 
points to. There is no dependency on the running kernel


-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Neil Bothwick]

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

On Sun, 16 Jan 2011 11:06:30 +0000, Peter Humphrey wrote:

> > > 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.  
> 
> > 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?  
> 
> It could easily be, yes. I remember being surprised once last year when 
> it happened, and since then it's been every time - enough that I've 
> written a tiny script to remerge drivers and vbox, then restart xdm.
> The difference may be my ~amd64 system and consequent later versions of 
> nvidia-drivers.

I don't have this problem. You could only see this error
if /usr/src/linux/.config does not exist. As long as you have run make
oldconfig, the drivers should build, although I only build them after
compiling the kernel (but before rebooting).


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Peter Humphrey]

On Sunday 16 January 2011 12:13:54 Adam Carter wrote:

> The no kernel config error sounds more like you havent done make
> oldconfig/menuconfig whatever to create the .config file.

In fact that isn't it. I've copied the .config from /boot, run make 
oldconfig, compiled the kernel and copied it to /boot. Still nvidia-
drivers won't compile, apparently because /usr/src/linux points to a 
kernel other than the running one.

-- 
Rgds
Peter.          Linux Counter 5290, 1994-04-23.

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Peter Humphrey]

On Sunday 16 January 2011 12:54:46 Alan McKinnon wrote:

> That's nonsense.

It is not.

-- 
Rgds
Peter.          Linux Counter 5290, 1994-04-23.

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Alan McKinnon]

Apparently, though unproven, at 17:18 on Sunday 16 January 2011, Peter 
Humphrey did opine thusly:

> On Sunday 16 January 2011 12:54:46 Alan McKinnon wrote:
> > That's nonsense.
> 
> It is not.

It has not been a problem for me, not once, in 4 years at least, both on x86 
and amd64. Other posters report the same and you are the only one reporting 
experiencing the problem.

Logic tells me you likely have something dodgy local to your machine as you 
are the only one so this would be a good point to post the error output you 
get.

-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Dale]

Peter Humphrey wrote:
> On Sunday 16 January 2011 12:13:54 Adam Carter wrote:
>
>    
>> The no kernel config error sounds more like you havent done make
>> oldconfig/menuconfig whatever to create the .config file.
>>      
> In fact that isn't it. I've copied the .config from /boot, run make
> oldconfig, compiled the kernel and copied it to /boot. Still nvidia-
> drivers won't compile, apparently because /usr/src/linux points to a
> kernel other than the running one.
>
>    

I haven't rebooted yet but I did point the symlink to the new kernel.  I 
can emerge nvidia here with no problems.  It noticed it was pointing to 
the new kernel and installed them correctly.  I'll reboot here in a bit 
and see what happens.

Dale

:-)  :-)

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Dale]

Dale wrote:
> Peter Humphrey wrote:
>> On Sunday 16 January 2011 12:13:54 Adam Carter wrote:
>>
>>> The no kernel config error sounds more like you havent done make
>>> oldconfig/menuconfig whatever to create the .config file.
>> In fact that isn't it. I've copied the .config from /boot, run make
>> oldconfig, compiled the kernel and copied it to /boot. Still nvidia-
>> drivers won't compile, apparently because /usr/src/linux points to a
>> kernel other than the running one.
>>
>
> I haven't rebooted yet but I did point the symlink to the new kernel.  
> I can emerge nvidia here with no problems.  It noticed it was pointing 
> to the new kernel and installed them correctly.  I'll reboot here in a 
> bit and see what happens.
>
> Dale
>
> :-)  :-)
>

OK.  I just rebooted.  When I booted, xdm started and the nvidia drivers 
worked fine.  I was still running the old kernel when I built the new 
one.  Peter, you got something weird going on with your system?

Dale

:-)  :-)

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[covici]

Dale <rdalek1967@gmail.com> wrote:

> Peter Humphrey wrote:
> > On Sunday 16 January 2011 12:13:54 Adam Carter wrote:
> >
> >    
> >> The no kernel config error sounds more like you havent done make
> >> oldconfig/menuconfig whatever to create the .config file.
> >>      
> > In fact that isn't it. I've copied the .config from /boot, run make
> > oldconfig, compiled the kernel and copied it to /boot. Still nvidia-
> > drivers won't compile, apparently because /usr/src/linux points to a
> > kernel other than the running one.
> >
> >    
> 
> I haven't rebooted yet but I did point the symlink to the new kernel.
> I can emerge nvidia here with no problems.  It noticed it was pointing
> to the new kernel and installed them correctly.  I'll reboot here in a
> bit and see what happens.
> 
Getting back to the original, I tried with 2.6.37 and it didn't work
either, but my 2.6.30 works fine with the same drivers.


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Dale]

covici@ccs.covici.com wrote:
> Dale<rdalek1967@gmail.com>  wrote:
>
>    
>> Peter Humphrey wrote:
>>      
>>> On Sunday 16 January 2011 12:13:54 Adam Carter wrote:
>>>
>>>
>>>        
>>>> The no kernel config error sounds more like you havent done make
>>>> oldconfig/menuconfig whatever to create the .config file.
>>>>
>>>>          
>>> In fact that isn't it. I've copied the .config from /boot, run make
>>> oldconfig, compiled the kernel and copied it to /boot. Still nvidia-
>>> drivers won't compile, apparently because /usr/src/linux points to a
>>> kernel other than the running one.
>>>
>>>
>>>        
>> I haven't rebooted yet but I did point the symlink to the new kernel.
>> I can emerge nvidia here with no problems.  It noticed it was pointing
>> to the new kernel and installed them correctly.  I'll reboot here in a
>> bit and see what happens.
>>
>>      
> Getting back to the original, I tried with 2.6.37 and it didn't work
> either, but my 2.6.30 works fine with the same drivers.
>
>    

I'm using nvidia-drivers-260.19.29 on kernel 2.6.37-gentoo and it is 
working fine so far.  It booted and X is working.

Could there be something amiss in the kernel config?  I ran into 
problems a while back.  It was missing the option CONFIG_SYSVIPC in the 
kernel.  You got that built in?

Dale

:-)  :-)

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[covici]

Dale <rdalek1967@gmail.com> wrote:

> covici@ccs.covici.com wrote:
> > Dale<rdalek1967@gmail.com>  wrote:
> >
> >    
> >> Peter Humphrey wrote:
> >>      
> >>> On Sunday 16 January 2011 12:13:54 Adam Carter wrote:
> >>>
> >>>
> >>>        
> >>>> The no kernel config error sounds more like you havent done make
> >>>> oldconfig/menuconfig whatever to create the .config file.
> >>>>
> >>>>          
> >>> In fact that isn't it. I've copied the .config from /boot, run make
> >>> oldconfig, compiled the kernel and copied it to /boot. Still nvidia-
> >>> drivers won't compile, apparently because /usr/src/linux points to a
> >>> kernel other than the running one.
> >>>
> >>>
> >>>        
> >> I haven't rebooted yet but I did point the symlink to the new kernel.
> >> I can emerge nvidia here with no problems.  It noticed it was pointing
> >> to the new kernel and installed them correctly.  I'll reboot here in a
> >> bit and see what happens.
> >>
> >>      
> > Getting back to the original, I tried with 2.6.37 and it didn't work
> > either, but my 2.6.30 works fine with the same drivers.
> >
> >    
> 
> I'm using nvidia-drivers-260.19.29 on kernel 2.6.37-gentoo and it is
> working fine so far.  It booted and X is working.
> 
> Could there be something amiss in the kernel config?  I ran into
> problems a while back.  It was missing the option CONFIG_SYSVIPC in
> the kernel.  You got that built in?
> 
> Dale
> 
> :-)  :-)
Yep, its in there.


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Peter Humphrey]

On Monday 17 January 2011 02:28:57 Dale wrote:

> Peter, you got something weird going on with your system?

Maybe I have, or did have at one time. I'll try it again at the next 
update. Thanks for the info.

-- 
Rgds
Peter.          Linux Counter 5290, 1994-04-23.

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Peter Humphrey]

On Sunday 16 January 2011 15:32:03 Alan McKinnon wrote:

> Logic tells me you likely have something dodgy local to your machine
> as you are the only one so this would be a good point to post the
> error output you get.

As I said to Dale, I'll check at the next upgrade. Thanks anyway.

-- 
Rgds
Peter.          Linux Counter 5290, 1994-04-23.

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Bill Longman]

On 01/16/2011 01:18 AM, 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.

You can *always* compile any package against your choice of kernel. Just
use "KERNEL_DIR=/usr/src/mykerneldir emerge package". It doesn't have to
be the running kernel or the current kernel.

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Peter Humphrey]

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

On Tuesday 25 January 2011 17:05:41 Bill Longman wrote:

> You can *always* compile any package against your choice of kernel.
> Just use "KERNEL_DIR=/usr/src/mykerneldir emerge package". It
> doesn't have to be the running kernel or the current kernel.

We've been through this once.

-- 
Rgds
Peter.          Linux Counter 5290, 1994-04-23.

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

[gentoo-user] Re: invalid argument when trying to modprobe nvidia module

[walt]

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.

Re: [gentoo-user] Re: invalid argument when trying to modprobe nvidia module

[Alan McKinnon]

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

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Alan McKinnon]

Apparently, though unproven, at 19:33 on Tuesday 25 January 2011, Peter 
Humphrey did opine thusly:

> On Tuesday 25 January 2011 17:05:41 Bill Longman wrote:
> > You can *always* compile any package against your choice of kernel.
> > Just use "KERNEL_DIR=/usr/src/mykerneldir emerge package". It
> > doesn't have to be the running kernel or the current kernel.
> 
> We've been through this once.

Correct me if I'm wrong[1] but wasn't it you who had this problem last time 
around? Did you ever figure out what the problem really was?

[1] old age this end = fuzzy memory = get names mixed up sometimes


-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Peter Humphrey]

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

On Tuesday 25 January 2011 22:43:17 Alan McKinnon wrote:
> Apparently, though unproven, at 19:33 on Tuesday 25 January 2011,
> Peter Humphrey did opine thusly:
> > On Tuesday 25 January 2011 17:05:41 Bill Longman wrote:
> > > You can *always* compile any package against your choice of
> > > kernel. Just use "KERNEL_DIR=/usr/src/mykerneldir emerge
> > > package". It doesn't have to be the running kernel or the
> > > current kernel.
> > 
> > We've been through this once.
> 
> Correct me if I'm wrong[1] but wasn't it you who had this problem
> last time around?

T'was I.

> Did you ever figure out what the problem really was?

I haven't investigated any further yet because it would need too much 
regression. As I said at the time, I'll check it when the next upgrade 
comes along.

> [1] old age this end = fuzzy memory = get names mixed up sometimes

Eh? I thought you were just a young whipper-snapper. And no, you can't 
have any fuzzy memory - it's all taken.

-- 
Rgds
Peter.          Linux Counter 5290, 1994-04-23.

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

Re: [gentoo-user] Re: invalid argument when trying to modprobe nvidia module

[Peter Humphrey]

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

On Tuesday 25 January 2011 19:31:04 walt wrote:

> Or, it might have been the chicken I sacrificed in front of the
> computer.

No, that wouldn't do it - it's the wrong place. You need to make the 
sacrifice as close as possible to the oven.

-- 
Rgds
Peter.          Linux Counter 5290, 1994-04-23.

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

Re: [gentoo-user] invalid argument when trying to modprobe nvidia module

[Alan McKinnon]

Apparently, though unproven, at 01:47 on Wednesday 26 January 2011, Peter 
Humphrey did opine thusly:

> > [1] old age this end = fuzzy memory = get names mixed up sometimes
> 
> Eh? I thought you were just a young whipper-snapper. And no, you can't 
> have any fuzzy memory - it's all taken.

You thought wrong, but don't worry - most people do :-)   I'm usually guessed 
at 10 years younger than I really am. 

It must be the girlfriend's youthfulness rubbing off. I like to make her blush 
and tell people that when I finished school, she was still in kindergarten.



-- 
alan dot mckinnon at gmail dot com