A couple days ago I did an emerge -avuD world, and now I can't get X
to start. After doing some debugging I noticed that the nvidia kernel
module wasn't loading. I don't have access to the machine at the
moment, but the error was something like "incorrect module format".
I made sure my /usr/src/linux symlink was correct, re-emerged
nvidia-kernel, and got the same error when trying to modprobe it. I
also tried reverting back to the older driver, but got the same error.
Any ideas why this might be happening? I haven't recompiled my kernel
in a few weeks, so it shouldn't be that.
Relevant info I can remember off the top of my head:
2.6.8-r1
ACCEPT_KEYWORDS='~x86'
Intel P4 2.2 Ghz Dell Laptop
Geforce 4 (don't remember exact model)
I tried doing an esync and emerge -avuD world again yesterday, but was
getting a block on callgrind (wanted by gdb I think) so I didn't end
up updating anything.
Thanks!
-Andy
--
gentoo-user@gentoo.org mailing list
to start. After doing some debugging I noticed that the nvidia kernel
module wasn't loading. I don't have access to the machine at the
moment, but the error was something like "incorrect module format".
I made sure my /usr/src/linux symlink was correct, re-emerged
nvidia-kernel, and got the same error when trying to modprobe it. I
also tried reverting back to the older driver, but got the same error.
Any ideas why this might be happening? I haven't recompiled my kernel
in a few weeks, so it shouldn't be that.
Relevant info I can remember off the top of my head:
2.6.8-r1
ACCEPT_KEYWORDS='~x86'
Intel P4 2.2 Ghz Dell Laptop
Geforce 4 (don't remember exact model)
I tried doing an esync and emerge -avuD world again yesterday, but was
getting a block on callgrind (wanted by gdb I think) so I didn't end
up updating anything.
Thanks!
-Andy
--
gentoo-user@gentoo.org mailing list