BandiPat wrote:

On Wednesday 02 June 2004 07:36 am, Basil Chupin wrote:

...

Does anyone know why in SuSE v9.1:

(a) the 3rd and 4th lines of the /var/log/boot.msg log file read-

Symbols match kernel version 2.6.4 No module symbols loaded - kernel modules not loaded

while in v 9.0 the same lines read-

Symbols match kernel version 2.4.21 Loaded 194 symbols from 11 moudules ?

and

(b) why isn't there an Athlon-specific kernel in 9.1?

All my 3 computers have AMD CPUs and when I installed v 9.0 on them, the installation automatically installed the Athlon-specific kernel but with v9.1 there is only the default kernel - which I presume is Intel-oriented.

Cheers.

===========

Basil, I can answer the second, but not the first. The present 2.6.x kernel-default automatically searches out the CPU and adjusts itself to that cpu. I'm not sure if that's built into 2.6 or a SuSE patch, but be assured you are using an Athlon optimized kernel still. That is why there is no need now for two different builds. That's the simple answer, as I'm sure it's a bit more technical than that. :o)

regards, Lee

Thanks for this, but where is this written about and at what point does the kernel so magically changes itself to fit the CPU? I mean, does it do this during the initial installation, in which case it must leave some modules or something lying around for itself, or during each bootup? The way the kernel is configured is stored in /proc/config.gz as I understand it, and if I look in there I find that it is a "M586" kernel and not an Athlon kernel (ie, "MK7"). Cheers. -- I am not young enough to know everything.