The screen goes black and the system freezes after a successful login when using 6.2.7-200.fc37.x86_64 kernel. I do not have any issue if I choose 6.1.18-200.fc37.x86_64 during boot,
The problem appeared after I installed the system updates from last Friday.
I am using X11 with Mesa Intel® Graphics (ADL GT2) / Mesa Intel® Graphics (ADL GT2) and I do not have any nvidia driver installed.
Thank you for your reply!
I am not able to activate tty because the system freezes, nothing happens when I press ctr + alt + f2.
The same thing happens when I use wayland.
I checked and compared the output of journalctl while booting those 2 kernel versions, but I did not find any particular error. Both versions are printing similar logs.
Since you can boot you might be able to setup an ssh server on your machine, then connect to it and monitor its state and what happens when you sign in from there. Comparing the different kernels booted.
@risotto8464 Thanks again for your support.
I fixed the issue by installing the latest nvidia drivers from RPM fusion. I think there is a problem with the nouveau driver, but I cannot give more detailed information about it. All I have are the following lines logged on startup: fedora kernel: nouveau 0000:01:00.0: gr: failed to construct context fedora kernel: nouveau 0000:01:00.0: fifo:000000:0002:[gnome-shell[1453]] ectx 0[gr]: -110
I found something similar from the begining on this month [SOLVED]nouveau kernel module black screen after login & battery / Kernel & Hardware / Arch Linux Forums.
I have a similar problem with kernel 6.2.7-200. I can boot, but when I try to login the computer freezes completely.
I had to use the Grub entry to boot with 6.1.18-200
HI, same problem here:
For me the following made everything work as it should.
In /etc/default/grub edit GRUB_CMDLINE_LINUX_DEFAULT to the following GRUB_CMDLINE_LINUX_DEFAULT="intremap=off". After that run a sudo update-grub. After a reboot, everything should work fine.
That is not the proper command for a grub update on a Fedora system.
Use sudo grub2-mkconfig -o /boot/grub2/grub.cfg instead.
Fedora and Ubuntu are somewhat different in how grub is managed.
I have the same problem and I also do not have that line. Should we edit the existing line line which has GRUB_CMDLINE_LINUX="rhgb quiet" and add ,intremap=off? Or should I replace the current contents? Or should I add the GRUB_CMDLINE_LINUX_DEFAULT line above or below the existing line?
I can verify that 6.2.8-200 and 6.2.9-200 kernels both fail the same way, and 6.1.18-200 works fine.
Should we submit a bug report or has someone already reported this?
You can edit the existing command line and add that option to it. I don’t believe fedora uses the cmdline _DEFAULT entry normally, but other distros may. Note that options are separated by white space only and do not use a comma on that line.
Only remove the rhgb quiet portion if you wish to have the boot messages scroll on the screen while booting.
It would appear that you have one of the newer GPUs in that machine (RTX/Quadro series) and that you are using the nouveau (open source) drivers.
It is known that nouveau does not, as yet, support those GPUs properly. I would suspect that if you were to install the nvidia drivers from rpmfusion that the problem with the 6.2.X series of kernel would be solved.
Why not? What happens when you try dnf upgrade? This is actually what should be done as the first step.
Edit: I understand that you cannot boot into the newer kernel, but it could be installed so the drivers are built for it.
I assume you are booting to the 6.1.18 kernel. Boot to that kernel, remove the other 6.2.x kernels with dnf remove 'kernel*6.2.*' then run the upgrade dnf upgrade. This will keep your 6.1.18 kernel installed and install the newest 6.2 kernel, and can all be done before the initial reboot.
If the reboot still gives the black screen with the 6.2 kernel then boot to the 6.1.18 kernel and follow the remaining steps to install the nvidia drivers.