Bug 15455

Summary: Intel EtherExpress Pro does not properly attach on the Alpha
Product: Base System Reporter: David E. O'Brien <obrien>
Component: kernAssignee: dg
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.0-CURRENT   
Hardware: Any   
OS: Any   

Description David E. O'Brien 1999-12-13 07:40:02 UTC
	The Ethernet address on a EtherExpress Pro/100B (i82558-based)
	is not properly determined.  The machine also looks solid when
	the card is ifconfig'ed.

How-To-Repeat: 
	# ifconfig -a
	de0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        	inet 169.237.7.192 netmask 0xffffff00 broadcast 169.237.7.255
        	ether 00:00:f8:23:5d:51 
        	media: autoselect (10baseT/UTP) status: active
        	supported media: autoselect 10base5/AUI manual 10baseT/UTP <full-duplex> 10baseT/UTP
	fxp0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        	ether ff:ff:ff:ff:ff:ff 
        	media: manual
        	supported media: manual
	sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552
	ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
	lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        	inet 127.0.0.1 netmask 0xff000000 

	kongur(r):/home/rootk> ifconfig fxp0 inet 192.168.100.1
	[ BOX HANGS SOLID ]
Comment 1 David E. O'Brien freebsd_committer freebsd_triage 1999-12-14 01:59:00 UTC
Responsible Changed
From-To: freebsd-bugs->dg

Knows more about fxp than anyone. 
Comment 2 dg freebsd_committer freebsd_triage 2000-10-16 20:07:47 UTC
State Changed
From-To: open->closed

Believed to be fuxed in later revs of the fxp driver.