Description of problem: f39 install Version-Release number of selected component: anaconda-core-39.32.2-1.fc39.x86_64 The following was filed automatically by anaconda: anaconda 39.32.2 exception report Traceback (most recent call first): File "/usr/lib/python3.12/site-packages/dasbus/client/handler.py", line 509, in _handle_method_error raise exception from None File "/usr/lib/python3.12/site-packages/dasbus/client/handler.py", line 483, in _get_method_reply return self._handle_method_error(error) File "/usr/lib/python3.12/site-packages/dasbus/client/handler.py", line 450, in _call_method return self._get_method_reply( File "/usr/lib64/python3.12/site-packages/pyanaconda/modules/common/task/__init__.py", line 46, in sync_run_task task_proxy.Finish() File "/usr/lib64/python3.12/site-packages/pyanaconda/installation.py", line 439, in run_install_bootloader sync_run_task(STORAGE.get_proxy(task)) File "/usr/lib64/python3.12/site-packages/pyanaconda/installation_tasks.py", line 246, in _run self._task_cb(*self._task_args, **self._task_kwargs) File "/usr/lib64/python3.12/site-packages/pyanaconda/installation_tasks.py", line 75, in start self._run() File "/usr/lib64/python3.12/site-packages/pyanaconda/installation_tasks.py", line 188, in _run item.start() File "/usr/lib64/python3.12/site-packages/pyanaconda/installation_tasks.py", line 75, in start self._run() File "/usr/lib64/python3.12/site-packages/pyanaconda/installation_tasks.py", line 188, in _run item.start() File "/usr/lib64/python3.12/site-packages/pyanaconda/installation_tasks.py", line 75, in start self._run() File "/usr/lib64/python3.12/site-packages/pyanaconda/installation_tasks.py", line 188, in _run item.start() File "/usr/lib64/python3.12/site-packages/pyanaconda/installation_tasks.py", line 75, in start self._run() File "/usr/lib64/python3.12/site-packages/pyanaconda/installation.py", line 515, in _run_installation queue.start() File "/usr/lib64/python3.12/site-packages/pyanaconda/installation.py", line 80, in run self._run_installation( File "/usr/lib64/python3.12/site-packages/pyanaconda/modules/common/task/task.py", line 107, in _task_run_callback self._set_result(self.run()) File "/usr/lib64/python3.12/site-packages/pyanaconda/modules/common/task/task.py", line 94, in _thread_run_callback self._task_run_callback() File "/usr/lib64/python3.12/threading.py", line 989, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.12/site-packages/pyanaconda/core/threads.py", line 280, in run threading.Thread.run(self) File "/usr/lib64/python3.12/site-packages/pyanaconda/core/threads.py", line 171, in raise_if_error raise exc_info[1] File "/usr/lib64/python3.12/site-packages/pyanaconda/modules/common/task/task.py", line 173, in finish thread_manager.raise_if_error(self._thread_name) File "/usr/lib64/python3.12/site-packages/pyanaconda/ui/gui/spokes/installation_progress.py", line 75, in _on_installation_done self._task.finish() File "/usr/lib64/python3.12/site-packages/pyanaconda/core/signal.py", line 41, in emit func(obj, *args, **kargs) File "/usr/lib64/python3.12/site-packages/pyanaconda/modules/common/task/runnable.py", line 115, in _task_stopped_callback self._stopped_signal.emit() File "/usr/lib64/python3.12/site-packages/pyanaconda/core/async_utils.py", line 68, in _idle_method func(*args, **kwargs) pyanaconda.modules.common.errors.installation.BootloaderInstallationError: Failed to set new efi boot target. This is most likely a kernel or firmware bug. Additional info: comment: f39 install cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --graphical executable: /sbin/anaconda hashmarkername: anaconda product: Fedora package: anaconda-core-39.32.2-1.fc39.x86_64 reason: pyanaconda.modules.common.errors.installation.BootloaderInstallationError: Failed to set new efi boot target. This is most likely a kernel or firmware bug. release_type: pre-release type: anaconda release: Fedora release 39 (Thirty Nine) cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-39-20230916-n-0 rd.live.image quiet rhgb addons: com_redhat_kdump kernel: 6.5.3-300.fc39.x86_64 version: 39 other involved packages: python3-dasbus-1.7-4.fc39.noarch, anaconda-gui-39.32.2-1.fc39.x86_64, python3-libs-3.12.0~rc1-1.fc39.x86_64
Created attachment 1989195 [details] File: anaconda-tb
Created attachment 1989196 [details] File: backtrace
Created attachment 1989197 [details] File: os_info
Created attachment 1989198 [details] File: environ
Created attachment 1989199 [details] File: journalctl
Created attachment 1989200 [details] File: description
Created attachment 1989201 [details] File: storage.log
Created attachment 1989202 [details] File: packaging.log
Created attachment 1989203 [details] File: program.log
Created attachment 1989204 [details] File: nmcli_dev_list
Created attachment 1989205 [details] File: anaconda.log
Created attachment 1989206 [details] File: lsblk_output
Created attachment 1989207 [details] File: dbus.log
Created attachment 1989208 [details] File: packaging.log
I'm confused with the relationships you're setting up, sorry. Are this bug and https://bugzilla.redhat.com/show_bug.cgi?id=2236626 different? How do both or either of them relate to https://bugzilla.redhat.com/show_bug.cgi?id=2236301 ? Thanks!
Adam, Same hardware, not directly related to the kernel bug ticket. I thought they might have something to do with each other, but depends on was not right. https://bugzilla.redhat.com/show_bug.cgi?id=2236626 is just an older image install attempt. I did another attempt for Fedora 39 Branched 20230916.n.0 and this was the result. This seems to have more technical details, but mostly the same information. Should I mark as duplicate and keep the newer one open?
Yes, please. Thanks.
*** Bug 2236626 has been marked as a duplicate of this bug. ***
Where did you find the error message referenced in the dupe, "Configuring storage org.fedoraproject.Anaconda.Error: [Errno 17] File exists: '/proc/self/mounts' -> '/mnt/sysroot/etc/mtab'" ? I can't find that message in any of the logs attached to that bug or this one. Was it displayed somewhere?
The error message about file exists was automatically filled in by the WebUI bug reporting process. I'm not sure where the WebUI got that as I also don't see it in the webui.log. It looks like in both the WebUI and gtk case something is dasbus is tripping up and resulting in the pyanaconda.modules.common.errors.installation.BootloaderInstallationError raise.
Well, the dbus stuff is just to do with how anaconda runs things internally (it's kinda modular and uses dbus to communicate). This is weird, though. Logically, the only way we can get this error is if the attempt to run `efibootmgr` to add an EFI boot manager menu entry for the new Fedora install fails, because that's the only place an exception with this text is raised: https://github.com/rhinstaller/anaconda/blob/5986213bdf4bcc7e354edbf7e2bf9954252277de/pyanaconda/modules/storage/bootloader/efi.py#L81-L95 but usually when this happens, the call to efibootmgr and its result should be logged in program.log . However, in this case, I can't find that output there or anywhere else in the logs, which makes it hard to see what might have gone wrong. I don't know if that's a bug in anaconda or what...
Okay, this is very helpful. I'll do another F38->Rawhide install on this hardware and see if I can trip up efibootmgr using it in the way that anaconda is calling it.
yeah, if you have the skills, one thing you can try is run an install, wait for it to fail, then go to a console - you can get one on tty3 - chroot to /mnt/sysimage and try running efibootmgr directly...
*** Bug 2236621 has been marked as a duplicate of this bug. ***
Okay, I'll try the runtime test now after it fails. I just installed F38->F39 and efibootmgr reports that this system is not supported. efibootmgr-18-4.fc39.x86_64 [root@fedora ~]# efibootmgr EFI variables are not supported on this system.
Hum. That would usually mean you're on a BIOS native install, but...this is a Mac, right? Can you attach the journal from that boot?
I have confirmed that in vt3, chrooted into the sysimage, using efibootmgr-18-4.fc39.x86_64, running what I've guessed are the options passed based on the python code, I also get: # efibootmgr -c -w -L 'linux-label' -d '/dev/nvme0n1' -p 1 -l \EFI\default\\shimx64.efi EFI variables are not supported on this system. I'll reinstall (since the disk was wiped) F38->F39 and then attach a boot log.
Created attachment 1989781 [details] lshw
Created attachment 1989782 [details] journal for boot on F39 upgrade (F38->F39)
OK, so I'm temporarily reassigning this to efibootmgr. But it may well end up being a kernel issue, or something. let's see. do you know exactly what model of Mac this is?
Yes, this is a MacBookPro14,1.
If it fails as described in comment 27 what is in /sys/firmware/efi/efivars/ ?
Thanks Petr, I actually meant to ask the same question and lost this in the forest of tabs! needinfoing Jonathan.
Well of course with the latest F39 kernel it works: jon@fedora:~$ efibootmgr BootCurrent: 000C BootOrder: 000C,000B,000A,0009,0008,0007,0006,0005,0004,0003,0002,0001,0000,0080 Boot0000* Fedora HD(1,GPT,0bfc06d0-1afd-42f7-a614-2114388fa9fa,0x100,0x25800)/File(\EFI\fedora\shimx64.efi) Boot0001* Fedora HD(1,GPT,7d9892cf-941d-4138-8ab8-b8aa8f2e9abc,0x100,0x25800)/File(\EFI\fedora\shimx64.efi) Boot0002* Fedora HD(1,GPT,4969b2c1-cc9f-419d-bcea-fc2b40ea5771,0x100,0x25800)/File(\EFI\fedora\shimx64.efi) Boot0003* Fedora HD(1,GPT,4969b2c1-cc9f-419d-bcea-fc2b40ea5771,0x100,0x25800)/File(\EFI\fedora\shimx64.efi) Boot0004* Fedora HD(1,GPT,34334bc1-004f-4ff5-b61a-d447c8bf223d,0x100,0x100000)/File(\EFI\fedora\shimx64.efi) Boot0005* Fedora HD(1,GPT,34334bc1-004f-4ff5-b61a-d447c8bf223d,0x100,0x100000)/File(\EFI\fedora\shimx64.efi) Boot0006* Fedora HD(1,GPT,d200f292-451b-4376-9a00-14cc812fc9a4,0x100,0x25800)/File(\EFI\fedora\shimx64.efi) Boot0007* Fedora HD(1,GPT,05e2a19d-b1c4-49bf-bca1-5d513be28d33,0x100,0x25800)/File(\EFI\fedora\shimx64.efi) Boot0008* Fedora HD(1,GPT,2713f0a3-5433-4510-8b2f-087413026559,0x100,0x25800)/File(\EFI\fedora\shimx64.efi) Boot0009* Fedora HD(1,GPT,8073933c-74fa-4648-91fc-d9c1689487f8,0x100,0x25800)/File(\EFI\fedora\shimx64.efi) Boot000A* Fedora HD(1,GPT,8073933c-74fa-4648-91fc-d9c1689487f8,0x100,0x25800)/File(\EFI\fedora\shimx64.efi) Boot000B* Fedora HD(1,GPT,f99f065f-1630-4a57-8104-e3afc75d9513,0x100,0x25800)/File(\EFI\fedora\shimx64.efi) Boot000C* Fedora HD(1,GPT,f99f065f-1630-4a57-8104-e3afc75d9513,0x100,0x25800)/File(\EFI\fedora\shimx64.efi) Boot0080* PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(1,GPT,a4cd70cf-c0d9-4844-bb29-2499cf39ac0c,0x100,0x25800)/File(\EFI\fedora\grubx64.efi) BootFFFF* PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(1,GPT,a4cd70cf-c0d9-4844-bb29-2499cf39ac0c,0x100,0x25800)/File(\EFI\fedora\grubx64.efi) jon@fedora:~$ uname -r 6.5.5-300.fc39.x86_64 jon@fedora:~$ rpm -q efibootmgr efibootmgr-18-4.fc39.x86_64 But with the kernel on the install media: jon@fedora:~$ efibootmgr EFI variables are not supported on this system. jon@fedora:~2$ uname -r 6.5.3-300.fc39.x86_64 jon@fedora:~$ rpm -q efibootmgr efibootmgr-18-4.fc39.x86_64 jon@fedora:~$ ls -Ral /sys/firmware/efi/efivars/ /sys/firmware/efi/efivars/: total 0 drwxr-xr-x. 2 root root 0 Sep 26 18:47 . drwxr-xr-x. 5 root root 0 Sep 26 18:49 .. -rw-r--r--. 1 root root 314 Sep 26 18:47 AAPL,PathProperties0000-4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14 -rw-r--r--. 1 root root 246 Sep 26 18:47 aht-results-7c436110-ab2a-4bbb-a880-fe41995c9f82 -rw-r--r--. 1 root root 12 Sep 26 18:47 ALS_Data-7c436110-ab2a-4bbb-a880-fe41995c9f82 -rw-r--r--. 1 root root 376 Sep 26 18:47 battery-health-735b3b05-2634-4253-9db8-5a048b418e3d -rw-r--r--. 1 root root 5 Sep 26 18:47 BBIF-4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14 -rw-r--r--. 1 root root 5 Sep 26 18:47 bluetoothExternalDongleFailed-7c436110-ab2a-4bbb-a880-fe41995c9f82 -rw-r--r--. 1 root root 18 Sep 26 18:47 bluetoothInternalControllerInfo-7c436110-ab2a-4bbb-a880-fe41995c9f82 -rw-r--r--. 1 root root 122 Sep 26 18:47 Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 122 Sep 26 18:47 Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 122 Sep 26 18:47 Boot0002-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 122 Sep 26 18:47 Boot0003-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 122 Sep 26 18:47 Boot0004-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 122 Sep 26 18:47 Boot0005-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 122 Sep 26 18:47 Boot0006-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 122 Sep 26 18:47 Boot0007-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 122 Sep 26 18:47 Boot0008-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 122 Sep 26 18:47 Boot0009-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 122 Sep 26 18:47 Boot000A-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 122 Sep 26 18:47 Boot000B-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 122 Sep 26 18:47 Boot000C-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 150 Sep 26 18:47 Boot0080-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 6 Sep 26 18:47 BootCampProcessorPstates-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 6 Sep 26 18:47 BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 150 Sep 26 18:47 BootFFFF-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 32 Sep 26 18:47 BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 154 Sep 26 18:47 ConIn-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 68 Sep 26 18:47 ConInDev-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 80 Sep 26 18:47 ConOut-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 102 Sep 26 18:47 ConOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 196 Sep 26 18:47 current-network-7c436110-ab2a-4bbb-a880-fe41995c9f82 -rw-r--r--. 1 root root 8 Sep 26 18:47 epid_provisioned-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 80 Sep 26 18:47 ErrOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 12 Sep 26 18:47 ExtendedFirmwareFeatures-4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14 -rw-r--r--. 1 root root 12 Sep 26 18:47 ExtendedFirmwareFeaturesMask-4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14 -rw-r--r--. 1 root root 8 Sep 26 18:47 FirmwareFeatures-4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14 -rw-r--r--. 1 root root 8 Sep 26 18:47 FirmwareFeaturesMask-4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14 -rw-r--r--. 1 root root 12 Sep 26 18:47 gfx-saved-config-restore-status-4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14 -rw-r--r--. 1 root root 12 Sep 26 18:47 GR_CAUSE-4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14 -rw-r--r--. 1 root root 8 Sep 26 18:47 HardwareBootMode-4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14 -rw-r--r--. 1 root root 24 Sep 26 18:47 HW_BID-4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14 -rw-r--r--. 1 root root 209 Sep 26 18:47 HW_BOOT_DATA-7c436110-ab2a-4bbb-a880-fe41995c9f82 -rw-r--r--. 1 root root 5 Sep 26 18:47 HW_BREV-4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14 -rw-r--r--. 1 root root 168 Sep 26 18:47 HW_ICT-4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14 -rw-r--r--. 1 root root 21 Sep 26 18:47 HW_MLB-4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14 -rw-r--r--. 1 root root 10 Sep 26 18:47 HW_ROM-4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14 -rw-r--r--. 1 root root 203 Sep 26 18:47 IDInstallerDataV2-7c436110-ab2a-4bbb-a880-fe41995c9f82 -rw-r--r--. 1 root root 6 Sep 26 18:47 KeyboardBacklightLevel-a076d2af-9678-4386-8b58-1fc8ef041619 -rw-r--r--. 1 root root 8 Sep 26 18:47 Lang-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 8 Sep 26 18:47 LangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 424 Sep 26 18:47 mca-info0-7c436110-ab2a-4bbb-a880-fe41995c9f82 -rw-r--r--. 1 root root 3667 Sep 26 18:47 MemoryConfig-c94f8c4d-9b9a-45fe-8a55-238b67302643 -rw-r--r--. 1 root root 21 Sep 26 18:47 MLB-4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14 -rw-r--r--. 1 root root 924 Sep 26 18:47 MokListRT-605dab50-e046-4300-abb6-3dd810dd8b23 -rw-r--r--. 1 root root 5 Sep 26 18:47 MokListTrustedRT-605dab50-e046-4300-abb6-3dd810dd8b23 -rw-r--r--. 1 root root 80 Sep 26 18:47 MokListXRT-605dab50-e046-4300-abb6-3dd810dd8b23 -rw-r--r--. 1 root root 8 Sep 26 18:47 MTC-eb704011-1402-11d3-8e77-00a0c969723b -rw-r--r--. 1 root root 10 Sep 26 18:47 PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 10 Sep 26 18:47 PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c -rw-r--r--. 1 root root 12 Sep 26 18:47 preferred-count-36c28ab5-6566-4c50-9ebd-cbb920f83843 -rw-r--r--. 1 root root 12 Sep 26 18:47 preferred-count-7c436110-ab2a-4bbb-a880-fe41995c9f82 -rw-r--r--. 1 root root 7 Sep 26 18:47 prev-lang-diags:kbd-7c436110-ab2a-4bbb-a880-fe41995c9f82 -rw-r--r--. 1 root root 8 Sep 26 18:47 PRTCCounter-4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14 -rw-r--r--. 1 root root 10 Sep 26 18:47 ROM-4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14 -rw-r--r--. 1 root root 22 Sep 26 18:47 SbatLevelRT-605dab50-e046-4300-abb6-3dd810dd8b23 -rw-r--r--. 1 root root 17 Sep 26 18:47 SSN-4d1ede05-38c7-4a6a-9cc6-4bcca8b38c14 -rw-r--r--. 1 root root 5 Sep 26 18:47 SystemAudioVolume-7c436110-ab2a-4bbb-a880-fe41995c9f82 -rw-r--r--. 1 root root 5 Sep 26 18:47 SystemAudioVolumeDB-7c436110-ab2a-4bbb-a880-fe41995c9f82
Jonathan: sorry, I kinda lost track of this bug. So if efibootmgr works with recent F39 kernels, does that mean the bug is fixed with recent F39 installer images? Can you check with a recent nightly and see? https://openqa.fedoraproject.org/nightlies.html
*** Bug 2243144 has been marked as a duplicate of this bug. ***
I'm proposing this as a Final blocker as a violation of "The installer must be able to install into free space alongside an existing macOS installation, install and configure a bootloader that will boot Fedora" - https://fedoraproject.org/wiki/Fedora_39_Final_Release_Criteria#macOS_dual_boot - but also marking it ON_QA as, based on Jonathan's info above, I'm hopeful it should be fixed with recent images. If someone could confirm that would be great.
I can confirm that on the MBP 14,1 the Fedora-39-20231017.n.0 Workstation Live image successfully installs. jon@fedora:~$ efibootmgr BootCurrent: 0000 BootOrder: 0000,0080 Boot0000* Fedora HD(1,GPT,98e333dc-abf9-42f0-99d8-bab1885b2e5f,0x100,0x25800)/File(\EFI\fedora\shimx64.efi) Boot0080* PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(1,GPT,a4cd70cf-c0d9-4844-bb29-2499cf39ac0c,0x100,0x25800)/File(\EFI\fedora\grubx64.efi) BootFFFF* PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(1,GPT,a4cd70cf-c0d9-4844-bb29-2499cf39ac0c,0x100,0x25800)/File(\EFI\fedora\grubx64.efi) jon@fedora:~$ uname -r 6.5.6-300.fc39.x86_64
Awesome! Thanks. Osama, if you can confirm a recent nightly works for you too, I think we can close the bug.
(In reply to Adam Williamson from comment #39) > Awesome! Thanks. Osama, if you can confirm a recent nightly works for you > too, I think we can close the bug. The install finished successfully with the latest nightly Fedora-39-20231017.n.0 Workstation Live image for me too :) liveuser@localhost-live:~$ chroot /mnt/sysimage chroot: cannot change root directory to '/mnt/sysimage': Operation not permitted liveuser@localhost-live:~125$ sudo !! sudo chroot /mnt/sysimage root@localhost-live:/# efibootmgr BootCurrent: 0000 BootOrder: 0001,0080,0005,0000,0004 Boot0000* ubuntu HD(1,GPT,723a528b-ae0c-4968-838a-148c20df0919,0x6,0x12c00)/File(\EFI\ubuntu\shimx64.efi) Boot0001* Fedora HD(3,GPT,f40d2243-f59e-4d06-983c-da8f83af599d,0x12efe00,0x25800)/File(\EFI\fedora\shimx64.efi) Boot0004* Garuda HD(1,GPT,94df5817-d1e3-da4e-8fe6-e507e64fc009,0x1000,0x96000)/File(\EFI\Garuda\grubx64.efi) Boot0005* Pop!_OS 22.04 LTS HD(1,GPT,16b0ef43-fb58-4d9b-9597-3d8b6547f6c7,0x1000,0x1fefff)/File(\EFI\systemd\systemd-bootx64.efi) Boot0080* Mac OS X PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(2,GPT,1050ba0d-049f-43dc-b862-32843d6fb66e,0x12c06,0x12dd0fc)/VenMedia(be74fcf7-0b7c-49f3-9147-01f4042e6842,35b1b2027eec694bb7231f6be821978d)/File(\1AAA88A4-F0D7-4B64-858A-EECD314835D2\System\Library\CoreServices\boot.efi) Boot0081* Mac OS X VenMedia(be74fcf7-0b7c-49f3-9147-01f4042e6842,91e8f0e548991b43b4cc01a2a7684026)/File(\73B793A0-52ED-4833-A804-5A416D183407\System\Library\CoreServices\boot.efi) Boot0082* PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(2,GPT,1050ba0d-049f-43dc-b862-32843d6fb66e,0x12c06,0x12dd0fc)/VenMedia(be74fcf7-0b7c-49f3-9147-01f4042e6842,35b1b2027eec694bb7231f6be821978d)/File(\1AAA88A4-F0D7-4B64-858A-EECD314835D2\System\Library\CoreServices\boot.efi) BootFFFF* PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(2,GPT,1050ba0d-049f-43dc-b862-32843d6fb66e,0x12c06,0x1c2d3f5)/VenMedia(be74fcf7-0b7c-49f3-9147-01f4042e6842,35b1b2027eec694bb7231f6be821978d)/File(\8607C61C-A9F7-4B6F-9E93-3F99AF342D51\System\Library\CoreServices\boot.efi) root@localhost-live:/# uname -r 6.5.6-300.fc39.x86_64
Awesome! Let's close this, then. Thanks to both of you for the confirmation.