Bug 1232491 - Unable to pass any extra arguments
Summary: Unable to pass any extra arguments
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: efibootmgr
Version: 22
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-16 21:24 UTC by Przemysław Palacz
Modified: 2016-07-19 19:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 19:11:56 UTC
Type: Bug


Attachments (Terms of Use)

Description Przemysław Palacz 2015-06-16 21:24:24 UTC
Description of problem:
After latest efibootmgr update to 0.12-1.fc22 passing any additional arguments via either -u or -@ no longer works for me - can't create any new boot entries.
I can however remove the old ones and create a new one without any additional args.

For example:
efibootmgr -c -d /dev/sda -p 1 -L 'Fedora debug' -l '\efi\fedora\vmlinuz.efi' -u 'initrd=\efi\fedora\initramfs.img ro root=UUID=21df0671-2956-439b-ac47-b9dd888f7c8e ivrs_ioapic[7]=00:14.0 ivrs_ioapic[8]=00:00.1 resume=UUID=21df0671-2956-439b-ac47-b9dd837f7c8e resume_offset=3309568 zswap.enabled=1 quiet LANG=en_US.UTF-8 debug log_buf_len=8M no_console_suspend=1'

shows those errors:
efibootmgr: Could not set variable: Invalid argument
efibootmgr: Could not prepare boot variable: Invalid argument

Hardware info:
Motherboard: Asus sabertooth 990fx
Latest BIOS version: 1604

Last working version: 0.11.0-1.fc22

How reproducible: Always

Comment 1 Fedora End Of Life 2016-07-19 19:11:56 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.