We help IT Professionals succeed at work.

Linux and DE-200+ ethernet cards: setup.

carletto asked
Medium Priority
Last Modified: 2010-03-17
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?
Watch Question

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.


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.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.