kernel 2.6.18: booting without initrd
I would like GRUB to boot my kernel directly without loading an initrd image.
So, I've recompiled my kernel with direct (not through a module) support for ext3 filesystems and the piix drivers to my Intel ICH7 SATA hard drive. But, now I get the following error message when booting without in initrd image:
I'm sure PIIX is the correct driver to my hard disk, as shown by:
Any idea what I have missed? Which module(s) shoud I add the to the kernel image if I am to boot without initrd?
Thanks for your answers.
Check what drivers your initrd loads and build them in, it could be the partition layout it does not understand.
Thanks for your answer.
I've gone back top menuconfig, and it appears that every type of partition that is supported by my kernel is supported natively and not as part as a module.
I have finally managed to uncompress and browse my initrd image and I must say I'm a bit confused... I located a "drivers" subdirectory within the modules. It has dozens of drivers as shown by ls -R:
I was a bit confused this morning, I'm still a bit confused, but I think I have found a way to tackle it. I'm going to dichotomitically (sp?) remove modules from the initrd image until I isolate the module(s) necessary for the boot of my computer.
I'll let you know how this goes.
EDIT: I've removed all kernel modules from my initramfs image. Yet, my kernel still boots.
initramfs image is supposed to be disposable. It"s only there to load some kernel modules which you can compile into the kernel just fine.
My kernel can't boot without the initramfs image.
I remove all kernel modules from the initramfs image.
My kernel still boots with this modified image.
This means things are not what they're supposed to be.
The most puzzling in all this is that my kernel is not all that recent. It's the debian etch kernel...
If someone can explain...
|All times are GMT -5. The time now is 07:28 AM.|