You are not logged in.
Pages: 1
Hello
Following a change of motherboard (old MSI B550 TOMAHAWK, new ASROCK X670E STEEL LEGEND) I can no longer access ARCHLINUX. I was in dual boot ARCH/WINDOWS. Now I have a systematic access to WINDOWS. In the bios, at the boot level of my motherboard, I only see WI!NDOWS.
Should I reinstall ARCH or is there another way?
If I have to reinstall ARCH it is not really a problem, only a waste of time .....
Last edited by Breizh29 (2022-11-14 09:12:34)
Offline
Just re-enable the NVRAM entry for ArchLinux, see: https://wiki.archlinux.org/title/Unifie … efibootmgr
<49,17,III,I> Fama di loro il mondo esser non lassa;
<50,17,III,I> misericordia e giustizia li sdegna:
<51,17,III,I> non ragioniam di lor, ma guarda e passa.
Offline
Unless the partition where your Arch install was has been wiped or the filesystem corrupted beyond repair, there is never any need to reinstall.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Whatever tip you'll end up following, start by booting from the Arch installer. It's not only an installer, it's basically a live rescue environment.
Offline
It should be possible to add a new entry from an Administrator prompt in Windows, for example:
bcdedit /create /d "Arch" {bootmgr}
bcdedit /set guid device partition=S:
bcdedit /set guid path \EFI\Boot\bootx64.efiThe first command should return a new GUID which should be substituted in place of guid in the other commands. The last command assumes $ESP/EFI/Boot/bootx64.efi to be the boot manager for Arch; mutatis mutandis.
Jin, Jîyan, Azadî
Offline
Pages: 1