2003-05-23 19:52:23

by Kari Kallioinen

[permalink] [raw]
Subject: Tigon3 auto-negotiation and force media

Hi,

I have a problem with broadcomm 5700 based card.
It's autonegotiating a wrong media and I can't change the parameters of another
end of link. So how I can force specified media technology with tg3-driver?
Mii-tool doesn't seem to work and I didn't find any option for tg3-module.

I have version 1.5 of tg3.c and Linux version 2.4.21-rc2.

--
Kari Kallioinen


2003-05-23 20:59:07

by walt

[permalink] [raw]
Subject: Re: Tigon3 auto-negotiation and force media

Kari Kallioinen wrote:
> Hi,
>
> I have a problem with broadcomm 5700 based card.
> It's autonegotiating a wrong media and I can't change the parameters of another
> end of link. So how I can force specified media technology with tg3-driver?
> Mii-tool doesn't seem to work and I didn't find any option for tg3-module.

I have the same chip on my motherboard and I have found that doing an
'ifconfig down' followed by 'ifconfig up' will make the chip work.
(You may need to restore the default route after doing the above.
Or, if you have an appropriate initscript in /etc/rc.d or /etc/init.d
you can just use it to restart the network -- same idea but less trouble.)

BTW, how do can you tell that the media choice is wrong? 'ifconfig' doesn't
give me that information.



2003-05-24 19:10:52

by Kari Kallioinen

[permalink] [raw]
Subject: Re: Tigon3 auto-negotiation and force media

On Fri, May 23, 2003 at 03:10:52PM -0700, walt wrote:
> BTW, how do can you tell that the media choice is wrong? 'ifconfig' doesn't
> give me that information.

I'm getting the information from dmesg:

tg3: eth0: Link is up at 100 Mbps, half duplex.


--
Kari Kallioinen

2003-05-26 04:06:39

by David Miller

[permalink] [raw]
Subject: Re: Tigon3 auto-negotiation and force media

On Fri, 2003-05-23 at 13:03, Kari Kallioinen wrote:
> So how I can force specified media technology with tg3-driver?

Just like for any other ethernet driver, you use the
'ethtool' utility to do this.

--
David S. Miller <[email protected]>