RE: Full/Half duplex - diagnostics not the same as reality

On Fri, 13 Jun 2003, Miskell, Craig wrote:

> Oh yeah, and the driver is 0.99H 11/17/98 
> Yeah, I know it's old - maybe that's my problem ;-)

I think that this is the reason for not being able to fully reproduce the 
behaviour of the recent versions (like the one used in the mentioned 
thread).

> 1:  Why do I stop getting collisions having unsuccesfully "forced"
> full-duplex?

You mean when forcing with "full_duplex=1" ? I can't explain this, but the 
code dealing with media selection had seen some changes in the last 5 
years :-)

> It's still advertising HD,

I don't really see where... This line:

>  Your link partner is generating 100baseTx link beat  (no autonegotiation).

... and the following two...

>  Link partner capability is 0080: 100baseTx.
>    Negotiation did not complete.

... are about the partner. All others include some "FD" letters :-o

> 3: Interestingly, if I put options=12 in the module conf, I get the same
> practical results (good transfer speed, no collisions),

I think this is because some old versions of the driver did force the 
media and did not use autonegotiation. In case media is forced in this 
way, reading the MII registers returns bogus information.

>    Capable of  100baseT4 100baseTx-FD.

The first part (100baseT4) is certainly not available on your card !

>    Negotiation  completed.

And this is obviously wrong, but these are just result of bogus MII 
registers reading, so don't worry about them!

-- 
Bogdan Costescu

IWR - Interdisziplinaeres Zentrum fuer Wissenschaftliches Rechnen
Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY
Telephone: +49 6221 54 8869, Telefax: +49 6221 54 8868
E-mail: [email protected]

_______________________________________________
vortex mailing list
[email protected]
http://www.scyld.com/mailman/listinfo/vortex