5.17.11-301.fsync.fc36.x86_64 not booting

Ask Fedora Ask in English
, , ,
1

My kernel was updated to 5.17.11-301.fsync.fc36.x86_64 and it is unable to boot on this kernel. It just boots to a black screen. I am able to boot from 5.17.9-302.fsync.fc36.x86_64 with no issues. Is there a safe way to get rid of 5.17.11-301.fsync.fc36.x86_64?

Operating System: Fedora Linux 36
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.17.9-302.fsync.fc36.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: AMD Radeon RX 6600 XT

1 Like
2

Sorry—where are you getting these kernels from? The kernels released to users to not include fsync in them as far as I know:

$ rpm -qa kernel\*
kernel-srpm-macros-1.0-14.fc36.noarch
kernel-core-5.17.6-300.fc36.x86_64
kernel-modules-5.17.6-300.fc36.x86_64
kernel-5.17.6-300.fc36.x86_64
kernel-modules-extra-5.17.6-300.fc36.x86_64
kernel-core-5.17.8-300.fc36.x86_64
kernel-modules-5.17.8-300.fc36.x86_64
kernel-5.17.8-300.fc36.x86_64
kernel-modules-extra-5.17.8-300.fc36.x86_64
kernel-headers-5.17.11-300.fc36.x86_64
kernel-core-5.17.11-300.fc36.x86_64
kernel-modules-5.17.11-300.fc36.x86_64
kernel-5.17.11-300.fc36.x86_64
kernel-modules-extra-5.17.11-300.fc36.x86_64

$ uname -r
5.17.11-300.fc36.x86_64
1 Like
3

its a gaming focused kernel - sentry/kernel-fsync Copr

So far not had any issues, until the last update

1 Like
4 
sudo dnf remove kernel-5.17.11-301.fsync.fc36.x86_64
1 Like
5

You’ll probably need to report this to the folks maintaining the fsync kernel, since it isn’t the Fedora kernel (the issue could also be occurring in the Fedora kernel, but one will have to test that out to confirm). The COPR page asks to file issues here:

https://pagure.io/kernel-fsync/issues

1 Like
6

sudo dnf remove 5.17.11-301.fsync.fc36.x86_64
No match for argument: 5.17.11-301.fsync.fc36.x86_64
No packages marked for removal.
Dependencies resolved.
Nothing to do.
Complete!

rpm -qa kernel* | grep ‘5.17.11-301’
kernel-core-5.17.11-301.fsync.fc36.x86_64
kernel-modules-5.17.11-301.fsync.fc36.x86_64
kernel-devel-5.17.11-301.fsync.fc36.x86_64
kernel-devel-matched-5.17.11-301.fsync.fc36.x86_64
kernel-5.17.11-301.fsync.fc36.x86_64
kernel-modules-extra-5.17.11-301.fsync.fc36.x86_64
kernel-headers-5.17.11-301.fsync.fc36.x86_64

7

sudo dnf remove kernel-5.17.11-301.fsync.fc36.x86_64

8

yes of course, in my command above I forgot “kernel”. Sorry. Let me fix that.

1 Like
9

Followed your advice and this pretty old thread:

sudo dnf remove kernel-5.17.11-301.fsync.fc36.x86_64
sudo grubby --default-index
sudo grubby --remove-kernel=0
sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

1 Like
10

So I checked where the issue was and it seems it cannot boot past:
“amdgpu: Topology: Add CPU node”

Tried to update to 5.17.12-301.fsync.fc36 and same issue. Any ideas?

11

you need to talk to the guys that cherry-pick the patches. Fedora’s 5.17.11 does not seem to have the issue.

1 Like
12

I also tried another kernel, Xanmod, and I am getting the same problem. Maybe the problem is my side.

I notified them, but I suspect something is wrong my side. Maybe a reinstall will fix it.

13

and the “regular” kernel-5.17.11 as Fedora releases it, just boots fine?
Install that from the repo and give it a try. If it boots, you have a problem with one of those ninja patches and you would have to file an issue with the COPR maintainers. If it doesn’t boot file a bug against kernel on Fedora’s bugzilla…

That would exaggerated, in my opinion. Older kernel boot just fine, right?

Just an idea, start up a virtual machine and see if the custom kernel boots there…

1 Like