Hello I recommend looking at the bios setup again. The desktop I am writing this email on is from 2011/2012 it is using UEFI and the laptop sitting in my lap is from 2013 and both are using UEFI bios. I had very similar problem stalling on my Laptop, I had to disable secure boot for the install to work properly. My laptop is HP it has two setting that can effect how it boots. 1. Legacy Support <Enabled> for MBR operating system <Disabled> for UEFI Operating system 2. Secure Boot <Enabled> /Disabled I needed to select the option "Clear All Secure Boot Keys" to disable the secure boot. If your computer was shipped with Windows 8 (release date 2012) or newer it most likely has an UEFI capable bios. Version 2.0 of UEFI specification was released in 2006, I would not make an assumption on what your computer supports. If I remember that time period even computers being shipped with Windows 7 had UEFI support; the bios was configured to use the Legacy mode. Now check to see how Fedora was installed, MBR or gpt. Use the installation media to boot the system into a shell either rescue mode or I like using the live boot media so you can have a fully functional graphical desktop and terminal. Use lsblk, fdisk and gdisk to determine if you have a MBR system or GPT system. If you need help post the output of the fdisk and gdisk command. You will need to determine what devices your system is using: $ lsblk sr0 11:0 1 4.9G 0 rom zram0 251:0 0 5.8G 0 disk [SWAP] sda 252:0 0 40G 0 disk ├─sda1 252:1 0 600M 0 part /boot/efi ├─sda2 252:2 0 1G 0 part /boot └─sda3 252:3 0 38.4G 0 part / If you see an efi mount point then you know the system was installed using UEFI and not MBR. If you do not see the efi mount point use the fdsik command, if your system is using a Legacy MBR than the output of the fdisk command will show the disklabel type as something other than gpt, I think mbr. I do not have any legacy systems to verify the output. At the root prompt (substitute / dev/sda with output from the lsblk command); # fdisk /dev/sda or using sudo $ sudo fdisk /dev/sda Post if you have further questions. Aaron On Sunday, January 30, 2022 3:15:47 PM MST WMU Bavaria wrote: > > On 01/30/2022 3:49 PM Barry <barry@xxxxxxxxxxxxxxxx> wrote: > > > > > > > > > Is this an EFI bios? If so there is a possibility that you need to reset > > the EFI variables. Some buggy EFI bios never clean up and fill nvram. > > This will prevent a new install. > > > No, at ten years old at least, it's too old for that. > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List > Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List > Archives: > https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
