Kernel Panic after lilo update
 

Recently, I was dual booting slackware and win2k. To make a long story short, I got entirely fed up with win2k so I formatted the partition it was on, and continued to only use slackware. I then wanted to try to re-add win2k to my dual boot. I installed win2k and then booted from the slackware CD to update lilo. The first time I did this, lilo didn't change. I did something wrong somewhere, because I had the old lilo menu (that did not include win2k). I tried to update it again, this time manually editing lilo.conf. I installed lilo to the MBR and it seemed to work because next time I booted up, I was given a choice between win2k and slackware.


win2k boots fine from lilo, but when I try to boot slackware, it doesn't completely boot. I immediatley noticed that I wasn't using framebuffer support anymore. The text was large and ugly. Then I get to a kernel panic. The specific message I get is, "Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (3,2)"

Has anyone seen something like this before? How can I correct this error?

Did you remember to run /sbin/lilo (as root) after changing your /etc/lilo.conf ?

Samac

Go to the sourcecode directory of the kernel you are using and do a make menuconfig. Make sure that the filesystem where the kernel modules are stored is builtin, NOT a module. The filesystem where the modules are kept must be builtin or the kernel can't load them.

removed incorrect answer

I'm assuming I must use the install CD to do the make menuconfig. Should I chroot into the environment via "chroot /mnt/slackware /bin/bash" ?