Update-grub does not update main grub entry

[Fabby]

@Stanzer

'/boot/vmlinuz-5.6-x86_64'

is an EOL kernel and doesn’t exist on your system any more:

@Stanzer

Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.7-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.7-x86_64.img
Found initrd fallback image: /boot/initramfs-5.7-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.4-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.7-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.7-x86_64.img
Found initrd fallback image: /boot/initramfs-5.7-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.4-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
Found Ubuntu 20.04 LTS (20.04) on /dev/sda1
Found Windows 10 on /dev/sdb1
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

So I expected the 5.7 kernel still to work and the update-grub there to fix the problem.

Go here for further help:

[Fix] Can’t login - black screen & chroot guide

Original author on old forum @AlManja If you are stuck and you can’t log into your system, use one of these steps below. They are sorted from easiest at the top. Start with the first step and if it doesn’t work, try with the next one and so on… Once you get access to the system, then proceed with updating the system or installing/removing packages, checking log files… Steps (you only need one) are: log to tty terminal boot without X chroot auto (with manjaro-chroot) chroot (with manjaro-chro…

Start at #3: manjaro-chroot - auto