Bug 1489317 - [RFC] Alternates-linux_entry-with-without-GRUB_CMDLINE_LINUX_CUSTOM
Summary: [RFC] Alternates-linux_entry-with-without-GRUB_CMDLINE_LINUX_CUSTOM
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-07 08:03 UTC by Nicolas Chauvet (kwizart)
Modified: 2020-05-26 14:40 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-26 14:40:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Current RFC suggested patch (2.48 KB, application/mbox)
2017-09-07 08:03 UTC, Nicolas Chauvet (kwizart)
no flags Details

Description Nicolas Chauvet (kwizart) 2017-09-07 08:03:11 UTC
Created attachment 1322963 [details]
Current RFC suggested patch

Description of problem:
This patch adds a GRUB_CMDLINE_LINUX_CUSTOM variable to existing
cmdline options, and creates a dedicated linux_entry without theses
custom cmdline options.  This allows users to switch between default
and custom cmdlines options without much editing.


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

How reproducible:
always


Actual results:
If a new cmdline option is needed for a specific case it will be done at the 

Expected results:
There is a need to switch between custom (optionals) and default cmdline options

For example, this helps when installing a optimized tuned profile for
some use cases, then be allowed to choose back to the default.

An example is for drivers that needs special boot options such as:
 "rd.driver.blacklist=nouveau modprobe.blacklist=nouveau"

Installing GRUB_CMDLINE_LINUX_CUSTOM_NVIDIA in /etc/default/grub will
create a boot menu to use the proprietary driver, then another one will
allows to boot to nouveau driver.
This requires a compatible driver integration


Additional info:
This RFC was reported usptream with:
https://savannah.gnu.org/bugs/index.php?51957

Comment 1 Fedora End Of Life 2018-02-20 15:28:05 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.

Comment 2 Leonardo Amaral 2018-10-15 16:11:51 UTC
Its possible to bump this issue to F29 or F30?

Comment 3 Nicolas Chauvet (kwizart) 2018-10-15 17:06:32 UTC
@leonardo
Thx for your interest in this feature.
Recently I've discovered 
https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/
(that should be implemented by f30) so maybe there will be a mean to properly specify what is needed in this case.

Comment 4 Ben Cotton 2019-02-19 17:11:46 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle.
Changing version to '30.

Comment 5 Ben Cotton 2020-04-30 22:17:29 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-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 '30'.

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 30 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 6 Ben Cotton 2020-05-26 14:40:39 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.


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