From: Blue Swirl <blauwirbel@gmail.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [6658] Update to OpenBIOS 1.0
Date: Tue, 3 Mar 2009 22:47:56 +0200 [thread overview]
Message-ID: <f43fc5580903031247o2348452aib598ab99d52b7667@mail.gmail.com> (raw)
In-Reply-To: <20090303090926.GA9043@volta.aurel32.net>
On 3/3/09, Aurelien Jarno <aurelien@aurel32.net> wrote:
> On Sun, Mar 01, 2009 at 08:18:10PM +0000, Blue Swirl wrote:
> > Revision: 6658
> > http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6658
> > Author: blueswir1
> > Date: 2009-03-01 20:18:09 +0000 (Sun, 01 Mar 2009)
> > Log Message:
> > -----------
> > Update to OpenBIOS 1.0
> >
> > Modified Paths:
> > --------------
> > trunk/pc-bios/README
> > trunk/pc-bios/openbios-ppc
> > trunk/pc-bios/openbios-sparc32
> > trunk/pc-bios/openbios-sparc64
> >
>
>
> It looks like this version has a problem with -nographic on the g3beige
> and mac99 machines. It is reproducible with the installation CD from
> Debian Etch and Lenny. Yaboot outputs a prompt, but as soon as the
> kernel tries to boot, I get:
>
> Please wait, loading kernel...
> Elf32 kernel loaded...
> Loading ramdisk...
> ramdisk loaded at 01900000, size: 3807 Kbytes
> invalid/unsupported opcode: 00 - 00 - 00 (00000000) fff18f00 1
> invalid/unsupported opcode: 00 - 00 - 00 (00000000) fff18f04 1
> invalid/unsupported opcode: 00 - 0c - 06 (00009198) 00009214 0
I can reproduce this, but -nographic support for PPC was added in
r452 and even that version behaves the same way. Strange bug, though.
next prev parent reply other threads:[~2009-03-03 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 20:18 [Qemu-devel] [6658] Update to OpenBIOS 1.0 Blue Swirl
2009-03-03 9:09 ` Aurelien Jarno
2009-03-03 11:03 ` Alexander Graf
2009-03-03 20:47 ` Blue Swirl [this message]
2009-03-03 21:06 ` Aurelien Jarno
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=f43fc5580903031247o2348452aib598ab99d52b7667@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=aurelien@aurel32.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).