mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bernhard Schauer <linux-kernel-list@acousta.at>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: INITRAMFS: junk in compressed archive
Date: Tue, 29 Mar 2005 08:20:51 +0200	[thread overview]
Message-ID: <1112077252.6427.21.camel@FC3-bernhard-1.acousta.local> (raw)
In-Reply-To: <d24rad$378$1@terminus.zytor.com>

> Kernel + compressed initramfs + uncompressed initramfs must fit in memory at
> the same time.

But that could not be the problem:
 
          initramfs   packed:  6,4 MByte
                    unpacked: 14,7 MByte
          kernel    unpacked:  2,2 MByte
         --------------------------------
                              23,3 MByte

128 MByte RAM on the PC (?) - the kernel tells that the RAM is
available.

An other interesting thing is that the "checking if image is
initramfs... it isn't (junk in compressed archive)" message disappeared
after using smaller initramfs (using the same method to compress
the .cpio.gz file!). 


Maybe my boot procedure is a problem(?):
I've to remote-boot DOS via RPL, load Novell Client for DOS, copy Linux
+ initramfs to ramdisk and call loadlin (version 1.6c) to start Linux.

Could there something remain in memory? The size of memory available to
the PC should still be enough to hold both systems and also the DOS -
Ramdisk in memory. 


Other Question: is (could) DOS-Ramdisk (be) available to Kernel? Maybe
as MTD?

regards

Bernhard Schauer


      parent reply	other threads:[~2005-03-29  7:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-24 15:59 Bernhard Schauer
2005-03-25 14:49 ` Bernhard Schauer
2005-03-26 16:06   ` Andreas Jellinghaus
2005-03-26 23:30   ` H. Peter Anvin
2005-03-27  8:31     ` Jan Engelhardt
2005-03-29  6:20     ` Bernhard Schauer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1112077252.6427.21.camel@FC3-bernhard-1.acousta.local \
    --to=linux-kernel-list@acousta.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schauer@acousta.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®