Custom kernel: Kernel panic: VFS: Unable to mount root fs on 21:05
Hi,
it seems like similar problems have happened to other people on this list,
but I could not determine a solution for my special case: After making and
installing a custom kernel with kernel-package my box will not boot any
longer.
Here is what I did:
* installed Debian potato with kernel 2.2.18pre21-ide (ABIT BE6-II
motherboard, HPT366 chipset with UDMA)
* upgraded to kernel-image-2.2.19-ide, everything works fine
* got the 2.2.19 kernel-sources with "apt-get install kernel-source-2.2.19"
and the ide-kernel-path with "apt-get install kernel-patch-2.2.19-ide"
* untarred the kernel-sources and copied /boot/config-2.2.19-ide to .config
in top-level kernel-source directory
* in toplevel kernel-source directory
export PATCH_THE_KERNEL=YES
make-kpkg clean
make-kpkg --revision=custom.1.0 kernel_image
Everything seems to work fine - the kernel gets patched and after answering
a few questions the compile-process starts and runs through without any
problems.
The options I had to set manually:
NS87415 chipset support (EXPERIMENTAL) (CONFIG_BLK_DEV_NS87415)=y
VIA82C586 chipset support (EXPERIMENTAL) (CONFIG_BLK_DEV_VIA82C586)=y
CMD646 chipset support (EXPERIMENTAL) (CONFIG_BLK_DEV_CMD646)=y
Here is my first question: Why are there any options which are not set by
the config-file in /boot? If the kernel-image was made with the same sources
and (kernel-source and patch) and the config-file in /boot I shouldn't get
any questions after calling 'make-kpkg kernel_image' (which calls 'make
oldconfig'), right?
* next I installed the new kernel with 'dpkg -i
kernel-image-2.2.19_custom1.0_i386.deb
* now after trying to reboot I get the following messages:
...
loop: registered device at major 7
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xf008-Oxf00f, BIOS settings: hdc:pio, hdd:pio
hda: CD-540E, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq14
hda: ATAPI 40X CD-ROM drive, 128kB Cache
Uniform CD-ROM driver Revision: 3.11
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
md driver0.36.6 MAX_MD_DEV=4, MAX_REAL=8
Partition check:
apm: BIOS version 1.2 Flags 0x07 (Driver verion 1.13)
apm: diabled on user request.
request_module[block-major-33]: Root fs not mounted
VFS: Cannot open root device 21:05
Kernel panic: VFS: Unable to mount root fs on 21:05
It looks as if my Harddisk on the UDMA-controller is not found. The startup
sequence with the debian kernel-image-2.2.19-ide looks something like this:
...
loop: registered device at major 7
Uniform Multi-Platform E-IDE driver Revision: 6.30
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
HPT366: onboard version of chipset, pin1=1 pin2=2
PCI: HPT366: Fixing interrupt 11 pin 2 to ZERO
HPT366: IDE controller on PCI bus 00 dev 98
HPT366: chipset revision 1
HPT366: not 100% native mode: will probe irqs later
ide2: BM-DMA at 0xe000-0xe007, BIOS settings: hde:DMA, hdf:pio
HPT366: IDE controller on PCI bus 00 dev 99
HPT366: chipset revision 1
HPT366: not 100% native mode: will probe irqs later
ide3: BM-DMA at 0xec00-0xec07, BIOS settings: hdg:pio, hdh:pio
hda: CD-540E, ATAPI CDROM drive
hde: ST310212A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide2 at 0xd800-0xd807,0xdc02 on irq 11
hde: ST310212A, 9768MB w/512kB Cache, CHS=19846/16/63, UDMA(33)
hda: ATAPI 40X CD-ROM drive, 128kB Cache
Uniform CD-ROM driver Revision: 3.11
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8
Partition check:
hde: [PTBL] [1245/255/63] hde1 hde2 < hde5 hde6 hde7 hde8 >
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.13)
apm: disabled on user request.
VFS: Mounted root (ext2 filesystem) readonly.
...
Any ideas?
Questions:
* Why do I not get the same kernel as kernel-image-2.2.19-ide? Am I patching
incorrectly?
* Where is the 'Uniform Multi-Platform E-IDE driver' in my custom kernel?
How do I activate it?
Matthias
Reply to: