Did you enable the "Symmetric multi-processing support" in Processor type and features? I got a very similiar error when I tried to toggle this off._________________Do you want your posessions identified? [ynq] (n)

The last time I tried to use the Gentoo sources it had similar issues if you tried to use it without preemption. So I'm working off the vanilla tree for the moment.

Bryn.

It works perfectly if you add SMP support (and presumably preemption, I've never tried it without), neither of which should be harmful in any way. Preemption, if anything, helps and the SMP support just complains about finding only one CPU and goes about its business. Why use the vanilla sources?_________________The greatest deeds are still undone, the greatest songs are still unsung...

After rebooting with the new kernel I get a load of failed dependancies. Any ideas how this can be fixed?

Search the forum for "unresolved symbols" or "kernel compile error" - you'll find some tips. If the problem persist with special modules, post your error messages here. Also Google around for these error messages, in many mailing list there's a work-around posted._________________Do you want your posessions identified? [ynq] (n)

At first I tried the gentoo-sources ... the kernel compiled, even modules ... booting no problem, everything worked flowlessly. But I got a lot of kernel messages spammed in my console. Preemptive exit kernel msgs or smth. I though, maybe there was some debugging option for preemptive, but I couldn't find it anyhow ... so I downloaded the 2.4.18 sources from kernel.org & patched it with the preemptive patch. Compiled it & everything's working great... duno what the prob was / what I did wrong ...

It happened to me as well, and only occurs if you first compile the kernel with SMP support and then later recompile it without (with the same sources) If you do a make mrproper before proceeding, it will go fine.

I wonder why SMP is selected by default anyways.. gives nothing but trouble

I wonder why SMP is selected by default anyways.. gives nothing but trouble

Full ACK - I was desperately trying to get my nvidia drivers to work but couldn't. The standard answer at #nvidia is already: "So you're using a gentoo kernel? Get yourself a 2.418 kernel directly from kernel.org and it will work!". I spend about 2 weeks on this issue. Finally I tracked this down as a result of SMP enabled in my kernel.

I also suggest to disable SMP by default._________________Do you want your posessions identified? [ynq] (n)

I started with the 2.4.18 drivers and after I got this working, I emerged the latest gentoo-sources and now I'm running my nvidia drivers happily in the 2.4.19-rc5 release._________________Do you want your posessions identified? [ynq] (n)

It happened to me as well, and only occurs if you first compile the kernel with SMP support and then later recompile it without (with the same sources) If you do a make mrproper before proceeding, it will go fine.

I wonder why SMP is selected by default anyways.. gives nothing but trouble

I had the same problem and it was my first compile of the kernel. (I also did a "make mrproper" before attempting to compile.) I was trying to compile with SMP turned off and the first APIC option after the SMP option turned on. (I am not at the Linux box so I cannot specifically quote the options.)

I solved the problem by turning on the IOAPIC option (second option after SMP in my menuconfig).

(I next failed because I had turned off quota support but chosen quota support for XFS. - I need to be consistent in my choices. (*shrug*))