From owner-freebsd-hardware  Thu Jan  9 18: 9:25 2003
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1EC0837B401; Thu,  9 Jan 2003 18:09:24 -0800 (PST)
Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 8730743F43; Thu,  9 Jan 2003 18:09:23 -0800 (PST)
	(envelope-from wa1ter@myrealbox.com)
Received: from myrealbox.com wa1ter@smtp-send.myrealbox.com [67.114.254.3]
	by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision:   3.22  $ on Novell NetWare
	via secured & encrypted transport (TLS);
	Thu, 09 Jan 2003 19:09:23 -0700
Message-ID: <3E1E2B8F.9050401@myrealbox.com>
Date: Thu, 09 Jan 2003 18:10:23 -0800
From: walt <wa1ter@myrealbox.com>
Organization: none
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2b) Gecko/20030108
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: jdp@freebsd.org, freebsd-hardware@freebsd.org
Subject: More on Broadcom gigabit (bge) chips.
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hardware.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware>
X-Loop: FreeBSD.org

I see others have had problems with the bge driver on recent ASUS
motherboards.

I originally thought that these chips were supported on -CURRENT
but not on -STABLE because I had no problems installing -CURRENT.

On further investigation I find that the chip is properly initialized
on reboot only 50% of the time on both -CURRENT and -STABLE, so it was
just a matter of chance.

I find that half the time the chip will not properly sense the
100baseTX medium it is connected to and defaults to 1000baseSX
and complains about 'no carrier'.

If this happens then it will respond to an 'ifconfig media 100baseTX'
with a 'device not configured' error, although it will accept other
ifconfig commands to change address, netmask, etc.

Anyone else seeing this?  Any suggestions?


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message