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: <LC82C115 PNIC II 10/100BaseTX> port 0xe800-0xe8ff mem
0xfebfff00-0xfebfffff irq 10 at device 19.0 on pci0
dc0: Ethernet address: 00:a0:cc:35:3e:56
miibus0: <MII bus> on dc0
dcphy0: <Intel 21143 NWAY media interface> on miibus0
dcphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> 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
[EMAIL PROTECTED]      NAI Labs, Safeport Network Services



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to