From: andre@osku.de (Andre Schmidt)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Minimum build config for boot messages
Date: Fri, 19 Aug 2016 16:17:22 +0200 [thread overview]
Message-ID: <20160819161722.24f7c4c1@foobaer> (raw)
Hello,
what is the minimum config to build a linux kernel that just prints boot messages/errors?
I was going through my old experiments/notes and found that we used to get kernel boot message with vanilla allnoconfig.
make ARCH=x86_64 allnoconfig
make all
qemu-system-x86_64 -kernel arch/x86/boot/bzImage
Those commands above used to be enough, but now the produced kernel doesn't print any messages on the qemu screen.
With some trial-and-error i was able to track down this commit
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/init/Kconfig?id=5d2acfc7b974bbd3858b4dd3f2cdc6362dd8843a
and if i add CONFIG_EMBEDDED=n to my KCONFIG_ALLCONFIG file, i can see kernel errors again.
I didn't investigate further cause i don't really know what i'm doing, but do wonder:
Can you reproduce this?
Is this (now) expected behavior?
(and it was luck before, to get kernel messages with vanilla allnoconfig)
Do we (now) need some specific option to enable kernel messages with allnoconfig?
(CONFIG_EMBEDDED=n sounds pretty generic and doesn't feel right)
Am i doing it all wrong? :D
Curiously,
Andre Schmidt
ps. i'm aware of defconfig, but i would like to experiment/learn from bottom-up, rather than top-down.
next reply other threads:[~2016-08-19 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 14:17 Andre Schmidt [this message]
2016-08-22 16:49 ` Minimum build config for boot messages John de la Garza
2016-08-22 18:50 ` Johannes Thoma
2016-08-23 12:56 ` Andre Schmidt
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=20160819161722.24f7c4c1@foobaer \
--to=andre@osku.de \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).