>Donald Lee <MacPPC@caution.icompute.com> writes:
>
>> I've tried the usual: (ofwboot.xcf and netbsd.try6 on HFS+ partition on HD)
>>
>> 0> setenv boot-device ultra0:,ofwboot.xcf
>> 0> setenv boot-file netbsd.try6
>> 0> setenv boot-command boot
>
>I did this on my PCI G4 a couple of weeks ago, and while I can't check
>it right now, I don't think I set boot-command away from the default;
>I just set boot-device and boot-file and auto-boot? to yes.

[snip] - see below

>> BTW - it's nice to be able to alternately boot back and forth between the
>> Mac OS HD and netbsd, since I have to build my kernel, and then move it
>> to the HFS partition to boot it.  unlike previous machines, MacOS doesn't
>> blow away the OF setup.
>
>Pain and suffering! ofwboot.xcf can read files from the netbsd
>partition; does that not work for you? ("boot hd:10,ofwboot.xcf
>hd:12/netbsd" or the like). Or netboot, but really, going back and
>forth shouldn't be necessary.

This works fine!  I changed boot-device to "ultra0:,ofwboot.xcf" and
the boot-file to "ultra0:10/netbsd".  boot-command is default (mac-boot).

When I cmd-opt-o-f it, and then type "boot", it comes right up.  I
no longer have to copy the kernel back to the HFS partition.

Cool!

Unfortunately, I still can't auto-boot.

When I set it up as described, and type "boot", it comes up.
When I change auto-boot? to true, I get a solid white or black
screen and an apparent hang.

I tried a couple of experiments.  One, I tried a different graphics card -
an ATI Radeon 8500 - and it didn't seem to help.  (It was a little hard to be
sure, as the monitor didn't sync up, but it still didn't auto-boot, and
I could type in the commands and get expected behavior)

My second experiment was more interesting.  On the theory that
the problem was in the OF init of some sort, I changed the
boot-command to "500 ms boot".  This yielded slightly different
behavior.  Now  on auto-boot I get a grey screen, and then the white
screen with the hang.

Ideas anyone?

-dgl-