My name is Alberto and I am new in the Fedora community. I hope my questions here are not very dummy or responded in other threads
I am actually trying to install Fedora 43 KDE on my “old” Asus Vivobook 15 (2022) and I am facing issues always with at the mid of installation with the anaconda bootloader.
I was following this thread which looked similar to what I was facing despite my PC not being Toshiba, but unfortunately not even just leaving the USB as only starting point with the efibootmgr is working.
Do you guys have any idea if an outated UEFI or any Asus known issue could be affecting?
More details in case needed:
Origiing of ISO file: Fedora Webpage
Method: flashed USB with Rufus
Notes: deactivated autoplay and realtime windows protection before flashing USB.
Any advice is welcome. Here ypu can find some pics of my error, installtion configuration and efiboot output.
Maybe a silly question from me, but: what happens if you ignore the error message and just try to boot into your new installation?
The output of efibootmgr in your screenshot shows that there is a Fedora entry there. And If you’re replacing one Fedora install with another, then as long as you’re reusing the same EFI partition, the old entry should still be valid for the new install - so it shouldn’t actually matter that Anaconda fails to replace and recreate it.
Strange on the ufibootmgr screenshot you have a usb HD with an MBR is this right? Fedora installer has a problem when this is not comes with a GPT boot record.
Yeah, i think it is not a silly question and i also thought the same.
Unfortunately when I try to jist boot on that, it only opens the GRUB terminal and offers me the option to go to UEFI settings again.
Regarding your question: the initial replacement was from windows, i rhink tahr entry remains just from one of the previous tries i made this afternoon.
I am very dummy on UEFI and booting in general, but seems the boot entry was created but not properly finished or corrupted (?)
Once the usb device boots I would suggest making certain the disk you are installing to is clean by using a terminal on the live media and running the commands
su - to gain root privileges
gdisk /dev/nvme0n1 to open the gpt partition manager
press o to create a new blank partition table on that device.
press w to write the new partition table to the drive and exit from gdisk.
Finally just click the installer icon and it should now install properly since the steps above will totally erase any lingering effects of having had windows previously installed on the SSD.
It looks good, but I must ask if you are using the storage editor or if you are allowing the system to do the automatic partitioning for you.?
Since you have wiped out the windows partition table completely using gdisk (assuming you followed my suggestion above) and are installing new onto a disk with an empty partition table it is not required to use the storage editor at all. The automatic partitioning does almost exactly what you show in that image.
When I do an installation of f44 onto a VM I see this
Clicking the ‘erase data and install’ button actually performs the installation using the automatic partitioning onto a 20GB virtual disk (vda). Yes, I am using Workstation and you are using KDE but the installation should be the same.
I just wanted to share with you all that I found the “solution”: i searched for UEFI updates for my model (Asus Vivobook Pro 15) and there was an update available from late 2022.
I just updated the UEFI and then tried it again: it worked straightaway
Nevertheless, your suggestions wer also applied during de process and were really helpful learning for mo, so many thanks!
I set this thread as resolved for anyone that faces issues with the same PC model i have.
