Subject: port-alpha/6446: netbooting Multia on -current broken.
To: None <>
From: None <>
List: netbsd-bugs
Date: 11/15/1998 04:09:57
>Number:         6446
>Category:       port-alpha
>Synopsis:       netbooting Multia on -current broken.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    gnats-admin (GNATS administrator)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Nov 15 04:20:01 1998
>Originator:     R. C. Dowdeswell
a bit.
>Release:        Thu Nov 12 05:11:56 PST 1998
System: NetBSD 1.3H NetBSD 1.3H (MABELODE) #2: Wed Nov 4 02:16:40 PST 1998 alpha

	I had a bit of a problem setting up netbooting on my Multia.
	To make a long story short, I set up the ether addr with
	setnetbootinfo into netboot, but it didn't seem to be properly
	receiving any packets (which is why my previous bug report about
	-DARP_DEBUG was filed, during my playing around...)

	Anyway, I found that if I set broken_firmware = 0, then it worked.
	Try to netboot a Multia that is similar to mine.
	I changed /sys/arch/alpha/stand/netboot/if_prom.c to not set
	broken_firmware to true, and I was able to hardcode the ether
	addr with /usr/mdec/setnetbootinfo and boot properly.

	I don't have any machines that require broken_firmware == 1,
	though, so I can't really suggest a fix except perhaps to
	change setnetbootinfo to be able to hard code broken_firmware
	and doc it.