F5F Stay Refreshed Software Operating Systems Switched from Intel CPUs to Ryzen now Grub appears, what should I do?

Switched from Intel CPUs to Ryzen now Grub appears, what should I do?

Switched from Intel CPUs to Ryzen now Grub appears, what should I do?

Pages (2): 1 2 Next
P
psych0builder
Member
186
05-17-2017, 06:33 PM
#1
This situation is unexpected. Initially, the system ran smoothly with an Athlon 3000 and Ubuntu 20.04 LTS. After replacing the CPU, the BIOS changed and Grub appeared correctly. However, upon restarting, the boot process repeatedly restarts to Grub. It’s a small issue but not what I anticipated. How can I resolve this?
P
psych0builder
05-17-2017, 06:33 PM #1

This situation is unexpected. Initially, the system ran smoothly with an Athlon 3000 and Ubuntu 20.04 LTS. After replacing the CPU, the BIOS changed and Grub appeared correctly. However, upon restarting, the boot process repeatedly restarts to Grub. It’s a small issue but not what I anticipated. How can I resolve this?

A
agossie
Member
156
05-18-2017, 02:43 AM
#2
I made adjustments to the text while keeping its original meaning.
A
agossie
05-18-2017, 02:43 AM #2

I made adjustments to the text while keeping its original meaning.

C
cooldude99889
Member
179
05-19-2017, 02:58 PM
#3
Does this indicate that grub isn't locating grub.cfg? Are you using a dual boot setup or multiple drives? It seems your CPU swap hasn't impacted grub functionality.
C
cooldude99889
05-19-2017, 02:58 PM #3

Does this indicate that grub isn't locating grub.cfg? Are you using a dual boot setup or multiple drives? It seems your CPU swap hasn't impacted grub functionality.

K
Kim_Namjoon
Member
62
05-19-2017, 09:23 PM
#4
It seems you suspect the system's default EFI boot configuration was altered. You may want to adjust it accordingly.
K
Kim_Namjoon
05-19-2017, 09:23 PM #4

It seems you suspect the system's default EFI boot configuration was altered. You may want to adjust it accordingly.

C
Chill159
Junior Member
5
05-24-2017, 02:37 PM
#5
Apparently nothing happened. After installing the new CPU and turning it on, the motherboard replied that a new CPU was found and reset the BIOS to its default settings. It seems I didn’t apply any overclocking or XMP profiles, and the only adjustments were disabling TPM settings, which the board doesn’t support. That’s why I was surprised.
C
Chill159
05-24-2017, 02:37 PM #5

Apparently nothing happened. After installing the new CPU and turning it on, the motherboard replied that a new CPU was found and reset the BIOS to its default settings. It seems I didn’t apply any overclocking or XMP profiles, and the only adjustments were disabling TPM settings, which the board doesn’t support. That’s why I was surprised.

G
GreenLightFabi
Senior Member
696
05-24-2017, 04:00 PM
#6
Consider updating your grub setup. The BIOS might have randomly changed drive labels, so running grub-mkconfig -o /boot/grub/grub.cfg could resolve issues.
G
GreenLightFabi
05-24-2017, 04:00 PM #6

Consider updating your grub setup. The BIOS might have randomly changed drive labels, so running grub-mkconfig -o /boot/grub/grub.cfg could resolve issues.

S
Skulldud47
Junior Member
38
05-29-2017, 03:59 AM
#7
You might resolve it by entering a chroot environment. These paths and commands seem accurate. I'm not testing on Ubuntu. Start a live ISO, run fdisk -l to identify the installation partition, then create /mnt. Enter chroot /mnt, view /etc/fstab, verify if the Fat32 partition exists. If it does, mount /dev/fat32partition to /mountpath_in_fstab. Run grub-install with the appropriate options, and if needed, mount /dev/fat32partition to /boot/EFI. Finally, configure grub-mkconfig and reboot.
S
Skulldud47
05-29-2017, 03:59 AM #7

You might resolve it by entering a chroot environment. These paths and commands seem accurate. I'm not testing on Ubuntu. Start a live ISO, run fdisk -l to identify the installation partition, then create /mnt. Enter chroot /mnt, view /etc/fstab, verify if the Fat32 partition exists. If it does, mount /dev/fat32partition to /mountpath_in_fstab. Run grub-install with the appropriate options, and if needed, mount /dev/fat32partition to /boot/EFI. Finally, configure grub-mkconfig and reboot.

F
Frosting_Ice
Member
59
05-30-2017, 12:35 AM
#8
Great! You're happy with the solution.
F
Frosting_Ice
05-30-2017, 12:35 AM #8

Great! You're happy with the solution.

R
relaxingbedo
Member
55
05-30-2017, 07:07 AM
#9
You're welcome!
R
relaxingbedo
05-30-2017, 07:07 AM #9

You're welcome!

R
ReD_T1000
Member
168
06-02-2017, 10:54 PM
#10
It indicates the system cannot locate the grub-mkconfig file.
R
ReD_T1000
06-02-2017, 10:54 PM #10

It indicates the system cannot locate the grub-mkconfig file.

Pages (2): 1 2 Next