Bug 1071 - beagleboard: core-lsb-sdk no login prompt
Summary: beagleboard: core-lsb-sdk no login prompt
Status: RESOLVED DUPLICATE of bug 1131
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 1.0
Hardware: Beagleboard arm
: High major
Target Milestone: 1.1 M2
Assignee: Darren Hart
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2011-05-14 10:33 UTC by Robert Berger
Modified: 2011-06-02 15:22 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Berger 2011-05-14 10:33:23 UTC
The latest and greatest poky from git (commit 65e5ebc1d27b0a6cb2e33596d6d32c536b857f0d) is able to produce a core-lsb-sdk rootfs, but if you try to run this on a beagle-xm it gets stuck and you don't get a login prompt

...
INIT: Id "S" respawning too fast: disabled for 5 minutes
...

Here are more details:

http://pastebin.com/TgHVcrTV
Comment 1 Robert Berger 2011-05-14 12:32:08 UTC
This seems to happen also with core-sato-sdk

commit 8b6416db1e04af83ecdf57522240ac859d5d8031 building a poky-sato-sdk gets you to login screen:

http://pastebin.com/BJi3D6K2

If you use the latest and greatest from git
(commit 65e5ebc1d27b0a6cb2e33596d6d32c536b857f0d) building a core-sato-sdk

The first time you run it will do this:
http://pastebin.com/tWhv6nnR

Which means it will stuck again with:
...
INIT: Id "S" respawning too fast: disabled for 5 minutes
...

maybe something was breaking here since yesterday, since I'm pretty sure that with the latest and greatest from yesterday core-sato-sdk worked.
Comment 2 Robert Berger 2011-05-16 00:46:47 UTC
further investigation shows that something goes wrong in the init scripts and /etc/inittab contains the wrong console.

S:2345:respawn:/sbin/getty 115200 ttyO2

should help
Comment 3 Darren Hart 2011-06-02 15:22:57 UTC
1131 was created later, but managed to get more attention. Marking this a dup of that.

*** This bug has been marked as a duplicate of bug 1131 ***