All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Johan Kullstam" <kullstam@ne.mediaone.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5.1-pre11 de2104X tulip driver problem
Date: 13 Dec 2001 17:57:13 -0500	[thread overview]
Message-ID: <m2hequpw3a.fsf@euler.axel.nom> (raw)
In-Reply-To: <20011213150346.A31843@Sophia.soo.com>
In-Reply-To: <20011213150346.A31843@Sophia.soo.com>

"really mason@soo.com" <lnx-kern@Sophia.soo.com> writes:

> 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
> 
> ====================================================================

i have a DEC DE450 (based on 21041 AA chipset).  i guess, for
2104[01], tulip driver has been broken since 2.4.4 (yes, that's over
six months of brokeness).  yes, jeff garzik knows about it.  i've
emailed the list and sourceforge &c.

rememdies --

0) buy a new network card.

1) use the de4x5 driver instead.

2) use the older tulip driver 0.9.14.  download it from 
   http://sourceforge.net/projects/tulip/

if you go with 2, just download.  have /usr/src/linux be your linux
source (or a symlink to them).  go into tulip-0.9.14/src, make dep,
make.  then copy tulip.o into /lib/modules/2.[45].X/kernel/drivers/net/tulip
which replaces the kernels one.

best of luck.

-- 
J o h a n  K u l l s t a m
[kullstam@mediaone.net]

  reply	other threads:[~2001-12-13 22:57 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 [this message]
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=m2hequpw3a.fsf@euler.axel.nom \
    --to=kullstam@ne.mediaone.net \
    --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.