From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: David Ford <david+cert@blue-labs.org>
Cc: Michal Jaegermann <michal@harddata.com>, linux-kernel@vger.kernel.org
Subject: Re: tulip driver again
Date: Sat, 30 Mar 2002 02:38:06 -0500 [thread overview]
Message-ID: <3CA56B5E.7030508@mandrakesoft.com> (raw)
In-Reply-To: <20020328174724.A24374@mail.harddata.com> <3CA50662.6090709@blue-labs.org>
David Ford wrote:
> "Me too" however I managed to get mine to work by swaping PCI cards
> in/out and doing power off reboots. It is working on this particular
> boot up so I'm leaving it running.
>
> Jeff Garzik, if you want the lspci, register dump, etc, please speak up.
Yes, please do.
The more bug reports I can receive (in private or CC'd to lkml), the
better picture I get. If you have multiple tulips, feel free to email
reports on those too :)
Best output is:
lspci -vvvn
dmesg, after updating drivers/net/tulip/tulip.h TULIP_DEBUG to 5,
and recompiling
tulip-diag -mmaavvveef
tulip-diag was written by Donald Becker, and is available from
ftp://www.scyld.com/pub/diag/ Compiling instructions are at the end of
tulip-diag.c. You should grab libmii.c as well.
Jeff
next prev parent reply other threads:[~2002-03-30 7:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-29 0:47 tulip driver again Michal Jaegermann
2002-03-29 2:40 ` brian
2002-03-29 4:57 ` Michal Jaegermann
2002-03-29 19:28 ` Jeff Garzik
2002-03-30 0:27 ` David Ford
2002-03-30 7:38 ` Jeff Garzik [this message]
[not found] <483868577@toto.iv>
2002-04-02 0:45 ` Peter Chubb
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=3CA56B5E.7030508@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=david+cert@blue-labs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal@harddata.com \
/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