[CentOS] Problem with 2.6.11.4 kernel and e1000 driver -Correction
Mark Hull-Richter
mhull-richter at datallegro.com
Wed Feb 7 23:42:25 UTC 2007
None of that worked. When I edited out the HWADDR lines, I got this
instead:
Feb 7 06:36:34 sparenode1 network: Setting network parameters:
succeeded
Feb 7 06:36:34 sparenode1 network: Bringing up loopback interface:
succeeded
Feb 7 06:36:34 sparenode1 ifup: e1000 device eth0 does not seem to be
present, delaying initialization.
Feb 7 06:36:34 sparenode1 network: Bringing up interface eth0: failed
Feb 7 06:36:34 sparenode1 ifup: e1000 device eth1 does not seem to be
present, delaying initialization.
Feb 7 06:36:34 sparenode1 network: Bringing up interface eth1: failed
Hwconf did not change significantly when I ran kudzu, so I have no idea
what's going on here.
Again, this works exactly as is on 32-bit builds. It only fails on the
64 bit build.
-----Original Message-----
From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On
Behalf Of Radu Radutiu
Sent: Wednesday, February 07, 2007 5:47 AM
To: CentOS mailing list
Subject: Re: [CentOS] Problem with 2.6.11.4 kernel and e1000 driver
-Correction
Editing out HWADDR should fix your problem. Another possible solution
is to check that the value in the HWADDR line in
/etc/sysconfig/network-scripts/ifcfg-ethX is the same as listed in
the /etc/sysconfig/hwconf for the corresponding network interface.
Also make sure that the files
/etc/sysconfig/networking/devices/ifcfg-ethX and
/etc/sysconfig/network-scripts/ifcfg-eth0 are hard links to the same
file.
You can regenerate the content of the /etc/sysconfig/hwconf by
removing it and running kudzu again.
More information about the CentOS
mailing list