Bug 749703 - eth0 does no initialize on install
Summary: eth0 does no initialize on install
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 16
Hardware: i686
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-28 01:05 UTC by Andrew Gillis
Modified: 2011-10-28 15:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-28 15:27:12 UTC
Type: ---


Attachments (Terms of Use)

Description Andrew Gillis 2011-10-28 01:05:36 UTC
Description of problem: I am installing Fedora 16 using a kickstart file. The installer tells me eth0 is not available.

After I get this error I drop to command line and see there is a /etc/sysconfig/network-scripts/ifcfg-p32p1 file with the mac address of my ethernet network card.

I can restart NetworkManager and the p32p1 interface comes up. I can ping a machine on the network etc. So its not a problem with the kernel being able to detect the card. lspci shows the network card as a RTL8111/8168B. I have had no problems installing Fedora 14 or 15 with the same kickstart file on this machine.

I tried this exact same kickstart on a vmware session and it works fine. I also notices that it configures wlan0 fine on this machine. 

Seems like the problem is with this network card.


How reproducible:

Install Fedora 16 on a machine with a RTL8111/8168B network card and specify eth0 in the kickstart file.

Comment 1 Chris Lumens 2011-10-28 15:27:12 UTC
Yeah, this is a result of the biosdevname feature (http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming), which is outside our control.  These are just the kinds of names network devices have now.


Note You need to log in before you can comment on or make changes to this bug.