Date: Sun, 16 Sep 2001 12:04:29 -0400 From: Mike Tancsa <mike@sentex.net> To: Andreas Wideroe Andersen <andreas@kpnqwest.no> Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Gigabyte 1U GS-SR101 Server and Onboard Intel NIC trouble.. anyone? Message-ID: <5.1.0.14.0.20010916115740.048925c0@192.168.0.12> In-Reply-To: <5.1.0.14.2.20010916125135.00a82380@kirov.eunet.no> References: <3jj7qt43t49sbnpn1kice63r5b9m9v7ikg@4ax.com> <SEN.1000565258.150440902@news.sentex.net> <SEN.1000565258.150440902@news.sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 01:03 PM 9/16/2001 +0200, Andreas Wideroe Andersen wrote:
>At 17:59 15.09.01 -0400, Mike Tancsa wrote:
>>On 15 Sep 2001 10:47:38 -0400, in sentex.lists.freebsd.hardware you wrote:
>>
>> >
>> >Has anyone else experienced this trouble? I hesitate to think that it is a
>> >faulty NIC, but that's all I can think of right now.. is there a known
>> >problem with FreeBSD and this hardware? GNATS and a search of the mailling
>> >lists doesn't seem to reveal anything.
>> >
>>
>>
>>Is this board based on the Intel 815e chipset by chance ? The Intel NICs on
>>those boards need 4.4Release (or 4.3 STABLE from late August) to work
>>properly.
>
>
>I've got an Aopen MX3S motherboard with Intel 815e chipset and an onboard
>Intel NIC. I'm having problems with timouts. Whenever I'm updating ports
>or when there is massive traffic going through the NIC I get:
>
>fxp0: Device timout or fxp0: scb timeout
>
>I just got 4.3 RELEASE installed after trying 30 times, now I want to
>upgrade to STABLE, but am unable to retrieve the latest distributions.
>
>I've been reading about this problem on websites and in mailinglists and
>it seems to be a bug in the driver. Is this bug fixed in the 4.4 version
>of FreeBSD?
Yes, there is a bug in this particular version of the Intel chip from what
I understand. A work around to it was committed to the FreeBSD tree Aug
30th. I have several of these boards and they work great with this version
of the driver. This fix corrects the problem for both the ET and EM version
of the NIC
e.g.
fxp1: <Intel Pro/100 Ethernet> port 0xc400-0xc43f mem 0xd5101000-0xd5101fff
irq 11 at device 8.0 on pci1
fxp1: Ethernet address 00:01:80:05:d2:67
inphy1: <i82562ET 10/100 media interface> on miibus1
inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
In the intrim, it *might* be possible to grabb the miibus and fxp KLDs from
4.4R and load them that way. Not sure if it will work or not, but it
might. Or grab a 4.4R kernel.GENERIC. That *might* work long enough for
you to cvsup. Also, the bug seems to happen less if you are in 100BaseTX
instead of 10baseT.
---Mike
--------------------------------------------------------------------
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, mike@sentex.net
Providing Internet since 1994 www.sentex.net
Cambridge, Ontario Canada www.sentex.net/mike
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.1.0.14.0.20010916115740.048925c0>