I'm trying to install and configure an Intel Pro / 1000 EB network card and I can't seem to get it to work. I think I downloaded the wrong driver ie for the wrong kernel. How do I delete the wrong files that I did a make install on? Is it as simple as doing the rm command? Or do I need to go to several locations to eradicate the wrong driver(s)? I installed the e1000 driver package on RedHat 4 version 3.

Thanks,
Scott

OK, I realized that I installed the right driver for my kernel. I did a make uninstall and tried installing the other driver and it gave me an error. So I reinstalled the previous driver and still can't get it to work. I read the README and followed the directions. What are some things I can try to see if RedHat sees the card in the first place? I've also tried switching the port on the back of the computer and I've played with that network utility a little bit. Same results... I get this error: e1000 device eth1 does not seem to be present, delaying initializing.

Thanks,
Scott

I use modprobe to install my nic card under fedora. Make sure .ko (driver) is located under /lib/modules/<KERNEL VERSION>/kernel/drivers/net/e1000/e1000.ko then I type modprobe e1000.

I did the same command and didn't get an error. If the driver wasn't located in /lib/modules etc then I think I would have gotten an error. Yet when I go back to the network utility it still doesn't work and I still get that error. There's got to be something I'm missing here.

~s

You should not need to compile the driver as my 2.6.24 kernel comes with the e1000 and e1000e modules precompiled.

Red Hat 4.3 is a little old no? I think the latest version is 5.4

Perhaps, the driver was there to begin with. I'm not even sure. The reason for using 4.3 is I need it for a specific application that will only run on that version of OS.

~s

OK, back to basics:

Check the card's hardware is visible:

lspci

Is your card listed? If so what as?

Is the module loaded?

lsmod | grep e1000

Is it listed?

What is the output of ifconfig

The card is actually an on board adapter. It's listed as this:

05:00.0 Ethernet controller: Intel Corporation Enterprise Southbridge DPT LAN Co pper (rev 01)
05:00.1 Ethernet controller: Intel Corporation Enterprise Southbridge DPT LAN Co pper (rev 01)

This is what I got from lsmod...


[root@xxxx ~]# lsmod | grep e1000
e1000 178816 0

This is ifconfig:

[root@xxxx ~]# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:191 errors:0 dropped:0 overruns:0 frame:0
TX packets:191 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13086 (12.7 KiB) TX bytes:13086 (12.7 KiB)

This is what I get when I try to configure an ethernet interface:

[root@discreet ~]# ifconfig eth1 192.20.200.157
SIOCSIFADDR: No such device
eth1: unknown interface: No such device
[root@discreet ~]# ifconfig eth0 192.20.200.157
SIOCSIFADDR: No such device
eth0: unknown interface: No such device

Hope that helps...
Thnx,
Scott

Good information. Thank you.

So your hardware is present, and detected. But why the space in "Co pper". Maybe a typo?

And the appropriate module is loaded.

But it is not seen

This won't work until your interface shows up in ifconfig, which it currently does not.

I googled 05:00.0 Ethernet controller: Intel Corporation Enterprise Southbridge DPT LAN Copper

There were 3 results. None helpful.

Please check that this device is enabled in your BIOS.

If so, I am fresh out of ideas and I suggest you disable the on-board interface with your BIOS, and buy another card (they are cheap now, and 3Com-anything seems to work with linux in my experience)

Sorry I cannot be more helpful.

The internal ethernet controller is working in Windows XP64 so I'd assume it's enabled in the BIOS. I guess the next logical step is to buy a cheap ethernet card on ebay or something.

Thanks,
Scott