Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 323
  • Last Modified:

Ethernet initialization

Hi, I have a problem with my ne2000 ethernet card clone running under Linux 4.1 (Red Hat).  Upon booting up Linux prints the error:  "Delaying eth0 initialization"  I've tried everything but I can't get it to work.  The same message prints to my console when I hit the activate button in the network portion of the "control-panel" configuration GUI.  

Also, when I was installing Linux, the install program couldn't find the card anywhere on my system. The card runs perfectly under Win95.  Please help me if you can.  Thank you.
0
dgtester
Asked:
dgtester
  • 2
  • 2
1 Solution
 
dgtesterAuthor Commented:
Edited text of question
0
 
hchengCommented:
Which version of the kernel are you using?  Are you sure you have NE2000 support compiled in?  Are you using the module version of the driver or is it in the kernel?  Also, is your ethernet card one of those plug-n-play cards?
0
 
dgtesterAuthor Commented:
Recently I added the following lines to /etc/conf.modules
in order to fix the problem:
      options eth0 io=0x240 irq=11
      alias eth0 ne
Also, my lilo.conf looks like this
        append="ether=11,0x240,eth0"
Now, as a result of this, not only does the bootup print
      "Delaying eth0 initialization"
but also I got the following lines
     loading device 'eth0'...
     ne.c: No NE*000 card found (i/o = 0x240).
     loading device 'eth0'...
     ne.c: No NE*000 card found (i/o = 0x240).
(I looked at these lines by typing "dmesg"
In case you're wondering, I got the number 0x240 from Win95

Also, if I type:
      "modprobe -t net ne"
I get:
      "Initialization of ne failed"

Kernel version=2.0.18
The ne2000 support was compiled into the kernel (not a module)
No, my card isn't plug and play

Thank you for your help, I tried to give you all the info
you needed
0
 
hchengCommented:
The lilo.conf file looks fine, assuming that your IRQ and I/O is right.  However, I don't think you need the conf.modules file since you are not using modules.  I wonder why you are getting 2 error messages.  Maybe you have the driver both in the kernel and as a module?  Check your start up script and /lib/modules to make sure that you only have one or the other.  You shouldn't have both.

A number of things you may try:

1. look at /proc/ioport, and make sure that the full range is not already in use (it would be 0x240 - 0x25f in your case).  By the way, 0x240 is not one of the default probed addresses.  The probed addresses are (from Ethernet HOWTO):

  0x300, 0x280, 0x320, 0x340, 0x360

Maybe you can try changing the IO address to one of these and see if it works.

2. If your card is a PCI card, try looking at /proc/pci, and see if you can find the IO address.  If it's different from what you think it is, use the one from /proc/pci in your append line.

3. Look at:

  http://cesdis.gsfc.nasa.gov/pub/linux/diag/diagnostic.html

and download the diagnostic program for NE2000 cards to check out your card., just to make sure that your card is a "good clone".

These are suggestions taken from the Ethernet HOWTO.  Hopefully, some of them will apply.

0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now