On Thursday 13 April 2006 22:35, Markus Ingvarsson wrote: > Does this mean the initrd is corrupt? Possibly because of endian > differences between the sparc and the x86 host, or special demands on > the initrd format, which are not met when using cpio and gzip manually.
Sounds possible. > The interesting question is really, where is the initrd generated by > d-i? Where would it be a good idea to try making the needed > modifications? It wouldn't be enough just adding a register-module > command to the hw-detect script, would it? You can use the resue option of the installer to get into a chroot of the installed system. Then mount /proc and /sys (and other partitions if needed), add esp to /etc/initramfs-tools/modules, and regenerate the initrd using 'update-initramfs -u' (you may need the -t and -k options too; see manpage). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
