Isobel wrote:
> // blahblah genre Copright California =A91515-2786.
> // ...
> CPU 7400 (revision 207)
> total mem : 128
> available mem : 111
> using 1664 /*comme la biere*/ buffer containing 6656 Kb of memory
> mainbus0 (root)
> CPU at mainbus0 : 1Mb backside cache
> md0 : internal 2048K iamge area
> bootdevice : unknown
> root filesystem type : ffs

	The key here is that the kernel output was *WAY* too short..  =)  The
kernel you're using didn't detect the northbridge on the Sawtooth, a
chip called "uni-north".  Support for this chip was added just a few
months ago, but unfortunately it was a week after the last snapshot was
built.  I hope Tsubai doesn't mind me pointing this out, but he has a
kernel on his site that should work with uni-north based machines:

ftp://nandra.iri.co.jp/pub/NetBSD/macppc/netbsd.md.gz

	(Maybe it'll help get a new snapshot built, or at least this file moved
to ftp.netbsd.org..  =)

	ofwboot.elf should be able to decompress and load this file.  I was
never able to get ofwboot.elf to boot something off a HFS partition on a
zip disk, so you've obviously had better luck than me..  =)  Otherwise
you should be able to un .gz the file with StuffIt Expander, and boot it
directly from Open Firmware (boot zip:netbsd.md), though you don't get
the symbol table that way (not a big deal for the first boot IMO).

> the the screens changes to a MacOS one, showinf an MacOS icon in a little
> box in the middle of the screen, and, under it, the MacOS boot-device e.g.
> 
>         /pci@f2000000/pci-bridge@d/mac-io@7/ata-4@1f000/@0:9,\\:tbxi

	This one has baffled me on my Blue&White G3.  This only changed in the
last few months, previously "halt", "halt -p", and "reboot" all did
their respective Right Thing's.  Recently it seems all of these commands
dump me back into Open Firmware, which then tries to actually boot
MacOS, and fails (likely because memory has been thorougly garbled from
what OFW expected).  It's unfortunate because it means I can't reboot my
Blue&White without being in front of it now, but fortunately it's not
something I do very often.  It seems we're not actually getting the
reboot or powerdown commands off to the PMU anymore, or something else
has gone wrong.  Anyway it means you're stuck in Open Firmware, if
you're lucky you might be able to hit ctrl-Z and type "reset-all" to
reboot the machine, otherwise you're stuck hitting the reset button on
the front of the machine (if OF isn't too far gone the keyboard power
button might work to shut off the machine, at least on my Blue&White USB
is completely dead on return to OF, so my only option is to hit the
reset button).

	Hope that helps.
                                     Will