Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf_samuelsson@telia.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: console-image: No login prompt
Date: Sun, 30 Oct 2011 01:05:33 +0200	[thread overview]
Message-ID: <4EAC86BD.9040903@telia.com> (raw)
In-Reply-To: <4EAC810B.8010302@telia.com>

2011-10-30 00:41, Ulf Samuelsson skrev:
> 2011-10-30 00:36, Ulf Samuelsson skrev:
>> Have build console-image and I am running it on an AT91SAM9G20EK.
>> The boot process freezes, and I have managed to verify that this
>> happens after the init process has executed "finished.sh".
>> (Put some print statements in this, and I see them)
>>
>> Then nothing...
>> Normally I would get a login prompt
>
> Is this somehow redirected to the non-existant screen?

A little futher.
If I enable SULOGIN and from SULOGIN do:

$ init 2

I get the login prompt,
but SULOGIN uses the same serial line, so things get mixed up.

It definitely looks like the system never leaves level 1 - why?



>
>>
>> Have been searching for people with similar problems,
>> and I found one that claimed that /etc/rcS.d/S03udev
>> needs to run after /etc/rcS.d/S10checkout.
>>
>> I tried this but this does not make any difference.
>> Is there some configuration item that enables/disables the console
>> after init.
>>
>> finish.sh is linked from rcS.d/S99/finish.sh
>>
>> Is the problem, that the kernel stays in level 1 for some reason?
>> Default run level is 5 (id:5:initdefault:) which I assume
>>
>> Does that make sense for a console-image?
>>
>> Should not level 3 be more appropriate if
>> you do not have any graphics?
>>
>> Any reason why console I/O is redirected?
>>
>> ------------------------------------------------------------------------------------ 
>>
>> # /etc/inittab: init(8) configuration.
>> # $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $
>>
>> # The default runlevel.
>> id:5:initdefault:
>>
>> # Boot-time system configuration/initialization script.
>> # This is run first except when booting in emergency (-b) mode.
>> si::sysinit:/etc/init.d/rcS
>>
>> # What to do in single-user mode.
>> ~~:S:wait:/sbin/sulogin
>>
>> # /etc/init.d executes the S and K scripts upon change
>> # of runlevel.
>> #
>> # Runlevel 0 is halt.
>> # Runlevel 1 is single-user.
>> # Runlevels 2-5 are multi-user.
>> # Runlevel 6 is reboot.
>>
>> l0:0:wait:/etc/init.d/rc 0
>> l1:1:wait:/etc/init.d/rc 1
>> l2:2:wait:/etc/init.d/rc 2
>> l3:3:wait:/etc/init.d/rc 3
>> l4:4:wait:/etc/init.d/rc 4
>> l5:5:wait:/etc/init.d/rc 5
>> l6:6:wait:/etc/init.d/rc 6
>> # Normally not reached, but fallthrough in case of emergency.
>> z6:6:respawn:/sbin/sulogin
>> S:2345:respawn:/sbin/getty 115200 ttyS0
>>
>>
>>
>>
>>
>
>


-- 
Best Regards
Ulf Samuelsson




  reply	other threads:[~2011-10-29 23:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-29 22:36 console-image: No login prompt Ulf Samuelsson
2011-10-29 22:41 ` Ulf Samuelsson
2011-10-29 23:05   ` Ulf Samuelsson [this message]
2011-10-30 19:07     ` Ulf Samuelsson

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=4EAC86BD.9040903@telia.com \
    --to=ulf_samuelsson@telia.com \
    --cc=openembedded-devel@lists.openembedded.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