>Number:         13545
>Category:       port-macppc
>Synopsis:       The enet install of 1.5.1 fails on ping test with mc0
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-macppc-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jul 24 04:33:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Ken Wellsch
>Release:        NetBSD-1.5.1 release
>Organization:
	
>Environment:
UMAX S900, NetBSD-1.5.1 install floppy
	
System: NetBSD s900 1.5W NetBSD 1.5W (S900) #0: Mon Jul 23 14:27:27 EDT 2001 kwellsch@s900:/usr/src/sys/arch/macppc/compile/S900 macppc
Architecture: powerpc
Machine: macppc
>Description:
	While attempting to install the 1.5.1 release onto an S900,
	I wanted to use the "ftp" set load method.  After providing
	the network particulars, there was a short pause while a
	ping test took place then I was told there was a problem.
	When I manually tried pinging out of the box, indeed the
	ping would just hang - upon killing the ping, I was told
	zero packets out, zero packets received.  Yet I could ftp
	out and I could ping the new box from another box.
	
>How-To-Repeat:
	Attempt to install 1.5.1 using the official install floppy
	and sysinst.  Select the ftp set load option and see that
	the network test fails and gives no other choices (e.g. like
	to proceed anyway as I think one could do with the 1.5 release).
	
>Fix:
	I vaguely recall seeing something like this with the m68k
	port several years ago.  I think it was a well known problem.
	The integrated enet chip in the S900 is shared with later issue
	mac68k boxes (the mc device).  If in fact this bug continues, then
	I guess the fix involves allowing a "proceed anyway" option
	when the network ping test fails.  Otherwise, fixing the issue
	with the mc driver I suppose makes more sense.
	
>Release-Note:
>Audit-Trail:
>Unformatted: