From: John Linn <John.Linn@xilinx.com>
To: "Stu Bershtein" <sbershtein@Quantum3D.com>,
<linuxppc-embedded@ozlabs.org>
Subject: RE: ml507 initrd problem
Date: Wed, 13 Aug 2008 08:11:04 -0600 [thread overview]
Message-ID: <20080813141107.92D4B948071@mail62-wa4.bigfish.com> (raw)
In-Reply-To: <8BB04FAC749BD24BBA250E9D09F2F18B220ABB@MAIL-SJC.quantum3d.com>
[-- Attachment #1: Type: text/plain, Size: 2821 bytes --]
Hi Stu,
I realize you are trying to get your own ram disk to work, but if you
want to get a baseline you can use one we have on our wiki site, at
http://xilinx.wikidot.com/open-source-linux, under Files To Download.
This is the same ram disk that is included in the ELDK.
This is the ram disk that I use to test the ML507 design in our Git
tree. I also use NFS a lot for testing.
Looks like you're close with yours, but I'm certainly no expert in that
area as I typically have something that works and don't change it.
Good luck,
John
________________________________
From: linuxppc-embedded-bounces+john.linn=xilinx.com@ozlabs.org
[mailto:linuxppc-embedded-bounces+john.linn=xilinx.com@ozlabs.org] On
Behalf Of Stu Bershtein
Sent: Tuesday, August 12, 2008 5:28 PM
To: linuxppc-embedded@ozlabs.org
Subject: ml507 initrd problem
I have been trying to boot linux on an ml507 board for a few days now.
I am using xilinx's linux-2.6-xlnx.git kernel. The rootfs is home
rolled. I have had experience with NFS mounted root filesystems (not an
option here), cramfs, and romfs but have never tried running root out of
a ramdisk. Because of that I am quite sure I have dorked this up. Any
help will be appreciated! I have added printk's in the kernel at
do_sys_open to get an idea what is going on. Here is a snip of the boot
output:
.
Kernel command line: console=ttyS0,9600 ip=on init=/linuxrc
root=/dev/ram rw ram disk_size=9000
.
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
disabled 83e00000.serial: ttyS0 at MMIO 0x83e00003 (irq = 16) is a
16550A
.
eth0: XLlTemac: Send Threshold = 0, Receive Threshold = 0
eth0: XLlTemac: Send Wait bound = 0, Receive Wait bound = 0
IP-Config: Incomplete network configuration information.
open /dev/ram
fd 0
open /initrd.image
fd 1
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 144k init
open /dev/console
fd 0
code 10000000 - 1019854c, data 10195000 - 1019854c, stack bf85df00
open /dev/null
fd 3
open /etc/inittab
fd 3
And it gets very quiet at that point. The kernel is still running in
ppc44x_idle. Does this suggest anything to anyone? I'll be more than
happy to send or describe any config files to any one who might take
pity.
Thanks,
Stu
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
[-- Attachment #2: Type: text/html, Size: 11962 bytes --]
next prev parent reply other threads:[~2008-08-13 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 23:28 ml507 initrd problem Stu Bershtein
2008-08-13 0:41 ` Philipp Hachtmann
2008-08-13 14:11 ` John Linn [this message]
2008-08-13 15:33 ` Stu Bershtein
2008-08-13 16:43 ` John Linn
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=20080813141107.92D4B948071@mail62-wa4.bigfish.com \
--to=john.linn@xilinx.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=sbershtein@Quantum3D.com \
/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