I’m running Fedora 37 with kernel-6.1.18-200.fc37.x86_64 and since kernel (and kernel-core) updates to 6.2 (6.2.7 / 6.2.8 / 6.2.10), when I chose a 6.2.* version in the grub boot menu, the computer freezes and does not react anymore.
I don’t understand the problem and i don’t have any errors on boot screen.
I have to start fedora with kernel 6.1.18 and that’s actually annoying…
Any ideas ? Thanks a lot…
(PC specs : Laptop HP HP ZBook Firefly 14 inch G8 Mobile Workstation PC / 11th Gen Intel® Core™ i7-1165G7 × 8 / Mesa Intel® Xe Graphics (TGL GT2) / Mesa Intel® Xe Graphics (TGL GT2))
Hi, I do have the same problem, I posted a request earlier but no answers so far.
My one year old Ryzen Desktop machine does not boot after upgrading to 6.2.x so I went back to 6.1.8.
By the way this issue happens only on my desktop, the other machines are laptops and work fine with Fedora and the 6.2.x
Could you tell me how I can get that log? I mean, something like journalctl -b -1?
I don’t upgrade the system anymore because I am afraid of not being able to go back again to 6.1.8 due to the fact that the grub shows 2 previous versions only… and I’ve already upgraded and downgraded twice…
Fedoras update process never replaces the running kernel. If you are booted into the 6.1.18 kernel when you do the update that kernel should remain and one of the newer kernel be replaced with a kernel upgrade.
The nouveau drivers are open source, reverse engineered, and do not fully (if at all) support the newer GPUs. Depending upon which GPU and kernel is installed it is quite possible that the nouveau driver may not function. Installing the nvidia driver from rpmfusion does provide support for the newer GPUs (the driver is built for each kernel when it is installed).
There are many reports of systems booting to a blank screen, which is probably a graphics problem. In such cases, you may be able to get a terminal by entering <Ctrl-Alt> N, where N=2, 3, or 4. Pressing escape when the system starts to boot may let you see kernel messages. From the grub menu you can edit the kernel command-line to remove “rhgb quiet” to see the messages.
In a terminal: man journalctl. A problem with journalctl is that the lines can be very long. On strategy is to run journalctl and scan for messages related to a problem and select a string specific to the problem. The capture those lines in a file:
$ journalctl -b N | grep string_specific_to_the_problem > string_specific_to_the_problem.txt
You then edit and annotate the file and paste into a forum post (bracketed with triple backquotes).
At the moment I went for the long term due to the fact that I am doing some important jobs and I cannot risk long debugging.
I will try to update Fedora only when my job is done and then will see.
Meanwhile I will follow this discussion becuse the problem is not solved yet
For now thanks a lot
I got the same problem on my ThinkPad T14 (2 gen) no 6.2.x kernel works for me; it’s frustrating because i cant upgrade the new release fedora 38; the usb installer not boot … my only soption in this moment is to stay on Kernel 6.1.X.
Your image truncates long text lines. When posting excerpts from journactl it is better to paste text bracketed with lines of 3 backtics.
You appear to have both i915 and Nvidea graphics. Failure of the driver for Nvidea hardware should fall back to i915 so the system still boots to a GUI. There may be more details yet to be found in journalctl.