initrd / generic kernel --> won't boot. What am I forgetting?
 

Hi all -

OK, I'm embarrassed to be posting this. I've used Slack since 1999, so there's no doubt no excuse.

I upgraded my Thinkpad T60 to 14.0 this morning. Did the whole "use the generic SMP kernel" do:

1) ran '/usr/share/mkinitrd/mkinitrd_command_generator.sh -k 3.2.29-smp | bash' as per UPGRADE.TXT. No errors.
2) pointed /boot/vmlinuz at vmlinuz-generic-smp-3.2.29-smp.
3) pointed /boot/config at config-generic-smp-3.2.29-smp.
4) pointed /boot/System.map at System.map-generic-smp-3.2.29-smp.
5) ran /sbin/lilo

... and when I attempt to reboot into the new system, I get a kernel panic. Am I forgetting a step?

This feels all-too-horribly familiar, and yet I can't figure out what step I might be missing.

Thanks,

Glenn

Edit lilo.conf before the last step?

Nope. I did edit it, pointing the 'image' line at the specific kernel image rather than the 'vmlinuz' link ... no good.

So ...

I just repointed everything to the 'huge smp' config/map/kernel, and it booted fine. Not sure what is going on here.

Is there a real downside to using the 'huge' kernels? If not I guess I'll just stick with it.

/G

You should have added 'initrd = /boot/initrd.gz' then ran lilo again.

Oh ACK!! That's it!!

I wish there were a way to delete posts as "sufficiently embarrassing to the OP to merit deletion."

Haha, yeah unfortunately it's considered "educational" to everyone else when we embarrass ourselves! Lol