public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "really mason@soo.com" <lnx-kern@Sophia.soo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.1-pre11 de2104X tulip driver problem
Date: Thu, 13 Dec 2001 18:36:46 -0500	[thread overview]
Message-ID: <3C193B8E.94F769B5@mandrakesoft.com> (raw)
In-Reply-To: <20011213150346.A31843@Sophia.soo.com>

"really mason@soo.com" wrote:
> i'm one of those dinosaurs using a 10base2 network and really
> old DLink-530 21040 and 21041 based ethercards.
[...]
> kernel: de0: SROM-listed ports: TP

Thanks for the report.  If you are using 10base2 that's definitely a
bug.

Can you please change DE_DEF_MSG_ENABLE in de2104x.c as shown below, and
[privately] e-mail me /bin/dmesg and "lspci -vvv" output?

-#define DE_DEF_MSG_ENABLE       (NETIF_MSG_DRV          | \
-                                 NETIF_MSG_PROBE        | \
-                                 NETIF_MSG_LINK         | \
-                                 NETIF_MSG_TIMER        | \
-                                 NETIF_MSG_IFDOWN       | \
-                                 NETIF_MSG_IFUP         | \
-                                 NETIF_MSG_RX_ERR       | \
-                                 NETIF_MSG_TX_ERR)
+#define DE_DEF_MSG_ENABLE       0xffffffff

-- 
Jeff Garzik      | Only so many songs can be sung
Building 1024    | with two lips, two lungs, and one tongue.
MandrakeSoft     |         - nomeansno

      parent reply	other threads:[~2001-12-13 23:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-13 20:03 2.5.1-pre11 de2104X tulip driver problem really mason@soo.com
2001-12-13 22:57 ` Johan Kullstam
2001-12-13 23:33   ` Jeff Garzik
2001-12-14  0:23     ` Johan Kullstam
2001-12-13 23:36 ` Jeff Garzik [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=3C193B8E.94F769B5@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lnx-kern@Sophia.soo.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