LinuxQuestions.org - Unable to boot kernel

- Debian (https://www.linuxquestions.org/questions/debian-26/)

- - Unable to boot kernel (https://www.linuxquestions.org/questions/debian-26/unable-to-boot-kernel-463771/)

Unable to boot kernel

I compiled my own kernel following these instructions: http://www.debian.org/doc/FAQ/ch-kernel.en.html When I try to reboot in my new kernel I get this error message:

"Cannot open root device"

I checked my menu.lst everything appears to be fine:

Code:

title                Debian GNU/Linux, kernel 2.6.15-1-486

root                (hd0,1)

kernel                /boot/vmlinuz-2.6.15-1-486 root=/dev/hda2 ro 

initrd                /boot/initrd.img-2.6.15-1-486

savedefault

boot



title                Debian GNU/Linux, kernel 2.6.15-1-486 (single-user mode)

root                (hd0,1)

kernel                /boot/vmlinuz-2.6.15-1-486 root=/dev/hda2 ro single

initrd                /boot/initrd.img-2.6.15-1-486

savedefault

boot



title                Debian GNU/Linux, kernel 2.6.15

root                (hd0,1)

kernel                /boot/vmlinuz-2.6.15 root=/dev/hda2 ro 

savedefault

boot



title                Debian GNU/Linux, kernel 2.6.15 (single-user mode)

root                (hd0,1)

kernel                /boot/vmlinuz-2.6.15 root=/dev/hda2 ro single

savedefault

boot

The 486 kernel boots fine, my own kernel doesn't. The only difference is the inird file which isn't mentioned in de Debian manual :confused: What can i do?

Did you remember to compile in your chipset and root filesystem type (for example mine is piix and ext3)? If you don't use initrd, they have to be compiled in as "Y" instead of as "M".

I think the chipset is the problem! Where can I set this?

When you do make gconfig (or xconfig) to configure your kernel, it is buried under "Device Drivers". If you have ATA (i.e. IDE disks, not SATA or SCSI) you'll want to go under the ATA/ATAPI/IDE section and then into "PCI IDE Chipset Support" and then to "Generic PCI bus-master DMA support."

At leat that's how it is on the 2.6.16.19 kernel that I compiled last month.

You'll just have to poke around a bit under device drivers. Make sure you know what your chipset is.