Bug 466546

Summary:	Network Install of F10 Beta on IBM T60P laptop fails to use eth0
Product:	[Fedora] Fedora	Reporter:	Joshua Jensen <joshua>
Component:	anaconda	Assignee:	David Cantrell <dcantrell>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	anaconda-maint-list, dcantrell
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-10-15 03:46:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Joshua Jensen 2008-10-10 20:21:31 UTC

Description of problem:

Network Install of F10 Beta on IBM T60P laptop fails to use eth0... it insists on using wlan0 instead.  wlan0 is on a network that I can't use.

using ksdevice=link or ksdevice=eth0 doesn't change anything


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

F10 Beta, x86_64




So how do we tell anaconda, with its fancy new NetworkManager, to use eth0, not wlan0 ??

Comment 1 David Cantrell 2008-10-11 03:52:43 UTC

Does this happen with rawhide (a nightly build) or a later Fedora 10 beta/test/snapshot/whatever release?

Comment 2 Joshua Jensen 2008-10-13 15:18:30 UTC

Ok... with rawhide one does get a choice via a menu that asks for eth0 or wlan0.  However, when eth0 is chosen, eth0 doesn't every actually initialize.  Strange.

But when, again with rawhide, I specific "ksdevice=eth0", then it works.... sort of.  By that I mean that eth0 really does get online, and allows me to actually download via http the second stage... however the installer crashes on the 2nd screen.  The debug of that screen says there is a problem with "ip4_config_props.Get(isys.NM_MANGER_IFACE, "Hostname") and "DBusException:  org.freedesktop.DBus.Error.InvalidArgs:  No such property Hostname"

Comment 3 David Cantrell 2008-10-15 03:46:19 UTC


*** This bug has been marked as a duplicate of bug 466775 ***