Bug 1475 - runqemu with nographic option doesn't display early boot messages
Summary: runqemu with nographic option doesn't display early boot messages
Status: RESOLVED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.2 M4
Assignee: Scott Garman
QA Contact:
URL:
Whiteboard: (P3) 2012-03-29: Merged to master
Depends on:
Blocks:
 
Reported: 2011-09-13 14:18 UTC by Mark Hatle
Modified: 2012-03-29 21:58 UTC (History)
4 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Hatle 2011-09-13 14:18:50 UTC 
The runqemu script, when run with the nographic option (qemux86) does not display the kernel boot messages.

By adding:

 bootparams="earlyprintk=ttyS0 console=ttyS0"

I was able to restore access to those early boot messages.


Reproducer:

../scripts/runqemu qemux86 core-image-minimal nographic

vs

../scripts/runqemu qemux86 core-image-minimal nographic bootparams="earlyprintk=ttyS0 console=ttyS0"
Comment 1 Darren Hart 2011-09-13 14:28:28 UTC 
earlyprintk probably shouldn't be on by default, but "--append='console=ttyS0'" probably makes sense to add when running without graphics. If we want to wrap qemu entirely, then some kind of a -text option to the top level script might be ideal.
Comment 2 Scott Garman 2012-03-29 21:58:23 UTC 
Fix included in oe-core and poky master as of:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=3af7e95d69d29f1a5f79e60adfd4db7bd3c4570d