On Thu, Aug 30, 2001 at 05:02:58PM -0400, Wayne Topa wrote: | dman([EMAIL PROTECTED]) is reported to have said: | > On Thu, Aug 30, 2001 at 01:10:58PM -0400, Wayne Topa wrote: | > ... | > | > | I had a simular problem when I enabled the Ramdisk and cramfs when I | > | went to 2.4.9. I thought I would see what all the initrd stuff was | > | about. So I de-selected all the initrd items and compiled without it. | > | BTW I compile the old way, not with make kpkg, and I get the kernels | > | from kernel.org. Anyway I didn't get those errors anymore. | > | > If you enable the initrd stuff, then you need to have an initrd and | > use it when booting. There is an argument to make-kpkg that will | > create an initrd as well as the kernel image (I have no idea wrt | > standard builds). I use grub as my bootloader and need to have an | > "initrd=/boot/initrd" (or whatever it is named) in my kernel arguments | > and then "initrd /boot/initrd" as the last command (instead of | > "boot"). | | I knew all that before I looked into trying out initrd. I had read | all the posts, and docs, before I ever started. I never got to the | booting stage as the kernel compile gave me 'cramfs' errors. Just | like the original poster was getting. That was a few weeks ago and I | did not keep notes so I think that was the only compile error I | received. | | Or are you saying that the Cramfs errors would have gone away if I had | used make kpkg? I don't think so .....
I didn't even see the original post, and know nothing of errors compiling the kernel. I had no errors whatsoever with my 2.4.8 compiles (using make-kpkg, didn't try the "traditional" method). I just a a mention of trouble booting with an initrd so I thought I'd add my $0.02 :-). -D
