From: curt brune <curt@acm.org>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: initrd, ramdisk problems
Date: Wed, 25 Sep 2002 08:12:13 -0700 [thread overview]
Message-ID: <20020925151213.GA19241@lenin.net> (raw)
In-Reply-To: <20020922032631.GA30804@lenin.net>
I managed to get this working -- what I did differently was:
* changed kernel version from 2.4.18 to 2.4.4 (from the ELDK cvs
repository)
And that was it. It now works. The ramdisk decompresses without
errors and the systems boots fine. Happy day.
I noticed that the directory layout for the kernel changed somewhat
from 2.4.4 to 2.4.18 -- In 2.4.4 I put ramdisk.image.gz in
linux/arch/ppc/mbxboot, while in 2.4.18 the ramdisk goes in
linux/arch/ppc/boot/images . Plus in 2.4.18 there are a lot of
directories in linux/arch/ppc/boot compared to 2.4.4 .
As a history lesson, why did this change ?
Another question: When booting the two different kernels (2.4.18 and
2.4.4-eldk) I noticed that the initial message about where the images
are loaded and relocated reported different addresses and sizes. Is
that expected?
Cheers,
Curt
On Sat, Sep 21, 2002 at 08:26:31PM -0700, curt brune wrote:
> Hi,
>
> I'm booting linux 2.4.18 on an embedded planet RPX_LITE-DW (823e) with
> a RAM disk, however I am getting a "crc" error while decompressing the
> RAM disk. Snipped from the boot log are these two lines:
>
> >> RAMDISK: Compressed image found at block 0
> >> crc errorFreeing initrd memory: 1670k freed
>
> I built the kernel image using "gmake zImage.initrd" . This picked up
> my gzipped ramdisk image OK.
>
> [editor: I know, I know. I should be using ppcboot.]
>
> The ramdisk is 8192 bytes uncompressed. Compressed it is 1.7MB.
>
> The target kernel is configured for 8192 byte ramdisks also. This is
> stumping me.
>
> In the boot log I also noticed something funny. My board only has
> 16MB total on it and the kernel is configured for 8MB ramdisk. In the
> boot log it says it is initializing 16 ramdisks of 8MB each ....
>
> >> Kernel command line: root=/dev/ram ramdisk=8192
> >> Memory: 13104k available (916k kernel code, 348k data, 52k init, 0k
> >> highmem)
> >> ...
> >> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
>
> Looking in rd.c I see 16 is a #define constant. Is this a problem?
>
> Cheers,
> Curt
>
>
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-09-25 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-22 3:26 initrd, ramdisk problems curt brune
2002-09-25 15:12 ` curt brune [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=20020925151213.GA19241@lenin.net \
--to=curt@acm.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).