Axios I got back to my system by pressing f1 at boot then selecting solus-current-5.13.4-189.conf takes longer to boot
Dunno will backup sometime Updates says system is up to date
I have had a similar problem for a few months now. I switched from linux-ltsto linux-current and no matter what I do my laptop always tries to boot into the linux-lts. This has been a consistent issue. The only way I have found to fix it has been to hit space immediately at boot in order to manually select the most recent linux-current kernel.
I did not see anyone state the most direct fix.. run clr-boot-manager update when you are using the kernel you want to run. That should fix everything.
It isn't working for me and this seems similar to my issue.
clr-boot-manager list-kernels will show all installed on a device. Currently this readout for me looks like:
* com.solus-project.current.5.13.12-193
com.solus-project.current.5.13.6-190
com.solus-project.lts.4.14.241-177
I believe the * indicates the currently selected kernel. There is a problem though because running uname -r gives me the following results:
There is some kind of a mismatch somewhere. However I haven't been able to work out what the problem is for some months now. Please let me know if this solution does anything for you.
On an unrelated note.. one of the very few times I ever broke Solus so bad I almost couldn't fix it was due to a theme that was broken. I know it sounds like it isn't a big deal but it can have horrible effects on your system. Personally I would advise you to make one of the most urgent tasks you accomplish removing the broken themes or icons you encountered. A broken theme or icon set can prevent your system from even booting up at all.
I would do these steps in this order:
- Remove the broken theme/icon set until your results of
sudo eopkg check return without error.
- SHUTDOWN your system. Then REBOOT your System.
- Tap SPACE to force the kernel selection upon boot. Choose the most recent kernel (or the most recent you are able to successfully log in to).
- When you have rebooted into your system, run
uname -r and ensure that the kernel you selected at boot is the currently running kernel.
- Then type
clr-boot-manager update
- SHUTDOWN. Then REBOOT. Do not press the SPACE key.
- Once your device has successfully restarted run
uname -r in a console to ensure the kernel you selected with clr-boot-manager update is the one that is currently running.
The order I laid out for you is, to the best of my knowledge, the correct set of steps in the right order to fix this. I don't know why it doesn't stay fixed in my case. It may work for you. It also may not.
If it doesn't work for you, I would run sudo usysconf run -f to run system wide checks. That should run clr-boot-manager update as well.
If at any point you find that you cannot log into to Solus, I would print this Boot Rescue troubshooting article. I had to go through these steps once because I was unable to boot because of a broken theme or icon set,
The steps look complicated.. they aren't. I have never run into an issue I was unable to fix using the steps exactly as t hey are listed from the Boot Rescue troubleshooting article. I have run the same installation since March 2019.
@DataDrake do you know if this bug you mentioned was fixed and whether or not it could be causing the current problems I am facing? Also I would appreciate any feedback you might have on the troubleshooting advice I gave above to make sure it is the right advice to be giving and to help me understand the underlying issues I have more fully.
