ofwboot.xcf fails to load kernel from MS-DOS formated USB-memory (OpenFirmware 3)

[Adrian Christiansen <adrian.christiansen%gmail.com@localhost>]

I'm trying to install NetBSD 5.1 onto my eMac 1GHz ATi from a MS-DOS
formatted USB-memory (formatted using mkfs -t msdos in Debian). I've
copied ofwboot.xcf onto the root of the USB-memory from
/macppc/installation/ on the installation CD. Then copied
netbsd-INSTALL.gz kernel from /macppc/binary/kernel into the root and
renaming it to netbsd.gz.
As I've understood it ofwboot.xcf will look after netbsd and netbsd.gz
on the same MS-DOS partition it was loaded from.

While I can get ofwboot.xcf to load from OpenFirmware, I can't get it
to load the kernel. This is how I loaded ofwboot.xcf:

0 > dev usb1    ok
0 > ls
ff9b6670: /disk@1
 ok
0 > dir usb1/disk@1:,\
        58800   11-06-2010 17:09:36 OFWBOOT.XCF
        2244369 11-06-2010 17:09:36 NETBSD.GZ
 ok
0 > boot usb1/disk@1:,\ofwboot.xcf netbsd.gz load-size=e5b0 adler32=a4eaf5e4

loading XCOFFF

tsize=e270 dsoze=260 bsize=2730 entry=e00000
SECTIONS:
.text   00e00000 00e00000 0000e270 000000e0
.data   00e0f000 00e0f000 00000260 0000e350
.bss    00e0f260 00e0f260 00002730 00000000
loading .text, done..
loading .data, done..
clearing .bss, done..

>> NetBSD/macppc OpenFirmware Boot, Revision 1.11
>> (builds%b7.netbsd.org@localhost, Sat Nov 6 16:54:34 UTC 2010)
4868548+242860|seek note: invalid file offset

I get the seek note for NETBSD.GZ as well and when I try telling it to
load usb1/disk@1:,̣/netbsd.gz it returns a note that it can't be
loaded/found, and leaves me the Boot: command line. This happens with
\ instead of / in the path as well.
Typing in netbsd.gz gives the same error (seek note), and
netbsd.macppc makes the loading look up with just a / as a clue to
why.

>> NetBSD/macppc OpenFirmware Boot, Revision 1.11
>> (builds%b7.netbsd.org@localhost, Sat Nov 6 16:54:34 UTC 2010)
/

I get the same error when no arguments are given to ofwboot.xcf from
OpenFirmware and when netbsd.macppc is given as an argument.

I'm clueless to what to try next or if this will work at all.