Red Hat Bugzilla – Bug 233507
two ifcfg-eth's created for one NIC.
Last modified: 2015-01-04 17:29:40 EST
From todays rawhide install on an X60. [davej@cheezit ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0 # Intel Corporation 82573L Gigabit Ethernet Controller DEVICE=eth0 BOOTPROTO=dhcp ONBOOT=yes [davej@cheezit ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth1 # Intel Corporation 82573L Gigabit Ethernet Controller DEVICE=eth1 ONBOOT=yes BOOTPROTO=dhcp HWADDR=00:16:d3:3a:62:d3
Do you have an iwlwifi adapter in this X60? I'm seeing this happen on a laptop-in-a-box system with iwlwifi. We don't have support for that interface during installation, but we hit a problem when it comes to gathering interface descriptions. We populate the table of interfaces to configure based on what interfaces are currently available. Then we gather descriptions for those interfaces using kudzu. Kudzu can see the iwlwifi driver and then screws up the descriptions because kudzu's list of interfaces does not match the list of currently available interfaces. Working on it.
Ahh, I see what's happening. I need the kudzu.PROBE_LOADED flag for kudzu.probe() in network.py. Unfortunately, PROBE_LOADED isn't defined in the Python kudzu module, so here's a patch: Index: kudzumodule.c =================================================================== RCS file: /usr/local/CVS/kudzu/kudzumodule.c,v retrieving revision 1.53 diff -u -p -r1.53 kudzumodule.c --- kudzumodule.c 9 Aug 2006 17:47:46 -0000 1.53 +++ kudzumodule.c 26 Mar 2007 18:11:43 -0000 @@ -97,6 +97,7 @@ static TableEntry modeTable[] = { { "PROBE_ALL", PROBE_ALL }, { "PROBE_SAFE", PROBE_SAFE }, { "PROBE_ONE", PROBE_ONE }, + { "PROBE_LOADED", PROBE_LOADED }, { NULL }, } ; static int numModeEntries = sizeof (modeTable) / sizeof (TableEntry); Bill, can you get a new kudzu built with this enabled? I need it to fix the problem in anaconda.
kudzu building; will be 1.2.66-1
Fixed in rawhide.
I just did a reinstall with the 20070409 tree, and this still occurs.
Yeah, many other people are reporting it, but it's not anaconda. It's either initscripts or something like udev or hal. Before you click Reboot at the end of an install, switch over to tty2 and look in /mnt/sysimage/etc/sysconfig/network-scripts and notice the ifcfg-* scripts are correct based on the settings you gave during installation. On reboot, the /etc/init.d/network script is crapping all over these and writing new files. I have no idea why. It might not be initscripts, but something that initscripts runs. Reassigning to initscripts.
*** This bug has been marked as a duplicate of 234764 ***