qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: "M. Warner Losh" <imp@bsdimp.com>
Cc: alex@csgraf.de, steven@uplinklabs.net, openbios@openbios.org,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [OpenBIOS] QEMU OpenBIOS booting?
Date: Mon, 20 Apr 2009 22:39:12 +0300	[thread overview]
Message-ID: <f43fc5580904201239x530f787ate4e9cce7f471cc9c@mail.gmail.com> (raw)
In-Reply-To: <20090419.171812.439561624.imp@bsdimp.com>

On 4/20/09, M. Warner Losh <imp@bsdimp.com> wrote:
> In message: <f43fc5580904191144y1fd8e4d6m3321855d0c558250@mail.gmail.com>
>             Blue Swirl <blauwirbel@gmail.com> writes:
>
> : On 4/19/09, M. Warner Losh <imp@bsdimp.com> wrote:
>  : > In message: <f488382f0904190128l4383a56eu67a2f16eb338e61c@mail.gmail.com>
>  : >
>  : >             Steven Noonan <steven@uplinklabs.net> writes:
>  : >  : I eventually decided it made more
>  : >  : sense to get QEMU working instead. I did notice that the pre-OpenBIOS
>  : >  : version of QEMU was able to boot Mac OS X via Open Hack'Ware, so I was
>  : >  : annoyed to find that OpenBIOS didn't have such support. So, I might as
>  : >  : well add it.
>  : >
>  : >
>  : > Open Hackware was barely enough to boot older versions of Linux.
>  : >  Other operating systems that needed more extensive properties from the
>  : >  OpenFirmware device tree failed to boot because they weren't present.
>  : >  I was involved in a large effort to get FreeBSD/powerpc booting on
>  : >  QEMU only to have it fail utterly because the amount of hacking on
>  : >  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=0x4a4ce0+0x3d4e4 syms=[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...

Right, the error comes from this line:
http://fxr.watson.org/fxr/source/powerpc/powerpc/mmu_oea.c?v=FREEBSD70#L825

  reply	other threads:[~2009-04-20 19:39 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f488382f0904111806i64421ff8t68e6d34aa2990f3a@mail.gmail.com>
     [not found] ` <1239525550.5516.3.camel@Quad>
     [not found]   ` <f488382f0904142246ga431e99obe666b7fb16adb02@mail.gmail.com>
     [not found]     ` <f488382f0904190050x1d6e9562sf000e9e9763735b7@mail.gmail.com>
2009-04-19  8:03       ` [Qemu-devel] Re: [OpenBIOS] QEMU OpenBIOS booting? Andreas Färber
2009-04-19  8:28         ` Steven Noonan
2009-04-19  9:44           ` Andreas Färber
2009-04-19 17:47           ` M. Warner Losh
2009-04-19 17:56             ` Steven Noonan
2009-04-19 18:44             ` Blue Swirl
2009-04-19 23:18               ` M. Warner Losh
2009-04-20 19:39                 ` Blue Swirl [this message]
2009-04-20 21:01                   ` François Revol
2009-04-20 22:15                   ` [OpenBIOS] [Qemu-devel] " Laurent Vivier
2009-04-19  8:31         ` [Qemu-devel] Re: [OpenBIOS] " Laurent Vivier
2009-05-20 13:51           ` Dave Willoughby
2009-05-20 14:14             ` Alexander Graf
     [not found]       ` <1240129450.5671.7.camel@Quad>
2009-04-19 18:59         ` [Qemu-devel] " Steven Noonan
2009-04-19 19:23           ` [Qemu-devel] Re: [OpenBIOS] " Blue Swirl
2009-04-19 20:00             ` Steven Noonan
2009-04-19 20:08               ` Laurent Vivier
2009-04-19 20:14                 ` Steven Noonan
2009-04-19 20:24                   ` Laurent Vivier
2009-04-19 20:33                     ` Steven Noonan
2009-04-19 20:48                       ` Laurent Vivier
2009-04-19 21:02                         ` Steven Noonan
2009-04-19 21:32                           ` Steven Noonan
2009-04-19 22:28                             ` Steven Noonan
2009-04-19 22:36                               ` Steven Noonan
2009-04-20  0:15                                 ` malc
2009-04-20  3:27                                 ` Steven Noonan
2009-04-20  3:50                                   ` Steven Noonan
2009-04-26  8:13                                     ` Alexander Graf
2009-04-19 19:47           ` Laurent Vivier
2009-04-19 19:53             ` Steven Noonan
2009-04-19 20:01             ` Steven Noonan
2009-04-19 20:21               ` Laurent Vivier
2009-04-19 20:23                 ` Steven Noonan
2009-04-19 20:29                   ` Laurent Vivier
2009-04-20  9:39 Laurent Vivier

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=f43fc5580904201239x530f787ate4e9cce7f471cc9c@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=alex@csgraf.de \
    --cc=imp@bsdimp.com \
    --cc=openbios@openbios.org \
    --cc=qemu-devel@nongnu.org \
    --cc=steven@uplinklabs.net \
    /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).