GNU GRUB - Bugs: bug #62886, Wrong $cmdpath when booting from...
You are not allowed to post comments on this tracker with your current authentication level.
bug #62886: Wrong $cmdpath when booting from an optical disc
Submitter: | nl6720 | ||
Submitted: | Thu 11 Aug 2022 09:55:39 AM UTC | ||
Category: | Booting | Severity: | Major |
Priority: | 5 - Normal | Item Group: | None |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | |
Open/Closed: | Open | Release: | other |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
Thu 11 Aug 2022 12:26:23 PM UTC, comment #3: |
nl6720 |
Thu 11 Aug 2022 12:10:47 PM UTC, comment #2: The issue is that configfile ${cmdpath}/grub.cfg doesn't work since $cmdpath is (cd0)/EFI/Boot.
|
nl6720 |
Thu 11 Aug 2022 11:46:39 AM UTC, comment #1: What is the actual problem? FAT is case-insensitive so /EFI/Boot and /EFI/BOOT is the same thing on it. If some pay doesn't test it this way it's the problem of the days part |
Vladimir Serbinenko <phcoder>![]() |
Thu 11 Aug 2022 09:55:39 AM UTC, original submission:
When booting GRUB standalone (created following https://wiki.archlinux.org/title/GRUB/Tips_and_tricks#GRUB_standalone ) from an optical disc (an emulated one using IODD 2531), where it was placed at /EFI/BOOT/BOOTx64.EFI in both the ISO9660 and in an attached FAT image used as an EFI system partition, GRUB's $cmdpath was wrong. echo $cmdpath returned (cd0)/EFI/Boot. Notice that it's Boot not BOOT, but ls (cd0)/EFI/ showed that the directory is indeed called BOOT.
|
nl6720 |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
comment #1:
While the El Torito image from which GRUB is launched is FAT, (cd0) which GRUB uses in its $cmdpath is ISO 9660 + Rock Ridge + Joliet.