Bug 950760 - double quotes in kernel parameter
Summary: double quotes in kernel parameter
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 32
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Javier Martinez Canillas
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-10 19:49 UTC by Andrea Oliveri
Modified: 2021-05-25 17:14 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-25 17:14:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Andrea Oliveri 2013-04-10 19:49:44 UTC
Description of problem:
If you try to pass the parameter acpi_osi="!Windows 2012" to kernel added it to /etc/default/grub the result in the kernel command line is wrong ( "acpi_osi=!Windows\x202012" ). I try to use the escape charaters ( \\ \" \' "' ) but the result is similar..
Please correct it becouse more users need acpi_osi="!Windows 2012" or acpi_osi="!Windows 2006"

Version-Release number of selected component (if applicable):
grub2-efi-2.00-15.fc18.x86_64

How reproducible:
Add acpi_osi="!Windows 2012" to /etc/default/grug, update grub.cfg, reboot and check /proc/cmdline

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Jason Sauders 2013-06-24 19:51:44 UTC
For what it's worth, I experienced this very thing yesterday when I installed Fedora 19 beta. It's a show stopper for Fedora on my systems at this point in time.

Comment 2 Adam Williamson 2013-06-28 00:45:27 UTC
Can't you just hack the correct form into grub2.cfg directly?

Note fedora does not run grub(2)-install on kernel updates. It instead uses grubby, which basically takes the top entry in the existing grub2.cfg, copies it, and modifies it for the new kernel. So if you make a direct edit to grub2.cfg in Fedora, installing a new kernel will keep that change, it won't be overwritten unless you yourself (or some non-Fedora tool) run grub(2)-install.

Comment 3 Jason Sauders 2013-07-07 23:51:37 UTC
Adam, I'm not exactly sure where in the file I would put these edits. Even if I did, that might serve as a hackery workaround, but it's still an issue that should be addressed. As it stands, it's literally the only show stopper keeping me from using Fedora full time.

For what it's worth, I did a fresh install today, running 3.9.9 with all of the updates. The issue persists.

Comment 4 Michael Anselmi 2013-10-05 23:20:54 UTC
I am encountering this problem as well.

For example, from /etc/default/grub:

GRUB_CMDLINE_LINUX="rd.md=0 rd.lvm=0 rd.dm=0 vconsole.keymap=us $([ -x /usr/sbin/rhcrashkernel-param ] && /usr/sbin/rhcrashkernel-param || :) rd.luks=0 vconsole.font=latarcyrheb-sun16 rhgb quiet rdblacklist=nouveau acpi_osi=\"!Windows 2012\""

After running grub2-mkconfig, this is in grub.cfg:

linuxefi /vmlinuz-3.11.2-201.fc19.x86_64 root=UUID=c5e62348-9830-4040-b52d-6bad4ff76ad6 ro rd.md=0 rd.lvm=0 rd.dm=0 vconsole.keymap=us  rd.luks=0 vconsole.font=latarcyrheb-sun16 rhgb quiet rdblacklist=nouveau acpi_osi="!Windows 2012"

So far, so good!

However, after booting, this is in /proc/cmdline:

BOOT_IMAGE=/vmlinuz-3.11.2-201.fc19.x86_64 root=UUID=c5e62348-9830-4040-b52d-6bad4ff76ad6 ro rd.md=0 rd.lvm=0 rd.dm=0 vconsole.keymap=us rd.luks=0 vconsole.font=latarcyrheb-sun16 rhgb quiet rdblacklist=nouveau "acpi_osi=!Windows\x202012"

And here we see the problem, same as the original bug reporter Andrea.

*********

Unfortunately, modifying /etc/default/grub to be like

GRUB_CMDLINE_LINUX=" ... acpi_osi=\"!Windows 2012\""

doesn't help.  After running grub2-mkconfig, grub.cfg looks like

linuxefi ... acpi_osi=\"!Windows 2012\"

and /proc/cmdline after reboot looks like

BOOT_IMAGE= ... acpi_osi=\"!Windows 2012\"

I suppose *that* is working as intended.

Comment 5 Fedora End Of Life 2013-12-21 12:45:31 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 Fedora End Of Life 2014-02-05 20:34:25 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.

Comment 7 Dmitry Tantsur 2020-11-20 13:55:35 UTC
I can confirm it on recent Fedoras and CentOS 8. We're working on provisioning automation, the generated grub.cfg is

set default=0
set timeout=5
set hidden_timeout_quiet=false
menuentry "boot_partition" {
linuxefi /vmlinuz nofb nomodeset systemd.journald.forward_to_console=yes console=ttyS0 ipa-insecure=1 sshkey="ssh-rsa <a long key>"
initrdefi /initrd
}

In the command line:

[    0.000000] Command line: BOOT_IMAGE=/vmlinuz nofb nomodeset systemd.journald.forward_to_console=yes console=ttyS0 ipa-insecure=1 "sshkey=ssh-rsa <a long key>"

Comment 8 Fedora Program Management 2021-04-29 16:49:53 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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 '32'.

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 32 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 9 Fedora Admin user for bugzilla script actions 2021-05-07 00:35:09 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 10 Ben Cotton 2021-05-25 17:14:10 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.