Bug 1582159
Summary: | start order of last kernel in rawhide | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | alain BELLEC <alain_bellec> |
Component: | grub2 | Assignee: | Peter Jones <pjones> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 29 | CC: | extras-orphan, jonathan, lkundrak, pjones |
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: | 2019-11-27 19:06:14 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
alain BELLEC
2018-05-24 12:08:46 UTC
forgot to tell you : all of these in the case of a multiboot . debian stretch stable + debian buster testing + windows 10 1803 + fedora 29 (rawhide) all works perfectly , included w$ and fedora , but grub has gone wrong with this O.S. what's the matter ? solution found . it seems that the /boot/grub2/grub.cfg had "linux16" and "initrd16" entries instead of "linux" and "initrd" ones . so , the debian multiboot did not work properly . my research gave me these links : https://bugzilla.redhat.com/show_bug.cgi?id=1173993 https://forums.fedoraforum.org/showthread.php?301929-Grub2-linux16-and-initrd16-instead-linux-and-initrd the second one is very usefull and it seems it solves my problem . now , my multiboot works well . nb: don't forget , at the end , to regenerate update-grub in debian . otherwise , boot won't work fine to reach last fedora's kernel . I wonder : do kernel and system updates change the work done? do I have to do it again? when? how? why? I wonder : do kernel and system updates change the work done? do I have to do it again? when? how? why? This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'. This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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. Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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. |