Since a couple of weeks I can't boot through anymore. When hitting "ESC" during startup I get an EFI selector, which is by default prompting a 4.9 LTS, which just gave me a blinking cursor. When I select the current kernel then, everything works fine.
I tried all the recommended "clr-boot-manager"-stuff, but nothing helped. Still helpless.
Additionally, I found something very strange: I once inserted a SD-card into the reader. This card was bootable (but unmounted, of course), I dd'd a raspian on it, wanted to fix something and forgot about it for months. So, there was a SD-card with a /boot directory in a mountable place all the time, even during the last big SOLUS update. And now I have some SOLUS stuff on my raspbian card. There's a subfolder /EFI/com.solus-project with two initrd* and two kernel-com.*, both from July 7th, containing the LTS and the current kernel.
I'm pretty sure I hadn't copied these on my raspian card. And I'm also sure this has something to do with the boot problems.
So, is someone able to tell me where I can fix this? I tried to mount sda1 as /boot and went through the configuration files, but did not see anything strange.
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 221,6M 1 loop /snap/freecad/4
loop1 7:1 0 81,7M 1 loop /snap/core/4206
sda 8:0 0 465,8G 0 disk
├─sda1 8:1 0 488,3M 0 part
└─sda2 8:2 0 465,3G 0 part
└─luks-ac5dae26-4854-4ccf-8ee7-286f3e36a103 253:0 0 465,3G 0 crypt
├─SolusSystem-Swap 253:1 0 3,7G 0 lvm
└─SolusSystem-Root 253:2 0 461,6G 0 lvm /
sdb 8:16 0 1,8T 0 disk
└─sdb1
It would be even helpful if someone could confirm that's a bad idea to have further bootable media available during a kernel update.
Thanks,
Michael