On 4/3/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I thought that there were architecture specific reasons for using > > initrd. Hmm, didn´t know that. But my iBook G4 runs sid & etch > > without ramdisk-support. Do you have additional Hardware or > > booting from USB or FireWire? > > I'm not that aware of it, but when I recompile a 2.6.15 (IIRC) kernel, > without the --initrd option, I've got some kernel panic, which > disappeared after I've been told to add the --initrd option. BTW, > I've no particular USB or FW stuff, just a (last model) iBook/G4. > > According to a more-or-less FAQ I've just read: "his means it has > to load any modules that are required to "see" things like IDE, > SCSI, or SATA drive" (speaking of the initrd). > If we compile these drivers into the kernel, not as modules, we don't need --initrd option.
Regards, Bin > Cheers, > > -- > Cyril Brulebois > > _______________________________________________ > Bcm43xx-dev mailing list > [email protected] > http://lists.berlios.de/mailman/listinfo/bcm43xx-dev > _______________________________________________ Bcm43xx-dev mailing list [email protected] http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
