From: octave klaba <oles@ovh.net>
To: linux-net@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: VM-global-2.2.18pre17-7
Date: Sat, 28 Oct 2000 14:53:41 +0200 [thread overview]
Message-ID: <39FACC55.29E85BE0@ovh.net> (raw)
In-Reply-To: <Pine.LNX.4.05.10010271651240.14633-100000@marina.lowendale.com.au> <Pine.LNX.4.21.0010271124550.5338-100000@freak.distro.conectiva> <20001027181344.B1248@niksula.cs.hut.fi> <39F9CEF3.2BE915D9@ovh.net>
>The Becker's driver from ftp://ftp.scyld.com/pub/network/eepro100.c cures
>the error messages, but the network still stalls, and worse yet, seems to
>stall forever (as opposed to few minutes with 2.2.18pre17 driver).
this eepro100.c works for me
asus/dual piii-800 133mhz/768ram ecc/mylex-170/2x18Go
thanks for your help.
Octave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-10-28 12:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0010251633080.3324-100000@freak.distro.conectiva>
[not found] ` <39F84B64.5935C12@ovh.net>
[not found] ` <39F8566D.51561CB3@profmakx.de>
2000-10-26 16:21 ` VM-global-2.2.18pre17-7 octave klaba
2000-10-26 19:53 ` VM-global-2.2.18pre17-7 Timothy Ball
2000-10-27 10:31 ` VM-global-2.2.18pre17-7 Andrew Morton
2000-10-27 5:59 ` VM-global-2.2.18pre17-7 Neale Banks
2000-10-27 13:29 ` VM-global-2.2.18pre17-7 Marcelo Tosatti
2000-10-27 15:13 ` VM-global-2.2.18pre17-7 Ville Herva
2000-10-27 15:42 ` VM-global-2.2.18pre17-7 Jeff Nguyen
2000-10-27 17:16 ` VM-global-2.2.18pre17-7 Alan Cox
2000-10-27 17:40 ` VM-global-2.2.18pre17-7 Jeff Nguyen
2000-10-27 18:52 ` VM-global-2.2.18pre17-7 octave klaba
2000-10-28 12:53 ` octave klaba [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=39FACC55.29E85BE0@ovh.net \
--to=oles@ovh.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.