Just updated to kernel 6.8.10 from Discover and couldn’t boot into the OS. Any suggestions on how to fix it?
OS: Fedora 40
DE: KDE Plasma
Kernel version: 6.8.10 (not booting)
If any more information is needed, do let me know.
1 Like
18 posts were split to a new topic: Boot waits indefinitely after kernel update to 6.8.10
sudo dmesg | grep -i failed gives:
0.256718] ACPI: _OSC evaluation for CPUs failed, trying _PDC
[ 6.688054] v4l2loopback: module verification failed: signature and/or required key missing - tainting kernel
[ 8.932398] Bluetooth: hci0: Failed to read codec capabilities (-22)
[ 27.746758] audit: type=1103 audit(1716391811.535:235): pid=6855 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='op=PAM:setcred grantors=? acct="privacyfreak" exe="/usr/lib/systemd/systemd-executor" hostname=? addr=? terminal=? res=failed'
The other 2 commands both give the following:
Specifying boot ID or boot offset has no effect, no persistent journal was found.
Will try holding the esc/ shift key in a few minutes
Doesn’t show anything 
That message was for @jakfrost. It’s a way to see the kernel messages of the system he is running since he was testing 6.8.10
Try these :
journalctl -b -1 | grep -i failed
To check the boot logs :
journalctl -b -1
- Although I already see your :
v4l2loopback: module verification failed:
signature and/or required key missing - tainting kernel
This could be the cause, so reinstalling this could be helpful and if you can sign the module (if you have SecureBoot enabled) you might need to do that.
- Might tackle this later if you get past the first.
[ 27.746758] audit: type=1103 audit(1716391811.535:235):
pid=6855 uid=0 auid=4294967295 ses=4294967295
subj=system_u:system_r:init_t:s0 msg='op=PAM:setcred grantors=?
acct="privacyfreak" exe="/usr/lib/systemd/systemd-executor" hostname=?
addr=? terminal=? res=failed'
Reinstalling what exactly?
Are you aware of how you got v4l2loopback ?
Also, please provide the output of the commands, so we can get more information to check the boot logs :
journalctl -b -1
Also, again, ‘journalctl -b -1 | grep -i failed’ and ‘journalctl -b -1’ give the following:
Specifying boot ID or boot offset has no effect, no persistent journal was found.
No, I do not remember
Same situation
Well, if you have other kernels you can boot into go ahead and you those for now. This issue could be widespread with 6.8.10.
Do you know how to boot into a different kernel using grub or grubby ?
Here is a quick guide for both grub and systemd-boot users :
Already done. Currently using 6.8.9
Still though, I would definitely prefer it this issue can be resolved because everyone else (save for one person on this forum) has had no issues with kernel version 6.8.10 so far
I certainly hope so!
I am on the said kernel and it seems to work.
I suggest to point people to this article:
Because maybe somebody doesn’t know what to do when the computer fails to boot.
Just ran sudo dmesg | grep -i failed again. This is the output:
[ 0.257843] ACPI: _OSC evaluation for CPUs failed, trying _PDC
[ 6.452808] v4l2loopback: module verification failed: signature and/or required key missing - tainting kernel
[ 8.733133] Bluetooth: hci0: Failed to read codec capabilities (-22)
[ 24.415028] audit: type=1100 audit(1716395033.144:228): pid=6855 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=? acct="privacyfreak" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=? res=failed'
[ 29.114986] audit: type=1103 audit(1716395037.852:236): pid=6865 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='op=PAM:setcred grantors=? acct="privacyfreak" exe="/usr/lib/systemd/systemd-executor" hostname=? addr=? terminal=? res=failed'
[ 394.692106] Bluetooth: hci0: Failed to read codec capabilities (-22)
[ 1306.610210] Bluetooth: hci0: Failed to read codec capabilities (-22)
[ 2450.393784] Bluetooth: hci0: Failed to read codec capabilities (-22)
[45600.546558] Bluetooth: hci0: Failed to read codec capabilities (-22)
[46873.486412] audit: type=1130 audit(1716441883.158:303): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-makecache comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[46873.590574] Bluetooth: hci0: Failed to read codec capabilities (-22)
[54098.467238] Bluetooth: hci0: Failed to read codec capabilities (-22)
[62824.748797] Bluetooth: hci0: Failed to read codec capabilities (-22)
So any concrete idea what could be causing it? The issue seems to be widespread
1 Like
As for exactly what, no. It is almost certainly the kernel update, from my POV since without the latest kernel I can boot as expected. If I can get some time on it today I may get further with it. It does seem to be affecting a number of people.
2 Likes
Removed kde, kde-plasma, wayland
Can somebody please explain what all of these terms mean? I’m a noob