Recent update switched to LTS kernel, boot fails, manual steps required.
- Edited
DataDrake Update for eopkg or the Software Center
Run sudo clr-boot-manager list-kernels to get a list of the available kernels.
Run sudo clr-boot-manager set-kernel <line from kernel list> to set a default kernel (no <> symbols)
Run sudo clr-boot-manager list-kernels to check for the * next to the kernel you selected.
(Optional) Run sudo clr-boot-manager update and sudo clr-boot-manager list-kernels to verify that it did not change after you set it.
Note: sudo clr-boot-manager update will always select the highest kernel release number from the same series (e.g. current-5.6.18-155 instead of current-5.6.13-153, but not lts-4.9.227-160).
(Optional) Reboot to confirm that it indeed loaded the entry you selected.
Step 5 seems to fail on my side, with the following error message :
[ERROR] cbm (../src/bootman/update.c:L189): Cannot determine the currently running kernel
I did all the previous steps but there already was a * next to the most recent kernel... Gotta warn that I had to chroot in order to reach a state in which I could run sudo eopkg up without getting an error message. I already updated everything and did all necessary steps from the solus boot rescue but for this kernel problem it seems ineffective !
EDIT : After like the tenth reboot it suddenly started working again, so sorry for the inconvenience, you can safely ignore my post
Yikes. So tossing my hat into the ring. Dell Latitude E5470 has exact same error after the last update. No boot. Not able to enter anything on the blinking cursor.
Most I can gather is "failed initialize dm devices" and a "handling fault" of some sort before hard shutdown required. Is this fixable? Makes at least the 3rd update that hosed this laptop. I thought I am fairly certain I was already running LTS Kernel because previously it wouldn't boot with the latest kernel but that was months ago.
- Edited
colorado_chris I think I have the same issue as you. I was running the LTS Kernel for the longest time, because the current would always give me a black screen forcing me to restart. This time around the LTS gives me the white cursor, while the current gives me the black screen. Tried pressing F11 on boot and trying all the possible entries. No dice.
Any way I could possibly debug this even? I get no error mesages or anything 
Edit: Seems I can login into the shell (CTRL+ALT+ one of the F keys) on both LTS and current. Anything I can do here to figure out what's going wrong?
- Edited
GueGuerreiro There has been an update since yesterday that addressed and fixed this. I would recommend when you boot, if you can drop into a TTY and then run a sudo eopkg up command and reboot and hopefully fingers crossed, you should be back in working order, at least with your LTS kernel.
Scotty-Trees I'm afraid not, I had all updates since yesterday before I shut off my laptop for the night (the .conf update that was pushed later is the last one I had installed).
I've been trying to get it to run on the Current kernel for a while now. Tried installing linux-current, nvidia-glx-driver-current, adding nomodeset to boot (I believe I had that before when installing solus for the first time, many years ago. Unfortunately the forum post I used to troubleshoot my issue was on the old domain and has since been lost). Then I tried restarting lightdm. Blank blinking cursor. Tried rebooting several times, and selecting every available entry, but still no dice.
I saw someone on reddit mentioning they ran systemctl --failed to get a list of failed services, so I tried that and I get failed on lightdm.service and vboxdrv.service (on the 5.0 current kernel. Running this on 5.6 gives me a lot more, and it seems my ethernet nor my external keyboard are working on that one, so I gave up on that version for the time being).
Seeing the Virtual Box service fail there led me to believe that it could be the issue linked above, but I'm already on the latest Vbox version and I removed virtualbox-guest-common. Also installed virtualbox-current, but the service still fails.
Not sure what I can try next :/
Sorry for the bad formatting in parts, or some typos that might be there, I'm having to type all this on mobile
Chrym Try installing virtualbox-current. I noticed that one exists too.
- Edited
GueGuerreiro
Indeed. There is a version for LTS kernel and the "current" kernel as explained here:
https://getsol.us/articles/software/virtualbox/en/
I did a rollback and it's currently working as before. So some other package was causing issues (possibly with lightdm). I'll try to look into this further when I have some extra time, but I wasted enough time as it is trying to get it to work, and I'll need this laptop working tomorrow for work.
InFamousM All I know so far is that you will need to boot a Solus .ISO and mount your hard drive to be able to update the broken files.
- Edited
SuperJC710e Hello. Were you able to fix this?
Trying the directions to mount EFI and my OS boot sector here https://getsol.us/articles/troubleshooting/boot-rescue/en/
but having no luck. "unknown filesystem type 'LVM2_member' message after mounting to the /target dir.
Updates have become very problematic with this OS to the point that I am no longer saving any files on local disk. Chances are you will lose that data after a simple update. Needs to be addressed.
GueGuerreiro thx, didn't notice that normal one is LTS.
sudo eopkg search virtualbox
Passwort:
minikube-dbginfo - Debug symbols for minikube
minikube - Kubernetes development environment
virtualbox - VirtualBox host modules for the linux-lts kernel
virtualbox-common - Common components for VirtualBox host packages
virtualbox-guest-common - Common components for the VirtualBox guest packages
virtualbox-guest - VirtualBox guest additions for the linux-lts kernel
virtualbox-32bit-dbginfo - 32-bit debug symbols for virtualbox
virtualbox-dbginfo - Debug symbols for virtualbox
virtualbox-devel - Development components for VirtualBox
virtualbox-current - VirtualBox host modules for the linux-current kernel
it even is described as LTS Version
DataDrake Chrym I am not in front of my computer but virtualbox comes with 4.9 kernel modules (LTS) so it doesn't seem odd to me.
If you are running the current kernel you have to install virtualbox-current as explained in the documentation.
https://getsol.us/articles/software/virtualbox/en/#solus-as-host
DataDrake Indeed. It currently follows the same naming convention as the other drivers so if we change this for vbox, we'll probably want to do it for the other packages to be consistent.
@DataDrake i tried your suggestions, but when i boot the LTS kernel i still only get a blinking cursor. Current kernel boots fine, but i cannot use it as it is still lagging as hell and freezes completely after some time on the XPS 9560.
The blinking cursor issue was also there a couple of updates ago 
Anything else i can try?
pappkamerad I think there was a regression with the LTS kernel on some newer hardware. We are all waiting on upstream to release a new version. I'll be creating a post shortly to get some feedback around LTS.