From owner-freebsd-questions  Wed Oct  4 22:24:14 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from guru.mired.org (okc-27-149-77.mmcable.com [24.27.149.77])
	by hub.freebsd.org (Postfix) with SMTP id 9BA0837B66C
	for <questions@freebsd.org>; Wed,  4 Oct 2000 22:24:09 -0700 (PDT)
Received: (qmail 28178 invoked by uid 100); 5 Oct 2000 05:24:05 -0000
From: Mike Meyer <mwm@mired.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14812.4213.576011.3976@guru.mired.org>
Date: Thu, 5 Oct 2000 00:24:05 -0500 (CDT)
To: questions@freebsd.org
Subject: dc ethernet driver config?
X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid
X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG%
 *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Ok, I couldn't find anything about this in the FAQ, handbook or mail
archives. So help? Please?

I'm setting up a brand new system with 4.1-stable. Update was
yesterday. Running the GENERIC kernel it comes up and talks to the
network and everything is fine. Here are the relevant dmesg lines:

	dc0: Ethernet address: 00:d0:09:fc:5a:e6
	miibus0: <MII bus> on dc0
	amphy0: <Am79C873 10/100 media interface> on miibus0
	amphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto


amphy? Huh? Ok, it's part of the miibus stuff - I guess. My other
miibus system has an xl, and find xlphy. Probably related. For futher
info, here's the "ifconfig" output on this box:

	> ifconfig
	dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	        inet 192.168.1.17 netmask 0xffffff00 broadcast 192.168.1.255
	        inet6 fe80::2d0:9ff:fefc:5ae6%dc0 prefixlen 64 scopeid 0x1 
	        ether 00:d0:09:fc:5a:e6 
	        media: autoselect (100baseTX <full-duplex>) status: active
	        supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP none
	lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
	ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
	sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552
	faith0: flags=8000<MULTICAST> mtu 1500
	gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
	gif1: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
	gif2: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
	gif3: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
	lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	        inet6 fe80::1%lo0 prefixlen 64 scopeid 0xa 
	        inet6 ::1 prefixlen 128 
	        inet 127.0.0.1 netmask 0xff000000 


Showing that yes, indeed, dc is the real ethernet interface.

So I now start configuring a custom kernel for this creature. I config
it as:

	# PCI Ethernet NICs that use the common MII bus controller code.
	device          miibus          # MII bus support
	device          dc              # DEC/Intel 21143 and various workalikes

(lifted straight from the LINT file).

After which, the system boots and fails to find the ethernet. No
mention of mii, amphy, or dc in the dmesg.

Anyone got any clues? Suggestions? Requests for more information?

	Thanx,
	<mike



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message