Re: Boot problems for OpenBSD 3.2 on Mac IIci

David de Groot wrote:

> I installed OpenBSD 3.2/mac68k on an old Mac IIci I had lying around as
> per the install instructions. After 7 hours or so, 

in case any non-mac68k users are listening in, he ain't kidding. 8-)

> all the packages
> were installed, the device nodes created, and it was ready to boot.
> 
> I ran up the Booter and selected the correct SCSI ID for my hard disk
> (ID 4), changed the kernel name to bsd (/bsd as it says in the install
> doc does not work). I tell it to boot, hit ok on the prompt when it
> comes up (the one asking whether to boot or not) and then the screen
> switches to framebuffer mode and displays the following:
> 
> [ using 380362 bytes of bsd a.out symbol table ]
> Bootstrapping OpenBSD/mac68k.
> Getting mapping from MMU.
> System RAM: 33226752 bytes in 8112 pages.
>            Low = 0x4000000, high = 0x4ff8000
>            Low = 0x50000, high = 0x1000000
>            Low = 0x4ff8000, high = 0x5000000
>      Video address = 0xfbb08000
>      Int video starts at 0xfbb08000
>      Length = 0x50000 (327680) bytes
> Done.
> Bootstrapping the pmap system.
> 
> And that's where it stops.
> 
> I've removed the 24 bit Video card that was in there and am now using
> the builtin video, but get the same results.
> I have left it in this state for several hours to see if anything
> happens (this box is incredibly slow compared to my iBook), but alas,
> no go.

"incredibly slow" -- you are kind. 8-/

I've had less than good success with the mac68k port on 030 machines
lately, though I REALLY think you should be getting a lot further than
THAT (and I'd have more hope for a IIci than any other 030 system). 
It looks like it is hanging on first load of the kernel, so I'm
suspecting more than a compatability problem.

1) Could you have the wrong file?  I'm thinking wrong platform (i.e.,
trying to boot a hp300 or i386), 

2) Could the file have got mangled?  Possibly by an FTP as a
non-binary file ('fetch' on MacOS didn't "guess" right on .tgz or
tar.gz files in my experience).

Something in the back of my head is saying the installer is really,
really stupid and would install a corrupted file on /, but I can't
remember why I think this.  (I'm thinking I once tried to install a
/bsd that wasn't in .tar.gz form, and it installed, but it refused to
boot...not sure, though.)

Basicly, reload bsd-generic.tar.gz, see if anything different
happens.  If not, try installing an older copy of bsd-generic.tar.gz,
that will give us some idea if it is a compatability issue.  Try going
back to 3.0 or even 2.9's kernel.

Let me know what you find...

Nick.
-- 
http://www.holland-consulting.net