Just as a simple sanity check, I'd test it without trying to overcomplicate things. Forget the symlinks to busybox; just rename the binary to /bin/sh, or whatever name busybox uses to decide to be a shell; then modify the test kernel to run /bin/sh instead of /sbin/init. That will at least prove that the kernel can successfully boot.
And from that, you can try running by hand each command that your proposed initramfs is supposed to run automatically via init. By doing that, you should be able to identify where the init process was failing. On Fri, July 11, 2008 7:59 am, Alexander Wolfson said: > This is what I am doing as well. > Usually there is a statically linked program in the /bin called busybox > which provides big chunk of expected command line functionality. > > All the programms - bash, ash, ls, ping, ... are slinks to busybox (init > as well) and busybox checks ARGV[0] for the name that was used to call it > and acts accordingly. It still has to be part of some filesystem and this > is where the problem is. I am doing something wrong creating the initramfs > and linking it with the kernel or something is wrong with my busybox or > this is something else that I am not even think of. > > Alex > > -----Original Message----- > From: [EMAIL PROTECTED] on behalf of John Abreau > Sent: Thu 7/10/2008 5:59 PM > To: gnhlug-discuss@mail.gnhlug.org > Subject: RE: Example of ARM based linux board using initramfs and serial > console > > > On Thu, July 10, 2008 4:08 pm, Alexander Wolfson said: >> This is our own board based on our own chip which among other things has >> ARM926EJ-S (ARMv5TEJ) core. >> There is no BSP yet, no Flash or USB drivers - only limited access to >> the board over JTAG. We can boot the board up to the point when kernel >> dies because there is no init. This why I need initramfs now. >> > > > While i don't know the details, I understand that it's common practice > when porting to a new platform to use bash, or perhaps a simpler shell, > in place of init, as a first step to achieve an initial boot. > > > -- > John Abreau / Executive Director, Boston Linux & Unix > IM: [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL > PROTECTED] > Email [EMAIL PROTECTED] / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9 > PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99 > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > _______________________________________________ > gnhlug-discuss mailing list > gnhlug-discuss@mail.gnhlug.org > http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > -- John Abreau / Executive Director, Boston Linux & Unix IM: [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED] Email [EMAIL PROTECTED] / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9 PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
