Hi Bill,
I'm having quite a few problems with my linksys cards.
I think most are caused because I'm connected to a switch
rather than a simple hub.
The cards are the new Version 2 cards (with Wake On Lan)
and use the MX driver.
1) On 3.3-stable, the linksys mx driver detects my network
connection to a 3COM switch as 100BaseT4.
However, the kernel then panics because if_media cannot
support media type 0x28.
My workarond was to hack the kernel source for if_mx.c
and stop it detecting 100BaseT4. It now detects 100Base Full
duplex and works ok.
2) On 4.x-current, the linksys mx driver is connected to
a Kingston 10/100 Switch.
It does not detect a carrier on the network.
If I do ifconfig mx0 media auto I see the 'link in use'
and '100 Megs in use' LED on my switch
go on for 2 seconds, then go off for 2 seconds, then go
on for 2 seconds, then go off for 2 seconds.
When the link is up, I can ping and use the network etc.
When the link is down, I have no network connection.
If I type in ifconfig mx0 media 100basetx
it all works OK.
Do you have any ideas on these.
I'm willing to test patches on both -stable and -current
and can swap switches too (swap the 3COM and the Kingston)
Thanks
Roger
--
Roger Hardiman | Telepresence Research Group
[EMAIL PROTECTED] | DMEM, University of Strathclyde
tel: 0141 548 2897 | Glasgow, Scotland, G1 1XJ, UK
fax: 0141 552 0557 | http://www.telepresence.strath.ac.uk
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
