linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "David H. Lynch Jr." <dhlii@comcast.net>
To: linuxppc-embedded@ozlabs.org
Subject: Problems starting /init
Date: Wed, 04 Jan 2006 18:03:11 -0500	[thread overview]
Message-ID: <43BC542F.5040302@comcast.net> (raw)
In-Reply-To: <20051208231947.92EB9353F77@atlas.denx.de>

 I have  a kernel for a new board (Linux 2.6.14.5, Pico E12/Xilinx V4
PPC405) booting to the point of starting /init.

/init appears to be getting loaded correctly - the execve call seems
happy. But I get no output on the console.

I have tried:

	executing
		sys_write(1,"Test",4);

		inside init/main.c immediately before starting /init - works fine.
	starting a "hello World" application written in PPC asm as /init -
works fine. The kernel panics on exit but that is normal, /init is not
supposed to exit.

	starting a c "Hello World" application that uses glibc, fputs, printf,
fwrite, to display a string - again works fine.

	But I can not get busybox to output a thing either run as /init or run
as /bin/sh.

	I have aslo tried /bin/sash - no output.
	I have even cross compiled sash - with all kinds of "I am here"
debugging scattered through main(), If I runn it on a powerbook, I get
what I expect. If I run it as /bin/sh on the e12 I get no output.


	Does anyone even have any ideas what I can look at ?
	

  parent reply	other threads:[~2006-01-04 23:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-08 15:19 Need help for Linux hangs jimmy liu
2005-12-08 16:05 ` Vitaly Bordug
2005-12-08 23:21   ` Wolfgang Denk
2005-12-08 23:19 ` Wolfgang Denk
2006-01-04  7:05   ` Problems starting /init David H. Lynch Jr.
     [not found]     ` <6AD9F6A5F6E096408F0B703773355A070E705B@CHN-SNR-MBX01.wipro.com>
2006-01-15  9:13       ` Problems starting /sbin/init David H. Lynch Jr.
2006-01-04 23:03   ` David H. Lynch Jr. [this message]
2006-01-04 23:20     ` Problems starting /init Geoff Thorpe
2006-01-04 23:19   ` RESEND:Problems " David H. Lynch Jr.
2006-01-09 18:45     ` Shawn Jin

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=43BC542F.5040302@comcast.net \
    --to=dhlii@comcast.net \
    --cc=linuxppc-embedded@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).