Bug 1470672

Summary:	Kickstart install fail on e1000e ethernet intel DQ75TM 82578DM
Product:	[Fedora] Fedora	Reporter:	Nigel Arnot <nigel.arnot>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	25	CC:	gansalmon, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, nigel.arnot
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-12 10:23:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nigel Arnot 2017-07-13 12:41:17 UTC

Description of problem:

If a kickstart install (ks=http://ipaddr/file) is attempted onto an Intel DQ57TM motherboard it fails with "No carrier detected on interface eno1". A manual install using the same distribution media, hardware and network cable succeeds and the eno1 ethernet device works AOK after install.

Version-Release number of selected component (if applicable):
Fedora 25
(as shipped on netinst.iso). Also Fedora 24 is the same.

How reproducible:
Easily, given an Intel DQ57TM motherboard

Steps to Reproduce:
1.Boot off netinst.iso media
2.At fedora prompt hit TAB to edit kernel invocation
3.Add ks=http://192.168.0.x/ks/file (or whatever is locally appropriate)

Actual results:
"No carrier detected on interface eno1"
long wait
timeout and failure messages

Expected results:
System installed by kickstart

Additional info:
A manual install booted off the same media using "nearest mirror" as the installation source succeeds
The exact same kickstart install invocation succeeds if the network cable is attached to the system via an Edimax EU-4208 USB Ethernet adapter.
Post-installation either of these ways, the system boots and uses the on-board Ethernet without any further issues
At this point lsmod reports e1000e and lspci reports intel 82578DM Gigabit Ethernet hardware.
I would guess the fault to be with whatever version or equivalent of e1000e is shipped on Fedora 25 (and 24) netinst.iso

I don't know how to identify the component at fault. It would be helpful if a pseudo-component "kickstart" could be created for kickstart installation failure reports. e1000 module is provided by kernel-core rpm on the installed system.

Comment 1 Fedora End Of Life 2017-11-16 19:32:06 UTC

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2017-12-12 10:23:12 UTC

Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.