On Sun, Apr 18, 2004 at 10:34:42AM -0700, Jeff Coppock wrote: > I've been experimenting with the new NetInst CD in VMWare, since I > don't have a scratch system. The installer defaults to Grub for a boot > loader and also defaults to installing into MBR. The setup also uses an > initrd kernel. > > This all fine and good, but I've been trying to compile a non-initrd > kernel (2.4.25 and 2.4.26), but they won't boot. I've resorted to > building initrd kernels and I had trouble with those until I learned > that there is a patch for the kernel.org sources for cramfs, which is > included in the Debian kernel source packages. > > I've been using non-initrd kernels for a long time and just want to > understand why one won't boot in this new environment. Does anyone know > what the issue might be with this? >
I don't think the boot problems you are running into are due to initrd. I am using a non-initrd kernel (2.4.25 and 2.4.26) on a system installed with the new installer with no troubles. Are you sure you compiled the root file system into the kernel and not as a module? anything else that you may need at boot that is compiled as a module? > Also, why is the bootloader default changing from Lilo to Grub? > No idea. The developers liked it, its supposed to be the next thing ... ;-) The only thing better I see about it is that you don't need to reinstall it when you make changes to the entrees, other then that it looks more complicated to me. > thanks, > jc > > -- > Jeff Coppock Systems Engineer > Diggin' Debian Admin and User > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > +++++++++++++++++++++++++++++++++++++++++++ > This Mail Was Scanned By Mail-seCure System > at the Tel-Aviv University CC. >
