Hi!

I'm having trouble building a new kernel (that boots) on my servermatrix server.

The preinstalled kernel, according to uname -r, is 2.4.19-ac4.

But all the files in /boot say 2.4.18-bf2.4.

So I was wondering what's the nature of this discrepancy. I would suspect it is the /boot files that are misnamed, and that uname -r would be telling the truth.

However, I downloaded stable kernel source package for 2.4.19, and used the config file in /boot (config-2.4.18-bf2.4)... and built a new 2.4.19 kernel based on that config, and the result wouldn't boot.

The boot log showed the following errors/warnings that were not present in the preinstalled kernel's boot logs:





I don't know what the "unexpected IO-APIC" means, but the "socket drivers loaded" meant I had to ask for the server to be rebooted, as I could no longer talk to it over ssh.

The strange naming discrepancy between uname -r and the files in /boot, and the resultant problems trying to build a kernel using the config-2.4.18-bf2.4 in /boot, makes me wonder if that's not really the correct config file for my kernel?

Anyone have any thoughts or ideas? I definitly would like to build a custom kernel, as I want to use the grsecurity kernel patch. For starters, I'd be happy to be able to build an unpached kernel that actually boots!

Thanks for any help,

Regards,

Bill / Tasty Spleen