newly compiled kernel (2.4.22)caught in reboot cycle

FeO · 11-14-2003, 09:36 AM

I have just done a compile of a new kernel for Slack 2.4.22, copied the bzImage to /boot/vmlinuz. I have LILO.conf pointing to this new kernel.

When I boot the newly compiled kernel, my PC does a BIOS check which says it was OK, then immediately reboots the machine.

I can boot old kernels and WinXP fine.

What gives?

fskmh · 11-14-2003, 09:48 AM

We need more details on that, e.g. your .config file, your lilo.conf, and anything else that you changed.

Azmeen · 11-14-2003, 09:51 AM

Did you run /sbin/lilo after editing your lilo.conf?

iro · 11-14-2003, 10:33 AM

Quote:

Originally posted by Azmeen
Did you run /sbin/lilo after editing your lilo.conf?

I was about to ask the same thing. This is an essential step, it gets lilo to re-read it's configuration and you need to do it when installing and attempting to run a new kernel.

FeO · 11-14-2003, 10:42 AM

yes /sbin/lilo was run.

Azmeen · 11-14-2003, 07:07 PM

The best probable answer that I can give right now (considering I don't know a single thing about your hardware or your kernel configuration), is that during your config process, you might have left out a core feature from your new kernel.

I'd advise you to use your old .config file from the working kernel and do a make oldconfig. Try to at least get a working 2.4.22 kernel first, you can tweak it more once it's working.