Why does Kernel 220.127.116.11 + Slackware 10.2 = Kernel Panic?
Hello. I recently had to reinstall my entire Slackware Linux OS because I did something stupid that screwed it up. After reinstalling I went to kernel.org to get the latest kernel and got 18.104.22.168. I went through and configured it with "make xconfig" and selected what I thought to be all the appropriate stuff--I'd had no trouble doing that with previous kernels, 22.214.171.124 being the most recent I've used before 126.96.36.199.
I did all the usual stuff such as "make bzImage", copying that bzimage to my boot directory as vmlinuz-188.8.131.52, "make modules", "make modules_install", copying the system.map and .config into /boot as system.map-184.108.40.206 and config-220.127.116.11 respectively, and all the symlink stuff. I didn't see any need to modify lilo.conf based on the circumstances--It was pointing to vmlinuz, which was a symlink to vmlinuz-ide-2.4.31, and I replaced that symlink with one pointing to the 2.6 version of vmlinuz. Seemed like I did everything right.
So I restart after I do all that, select Slackware from the NTLDR boot menu, and Lilo starts as usual. Not long after that the kernel says to please properly specify "root=" or something like that, says something along the lines of no VFS linking, and then kernel panic happens and everything freezes. I'm forced to do a hard shutdown. I figured I'd just checked a wrong option in Xconfig, but I didn't have anyway to fix that now, so I was forced to reinstall Slackware again.
This time, before compiling kernel 18.104.22.168, I used "dd" to dump my current mbr using the 2.4.31 kernel to a file, "slack.old" and stored that file on a FAT32 partition. After compiling and going into /sbin/lilo to have it register the new settings, I dumped the new mbr onto that same FAT32 partition as "slack.mbr," the file which NTLDR was told to boot if I selected Slackware. I rebooted and selected Slackware, and the same thing happened--Kernel panic. After another hard shutdown I booted into another OS and copied the "slack.mbr" file into "slack.bad", deleted slack.mbr and copied "slack.old" into slack.mbr. That allowed me to boot Slack again under the 2.4 kernel, but I'd really like to use the 2.6 kernel.
What exactly should I do to stop kernel panic from happening? Does it have to do with what I select in the kernel compilation? This is really strange because it hasn't happened to me when using 2.6 kernels older than 22.214.171.124.