>Number:         4782
>Category:       kern
>Synopsis:       ep driver won't work with 3c905 in (at least some) Dell systems
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people (Kernel Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jan  5 14:35:01 1998
>Last-Modified:
>Originator:     Chris G. Demetriou
>Organization:
We don't need not stinkin' organization.
>Release:        1.3
>Environment:
NetBSD 1.3, Dell Optiplex GX Pro 200.  Built-in (on motherboard) 3c905.

>Description:
	[ this bug filed as 'kern' because it applies to a
	machine-independent driver that i'm using on an x86 system.
	If that's the wrong classification, refile it! 8-]

	The NetBSD 1.3 'ep' driver doesn't work with the built-in 3c905 in
	(at least some) Dell systems.  I care, because my system happens
	to be one in which it doesn't work.

	It seems that the 'ep' driver selects an incorrect media type, and
	won't allow the user to select any other media types.  This makes
	it pretty much impossible to install the system using the built-in
	ethernet.

	The startup messages look like (10-finger copy, with irrelevant
	bits deleted):

	ep1 at pci1 dev 8 function 0: 3Com 3C905 Ethernet
	ep1: MAC address ...
	ep1: 8KB word-wide FIFO, (undefined) Rx:Tx split, mii default mii
	ep1: interrupting at irq 10

	The device is detected properly as a 3C905.  ifconfig -am shows
	the following for ep1 (again 10-finger copy, with irrelevant bits
	deleted):

	ep1: flags=...
		address: ....
		media: 100baseTX status: active
		supported media: 100baseTX

	Not only does this not match what's printed at boot (should it?), it
	doesn't let me select 10baseT.  My network is 10baseT, and the device
	is supposed to work with 10baseT.  Other systems, e.g. FreeBSD,
	do the right thing.  (indeed, i don't even have to muck with setting
	the media type under freebsd.  it either autodetects it, or the
	default is 10baseT which works for me.)

	It's worth noting that the "(undefined)" message for Rx:Tx split
	is probably bogus, as well.  It should probably be "unknown."  The
	value reported by the card is almost certainly _defined_ to have
	some meaning (otherwise, why would the card be using it?!), but
	that meaning probably isn't known to the NetBSD kernel.

>How-To-Repeat:
	Boot a 1.3 install floppy on my Dell (or probably many other
	Dell Optiplex GX Pro systems).  Poke around, when you realize
	that you can't talk to the network.

>Fix:
	"Install FreeBSD."  FreeBSD 2.2.5-RELEASE works "out of the box."
>Audit-Trail:
>Unformatted: