From: Chris Dumoulin <cdumoulin@ics-ltd.com>
To: "Steve Iribarne (GMail)" <netstv@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: help with inittab
Date: Fri, 09 Jun 2006 15:14:49 -0400 [thread overview]
Message-ID: <4489C8A9.1080401@ics-ltd.com> (raw)
In-Reply-To: <b4b98b690606091123q6a31a9d2xf7219de14b94003a@mail.gmail.com>
The init is from Busybox. Since I'm getting output from my serial port
during the kernel boot process, I think it's safe to say that my
/dev/ttyS0 is properly configured. Besides passing the kernel argument
console=ttyS0,57600, is there anything else I need to do to properly
configure the console? I've looked through my kernel configuration to
make sure that any serial device or console related stuff was enabled
and configured.
I'm feeling pretty stumped.
- Chris
Steve Iribarne (GMail) wrote:
> On 6/9/06, Chris Dumoulin <cdumoulin@ics-ltd.com> wrote:
>
>> I've now determined that my kernel seems to stop in the following line
>> of code, in the function init(void * unused), in init/main.c:
>> run_init_process("/sbin/init");
>
>
> Who's init are you using??
>
> Are you using Busyboxes or sysinit from GNU?
>
>
>> I've determined that it stops at this call by stepping through the code
>> with a BDI2000.
>>
>> My boot arguments are:
>> console=ttyS0,57600n8 ip=off root=/dev/ram0 rw
>>
>> My current inittab is:
>> ::sysinit:/etc/rc.sh
>> ::ctrlaltdel:/sbin/reboot
>> ::shutdown:/sbin/swapoff -a
>> ::shutdown:/bin/umount -a -r
>> ::restart:/sbin/init
>> ::respawn:/bin/sh
>>
>> I've tried adding an "echo" command to the /etc/rc.sh script that is
>> called, but I don't see any output. I've also trying changing the
>> ::sysinit line in inittab to point to some non-existent script, to see
>> if I'll get some error message, but I still see nothing. Is it possible
>> that /sbin/init is dying before it gets to the point of reading inittab?
>> Any ideas?
>>
>> Regards,
>> Chris Dumoulin
>>
>>
>> Wolfgang Denk wrote:
>>
>> >In message <44888B92.40409@ics-ltd.com> you wrote:
>> >
>> >
>> >>I am using the linux kernel 2.6.15 and initrd ramdisk image from ELDK
>> >>4.0. Currently, I seem to be able to boot without errors, but after
>> the
>> >>root filesystem is mounted, things just stop.
>> >>
>> >>
>> >
>> >And what's your console device? Are you passing any console=
>> >arguments on the command line? Is the corresponding device entry
>> >present in the /dev/directory?
>> >
>> >Best regards,
>> >
>> >Wolfgang Denk
>> >
>> >
>> >
>>
>> --
>> *--Christopher Dumoulin--*
>> Software Team Leader
>>
>> <http://ics-ltd.com/>
>> <http://ics-ltd.com/>
>>
>> Interactive Circuits and Systems Ltd.
>> 5430 Canotek Road
>> Ottawa, ON
>> K1J 9G2
>> (613)749-9241
>> 1-800-267-9794 (USA only)
>>
>> ------------------------------------------------------------------------
>> This e-mail is private and confidential and is for the addressee only.
>> If misdirected, please notify us by telephone and confirm that it has
>> been deleted from your system and any hard copies destroyed. You are
>> strictly prohibited from using, printing, distributing or disseminating
>> it or any information contained in it save to the intended recipient.
>> _______________________________________________
>> Linuxppc-embedded mailing list
>> Linuxppc-embedded@ozlabs.org
>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>
>
--
*--Christopher Dumoulin--*
Software Team Leader
<http://ics-ltd.com/>
<http://ics-ltd.com/>
Interactive Circuits and Systems Ltd.
5430 Canotek Road
Ottawa, ON
K1J 9G2
(613)749-9241
1-800-267-9794 (USA only)
------------------------------------------------------------------------
This e-mail is private and confidential and is for the addressee only.
If misdirected, please notify us by telephone and confirm that it has
been deleted from your system and any hard copies destroyed. You are
strictly prohibited from using, printing, distributing or disseminating
it or any information contained in it save to the intended recipient.
next prev parent reply other threads:[~2006-06-09 19:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 20:41 help with inittab Chris Dumoulin
2006-06-08 20:49 ` Steve Iribarne (GMail)
2006-06-08 21:42 ` Wolfgang Denk
2006-06-09 2:11 ` Help -- failed to boot up kernel on PPC40 5 Denny
2006-06-09 7:40 ` Wolfgang Denk
2006-06-09 16:14 ` help with inittab Chris Dumoulin
2006-06-09 18:23 ` Steve Iribarne (GMail)
2006-06-09 19:14 ` Chris Dumoulin [this message]
2006-06-09 20:24 ` Steve Iribarne (GMail)
-- strict thread matches above, loose matches on Subject: below --
2006-06-09 19:19 Scott Coulter
2006-06-09 19:49 ` Chris Dumoulin
2006-06-12 2:02 ` David H. Lynch Jr.
2006-06-09 19:53 Scott Coulter
2006-06-09 20:43 ` Chris Dumoulin
[not found] <mailman.9.1150164003.18626.linuxppc-embedded@ozlabs.org>
2006-06-13 16:26 ` Anantharaman Chetan-W16155
2006-06-13 21:07 ` David H. Lynch Jr.
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=4489C8A9.1080401@ics-ltd.com \
--to=cdumoulin@ics-ltd.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=netstv@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.