* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-16 9:18 ` Peter Humphrey
@ 2011-01-16 10:48 ` Dale
2011-01-16 11:06 ` Peter Humphrey
2011-01-16 12:25 ` covici
` (2 subsequent siblings)
3 siblings, 1 reply; 33+ messages in thread
From: Dale @ 2011-01-16 10:48 UTC (permalink / raw
To: gentoo-user
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
:-) :-)
^ permalink raw reply [flat|nested] 33+ messages in thread* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-16 10:48 ` Dale
@ 2011-01-16 11:06 ` Peter Humphrey
2011-01-16 11:18 ` Dale
2011-01-16 12:55 ` Neil Bothwick
0 siblings, 2 replies; 33+ messages in thread
From: Peter Humphrey @ 2011-01-16 11:06 UTC (permalink / raw
To: gentoo-user
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.
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-16 11:06 ` Peter Humphrey
@ 2011-01-16 11:18 ` Dale
2011-01-16 12:13 ` Adam Carter
2011-01-16 12:55 ` Neil Bothwick
1 sibling, 1 reply; 33+ messages in thread
From: Dale @ 2011-01-16 11:18 UTC (permalink / raw
To: gentoo-user
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
:-) :-)
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-16 11:18 ` Dale
@ 2011-01-16 12:13 ` Adam Carter
2011-01-16 15:16 ` Peter Humphrey
0 siblings, 1 reply; 33+ messages in thread
From: Adam Carter @ 2011-01-16 12:13 UTC (permalink / raw
To: gentoo-user
[-- 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 --]
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-16 12:13 ` Adam Carter
@ 2011-01-16 15:16 ` Peter Humphrey
2011-01-17 1:56 ` Dale
0 siblings, 1 reply; 33+ messages in thread
From: Peter Humphrey @ 2011-01-16 15:16 UTC (permalink / raw
To: gentoo-user
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.
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-16 15:16 ` Peter Humphrey
@ 2011-01-17 1:56 ` Dale
2011-01-17 2:28 ` Dale
2011-01-17 2:50 ` covici
0 siblings, 2 replies; 33+ messages in thread
From: Dale @ 2011-01-17 1:56 UTC (permalink / raw
To: gentoo-user
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
:-) :-)
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
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
1 sibling, 1 reply; 33+ messages in thread
From: Dale @ 2011-01-17 2:28 UTC (permalink / raw
To: gentoo-user
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
:-) :-)
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-17 2:28 ` Dale
@ 2011-01-17 10:40 ` Peter Humphrey
0 siblings, 0 replies; 33+ messages in thread
From: Peter Humphrey @ 2011-01-17 10:40 UTC (permalink / raw
To: gentoo-user
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.
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-17 1:56 ` Dale
2011-01-17 2:28 ` Dale
@ 2011-01-17 2:50 ` covici
2011-01-17 3:05 ` Dale
1 sibling, 1 reply; 33+ messages in thread
From: covici @ 2011-01-17 2:50 UTC (permalink / raw
To: gentoo-user
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
^ permalink raw reply [flat|nested] 33+ messages in thread* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-17 2:50 ` covici
@ 2011-01-17 3:05 ` Dale
2011-01-17 3:28 ` covici
0 siblings, 1 reply; 33+ messages in thread
From: Dale @ 2011-01-17 3:05 UTC (permalink / raw
To: gentoo-user
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
:-) :-)
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-17 3:05 ` Dale
@ 2011-01-17 3:28 ` covici
0 siblings, 0 replies; 33+ messages in thread
From: covici @ 2011-01-17 3:28 UTC (permalink / raw
To: gentoo-user
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
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-16 11:06 ` Peter Humphrey
2011-01-16 11:18 ` Dale
@ 2011-01-16 12:55 ` Neil Bothwick
1 sibling, 0 replies; 33+ messages in thread
From: Neil Bothwick @ 2011-01-16 12:55 UTC (permalink / raw
To: gentoo-user
[-- 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 --]
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-16 9:18 ` Peter Humphrey
2011-01-16 10:48 ` Dale
@ 2011-01-16 12:25 ` covici
2011-01-16 12:44 ` Adam Carter
2011-01-16 12:54 ` Alan McKinnon
2011-01-25 17:05 ` Bill Longman
3 siblings, 1 reply; 33+ messages in thread
From: covici @ 2011-01-16 12:25 UTC (permalink / raw
To: gentoo-user
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
^ permalink raw reply [flat|nested] 33+ messages in thread* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-16 9:18 ` Peter Humphrey
2011-01-16 10:48 ` Dale
2011-01-16 12:25 ` covici
@ 2011-01-16 12:54 ` Alan McKinnon
2011-01-16 15:18 ` Peter Humphrey
2011-01-25 17:05 ` Bill Longman
3 siblings, 1 reply; 33+ messages in thread
From: Alan McKinnon @ 2011-01-16 12:54 UTC (permalink / raw
To: gentoo-user
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
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-16 12:54 ` Alan McKinnon
@ 2011-01-16 15:18 ` Peter Humphrey
2011-01-16 15:32 ` Alan McKinnon
0 siblings, 1 reply; 33+ messages in thread
From: Peter Humphrey @ 2011-01-16 15:18 UTC (permalink / raw
To: gentoo-user
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.
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-16 15:18 ` Peter Humphrey
@ 2011-01-16 15:32 ` Alan McKinnon
2011-01-17 10:42 ` Peter Humphrey
0 siblings, 1 reply; 33+ messages in thread
From: Alan McKinnon @ 2011-01-16 15:32 UTC (permalink / raw
To: gentoo-user
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
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-16 15:32 ` Alan McKinnon
@ 2011-01-17 10:42 ` Peter Humphrey
0 siblings, 0 replies; 33+ messages in thread
From: Peter Humphrey @ 2011-01-17 10:42 UTC (permalink / raw
To: gentoo-user
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.
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-16 9:18 ` Peter Humphrey
` (2 preceding siblings ...)
2011-01-16 12:54 ` Alan McKinnon
@ 2011-01-25 17:05 ` Bill Longman
2011-01-25 17:33 ` Peter Humphrey
3 siblings, 1 reply; 33+ messages in thread
From: Bill Longman @ 2011-01-25 17:05 UTC (permalink / raw
To: gentoo-user
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.
^ permalink raw reply [flat|nested] 33+ messages in thread* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-25 17:05 ` Bill Longman
@ 2011-01-25 17:33 ` Peter Humphrey
2011-01-25 22:43 ` Alan McKinnon
0 siblings, 1 reply; 33+ messages in thread
From: Peter Humphrey @ 2011-01-25 17:33 UTC (permalink / raw
To: gentoo-user
[-- 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 --]
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-25 17:33 ` Peter Humphrey
@ 2011-01-25 22:43 ` Alan McKinnon
2011-01-25 23:47 ` Peter Humphrey
0 siblings, 1 reply; 33+ messages in thread
From: Alan McKinnon @ 2011-01-25 22:43 UTC (permalink / raw
To: gentoo-user
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
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-25 22:43 ` Alan McKinnon
@ 2011-01-25 23:47 ` Peter Humphrey
2011-01-26 0:10 ` Alan McKinnon
0 siblings, 1 reply; 33+ messages in thread
From: Peter Humphrey @ 2011-01-25 23:47 UTC (permalink / raw
To: gentoo-user
[-- 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 --]
^ permalink raw reply [flat|nested] 33+ messages in thread
* Re: [gentoo-user] invalid argument when trying to modprobe nvidia module
2011-01-25 23:47 ` Peter Humphrey
@ 2011-01-26 0:10 ` Alan McKinnon
0 siblings, 0 replies; 33+ messages in thread
From: Alan McKinnon @ 2011-01-26 0:10 UTC (permalink / raw
To: gentoo-user
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
^ permalink raw reply [flat|nested] 33+ messages in thread