Bug 1476063

Summary:	No wireless after successful install
Product:	[Fedora] Fedora	Reporter:	Thom Carlin <tcarlin>
Component:	comps	Assignee:	Stephen Gallagher <sgallagh>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	26	CC:	anaconda-maint-list, g.kaviyarasu, jkonecny, jonathan, kevin, leandroembu, mkolman, vanmeeuwen+fedora, vpavlin, vponcova
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-28 11:43:28 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 Thom Carlin 2017-07-28 00:57:44 UTC

Description of problem:

After minimal install of Fedora 26 no wireless connection on reboot

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

26

How reproducible:

100%

Steps to Reproduce:
1. Install Fedora 26 with minimal (Custom Fedora Server Installation)
2. Specify wireless connection information on installation screen
3. Successfully install F26
4. Reboot
5. Log into system
6. ip a

Actual results:

l0, eth0 (but no wireless)

Expected results:

Configured and working wireless connection

Additional info:

Comment 1 Jiri Konecny 2017-07-28 08:44:55 UTC

Hi Thom,

Your wireless drivers are not included in the minimal environment, which I think is correct for minimal installation. 

If you want to have your wireless drivers installed then we need to add iwl* packages to minimal environment or better to add an optional group in it. However, this must be done in comps not in Anaconda.

Comment 2 Stephen Gallagher 2017-07-28 11:43:28 UTC

This isn't a bug. A minimal install is not expected to have wireless support. If you want wireless support, either select the optional wireless drivers checkbox in anaconda or choose a more-complete install target (such as Workstation or Server).

Comment 3 Stephen Gallagher 2020-04-06 12:16:03 UTC

*** Bug 1821047 has been marked as a duplicate of this bug. ***