Network Adapter not found / Intel PRO/1000 PL / Fedora Core 4 Kernel 2.6 Dell XPS 400

zhamuth · #1 2nd January 2006, 07:26 AM

Hi,
I am unable to connect to the Internet on my Fedora Core 4 machine. Here are the details:

1. Ran /sbin/lspci. This is an excerpt from what I got.
04:00.0 Ethernet Controller: Intel Corporation: Unknown device 109a (rev 01)

2. Running /sbin/ifconfig comes back with
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
RX, TX packets all ok (skipping details)

3. Running /sbin/ifconfig eth0 (ran the same for eth1, 2, 17). Got the following result:
eth0: error fetching interface information: Device not found.

4. No luck with system-config-network either.

As regards the distribution of Fedora and the machine: Fedora Core 4, Kernel 2.6. Running on a Intel 820 Dual Core, Dell XPS 400 machine. Dual boot with Windows XP Professional (clean install after wiping out factory loaded programs).

Everything is functional when I log in to Windows XP Professional. So hardware failure can be ruled out.

Can someone please help?

Thank you.

jowah · #2 2nd January 2006, 06:20 PM

The reason is that the Intel network drivers that come with the FC4 installation media don't recognize the LAN circuitry on your computer's motherboard. However, there are updated drivers in later FC4 kernel packages.

The solution? In short: boot into XP and download the latest versions of the kernel, kernel-smp and hwdata packages from a FC4 mirror. Put these packages on a USB memory stick or a CD-R(W) and transfer them to FC4 and install/update these packages. After that, you ought to be able to configure the network in FC4.

I have described the process in more detail in two places:

Unable to setup my Network(EM64T) and Can't install Intel (R) Pro 100/VE Network Connection.

So, find and download the following packages from a FC4 mirror near you:

Code:

kernel-2.6.14-1.1653_FC4
kernel-smp-2.6.14-1.1653_FC4
hwdata-0.158.3-1

Install them, then reboot the machine into the new kernel, and you should be able to use the network setup wizard (Desktop->System Settings->Network, same as system-config-network) to configure your network connection.

zhamuth · #3 2nd January 2006, 07:42 PM

Quote:

Originally Posted by jowah

The reason is that the Intel network drivers that come with the FC4 installation media don't recognize the LAN circuitry on your computer's motherboard. However, there are updated drivers in later FC4 kernel packages.

The solution? In short: boot into XP and download the latest versions of the kernel, kernel-smp and hwdata packages from a FC4 mirror. Put these packages on a USB memory stick or a CD-R(W) and transfer them to FC4 and install/update these packages. After that, you ought to be able to configure the network in FC4.

I have described the process in more detail in two places:

Unable to setup my Network(EM64T) and Can't install Intel (R) Pro 100/VE Network Connection.

So, find and download the following packages from a FC4 mirror near you:

Code:

kernel-2.6.14-1.1653_FC4
kernel-smp-2.6.14-1.1653_FC4
hwdata-0.158.3-1

Install them and you should be able to use the network setup wizard (Desktop->System Settings->Network, same as system-config-network) to configure your network connection.

Hi Jowah,
No luck with the above. Same messages as before. The only options available are (when running system-config-network):
1. Intel EtherExpress Pro 100B
2. Intel EtherExpress/100 driver
3. Intel EtherExpress/1000 gigabit
The rest are from other adapter manufacturers.

What could be wrong?

Thank you.

jowah · #4 2nd January 2006, 09:15 PM

Just to be sure - did you reboot the machine after the kernel upgrade and chose the 2.6.14-1.1653 kernel before trying to setup the network? If not, do so and try again.

Reboot or no reboot, after the hwdata upgrade, /sbin/lspci should at least show you something else than "Unknown device 109a" for the network controller.

It remains to be seen if the 2.6.14-1.1653 Intel drivers are up to date enough to recognize the LAN adapter on your motherboard, so when I originally wrote "here's the solution" I should have said "here's a possible solution". Fingers crossed...

The driver you want is the third one in your list - the "Intel EtherExpress/1000 gigabit" one (the "e1000" driver).

EDIT: I've taken a gander at the e1000 driver source for the 2.6.14-1.1653 kernel package and it seems that it has no accommodation for the Intel 82573L network controller (PCI ID 0x109A) on your motherboard. The e1000 driver version in that kernel is "6.0.60-k2-NAPI". I'm grabbing the 1654 kernel which is still in testing to see if it has a later Intel e1000 driver... nope, same driver.

That takes us to the last resort:

Getting updated e1000 drivers from Intel
You'll need a terminal window where you're logged in as root to do this.

1) Go here and get the file "e1000-6.2.15.tar.gz". I'll assume you'll save that file to /tmp.

1b) For referernce, read the Intel documentation for the kernel here.

2) Make sure you have the package "kernel-devel". Do a "rpm -q kernel-devel" and see if it spits out "kernel-devel-2.6.14-1.1653_FC4". If not, a "yum -y install kernel-devel" will take care of that.

2b) Many driver sources expect to find kernel source headers under the /usr/src/linux tree. We'll need to point that folder to where kernel-devel puts its files:

Code:

ln -s /usr/src/kernels/kernel-$(uname -r) /usr/src/linux

3) Hopefully, you can now do the following:

3a: Compile and make a Intel e1000 driver package:

Code:

# cd /tmp
# rpmbuild -tb e1000-6.2.15.tar.gz

That will result in a lot of things being printed in the terminal window, just wait for it to finish, hopefully without an error.

3b: Install that

Code:

rpm -Uvh /usr/src/redhat/RPMS/i386/e1000-6.2.15-1.i386.rpm

EDIT: 3c below might actually be a better way of doing it

3c: Alternative: build the driver module directly and install it manually:

Code:

# cd /tmp
# tar xzf e1000-6.2.15.tar.gz
# cd e1000-6.2.15
# make install

4: try the new driver module

Code:

# modprobe -r e1000    (to unload an old 6.0.60 module, if it's loaded)
# modprobe e1000       (try the new, 6.2.15 one)
# dmesg|grep e1000     (Check the kernel log to see what happened)

zhamuth · #5 4th January 2006, 01:29 AM

Quote:

Originally Posted by jowah

Just to be sure - did you reboot the machine after the kernel upgrade and chose the 2.6.14-1.1653 kernel before trying to setup the network? If not, do so and try again.

Reboot or no reboot, after the hwdata upgrade, /sbin/lspci should at least show you something else than "Unknown device 109a" for the network controller.

It remains to be seen if the 2.6.14-1.1653 Intel drivers are up to date enough to recognize the LAN adapter on your motherboard, so when I originally wrote "here's the solution" I should have said "here's a possible solution". Fingers crossed...

The driver you want is the third one in your list - the "Intel EtherExpress/1000 gigabit" one (the "e1000" driver).

EDIT: I've taken a gander at the e1000 driver source for the 2.6.14-1.1653 kernel package and it seems that it has no accommodation for the Intel 82573L network controller (PCI ID 0x109A) on your motherboard. The e1000 driver version in that kernel is "6.0.60-k2-NAPI". I'm grabbing the 1654 kernel which is still in testing to see if it has a later Intel e1000 driver... nope, same driver.

That takes us to the last resort:

Getting updated e1000 drivers from Intel
You'll need a terminal window where you're logged in as root to do this.

1) Go here and get the file "e1000-6.2.15.tar.gz". I'll assume you'll save that file to /tmp.

2) Make sure you have the package "kernel-devel". Do a "rpm -q kernel-devel" and see if it spits out "kernel-devel-2.6.14-1.1653_FC4". If not, a "yum -y install kernel-devel" will take care of that.

3) Hopefully, you can now do the following:

3a: Compile and make a Intel e1000 driver package:

Code:

# cd /tmp
# rpmbuild -tb e1000-6.2.15.tar.gz

That will result in a lot of things being printed in the terminal window, just wait for it to finish, hopefully without an error.

3b: Install that

Code:

rpm -Uvh /usr/src/redhat/RPMS/i386/e1000-6.2.15-1.i386.rpm

4: try the new driver module

Code:

# modprobe -r e1000    (to unload the old 6.0.60 module, if it's loaded)
# modprobe e1000       (try the new, 6.2.15 one)
# dmesg|grep e1000     (Check the kernel log to see what happened)

Thanks Jowah. Yep, I did log in with the correct kernel. Let me try the alternate solution provided by you and see what happens. Will keep you posted.

Thank you,
Muthu

zhamuth · #6 4th January 2006, 02:30 AM

Jowah,
Here is the update.
1. I installed the 2.6.14-1.1653 kernel-devel package first, since I did not have it.

2. Copied the e1000-6.2.15.tar.gz to /tmp and built it with rpmbuild -tb e1000-6.2.15.tar.gz

3. But, it did not execute without an error.

Providing the screen-dump below:

[muthu@localhost ~]$ su
Password:
[root@localhost muthu]# rpm -q kernel-devel
kernel-devel-2.6.14-1.1653_FC4
[root@localhost muthu]# cd /tmp
[root@localhost tmp]# rpmbuild -tb e1000-6.2.15.tar.gz
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.33322
+ umask 022
+ cd /usr/src/redhat/BUILD
+ LANG=C
+ export LANG
+ unset DISPLAY
+ cd /usr/src/redhat/BUILD
+ rm -rf e1000-6.2.15
+ /usr/bin/gzip -dc /tmp/e1000-6.2.15.tar.gz
+ tar -xvvf -
drwxr-xr-x root/root 0 2005-09-20 13:48:43 e1000-6.2.15/
drwxr-xr-x root/root 0 2005-09-20 13:48:43 e1000-6.2.15/src/
-rw-r--r-- root/root 9780 2005-09-20 13:48:43 e1000-6.2.15/src/Makefile
-rw-r--r-- root/root 10557 2005-09-20 13:48:43 e1000-6.2.15/src/e1000.h
-rw-r--r-- root/root 57439 2005-09-20 13:48:43 e1000-6.2.15/src/e1000_ethtool.c
-rw-r--r-- root/root 237294 2005-09-20 13:48:43 e1000-6.2.15/src/e1000_hw.c
-rw-r--r-- root/root 122934 2005-09-20 13:48:43 e1000-6.2.15/src/e1000_hw.h
-rw-r--r-- root/root 136492 2005-09-20 13:48:43 e1000-6.2.15/src/e1000_main.c-rw-r--r-- root/root 4258 2005-09-20 13:48:43 e1000-6.2.15/src/e1000_osdep.h
-rw-r--r-- root/root 23489 2005-09-20 13:48:43 e1000-6.2.15/src/e1000_param.c
-rw-r--r-- root/root 4601 2005-09-20 13:48:43 e1000-6.2.15/src/kcompat.c
-rw-r--r-- root/root 21476 2005-09-20 13:48:43 e1000-6.2.15/src/kcompat.h
-rw-r--r-- root/root 21147 2005-09-20 13:48:43 e1000-6.2.15/src/kcompat_ethtool.c
-rw-r--r-- root/root 18671 2005-09-20 13:48:43 e1000-6.2.15/LICENSE
-rw-r--r-- root/root 23977 2005-09-20 13:48:43 e1000-6.2.15/README
-rw-r--r-- root/root 5846 2005-09-20 13:48:43 e1000-6.2.15/ldistrib.txt
-rw-r--r-- root/root 15699 2005-09-20 13:48:43 e1000-6.2.15/e1000.spec
-rw-r--r-- root/root 10108 2005-09-20 13:48:43 e1000-6.2.15/e1000.7
-rw-r--r-- root/root 417 2005-09-20 13:48:43 e1000-6.2.15/SUMS
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd e1000-6.2.15
++ /usr/bin/id -u
+ '[' 0 = 0 ']'
+ /bin/chown -Rhf root .
++ /usr/bin/id -u
+ '[' 0 = 0 ']'
+ /bin/chgrp -Rhf root .
+ /bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.33322
+ umask 022
+ cd /usr/src/redhat/BUILD
+ cd e1000-6.2.15
+ LANG=C
+ export LANG
+ unset DISPLAY
+ mkdir -p /var/tmp/e1000-6.2.15-root
++ uname -r
+ KV=2.6.14-1.1653_FC4
+ KA=x86_64
++ echo 2.6.14-1.1653_FC4
++ sed '{ s/hugemem//g; s/smp//g; s/enterprise//g; }'
+ KV_BASE=2.6.14-1.1653_FC4
+ '[' -e /usr/src/kernels ']'
++ echo 2.6.14-1.1653_FC4
++ grep '^2.6'
+ '[' 2.6.14-1.1653_FC4 ']'
+ '[' -e /etc/redhat-release ']'
++ ls /lib/modules
++ grep 2.6.14-1.1653_FC4
+ KSP='2.6.14-1.1653_FC4
2.6.14-1.1653_FC4smp'
+ for K in '$KSP'
+ '[' x86_64 == x86_64 ']'
++ echo 2.6.14-1.1653_FC4
++ grep hugemem
+ '[' ']'
+ make -C src clean
make: Entering directory `/usr/src/redhat/BUILD/e1000-6.2.15/src'
rm -rf e1000.ko e1000.o e1000.mod.c e1000.mod.o e1000_main.o e1000_hw.o e1000_param.o e1000_ethtool.o kcompat.o e1000.7.gz .*cmd .tmp_versions
make: Leaving directory `/usr/src/redhat/BUILD/e1000-6.2.15/src'
+ make -C src KSP=/lib/modules/2.6.14-1.1653_FC4/build INSTALL_MOD_PATH=/var/tmp/e1000-6.2.15-root MANDIR=/usr/share/man CFLAGS_EXTRA= install
make: Entering directory `/usr/src/redhat/BUILD/e1000-6.2.15/src'
make -C /lib/modules/2.6.14-1.1653_FC4/build SUBDIRS=/usr/src/redhat/BUILD/e1000-6.2.15/src modules
make[1]: Entering directory `/usr/src/kernels/2.6.14-1.1653_FC4-x86_64'
CC [M] /usr/src/redhat/BUILD/e1000-6.2.15/src/e1000_main.o
/usr/src/redhat/BUILD/e1000-6.2.15/src/e1000_main.c:307: warning: initialization from incompatible pointer type
CC [M] /usr/src/redhat/BUILD/e1000-6.2.15/src/e1000_hw.o
CC [M] /usr/src/redhat/BUILD/e1000-6.2.15/src/e1000_param.o
CC [M] /usr/src/redhat/BUILD/e1000-6.2.15/src/e1000_ethtool.o
CC [M] /usr/src/redhat/BUILD/e1000-6.2.15/src/kcompat.o
LD [M] /usr/src/redhat/BUILD/e1000-6.2.15/src/e1000.o
Building modules, stage 2.
MODPOST
CC /usr/src/redhat/BUILD/e1000-6.2.15/src/e1000.mod.o
LD [M] /usr/src/redhat/BUILD/e1000-6.2.15/src/e1000.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.14-1.1653_FC4-x86_64'
gzip -c ../e1000.7 > e1000.7.gz
# remove all old versions of the driver
find /var/tmp/e1000-6.2.15-root/lib/modules/2.6.14-1.1653_FC4 -name e1000.ko -exec rm -f {} \; || true
find: /var/tmp/e1000-6.2.15-root/lib/modules: No such file or directory
find /var/tmp/e1000-6.2.15-root/lib/modules/2.6.14-1.1653_FC4 -name e1000.ko.gz -exec rm -f {} \; || true
find: /var/tmp/e1000-6.2.15-root/lib/modules: No such file or directory
install -D -m 644 e1000.ko /var/tmp/e1000-6.2.15-root/lib/modules/2.6.14-1.1653_FC4/kernel/drivers/net/e1000/e1000.ko
/sbin/depmod -b /var/tmp/e1000-6.2.15-root -a -n > /dev/null || true
install -D -m 644 e1000.7.gz /var/tmp/e1000-6.2.15-root/usr/share/man/man7/e1000.7.gz
man -c -P'cat > /dev/null' e1000 || true
No manual entry for e1000
make: Leaving directory `/usr/src/redhat/BUILD/e1000-6.2.15/src'
+ for K in '$KSP'
+ '[' x86_64 == x86_64 ']'
++ echo 2.6.14-1.1653_FC4smp
++ grep hugemem
+ '[' ']'
+ make -C src clean
make: Entering directory `/usr/src/redhat/BUILD/e1000-6.2.15/src'
rm -rf e1000.ko e1000.o e1000.mod.c e1000.mod.o e1000_main.o e1000_hw.o e1000_param.o e1000_ethtool.o kcompat.o e1000.7.gz .*cmd .tmp_versions
make: Leaving directory `/usr/src/redhat/BUILD/e1000-6.2.15/src'
+ make -C src KSP=/lib/modules/2.6.14-1.1653_FC4smp/build INSTALL_MOD_PATH=/var/tmp/e1000-6.2.15-root MANDIR=/usr/share/man CFLAGS_EXTRA= install
make: Entering directory `/usr/src/redhat/BUILD/e1000-6.2.15/src'
Makefile:97: *** Linux kernel source not configured - missing version.h. Stop.
make: Leaving directory `/usr/src/redhat/BUILD/e1000-6.2.15/src'
error: Bad exit status from /var/tmp/rpm-tmp.33322 (%build)

RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.33322 (%build)
[root@localhost tmp]#

Any ideas?

Thank you,
Muthu

zhamuth · #7 4th January 2006, 02:33 AM

"...Reboot or no reboot, after the hwdata upgrade, /sbin/lspci should at least show you something else than "Unknown device 109a" for the network controller..." - from your previous post.

Yes, /sbin/lspci correctly recognizes the Ethernet Adapter to be Intel Corporation 82573L Gigabit Ethernet Controller (rev 01). But no luck in getting it to work.

Thank you.

jowah · #8 4th January 2006, 05:25 AM

Quote:

Originally Posted by zhamuth

Code:

...
Makefile:97: *** Linux kernel source not configured - missing version.h.  Stop.
make: Leaving directory `/usr/src/redhat/BUILD/e1000-6.2.15/src'
error: Bad exit status from /var/tmp/rpm-tmp.33322 (%build)

RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.33322 (%build)
[root@localhost tmp]#

Any ideas?

Thank you,
Muthu

Yep. The highlighted error in red tells me I missed out on one crucial step in the instructions above. Issue this command:

Code:

ln -s /usr/src/kernels/kernel-$(uname -r) /usr/src/linux

After that, try the rpmbuild command again. Fingers crossed...

zhamuth · #9 5th January 2006, 12:06 AM

Quote:

Originally Posted by jowah

Yep. The highlighted error in red tells me I missed out on one crucial step in the instructions above. Issue this command:

Code:

ln -s /usr/src/kernels/kernel-$(uname -r) /usr/src/linux

After that, try the rpmbuild command again. Fingers crossed...

Hi Jowah,
Same error Linux kernel source not configured - missing version.h even after linking. Googling the exact words above, takes us to the Intel page. Scroll down and you will find this in the Known Issues section. They are asking us to do a make include/linux/version.h. On executing it, I get a
make: ***No rule to make target 'inlcude/linux/version.h'. Stop.

How do we get this to work?

Thank you,
Muthu

zhamuth · #10 5th January 2006, 12:34 AM

Quote:

Originally Posted by zhamuth

Hi Jowah,
Same error Linux kernel source not configured - missing version.h even after linking. Googling the exact words above, takes us to the Intel page. Scroll down and you will find this in the Known Issues section. They are asking us to do a make include/linux/version.h. On executing it, I get a
make: ***No rule to make target 'inlcude/linux/version.h'. Stop.

How do we get this to work?

Thank you,
Muthu

Jowah,
I followed the instructions given on the Intel page above and now FC4 recognizes my Ethernet card. Cool.

I have a different problem now though. When I click on the RHN button for updating files, I get a message: Network Error -3: Temporary failure in name resolution

How do I get out of this now? I am able to go to other sites though.

Thank you,
Muthu

zhamuth · #11 5th January 2006, 02:42 AM

Did a yum -y update, re-started the system and I am all set to go now. Thanks a lot for all the help, hopefully this thread will be useful for others having the same problem.

jowah · #12 5th January 2006, 06:53 AM

I'm glad to hear that you got it to work, despite my instructions.

I took the "how to make a RPM" part from that Intel page you mentioned and tried to make a mini-howto of it. Now, since I have a "real" expanded kernel source tree (see the FC4 Release Notes for how to create that) in /usr/src/linux, I wasn't able to properly confirm that the steps I listed would actually work.

But you found the other way of building the drivers using a straight "make install" from the Intel sources, which is probably the better way to do it. I've edited my little howto above to point both to the Intel docs and suggest the manual build option (3c), which worked for you, I take it.

Again, I'm glad you got it sorted and just like you hope this thread might be of use for future readers.

deanhiller · #13 18th August 2006, 03:30 AM

I can't seem to find this version of the kernel anywhere? When I get on the mirrors, there is only 2.6.11 and when I search, I find a kernel of 2.6.18 but not an smp. help please.
dean