From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lw1lu-0003X1-54 for qemu-devel@nongnu.org; Mon, 20 Apr 2009 18:15:26 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lw1lp-0003Uv-DM for qemu-devel@nongnu.org; Mon, 20 Apr 2009 18:15:25 -0400 Received: from [199.232.76.173] (port=53931 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lw1lp-0003Us-Ak for qemu-devel@nongnu.org; Mon, 20 Apr 2009 18:15:21 -0400 Received: from moutng.kundenserver.de ([212.227.126.186]:55946) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Lw1lo-0006Wt-RF for qemu-devel@nongnu.org; Mon, 20 Apr 2009 18:15:21 -0400 Subject: Re: [OpenBIOS] [Qemu-devel] Re: QEMU OpenBIOS booting? From: Laurent Vivier In-Reply-To: References: <20090419.114724.-1622542522.imp@bsdimp.com> <20090419.171812.439561624.imp@bsdimp.com> Content-Type: text/plain; charset=utf-8 Date: Tue, 21 Apr 2009 00:15:06 +0200 Message-Id: <1240265706.5728.3.camel@Quad> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: The OpenBIOS Mailinglist Cc: alex@csgraf.de, steven@uplinklabs.net, qemu-devel@nongnu.org Le lundi 20 avril 2009 =C3=A0 22:39 +0300, Blue Swirl a =C3=A9crit : > On 4/20/09, M. Warner Losh wrote: > > In message: > > Blue Swirl writes: > > > > : On 4/19/09, M. Warner Losh wrote: > > : > In message: > > : > > > : > Steven Noonan writes: > > : > : I eventually decided it made more > > : > : sense to get QEMU working instead. I did notice that the pre-Op= enBIOS > > : > : version of QEMU was able to boot Mac OS X via Open Hack'Ware, s= o I was > > : > : annoyed to find that OpenBIOS didn't have such support. So, I m= ight as > > : > : well add it. > > : > > > : > > > : > Open Hackware was barely enough to boot older versions of Linux. > > : > Other operating systems that needed more extensive properties fro= m the > > : > OpenFirmware device tree failed to boot because they weren't pres= ent. > > : > I was involved in a large effort to get FreeBSD/powerpc booting o= n > > : > QEMU only to have it fail utterly because the amount of hacking o= n > > : > OpenHackWare needed was rather large and mysterious... > > : > > : This is what I get with OpenBIOS: > > : >> *** Boot failure! No secondary bootloader specified *** > > : > > : 0 > boot cd:,\boot\loader cd:0 > > : Consoles: Open Firmware console > > : > > : FreeBSD/Open Firmware/PowerPC bootstrap loader, Revision 0.1 > > : (root@xserve.lan.xcllnt.net, Thu Apr 16 18:47:58 UTC 2009) > > : Memory: 131072KB > > : Booted from: cd > > : > > : Loading /boot/defaults/loader.conf > > : /boot/kernel/kernel data=3D0x4a4ce0+0x3d4e4 syms=3D[0x4+0x454f0+0x4+= 0x5a4b9] > > : / > > : Hit [Enter] to boot immediately, or any other key for command prompt= . > > : Booting [/boot/kernel/kernel]... > > : Kernel entry at 0x13dac0 ... > > : panic: moea_bootstrap: no space to copy translations > > : Uptime: 1s > > > > > > That's similar to the one that I've seen as well. The problem with > > this one, IIRC, is that FreeBSD/powerpc is trying to setup the memory > > translations for the MMU and the 'translations' property length is > > zero, or something like that... >=20 > Right, the error comes from this line: > http://fxr.watson.org/fxr/source/powerpc/powerpc/mmu_oea.c?v=3DFREEBSD70#= L825 I think '/memory/available' is badly encoded and doesn't reflect the actual memory availability.. Regards, Laurent