From: "Jamie" <darkshad@home.com>
To: "Jeff Garzik" <jgarzik@mandrakesoft.com>
Cc: <becker@webserv.gsfc.nasa.gov>, <jam@McQuil.com>,
<hendriks@lanl.gov>, <jgolds@resilience.com>,
<sdegler@degler.net>, <tulip-users@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>,
"Anders Hedborg" <ahe@systemkoreograferna.com>
Subject: Re: Tulip Drivers Problem in 2.4.xx Kernel
Date: Mon, 5 Nov 2001 20:29:38 -0500 [thread overview]
Message-ID: <000b01c16662$81ccdf00$0300a8c0@theburbs.com> (raw)
In-Reply-To: <000c01c16655$78a1af80$0300a8c0@theburbs.com> <3BE729BB.F84AFAEF@mandrakesoft.com>
Ok Jeff thanks I will definately give that a try I have never tried the
dec4x5 drivers I will see if it works
for my NIC.
Thanks,
Jamie
----- Original Message -----
From: "Jeff Garzik" <jgarzik@mandrakesoft.com>
To: "Jamie" <darkshad@home.com>
Cc: <becker@webserv.gsfc.nasa.gov>; <jam@McQuil.com>; <hendriks@lanl.gov>;
<jgolds@resilience.com>; <sdegler@degler.net>;
<tulip-users@lists.sourceforge.net>; <linux-kernel@vger.kernel.org>; "Anders
Hedborg" <ahe@systemkoreograferna.com>
Sent: Monday, November 05, 2001 7:07 PM
Subject: Re: Tulip Drivers Problem in 2.4.xx Kernel
Currently there is a bug in 2.4.x-current tulip drivers that prevents
21041 from initializing correctly. Until then you can use the 'de4x5'
driver or download the latest stable version on the tulip web page:
http://sourceforge.net/projects/tulip/
--
Jeff Garzik | Only so many songs can be sung
Building 1024 | with two lips, two lungs, and one tongue.
MandrakeSoft | - nomeansno
next prev parent reply other threads:[~2001-11-06 1:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-05 23:56 Tulip Drivers Problem in 2.4.xx Kernel Jamie
2001-11-06 0:07 ` Jeff Garzik
2001-11-06 1:29 ` Jamie [this message]
2001-11-06 16:50 ` EricMarts
2001-11-06 19:12 ` Jamie
2001-11-06 19:17 ` EricMarts
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='000b01c16662$81ccdf00$0300a8c0@theburbs.com' \
--to=darkshad@home.com \
--cc=ahe@systemkoreograferna.com \
--cc=becker@webserv.gsfc.nasa.gov \
--cc=hendriks@lanl.gov \
--cc=jam@McQuil.com \
--cc=jgarzik@mandrakesoft.com \
--cc=jgolds@resilience.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sdegler@degler.net \
--cc=tulip-users@lists.sourceforge.net \
/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