From: Ferry Toth <fntoth@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: public-openembedded-core-ZwoEplunGu3dfDuKDZ/zN51Ccm5ICvs9@plane.gmane.org,
public-public-openembedded-core-ZwoEplunGu3dfDuKDZ/zN51Ccm5ICvs9-wOFGN7rlS/M9smdsby/KFg@plane.gmane.org
Subject: Re: zimage Initramfs booting stuck at Start Kernel
Date: Tue, 29 Oct 2019 18:37:55 +0100 [thread overview]
Message-ID: <c66d5833-ffb1-327d-6297-ca41c5dcfd59@gmail.com> (raw)
In-Reply-To: <CAA=hcWTucG_LwdAPBX4AA3wAv44Y-h3zqEMn9af8pWEQQFG8tg@mail.gmail.com>
Op 29-10-2019 om 11:25 schreef JH:
> Hi Ferry,
>
> On 10/29/19, Ferry Toth <fntoth@gmail.com> wrote:
>>
>> https://github.com/edison-fw/meta-intel-edison/blob/master/meta-intel-edison-bsp/conf/machine/edison.conf
>>
>> And there is the max size!
>
> Are you able to run u-boot to start kernel in the large size 64 MB?
No, the largest I had was 18MB compressed and it didn't boot. After I
brought it back to 10MB or so it boots again. Like I said, I don't know
where the limit comes from.
I think you should be able to make the initramfs minimal and put the
rest in a separate file system same as I do and your problem will be
solved. But it looks like if you want to trace the root cause and solve
it, you are on your own.
> Thank you.
>
> Kind regards,
>
> - jh
>
next prev parent reply other threads:[~2019-10-29 17:38 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
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 [this message]
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=c66d5833-ffb1-327d-6297-ca41c5dcfd59@gmail.com \
--to=fntoth@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=public-openembedded-core-ZwoEplunGu3dfDuKDZ/zN51Ccm5ICvs9@plane.gmane.org \
--cc=public-public-openembedded-core-ZwoEplunGu3dfDuKDZ/zN51Ccm5ICvs9-wOFGN7rlS/M9smdsby/KFg@plane.gmane.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