Subject: Re: Unable to netboot G3 (blue and white) NetBSD 1.5.2
To: Bill Studenmund <wrstuden@netbsd.org>
From: Michael Wolfson <mw@blobulent.com>
List: port-macppc
Date: 12/18/2001 20:33:21
At 11:12 AM -0800 12/18/01, you wrote:
:)On Tue, 18 Dec 2001, Michael Wolfson wrote:
:)
:)> Funny y'all should mention this. I was working on the Diskless HOW-TO
:)> (now that I figured you need to explicitly mention ofwboot.xcf
:)> "boot enet:,\ofwboot.xcf" to get older PCI PowerMacs to netboot), and
:)> noticed that my PowerBook (FireWire) no longer netboots now that I've
:)> upgraded it to BootROM 4.1.8.
:)
:)Oh, I can netboot my system with "boot enet". This is an OF 2.0 system. My
:)dhcpd.conf has:
Yeah, I haven't heard any complaints about OF 2.0.x regarding netbooting,
but some people have had problems with early OF 1.0.5 machines (probably
the first generation VAL4 motherboards which had the MAC address reversed).
I really truly couldn't get it to boot unless I specified the path to the
bootloader or the kernel:
boot enet:,\ofwboot.xcf
boot enet enet:,/netbsd
Just "boot enet" or "boot enet:" fails to load the kernel.
My dhcpd.conf is essentially the same (plus comments from the Diskless HOW-TO):
host doctor.blobulent.com {
hardware ethernet 00:05:02:D0:EE:34;
fixed-address 10.0.1.202;
option host-name "doctor"; #name of the host (if the fixed address
#doesn't resolve to a simple name)
filename "ofwboot.xcf"; #name of the bootloader or kernel to
#download via tftp
next-server 10.0.1.201; #which machine to tftp filename from
option root-path "/export/doctor/root"; #the path on the NFS server.
#typically the client assumes the
#nfsserver = tftpserver
#always-reply-rfc1048 true; #this is needed if your client isn't
#getting the options you set and
#the log says "(non-rfc1048)"
}
In any case, my PowerBook (FireWire) now failing to netboot concerns me a
bit more than old Open Firmware bugs that we can work around, but not
repair.
-- MW