From: "sungyeon" <sungyeon@cosmo.etri.re.kr>
To: "dony" <dony.he@huawei.com.cn>, <Ruedi.Hofer@ascom.ch>,
"linuxppc-embed" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: initrd question...
Date: Wed, 16 Feb 2000 11:59:30 +0900 [thread overview]
Message-ID: <006a01bf7829$d9390c10$5a01a8c0@blue> (raw)
In-Reply-To: 38AA0E9C.619E523@huawei.com.cn
----- Original Message -----
From: "dony" <dony.he@huawei.com.cn>
To: <Ruedi.Hofer@ascom.ch>; "linuxppc-embed"
<linuxppc-embedded@lists.linuxppc.org>
Sent: Wednesday, February 16, 2000 11:42 AM
Subject: initrd question...
>
> Hello:
> Now I want to get my initrd running. I use the ramdisk demo
"ramdisk.image.gz" under
> arch/ppc/mbxboot and compile my zvmlinux.initrd.
> The target boots correctly at the beginning. It decompresses the
kernel and runs the kernel and
> shows the boot messages. When all is done, it begins to mount root
filesystem (on Ramdisk), and shows
> the following messages:
> RAMDISK:Compressed image found at block 0
> VFS:Mounted root (ext2 filesystem)
> Freeing unused kernel memory:28k init
> Then nothing happen.
If your root file system is nfs, and disable BOOTP kernel option
then nothing happen. like you.
I'v changed root file system from NFS to RAMdisk. and disabled BOOTP.
> At this time it should show the shell prompt. But I don't know why it
didn't show. And I couldnot input
> any character.
> Cross-compile environment:
> [binutils-2.9.1.0.19a egcs-1.1.2 glibc-2.1(including
crypt, linuxthreads)]
> I cross-compile my kernel under the above environment.
> Any suggestions will be highly appreciated.
> Thank in advance
> dony
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-16 2:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0FPX00FFH0XJV5@pmdf-it.hasler.ascom.ch>
2000-02-16 2:42 ` initrd question dony
2000-02-16 2:59 ` sungyeon [this message]
2000-02-16 3:13 ` dony
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='006a01bf7829$d9390c10$5a01a8c0@blue' \
--to=sungyeon@cosmo.etri.re.kr \
--cc=Ruedi.Hofer@ascom.ch \
--cc=dony.he@huawei.com.cn \
--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).