From: Juan Quintela <quintela@mandrakesoft.com>
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: 23 Nov 2001 01:50:26 +0100 [thread overview]
Message-ID: <m2u1vml38t.fsf@trasno.mitica> (raw)
In-Reply-To: <001201c1735c$9ac546d0$0b01a8c0@lotus>
In-Reply-To: <001201c1735c$9ac546d0$0b01a8c0@lotus>
>>>>> "ishak" == Ishak Hartono <lotus@upnaway.com> writes:
ishak> I tried to compile 2.4.14 and successfully detect the digital 21143 network
ishak> card, however, i can't ping out
ishak> this is just a curiosity, because it works with my 2.2.17 kernel
ishak> the reason why i didn't move to 2.4.x yet because i got this problem with
ishak> 2.4.5 as well and gave it a try again on 2.4.14 kernel
ishak> anyone know what should i check in the system other than blaming on the
ishak> kernel ?
Could you check if this patch makes your card work?
It works for me.
Later, Juan.
--- linux/drivers/net/tulip/21142.c.orig Mon Nov 5 20:50:27 2001
+++ linux/drivers/net/tulip/21142.c Mon Nov 5 21:26:40 2001
@@ -188,8 +188,9 @@
int i;
for (i = 0; i < tp->mtable->leafcount; i++)
if (tp->mtable->mleaf[i].media == dev->if_port) {
+ int startup = ! ((tp->chip_id == DC21143 && tp->revision == 65));
tp->cur_index = i;
- tulip_select_media(dev, 1);
+ tulip_select_media(dev, startup);
setup_done = 1;
break;
}
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
next prev parent reply other threads:[~2001-11-23 0:52 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
2001-11-22 17:15 ` Russell King
2001-11-22 17:21 ` Peter Adebahr
2001-11-23 0:50 ` Juan Quintela [this message]
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=m2u1vml38t.fsf@trasno.mitica \
--to=quintela@mandrakesoft.com \
--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®