All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Manfred Bartz" <md-linux-kernel@logi.cc>
To: linux-kernel@vger.kernel.org
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>
Subject: Re: ethernet driver probs (tulip, de4x5, 3c509)
Date: 20 Feb 2001 14:31:45 +1100	[thread overview]
Message-ID: <20010220033145.8260.qmail@logi.cc> (raw)
In-Reply-To: <Pine.LNX.3.96.1010219085051.17842D-100000@mandrakesoft.mandrakesoft.com>
In-Reply-To: Jeff Garzik's message of "Mon, 19 Feb 2001 08:52:15 -0600 (CST)"

Jeff Garzik <jgarzik@mandrakesoft.com> writes:

> On 20 Feb 2001, Manfred Bartz wrote:
> > I have 3 NICs (2*DEC, 1*3c509) in my gateway (P75, 40M RAM).
> > 
> > tulip.o in 2.4.1 insists on selecting 10baseT, no command
> > line option can convince it otherwise.  tulip.o in 2.2.16 auto
> > detected media and worked fine.
> 
> A little info on your cards would be helpful.  With well over 100
> different types of Tulip cards, I can't just read your mind :)

The problem seems to be generic.  It is always related to media
selection and occurs with at least 3 different NICs which are based 
on the 21040 and 21041 chips.

> lspci, tulip-diag, and dmesg output would all be helpful.

I have not got lspci but since the driver reports the correct IRQ and
IO-ports that should be no issue.  (I'll install lspci if necessary).

Outputs of dmesg, tulip-diag, and some other info is now at:
        <http://www.logi.cc/tulip/>

> > de4x5.o in 2.4.1 needs to be told the media, then works fine.
> > de4x5.o in 2.2.16 auto detected media and worked fine.
> 
> de4x5 is going away, anyway.

Pity.  It works and I really like the manual options interface...   :/

-- 
Manfred

      reply	other threads:[~2001-02-20  3:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-19 13:07 ethernet driver probs (tulip, de4x5, 3c509) Manfred Bartz
2001-02-19 14:52 ` Jeff Garzik
2001-02-20  3:31   ` Manfred Bartz [this message]

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=20010220033145.8260.qmail@logi.cc \
    --to=md-linux-kernel@logi.cc \
    --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.