From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Starting from scratch fails - how do I get to a basic PXE boot?
Date: Fri, 13 Jul 2012 16:53:43 +0200 [thread overview]
Message-ID: <20120713165343.6c5a4d21@skate> (raw)
In-Reply-To: <07221C471CA1C044B6D10EC0D483C95708D3FE8B@hercules.clumpton.homeip.net>
Hello,
Le Fri, 13 Jul 2012 08:23:17 +0000,
"Bart J. Smit" <bart@smits.co.uk> a ?crit :
> I was under the impression from the on-line help that the BR2_LINUX_KERNEL_DEFCONFIG option had to specify one of the defconfig files from the configs directory.
You're confusing two things:
* The Buildroot defconfigs, which are stored in the configs/ directory
of Buildroot. These defconfigs are *Buildroot* configuration for
certain platforms.
* The kernel defconfigs, which are part of the kernel sources, and
available for each architecture in the arch/<ARCH>/configs/
directory of the kernel source tree. This is the defconfig that is
selected by BR2_LINUX_KERNEL_DEFCONFIG.
Now look at the available kernel defconfigs for x86:
$ ls arch/x86/configs/
i386_defconfig x86_64_defconfig
So basically, on x86, for a vanilla Linux kernel, your only choice for
BR2_LINUX_KERNEL_DEFCONFIG is "i386", and for x86_64, your only choice
is "x86_64".
> It now builds without error, but booting the VM from the resulting bzImage and rootfs.cpio.gz causes it to stall at the same point as before. Could this be because I haven't cleaned the config? Any thoughts on how to wipe the slate clean? Will make clean do the trick?
'make clean' cleans up everything. The next 'make' invocation will
therefore restart the build from scratch completely.
If the thing halts at:
Starting logging: ON
Initializing random number generator ... done.
Starting network ...
[ 2.227418] ip used greatest stack depth: 6392 bytes left
Then most likely the reason is that you have not properly configured
System configuration -> Port to run a getty (login prompt) on. You have
to figure out which serial port is used for the console of your
virtual machine, and set it in this configuration option.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-13 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.29648.1342161106.7700.buildroot@busybox.net>
2012-07-13 8:23 ` [Buildroot] Starting from scratch fails - how do I get to a basic PXE boot? Bart J. Smit
2012-07-13 14:53 ` Thomas Petazzoni [this message]
2012-07-12 10:54 Bart J. Smit
2012-07-12 22:13 ` Thomas Petazzoni
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=20120713165343.6c5a4d21@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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