Bug 1576991 - Fresh install of Fedora 28 installs current kernel (4.16.6) without matching kernel modules
Summary: Fresh install of Fedora 28 installs current kernel (4.16.6) without matching ...
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 28
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-05-10 22:51 UTC by reescf
Modified: 2019-05-28 20:10 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-05-28 20:10:55 UTC
Type: Bug

Attachments (Terms of Use)

Description reescf 2018-05-10 22:51:52 UTC
Description of problem:

A fresh installation of Fedora 28 (KDE spin) included the current kernel (4.16.6) without matching kernel modules. 

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


How reproducible:

Unknown. I'm not about to start over - I've already installed twice as the machine wouldn't boot Fedora in UEFI mode.

Steps to Reproduce:
1. Download iso for Fedora 28 (KDE spin)
2. Create USB installation key using dd
3. Boot machine using key, choosing the non-UEFI version from the boot menu.
4. Install Fedora to hard disk.
5. Reboot machine to new installation.

Actual results:

Installed kernels: 4.16.3, 4.16.6

Installed kernel-modules: 4.16.3

Default kernel configured in grub: 4.16.6

On this machine, this broke network access when the default kernel was booted because the machine depends on WIFI which needs, obviously, the relevant modules.

Expected results:

Every installed kernel package should depend on the corresponding kernel-modules package, so that whichever kernel gets booted, usable kernel modules are present.

Additional info:

Thank goodness for 4.16.3. It took me a while to figure out what was wrong (I assumed I needed some non-standard firmware trick or something as this was a fresh install), but at least there's an easy fix now I've got there. I couldn't figure out what differed in the live install, where everything worked fine. Doh! Of course, the live install has a kernel *and* modules.

Comment 1 Ben Cotton 2019-05-02 21:48:35 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 Ben Cotton 2019-05-28 20:10:55 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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

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

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