Thanks for these good news.
I am wondering: to update my machine from 6.1.x to 6.2.11 using the Fedora regular update procedure, will I go straight to that working kernel version without passing through the earlier ones?
Tnx
sudo dnf upgrade without the -y parameter gives you the possability to see what gets installed and which kernel verson gets deinstalled. Pressing n will interrupt update if you don’t want to do it.
Thanks for reminding me to check it out before hitting “y”…
The only kernel that gets installed with dnf upgrade is the latest one in the repos. None of the older releases will even be available for installation.
2 Likes
I had the same problem; but replacing for the propietary drivers for NVIDIA cards the boot process work fine again.
Note the kernel needs de nvidia module to work.
This work for me:
$ sudo dracut --force /boot/initramfs-$(uname -r).img $(uname -r)
Or replace (uname -r) with the option that you need
$ ls /lib/modules
Thanks for your suggestions, I will keep in mind in case the new Kernel won’t solve the problem for me.
Yes thank you, I verified the installation list before actually doing it and it says it will remove my 6.1.x kernel so, to be sure 100% I will finish my work project and then I will upgrade it.
You might pin the current 6.1 kernel by making an entry into /etc/dnf/dnf.conf for that purpose.
A better choice might be to remove any kernels of the 6.2 version before doing the upgrade so you have less than 3 kernels installed when you do the upgrade and the upgrade will then not remove the 6.1.x kernel.
dnf remove 'kernel*6.2.*' would accomplish that.
My concern is about this one (kernel-longterm-devel x86_64 6.1.24-200.fc37 @copr:copr.fedorainfracloud.org:kwizart:kernel-longterm-6.1) which this procedure output asks me to delete too…
It is from a different repository. And if it say it removes a 6.1.x kernel it will be a older one from the LTS, so do not worry to much.
And as @gnwiii mentinoed if you try to update to F38 the LTS you use should be available there too.
I found a solution for the problem. I do not have the probleme anymore and that’s different from you’r solution. Thanks all.
Could you elaborate please? So that maybe I can learn something new… Tnx
Not just you – the whole community benefits from broader understanding of solutions.
I thought it was obvious and implicit… sorry
Before doing the update I changed the install limit to keep my 6.1.18 too, because I didn’t tried yet the LTS one, just to have a life ring… then I updated to the last 37 update for now.
Basically, with the Fedora 37 last update, even the very last 6.2.x kernel is causing the same issue…
The machine stops working during the initial boot phase, and there is no possibility to do anything except powering off and restarting awaiting for the grub to show up.
So I made the LTS as default by grubby.
Would try later to upgrade to 38 to see what will happen next.
I seem to have a similar problem. kernel 6.0.15-300.fc37.x86_64 is working fine. However, any of the 6.2.x kernels are having problems. Looks to me like the only real errors I get are with the “nouveau” driver. Logs from journalctl -b -1 show:
kernel: nouveau 0000:02:00.0: DRM: [DRM/00000005:sor-0002-0384] [ACQUIRE proto:TMDS head:1 hdmi:1 max_ac_packet:6 rekey:56 scdc:0 hda:0] or:0 link:0 (ret:22)
kernel: nouveau 0000:02:00.0: disp: ERROR 3 [RESERVED_METHOD] 00 [] chid 0 mthd 05c0 data 00000202
kernel: nouveau 0000:02:00.0: disp: ERROR 5 [INVALID_STATE] 05 [] chid 0 mthd 0080 data 00000202
inxi -Fzxx shows my graphics to be:
Graphics:
Device-1: NVIDIA G96CGL [Quadro FX 580] driver: nouveau v: kernel
arch: Tesla pcie: speed: 2.5 GT/s lanes: 16 ports: active: DP-1,DP-2
empty: DVI-I-1 bus-ID: 02:00.0 chip-ID: 10de:0659 temp: 59.0 C
Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 22.1.9
compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
dri: nouveau gpu: nouveau display-ID: 0
Monitor-1: DP-1 model: HP 2709 res: 1920x1080 dpi: 81 diag: 690mm (27.2")
Monitor-2: DP-2 model: U27I res: 1920x1080 dpi: 81 diag: 685mm (27")
API: OpenGL v: 3.3 Mesa 23.0.3 renderer: NV96 direct-render: Yes
Any suggestions? I’m not sure if I need to try and somehow rebuild the nVidia module or something. I think it’s a pretty old nvidia card, so wondering if maybe I’m just going to have to get a new video card.
I did check out the good boot with the 6.0.15 kernel and don’t see any nouveau errors.
The issue seems that the old nvidia card with nouveau and the newer kernels does not play well, especially when wayland is used. You might be able to use the nvidia driver from rpmfusion but would be stuck with using the 470xx driver and xorg only.
If the budget allows I would suggest that you upgrade the GPU to something like the GTX 1660 or newer so you can use the latest nvidia drivers and also support using wayland. Even better would be something in the RTX 2050 or so range with little difference in price.
Just saw this here by accident, but would you mind just reporting such bugs to the nouveau project and ask people knowledgeable first before handing out tips?
There is no need to buy a new GPU, it’s merely a regression inside the nouveau kernel driver and I’d be grateful if such issues get reported timely. Luckily this issue got reported by somebody else already and we are trying to figure things out, but the more reports we get, the higher priority fixing a specific bug will become.
Anyway, to get around this error users can use a different type of display connector besides HDMI until we’ll fix the bug upstream.
I think I have reproduced this bug on a Quadro FX 1800 on Ubuntu as well. I’d like to report it in the right place. Can you send a link for searching for open bugs related to this in the nouveau project and how to report a bug? I googled it and found this:
https://www.reddit.com/r/linuxquestions/comments/s411te/where_do_i_report_a_nouveau_bug/
Which suggests to report it to Ubuntu not to Nouveau.
It’s not hard to find the bug tracker from that reddit link. Is this it?
From there I can’t seem to search for issues referencing Quadro or Quadro FX effectively. Should I just create a new bug report without a thorough search?
Ubuntu is worse… I have no idea how to report bugs to ubuntu.