Bug 1082318 - [REGRESSION] can't find command 'devicetree' (for installing new kernels)
Summary: [REGRESSION] can't find command 'devicetree' (for installing new kernels)
Alias: None
Product: Fedora
Classification: Fedora
Component: grubby
Version: 22
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2014-03-30 10:50 UTC by Igor Gnatenko
Modified: 2016-03-27 15:13 UTC (History)
7 users (show)

Fixed In Version: grubby-8.33-1.fc21
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-03-27 15:13:27 UTC
Type: Bug

Attachments (Terms of Use)

Description Igor Gnatenko 2014-03-30 10:50:17 UTC
Description of problem:
I can't boot in new installed kernels after updating grubby.

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

How reproducible:

Steps to Reproduce:
1. yum --enablerepo=koji update grubby
2. yum --enablerepo=koji update kernel\*
3. reboot

Actual results:
error: file '/vmlinuz-3.14.0-0.rc8.git1.1.fc21.x86_64' not found.
error: can't find command 'devicetree'.
error: you need to load the kernel first.

Expected results:
Boot ok

Comment 1 Kevin Fenzi 2014-03-31 17:13:09 UTC
I see this here too: 

The new entry it added is: 

menuentry 'Fedora (3.14.0-1.fc21.x86_64) 21 (Rawhide)' --class gnu-linux --class gnu --class os {
        linuxefi /vmlinuz-3.14.0-1.fc21.x86_64 root=/dev/mapper/fedora-root LANG=en_US.UTF-8
        devicetree --copy-default
        initrdefi /initramfs-3.14.0-1.fc21.x86_64.img

Comment 2 darrell pfeifer 2014-03-31 20:45:35 UTC
The updated grubby 8.32-1 results in 

/sbin/new-kernel-pkg: line 156: [: argument expected

Comment 3 Filipe Rosset 2014-04-01 05:15:09 UTC
same issue here:


Comment 4 darrell pfeifer 2014-04-01 15:05:11 UTC
The 8.33 version no longer has the "argument expected" problem. It still produces a devicetree paragraph and that still fails with the original error on boot.

Comment 5 Adam Williamson 2014-04-01 15:42:50 UTC
as long as you have a busted entry as the top entry in grubby, this will be broken. you need to remove all the busted entries in the file or/and re-generate the file with grub2-mkconfig .

grubby works by copying the existing top entry and then tweaking it, so if that entry's broken, grubby will never produce a working one.

Comment 6 darrell pfeifer 2014-04-01 15:52:57 UTC
Thanks. Forgot about that.

Works as expected now.

Comment 7 Jaroslav Reznik 2015-03-03 17:12:13 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:

Comment 8 Igor Gnatenko 2016-03-27 15:13:27 UTC
It's already arrived in updates.

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