Hi everybody,
I have been getting this screen (see below) at boot-up for a few weeks now and do not quite understand why it started appearing or how to remove it?
Clear Linux: 33510
I believe clr-boot-manager has a subcommand to set timeout.
^^^
sudo clr-boot-manager set-timeout 10
1 Like
I apologise for the long quite, work has been hectic! I tried to use clr-boot-manager and it did not remove the screen.
However, I have uncovered something else that is worrying; the kernel number is frozen at 5.6.10 (uname and boot-screen) even after numerous OS updates, see the below:
uname -a
Linux lusi 5.6.10-947.native #1 SMP Sat May 2 11:03:57 PDT 2020 x86_64 GNU/Linux
swupd info
Distribution: Clear Linux OS
Installed version: 33620
clr-boot-manager list-kernels
- org.clearlinux.native.5.7.15-977
org.clearlinux.native.5.6.10-947
org.clearlinux.iot-lts2018-sos.4.19.128-109
org.clearlinux.iot-lts2018-sos.4.19.120-108
Even though I set the active kernel to 5.7.* it remains at 5.6.10*
run sudo clr-boot-manager update to check whether it removes the old kernel.
It did not have an effect it seems…
sudo clr-boot-manager update
sudo clr-boot-manager list-kernels
- org.clearlinux.native.5.7.15-977
org.clearlinux.native.5.6.10-947
org.clearlinux.iot-lts2018-sos.4.19.128-109
org.clearlinux.iot-lts2018-sos.4.19.120-108
uname -a
Linux lusi 5.6.10-947.native #1 SMP Sat May 2 11:03:57 PDT 2020 x86_64 GNU/Linux
have you set the timeout?
what if you manually choose the latest kernel when booting?
Yes, I set the timeout to 0… it did not remove it however.
At boot, the only kernel option available is the old 5.6.10* (seen on original screenshot/post)…
you may need to manually mount the boot partition and check what’s in there.
do you happen to have multiple boot partitions used by other OS?
I will try that suggestion and see what I get…
No, I am only running Clear Linux… I only have multiple environments
what do you mean by multiple environments?
Desktop environments/Window managers; I use GNOME and SWAY
I experimented with KDE, i3, awesome, dwm but removed them
Have you tried XFCE already ?
Unless you actually need it, I would remove the iot-lts2018 kernel:
sudo swupd bundle-remove kernel-iot-lts2018-sos
…then run sudo clr-boot-manager update again. You might also need to remove the vmlinux image(s) for it from /usr/lib/kernel.
@doct0rHu I tried to ‘direct’ the bootloader via BIOS (don’t know if that’s what you meant) but only found that it listed the 5.6…
@Businux Not on this machine/installation… But I’ve advised my brother to, who’s currently using it
@btwarden I removed it, but then I may have gotten excited with the removing and removed some essential stuff that broke the laptop keyboard and touchpad functionality somehow…
In case you haven’t already:
sudo swupd repair
I did, and even tried the "Fix a broken installation’ method here. That did not help, I eventually decided to reinstall afresh.
So I am replying from a fresh install right now, though I wished I could have been able to fix it instead of starting over. Thank you.