LinuxQuestions.org - Slack 10.2 with kernel panic after compile of 2.6.18.1

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Slack 10.2 with kernel panic after compile of 2.6.18.1 (https://www.linuxquestions.org/questions/slackware-14/slack-10-2-with-kernel-panic-after-compile-of-2-6-18-1-a-501996/)

Slack 10.2 with kernel panic after compile of 2.6.18.1

ok im running slackware 10.2 on a toshiba laptop and am compiling the new 2.6.18.1 kernel. i get

Quote:

Kernel Panic - not syncing : VFS: Unable to mount Root FS on unknown-block(3,2)

heres my lilo.conf

Quote:

# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.15.6
root = /dev/hda2
label = Back|Track
read-write
image = /boot/vmlinuz
root = /dev/hda2
label = new
read-write
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/hda3
label = Windoze
table = /dev/hda
# Windows bootable partition config ends

(learned to leave my self an out)

heres my config file (portions of it any way)

Quote:

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# File systems
#
CONFIG_REISERFS_FS=y

and my fstab

Quote:

/dev/hda3 / auto defaults 1 1
tmpfs / tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
/dev/hda1 swap swap swap 0 0 # AutoUpdate
/dev/hda2 /mnt/hda2 reiserfs auto,users,suid,dev,exec 0 0 # AutoUpdate
/dev/hda3 /mnt/hda3 ntfs auto,users,suid,dev,exec 0 0 # AutoUpdate
/dev/hdc /mnt/hdc_cdrom iso9660 noauto,users,exec 0 0 # AutoUpdate

ive been googleing my ass off and as you can see compiled in support for reiserfs. any help would be greatly appriciated.

EDIT: after my newest compile failed "no file system could mount root tried: reiserfs vfat iso9660 ntfs. Kernel Panic..." i booted into my working kernel and got "reiserfs: hda2 found reiserfs version "3.6"" that may or may not help.

Welcome to LQ.

I think you are missing the boot parameter. Just add the following line to the top of lilo.conf

Code:

boot = /dev/hda

Note that you need to rerun the lilo program to make your changes take effect

Code:

/sbin/lilo

heres my entire lilo.conf

Quote:

# Start LILO global section
boot = /dev/hda
#compact # faster, but won't work on all systems.
prompt
timeout = 300
# VESA framebuffer console @ 1024x768x256
vga = 773
# Ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.15.6
root = /dev/hda2
label = Back|Track
read-write
image = /boot/vmlinuz
root = /dev/hda2
label = new
read-write
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/hda3
label = Windoze
table = /dev/hda
# Windows bootable partition config ends

i edited it slightly for my first post.

Hi,

I know you said that you compiled filesystem support in your new kernel, right.

What about for your controller?

To get the system going for now, read the /boot/README.initrd and create a initrd. Modify your lilo.conf stanza for the new kernel as per the example.

edit: BTW, don't forget to run lilo. <end edit>

well in a move that worked some what (i needed to vpn in to my work which is why im recompiling my kernel) i went out and downloaded the 2.6.16.32 source and the 2.6.18.1 md5 hash. the 16.32 kernel compiled and had no problems the md5 hash for the 2.6.18.1 tarbell did not match what i got so my download was screwed up. thanks for all your help and this has taught me a lesson. always check the hash. now i just have to get my drivers compiled into my new kernel.