mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pierfrancesco Caci <ik5pvx@penny.ik5pvx.ampr.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Tulip problem in Kernel 2.4.11
Date: 11 Oct 2001 09:06:17 +0200	[thread overview]
Message-ID: <87u1x6zmdy.fsf@penny.ik5pvx.ampr.org> (raw)
In-Reply-To: <000701c151c4$0e6933e0$0300a8c0@theburbs.com>
In-Reply-To: <000701c151c4$0e6933e0$0300a8c0@theburbs.com>

:-> "Jamie" == Jamie  <darkshad@home.com> writes:

    > Hello there is a definate problem with the tulip drivers in the 2.4.11
    > kernel.
    > I have a DEC DC 21041 NIC which uses the tulip drivers.  I use the 2.2.19
    > kernel and there are
    > two different sets of tulip drivers listed in that kernel which
    > I can choose 
    > from in the 2.4.11 kernel there is only one. When I do a
    > modprobe tulip the 
    > driver loads fine as you can see bellow there are no strange
    > error messages 
    > ect.  But I can not communicate though this one NIC. When I use
    > the 2.2.19 
    > Kernel it works fine.

I can add to this that 2.4.2 works fine, I've tried 2.4.9 and 2.4.11
and I can't use the lan either. 
In 2.4.11, I can see that the driver can sense if I plug/unplug the
connector (10BaseT, connected to a Compaq Netelligent 8 port hub), but
nothing more.

here's what 2.4.2 says about the card:

# lspci -v -v -s 00:03.0
00:03.0 Ethernet controller: Digital Equipment Corporation DECchip 21041 [Tulip Pass 3] (rev 11)
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 96
        Interrupt: pin A routed to IRQ 15
        Region 0: I/O ports at fc00 [size=128]
        Region 1: Memory at df000000 (32-bit, non-prefetchable) [size=128]
        Expansion ROM at de000000 [disabled] [size=256K]

I am now trying to compile again 2.4.11 with the driver as module,
instead of built-in, just to see if I can pass some parameters to
force a media type without rebooting every time.

Please suggest any other test I can make, or if you need more informations.

Pf

-- 

-------------------------------------------------------------------------------
 Pierfrancesco Caci | ik5pvx | mailto:p.caci@tin.it  -  http://gusp.dyndns.org
  Firenze - Italia  | Office for the Complication of Otherwise Simple Affairs 
     Linux penny 2.4.7 #1 Thu Jul 26 14:48:56 CEST 2001 i686 unknown

  reply	other threads:[~2001-10-11  7:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-10 19:45 Jamie
2001-10-11  7:06 ` Pierfrancesco Caci [this message]
2001-10-11 11:38   ` Johan Kullstam
2001-10-11 12:26     ` Pierfrancesco Caci
2001-10-11 13:50       ` Fabbione

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=87u1x6zmdy.fsf@penny.ik5pvx.ampr.org \
    --to=ik5pvx@penny.ik5pvx.ampr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.caci@tin.it \
    /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®