I'm trying to get the kernel 2.6.6 booting on my machine. Following are my bootup mesages :

Device mapper:4.1.0-ioctl (2003-12-120) initialized: dm@uk.sistina.com
EISA: Probing bus 0 at EISA
NET: Registered protocol family 2
IP: routing cache hash table of 2048 buckets, 15Kbytes
TCP: hash tables configured (established 16384 bind 32768)
Net: Registered protocol family 1
NET: Registered protocol family 8
NET: Registered protocol family 20
Md: Autodetecting RAID arrays.
Md: autorun …
Md: … autorun DONE.
VFS: Cannot open root device “3a00” or unknown-block(58,0)
Please append a correct “root= “ boot option
Kernel panic: VFS: Unable to mount fs or unknown-block(58,0)

I checked my lilo configuration and I do not find anything wrong in it.

menu-scheme = Wb:kw:Wb:Wb
default = Linux
timeout = 80
message = /boot/message
lba32
change-rules
reset
read-only
prompt
boot = /dev/hda

image = /boot/vmlinuz
###Don't change this comment - YaST2 identifier: Original name: linux###
label = Linux
initrd = /boot/initrd
root = /dev/vg00/lvol1
append = "splash=silent desktop"
vga = 0x314

image = /boot/bzImage-2-6-6
label = Linux-2.6.6
root = /dev/vg00/lvol1
append = "ide=nodma apm=off acpi=off vga=normal nosmp noapic maxcpus=0 3"

image = /boot/vmlinuz
###Don't change this comment - YaST2 identifier: Original name: failsafe###
label = Failsafe
initrd = /boot/initrd
root = /dev/vg00/lvol1
append = "ide=nodma apm=off acpi=off vga=normal nosmp noapic maxcpus=0 3"

I do not use a inird with the new kernel since the reiserfs and LVM are all built in. And for the root device I used the same as for the 2.4.21 kernel could this possibly be wrong? If so why?
Or is there something I am overlooking in the configuration of the kernel?

I have support for IDE drives included:

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

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_IDEDISK_STROKE=y
CONFIG_BLK_DEV_IDECS=m
CONFIG_BLK_DEV_IDECD=m
CONFIG_BLK_DEV_IDETAPE=m
CONFIG_BLK_DEV_IDEFLOPPY=y
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_IDE_TASK_IOCTL is not set

Anybody has any ideas aff what could be wrong ? What am I overlooking or doing wrong?

did you complile support for reiserfs/ext3 or whatever your root file system is? it's an easy thing to overlook if you don't think about it.

Yes reiserfs is included in the kernel, So is the Raid/LVM support. My current filesystem is Reiferfs in combination with LVM.

Here are the entries from the .config file :

#
# File systems
#
CONFIG_EXT2_FS=m
CONFIG_EXT2_FS_XATTR=y
# CONFIG_EXT2_FS_POSIX_ACL is not set
# CONFIG_EXT2_FS_SECURITY is not set

CONFIG_EXT3_FS=y

# CONFIG_EXT3_FS_XATTR is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y

CONFIG_REISERFS_FS=y

# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_JFS_FS=m
CONFIG_JFS_POSIX_ACL=y
# CONFIG_JFS_DEBUG is not set
CONFIG_JFS_STATISTICS=y
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=m
# CONFIG_XFS_RT is not set
# CONFIG_XFS_QUOTA is not set
# CONFIG_XFS_SECURITY is not set
CONFIG_XFS_POSIX_ACL=y
CONFIG_MINIX_FS=y
CONFIG_ROMFS_FS=m
CONFIG_QUOTA=y
CONFIG_QFMT_V1=m
CONFIG_QFMT_V2=m
CONFIG_QUOTACTL=y
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=m

# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=y
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=y
CONFIG_MD_RAID5=y
CONFIG_MD_RAID6=y
CONFIG_MD_MULTIPATH=y
CONFIG_BLK_DEV_DM=y
CONFIG_DM_CRYPT=m

Recompile and pay attention to ext2 and ext3 and other filesystems you might be using. Include those and you should be fine.

But I only use reiserfs and this is already build into the kernel. I already tried to buiil the kernel with all filesystems build in but is failed to boot at the exact same way.

Hi,
Have you already found solution for your kernel panic.
I have the exact same error with the 2.6.6 kernel, but I think I have inbuilt all important drivers into the kernel.(ide,reisefs,chipset)

I had the same problem. Went with the original kernel and went back and stripped it down.

Sorry, but what do you mean with that?
Does it work? Where was the reason?
can send me your .config, plz.

Greetz
Bernhard

I can. Just post an email.

Hi,

bernhard@baase.de

thx

Bernhard

has anyone got a Solution to it ..im having the same Proob

to mehargags: The solution is rather easy as I figured it out. Just change your grub.conf file:

kernel /vmlinuz-2.6.6.xxxx ro root=/dev/hdax

(replace hdax with your / partition)

This way you tell grub on which partition root is instead of the root=LABEL=/ which sometimes doesn't work.)

This little adjustment worked for me. Hope it works for you too.

I am a chinese, maybe you understand what's i say
first change the directory the kernel source, for example:
#cd linux-2.6.6
#make menuconfig
select "Dvice Drivers->ATA/ATAPI/MFM/RLL support->"
you hat to select this "ATA/ATAPI/MFM/RLL support"
#make
#make modules
#make modules_instal
#make install
configure the boot manager
#reboot
Good lucky!
If not succes! please mail to youxia_2008@yahoo.com.cn
Remember send me the .config file to me!

Hi,
I guess you also have to create new initrd and add row into you lilo.conf:
image = /boot/bzImage-2-6-6
label = Linux-2.6.6
initrd=/boot/initrd-2.6.6 #/sbin/mkinitrd /boot/initrd-2.6.6 2.6.6
root = /dev/vg00/lvol1
append = "ide=nodma apm=off acpi=off vga=normal nosmp noapic maxcpus=0 3"

Did your problem get resolved ?

if not try this.
I had the same issue when I went for 2.6.6 for the first time. same message as you get.

It turned out that my bzImage didn't have in-built driver for "BusLogic" (my dell latitude's SCSI disk) and it wasn't able to read the boot point I gave. I added generic SCSI support as in-built and BANG !!!

Good Luck