From: David Ford <david+cert@blue-labs.org>
To: Michal Jaegermann <michal@harddata.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tulip driver again
Date: Fri, 29 Mar 2002 19:27:14 -0500 [thread overview]
Message-ID: <3CA50662.6090709@blue-labs.org> (raw)
In-Reply-To: <20020328174724.A24374@mail.harddata.com>
"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.
David
Michal Jaegermann wrote:
>I know that this is boring and a number of my earlier reports was
>apparently ignored but a tulip driver "0.9.15-pre10 (Mar 8, 2002)"
>as used in 2.4.19-pre4 still does not really work. I know that it is
>
next prev parent reply other threads:[~2002-03-30 0:24 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 [this message]
2002-03-30 7:38 ` Jeff Garzik
[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=3CA50662.6090709@blue-labs.org \
--to=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