Hello, the latest working kernel on my old machine with an HDD was the 6.18. When booting with any 7-kernel, the boot process hangs between * ‘udisk mount’ and * ‘setting up network-manager’
I have a second laptop, same hardware but with an SDD instead that boots perfectly fine.
I am just sticking with the 6.18 kernel on F43 xfce. If you think I should fill a bug report, please drop me a line. Thank you for reading
Based on the available data, I cannot answer that.
But sticking forever with an old kernel is not a good idea.
Before going ahead: why are you using 6.18 rather than 6.19? Is 6.19.14 broken too? And have you already tried 7.1, which contains many fixes? What is the output of cat /proc/sys/kernel/tainted on the most recent working/booting kernel? And what is uname -r ?
First, to ensure your working kernel is not removed before installing more kernels, you might want to adjust the option installonly_limit in the file /etc/dnf/dnf.conf from 3 to 5 (please ensure that you have at least 1 GB in /boot before increasing this to 5 kernels → otherwise, let us know)
Second, you can try the current 7.1 with the following:
dnf update https://kojipkgs.fedoraproject.org//packages/kernel/7.1.2/200.fc44/x86_64/kernel-7.1.2-200.fc44.x86_64.rpm \
https://kojipkgs.fedoraproject.org//packages/kernel/7.1.2/200.fc44/x86_64/kernel-core-7.1.2-200.fc44.x86_64.rpm \
https://kojipkgs.fedoraproject.org//packages/kernel/7.1.2/200.fc44/x86_64/kernel-modules-7.1.2-200.fc44.x86_64.rpm \
https://kojipkgs.fedoraproject.org//packages/kernel/7.1.2/200.fc44/x86_64/kernel-modules-core-7.1.2-200.fc44.x86_64.rpm \
https://kojipkgs.fedoraproject.org//packages/kernel/7.1.2/200.fc44/x86_64/kernel-modules-extra-7.1.2-200.fc44.x86_64.rpm \
https://kojipkgs.fedoraproject.org//packages/kernel/7.1.2/200.fc44/x86_64/kernel-modules-extra-matched-7.1.2-200.fc44.x86_64.rpm \
https://kojipkgs.fedoraproject.org//packages/kernel/7.1.2/200.fc44/x86_64/kernel-modules-internal-7.1.2-200.fc44.x86_64.rpm \
https://kojipkgs.fedoraproject.org//packages/kernel/7.1.2/200.fc44/x86_64/kernel-selftests-internal-7.1.2-200.fc44.x86_64.rpm \
https://kojipkgs.fedoraproject.org//packages/kernel/7.1.2/200.fc44/x86_64/kernel-tools-7.1.2-200.fc44.x86_64.rpm \
https://kojipkgs.fedoraproject.org//packages/kernel/7.1.2/200.fc44/x86_64/kernel-tools-libs-7.1.2-200.fc44.x86_64.rpm \
https://kojipkgs.fedoraproject.org//packages/kernel/7.1.2/200.fc44/x86_64/libperf-7.1.2-200.fc44.x86_64.rpm \
https://kojipkgs.fedoraproject.org//packages/kernel/7.1.2/200.fc44/x86_64/perf-7.1.2-200.fc44.x86_64.rpm \
https://kojipkgs.fedoraproject.org//packages/kernel/7.1.2/200.fc44/x86_64/python3-kernel-tools-7.1.2-200.fc44.x86_64.rpm \
https://kojipkgs.fedoraproject.org//packages/kernel/7.1.2/200.fc44/x86_64/python3-perf-7.1.2-200.fc44.x86_64.rpm \
https://kojipkgs.fedoraproject.org//packages/kernel/7.1.2/200.fc44/x86_64/rtla-7.1.2-200.fc44.x86_64.rpm \
https://kojipkgs.fedoraproject.org//packages/kernel/7.1.2/200.fc44/x86_64/rv-7.1.2-200.fc44.x86_64.rpm
→ the “update” leads dnf to automatically ignore packages that you do not need (I expect it will ignore several of them in your case).
While this kernel is already in use by many people (including me) and should work fine, it is formally still testing, so as usual with testing stuff, it is a good practice to maintain backups (which you should do anyway when you play with kernels that are broken on your system)
If 7.1.2 is also broken, please do the following in the exact order:
sudo journalctl --boot=-1 -k --no-hostname → maybe this contains a log of 7.n, maybe of 6.n, but provide it in both cases.Hello Chris, thank you for helping here. I just upgraded to 7.0.14-101 and it boots flawlessly 
. Cheers