This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C07A8B.A64C8790
Content-Type: text/plain;
charset="iso-8859-1"
Well, Intel does state that use the enet port WITHOUT a CNT increase the
error rate by about a factor of 10. I read it as saying that a CNR should be
used for reliable networking.
-----Original Message-----
From: Jamie Curtis [mailto:jpc2@cs.waikato.ac.nz]
Sent: Tuesday, January 09, 2001 2:14 PM
To: Infinity2
Cc: eepro100@scyld.com
Subject: Re: [eepro100] Ok, I'm fed up now.
On Mon, 8 Jan 2001, Infinity2 wrote:
> Ok, I just build another server, also using an Intel D815EAL. Same exact
> setup as the other one. Celeron 600cpu w/ 128mb ram (PC133 btw). both
> systems lockup doing ftp transfers. I didn't know for sure about the
first
> one, so I just opened up an ncftp session and downloaded something large
> from the internet. Netscape 6 was what I found (not planning on
installing
> it btw), didn't get very far then locked up tight. twice in a row. no
> errors, nothing, nothing to report either.
Unfortunatly while I cannot provide any solution to your problem I may
have some more information from my experiences people may find
interesting.
I have seen *exactly* the same problem as you are describing occur on two
machines based on the Intel 815e chipset, a compaq deskpro and an intel
815eal board. They both locked up using the shipped driver, the Becker
driver, the intel e100 driver and also, for interests sake, the FreeBSD
eepro driver. All of them would lock up consistantly on a 1Gb ftp or rcp,
while the smaller the file got the more unpredictable the lockup became,
but they always locked up eventually.
However another group on the same network using the same software
(specifically the e100 driver) and identical compaq deskpro's had the
machines working first go with no problems.
There was only one difference that I can see between the machines. Both of
our machines were celeron based (ie 66MHz FSB) and the other machines were
P III based (133MHz FSB). Both of our machines by this point had
unfortunatly turned into Win2k machines because of the problems with
linux, so I never got to investigate if the CPU was infact the issue, but
I see no other differences between the machines.
I am still very interested in seeing if other people who have had success
with 815e boards have all been using them with P III CPU's or is the
Celeron vs P III issue here just a freak co-incidence.
Jamie
-----------------------------------------------------------------------
Jamie Curtis email: jpc2@cs.waikato.ac.nz
WAND Group Lab G1.31 phone +64 21 392 102
Computer Science Department, University of Waikato, New Zealand
-----------------------------------------------------------------------
_______________________________________________
eepro100 mailing list
eepro100@scyld.com
http://www.scyld.com/mailman/listinfo/eepro100
------_=_NextPart_001_01C07A8B.A64C8790
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
RE: [eepro100] Ok, I'm fed up now.
Well, Intel does state that use the enet port WITHOUT =
a CNT increase the error rate by about a factor of 10. I read it as =
saying that a CNR should be used for reliable networking.
-----Original Message-----
From: Jamie Curtis [mailto:jpc2@cs.waikato.ac.nz]<=
/FONT>
Sent: Tuesday, January 09, 2001 2:14 PM
To: Infinity2
Cc: eepro100@scyld.com
Subject: Re: [eepro100] Ok, I'm fed up now.
On Mon, 8 Jan 2001, Infinity2 wrote:
> Ok, I just build another server, also using an =
Intel D815EAL. Same exact
> setup as the other one. Celeron 600cpu w/ =
128mb ram (PC133 btw). both
> systems lockup doing ftp transfers. I =
didn't know for sure about the first
> one, so I just opened up an ncftp session and =
downloaded something large
> from the internet. Netscape 6 was what I =
found (not planning on installing
> it btw), didn't get very far then locked up =
tight. twice in a row. no
> errors, nothing, nothing to report =
either.
Unfortunatly while I cannot provide any solution to =
your problem I may
have some more information from my experiences =
people may find
interesting.
I have seen *exactly* the same problem as you are =
describing occur on two
machines based on the Intel 815e chipset, a compaq =
deskpro and an intel
815eal board. They both locked up using the shipped =
driver, the Becker
driver, the intel e100 driver and also, for =
interests sake, the FreeBSD
eepro driver. All of them would lock up consistantly =
on a 1Gb ftp or rcp,
while the smaller the file got the more =
unpredictable the lockup became,
but they always locked up eventually.
However another group on the same network using the =
same software
(specifically the e100 driver) and identical compaq =
deskpro's had the
machines working first go with no problems.
There was only one difference that I can see between =
the machines. Both of
our machines were celeron based (ie 66MHz FSB) and =
the other machines were
P III based (133MHz FSB). Both of our machines by =
this point had
unfortunatly turned into Win2k machines because of =
the problems with
linux, so I never got to investigate if the CPU was =
infact the issue, but
I see no other differences between the =
machines.
I am still very interested in seeing if other people =
who have had success
with 815e boards have all been using them with P III =
CPU's or is the
Celeron vs P III issue here just a freak =
co-incidence.
Jamie
---------------------------------------------------------------=
--------
Jamie =
Curtis =
=
email: jpc2@cs.waikato.ac.nz
WAND =
Group &=
nbsp; Lab =
G1.31 phone +64 21 392 102
Computer Science Department, =
University of Waikato, New Zealand
---------------------------------------------------------------=
--------
_______________________________________________
eepro100 mailing list
eepro100@scyld.com
http://www.scyld.com/mailman/listinfo/eepro100
------_=_NextPart_001_01C07A8B.A64C8790--