Re: 2 problems with the linksys mx driver
Mike Nowlin wrote: Autonegotiation is failing. That happens in the Fast Ethernet world. Buying better quality switches *may* help. ;^) Can you get any better than 3COM's top of the range stacks? I ran into a similar problem with a couple Linksys cards under both FBSD (ugh) Win95 -- telling the HP ProCurve 2424M to force 100BTX half-duplex (didn't try full) fixed the problem Still seeing this autoneg problem with my cheapy Linksys 100-only hub and my wife's Linksys card on '95... You'd figure that autoneg would work when everything's by the same manufacturer :) But it's not, is just all from the same assembler. The cards and boxes are assembled from a bewildering supply of chips, all from different vendors. Ethernet is so nice, because it just works, except when it doesn't. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
2 problems with the linksys mx driver
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
Re: 2 problems with the linksys mx driver
Hi, Problems with linksys (mx driver) cards in -stable and - current If I type in ifconfig mx0 media 100basetx it all works OK. Do you have any ideas on these. Autonegotiation is failing. That happens in the Fast Ethernet world. Buying better quality switches *may* help. ;^) Can you get any better than 3COM's top of the range stacks? Seriously though, in -stable there are 2 bugs with the linksys (mx driver) cards. 1) In if_mx, (and a few other drivers too for that mater) the driver probes the link and then selects the most suitable speed and mode (half or full duplex) The code picks 100BaseT4 as its first chose, then 100 Meg Full Duplex second, then 100 Meg Half duplex, then 10 Full Duplex, then 10 Half duplex. The Ethernet specs I have read say the official order should be 100 Meg Full Duplex FIRST, then 100base T4, then 100 Meg Half duplex, then 10 Full D then 10 Half D. 2) Even if my line was 100BaseT4, the if_mx driver should not be passing an invalid paremter to if_media, causeing if_media to panic with something along the lines of "invalid media type 0x28/0xff" if_mx should not select 100BaseT4 if the rest of the kernel cannot handle it. _OR_ it should be passing the right parameter to if_media. Then there are issues in -current, but lets fix -stable first. This is all a bit different to the Bt848 driver, so I could do with some help kernel hacking. Cheers Roger To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 2 problems with the linksys mx driver
Autonegotiation is failing. That happens in the Fast Ethernet world. Buying better quality switches *may* help. ;^) Can you get any better than 3COM's top of the range stacks? I ran into a similar problem with a couple Linksys cards under both FBSD (ugh) Win95 -- telling the HP ProCurve 2424M to force 100BTX half-duplex (didn't try full) fixed the problem Still seeing this autoneg problem with my cheapy Linksys 100-only hub and my wife's Linksys card on '95... You'd figure that autoneg would work when everything's by the same manufacturer :) mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
