mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joshua Schmidlkofer <menion@srci.iwpsd.org>
To: Thomas Zehetbauer <thomasz@hostmaster.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tulip driver still broken
Date: Mon, 30 Jul 2001 16:57:19 -0600	[thread overview]
Message-ID: <01073016571903.25803@widmers.oce.srci.oce.int> (raw)
In-Reply-To: <20010731001907.A21982@hostmaster.org>
In-Reply-To: <20010731001907.A21982@hostmaster.org>

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,
 
 joshua

On Monday 30 July 2001 04:19 pm, Thomas Zehetbauer wrote:
> My genuine digital network interface card ceased to work with the tulip
> driver contained in kernel revisions >= 2.4.4 and the development driver
> from sourceforge.net.
>
> It seems that the driver incorrectly configures the card for full duplex
> mode and I could not figure out how to override this with the new
> MODULE_PARM macro.
>
> I am now using the stable driver 0.9.14 from sourceforge.net which works
> fine.
>
> Further information available by request!
>
> Tom
>
> Quantum Mechanics is God's version of "Trust me."


  reply	other threads:[~2001-07-30 23:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30 22:19 Thomas Zehetbauer
2001-07-30 22:57 ` Joshua Schmidlkofer [this message]
2001-07-30 23:09   ` Jeff Garzik
2001-07-30 23:30     ` Michal Jaegermann
2001-08-01 14:36     ` Patrick Cole
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=01073016571903.25803@widmers.oce.srci.oce.int \
    --to=menion@srci.iwpsd.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomasz@hostmaster.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®