You are not logged in.
Pages: 1
Hello, first post here and kinda newbie.
Ok, so this is my first time doing an Arch installation and still learning. Still configuring my new system.
I decided to enable Secure boot. I have both Windows and Arch installed right now. (different disks)
Anyway, I decided to disable it, since there was some configuration to do and read about it some other time. Now it's disabled.
The thing is.. since i disabled it, everytime I boot my PC a new entry is added to the UEFI boot menu. An entry that leads to the Arch installation.
https://i.paste.pics/8e7798a0b4c192582f … b59846.png
Anyone has any idea what's going wrong? How do i stop this? Will it reach infinite entries?
Thanks a lot!
Mod Edit - Replaced oversized image with link.
CoC - Pasting pictures and code
Last edited by Slithery (2019-10-30 21:06:54)
Offline
I don't think it is creating creating new entries. The UEFI OS in your pastebin looks like your Arch installation and your BIOS is merely setting it up as the default OS to each successive boot order.
I am not entirely clear. Are you trying to remove the Arch OS entry in your motherboard's NVRAM?
Offline
Since I installed both OSes, I always had two entries in the boot menu. One for Windows and one for Arch.
I didn't want to remove anything, I just enabled and then disabled the Secure Boot option.
The problem is that everytime I boot into Arch a new "UEFI OS" entry is added in the menu. The screenshot shows 8 options. Since then, I booted into Arch two more times. Now it has 10 options.
Of course right now I want to remove them and I know the way. The thing is I don't know how to stop the firmware from adding new entries everytime.
It really seems like a bug, and there is no newer version since 2016.
What I'm thinking now is to clear the SSD that Arch is installed of all data. Return UEFI to it's original configuration and flash it with the latest version again. Then reinstall and see how it goes. I'll do it tomorrow and see how it goes.
If anyone though knows something more please inform me.
Offline
Before doing something drastic as reinstalling the BIOS (dangerous too) and wiping your Arch install, you can clean up your NVRAM first, removing your Arch entry there, and see what that brings. It could be that there's just a bit-flag regarding secure boot on the Arch entry that's causing the problem. The best way is to boot into a UEFI-Shell. You can create a bootable usb UEFI shell by following this. I've done this in the past and the link works for me. You can find the shell commands here but you will mainly need bcfg for listing your entries and removing the Arch entry (make sure not to remove Windows entry). Once you've removed the Arch entry, see if the old problem persist. If not then you can boot Arch via a bootable media, chroot to your old SSD installation and create a new entry via efibootmgr. Reboot and see if the old problem returns (with Secure Boot disabled of course).
Offline
Pages: 1
