On Sat, Oct 08, 2005 at 08:30:42PM -0400, Jonathan Brandmeyer wrote: > On Sat, 2005-10-08 at 23:04 +0200, Frederik Schueler wrote: > > Hello, > > > > can you please try building the initrd with initramfs-tools and see if > > that works? > > I manually built an initramfs with: > # mkinitramfs -o /boot/initrd.img-2.6.13-1-686 2.6.13-1-686 && lilo > and rebooted. The system successfully booted with the exception that > udev did not setup the nvidia /dev entries, and X would not start. This > was successfully worked around using the solution presented in > http://lists.debian.org/debian-amd64/2005/09/msg00827.html > > > And if you have the time, do the same check with an initrd > > built using yaird? > > The double-zero version number and package comment "At the moment, yaird > is lightly tested" are not confidence-inspiring. Nonetheless the
Well, it works very well, and booted out of the box > yaird-built pre-init image worked as well, and was smaller than the > initramfs image (1.6 MB vs 5.4 MB). He nice, comparison, i suppose you need to drop the default "MODULES=most" option of initramfs-tools and use MODULES=dep. Can we now please try to default to MODULES=dep ? If we don't do it we will again be saddled with MODULES=most for etch. > > 2.6.13 has no devfs anymore, which breaks initrd in some cases, like > > yours. Maybe we need some way of ensuring that initrd-tools is no more used for 2.6.13+. My suggestion of mkinitrd adding --supported-target-version and --supported-host-version calls would come in handy here, maybe we should implement it. Any comments on this ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
