EtherExpress Pro module installation failure

Posted on 1997-02-28
Last Modified: 2010-03-18
We've successfully installed the new Debian Linux, except that the EtherExpress Pro/10+ card driver won't seem to install.  The details are below; does anyone have any ideas as to what the problem might be, or can you point me to where I might be able to find the solution?
David Scott Farrar
UCSD Cognitive Science

--The Details---------------------------------------------

We're trying to install Debian GNU/Linux (from CD-ROM) version 1.2.6, Kernel 2.0.27 on a 180MHz PentiumPro with an Intel Etherexpress Pro/10+ ISA card.  Following the instructions in the document "install.txt", we
were able to install everything except the device driver module for our ethernet card, "eepro".  When we select "Configure Device Driver Modules" and choose "eepro", we get the message:
        loading device 'eth0'
        Initialization of eepro failed
        Installation failed.

From a Windows 95 partition, the card seems to work fine; Windows recognizes the card as an "Intel EtherExpress PRO/10 (PnP Enabled)", and we are able to run Netscape, etc.  Under the Windows System Properties/Device Manager/Resources tab, the card uses I/O range 0x230-0x23F and IRQ 09.  Windows does not detect any device conflicts with these resources.

During a linux boot, there are no ethernet device messages
"".  From linux, a "cat /proc/ioports" shows no devices at all in the range of 0x200-0x2F7, and "cat /proc/interrupts" shows that irq 9 is not used.  We tried passing ethernet arguments to the kernel:
        linux ether=9,0x230,0,0,eth0
and we tried loading the "eepro" module after booting linux:
        insmod eepro
        insmod eepro io=0x230 irq=9    (From Windows Resources tab)
        insmod eepro io=0x200 irq=0
         (From /usr/src/linux/Documentation/networking/net-modules.txt)
both fail to install and give the same error message:
        loading device 'eth0'
        Initialization of eepro failed
We built a new kernel specifically including the Etherexpress Pro driver, but we get no ethernet device messages during boot, nor does the device appear in /dev.

We're baffled.  Any suggestions would be greatly appreciated, and can be sent to:

Question by:farrar
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2

Accepted Solution

dux earned 200 total points
ID: 1584207
Look at
There you can find detailed instruction about your question.
Good Luck!

Author Comment

ID: 1584208
The website page: 
has instructions for the EtherExpress Pro/100.  I looked around the same site, however, and found instructions and new driver source code for the card I have, the EtherExpress Pro/10+ ISA
(http://titan.cs.uni-bonn.ed/~canavan/eepro.c).  I recompiled the kernel and the modules with the new driver source code, but I get the same behavior:
    loading device 'eth0'
    Initialization of eepro failed


Expert Comment

ID: 1584209
Compile your kernel with EtherExpress Pro/10+ support, not module.

Author Comment

ID: 1584210
When I compiled the Pro/10+ driver, I put it in the kernel (not as a loadable module).  The behavior was still the same as before (no ethernet device messages during bootup).  And after booting up, I tried 'insmod' (as before, with&without io/irqs), but still no change.


Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

I have seen several blogs and forum entries elsewhere state that because NTFS volumes do not support linux ownership or permissions, they cannot be used for anonymous ftp upload through the vsftpd program.   IT can be done and here's how to get i…
Note: for this to work properly you need to use a Cross-Over network cable. 1. Connect both servers S1 and S2 on the second network slots respectively. Note that you can use the 1st slots but usually these would be occupied by the Service Provide…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question