On Monday, 25th March 2002, Robert Watson wrote:
>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.
After careful consideration, I think this has to be a different problem.
My problem is that auto-negotiation doesn't start at boot (when an address
is assigned to dc0). If I explicitly set a speed, that speed works. Most
bizarrely, if I misspell the media option, that causes a successful
autonegotation! I mean, I type "ifconfig dc0 media 10baset" immediately
after boot, and autonegotiation takes over. (If I spell it "10baset/utp"
it goes into 10Mbit half-duplex mode, like you expect.) So it's just a
hair's breadth away from working properly, and reverting rev 1.56 is enough
for full operation to be restored.
Since you explicitly set 100Mbit half-duplex and it doesn't work, then that
must be something else. We could have a go at finding that bug too, but
it will be harder, since I don't have a PNIC II here. I do have some info
on the Macronix 98715A, which Bill Paul says is almost the same. Maybe
we can get lucky.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message