[no subject]

The card is not reporting media information though, and I'll bet this is the
problem. It is not autosensing the connection rate or media type.

Have you tried running any of the supplied DOS programs... specifically the
diagnostic routines.?

This might be enough to get the card to reset the PCI information in the
Bios... do this AFTER going into CMOS and resetting the PCI info though...

Linux does appear to be loading the tulip driver which is why you have a
valid eth0 device...

the rather high error rate indicates that it is not talking to your hub &
Lan...

BTW: anyone else reading this, where can I get the updated Vendor Ethernet
Prefixes file???
It would be useful to identify the chipset on this card... (for those who
don't know, the MAC address's first three bytes uniquely identify the chip
vendor for the card...)

-JMS




-----Original Message-----
From: James Moechnig <jmoechni gac edu>
To: Jose M. Sanchez <nresults ex-pressnet com>
Cc: James Moechnig <jmoechni gac edu>; Redhat list <redhat-list redhat com>
Date: Friday, September 18, 1998 3:46 AM
Subject: Re: Kingston KNE110TX vs Dec Tulip


>Ok, I've done a little testing to try and get this card to work with the
tulip
>driver.  Here's what I did.  I booted the machine with the card I've now
>switched back to, the working tulip card, and ran a couple programs,
>outputting to files.  Here's the highlights (deleted some irrelevant
parts):
>
>dmesg:
>eth0: Digital DC21041 Tulip at 0xfc80, 21041 mode, 00 c0 f0 23 ce 35, IRQ
12.
>eth0:21041 Media information at 30, default media 0800 (Autosense).
>eth0:  21041 media #0, 10baseT.
>
>ifconfig:
>eth0      Link encap:Ethernet  HWaddr 00:C0:F0:23:CE:35
>          inet addr:138.236.216.35  Bcast:138.236.223.255
Mask:255.255.240.0
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:7312083 errors:13672237 dropped:0 overruns:0
>          TX packets:906613 errors:255 dropped:0 overruns:0
>          Interrupt:12 Base address:0xfc80
>
>cat /proc/ioports:
>fc80-fcff : Digital DC21041 Tulip
>
>cat /proc/pci:
>  Bus  0, device  14, function  0:
>    Ethernet controller: DEC DC21041 (rev 33).
>      Medium devsel.  Fast back-to-back capable.  IRQ 12.  Master Capable.
>Latency=64.
>      I/O at 0xfc80.
>      Non-prefetchable 32 bit memory at 0xffbeff80.
>
>Then, I did the same thing with the kingston "mystery card" in its place.
I
>used the same pci slot both times, of course.
>
>dmesg:
>eth0: Lite-On 82c168 PNIC at 0xfc00, c0 00 2c f0 b4 08, IRQ 12.
>
>Notice that there was only one eth0 line in dmesg with this card.  does
anyone
>with a real lite-on based card care to comment on weather or not it should
be
>more verbose?
>
>ifconfig:
>eth0      Link encap:Ethernet  HWaddr C0:00:2C:F0:B4:08
>          inet addr:138.236.216.35  Bcast:138.236.223.255
Mask:255.255.240.0
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:0 errors:1 dropped:0 overruns:0
>          TX packets:0 errors:99 dropped:0 overruns:1
>          Interrupt:12 Base address:0xfc00
>
>cat /proc/ioports:
>fc00-fc7f : Lite-On 82c168 PNIC
>
>cat /proc/pci:
>  Bus  0, device  14, function  0:
>    Ethernet controller: Unknown vendor LNE100TX (rev 32).
>      Medium devsel.  Fast back-to-back capable.  IRQ 12.  Master Capable.
>Latency=64.
>      I/O at 0xfc00.
>      Non-prefetchable 32 bit memory at 0xffbeff00.
>
>All this was after a "normal" bootup, except for switching the cards.  With
>the Kingston chipset card, all networking programs that tried to make
>connections took forever to time out, including the usual sendmail but also
>xntpd, which usually times out immediately if there's no route or other
>obvious networking problems.
>
>I'm guessing, at this point, that the silly thing is a new tulip-compatible
>chip that's not fully supported yet but I just may be confused.
>
>It has occurred to me as I was writing this to check and make sure that the
>card is still identified as a Lite-On in /proc/pci before attempting to
load
>any related modules.  Anyone care to comment further?
>
>Jim
>