Description of problem: installing fresh onto free space on the main osx boot disk of an iMac fifteen-five Version-Release number of selected component: anaconda-core-37.12.6-1.fc37.x86_64 The following was filed automatically by anaconda: anaconda 37.12.6 exception report Traceback (most recent call first): File "/usr/lib/python3.11/site-packages/dasbus/client/handler.py", line 497, in _handle_method_error raise exception from None File "/usr/lib/python3.11/site-packages/dasbus/client/handler.py", line 477, in _get_method_reply return self._handle_method_error(error) File "/usr/lib/python3.11/site-packages/dasbus/client/handler.py", line 444, in _call_method return self._get_method_reply( File "/usr/lib64/python3.11/site-packages/pyanaconda/modules/common/task/__init__.py", line 46, in sync_run_task task_proxy.Finish() File "/usr/lib64/python3.11/site-packages/pyanaconda/installation.py", line 439, in run_install_bootloader sync_run_task(STORAGE.get_proxy(task)) File "/usr/lib64/python3.11/site-packages/pyanaconda/installation_tasks.py", line 246, in _run self._task_cb(*self._task_args, **self._task_kwargs) File "/usr/lib64/python3.11/site-packages/pyanaconda/installation_tasks.py", line 75, in start self._run() File "/usr/lib64/python3.11/site-packages/pyanaconda/installation_tasks.py", line 188, in _run item.start() File "/usr/lib64/python3.11/site-packages/pyanaconda/installation_tasks.py", line 75, in start self._run() File "/usr/lib64/python3.11/site-packages/pyanaconda/installation_tasks.py", line 188, in _run item.start() File "/usr/lib64/python3.11/site-packages/pyanaconda/installation_tasks.py", line 75, in start self._run() File "/usr/lib64/python3.11/site-packages/pyanaconda/installation_tasks.py", line 188, in _run item.start() File "/usr/lib64/python3.11/site-packages/pyanaconda/installation_tasks.py", line 75, in start self._run() File "/usr/lib64/python3.11/site-packages/pyanaconda/installation.py", line 515, in _run_installation queue.start() File "/usr/lib64/python3.11/site-packages/pyanaconda/installation.py", line 80, in run self._run_installation( File "/usr/lib64/python3.11/site-packages/pyanaconda/modules/common/task/task.py", line 109, in _task_run_callback self._set_result(self.run()) File "/usr/lib64/python3.11/site-packages/pyanaconda/modules/common/task/task.py", line 96, in _thread_run_callback self._task_run_callback() File "/usr/lib64/python3.11/threading.py", line 975, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.11/site-packages/pyanaconda/threading.py", line 275, in run threading.Thread.run(self) File "/usr/lib64/python3.11/site-packages/pyanaconda/threading.py", line 166, in raise_if_error raise exc_info[1] File "/usr/lib64/python3.11/site-packages/pyanaconda/modules/common/task/task.py", line 175, in finish threadMgr.raise_if_error(self._thread_name) File "/usr/lib64/python3.11/site-packages/pyanaconda/ui/gui/spokes/installation_progress.py", line 75, in _on_installation_done self._task.finish() File "/usr/lib64/python3.11/site-packages/pyanaconda/core/signal.py", line 41, in emit func(obj, *args, **kargs) File "/usr/lib64/python3.11/site-packages/pyanaconda/modules/common/task/runnable.py", line 115, in _task_stopped_callback self._stopped_signal.emit() File "/usr/lib64/python3.11/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: addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --graphical cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-37-1-7 rd.live.image rd.live.check quiet dnf.librepo.log: executable: /sbin/anaconda hashmarkername: anaconda kernel: 6.0.7-301.fc37.x86_64 other involved packages: anaconda-gui-37.12.6-1.fc37.x86_64, python3-libs-3.11.0-1.fc37.x86_64, python3-dasbus-1.6-6.fc37.noarch product: Fedora release: Fedora release 37 (Thirty Seven) type: anaconda version: 37
Created attachment 1924486 [details] File: anaconda-tb
Created attachment 1924487 [details] File: anaconda.log
Created attachment 1924488 [details] File: dbus.log
Created attachment 1924489 [details] File: environ
Created attachment 1924490 [details] File: journalctl
Created attachment 1924491 [details] File: lsblk_output
Created attachment 1924492 [details] File: nmcli_dev_list
Created attachment 1924493 [details] File: os_info
Created attachment 1924494 [details] File: program.log
Created attachment 1924495 [details] File: storage.log
Similar problem has been detected: Device: MacBook Pro 2015 15 inch with SSD How to reproduce: Using aforementioned device, format SSD with Fedora Live USB "Disks" utility to be empty prior to install Run install with automatic partitioning option During install, install fails with the "Failed to set new efi boot target" error Note, that also all other partitioning options were tried with similar effects. addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --graphical cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-37-1-7 rd.live.image quiet rhgb dnf.librepo.log: hashmarkername: anaconda kernel: 6.0.7-301.fc37.x86_64 other involved packages: anaconda-gui-37.12.6-1.fc37.x86_64, python3-libs-3.11.0-1.fc37.x86_64, python3-dasbus-1.6-6.fc37.noarch package: anaconda-core-37.12.6-1.fc37.x86_64 packaging.log: product: Fedora reason: pyanaconda.modules.common.errors.installation.BootloaderInstallationError: Failed to set new efi boot target. This is most likely a kernel or firmware bug. release: Fedora release 37 (Thirty Seven) version: 37
Similar problem has been detected: Running the installer on an iMac 13,1 on a freshly formatted and unpartitioned hard disk. addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --graphical cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-37-1-7 rd.live.image quiet rhgb dnf.librepo.log: hashmarkername: anaconda kernel: 6.0.7-301.fc37.x86_64 other involved packages: python3-libs-3.11.0-1.fc37.x86_64, anaconda-gui-37.12.6-1.fc37.x86_64, python3-dasbus-1.6-6.fc37.noarch package: anaconda-core-37.12.6-1.fc37.x86_64 packaging.log: product: Fedora reason: pyanaconda.modules.common.errors.installation.BootloaderInstallationError: Failed to set new efi boot target. This is most likely a kernel or firmware bug. release: Fedora release 37 (Thirty Seven) version: 37
Similar problem has been detected: Trying to install Fedora Workstation 37 on a MacBook Air 11-inch, mid-2012 (8GB RAM, 60GB SSD, model: MacBookAir5,1). Booting from USB worked. But install failed with error "failed to set new efi boot target". I chose to delete all existing partitions, encrypt the drive, and use auto partitioning. This MacBook Air used to have chromeOS Flex and then Ubuntu 22.10 installed. Side note: I had to attach a USB Realtek Wi-Fi dongle because the included Broadcom drivers don't really work -- it shows full Wi-Fi signal bars but does not connect to any websites. This bug report was written from within the live USB session. Hope this helps. addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --graphical cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-37-1-7 rd.live.image quiet rhgb dnf.librepo.log: hashmarkername: anaconda kernel: 6.0.7-301.fc37.x86_64 other involved packages: python3-dasbus-1.6-6.fc37.noarch, anaconda-gui-37.12.6-1.fc37.x86_64, python3-libs-3.11.0-1.fc37.x86_64 package: anaconda-core-37.12.6-1.fc37.x86_64 packaging.log: product: Fedora reason: pyanaconda.modules.common.errors.installation.BootloaderInstallationError: Failed to set new efi boot target. This is most likely a kernel or firmware bug. release: Fedora release 37 (Thirty Seven) version: 37
Similar problem has been detected: SSStarrteddd the install, chosee to delete all existingg partitionss, ennablled encryptioon. ((Sorry abbout duplicate lettters, but it's barely letting me type at aall.) addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --graphical cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-37-1-7 rd.live.image rd.live.check quiet dnf.librepo.log: hashmarkername: anaconda kernel: 6.0.7-301.fc37.x86_64 other involved packages: python3-dasbus-1.6-6.fc37.noarch, python3-libs-3.11.0-1.fc37.x86_64, anaconda-gui-37.12.6-1.fc37.x86_64 package: anaconda-core-37.12.6-1.fc37.x86_64 packaging.log: product: Fedora reason: pyanaconda.modules.common.errors.installation.BootloaderInstallationError: Failed to set new efi boot target. This is most likely a kernel or firmware bug. release: Fedora release 37 (Thirty Seven) version: 37
Similar problem has been detected: - use Fedora 36 netinstall ISO on USB thumb drive (sudo su; cat *iso > /dev/sdb) to install Fedora Workstation 36 on this computer (Apple MacBook, 13-inch, Aluminium, late 2008) - F36 installation had no issue - broke F36 with non-free nvidia-340 driver from rpmfusion (kernel crash at start); description said Nvidia does not support it anymore; tested that driver because the Nvidia 9400M GPU with nouveau driver cannot properly display image on external screen (1920x1080 px, 60 Hz), i.e. solid blue color rising from bottom to top, then F36 background image shown properly, then solid color area rises again - absent minded I put computer to sleep, remove F36 hard disk, put Mac OS X 10.11 hard disk in and woke computer; to realize and notice my mistake of missing poweroff before hard disk swap; F36 crashed - I restarted notebook to Mac OS X; external screen display hardware: no problem - power down computer and remove Mac hard disk - delete F36 hard disk (dd if=/dev/zero of=/dev/sdb) and put it back in - reset USB thumb drive to Fedora 37 netinstall ISO (sudo su; cat *iso > /dev/sdb) - install Fedora Workstation 37 - download and installation of F37 packages went without problem, but in finish task section out of a sudden error message appeared stating that bootloader could not be written or something like that addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-E-dvd-x86_64-37 rd.live.check quiet hashmarkername: anaconda kernel: 6.0.7-301.fc37.x86_64 package: anaconda-37.12.6 product: Fedora reason: pyanaconda.modules.common.errors.installation.BootloaderInstallationError: Failed to set new efi boot target. This is most likely a kernel or firmware bug. release: Fedora release 37 (Thirty Seven) version: 37
> ... Nvidia 9400M GPU with nouveau driver cannot properly > display image on external screen (1920x1080 px, 60 Hz), i.e. solid blue > color rising from bottom to top, then F36 background image shown properly, > then solid color area rises again The "solid blue color" does change its color, depending on the background image. Following this: https://nouveau.freedesktop.org/TroubleShooting.html#index8h3 https://nouveau.freedesktop.org/ => /sys/kernel/debug/dri/0/pstate I could change to a rather stable image on external screen, but sometimes areas flash.
As a quick update, this problem seems resolved in F38 development version (Fedora-Workstation-Live-x86_64-38-20230220.n.0.iso).
Hey folks! It'd be great if anyone who has an Intel Mac that's safe for experimenting on can try doing a dual-boot install of Fedora 38 on it to make sure everything is OK here for F38. Our (the RH Fedora QA team) initial test of this had an issue where no option to boot macOS could be found after the Fedora install; a repeat test didn't show the same problem, but it would be great to have tests from other folks to verify it was just a one-time blip. Obviously don't try this on a Mac you really need to keep working, or which you don't know how to recover if it does get messed up. Thanks a lot! You can find the current F38 RC here: https://dl.fedoraproject.org/pub/alt/stage/38_RC-1.1/
@Kamil: I could not reproduce this bug's error message with Fedora Workstation RC 1.1 38 DVD live installer. @Adam: I could not reproduce the problem you mentioned. More details: I used the Fedora Workstation RC 1.1 DVD and "Apple MacBook, 13-inch, Aluminium, late 2008" for test installation. Anaconda installer could not resize the existing hfs+ partition or layout, hence I resized in Mac OS X 10.11 with "Disk Utility.app". In Anaconda installer I could delete the new hfs+ partition and use it for Fedora. After installation was done I rebooted and was greeted with "GRUB version 2.06" boot screen with items: Fedora Linux (6.2.9-300.fc38.x86_64) 38 (Workstation Edition) Fedora Linux (0-rescue-...) 38 (Workstation Edition) Mac OS X (on /dev/sda3) UEFI Firmware Settings Both Fedora items boot into Fedora Workstation graphical login. Mac OS X prints: error: ../../grub-core/fs/fshelp.c:257:file '/System/Library/CoreServices/boot.efi' not found. error: ../../grub-core/commands/boot.c:196:you need to load the kernel first. UEFI Firmware Settings prints: error: ../../grub-core/commands/efi/efifwsetup.c:61:Reboot to firmware setup is not supported. Booting the notebook with alt-key pressed down I was given a boot menu with: Macintosh HD Fedora Recovery-10.11.6 The "Macintosh HD" item boots into working Mac OS X 10.11.
Awesome, thanks a lot for the confirmation that it looks good for F38!
Since the install media or not going to get fixed for Fedora 37, let's close this. Anyone affected can use Fedora 38 install media (to be publicly available next week). If you still see the same issue with Fedora 38, please note it here. If you see a different issue, please create a separate bug report. Thanks.
It seems this bug is back in Fedora 39. I installed from the 2023.09.18 compose, got the EFI boot target error, and the installed system was indeed unbootable.
This is a fairly generic error message. All it really means is "we ran efibootmgr to add an efi boot manager menu entry and it failed". It can be caused by all sorts of different things; encountering it doesn't mean your bug is the same as some previous bug which encountered the same error. It's like a "file not found" error or a "oops, X crashed" error or something like that. Same effect, potentially many different causes. Unless you had a system affected by the actual initial bug here (and I don't see you in the original reporters), I wouldn't assume this has the same cause. You *may* be seeing the same thing as https://bugzilla.redhat.com/show_bug.cgi?id=2239316 , since you're both testing F39 at least.
*** Bug 2144186 has been marked as a duplicate of this bug. ***