From owner-freebsd-current Mon Mar 25 9:30:41 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 151BC37B421 for ; Mon, 25 Mar 2002 09:30:23 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.6) with SMTP id g2PHUCk95504; Mon, 25 Mar 2002 12:30:12 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 25 Mar 2002 12:30:11 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Ilmar S. Habibulin" Cc: Stephen McKay , freebsd-current@freebsd.org Subject: Re: if_dc broken in -current In-Reply-To: <20020325100450.C93820-200000@fledge.watson.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 25 Mar 2002, Ilmar S. Habibulin wrote: > On Mon, 25 Mar 2002, Stephen McKay wrote: > > > What sort of card do you have? The output of dmesg would help. Have you > > tried 4.5 on this machine? > I have some noname nic with Intel 21143 chip. dmesg attached. I'm using > only trustedbsd_mac branch on my ws. > > > Of course the dc driver should autonegotiate (and does so when I revert > > rev 1.56). Your info could help trace this problem. > Well, i don't think this is the problem. Hardware became too much > inteligent now a days, so one have to use his own hands to make this > hardware work like user wants it to work. Maybe just put some FAQ about > dc(4) and autoconfigurable hubs/switches? I think I have an identical problem involving a Linksys ethernet card using if_dc. I have to force it to negotiate 10mbps, since it fails to negotiate anything higher with my 10/100 switch. No idea why at all. dc0: port 0xe800-0xe8ff mem 0xfebfff00-0xfebfffff irq 10 at device 19.0 on pci0 dc0: Ethernet address: 00:a0:cc:35:3e:56 miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: flags=8843 mtu 1500 inet6 fe80::2a0:ccff:fe35:3e56%dc0 prefixlen 64 scopeid 0x1 inet 192.168.11.150 netmask 0xffffff00 broadcast 192.168.11.255 ether 00:a0:cc:35:3e:56 media: Ethernet 10baseT/UTP status: active If I set it to auto-negotiate or hard-set to 100mbps, no packets go back or forth. I've had this problem for at least a year, if not longer. I have the same problem with 4.4-STABLE using an identical card on different hardware: if it tries to negotiate 100mbps, then it simply doesn't work. If I force it to 10, it's fine. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message