<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7232.39">
<TITLE>Re: Mounta Vista Linux prompt on serial console </TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText82453 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Sorry if I am eating away
your time .. but now it has come to some stage ..able to decompress image of
ramdisk image ( with ext2 in it)</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT size=2><FONT
face="Courier New">But the problem is that it was stopping at<?xml:namespace
prefix = o ns = "urn:schemas-microsoft-com:office:office"
/><o:p></o:p></FONT></FONT></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><FONT size=2><FONT
face="Courier New">"No init found.<SPAN style="mso-spacerun: yes">
</SPAN>Try passing init= option to kernel". Before that there were no errors.
Everthing looks fine Mounted VFS root file system was also seen. From the net I
understood is that the fstab file was the cause. So edited the filesytem
parameter for / as /dev/ram earlier it used to be
/dev/root.<o:p></o:p></FONT></FONT></P></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV></DIV>
<P class=MsoPlainText dir=ltr style="MARGIN: 0in 0in 0pt"><FONT size=2><FONT
face="Courier New">The fstab file is like this. <o:p></o:p></FONT></FONT></P>
<P class=MsoPlainText dir=ltr style="MARGIN: 0in 0in 0pt"><o:p><FONT
face="Courier New" size=2> </FONT></o:p></P>
<P class=MsoPlainText dir=ltr style="MARGIN: 0in 0in 0pt"><FONT size=2><FONT
face="Courier New">/dev/ram<SPAN
style="mso-spacerun: yes"> </SPAN>/<SPAN
style="mso-spacerun: yes">
</SPAN>auto<SPAN
style="mso-spacerun: yes">
</SPAN>defaults,errors=remount-ro<o:p></o:p></FONT></FONT></P>
<P class=MsoPlainText dir=ltr style="MARGIN: 0in 0in 0pt"><FONT size=2><FONT
face="Courier New">/proc<SPAN
style="mso-spacerun: yes">
</SPAN>/proc<SPAN
style="mso-spacerun: yes">
</SPAN>proc<SPAN
style="mso-spacerun: yes">
</SPAN>defaults<o:p></o:p></FONT></FONT></P>
<P class=MsoPlainText dir=ltr style="MARGIN: 0in 0in 0pt"><o:p><FONT
face="Courier New" size=2> </FONT></o:p></P>
<P class=MsoPlainText dir=ltr style="MARGIN: 0in 0in 0pt"><FONT size=2><FONT
face="Courier New">So please tell me whether the given fstab file will suffice?
The filesystem image was build for ext2. I tried wih CRAMFS but some
decompressing error was coming where as the ext2 filesystem image was working
fine.<o:p></o:p></FONT></FONT></P>
<P class=MsoPlainText dir=ltr style="MARGIN: 0in 0in 0pt"><o:p><FONT
face="Courier New" size=2></FONT></o:p> </P>
<P class=MsoPlainText dir=ltr style="MARGIN: 0in 0in 0pt"><o:p><FONT
face="Courier New" size=2></FONT></o:p> </P>
<P class=MsoPlainText dir=ltr style="MARGIN: 0in 0in 0pt"><o:p><FONT
face="Courier New" size=2>2. I have one more doubt /sbin/init utility comes with
what package? Because in /sbin directory although the init binary is present,
not shown in the file system heirarchy view. For eg. if I select DHCPD package
then able to see dhcpd related binary in the /sbin similarly my question was
which package has to be selected to have init included.</FONT></o:p></P>
<P class=MsoPlainText dir=ltr style="MARGIN: 0in 0in 0pt"><o:p><FONT
face="Courier New" size=2></FONT></o:p> </P>
<P>Thanks & Regards</P>
<P>Surabhi Srinivas</P>
<P>
<HR tabIndex=-1>
</P>
<DIV dir=ltr><FONT face=Tahoma size=2><B>From:</B> Wolfgang Denk
[mailto:wd@denx.de]<BR><B>Sent:</B> Thu 2/17/2005 1:30 AM<BR><B>To:</B> Srinivas
Surabhi (WT01 - EMBEDDED & PRODUCT ENGINEERING SOLUTIONS)<BR><B>Cc:</B>
linuxppc-embedded@ozlabs.org<BR><B>Subject:</B> Re: Mounta Vista Linux prompt on
serial console <BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>In message
<EF9B29C78F41FA488927FCBC7750AF0E011DA5D1@hyd-mdp-msg.wipro.com> you
wrote:<BR>><BR>> cramfs is 2.7MB where as the RAM size is 32MB. While
building ofcourse<BR>> the RAMDISK size was told as 8MB. This I mentioned in
the devrocket<BR><BR>What has the ramdisk to do here? Either
you are using a cramfs<BR>filesystem, or a ramdisk
(probably with an ext2 filesystem in it).<BR><BR>Putting cramfs filesystem in a
ramdisk image is a pretty bad idea.<BR><BR>> Here I have one doubt while
building the uBoot image using mkImage with<BR>> multi option where was the
FileSystem image getting downloaded ? and how<BR><BR>A multi-file image in
U-Boot indeed requires a ramdisk image. Then<BR>you
should not use a cramfs filesystem. The method for loading
tha<BR>ramdisk image is described in the U-Boot "README" file;
search for<BR>"positioning of initrd images".<BR><BR>> the downloaded
location was known to the kernel Image for pointing out<BR>> the File System
image location. The options -a and -e are applicable<BR>> only for first
image, isn't it? First image I mean the kernel Image. I<BR><BR>Yes. Only the
kernel is executable code and has an entry point.<BR><BR>> YES. You are right
I am building the image on x86 (Windows platform).<BR>> But I checked the
build log it used the -r option. The default build was<BR>> cpio format and
after that using fstool converting to CRAMS and the<BR>> option -r was
present .I believe that devrocket of MountaVista has<BR>> makefiles specific
to OS i.e for Windows, because while installation it<BR>> asks for what type
of OS do you want to have the Image Development<BR>>
environment.<BR><BR>Maybe you should ask MV support, then.<BR><BR>Best
regards,<BR><BR>Wolfgang Denk<BR><BR>--<BR>See us @ Embedded World, Nuremberg,
Feb 22 - 24, Hall 10.0 Booth 310<BR>Phone: (+49)-8142-66989-10 Fax:
(+49)-8142-66989-80 Email: wd@denx.de<BR>It is clear that the individual who
persecutes a man, his brother,<BR>because he is not of the
same opinion, is a monster. -
Voltaire<BR></FONT></P></DIV>
</BODY>
</HTML>
<table><tr><td bgcolor=#ffffff><font color=#000000><br>
<br>
Confidentiality Notice <br>
<br>
The information contained in this electronic message and any attachments to this message are intended<br>
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If<br>
you are not the intended recipient, please notify the sender at Wipro or Mailadmin@wipro.com immediately<br>
and destroy all copies of this message and any attachments.<br>
</font></td></tr></table>