From: Patrick Cole <z@amused.net>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tulip driver still broken
Date: Thu, 2 Aug 2001 00:36:07 +1000 [thread overview]
Message-ID: <20010802003607.A9699@backdraft.amused.net> (raw)
In-Reply-To: <Pine.LNX.3.96.1010730180814.27870D-100000@mandrakesoft.mandrakesoft.com>
Mon, Jul 30, 2001 at 06:09:33PM -0500, Jeff Garzik wrote:
> On Mon, 30 Jul 2001, Joshua Schmidlkofer wrote:
>
> > I am afraid of post these days. However, I must comment that I too am having
> > trouble with the tulip driver, on several SMC nic's that use the DEC
> > chipset. I tried mii_tool, with no success.
> >
> > I have just been copying the tulip driver from 2.4.4 forward... because I
> > don't have enough time to try and create an intelligent error report.
>
> Thanks for the report!
>
> Currently there are problems with 21041 old chipsets, which include SMC
> and several other cards. You can use 0.9.14 from
> http://sf.net/projects/tulip/ until I get around to fixing it.
My 21041 is also not working with late 2.4 series tulip drver. I've heard the
de4x5 driver does however work.
--
Patrick Cole - Debian Developer <ltd@debian.org>
- Linux.com Volunteer <z@linux.com>
- ANU JCSMR ICU Staff <Patrick.Cole@anu.edu.au>
- PGP 1024R/60D74C7D C8 E0 BC 79 69 BE 78 99
AA 0F EB 16 F8 4B FE 5A
next prev parent reply other threads:[~2001-08-01 14:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 22:19 tulip driver still broken Thomas Zehetbauer
2001-07-30 22:57 ` Joshua Schmidlkofer
2001-07-30 23:09 ` Jeff Garzik
2001-07-30 23:30 ` Michal Jaegermann
2001-08-01 14:36 ` Patrick Cole [this message]
2001-07-31 13:23 ` Chris Friesen
2001-07-31 18:00 ` Jeff Garzik
2001-08-01 15:51 ` Ben Greear
2001-08-01 16:45 ` joseph.bueno
2001-08-01 21:14 ` Justin Guyett
2001-08-02 7:35 ` joseph.bueno
2001-08-01 21:52 ` Jeff Garzik
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=20010802003607.A9699@backdraft.amused.net \
--to=z@amused.net \
--cc=jgarzik@mandrakesoft.com \
--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 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.