You are not logged in.
Pages: 1
Hello.
Today I was unable to boot my Arch because it didn't mount my /boot partition (it's also my EFI partition) due to "vfat" module bug. I recognized that GRUB loaded different kernel image (4.10.6-1) than the installed one (4.10.13-1, results of commands "uname -a" and "pacman -Q linux" were different). So I downgraded the linux package and system booted correctly. After that, I decided to update my system again and check if my vmlinuz-image would be correctly replaced. Everything went ok, I had an up-to-date image on my EFI partition (/boot). However GRUB was still loading an old kernel. What's more, I didn't perform today any Linux update so I don't know what causes this problem. It occured just after my Windows Update and firstly I thought that it had locked EFI some way but it was impossible because I had an access to the boot partition after downgrading kernel. Do you have any idea how to correctly update the kernel?
Last edited by kadev (2017-05-14 16:28:53)
Offline
Welcome to the arch linux forums kadev. Examine the grub entry and find the location of the old kernel.
Offline
Mod note: not a kernel/hardware issue, moving to NC.
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
Reinstall grub with your ESP mounted to /boot; I bet you see no grub directory under /boot (not /boot/EFI/grub, but /boot/grub); if you umount /boot you should see it and the old set of kernel it is loading.
Offline
Pages: 1