Bug 1476063 - No wireless after successful install
No wireless after successful install
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: comps (Show other bugs)
26
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Stephen Gallagher
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-27 20:57 EDT by Thom Carlin
Modified: 2017-07-28 07:43 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-07-28 07:43:28 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Thom Carlin 2017-07-27 20:57:44 EDT
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 04:44:55 EDT
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 07:43:28 EDT
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).

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