Bug 476977

Description of problem:
Booting from the standard pxeboot vmlinuz and initrd.img
anaconda starts up and starts NetworkManager to do get the kickstart script downloaded. Network is not set up properly. -> Error message.
Click "Retry" and everything is set up and installation goes as expected.

Seen with Syskonnect SK-9871 (skge) and RTL-8169 NICs

Version-Release number of selected component (if applicable):
anaconda version 11.4.1.64
Seen on both 32 and 64 bit

How reproducible:
Every time.

Steps to Reproduce:
1. Have a kickstart server with appropriate kickstart file
2. Have client with Syskonnect SK-9871 (driver: skge) or RTL-8169 NIC
3. boot with the pxeboot kernel and initrd.img, use ks= to point to kickstart file
4. Wait for anaconda to start and the Error message to turn up.
  
Actual results:
NetworkManages fails to set up the network card, presents you with an error message that network couldn't be set up and gives you the option "retry"
Pressing "Retry" sets up network properly and continues kickstart installation as expected.


Expected results:

Installation should run without any intervention needed
(subject to what the kickstart file is set up to do, of course)

Additional info:
This is seen on machines with the following NIC chipsets;
Syskonnect SK-9871 (driver: skge) and RTL-8169
The Syskonnect has been tested in widely different machines, the behaviour follows the NICs. (More than one NIC has been tested)
------------------------
The anaconda error looks something like this;
<box>
"Waiting for NetworkManager to configure eth0..."
</box>

<box>
Network Error
"There was an error configurring your network interface."
<button>
Retry
</button>
</box>

-----------------------
The messages from vt4
"
NetworkManager: <info>  (eth0):
NetworkManager: <info>  starting...
NetworkManager: <info>  Waiting for HAL to start...
NetworkManager: <WARN>  nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add():
Sucess
NetworkManager: <info>  Trying to start the supplicant...
NetworkManager: <info>  Trying to start the system settings daemon...
nm-system-settings: initial_add_devices_of_type: could not get device from HAL: The name org.freedesktop.Hal was not provided by any .service files (2)
nm-system-settings: initial_add_devices_of_type: could not get device from HAL: The name org.freedesktop.Hal was not provided by any .service files (2)
nm-system-settings: initial_add_devices_of_type: could not get device from HAL: The name org.freedesktop.Hal was not provided by any .service files (2)
nm-system-settings: Loaded plugin ifcfg-fedora: (c) 2007 - 2008 Red Had, Inc. To report bugs please use the NetworkManager mailing list.
nm-system-settings:     ifcfg-fedora: parsing /etc/sysconfig/network-scripts-ifcfg-eth0 ...
nm-system-settings:     ifcfg-fedora:     error: File '/etc/sysonfig/network-scripts/ifcfg-eth0' specified device 'eth0', but the device's type could not be determined.
NetworkManager: <info>  HAL re-appeared
NetworkManager: <info>  eth0: driver is 'skge'.
NetworkManager: <info>  Found new Ethernet device 'eth0'.
NetworkManager: <info>  (eth0): exported as /org/freedesktop/Hal/devices/net_00_00_5a_9d_3e_2c
NetworkManager: <info>  (eth0): device state change: 1 -> 2
NetworkManager: <info>  (eth0): bringing up device.
skge eth0: enabling interface
NetworkManager: <info>  (eth0): preparing device.
NetworkManager: <info>  (eth0): deactivating device (reason: 2).
skge eth0: Link is up at 100 Mbps, full duplex, flow control both
NetworkManager: <info>  (eth0): carrier now ON (device state 2)
NetworkManager: <info>  (eth0): device state change: 2 -> 3
"
<waiting>
------------------