anyone got the same problem with DIGITAL 21143 network card ?

anyone got the same problem with DIGITAL 21143 network card ?

[Ishak Hartono]

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 ?

-Ishak-

Re: anyone got the same problem with DIGITAL 21143 network card ?

[listmail]

I do not have that problem with either my 21140 or my 21141 both of which
use the same driver...not an exact answer, but hopefully knowing it works
fine with other cards in that series, on a 2.4.3, 2.4.12, 2.4.5 kernel
helps.

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 ?
>
> -Ishak-
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

Re: anyone got the same problem with DIGITAL 21143 network card ?

[Sven Koch]

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/)

Re: anyone got the same problem with DIGITAL 21143 network card ?

[Russell King]

On Thu, Nov 22, 2001 at 09:50:10PM +0800, 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 ?

I'm not sure if this counts or not.  One of my kernel build boxes for ARM
is a NetWinder, which I run over the 100MBit port (which is a 21143).  I've
been building kernels on it for ages under various 2.4 kernel versions (both
Linus and -ac) without any problems.

Linux sturm 2.4.15-pre5 #32 Sat Nov 17 22:10:45 GMT 2001 armv4l unknown

lspci reports:

00:0a.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43 (rev 41)
        Subsystem: Unknown device 574e:5554
        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: 20 min, 40 max, 32 set, cache line size 08
        Interrupt: pin A routed to IRQ 22
        Region 0: I/O ports at 6000 [size=128]
        Region 1: Memory at c1000000 (32-bit, non-prefetchable) [size=1K]
        Expansion ROM at 80000000 [disabled] [size=256K]

Note that I haven't tried 2.4.14 on this machine, only 2.4.13-ac8 and
2.4.15-pre*.

--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html

Re: anyone got the same problem with DIGITAL 21143 network card ?

[Peter Adebahr]

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

I have had the same problem with my older 21140 card, which I have
replaced a couple of days ago. In other systems, I have 21143 cards,
which all behave as expected (all -ac kernels until last one).

There was an easy remedy, however: use the tulip-0.9.14 or 1.1.8 drivers.

Good Luck,
Peter

Re: anyone got the same problem with DIGITAL 21143 network card ?

[Juan Quintela]

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

Re: anyone got the same problem with DIGITAL 21143 network card ?

[Peter Kjellström]

I too have the same problem with atleast 2.4.9 and later (I think
it broke somewhere around 2.4.4). However, in my case there is a fix (not
a practical one though). Simply pull the ethernet cable out and plug it
back in again and it starts working.

I see no errors and the cards signal link and 100fdx.

I currently run 2.4.1 which is ok (tulip version 0.9.13a).

My card is a dlink 500TX detected (2.4.1) like this:


 Linux Tulip driver version 0.9.13a (January 20, 2001)
 PCI: Found IRQ 5 for device 00:09.0
 eth0: Digital DS21143 Tulip rev 65 at 0xbc00, 00:80:C8:F7:14:BA, IRQ 5.


some version info (guessing it broke somewhere around 2.4.4)
2.4.1      tulip-0.9.13a     OK
2.4.4-ac12 tulip-0.9.14e     bad*
2.4.6      tulip-0.9.15-pre6 bad*

* can't reboot the machine in question, but IIRC...


/Peter

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 ?
>
> -Ishak-

Re: anyone got the same problem with DIGITAL 21143 network card ?

[Martin Josefsson]

On Thu, 22 Nov 2001, Peter Kjellström wrote:

Hi Peter.

> I too have the same problem with atleast 2.4.9 and later (I think
> it broke somewhere around 2.4.4). However, in my case there is a fix (not
> a practical one though). Simply pull the ethernet cable out and plug it
> back in again and it starts working.

I've used 2.4.10-ac12 with a D-Link DFE570TX NIC (quad DECchip 21143
tulip) without any problems. Maybe the tulipdriver in -ac is somewhat
diffrent.


> My card is a dlink 500TX detected (2.4.1) like this:
> 
> 
>  Linux Tulip driver version 0.9.13a (January 20, 2001)
>  PCI: Found IRQ 5 for device 00:09.0
>  eth0: Digital DS21143 Tulip rev 65 at 0xbc00, 00:80:C8:F7:14:BA, IRQ 5.

My cards are also DS21143 Tulip rev 65, they are located behind a DECchip
21152 pci-pci bridge but I don't think it matters.

(it's Intel who produces the chips these days but I don't think they have
changed the design)

I've used the vanilla driver in 2.4.10-ac12 and the tulip-ss010402-poll
and tulip-NAPI-011015 drivers and they all work fine with my NIC.

/Martin

Never argue with an idiot. They drag you down to their level, then beat you with experience.

Re: anyone got the same problem with DIGITAL 21143 network card ?

[Peter Kjellström]

On Thu, 22 Nov 2001, Juan Quintela wrote:

> Could you check if this patch makes your card work?

On my system it behaves no diffrent from 2.4.[14,15] vanilla :-(
My box still requires me to a disconnect/reconnect my ethernet cable with
these new tulip drivers... (resulting in that I still run 0.9.13a)

Here is what my kernel spits out during boot (2.4.15-final):

 Linux Tulip driver version 0.9.15-pre9-quintela (Nov 23, 2001)
 PCI: Found IRQ 5 for device 00:09.0
 tulip0:  EEPROM default media type Autosense.
 tulip0:  Index #0 - Media MII (#11) described by a 21142 MII PHY
 (3) block.
 tulip0:  MII transceiver #8 config 3100 status 782d advertising 01e1.
 eth0: Digital DS21143 Tulip rev 65 at 0xbc00, 00:80:C8:F7:14:BA, IRQ 5.
 .
 .
 .
 eth0: Setting full-duplex based on MII#8 link partner capability of 41e1.


and here is lspci for the NIC:

 00:09.0 Ethernet controller: Digital Equipment Corporation DECchip
 21142/43 (rev 41)
	Subsystem: D-Link System Inc DFE-500TX Fast Ethernet
	Flags: bus master, medium devsel, latency 32, IRQ 5
	I/O ports at bc00 [size=128]
	Memory at e8061000 (32-bit, non-prefetchable) [size=1K]
	Expansion ROM at <unassigned> [disabled] [size=256K]


ifconfig:

 eth0     Link encap:Ethernet  HWaddr 00:80:C8:F7:14:BA  
          inet addr:192.168.1.253  Bcast:192.168.1.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:1 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:5 Base address:0xbc00 

...doing some pinging (no ans. then host unreachable)...

 eth0     Link encap:Ethernet  HWaddr 00:80:C8:F7:14:BA  
          inet addr:192.168.1.253  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:1 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:5 Base address:0xbc00 

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

/Peter