qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [6658] Update to OpenBIOS 1.0


From: Aurelien Jarno
Subject: Re: [Qemu-devel] [6658] Update to OpenBIOS 1.0
Date: Tue, 3 Mar 2009 22:06:18 +0100
User-agent: Mutt/1.5.18 (2008-05-17)

On Tue, Mar 03, 2009 at 10:47:56PM +0200, Blue Swirl wrote:
> On 3/3/09, Aurelien Jarno <address@hidden> 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.
> 

Version before r452 were already supporting -nographic, even if the
traffic was not redirected to the serial port automagically. Now if you
don't want a graphical output, the only solution is VNC.

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
address@hidden                 http://www.aurel32.net




reply via email to

[Prev in Thread] Current Thread [Next in Thread]