Description of problem: Install Fedora-Everything-netinst-aarch64-Rawhide-20250724.n.0.iso on NXP i.MX8MP-EVK(AARCH64). In step "Installing boot loader", it reports the error. Version-Release number of selected component: anaconda-43.31 The following was filed automatically by anaconda: anaconda 43.31 exception report Traceback (most recent call first): File "/usr/lib/python3.14/site-packages/dasbus/client/handler.py", line 509, in _handle_method_error raise exception from None File "/usr/lib/python3.14/site-packages/dasbus/client/handler.py", line 483, in _get_method_reply return self._handle_method_error(error) File "/usr/lib/python3.14/site-packages/dasbus/client/handler.py", line 450, in _call_method return self._get_method_reply( File "/usr/lib64/python3.14/site-packages/pyanaconda/ui/gui/spokes/installation_progress.py", line 76, in _on_installation_done self._task_proxy.Finish() File "/usr/lib/python3.14/site-packages/dasbus/signal.py", line 53, in emit callback(*args, **kwargs) File "/usr/lib/python3.14/site-packages/dasbus/client/handler.py", line 365, in _signal_callback callback(*unwrap_variant(parameters)) File "/usr/lib/python3.14/site-packages/dasbus/client/handler.py", line 133, in _signal_callback callback(parameters, *callback_args) pyanaconda.modules.common.errors.installation.BootloaderInstallationError: Failed to set new efi boot target. This is most likely a kernel or firmware bug. Additional info: cmdline: /usr/bin/python3 /usr/bin/anaconda executable: /usr/bin/anaconda hashmarkername: anaconda 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. package: anaconda-43.31 release_type: pre-release type: anaconda release: Fedora release 43 (Rawhide) cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-E-dvd-aarch64-rawh rd.live.check addons: com_redhat_kdump kernel: 6.16.0-0.rc7.60.fc43.aarch64 version: rawhide
Created attachment 2098167 [details] File: anaconda-tb
Created attachment 2098168 [details] File: backtrace
Created attachment 2098169 [details] File: os_info
Created attachment 2098170 [details] File: environ
Created attachment 2098171 [details] File: syslog
Created attachment 2098172 [details] File: description
Created attachment 2098173 [details] File: storage.log
Created attachment 2098174 [details] File: packaging.log
Created attachment 2098175 [details] File: program.log
Created attachment 2098176 [details] File: nmcli_dev_list
Created attachment 2098177 [details] File: anaconda.log
Created attachment 2098178 [details] File: lorax-packages.log
Created attachment 2098179 [details] File: lsblk_output
Created attachment 2098180 [details] File: dbus.log
Created attachment 2098181 [details] File: packaging.log
This is because the device doesn't implement UEFI set variable. It should offer an option to continue. It's been dealt with upstream with the following PR https://github.com/rhboot/efivar/pull/282 But I'm not sure efivar has had a new release or that patch hasn't been pulled in yet.
*** This bug has been marked as a duplicate of bug 2367837 ***