On Thu, 27 Jan 2000, Matthew Browne wrote:

> At 12:47 PM -0800 on 26/1/2000, David A. Gatwood wrote:
> >
> > Well, MkLinux doesn't boot on those, at least not quite, but....  Off the
> > top of my head, the boot args contain something pretty close to the
> > following, but not in this order, I don't think):
> >
> > * Booter Version
> > * OF Tree (where applicable, zero height where not)
> > * Gestalt
> > * Boot arguments
> > * Memory regions
> > * VRAM base and size
> > * Addresses of kernel, bootstrap task, etc.
> >
> > I think that's about it....  Memory is mapped 1:1 with address translation
> > _on_.
> 
> Actually you've just reminded me of something else. The MkLinux
> booter is one of only two I've tried that's even comes close to
> booting my 6200 as it actually gets to booting the kernel. BootX
> just crashes. The only other one was the booter for PowerOS
> that was a MacOS application that used a workaround in the 68K
> emulator to get into supervisor mode. The page for that went
> down a few years back though AFAIK.

I've been looking back for messages from folks who mention an interest in
this family of machines and dropping them all notes.  For what it's worth,
I experienced the same thing w/ BootX on the 6214 I have beside me.  (Any
idea how to get the top cover off this thing, BTW?)

There's a quick two-line hack for this -- you can disable the code that
disables the MacOS video driver and the thing will start the kernel.  I'm
not saying it will run the kernel -- I haven't tried it since I got the
kernel booting -- but at least it will start the kernel.  ;-)


David

---------------------------------------------------------------------
A brief Haiku:

Microsoft is bad.
It seems secure at first glance.
Then you read your mail.