From: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
To: Donald Becker <becker@scyld.com>,
Linux-Kernel mailing list <linux-kernel@vger.kernel.org>,
linux-net@vger.kernel.org, jgarzik@mandrakesoft.com
Subject: Re: RTL8139 difficulties in 2.2, not in 2.4
Date: Sun, 20 May 2001 16:47:02 +0200 [thread overview]
Message-ID: <20010520164702.A1569@emma1.emma.line.org> (raw)
In-Reply-To: <20010519140413.B1795@emma1.emma.line.org> <Pine.LNX.4.10.10105191107450.956-100000@vaio.greennet> <20010520122759.B2910@emma1.emma.line.org>
In-Reply-To: <20010520122759.B2910@emma1.emma.line.org>; from matthias.andree@stud.uni-dortmund.de on Sun, May 20, 2001 at 12:27:59 +0200
On Sun, 20 May 2001, Matthias Andree wrote:
> > > eth1: Transmit timeout, status 0c 0005 media 18.
It looks like I found a workaround which may help you debugging, if new
questions arise, please ask. Willing to help so this issue can be
resolved for Linux 2.2.20.
1. I'm compiling my eth drivers as modules.
2. I alias eth0 to 3c59x and eth1 to either 8139too or rtl8139 (doesn't
matter); my rtl8139 is the current version 1.13 from scyld.com
3. after X has come up, I issue "ifconfig eth1 down; rmmod rtl8139" (or
8139too, depending on what modules.conf says)
4. I do "ifconfig eth1 up" (pppoe with Deutsche Telekom AG doesn't
require IP, just raw ethernet)
5. I launch pppd which runs pppoe, the problems are gone.
I haven't yet checked if after this procedure, 3D graphics work out, I
don't have current NVidia drivers here, just plain XFree 4.0.3 as
packaged by SuSE.
next prev parent reply other threads:[~2001-05-20 14:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-19 12:04 Matthias Andree
2001-05-19 15:15 ` Donald Becker
2001-05-20 10:27 ` Matthias Andree
2001-05-20 14:47 ` Matthias Andree [this message]
2001-05-21 9:20 ` also in 2.4: " Matthias Andree
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=20010520164702.A1569@emma1.emma.line.org \
--to=matthias.andree@stud.uni-dortmund.de \
--cc=becker@scyld.com \
--cc=jgarzik@mandrakesoft.com \
--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 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®