Video not working at boot after update/install kernel-6.0.11-300.fc37.x86_64

On 08 December 2022 ran the system update suggested by the vanilla software center in fedora 37. Turned out to be a lot longer an update that I was expecting. Then, when it was completed and rebooted there was no video out to my monitors at all…

Used the hardware restart button to restart the motherboard more than once (my main monitor is a bit sluggish and sometimes doesn’t pick up fast enough to show GRUB).
On GRUB menu I noticed I have two versions of the 6.0.9 kernels and a new 6.0.11 kernel - it was 6.0.11 kernel that it was trying to start. So, 6.0.11 was what was showing no video, this means no plymouth.

6.0.9 works though. Got some good advice from supporters on Discord and checked the boot logs using journalctl but it looks like whenever it tries to boot to the 6.0.11 kernel there are no boot logs at all. That is, when you use -b x to select a specific boot session, the only things that show up are the boot sequences from 6.0.9, can’t see anything from attempts at 6.0.11.

Next I used yum history to look at the details of that update/install from the 8th December (bear with me here, please, I am still kind of new to fedora for troubleshooting), and saw that while it installed the 6.0.11 kernel there was nothing about nvidia kernel modules in the long list of packages.

So, I am currently at the point where I want to check how to install kernel modules for that 6.0.11 and then check if it works. I have never done this for the kernel which is not currently running, (plus I actually use this machine for things other than discovering and troubleshooting problems), so it might be a bit before I do this.

In the meantime if anyone reading this is willing to offer some advice as to what else I might do, I would appreciate it.

We do not know if the upgrade completed or not. We do know that 2 copies of the 6.0.9 kernel in F36 would be unusual, so can you tell us what the grub menu displays? Probably one for F36 and one for F37 on the 6.0.9 kernel, then another for 6.0.11 on F37.

Of the 6.0.9 kernels which are you using to boot? Do both boot successfully or only one?

The problem with the 6.0.11 kernel may be solved by a reinstall of that kernel, or by additional update steps, or by something else so we need info to avoid heading down the wrong rabbit hole.

Can you tell us where the nvidia drivers were installed from? Directly from nvidia? From negativo? or the recommended install from rpmfusion?

With the system up please show us the output of inxi -Fzxx, dnf repolist, and dnf list installed *nvidia*.

There was a new update to install kernel 6.0.12-300, along with kernel modules, pipwewire and associated packages. So I ran it and now I can boot to the latest kernel again. So, I would guess this was some quirk of my installation where the 6.0.11 install did not get some or all of the necessary modules with it. I say this because when I execute yum history info against the install of the 6.0.11 there is no mention of the packages responsible for the kernel modules, but the same for this last there is. So, not exactly a smoking gun, but at least reasonable evidence I suppose. But I will post the output for Jeff V’s question anyways in the hope that it is useful.

edit 14:11-11DEC22:Had to install inxi, strangely heavy for a system tool.

By the way, thank you for the help! :slight_smile:

Output from inxi -Fzxx:

System:
Kernel: 6.0.12-300.fc37.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.38-25.fc37 Desktop: GNOME v: 43.2 tk: GTK v: 3.24.35 wm: gnome-shell
dm: GDM Distro: Fedora release 37 (Thirty Seven)
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial:
Mobo: ASUSTeK model: TUF GAMING X570-PRO (WI-FI) v: Rev X.0x
serial: UEFI: American Megatrends v: 4002
date: 06/15/2021
CPU:
Info: 16-core model: AMD Ryzen 9 5950X bits: 64 type: MT MCP arch: Zen 3
rev: 0 cache: L1: 1024 KiB L2: 8 MiB L3: 64 MiB
Speed (MHz): avg: 2274 high: 3400 min/max: 2200/5083 boost: enabled cores:
1: 2200 2: 2200 3: 2200 4: 2200 5: 2200 6: 2200 7: 2200 8: 2200 9: 2200
10: 2200 11: 2200 12: 2200 13: 2200 14: 2200 15: 2200 16: 2200 17: 2196
18: 2200 19: 2200 20: 2200 21: 2200 22: 2200 23: 2200 24: 2200 25: 2200
26: 2200 27: 2200 28: 2200 29: 3400 30: 2200 31: 3400 32: 2200
bogomips: 217197
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK
driver: vfio-pci v: N/A arch: Pascal pcie: speed: 2.5 GT/s lanes: 4
bus-ID: 04:00.0 chip-ID: 10de:1c82
Device-2: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate]
vendor: Micro-Star MSI driver: nvidia v: 520.56.06 arch: Ampere pcie:
speed: 2.5 GT/s lanes: 16 ports: active: none off: DP-1,DP-3,HDMI-A-1
empty: DP-2 bus-ID: 0a:00.0 chip-ID: 10de:2504
Device-3: Logitech Webcam C310 type: USB driver: snd-usb-audio,uvcvideo
bus-ID: 5-3.4:5 chip-ID: 046d:081b
Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 22.1.5
compositor: gnome-shell driver: X: loaded: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv
gpu: nvidia,nvidia-nvswitch display-ID: 0
Monitor-1: DP-1 model: Sceptre E24 res: 1920x1080 dpi: 92
diag: 604mm (23.8")
Monitor-2: DP-3 model: Samsung S27D850 res: 2560x1440 dpi: 109
diag: 686mm (27")
Monitor-3: HDMI-A-1 model: BenQ GW2280 res: 1920x1080 dpi: 102
diag: 546mm (21.5")
API: OpenGL v: 4.6.0 NVIDIA 520.56.06 renderer: NVIDIA GeForce RTX
3060/PCIe/SSE2 direct render: Yes
Audio:
Device-1: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK
driver: vfio-pci bus-ID: 5-3.4:5 pcie: speed: 2.5 GT/s chip-ID: 046d:081b
lanes: 4 bus-ID: 04:00.1 chip-ID: 10de:0fb9
Device-2: NVIDIA GA106 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
bus-ID: 0a:00.1 chip-ID: 10de:228e
Device-3: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
bus-ID: 0c:00.4 chip-ID: 1022:1487
Device-4: Logitech Webcam C310 type: USB driver: snd-usb-audio,uvcvideo
Device-5: C-Media CM106 Like Sound Device type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-4.1.4:15
chip-ID: 0d8c:0102
Device-6: JMTek LLC. VKSMICUSB1 type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-4.4:9 chip-ID: 0c76:120c
Sound API: ALSA v: k6.0.12-300.fc37.x86_64 running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.62 running: yes
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: speed: 5 GT/s
lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2723
IF: wlp5s0 state: down mac:
Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
pcie: speed: 5 GT/s lanes: 1 port: N/A bus-ID: 06:00.0 chip-ID: 8086:15f3
IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac:
IF-ID-1: nm-bridge01 state: down mac:
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-4:3
chip-ID: 8087:0029
Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
Local Storage: total: 6.37 TiB used: 769.66 GiB (11.8%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 2TB
size: 1.82 TiB speed: 31.6 Gb/s lanes: 4 serial: temp: 37.9 C
ID-2: /dev/sda vendor: Smart Modular Tech. model: SHGS31-1000GS-2
size: 931.51 GiB speed: 6.0 Gb/s serial:
ID-3: /dev/sdb vendor: Seagate model: ST2000VN004-2E4164 size: 1.82 TiB
speed: 6.0 Gb/s serial:
ID-4: /dev/sdc vendor: Seagate model: ST2000VN004-2E4164 size: 1.82 TiB
speed: 6.0 Gb/s serial:
Partition:
ID-1: / size: 1.82 TiB used: 524.75 GiB (28.2%) fs: btrfs dev: /dev/dm-0
mapped: luks-71373c67-f066-4a42-9d41-0a6b3fb68cee
ID-2: /boot size: 973.4 MiB used: 414.2 MiB (42.6%) fs: ext4
dev: /dev/nvme0n1p2
ID-3: /boot/efi size: 598.8 MiB used: 17.4 MiB (2.9%) fs: vfat
dev: /dev/nvme0n1p1
ID-4: /home size: 1.82 TiB used: 524.75 GiB (28.2%) fs: btrfs
dev: /dev/dm-0 mapped: luks-71373c67-f066-4a42-9d41-0a6b3fb68cee
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 49.6 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 711 Uptime: 18m Memory: 62.7 GiB used: 3.85 GiB (6.1%)
Init: systemd v: 251 target: graphical (5) default: graphical Compilers:
gcc: 12.2.1 Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 81
Shell: Bash v: 5.2.9 running-in: gnome-terminal inxi: 3.3.23

dnf repolist:

repo id repo name
WineHQ WineHQ packages
code Visual Studio Code
fedora Fedora 37 - x86_64
fedora-cisco-openh264 Fedora 37 openh264 (From Cisco) - x86_64
fedora-modular Fedora Modular 37 - x86_64
google-chrome google-chrome
phracek-PyCharm Copr repo for PyCharm owned by phracek
rpmfusion-free RPM Fusion for Fedora 37 - Free
rpmfusion-free-tainted RPM Fusion for Fedora 37 - Free tainted
rpmfusion-free-updates RPM Fusion for Fedora 37 - Free - Updates
rpmfusion-nonfree RPM Fusion for Fedora 37 - Nonfree
rpmfusion-nonfree-nvidia-driver RPM Fusion for Fedora 37 - Nonfree - NVIDIA Driver
rpmfusion-nonfree-steam RPM Fusion for Fedora 37 - Nonfree - Steam
rpmfusion-nonfree-updates RPM Fusion for Fedora 37 - Nonfree - Updates
updates Fedora 37 - x86_64 - Updates
updates-modular Fedora Modular 37 - x86_64 - Updates
virtio-win-stable virtio-win builds roughly matching what was shipped in latest RHEL

dnf list installed *nvidia*

Installed Packages
akmod-nvidia.x86_64 3:520.56.06-1.fc37 @rpmfusion-nonfree-nvidia-driver
kmod-nvidia-6.0.11-300.fc37.x86_64.x86_64 3:520.56.06-1.fc37 @@commandline
kmod-nvidia-6.0.12-300.fc37.x86_64.x86_64 3:520.56.06-1.fc37 @@commandline
kmod-nvidia-6.0.9-300.fc37.x86_64.x86_64 3:520.56.06-1.fc37 @@commandline
nvidia-gpu-firmware.noarch 20221109-144.fc37 @updates
nvidia-persistenced.x86_64 3:520.56.06-1.fc37 @rpmfusion-nonfree-nvidia-driver
nvidia-settings.x86_64 3:520.56.06-1.fc37 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia.x86_64 3:520.56.06-1.fc37 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda.x86_64 3:520.56.06-1.fc37 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda-libs.i686 3:520.56.06-1.fc37 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda-libs.x86_64 3:520.56.06-1.fc37 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-kmodsrc.x86_64 3:520.56.06-1.fc37 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-libs.i686 3:520.56.06-1.fc37 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-libs.x86_64 3:520.56.06-1.fc37 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-power.x86_64 3:520.56.06-1.fc37 @rpmfusion-nonfree-nvidia-driver

And spoke too soon. I think there is still an issue. I will be trying the suggestions from https://discussion.fedoraproject.org/t/system-update-do-not-run-dracut-f-and-so-breaks-plymnouth-every-time/77590 to see if it helps.

In your case I wonder if it may have something to do with the fact you have 2 very different nvidia GPUs.
The 1050 Ti and the 3050 are much different in design and it seems possible that since the 1050 is seen first the firmware and drivers react differently.

BTW,
Please when possible post the output of commands as preformatted text using the </> button on the tool bar above your input screen.

The first below is what you posted and the second is mine using the </> text tags.
There is a significant difference in readability

dnf repolist:
repo id repo name
WineHQ WineHQ packages
code Visual Studio Code
fedora Fedora 37 - x86_64
fedora-cisco-openh264 Fedora 37 openh264 (From Cisco) - x86_64
fedora-modular Fedora Modular 37 - x86_64
google-chrome google-chrome
phracek-PyCharm Copr repo for PyCharm owned by phracek
rpmfusion-free RPM Fusion for Fedora 37 - Free
rpmfusion-free-tainted RPM Fusion for Fedora 37 - Free tainted
rpmfusion-free-updates RPM Fusion for Fedora 37 - Free - Updates
rpmfusion-nonfree RPM Fusion for Fedora 37 - Nonfree
rpmfusion-nonfree-nvidia-driver RPM Fusion for Fedora 37 - Nonfree - NVIDIA Driver
rpmfusion-nonfree-steam RPM Fusion for Fedora 37 - Nonfree - Steam
rpmfusion-nonfree-updates RPM Fusion for Fedora 37 - Nonfree - Updates
updates Fedora 37 - x86_64 - Updates
updates-modular Fedora Modular 37 - x86_64 - Updates
virtio-win-stable virtio-win builds roughly matching what was shipped in latest RHEL
$ dnf repolist
repo id                                                                repo name
PlexRepo                                                               PlexRepo
WineHQ                                                                 WineHQ packages
code                                                                   Visual Studio Code
copr:copr.fedorainfracloud.org:alanfla:mintstick                       Copr repo for mintstick owned by alanfla
fedora                                                                 Fedora 37 - x86_64
fedora-cisco-openh264                                                  Fedora 37 openh264 (From Cisco) - x86_64
google-chrome                                                          google-chrome
google-earth-pro                                                       google-earth-pro
phracek-PyCharm                                                        Copr repo for PyCharm owned by phracek
rpmfusion-free                                                         RPM Fusion for Fedora 37 - Free
rpmfusion-free-tainted                                                 RPM Fusion for Fedora 37 - Free tainted
rpmfusion-free-updates                                                 RPM Fusion for Fedora 37 - Free - Updates
rpmfusion-nonfree                                                      RPM Fusion for Fedora 37 - Nonfree
rpmfusion-nonfree-steam                                                RPM Fusion for Fedora 37 - Nonfree - Steam
rpmfusion-nonfree-updates                                              RPM Fusion for Fedora 37 - Nonfree - Updates

Can’t do anything with this. I can say that when I installed Fedora from scratch the machine had no major hangups. Then I black listed the 1050 Ti so that I could use it for GPU passthrough. But that was a older card, then I upgraded to the 3060. I don’t remember how, I followed one of the more popular tutorials for that subject.
In any case, right now, all of my kernel images are yeilding no-video on attempt to boot. I know the machine is still able to get a system up though. When I edit the grub commands at the menu I can see system outputs and see usb device messages. But I can’t actually log in or unlock LUKS…

edited 12 minutes later… Thanks to Jeff! – I did some digging and found a problem thread where someone was saying that the option nvidia-drm.modeset=1 can result in GPU’s being accessed prior to other configurations being executed. So I changed that from …=1 to …=0. And I am able to get into my system. That would seem to bear out that whatever configurations I did previously to blacklist the 1050 is obviously not working now. Strange that I can get the plymouth theme as I restart the machine though, even when I normally get no video. So, now I expect I need to see why that card i no longer being blacklist. And now that I think about it, I had a 10 series card when I first installed fedora 35. Had the new one for 3 or four months now, but still, the incompatible GPU angle makes sense…So thanks again.

I just scanned the inxi output again and see that the listed driver for the 1050 is vfio-pci which may indicate it is still configured for pass-thru to the VM, but I have no experience with that. The 3060 does show the nvidia driver and following graphics info indicates the 3060 is the one that is active.

Sure, but that was before the 6.0.9 image got recompiled, I believe. Since changing the nomodeset to =0 gets me in, I have to wonder if that is the only real problem. So, I expect I will be researching this and seeing if I can restore normal booting…

Incidentally, anyone know if yum tracks when the last time a file was changed by a update/install action? I think that since most of the tutorials for gpu passthrough have a distinct lack of a modeset=1 that that means the default grub file might have been ‘updated’ by recent updates…

(Beginning ti wish I had tried Silverblue now…)

For most files, you can use rpm -q --file <path-to-filename> to query what package a particular file belongs to. Then rpm -q --last <package-name> should tell you when that package was last installed/updated. Some configuration files, however, are dynamically generated and may not be listed as belonging to a particular package. The /boot/loader/entries files are dynamically generated from the %post scripts in the kernel-core package.

It seems my issues may be solved. Ceck out this other thread if you are interested:

https://discussion.fedoraproject.org/t/system-update-do-not-run-dracut-f-and-so-breaks-plymnouth-every-time/77590/10

Thanks again for all the help!