At 3:32 PM +0900 2/14/00, SUNAGAWA Keiki wrote:

:)The implementation of Open Firmware changed enough to be
:)hard to work with.  Some firmware update is available for a
:)kind of iMac, though (I don't know the details).

Unfortunately, the 8500 has no firmware upgrade options (though one can
write a few changes into nvram).  This is OF 1.0.5.

:)What's in your configuration file?  I'm afraid it depends on
:)the version of Open Firmware (I tried it on original iMac
:)and iBook), but in my experience, both of ofwboot.elf and
:)ofwboot.xcf worked nicely.

It's a powermac 8500 being served by a hp300 running 1.4.  /etc/bootptab is:
darkplain.ee.cornell.edu:\
        :ht=ether:\
        :ha=00A0400B772C:\
        :sm=255.255.255.0:\
        :lg=128.84.235.81:\
        :ip=128.84.235.150:\
        :hn:\
        :bf=boot.netbsd:\
        :bs=auto:\
        :rp=/mnt/mems/home/admin/mw/macppc/:\
        :vm=auto:

/etc/inetd.conf is:
bootps          dgram   udp     wait    root    /usr/sbin/bootpd        bootpd
tftp            dgram   udp     wait    root    /usr/libexec/tftpd
tftpd -l  -s /tftpboot

(fatmac) ~> ls -l /tftpboot/
total 4162
-rw-r--r--  1 root  wheel    57580 Feb 13 23:46 boot.netbsd
-rw-r--r--  1 root  wheel  2064377 Feb 13 23:46 netbsd
(fatmac) ~> tail /var/log/messages
Feb 13 23:49:46 fatmac bootpd[4478]: version 2.4.1
Feb 13 23:56:28 fatmac bootpd[4478]: can not determine size of file
"/boot.netbs
d"
Feb 14 04:56:29 fatmac tftpd[4661]: 128.84.235.150: read request for
/boot.netbs
d: success
Feb 14 04:56:50 fatmac tftpd[4664]: 128.84.235.150: read request for : File
not
found
Feb 14 04:56:55 fatmac tftpd[4666]: 128.84.235.150: read request for : File
not
found

When I type in 'boot enet <filename>', it ignores the <filename> parameter,
no matter what I type in.  If I do 'boot enet -a', it stops to ask me, but
then ignores what I type in.

At 11:45 PM -0700 2/13/00, Miles Nordin wrote:

:)The iMac diskless FAQ is wrong.  ofwboot loads the kernel over NFS, just
:)like on every other platform.  Only ofwboot is loaded over TFTP, not the
:)kernel.  (unless you skip ofwboot of course)

Actually, I believe that this bootloader does indeed load the kernel over
tftp, as the client machine keeps repeating 'TFTP Timeout', and there are a
lot more of the 'read request for  :File not found' entries in my log files.

Any more suggestions?

Thanks,
  -- MW