Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 May 2007 15:01:58 -0700
From:      "Jack Vogel" <jfvogel@gmail.com>
To:        stefan.lambrev@sun-fish.com
Cc:        freebsd-net@freebsd.org
Subject:   Re: em0 - bge0 failed to work at 1000baseTX
Message-ID:  <2a41acea0705111501h41170824qddbf8fee9d9dacc7@mail.gmail.com>
In-Reply-To: <463F2318.4070702@sun-fish.com>
References:  <462E3B4A.5030307@sun-fish.com> <2a41acea0704241103r59a1fa8di7e7747e191eea787@mail.gmail.com> <462F0CBF.6020507@sun-fish.com> <2a41acea0704250936l46ed31a3w930ac8fba04df810@mail.gmail.com> <2a41acea0705041349o7bce9e1eh63ef1a036f80d1b6@mail.gmail.com> <463F2318.4070702@sun-fish.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 5/7/07, Stefan Lambrev <stefan.lambrev@sun-fish.com> wrote:
> Hi again,
>
> Jack Vogel wrote:
>
> >
> > The new driver I just checked into CURRENT has this fix, I hope its
> > going to be in the May snapshot, Stefan, can you try CURRENT to
> > see if it solves your problem?
> >
> > Jack
> I have problems with loading if_em as module on 7.0-current from today:
>
> link_elf: symbol e1000_init_function_pointers_82575 undefined
>
> so I compiled in the kernel, and it works, but nothing changed about my
> problem - it still refuses to stay on 1000baseTX for more then 2 seconds
> and auto-negotiate to 100baseTX.
>
> em0: <Intel(R) PRO/1000 Network Connection Version - 6.5.0> port
> 0x2000-0x201f mem 0xf0500000-0xf051ffff,0xf0524000-0xf0524fff irq 19 at
> device 25.0 on pci0
> em0: Ethernet address: 00:0f:fe:4e:78:16
> em0: [FILTER]
>
> I'm ready to test any new patches :)

My patch made assumptions about what is causing your problem,
and that may be incorrect. Our test group does not have that Broadcom
adapter but they are going to get one.

They had a suggestion that you can try, go into your BIOS, and
then the Advanced Menu, I believe under that you will find settings
for the NorthBridge, in that submenu there is settings for HECI,
disable that, it is the interface to the management processor.

Then boot up and test again, if it now autonegs correctly then
it is the management getting in your way, on the other hand if
you still see it happen then we're back to square one :)

Good luck,

Jack



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2a41acea0705111501h41170824qddbf8fee9d9dacc7>