1 |
Peter Humphrey wrote: |
2 |
> On Sunday 16 January 2011 03:25:41 covici@××××××××××.com wrote: |
3 |
> |
4 |
>> Adam Carter<adamcarter3@×××××.com> wrote: |
5 |
>> |
6 |
>>> Did you remember to repoint the /usr/src/linux link? IIRC the |
7 |
>>> module is built to suit whatever kernel that is pointing to. If |
8 |
>>> its not set correctly you'll need to re-emerge nvidia-drivers. |
9 |
>>> |
10 |
>> linux is pointing correctly and it was after I emerged the |
11 |
>> nvidia-drivers that I got the invalid argument. |
12 |
>> |
13 |
> You can't emerge nvidia-drivers if /usr/src/linux points to a kernel |
14 |
> version other than the currently running one - it complains it can't find |
15 |
> a valid kernel config. This means that, after emerging a new kernel |
16 |
> version, it's necessary to reboot with the new kernel (and fail to start |
17 |
> X) before it's possible to remerge nvidia-drivers to suit the new kernel |
18 |
> - you can't do it in advance. |
19 |
> |
20 |
> On this ~amd64 multilib box, 260.19.29 has run trouble-free with gentoo- |
21 |
> sources 2.6.36-r5, 2.6.36-r6 and 2.6.37. Perhaps your -multilib USE flag |
22 |
> is causing trouble. |
23 |
> |
24 |
> |
25 |
|
26 |
In the past when I do a kernel upgrade, I have linked to the new kernel, |
27 |
emerged nvidia drivers then rebooted to the new kernel. It worked fine |
28 |
for me. I haven't done that in a while since I just built a new rig but |
29 |
I have done that in the past many times. |
30 |
|
31 |
Is this something new? |
32 |
|
33 |
Dale |
34 |
|
35 |
:-) :-) |