On Tue, Sep 23, 2008 at 12:10:54AM +0300, Andrei Popescu wrote:
> On Mon, 22 Sep 2008 16:34:21 -0400 Thomas H. George wrote:
>
> > With BUSYBOX=n the initrd.img file size is reduced to 6683876 but
> > bootup still fails.
>
> Maybe yaird can help. Install the yaird package and then add
>
>
On Mon, 22 Sep 2008 16:34:21 -0400 Thomas H. George wrote:
> With BUSYBOX=n the initrd.img file size is reduced to 6683876 but
> bootup still fails.
Maybe yaird can help. Install the yaird package and then add
ramdisk=mkinitrd.yaird mkinitramfs
to /etc/kernel-img.conf (try to use yaird,
On 09/22/08 15:34, Thomas H. George wrote:
On Mon, Sep 22, 2008 at 10:57:49PM +0300, Andrei Popescu wrote:
On Mon, 22 Sep 2008 14:08:24 -0400 Thomas H. George wrote:
Last month when lilo could not boot a stock 2.6.26-1-amd64 debian
system it was pointed out to me that the initrd.img was too bi
On Mon, Sep 22, 2008 at 10:57:49PM +0300, Andrei Popescu wrote:
> On Mon, 22 Sep 2008 14:08:24 -0400 Thomas H. George wrote:
>
> > Last month when lilo could not boot a stock 2.6.26-1-amd64 debian
> > system it was pointed out to me that the initrd.img was too big and
> > that the solution was to
On Mon, 22 Sep 2008 14:08:24 -0400 Thomas H. George wrote:
> Last month when lilo could not boot a stock 2.6.26-1-amd64 debian
> system it was pointed out to me that the initrd.img was too big and
> that the solution was to edit /etc/initramfs-tools/initramfs.conf and
> change MODULES=most to MODU
Last month when lilo could not boot a stock 2.6.26-1-amd64 debian system
it was pointed out to me that the initrd.img was too big and that the
solution was to edit /etc/initramfs-tools/initramfs.conf and change
MODULES=most to MODULES=dep. This indeed reduced the size of the
initrd.img from about
6 matches
Mail list logo
