1 |
On Thu, 2005-11-24 at 14:01 +0000, Neil Bothwick wrote: |
2 |
> On Thu, 24 Nov 2005 13:48:00 +0100, Jules Colding wrote: |
3 |
> |
4 |
> > nvidia-kernel fails to load in 2.6.14-gentoo-r2. "/var/log/messages" |
5 |
> > below. |
6 |
> |
7 |
> > ############### emerge --info ################# |
8 |
> > omc-2 ~ # emerge --info |
9 |
> > Portage 2.0.51.22-r3 (default-linux/amd64/2005.1, gcc-3.4.4, |
10 |
> > glibc-2.3.5-r2, 2.6.13-gentoo-r3 x86_64) |
11 |
> > ================================================================= |
12 |
> > System uname: 2.6.13-gentoo-r3 x86_64 AMD Opteron(tm) Processor 252 |
13 |
> |
14 |
> You're not running 2.6.14-gentoo-r2. |
15 |
|
16 |
I was. I rebooted into 2.6.13 to ease cut'n paste. |
17 |
|
18 |
But I double-checked anyway and nvidia still has unknown symbols in the |
19 |
latest kernel. I have attached the emerge output from the nvidia build |
20 |
and the emerge info from that session too. |
21 |
|
22 |
Best regards, |
23 |
jules |
24 |
|
25 |
|
26 |
> if /usr/src/linux is symlinked to |
27 |
> anything but the running kernel, you may experience problems. that's why |
28 |
> I always reboot into a new kernel before re-emerging nvidia-kernel, |
29 |
> which works fine with 2.6.14-gentoo-r2 here. |
30 |
> |
31 |
> If you don't want the hassle of logging into a console, emerging |
32 |
> nvidia-kernel and starting X when booting into a new kernel, put this |
33 |
> in /etc/conf.d/local.start, on a single line |
34 |
> |
35 |
> lsmod | grep --quiet nvidia || (AUTOCLEAN="no" FEATURES="-sandbox" emerge --oneshot nvidia-kernel && modprobe -v nvidia && /etc/init.d/xdm stop zap start) |
36 |
> |
37 |
> |