Bug 1703821 - GRUB_CMDLINE_LINUX are not taken
Summary: GRUB_CMDLINE_LINUX are not taken
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 30
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2019-04-28 15:19 UTC by yucef sourani
Modified: 2020-05-26 14:54 UTC (History)
3 users (show)

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

Attachments (Terms of Use)

Description yucef sourani 2019-04-28 15:19:42 UTC
Why when I have more than one distro, including Fedora, and if the second distro bootloader is the default, Fedora rescue mode will appear first in the boot menu and the normal mode will appear in Advanceda and last kernel in last order,This problem is annoying and is found in most Fedora versions,Not everyone knows this and thinks there is a problem because the Internet does not work.

Another problem, for example, now I have Fedora ًWorkstation 30 and Fedora Mate 30 and fedora Mate it's the default bootloader  when I'm changing GRUB_CMDLINE_LINUX in Fedora Workstation Changes are not taken ,examle rd.driver.blacklist=nouveau ,the changes in /etc/default/grub and /boot/grub2/grubenv ,if BLSCFG is false or true in fedora workstation same problem.

Another problem is that grub2-mkconfig sometimes failed to add all the systems and distro even if it showed that it had found a new system, but it was shown that there was a busy partition and the solution was to restart the system again,and Sometimes failed to add all the systems and distro and does not show any error log example partition busy or something .

partition table msdos/legacy bios .

Fedora Mate 30 64bit (default bootloader).
boot in /dev/sda3
root in lvm /dev/mapper/fedora_fedora25beta-root
home in lvm /dev/mapper/fedora_fedora25beta-home

Fedora Workstation 30 64bit.
root in /dev/sda6
home in lvm /dev/mapper/fedora_fedora25beta-home

Comment 1 yucef sourani 2019-04-28 15:59:22 UTC

Comment 2 Ben Cotton 2020-04-30 22:11:13 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 3 Ben Cotton 2020-05-26 14:54:57 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

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.