From: aris <aris@cathedrallabs.org>
To: Jacek Pop?awski <jpopl@interia.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: new eepro driver seems broken
Date: Wed, 9 Jan 2002 13:27:52 -0200 [thread overview]
Message-ID: <20020109152752.GG1954@cathedrallabs.org> (raw)
In-Reply-To: <20020109125532.A1118@localhost.localdomain>
In-Reply-To: <20020109125532.A1118@localhost.localdomain>
> I assume there is the same version of eepro driver in 2.2.21-pre2 and 2.4.17.
>
> Version included in kernel 2.2.20 is broken, becouse sometime ethernet card
> "dies" - I can't ping it from outside. However, when eepro card is in server,
> and I ping workstation from there - card works again. So my current solution is
> script which pings everything in localnet all the time.
yes, it's broken
> But new version works much worse for me. In 2.2.21-pre2 and 2.4.17 card never
> dies - it always work, but there are many problems with connections. I thought
> it's problem with MASQ, but it behaves exactly the same on 2.2 and 2.4. When I
> send single file by scp - I have transfer bigger than 100KB/s. But when I watch
> WWW or use p2p - transfer is very small or stops.
the 0.13 version had this mention: become stable. performance is scheduled
for next versions. you may try eepro.c from 2.2.13 kernel but as i could see
it's less stable than 0.13 version.
> Driver from 2.2.20 works bad, newer driver works bad, too, but in another way.
> Where can I find older releases of eepro driver? How can I contact author
> (email from eepro.c doesn't work) ? Is anyone still using EtherExpress ISA 10 ?
i think there's nobody else working on this driver right now. you may send
questions to lkml with a copy to me.
--
aris
prev parent reply other threads:[~2002-01-09 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 11:55 Jacek Popławski
2002-01-09 15:27 ` aris [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020109152752.GG1954@cathedrallabs.org \
--to=aris@cathedrallabs.org \
--cc=jpopl@interia.pl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®