Fedora Account System
Red Hat Associate
Red Hat Customer
Installer WebUI Critical Error: org.fedoraproject.Anaconda.BootloaderInstallationError: Failed to set new efi boot target. This is most likely a kernel or firmware bug. Please attach the log file /tmp/journal.log to the issue. ---[ System & Environment Information ]--- OS: Fedora Linux 43 (Workstation Edition) Anaconda version: 43.44 Anaconda UI version: 53.14.g7ea927aa This is an attempt to install Fedora 43 on an Asus laptop (VivoBook_ASUSLaptop X515EP_F515EP) with: RAM: 8Gb Processor: 11th Gen Intel® Core™ i3-1115G4 × 4 Graphics: Intel® UHD Graphics (TGL GT2) Firmware version: X515EP.305 I've removed any efi boot entries and the disk is cleaned. Secure boot and fast boot are both disabled. There's not a lot of information given by the installer UI, only that, on the third step, the boot setting it gives out an error, mentioned here above. I looked at the journal.log but I don't really have experience necessary to interpret it. I'm unable to attach it but have saved the file, if necessary please let me know how I can provide it to you. Reproducible: Always Steps to Reproduce: 1.Start installer 2.Choose automatic or use mount points, each one gives the same result 3.Sets the disk partitions. 4.Installs the OS 5.Aborts when setting up the bootloader Actual Results: Aborts when setting up the bootloader. Shows error message mentioned in details Expected Results: It should continue and finish installation Additional Information: I should mention that before attempting this installation I had Ubuntu installed and a year ago I had successfully installed Fedora (I think 41 or 42) KDE on this same machine. Back then I had trouble installing the nvidia drivers with secure boot on and decided to revert back to Ubuntu 24.04 because I was unsure about disabling secure boot. I tried signing some keys in order to install the nvidia driver so I don't know if the issue could be related to that, since I was successful in installing Fedora before.
Created attachment 2122341 [details] Journal log
*** This bug has been marked as a duplicate of bug 2367837 ***