Bug 2523734 - BIOS installs fail with kernel-7.3.0-0.rc0.260821g818bebeb63dd.8.fc46 and later
Summary: BIOS installs fail with kernel-7.3.0-0.rc0.260821g818bebeb63dd.8.fc46 and later
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Nicolas Frayer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: openqa
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-25 19:16 UTC by Adam Williamson (Red Hat non-Fedora)
Modified: 2026-09-01 19:49 UTC (History)
25 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson (Red Hat non-Fedora) 2026-08-25 19:16:18 UTC
With kernel-7.3.0-0.rc0.260821g818bebeb63dd.8.fc46 and later builds, BIOS installs fail with an error:

Aug 21 23:42:29 localhost.localdomain org.fedoraproject.Anaconda.Modules.Storage[2485]: INFO:program:Running in chroot '/mnt/sysroot'... grub2-install --no-floppy /dev/vda
Aug 21 23:42:29 localhost.localdomain org.fedoraproject.Anaconda.Modules.Storage[2485]: INFO:program:grub2-install: error: /usr/lib/grub/i386-ieee1275/modinfo.sh doesn't exist. Please specify --target or --directory.
Aug 21 23:42:29 localhost.localdomain org.fedoraproject.Anaconda.Modules.Storage[2485]: DEBUG:program:Return code of grub2-install: 1

UEFI installs are fine.

The affected builds are gated from Rawhide, but have reached ELN, so ELN BIOS installs are failing in Real Life.

CCing ELN folks and folks from the BIOS SIG which Justin kindly reminded me exists.

Comment 1 Stephen Gallagher 2026-08-25 19:25:10 UTC
I've just tagged kernel-7.3.0-0.rc0.260818g0f23d56f17fd.3.eln159 into ELN (I think that's the last known-good kernel), so things should recover shortly.

Comment 2 Adam Williamson (Red Hat non-Fedora) 2026-08-25 19:46:20 UTC
Yeah, I believe that one was OK.

Comment 3 Adam Williamson (Red Hat non-Fedora) 2026-08-26 00:06:59 UTC
There's a new build kernel-7.3.0-0.rc0.260825g66498c75b4f8.12.fc46 which still has this bug, so you'll need to untag the corresponding ELN build, Stephen.

Comment 4 Stephen Gallagher 2026-08-26 12:45:56 UTC
No ELN build has been kicked off for that kernel. I assume Justin is going to hold off building for ELN until that issue is addressed. (Kernel is on the list of packages that aren't automatically built for ELN and have to be submitted: https://github.com/fedora-eln/elnbuildsync-config/blob/production/elnbuildsync_dynamic.yaml#L53).

Comment 5 Yaakov Selkowitz 2026-08-27 04:32:18 UTC
We were *supposed* to have gating on kernel updates by now...

Comment 6 Adam Williamson (Red Hat non-Fedora) 2026-08-27 06:28:11 UTC
I still haven't thought of a good way to deal with the "results reported against update vs. results reported against build" problem :( It is not easily tractable.

Comment 7 Justin M. Forbes 2026-08-31 22:14:38 UTC
From grub-core/osdep/linux/platform.c:
  grub_util_info ("Looking for /proc/device-tree ..");
  if (is_not_empty_directory ("/proc/device-tree"))
    {
      grub_util_info ("...found");
      return "i386-ieee1275";
    }

  grub_util_info ("... not found");
  return "i386-pc";


Fedora ships i386-pc but not i386-ieee1275. With kernel 7.3 we now have the structure there, even if the files are empty:
ls /proc/device-tree/
'#address-cells'   name  '#size-cells'

I would recommend that if Fedora is not going to ship i386-ieee1275 grub2 should just patch out that section and have it all return i386-pc?  In the meantime, no kernel updates will ship until grub changes this. Gating prevents it.

Comment 8 Justin M. Forbes 2026-08-31 22:46:21 UTC
So it appears I can turn this off in kernel for the time being. Though it still seems a problematic method for checking.

Comment 9 Leo Sandoval 2026-09-01 19:49:14 UTC
I followed Justin's suggestion here https://src.fedoraproject.org/rpms/grub2/pull-request/255# but at the end I did not remove the whole 'if /proc/device-tree' because I consider useful for debugging purposes. Thanks Justin for pointing out the fix.


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