On Mon, 8 Jan 2007, Tilman Schmidt wrote: > Jonas Svensson schrieb: > > On Mon, 8 Jan 2007, Tilman Schmidt wrote: > > > >> Jonas Svensson schrieb: > >> [...] > >> > All results in the same problem: the booting stops about when grub is > >> > finished and the kernel should continue. I get the > >> > message about loading initrd but not the line of "Uncompressing > >> > Linux... Ok, booting the kernel". Instead I get a blank screen with a > >> > flashing cursor at top left. Thats all, nothing more happens. Any > >> > suggestions on what could be wrong or what I should do? > >> > >> Did you build a new initrd to go with your new kernel? > > > > I beleive make install does that in CentOS. There were a new initrd > > installed and it was not identical to the one supplied by CentOS. > > That's surprising. On SuSE I always have to build it separately > with mkinitrd, and the kernel makefiles are the same, after all. > Anyway, your symptoms definitely look like a bad initrd, so you > may want to have a closer look in that area. Perhaps build a > kernel you can boot without initrd for testing, ie. with the > drivers for the root disk and filesystem built in.
I have done a kernel without support for modules and what I beleive is sane settings regarding drivers. I installed it and removed the initrd from grub.config but still got the same error. I will try it again, maybe I missed something. I will also try to read more on initrd and see if I am wrong to assume that make install does it for me. Thanks for trying to help. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
