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.
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…
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.