[Ltib] Re: Ltib Digest, Vol 22, Issue 3

[hong zhang]

Stuart,

I typed ./ltib -D and does not see ramdisk
information.
How do I know ramdisk size?
Based on my experience with LTIB, ltib does not
generate ramdisk in iMX31ads.

---henry
--- address@hidden wrote:

> Send Ltib mailing list submissions to
>       address@hidden
> 
> To subscribe or unsubscribe via the World Wide Web,
> visit
>       http://lists.nongnu.org/mailman/listinfo/ltib
> or, via email, send a message with subject or body
> 'help' to
>       address@hidden
> 
> You can reach the person managing the list at
>       address@hidden
> 
> When replying, please edit your Subject line so it
> is more specific
> than "Re: Contents of Ltib digest..."
> 
> 
> Today's Topics:
> 
>    1. Booting problem, please help (B R Manjula)
>    2. Re: Booting problem, please help (Stuart
> Hughes)
>    3. Compact Flash on MPC8349ITX? (Chip Webb)
>    4. Re: Compact Flash on MPC8349ITX? (Stuart
> Hughes)
> 
> 
>
----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 5 Feb 2008 02:57:10 +0530
> From: "B R Manjula" <address@hidden>
> Subject: [Ltib] Booting problem, please help
> To: address@hidden
> Message-ID:
> <address@hidden>
> Content-Type: text/plain;     charset=iso-8859-1
> 
> 
> Hi! 
> 
> Description: We are using LTIB for MPC8323-RDB and
> we are trying to build a image.
> The Release info is as follows:
> Release date = Fri Apr 20 18:50:31 2007 UTC
> CVS wtag     = Tbranch-mpc832x_rdb-7-2-1
> CVS tag      = branch-mpc832x_rdb-7-2-1
> Release tag  = ltib-mpc832x_rdb-20070420
> App version  = 7.2.1
> CVS version  = $Revision: 1.271.2.1 $
> 
> The ltib is installed and configured as given in the
> FAQ.
> When we tried to boot the linux kernel image on the
> target i.e MPC8323RDB
> using the command "run tftpramboot" on the minicom,
> the following error occured.
> 
> RAMDISK: incomplete write (8192 != 32768) 25591808
> VFS: Mounted root (ext2 filesystem).
> Freeing unused kernel memory: 132k init
> attempt to access beyond end of device
> ram0: rw=0, want=60876, limit=50000
> EXT2-fs error (device ram0): ext2_get_inode: unable
> to read inode block -
> inode7Warning: unable to open an initial console.
> attempt to access beyond end of device
> ram0: rw=0, want=60888, limit=50000
> EXT2-fs error (device ram0): ext2_get_inode: unable
> to read inode block -
> inode3Kernel panic - not syncing: No init found. 
> Try passing init= option to
> kernel.
> <0>Rebooting in 180 seconds..
> 
> We tried several times by varying the   ramdisk size
> i.e
> CONFIG_BLK_DEV_RAM_SIZE.But this did not  work.
> Awaitng a prompt reply from you.
> 
> Thanks in advance,
> Manjula 
> -Regards
>  Manjula
> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Tue, 05 Feb 2008 10:19:19 +0000
> From: Stuart Hughes <address@hidden>
> Subject: Re: [Ltib] Booting problem, please help
> To: B R Manjula <address@hidden>
> Cc: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain
> 
> Hi Manjula,
> 
> This is from a Freescale ISO release, so you need to
> contact them for
> support by following these steps:
> 
>    * go to http://www.freescale.com
>    * click on "Support / Technical support"
>    * click on "Submit a Service Request"
>    * register to get a user name and password.
>    * login in with your user name and password
>    * on the "New Service Request" page:
>       * category = Technical Request
>       * topic = Linux BSP
>       * Click on "Continue"
>    * fill out the information for the service
> request
>    * click on the "Submit" button at the bottom of
> the page.
> 
> However, it looks like the problem is that you
> haven't passed in the
> size of the ramdisk to the u-boot command (you don't
> need to change the
> kernel config).
> 
> If you run ./ltib -D, it will print out the size of
> the ramdisk you
> need, for example (from another system):
> 
> Filesystem stats, including padding:
> 
>     Total size            = 13240k
>     Total number of files = 404
> 
> Your ramdisk exceeds the old default size of 4096k,
> you may need to
> set the command line argument for ramdisk_size in
> your bootloader
> allowing 10% free this gives 14564k .  For instance,
> for u-boot:
> 
> setenv bootargs root=/dev/ram rw ramdisk_size=14564
> 
> So if I'm using u-boot I need to make sure in my
> command line I add to
> it: ramdisk_size=14564 (your exact size will be
> different to this
> example).
> 
> Because you're running the macro "tftpramboot"
> you'll need to figure out
> where it is getting its command line and to update
> that (append to it).
> 
> Regards, Stuart
> 
> 
> On Tue, 2008-02-05 at 02:57 +0530, B R Manjula
> wrote:
> > Hi! 
> > 
> > Description: We are using LTIB for MPC8323-RDB and
> we are trying to build a image.
> > The Release info is as follows:
> > Release date = Fri Apr 20 18:50:31 2007 UTC
> > CVS wtag     = Tbranch-mpc832x_rdb-7-2-1
> > CVS tag      = branch-mpc832x_rdb-7-2-1
> > Release tag  = ltib-mpc832x_rdb-20070420
> > App version  = 7.2.1
> > CVS version  = $Revision: 1.271.2.1 $
> > 
> > The ltib is installed and configured as given in
> the FAQ.
> > When we tried to boot the linux kernel image on
> the target i.e MPC8323RDB
> > using the command "run tftpramboot" on the
> minicom, the following error occured.
> > 
> > RAMDISK: incomplete write (8192 != 32768) 25591808
> > VFS: Mounted root (ext2 filesystem).
> > Freeing unused kernel memory: 132k init
> > attempt to access beyond end of device
> > ram0: rw=0, want=60876, limit=50000
> > EXT2-fs error (device ram0): ext2_get_inode:
> unable to read inode block -
> > inode7Warning: unable to open an initial console.
> > attempt to access beyond end of device
> > ram0: rw=0, want=60888, limit=50000
> > EXT2-fs error (device ram0): ext2_get_inode:
> unable to read inode block -
> > inode3Kernel panic - not syncing: No init found. 
> Try passing init= option to
> > kernel.
> > <0>Rebooting in 180 seconds..
> > 
> > We tried several times by varying the   ramdisk
> size i.e
> > CONFIG_BLK_DEV_RAM_SIZE.But this did not  work.
> > Awaitng a prompt reply from you.
> 
=== message truncated ===



      
____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ