Created attachment 407241 [details]
dmesg, /var/log/messages, /var/log/boot.log
Description of problem:
After reboot, the cards appear as eth2 and eth3 instead of eth0 and eth1, and it is impossible to configure them. The only way to fix the problem is to unplug the computer, then on the next reboot, the interfaces show up as eth0 and eth1 again.
Version-Release number of selected component (if applicable):
happens on every reboot.
Steps to Reproduce:
1. unplug computer
2. plug back in
3. boot up
4. network interfaces show up as eth0 and eth1 and are working
5. shutdown -h
6. switch the computer on (press button)
7. network interfaces show up as eth2 and eth3 and are NOT working
network interfaces appear as eth2 and eth3, and cannot be configured
network interfaces to always appear as eth0 and eth1, and always being able to configure them.
this problem never occurred with Fedora 8, 10, nor 12.
Can we change the priority on this bug?
I makes Fedoara 13 not usable in a data centre, or remotely because it makes rebooting remotely fail 100% of the time (the network never comes back properly until power is pulled and put back in).
After more investigation, I have found that this is a duplicate of:
I will add myself there and report the fact that the problem is still in fedora 13, and close this report.
*** This bug has been marked as a duplicate of bug 573201 ***
bug 573201 is specific to Fedora 12, and has been fixed. It seems that the patch applied to 2.6.32 has not been applied to 2.6.33, as the bug is still present in Fedora 13. I've been advised to re-open this bug to make sure that it gets looked at.
This is now fixed.
I have "yum update", got package kernel-PAE-22.214.171.124-47.fc13.i686, and the problem isn't there any more.