Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ferry Toth <fntoth@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: zimage Initramfs booting stuck at Start Kernel
Date: Sat, 26 Oct 2019 23:20:31 +0200	[thread overview]
Message-ID: <de0e9a45-522a-be55-120a-b3cbd398ec6c@gmail.com> (raw)
In-Reply-To: <CAA=hcWTH9VCNgbDbU+ai3sydbWWKNR9HfnuGKu3oQ7XsHN6JBQ@mail.gmail.com>

Op 26-10-2019 om 11:46 schreef JH:
> Hi,
> 
> I finally built the
> zImage->zImage--4.19.75+git0+d573e8a79f-r0-20191026074920.bin and
> zImage-initramfs ->
> zImage-initramfs--4.19.75+git0+d573e8a79f-r0-20191026074920.bin based
> on oe-core kernel.bbclass.
> 
> The zImage could be loaded by u-boot on RAM booting but failed at
> mount rootfs which was fine as it did not bundle the rootfs. The
> zImage-initramfs bundled to rootfs, but it could not be started and
> stuck at u-boot Starting kernel, there was no trace of errors.
> 
> Hit any key to stop autoboot:  0
> => bootz ${loadaddr} - ${fdt_addr}
> Kernel image @ 0x80800000 [ 0x000000 - 0x219df80 ]
> ## Flattened Device Tree blob at 83000000
>     Booting using the fdt blob at 0x83000000
>     Using Device Tree in place at 83000000, end 83008831
> ft_system_setup for mx6
> 
> Starting kernel ...
> 
> Because zImage could be started, zImage-initramfs could not, that
> implies there were no issues in the u-boot, is must be something wrong
> with the zImage-initramfs. Seems debug is harder, are there anyway to
> extract information from zImage-initramfs to figure out what is wrong?

As an example you might want to look at my repo, I have 2 images minimal 
and initramfs:
https://github.com/edison-fw/meta-intel-edison/tree/master/meta-intel-edison-distro/recipes-core/images

I don't exactly know how you are doing it. But I'll try to explain what 
I do:
I have
1) a normal rootfs (say edison-image-minimal) and
2) a initramfs rootfs containing kernel modules needed for booting and a 
init script.

Initramfs is build using core-image-minimal-initramfs.bbappend. Some 
additional unneeded packages are pulled, and as size is restricted (10MB 
or so?) we remove them here.

The init script is here: 
https://github.com/edison-fw/meta-intel-edison/blob/master/meta-intel-edison-distro/recipes-core/initrdscripts/initramfs-framework/init

The init script loads modules, waits for the disk with the rootfs to 
appear and mount it. Then switchroot to it.
If it doesn't appear it drops to a shell so you can investigate what's 
wrong.

To build everything edison-image-minimal triggers build of u-boot, 
kernel, rootfs, initramfs and kernel-with-built-in-initramfs.

Search for 'init' and 'live' and find the needed lines in 
https://github.com/edison-fw/meta-intel-edison/blob/master/meta-intel-edison-distro/recipes-core/images/edison-image-minimal.bb

> Thank you.
> 
> Kind regards,
> 
> - jh
> 




  reply	other threads:[~2019-10-26 21:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-26  9:46 zimage Initramfs booting stuck at Start Kernel JH
2019-10-26 21:20 ` Ferry Toth [this message]
2019-10-27  0:27   ` JH
2019-10-27 12:24     ` Ferry Toth
2019-10-27 21:52       ` JH
2019-10-27 22:27         ` Ferry Toth
2019-10-28  2:02           ` JH
2019-10-28 20:46             ` Ferry Toth
2019-10-29  6:27               ` JH
2019-10-29 10:25               ` JH
2019-10-29 17:37                 ` Ferry Toth
2019-10-29 20:42                   ` JH

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=de0e9a45-522a-be55-120a-b3cbd398ec6c@gmail.com \
    --to=fntoth@gmail.com \
    --cc=openembedded-core@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