Linux and DE-200+ ethernet cards: setup.

I've a problem getting Linux (debian, but same problems with RedHat and Slackware) talking with my Ethernet card.

The DE-200+ (self proclaiming NE-2000 compatible, but see the Ethernet HOWTO) is not autodetected. Even using io=0x300 irq=5 doesn't help because the driver waits for an acknowledge to the reset command, which never arrives.

After disabling that part of the driver initialization I can get the driver loaded into the kernel. Debugging printouts confirm that the card is actually there sending interrupts and I can even stop it with ifconfig eth0 down.

Problem is, I cannot send/receive packets [done the appropriate ifconfig/route add thing]. If I enable NE_SANITY_CHECK I get this additional piece of information:

eth0: Tx packet transfer address mismatch, 202a (expected) vs. 2054 (actual)

The 20 part is the offset into the transmit ring while 0x2a is the number of bytes that the kernel asked to transmit and 0x54 is the number of bytes that the 8390 [actually it's an 8392 on my board]
reports. Since 0x54 = 2 x 0x2a I tend to believe that a byte/word misunderstanding is happening somewhere, but I cannot figure out where.

I've run some additional tests: A colleague of mine has a working Linux machine using a 220CT, hence I've grabbed the nearest thing to it that was available to me, a 220CAT. It behaves exactly the same way as my 200+, except for the fact that it's autodetected (it acknowledges the reset command). The 220CT doesn't work in his PC, so I tend to dismiss problems with the rest of my PC.

Suggestion anybody?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

With the price of some ethernet cards below $50, you may try buying a new one at your local computer store.  If it works, great; you now have a weekend free to go hiking.  If not, return it.
carlettoAuthor Commented:
If it was my personal PC I would have gone out and bought a new card a long ago. Unfortunately, this is the PC I use at work and it is presently running Windows 95. The only chance I have to turn it into an usable machine running Linux is if I can do it at zero cost (and putting a personal card in a PC owned by the university is not an option either)
I think that you have two options -either bite the bullet and buy a new net card (which I know you don't want to do) or write a new driver for the card. This should fix the problem but will probably take you a bit of time.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux Networking

From novice to tech pro — start learning today.