From: Sven Koch <haegar@sdinet.de>
To: Ishak Hartono <lotus@upnaway.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: anyone got the same problem with DIGITAL 21143 network card ?
Date: Thu, 22 Nov 2001 16:33:03 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.40.0111221625540.9632-100000@space.comunit.de> (raw)
In-Reply-To: <001201c1735c$9ac546d0$0b01a8c0@lotus>
On Thu, 22 Nov 2001, Ishak Hartono wrote:
> I tried to compile 2.4.14 and successfully detect the digital 21143 network
> card, however, i can't ping out
>
> this is just a curiosity, because it works with my 2.2.17 kernel
>
> the reason why i didn't move to 2.4.x yet because i got this problem with
> 2.4.5 as well and gave it a try again on 2.4.14 kernel
>
> anyone know what should i check in the system other than blaming on the
> kernel ?
Same problem here with a p100 and two dec-tulip-cards and 2.4.14.
Driver loads without problems, ifconfig works too, routes are set - even
the 10baseT-link is detected (it switches to 10base2 when I remove the
cable, and back to 10baseT after reattaching)
But the kernel sees nothing on the wire (tcpdump), and nothing it sends is
seen by the other machines.
Dropped Packet/Overrun count (don't remember which of the two) keeps
rising for every packet it tries to send.
The woody-default-kernel (2.2.20?) works without problems.
I will lookup the exact card-type and error-symptomes this night, when I'm
back home. (And possibly try 2.4.15-preNewest, but kernel-compiling on
this to-be-router takes a long time)
c'ya
sven
--
The Internet treats censorship as a routing problem, and routes around it.
(John Gilmore on http://www.cygnus.com/~gnu/)
next prev parent reply other threads:[~2001-11-22 15:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 13:50 Ishak Hartono
2001-11-22 15:01 ` listmail
2001-11-22 15:33 ` Sven Koch [this message]
2001-11-22 17:15 ` Russell King
2001-11-22 17:21 ` Peter Adebahr
2001-11-23 0:50 ` Juan Quintela
2001-11-22 15:37 Peter Kjellström
2001-11-22 15:59 ` Martin Josefsson
2001-11-23 14:05 Peter Kjellström
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=Pine.LNX.4.40.0111221625540.9632-100000@space.comunit.de \
--to=haegar@sdinet.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lotus@upnaway.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
all inboxes | Powered by JetHome®