Bug 222949

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; pt-BR; rv:1.8.0.9) Gecko/20061219 Fedora/1.5.0.9-1.fc6 Firefox/1.5.0.9 pango-text

Description of problem:
Sometimes, after booting the computer, my wireless NIC is named __tmp????????? (the question marks are random digits). I was not able to identify a pattern in this behavior. In every boot, the wireless NIC may be named eth1 or __tmp?????????, with no apparent reason.
If it is not shown as eth1, I need to reboot and try again, until it's correctly shown as eth1. Right before filling this bug, I've rebooted the machine six times in a row until I got the NIC named eth1.
When the NIC is shown as __tmp?????????, KNetworkManager sees all available networks, but can't connect to any of them because dhcpcd is not able to get the IP configuration. If I rmmod ipw2200 and restart NetworkManager, the wireless NIC is correctly named eth1, but then KNetworkManager does not see the wireless networks. I can use the NIC only if it's shown as eth1 after booting.


Version-Release number of selected component (if applicable):
initscripts-8.45.7-1

How reproducible:
Sometimes


Steps to Reproduce:
1. Boot the computer
2. See if the wireless NIC was correctly named eth1. If not, go to step 1.
3. Connect to your wireless network.

Actual Results:
After each boot, the wireless NIC may or may not be named eth1. If it's shown as __tmp?????????, another reboot is needed, until it's shown as eth1.

Expected Results:
The wirless NIC should never be named __tmp?????????.
It should be named eth1 after every boot.

Additional info:
This computer is a centrino notebook with a intel ipw2200 wireless NIC.
The kernel I'm running is: kernel-2.6.18-1.2849.fc6
NetworkManager version is: NetworkManager-0.6.4-5.fc6
Normally, I have the network daemon ON with no NICs up on start up, NetworkManager ON and NetworkManagerDispatcher ON. I've tried to chkconfig network off, with no positive results.