From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Finn Thain <fthain@linux-m68k.org>, mark.cave-ayland@ilande.co.uk
Cc: Stan Johnson <userm57@yahoo.com>,
mpe@ellerman.id.au, npiggin@gmail.com,
christophe.leroy@csgroup.eu, sam@ravnborg.org,
benh@kernel.crashing.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, rdunlap@infradead.org,
Cedar Maxwell <cedarmaxwell@mac.com>
Subject: Re: QEMU limitations, was Re: [PATCH v4] powerpc: Use shared font data
Date: Wed, 5 Nov 2025 14:58:10 +0000 [thread overview]
Message-ID: <aQtmAjvkD9CzzIJH@gallifrey> (raw)
In-Reply-To: <492c13c9-666c-9578-6c66-0eb8fefc93dc@linux-m68k.org>
(Copying Mark Cave-Ayland in - see below)
* Finn Thain (fthain@linux-m68k.org) wrote:
>
> On Mon, 3 Nov 2025, Finn Thain wrote:
>
> > > OK, remember I don't think I've ever tried PPC via MacOS booting, so
> > > not familiar with it.
> > >
> >
> > I will try to set up a MacOS guest in QEMU, to see if the hang can be
> > reproduced that way.
> >
>
> QEMU appears to be incompatible with the Old World ROM from the Beige G3.
> 'qemu-system-ppc -M g3beige -bios 78F57389.ROM -serial stdio' drops into a
> ROM diagnostic menu and won't boot.
>
> I did get 'qemu-system-ppc -M mac99 ...' to boot into MacOS 9, by using
> OpenBIOS instead of Apple firmware. Unforunately, BootX is not compatible
> with this configuration, so it won't help.
>
> BootX is compatible with beige powermacs, but 'qemu-system-ppc -M g3beige'
> with OpenBIOS fails to boot MacOS 9 ("MacOS: unable to find an interrupt
> controller node").
>
> OpenBIOS wouldn't boot a MacOS 8.1 CD-ROM either, but for different
> reasons: both mac99 and g3beige failed with "No valid state has been set
> by load or init-program".
Thanks for trying,
I've copied Mark Cave-Ayland from Qemu in; he's down as the g3beige
maintainer in qemu, he might have a hint.
Dave
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2025-11-05 14:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 14:27 [PATCH v4] powerpc: Use shared font data linux
2023-09-30 13:15 ` Dr. David Alan Gilbert
2023-10-01 12:08 ` Michael Ellerman
2023-10-02 12:21 ` Dr. David Alan Gilbert
2023-10-15 10:04 ` Michael Ellerman
2025-11-02 5:02 ` Stan Johnson
2025-11-02 11:20 ` Finn Thain
2025-11-02 17:09 ` Dr. David Alan Gilbert
2025-11-02 19:01 ` Stan Johnson
2025-11-03 1:33 ` Finn Thain
2025-11-03 1:48 ` Dr. David Alan Gilbert
2025-11-03 7:26 ` Finn Thain
2025-11-04 17:59 ` Dr. David Alan Gilbert
2025-11-04 19:49 ` Stan Johnson
2025-11-04 21:59 ` Dr. David Alan Gilbert
2025-11-05 4:13 ` QEMU limitations, was " Finn Thain
2025-11-05 14:58 ` Dr. David Alan Gilbert [this message]
2025-11-05 21:44 ` Christophe Leroy
2025-11-05 23:48 ` Finn Thain
2025-11-06 4:11 ` Finn Thain
2025-11-06 9:28 ` Christophe Leroy
2025-11-06 11:50 ` Finn Thain
2025-11-06 12:07 ` Dr. David Alan Gilbert
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=aQtmAjvkD9CzzIJH@gallifrey \
--to=linux@treblig.org \
--cc=benh@kernel.crashing.org \
--cc=cedarmaxwell@mac.com \
--cc=christophe.leroy@csgroup.eu \
--cc=fthain@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=rdunlap@infradead.org \
--cc=sam@ravnborg.org \
--cc=userm57@yahoo.com \
/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