Two days ago I updated my (dual boot Manjaro/Win10 with grub) which went a bit funny. I got some “package xxx in local is newer than extra” warnings, that I managed to reverse by changing mirrors and multiple
pacman -Sy(y)u(u) commands. So all seemed fine…
Today I am booted up my laptop again and whereas Win10 boots fine (same physical drive, different partition), booting Linux seems not exactly okay. Link to photo of boot screen:
Then I log in, run
journalctl -xb and scroll down to where I think things start going awry:
Unknown kernel command line parameters "BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64 cryptdevice=UUID=(long hexadecimals...)", will be passed to user space.
(All terminal text can contain typos, since I copied it by hand.)
Then I quite some bios errors, even a message saying
ccp (...): unable to access the device: you might be running a broken BIOS. Are these serious errors? They sure sound grave. Or can these be the result of something else?
So far, only warnings (bold text).
Then I see the first red text appearing, about clocksource:
timekeeping watchdog on CPU4: Marking clocksource 'tsc' as unstable because the skew is too large etc. etc. Then
TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'.
Then some warnings regarding cryptsetup and lvm about un-initialized urandom reads.
Then everything seems to be going fine, but then some more red text:
systemd-modules-load: Failed to find module xxx where xxx = crypto_user, sg, vbox…, uinput, …
What’s going on here??? I can see my whole hard drive using
ls, so all data is there.
Moderation note: Edited the link so nobody has to remove spaces after each letter …