From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from WA4EHSOBE006.bigfish.com (outbound-wa4.frontbridge.com [216.32.181.16]) by ozlabs.org (Postfix) with ESMTP id 30D45DDF1D for ; Thu, 14 Aug 2008 00:11:16 +1000 (EST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8FD4E.6CC088FE" Subject: RE: ml507 initrd problem Date: Wed, 13 Aug 2008 08:11:04 -0600 In-Reply-To: <8BB04FAC749BD24BBA250E9D09F2F18B220ABB@MAIL-SJC.quantum3d.com> References: <8BB04FAC749BD24BBA250E9D09F2F18B220ABB@MAIL-SJC.quantum3d.com> From: John Linn To: "Stu Bershtein" , Message-ID: <20080813141107.92D4B948071@mail62-wa4.bigfish.com> List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , ------_=_NextPart_001_01C8FD4E.6CC088FE Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable 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=3Dxilinx.com@ozlabs.org [mailto:linuxppc-embedded-bounces+john.linn=3Dxilinx.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=3DttyS0,9600 ip=3Don init=3D/linuxrc root=3D/dev/ram rw ram disk_size=3D9000 . Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled 83e00000.serial: ttyS0 at MMIO 0x83e00003 (irq =3D 16) is a 16550A . eth0: XLlTemac: Send Threshold =3D 0, Receive Threshold =3D 0 eth0: XLlTemac: Send Wait bound =3D 0, Receive Wait bound =3D 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 r= ecipient(s) and contain(s) confidential information that may be proprietary= , privileged or copyrighted under applicable law. If you are not the intend= ed recipient, do not read, copy, or forward this email message or any attac= hments. Delete this email message and any attachments immediately. ------_=_NextPart_001_01C8FD4E.6CC088FE Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Hi Stu,

 

I realize you are trying to get your o= wn ram disk to work, but if you want to get a baseline you can use one we have= on our wiki site, at h= ttp://xilinx.wikidot.com/open-source-linux, under Files To Download.  This is the same ram disk that is included i= n the ELDK.

 

This is the ram disk that I use to tes= t the ML507 design in our Git tree.  I also use NFS a lot for testing.

 

Looks like you’re close with you= rs, but I’m certainly no expert in that area as I typically have somethin= g that works and don’t change it.

 

Good luck,

John

 

From: linuxppc= -embedded-bounces+john.linn=3Dxilinx.com@ozlabs.org [mailto:linuxppc-embedded-bounces+john.linn=3Dxilinx.com@ozlabs.org] On Behalf Of Stu Bershtein
Sent: Tuesday, August 12, 20= 08 5:28 PM
To: linuxppc-embedded@ozlabs= .org
Subject: ml507 initrd proble= m

 

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 a= t do_sys_open to get an idea what is going on.  Here is a snip of the bo= ot output:

 

.<= o:p>

Ke= rnel command line: console=3DttyS0,9600 ip=3Don init=3D/linuxrc root=3D/dev/ram = rw ram disk_size=3D9000

.<= o:p>

Se= rial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled 83e00000.serial: ttyS0 at MMIO 0x83e00003 (irq =3D 16) is a 16550A

.<= o:p>

et= h0: XLlTemac: Send Threshold =3D 0, Receive Threshold =3D 0

et= h0: XLlTemac: Send Wait bound =3D 0, Receive Wait bound =3D 0=

IP= -Config: Incomplete network configuration information.<= /p>

op= en /dev/ram

fd= 0

op= en /initrd.image

fd= 1

RA= MDISK: Compressed image found at block 0

VF= S: Mounted root (ext2 filesystem).

Fr= eeing unused kernel memory: 144k init

op= en /dev/console

fd= 0

co= de 10000000 - 1019854c, data 10195000 - 1019854c, stack bf85df00

op= en /dev/null

fd= 3

op= en /etc/inittab

fd= 3

 

An= d it gets very quiet at that point.  The kernel is still running in ppc44x_idle.  Does this suggest anything to anyone?  I’ll b= e more than happy to send or describe any config files to any one who might t= ake pity.

 

Th= anks,

St= u

 


This email and any attachments are intended for the sole u= se of the named recipient(s) and contain(s) confidential information that m= ay be proprietary, privileged or copyrighted under applicable law. If you a= re not the intended recipient, do not read, copy, or forward this email mes= sage or any attachments. Delete this email message and any attachments imme= diately. ------_=_NextPart_001_01C8FD4E.6CC088FE--