Gnupg GRUB problem during initial Linux setup Attempt to install Linux and encounter issues with GRUB configuration.
Gnupg GRUB problem during initial Linux setup Attempt to install Linux and encounter issues with GRUB configuration.
I am currently attempting my first Linux install on and old acer predator 15 laptop (as a start-up) gaming station for my son. I am an intermediate windows user; but have not attempted anything Linux related before; having now just learned about different distros. I likely messed up a simple item along the way, or changed something in the bios incorrectly that I cannot identify on my own. Looking for any assistance! Greatly appreciated! The story so far: Windows is installed on the primary hard drive; installing ubuntu 24.04.3 on a secondary drive; which seemed to go smooth. After install I adjusted the boot order and restarted. Upon restart the system shows the following message: Minimal BASH-like line editing supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. To Enable less(1)-like paging, "set pager=1". grub> gnu grub 2.12 I have attempted a boot repair twice, browsed help topics related to gnu GRUB 2.12 over the last 3-4 days, and even tried this guys step by step repair video related to grub ( https://www.youtube.com/watch?v=Zr9oyWjD6IA ) without any luck so far. Bios things I learned to check so far: secure boot is off. SATA is set to AHCI boot mode set to UEFI I have attached my last boot-repair log. I have screenshots of my bios windows if that also helps: https://photos.app.goo.gl/PuhLLiYcooaY5PED8 boot log dec 29 2205 736pm.txt Edited December 30, 2025 by EyeKon clarification
Apologies, I didn't specify that I attempted this. Please type 'exit' once for no change or again to confirm the boot process. I suspect a boot order adjustment may have affected detection of the Ubuntu installation. It should be on disk1, partition 2, (930gb).
cat /sys/firmware/efi/fw_platform_size. It should read 64 for a 64-bit system. If absent, the system isn’t booting in UEFI. A missing file suggests non-UEFI booting, which is problematic when memory is scarce or the firmware is flawed. To proceed safely, use gparted to locate partition paths in the upper-right corner. https://forum.manjaro.org/t/howto-chroot...tion/34071 Ensure correct partitions are mounted before moving forward. (Note: Windows partitions differ.) Skipping step 4 is optional but recommended. Remember to acquire the efivors if needed: https://unix.stackexchange.com/a/788257 After launching a terminal in the chroot environment, attempt a fresh grub installation for 64-bit: (requires root access, which you should have). Run: grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB. Success indicates completion without errors. Afterwards, regenerate the grub configuration. Ubuntu provides update-grub; it should display “Linux found” and “Windows detected.” If no errors appear, restart the system. If issues persist, explore the GRUB recovery console for troubleshooting or cleanup options. The official wiki offers general guidance, though commands may vary slightly depending on your distribution. The core idea remains consistent: follow the steps carefully to avoid conflicts from multiple boot entries.