There is a strange issue with the bge(4) driver under which some, but not all bge(4) chipsets lose their link after being probed by the driver. Indeed, this behavior doesn't even seem to affect all the chips of the affected chipsets. While the rc scripts explicitly up the interface before attempting to use dhclient on them, sysinstall(8) does not. This is particularly annoying when doing PXE-booted, NFS-based installations on a network with addresses allocated via DHCP (as we have in our server assembly network). Fix: This patch is also available at http://www.sitetronics.com/~dodell/sysinstall.diff in case this web submission has whitespace issues. -- begin patch -- How-To-Repeat: Find a system that exhibits this issue (it's not that difficult: I've come across about 15 out of 50 in the last month that do this). Boot it with PXE. When sysinstall(8) asks if you'd like to enable DHCP for the interface, say yes. Be astonished when all fields come up blank. Lather. Rinse. Repeat.
State Changed From-To: open->feedback Can you reproduce the problem in recent RELEASEs?
State Changed From-To: feedback->closed Submitter's email address bounces