From: BALATON Zoltan <balaton@eik.bme.hu>
To: Ben Hekster <ben.hekster@foghorn.io>
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] Booting Raspbian on RPi emulation
Date: Tue, 18 Dec 2018 23:34:10 +0100 (CET) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.1812182314450.71625@zero.eik.bme.hu> (raw)
In-Reply-To: <83206F6D-0BA5-4781-8635-84D48DD33A2A@foghorn.io>
On Tue, 18 Dec 2018, Ben Hekster via Qemu-devel wrote:
> I had the exact same issue; for me it was just the addition of Günther's "rootwait" option that resolved it, so:
>
> $ qemu-system-arm \
> -m 256m \
> -M raspi2 \
> -cpu cortex-a7 \
> -append "console=ttyAMA0,115200 root=/dev/mmcblk0p2 rootwait rw" \
> -dtb bcm2709-rpi-2-b.dtb \
> -drive file=2018-11-13-raspbian-stretch-lite.img,if=sd,format=raw \
> -kernel kernel7.img \
> -nographic
>
> Did it for me using stock QEMU 3.1.0. (I need "-nographic" because the OS X port crashes without it)
Indeed. Thanks. It also boots with the raspbian kernel7.img after adding
this option, so likely the cause of this was that mmc wasn't detected fast
enough and without rootwait it tried to mount it without waiting before
it was available.
It does not crash on OS X for me even without -nographic but I'm not yet
on Mojave. I've read there may be problems on latest macOS and seen
patches to fix that. Here's the discussion:
https://bugs.launchpad.net/qemu/+bug/1802684
Launchpad seems to have eaten the RFC patch URL in the last comment but I
think it's this one:
http://patchew.org/QEMU/20181201123056.432-1-peter.maydell@linaro.org/
Maybe you can test and report back if this fixes your problem so it can be
merged if it helps.
Thank you,
BALATON Zoltan
next prev parent reply other threads:[~2018-12-18 22:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 21:53 [Qemu-devel] Booting Raspbian on RPi emulation Ben Hekster
2018-12-18 22:34 ` BALATON Zoltan [this message]
2018-12-19 13:17 ` Peter Maydell
2018-12-19 17:46 ` Ben Hekster
2018-12-19 18:43 ` Peter Maydell
2018-12-19 19:36 ` Ben Hekster
2018-12-19 19:42 ` Ben Hekster
2018-12-20 2:14 ` BALATON Zoltan
2019-01-27 19:27 ` Peter Maydell
2019-01-27 23:13 ` BALATON Zoltan
2019-01-28 10:24 ` Peter Maydell
2019-01-28 15:30 ` BALATON Zoltan
-- strict thread matches above, loose matches on Subject: below --
2018-11-29 20:29 BALATON Zoltan
2018-11-30 0:43 ` Philippe Mathieu-Daudé
2018-11-30 1:27 ` Guenter Roeck
2018-11-30 2:42 ` BALATON Zoltan
2018-11-30 3:39 ` Guenter Roeck
2018-11-30 12:36 ` BALATON Zoltan
2019-01-15 18:29 ` BALATON Zoltan
2019-01-15 18:54 ` Philippe Mathieu-Daudé
2019-03-04 17:58 ` BALATON Zoltan
2019-08-20 14:50 ` BALATON Zoltan
2019-08-20 15:14 ` Philippe Mathieu-Daudé
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=alpine.BSF.2.21.9999.1812182314450.71625@zero.eik.bme.hu \
--to=balaton@eik.bme.hu \
--cc=ben.hekster@foghorn.io \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.