From owner-freebsd-alpha Thu Apr 6 12:28:14 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id BCE6037B5A8 for ; Thu, 6 Apr 2000 12:28:06 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 99c8f334c649856e3f2cdadc4054e412) with ESMTP id <20000406192743.YMSX15447.relay02@chello.nl> for ; Thu, 6 Apr 2000 21:27:43 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id VAA01792 for freebsd-alpha@freebsd.org; Thu, 6 Apr 2000 21:28:04 +0200 (CEST) (envelope-from wkb) Date: Thu, 6 Apr 2000 21:28:04 +0200 From: Wilko Bulte To: FreeBSD-alpha mailing list Subject: dc driver for embedded ethernet on Miata MX5 problems Message-ID: <20000406212804.A1731@yedi.wbnet> Reply-To: wc.bulte@chello.nl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm experiencing some problems using the embedded ethernet on the Miata MX5 I have here. This is 4.0R, freshly installed. The symptoms are that the dc driver reports watchdog timeouts and no network connections can be made. Using the de driver instead of dc works fine. The MX5 has a 10baseT/10base2 bulkhead mounted. It is also possible to have a 100baseT bulkhead (I have one on my MiataGL) that is connected to another connector on the PCI riser card. Initially I assumed that maybe the 21143 can't 'see' that it has a 10Mbit-only bulkhead mounted. So I set the SRM ewa0_mode to 10baseT. This does not make a difference. I also tried setting 10Mbit mode in rc.conf: ifconfig_dc0="inet 192.168.200.24 netmask 255.255.255.0 media 10baseT/UTP" This also did not make a difference. Apr 6 21:00:40 mx5 /kernel: dc0: port 0x8000-0x807f mem 0 x80850000-0x8085007f irq 0 at device 3.0 on pci0 Apr 6 21:00:40 mx5 /kernel: dc0: interrupting at CIA irq 0 Apr 6 21:00:40 mx5 /kernel: dc0: Ethernet address: 00:00:f8:75:3c:6a Apr 6 21:00:40 mx5 /kernel: miibus0: on dc0 Apr 6 21:00:40 mx5 /kernel: dcphy0: on miibus0 Apr 6 21:00:40 mx5 /kernel: dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Apr 6 21:00:40 mx5 /kernel: dc0: supplying EUI64: 00:00:f8:ff:fe:75:3c:6a ... Apr 6 21:00:40 mx5 /kernel: dc0: starting DAD for fe80:0001::0200:f8ff:fe75:3c6a Apr 6 21:00:41 mx5 /kernel: dc0: DAD complete for fe80:0001::0200:f8ff:fe75:3c6a - no duplicates found Apr 6 21:00:45 mx5 /kernel: dc0: watchdog timeout de driver boot message: de0: port 0x8000-0x807f mem 0x80850000-0x8085007f irq 0 at device 3.0 on pci0 de0: interrupting at CIA irq 0 de0: DEC 21142 [10-100Mb/s] pass 1.1 de0: address 00:00:f8:75:3c:6a de0: enabling 10baseT port de0: supplying EUI64: 00:00:f8:ff:fe:75:3c:6a de0: driver is using old-style compatability shims Is there anything special that I'm overlooking maybe? Comments from fellow MX5 owners are invited as well. TIA -- Wilko Bulte Powered by FreeBSD http://www.freebsd.org http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message