Mounta Vista Linux prompt on serial console

Mounta Vista Linux prompt on serial console

[srinivas.surabhi]

Our target is somewhat like this. It has PPC8270, Flash and SDRAM. We
are using the uboot for booting. Successfully built the linux kernel and
Ramdisk images using devrocket. The problem is that the kernel and
Ramdisk images although getting extracted successfully to 0M location of
SDRAM from Flash with the help of uboot, the serial console says nothing
except "uboot ist nicht tot..."

The command used is bootm "kernelImageLocation in Flash" "RAMdisk Image
in Flash"

i.e bootm 0xfe080000 0xff080000


1. How do I know that the control was given to linux kernel?

2. Is it that the linux kernel got the control but unable to put the
prompt on the serial line? FYI.  I modified the inittab to reflect the
console to come on the serial line.

3. Is there any documentation which gives the detailed debugging of the
linux kernel from the loading of kernel?


-Thanks=0D
SS




Confidentiality Notice=0D

The information contained in this electronic message and any attachments to=
 this message are intended
for the exclusive use of the addressee(s) and may contain confidential or=
 privileged information. If
you are not the intended recipient, please notify the sender at Wipro or=
 Mailadmin@wipro.com immediately
and destroy all copies of this message and any attachments.

Re: Mounta Vista Linux prompt on serial console

[Wolfgang Denk]

In message <EF9B29C78F41FA488927FCBC7750AF0E011DA5A1@hyd-mdp-msg.wipro.com> you wrote:
> 
> Our target is somewhat like this. It has PPC8270, Flash and SDRAM. We
> are using the uboot for booting. Successfully built the linux kernel and
> Ramdisk images using devrocket. The problem is that the kernel and

Are you sure that your Linux kernel is configured to be booted by U-Boot?

> Ramdisk images although getting extracted successfully to 0M location of
> SDRAM from Flash with the help of uboot, the serial console says nothing
> except "uboot ist nicht tot..."

Funny. This message is neiter part of the standard U-Boot code nor of
the standard Linux kernel. Try to find out where this code is  coming
from.

> 1. How do I know that the control was given to linux kernel?

Set a breakpoint at a low address like 0x000C. If the debugger  stops
there you are executing Linux kernel code.

Alternatively, enable DEBUG when building your U-Boot image (at least
when compiling file "common/cmd_bootm.c").

> 2. Is it that the linux kernel got the control but unable to put the
> prompt on the serial line? FYI.  I modified the inittab to reflect the
> console to come on the serial line.

Inittab has nothing to do with the kernel's startup messages. Is your
kernel configured correctly for using a serial console?

> 3. Is there any documentation which gives the detailed debugging of the
> linux kernel from the loading of kernel?

This is partially covered in the DULG, see
http://www.denx.de/twiki/bin/view/DULG/Manual

Best regards,

Wolfgang Denk

-- 
See us @ Embedded World, Nuremberg, Feb 22 - 24,  Hall 10.0 Booth 310
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Cogito cogito ergo cogito sum - "I think that I  think,  therefore  I
think that I am."          - Ambrose Bierce, "The Devil's Dictionary"

RE: Mounta Vista Linux prompt on serial console

[srinivas.surabhi]

Hi,

Today somehow after removing many options I build the kernel and able to
succeed till the VFS: "Mounted root (cramfs filesystem) readonly." But
then I am seeming "kernel panic". Actually what option has to be given
for init. We have given init=3D/bin/sh but no luck.

Please pull me out.

One more observation is that the U-boot bootargs are overwriting the
Kernel boot arguments given at the time of build. Even though using
setenv I removed the bootargs but still the kernel arguments given at
the time of build using devrocket are not still active.


The end part on the hyperterminal is given below

RAMDISK: Compressed image found at block 0
Freeing initrd memory: 2640k freed
VFS: Mounted root (cramfs filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 60k init
Warning: unable to open an initial console.
Error -3 while decompressing!
0015fd20(1928974736)->00141000(4096)
Kernel panic: No init found.  Try passing init=3D option to kernel.
 <0>Rebooting in 180 seconds..


Thanks & Regards
Surabhi Srinivas

-----Original Message-----
From: wd@denx.de [mailto:wd@denx.de]=0D
Sent: Tuesday, February 15, 2005 3:20 AM
To: Srinivas Surabhi (WT01 - EMBEDDED & PRODUCT ENGINEERING SOLUTIONS)
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Mounta Vista Linux prompt on serial console=0D

In message
<EF9B29C78F41FA488927FCBC7750AF0E011DA5A1@hyd-mdp-msg.wipro.com> you
wrote:
>=0D
> Our target is somewhat like this. It has PPC8270, Flash and SDRAM. We
> are using the uboot for booting. Successfully built the linux kernel
and
> Ramdisk images using devrocket. The problem is that the kernel and

Are you sure that your Linux kernel is configured to be booted by
U-Boot?

> Ramdisk images although getting extracted successfully to 0M location
of
> SDRAM from Flash with the help of uboot, the serial console says
nothing
> except "uboot ist nicht tot..."

Funny. This message is neiter part of the standard U-Boot code nor of
the standard Linux kernel. Try to find out where this code is  coming
from.

> 1. How do I know that the control was given to linux kernel?

Set a breakpoint at a low address like 0x000C. If the debugger  stops
there you are executing Linux kernel code.

Alternatively, enable DEBUG when building your U-Boot image (at least
when compiling file "common/cmd_bootm.c").

> 2. Is it that the linux kernel got the control but unable to put the
> prompt on the serial line? FYI.  I modified the inittab to reflect the
> console to come on the serial line.

Inittab has nothing to do with the kernel's startup messages. Is your
kernel configured correctly for using a serial console?

> 3. Is there any documentation which gives the detailed debugging of
the
> linux kernel from the loading of kernel?

This is partially covered in the DULG, see
http://www.denx.de/twiki/bin/view/DULG/Manual

Best regards,

Wolfgang Denk

--=0D
See us @ Embedded World, Nuremberg, Feb 22 - 24,  Hall 10.0 Booth 310
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Cogito cogito ergo cogito sum - "I think that I  think,  therefore  I
think that I am."          - Ambrose Bierce, "The Devil's Dictionary"



Confidentiality Notice=0D

The information contained in this electronic message and any attachments to=
 this message are intended
for the exclusive use of the addressee(s) and may contain confidential or=
 privileged information. If
you are not the intended recipient, please notify the sender at Wipro or=
 Mailadmin@wipro.com immediately
and destroy all copies of this message and any attachments.

Re: Mounta Vista Linux prompt on serial console

[Wolfgang Denk]

In message <EF9B29C78F41FA488927FCBC7750AF0E011DA5C5@hyd-mdp-msg.wipro.com> you wrote:
> 
> Today somehow after removing many options I build the kernel and able to
> succeed till the VFS: "Mounted root (cramfs filesystem) readonly." But
> then I am seeming "kernel panic". Actually what option has to be given
> for init. We have given init=/bin/sh but no luck.

You have to provide a working root filesystem in the first place.

> One more observation is that the U-boot bootargs are overwriting the
> Kernel boot arguments given at the time of build. Even though using

This is normal. If you use U-boot  there  is  no  need  to  have  any
pre-compiled  boot arguments; more: there is no need to use the whole
bootstrap loader which supplied these precompiled bootargs.

> setenv I removed the bootargs but still the kernel arguments given at
> the time of build using devrocket are not still active.

Just define the required bootargs in U-Boot.

> VFS: Mounted root (cramfs filesystem) readonly.
> Mounted devfs on /dev
> Freeing unused kernel memory: 60k init
> Warning: unable to open an initial console.
> Error -3 while decompressing!

Do not ignore this error. How big is your cramfs iage? How  much  RAM
do you have?

> 0015fd20(1928974736)->00141000(4096)

Is there any chance that you built your cramfs image on a x08 (or any
other little-endian) system and forgot  to  give  the  "-r"  (reverse
endian-ness of filesystem) option to mkcramfs??

Best regards,

Wolfgang Denk

-- 
See us @ Embedded World, Nuremberg, Feb 22 - 24,  Hall 10.0 Booth 310
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
In the strict scientific sense we all feed on death -- even
vegetarians.
	-- Spock, "Wolf in the Fold", stardate 3615.4

RE: Mounta Vista Linux prompt on serial console

[srinivas.surabhi]

[-- Attachment #1: Type: text/plain, Size: 3013 bytes --]


My replies in blue tagged with surabhi



-----Original Message-----
From: wd@denx.de [mailto:wd@denx.de]
Sent: Tuesday, February 15, 2005 5:24 PM
To: Srinivas Surabhi (WT01 - EMBEDDED & PRODUCT ENGINEERING SOLUTIONS)
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Mounta Vista Linux prompt on serial console



In message
<EF9B29C78F41FA488927FCBC7750AF0E011DA5C5@hyd-mdp-msg.wipro.com> you
wrote:

>

> Today somehow after removing many options I build the kernel and able
to

> succeed till the VFS: "Mounted root (cramfs filesystem) readonly." But

> then I am seeming "kernel panic". Actually what option has to be given

> for init. We have given init=/bin/sh but no luck.



You have to provide a working root filesystem in the first place.



[surabhi --- start] could you please guide me how to provide a working
file system on SDRAM before decompressing the Linux Image on SDRAM. Is
it really related to init process failed.



Is the below doesn't mean that the mounted one is working one ?

"VFS: Mounted root (cramfs filesystem) readonly.

 Mounted devfs on /dev "

[surabhi --- end]



> One more observation is that the U-boot bootargs are overwriting the

> Kernel boot arguments given at the time of build. Even though using



This is normal. If you use U-boot  there  is  no  need  to  have  any

pre-compiled  boot arguments; more: there is no need to use the whole

bootstrap loader which supplied these precompiled bootargs.



> setenv I removed the bootargs but still the kernel arguments given at

> the time of build using devrocket are not still active.



Just define the required bootargs in U-Boot.



> VFS: Mounted root (cramfs filesystem) readonly.

> Mounted devfs on /dev

> Freeing unused kernel memory: 60k init

> Warning: unable to open an initial console.

> Error -3 while decompressing!



Do not ignore this error. How big is your cramfs iage? How  much  RAM

do you have?



> 0015fd20(1928974736)->00141000(4096)



Is there any chance that you built your cramfs image on a x08 (or any

other little-endian) system and forgot  to  give  the  "-r"  (reverse

endian-ness of filesystem) option to mkcramfs??



Best regards,



Wolfgang Denk



--

See us @ Embedded World, Nuremberg, Feb 22 - 24,  Hall 10.0 Booth 310

Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de

In the strict scientific sense we all feed on death -- even

vegetarians.

      -- Spock, "Wolf in the Fold", stardate 3615.4





Confidentiality Notice

The information contained in this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or Mailadmin@wipro.com immediately
and destroy all copies of this message and any attachments.

[-- Attachment #2: Type: text/html, Size: 11678 bytes --]

Re: Mounta Vista Linux prompt on serial console

[Wolfgang Denk]

In message <EF9B29C78F41FA488927FCBC7750AF0E011DA5CB@hyd-mdp-msg.wipro.com> you wrote:
> 
> My replies in blue tagged with surabhi

Don't do this. Email is a plain text medium only.

Read the netiquette, and quote properly.

> [surabhi --- start] could you please guide me how to provide a working
> file system on SDRAM before decompressing the Linux Image on SDRAM. Is
> it really related to init process failed.

It is obviously related -there was a clear  error  message  that  the
uncompressing of the cramfs filesystem failed.

> Is the below doesn't mean that the mounted one is working one ?
> "VFS: Mounted root (cramfs filesystem) readonly.
>  Mounted devfs on /dev "

No, not at all. You can for example mount an empty  filesystem  -  it
will mount perfectly fine, but it still doesn't work.


You should also read my message until the end; I asked:


>> Do not ignore this error. How big is your cramfs iage? How  much  RAM
>> do you have?
...
>> Is there any chance that you built your cramfs image on a x08 (or any
>> other little-endian) system and forgot  to  give  the  "-r"  (reverse
>> endian-ness of filesystem) option to mkcramfs??


Best regards,

Wolfgang Denk

-- 
See us @ Embedded World, Nuremberg, Feb 22 - 24,  Hall 10.0 Booth 310
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Looks clean and obviously correct to me, but then _everything_ I
write always looks obviously correct to me.  - Linus Torvalds in
<Pine.LNX.4.10.10012090054360.791-100000@penguin.transmeta.com>

RE: Mounta Vista Linux prompt on serial console

[srinivas.surabhi]

>> Do not ignore this error. How big is your cramfs image? How  much
RAM
>> do you have?

cramfs is 2.7MB where as the RAM size is 32MB. While building ofcourse
the RAMDISK size was told as 8MB. This I mentioned in the devrocket
kernel configuration.

Just FYI. Kernel Image was 640KB.

Here I have one doubt while building the uBoot image using mkImage with
multi option where was the FileSystem image getting downloaded ? and how
the downloaded location was known to the kernel Image for pointing out
the File System image location. The options -a and -e are applicable
only for first image, isn't it? First image I mean the kernel Image. I
was giving -a 0x0 and -e 0x0 since while building the kernel the kernel
base address was mentioned 0.

...
>> Is there any chance that you built your cramfs image on a x08 (or any
>> other little-endian) system and forgot  to  give  the  "-r"  (reverse
>> endian-ness of filesystem) option to mkcramfs??

YES. You are right I am building the image on x86 (Windows platform).
But I checked the build log it used the -r option. The default build was
cpio format and after that using fstool converting to CRAMS and the
option -r was present .I believe that devrocket of MountaVista has
makefiles specific to OS i.e for Windows, because while installation it
asks for what type of OS do you want to have the Image Development
environment.

Thanks & Regards
Surabhi Srinivas


-----Original Message-----
From: wd@denx.de [mailto:wd@denx.de]=0D
Sent: Wednesday, February 16, 2005 1:30 AM
To: Srinivas Surabhi (WT01 - EMBEDDED & PRODUCT ENGINEERING SOLUTIONS)
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Mounta Vista Linux prompt on serial console=0D

In message
<EF9B29C78F41FA488927FCBC7750AF0E011DA5CB@hyd-mdp-msg.wipro.com> you
wrote:
>=0D
> My replies in blue tagged with surabhi

Don't do this. Email is a plain text medium only.

Read the netiquette, and quote properly.

> [surabhi --- start] could you please guide me how to provide a working
> file system on SDRAM before decompressing the Linux Image on SDRAM. Is
> it really related to init process failed.

It is obviously related -there was a clear  error  message  that  the
uncompressing of the cramfs filesystem failed.

> Is the below doesn't mean that the mounted one is working one ?
> "VFS: Mounted root (cramfs filesystem) readonly.
>  Mounted devfs on /dev "

No, not at all. You can for example mount an empty  filesystem  -  it
will mount perfectly fine, but it still doesn't work.


You should also read my message until the end; I asked:


>> Do not ignore this error. How big is your cramfs iage? How  much  RAM
>> do you have?

cramfs is 2.7MB where as the RAM size is 32MB. While building ofcourse
the RAMDISK size was told as 8MB. This I mentioned in the devrocket
kernel configuration.

...
>> Is there any chance that you built your cramfs image on a x08 (or any
>> other little-endian) system and forgot  to  give  the  "-r"  (reverse
>> endian-ness of filesystem) option to mkcramfs??

YES. You are right I am building the image on x86 (Windows platform).
But I checked the build log it used the -r option. The default build was
cpio format and after that using fstool converting to CRAMS and the
option -r was present .I believe that devrocket of MountaVista has
makefiles specific to OS i.e for Windows, because while installation it
asks for what type of OS do you want to have the Image Development
environment.

Thanks & Regards
Surabhi Srinivas


=0D

Best regards,

Wolfgang Denk

--=0D
See us @ Embedded World, Nuremberg, Feb 22 - 24,  Hall 10.0 Booth 310
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Looks clean and obviously correct to me, but then _everything_ I
write always looks obviously correct to me.  - Linus Torvalds in
<Pine.LNX.4.10.10012090054360.791-100000@penguin.transmeta.com>



Confidentiality Notice=0D

The information contained in this electronic message and any attachments to=
 this message are intended
for the exclusive use of the addressee(s) and may contain confidential or=
 privileged information. If
you are not the intended recipient, please notify the sender at Wipro or=
 Mailadmin@wipro.com immediately
and destroy all copies of this message and any attachments.

Re: Mounta Vista Linux prompt on serial console

[Wolfgang Denk]

In message <EF9B29C78F41FA488927FCBC7750AF0E011DA5D1@hyd-mdp-msg.wipro.com> you wrote:
> 
> cramfs is 2.7MB where as the RAM size is 32MB. While building ofcourse
> the RAMDISK size was told as 8MB. This I mentioned in the devrocket

What has the ramdisk to do  here?  Either  you  are  using  a  cramfs
filesystem, or a ramdisk (probably with an ext2 filesystem in it).

Putting cramfs filesystem in a ramdisk image is a pretty bad idea.

> Here I have one doubt while building the uBoot image using mkImage with
> multi option where was the FileSystem image getting downloaded ? and how

A multi-file image in U-Boot indeed requires a  ramdisk  image.  Then
you  should  not  use a cramfs filesystem. The method for loading tha
ramdisk image is described in the U-Boot "README"  file;  search  for
"positioning of initrd images".

> the downloaded location was known to the kernel Image for pointing out
> the File System image location. The options -a and -e are applicable
> only for first image, isn't it? First image I mean the kernel Image. I

Yes. Only the kernel is executable code and has an entry point.

> YES. You are right I am building the image on x86 (Windows platform).
> But I checked the build log it used the -r option. The default build was
> cpio format and after that using fstool converting to CRAMS and the
> option -r was present .I believe that devrocket of MountaVista has
> makefiles specific to OS i.e for Windows, because while installation it
> asks for what type of OS do you want to have the Image Development
> environment.

Maybe you should ask MV support, then. 

Best regards,

Wolfgang Denk

-- 
See us @ Embedded World, Nuremberg, Feb 22 - 24,  Hall 10.0 Booth 310
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
It is clear that the individual who persecutes a  man,  his  brother,
because he is not of the same opinion, is a monster.       - Voltaire

RE: Mounta Vista Linux prompt on serial console

[srinivas.surabhi]

[-- Attachment #1: Type: text/plain, Size: 3927 bytes --]


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)


But the problem is that it was stopping at

"No init found.  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.



The fstab file is like this.



/dev/ram      /            auto         defaults,errors=remount-ro

/proc         /proc        proc         defaults



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.





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.



Thanks & Regards

Surabhi Srinivas

________________________________

From: Wolfgang Denk [mailto:wd@denx.de]
Sent: Thu 2/17/2005 1:30 AM
To: Srinivas Surabhi (WT01 - EMBEDDED & PRODUCT ENGINEERING SOLUTIONS)
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Mounta Vista Linux prompt on serial console



In message <EF9B29C78F41FA488927FCBC7750AF0E011DA5D1@hyd-mdp-msg.wipro.com> you wrote:
>
> cramfs is 2.7MB where as the RAM size is 32MB. While building ofcourse
> the RAMDISK size was told as 8MB. This I mentioned in the devrocket

What has the ramdisk to do  here?  Either  you  are  using  a  cramfs
filesystem, or a ramdisk (probably with an ext2 filesystem in it).

Putting cramfs filesystem in a ramdisk image is a pretty bad idea.

> Here I have one doubt while building the uBoot image using mkImage with
> multi option where was the FileSystem image getting downloaded ? and how

A multi-file image in U-Boot indeed requires a  ramdisk  image.  Then
you  should  not  use a cramfs filesystem. The method for loading tha
ramdisk image is described in the U-Boot "README"  file;  search  for
"positioning of initrd images".

> the downloaded location was known to the kernel Image for pointing out
> the File System image location. The options -a and -e are applicable
> only for first image, isn't it? First image I mean the kernel Image. I

Yes. Only the kernel is executable code and has an entry point.

> YES. You are right I am building the image on x86 (Windows platform).
> But I checked the build log it used the -r option. The default build was
> cpio format and after that using fstool converting to CRAMS and the
> option -r was present .I believe that devrocket of MountaVista has
> makefiles specific to OS i.e for Windows, because while installation it
> asks for what type of OS do you want to have the Image Development
> environment.

Maybe you should ask MV support, then.

Best regards,

Wolfgang Denk

--
See us @ Embedded World, Nuremberg, Feb 22 - 24,  Hall 10.0 Booth 310
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
It is clear that the individual who persecutes a  man,  his  brother,
because he is not of the same opinion, is a monster.       - Voltaire






Confidentiality Notice

The information contained in this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or Mailadmin@wipro.com immediately
and destroy all copies of this message and any attachments.

[-- Attachment #2: Type: text/html, Size: 7144 bytes --]

Re: Mounta Vista Linux prompt on serial console

[Wolfgang Denk]

In message <EF9B29C78F41FA488927FCBC7750AF0E08DA14@hyd-mdp-msg.wipro.com> you wrote:
> 
> But the problem is that it was stopping at
> 
> "No init found.  Try passing init= option to kernel". Before that there
>  were no errors. Everthing looks fine Mounted VFS root file system was also

Fine. So you can mount the root filesystem, but it obviously does not
contain all the required files.

>  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.

No. /etc/fstab has absolutley nothing to do with  your  problem.  The
kernel  cannot  start  the  init  porocess - make sure init is in the
filesystem, plus all required libraries.

> So please tell me whether the given fstab file will suffice? The filesystem

This is completley unrelated.

> 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.

Please contact MV support. I have no  idea  how  they  package  their
distribution,  or  how  their  config  tools might work. You paid for
their stuff, so ask _them_.

Best regards,

Wolfgang Denk

-- 
See us @ Embedded World, Nuremberg, Feb 22 - 24,  Hall 10.0 Booth 310
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
The most exciting phrase to hear in science, the one that heralds new
discoveries, is not "Eureka!" (I found it!) but "That's funny ..."
                                                      -- Isaac Asimov

RE: Mounta Vista Linux prompt on serial console

[srinivas.surabhi]

[-- Attachment #1: Type: text/plain, Size: 3101 bytes --]


The latest update is that the init was also found in one of the packages. So now I am not facing init not found problem . But there was a hung problem, once the init is invoked .. Please find the output below...

RAMDISK: Compressed image found at block 0

Freeing initrd memory: 1235k freed

kjournald starting. Commit interval 5 seconds

EXT3-fs: mounted filesystem with ordered data mode.

VFS: Mounted root (ext3 filesystem) readonly.

Mounted devfs on /dev

Freeing unused kernel memory: 56k init

< there is no output after the above statement.....>

Thanks & Regards
Surabhi Srinivas

________________________________

From: Wolfgang Denk [mailto:wd@denx.de]
Sent: Thu 2/17/2005 5:12 PM
To: Srinivas Surabhi (WT01 - EMBEDDED & PRODUCT ENGINEERING SOLUTIONS)
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Mounta Vista Linux prompt on serial console



In message <EF9B29C78F41FA488927FCBC7750AF0E08DA14@hyd-mdp-msg.wipro.com> you wrote:
>
> But the problem is that it was stopping at
>
> "No init found.  Try passing init= option to kernel". Before that there
>  were no errors. Everthing looks fine Mounted VFS root file system was also

Fine. So you can mount the root filesystem, but it obviously does not
contain all the required files.

>  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.

No. /etc/fstab has absolutley nothing to do with  your  problem.  The
kernel  cannot  start  the  init  porocess - make sure init is in the
filesystem, plus all required libraries.

> So please tell me whether the given fstab file will suffice? The filesystem

This is completley unrelated.

> 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.

Please contact MV support. I have no  idea  how  they  package  their
distribution,  or  how  their  config  tools might work. You paid for
their stuff, so ask _them_.

Best regards,

Wolfgang Denk

--
See us @ Embedded World, Nuremberg, Feb 22 - 24,  Hall 10.0 Booth 310
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
The most exciting phrase to hear in science, the one that heralds new
discoveries, is not "Eureka!" (I found it!) but "That's funny ..."
                                                      -- Isaac Asimov






Confidentiality Notice

The information contained in this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or Mailadmin@wipro.com immediately
and destroy all copies of this message and any attachments.

[-- Attachment #2: Type: text/html, Size: 4612 bytes --]

RE: Mounta Vista Linux prompt on serial console

[srinivas.surabhi]

Hi,

We are facing the problem with MVlinux3.1 having kernel 2.4.20 booting
once the PCI is enabled in config kernel.

Even the message " linux banner " which is at the beginning of the
start_kernel function is not seen. Once the multi image( kernel + ram
disk File system) is extracted into RAM. After that it hangs=0D

bootm 0xfef80000 ## Booting image at fef80000 ...
   Image Name:   MultiImage
   Image Type:   PowerPC Linux Multi-File Image (gzip compressed)
   Data Size:    4647626 Bytes =3D  4.4 MB
   Load Address: 00000000
   Entry Point:  00000000
   Contents:
   Image 0:   551181 Bytes =3D 538.3 kB
   Image 1:  4096430 Bytes =3D  3.9 MB
   Verifying Checksum ... OK
   Uncompressing Multi-File Image ... =3D0=3D
OK
Booting Linux
   Loading Ramdisk to 07417000, end 077ff1ae ... OK

...Then hangs ....

SO please help me out in finding out the relation of PCI and the
start_kernel. As per my knowledge once the kernel_init is entered then
the pci_init is invoked. But strangely I am seeing with pci enabled,
hang at the very beginning..

Thanks & Rgds
SS

-----Original Message-----
From: wd@denx.de [mailto:wd@denx.de]=0D
Sent: Thursday, February 17, 2005 5:13 PM
To: Srinivas Surabhi (WT01 - EMBEDDED & PRODUCT ENGINEERING SOLUTIONS)
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Mounta Vista Linux prompt on serial console=0D

In message
<EF9B29C78F41FA488927FCBC7750AF0E08DA14@hyd-mdp-msg.wipro.com> you
wrote:
>=0D
> But the problem is that it was stopping at
>=0D
> "No init found.  Try passing init=3D option to kernel". Before that
there
>  were no errors. Everthing looks fine Mounted VFS root file system was
also

Fine. So you can mount the root filesystem, but it obviously does not
contain all the required files.

>  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.

No. /etc/fstab has absolutley nothing to do with  your  problem.  The
kernel  cannot  start  the  init  porocess - make sure init is in the
filesystem, plus all required libraries.

> So please tell me whether the given fstab file will suffice? The
filesystem

This is completley unrelated.

> 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.

Please contact MV support. I have no  idea  how  they  package  their
distribution,  or  how  their  config  tools might work. You paid for
their stuff, so ask _them_.

Best regards,

Wolfgang Denk

--=0D
See us @ Embedded World, Nuremberg, Feb 22 - 24,  Hall 10.0 Booth 310
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
The most exciting phrase to hear in science, the one that heralds new
discoveries, is not "Eureka!" (I found it!) but "That's funny ..."
                                                      -- Isaac Asimov



Confidentiality Notice=0D

The information contained in this electronic message and any attachments to=
 this message are intended
for the exclusive use of the addressee(s) and may contain confidential or=
 privileged information. If
you are not the intended recipient, please notify the sender at Wipro or=
 Mailadmin@wipro.com immediately
and destroy all copies of this message and any attachments.