From: "really mason@soo.com" <lnx-kern@Sophia.soo.com>
To: linux-kernel@vger.kernel.org
Subject: 2.5.1-pre11 de2104X tulip driver problem
Date: Thu, 13 Dec 2001 15:03:46 -0500 [thread overview]
Message-ID: <20011213150346.A31843@Sophia.soo.com> (raw)
Just a tulip driver bug report:
i'm one of those dinosaurs using a 10base2 network and really
old DLink-530 21040 and 21041 based ethercards.
This is what a recent kernel version (2.5.1-pre10) working
tulip driver prints out when booting up:
kernel: tulip0: 21041 Media table, default media 0800 (Autosense).
kernel: tulip0: 21041 media #0, 10baseT.
kernel: tulip0: 21041 media #4, 10baseT-FDX.
kernel: tulip0: 21041 media #1, 10base2.
[...]
kernel: eth0: Digital DC21041 Tulip rev 17 at 0xe0800f80, 21041 mode, 00:80:C8:3E:D0:BC, IRQ 12.
[...]
kernel: eth0: No 21041 10baseT link beat, Media switched to AUI.
Card still works on my 10base2 network even tho i haven't got
an AUI port on the ethercard.
======================================================================
This is what the non working 2.5.1-pre11 tulip driver prints out:
kernel: de2104x PCI Ethernet driver v0.5.1 (Nov 20, 2001)
kernel: de0: SROM-listed ports: TP
kernel: eth0: 21041 at 0xe0800f80, 00:80:c8:3e:d0:bc, IRQ 12
[...]
kernel: eth0: set link 10baseT auto, mode 7ffc0040, sia 10c4,ffffef01,ffffffff,ffff0008
kernel: set mode 7ffc0000, set sia ef01,ffff,8
====================================================================
regards,
b <mason@soo.com>
next reply other threads:[~2001-12-13 20:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 20:03 really mason@soo.com [this message]
2001-12-13 22:57 ` 2.5.1-pre11 de2104X tulip driver problem Johan Kullstam
2001-12-13 23:33 ` Jeff Garzik
2001-12-14 0:23 ` Johan Kullstam
2001-12-13 23:36 ` 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=20011213150346.A31843@Sophia.soo.com \
--to=lnx-kern@sophia.soo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox