Problem with Gig Link not coming up

Hello -I am using a Intel 82540EM Gig controller with 1 copper Port on my PC(PCI slot) . I have connected this Gig Port to my device(Broadcom)which has Gig Copper Interface and the Link does not come up.

My settings are Auto Nego 1000Mbs FDX on both sides.I have observed the MII Status Registers on my device (Broadcom ) andit shows Auto Nego not completed/Error. Since I have no control on theIntel Side, wondering what could be the problem .Two possibilities are- MDI/MDIX Crossover is not happening- Master/Slave Resolution is not hapenning and it is getting to adeadlock

The other observation is that when I connect two of my devices back toback the Gig Copper link is coming up.

I thought the Gig connection needed to be FORCED to work.Did you try that?

kmatpral@yahoo.com (Kott) wrote in message news:<3755c855.0410080638.502d5037@posting.google.com>...> Hello -> I am using a Intel 82540EM Gig controller with 1 copper Port on my PC> (PCI slot) . I have connected this Gig Port to my device(Broadcom)> which has Gig Copper Interface and the Link does not come up.> > My settings are Auto Nego 1000Mbs FDX on both sides.> I have observed the MII Status Registers on my device (Broadcom ) and> it shows Auto Nego not completed/Error. Since I have no control on the> Intel Side, wondering what could be the problem .> Two possibilities are> - MDI/MDIX Crossover is not happening> - Master/Slave Resolution is not hapenning and it is getting to a> deadlock> > The other observation is that when I connect two of my devices back to> back the Gig Copper link is coming up.> > > any comments from the gurus out there> > Thanks> Kott

In article <af3623de.0410080926.57a8f7c2@posting.google.com>,Mike Farnham <mike.farnham@co.manatee.fl.us> wrote::I thought the Gig connection needed to be FORCED to work.

In my reading of postings, the majority of people I would tend totrust have said that Gig -must- be autonegotiate according to thestandards. I have, though, also seen reputable people advise toforce gig connections.

My conclusion from reading those messages is that either -some- gig devicesare not fully standards compliant, or else that the standards leftsomething ambiguous even though they tried to eliminate the ambiguities.-- "The human genome is powerless in the face of chocolate." -- Dr. Adam Drewnowski

roberson@ibd.nrc-cnrc.gc.ca (Walter Roberson) wrote in message news:<ck6kri$7je$1@canopus.cc.umanitoba.ca>...> In article <af3623de.0410080926.57a8f7c2@posting.google.com>,> Mike Farnham <mike.farnham@co.manatee.fl.us> wrote:> :I thought the Gig connection needed to be FORCED to work.> > In my reading of postings, the majority of people I would tend to> trust have said that Gig -must- be autonegotiate according to the> standards. I have, though, also seen reputable people advise to> force gig connections.> > My conclusion from reading those messages is that either -some- gig devices> are not fully standards compliant, or else that the standards left> something ambiguous even though they tried to eliminate the ambiguities.

Update on this:The link did come up and the problem was that the Transmit signalAmplitude was very high. So I lowered the Tx signal amplitude from myDevice and the link came up. What was happening previously was thatthe Link was coming up but after 20 mins or so. But if I used alonger cable then the signal was getting attentuated and link used tocome up faster.

From this I concluded that the Auto Nego Link code words signals weregettingdistorted and the the link partner was not able to decode this. So Ireduced theTransmit Signal amplitude from my device and link comes up rightaway.I need to test it though with different cable lengths.Kott