CentOS - Feb 2007 - Problem with 2.6.11.4 kernel and e1000 driver - Correction

Actually, here is what shows up in the log, regardless of whether the
driver is built-in or loaded as a module:

Feb 5 10:16:15 sparenode1 sysctl: net.ipv4.conf.default.rp_filter = 1
Feb 5 10:16:15 sparenode1 sysctl:
net.ipv4.conf.default.accept_source_route = 0
Feb 5 10:16:15 sparenode1 sysctl: kernel.sysrq = 0
Feb 5 10:16:15 sparenode1 sysctl: kernel.core_uses_pid = 1
Feb 5 10:16:15 sparenode1 network: Setting network parameters: succeeded
Feb 5 10:16:15 sparenode1 network: Bringing up loopback interface:
succeeded
Feb 5 10:16:15 sparenode1 ifup: Device eth0 has different MAC address
than expected, ignoring.
Feb 5 10:16:15 sparenode1 network: Bringing up interface eth0: failed
Feb 5 10:16:15 sparenode1 ifup: Device eth1 has different MAC address
than expected, ignoring.
Feb 5 10:16:15 sparenode1 network: Bringing up interface eth1: failed

It has been suggested that I edit out the HWADDR= contents from the
/etc/sysconfig/network-scripts file and restart the network.

Any other/further input?

Thanks.

-----Original Message-----
From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On
Behalf Of Mark Hull-Richter
Sent: Monday, February 05, 2007 6:35 PM
To: CentOS mailing list
Subject: [CentOS] Problem with 2.6.11.4 kernel and e1000 driver

I get the following results when I try to load the 2.6.11.4 kernel with
an Intel e1000 driver (the one that comes in the kernel source):

1) If I build it into the kernel, nothing shows up at all.

2) If I build it as a loadable module, I get errors on eth0 and eth1
that the MAC address is different than expected, and it ignores the
controller.

What's up with this?

Thanks.

mhr

_______________________________________________
CentOS mailing list
CentOS at centos.org
http://lists.centos.org/mailman/listinfo/centos

On 2/6/07, Mark Hull-Richter <mhull-richter at datallegro.com>
wrote:
> Any other/further input?
Yes, though not directly related to your issue.

1. Why build a custom kernel instead of sticking with the distro provided one?
2. If you feel that you absolutely have to build a custom kernel, why
build such an old one?

-- 
During times of universal deceit, telling the truth becomes a revolutionary act.
George Orwell

On 2/7/07, Mark Hull-Richter <mhull-richter at datallegro.com>
wrote:
> Actually, here is what shows up in the log, regardless of whether the
> driver is built-in or loaded as a module:
>
> Feb 5 10:16:15 sparenode1 sysctl: net.ipv4.conf.default.rp_filter = 1
> Feb 5 10:16:15 sparenode1 sysctl:
> net.ipv4.conf.default.accept_source_route = 0
> Feb 5 10:16:15 sparenode1 sysctl: kernel.sysrq = 0
> Feb 5 10:16:15 sparenode1 sysctl: kernel.core_uses_pid = 1
> Feb 5 10:16:15 sparenode1 network: Setting network parameters: succeeded
> Feb 5 10:16:15 sparenode1 network: Bringing up loopback interface:
> succeeded
> Feb 5 10:16:15 sparenode1 ifup: Device eth0 has different MAC address
> than expected, ignoring.
> Feb 5 10:16:15 sparenode1 network: Bringing up interface eth0: failed
> Feb 5 10:16:15 sparenode1 ifup: Device eth1 has different MAC address
> than expected, ignoring.
> Feb 5 10:16:15 sparenode1 network: Bringing up interface eth1: failed
>
> It has been suggested that I edit out the HWADDR= contents from the
> /etc/sysconfig/network-scripts file and restart the network.
>
> Any other/further input?
>
> Thanks.
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.