Welcome NVIDIA Driver Not 100%

[chairmankam]

Hello,

Requirements:

I have Searched the forum for my issue and found nothing related or helpful
I have checked the Resources category (Resources Index)
I have reviewed the Wiki for relevant information
I have read the the Release Notes and Errata

OpenMandriva Lx version:

OpenMandriva Lx 25.06 (ROME) Rolling x86_64

Desktop environment (KDE, LXQT…):

KDE

Description of the issue (screenshots if relevant):

I ran the NVIDIA installer for my RTX 2070 Rev A (incompatible with open-source driver) from the Welcome applet. Unfortunately, it froze during the last step, which I am pretty sure was the switchover command, so I restarted. The module is installed, but not activated. My usual response would be to mess around with dnf and dnfdragora, but this is actually a nuked reinstall for me, because I was trying to correct issues with my last install where I was installing packages from dnfdragora to try and make it work better and I wound up making Steam go transparent and having to relaunch plasma every time I came back from sleep. So I am trying to be simpler and more careful. I am asking primarily for how I can run that final command manually, or perhaps identify what I am doing wrong. NVIDIA appears to be on in my grub, I attempted to blacklist nouveau. Thank you all in advance.

Relevant informations (hardware involved, software version, logs or output…):

Kernel: Linux 6.14.2-desktop-3omv2590
output of lspci -v:

29:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce RTX 2070 Rev. A] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Device 37c6
Flags: bus master, fast devsel, latency 0, IRQ 75, IOMMU group 17
Memory at fb000000 (32-bit, non-prefetchable) [size=16M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
Memory at e0000000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [size=128]
Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities:
Kernel driver in use: nouveau
Kernel modules: nouveau, nvidia_drm, nvidia

I apologize if I missed the answer somewhere. I am search-disabled.

[zeroability]

Welcome.

@chairmankam

incompatible with open-source driver

No it isn’t

GitHub - NVIDIA/open-gpu-kernel-modules: NVIDIA Linux open GPU kernel module source

Either way, we need more info:

How to get better results when posting about problems

All OpenMandriva contributors are unpaid part time volunteers. There are no employees being paid to help you. All OpenMandriva contributors have more on our “To Do” and “Want To Do” lists than we can actually do. So when someone stops what they are doing to help a user with an issue that stops progress on other work that we are doing. Because of this we won’t hesitate to ask users to do some work themselves to get an issue resolved. This means RTFM yourself and do your own internet searches. S…

@chairmankam

I apologize if I missed the answer somewhere. I am search-disabled.

The link provided was in the upper right hand corner of the main page of the forums, and fairly obvious. The nvidia open module testing is pinned.

@chairmankam

Kernel driver in use: nouveau
Kernel modules: nouveau, nvidia_drm, nvidia

If I had to guess without more info, you are using the wayland version, multiple monitors, or both simultaneously.

https://forum.openmandriva.org/search?q=nvidia

[chairmankam]

From the top: Yes it is. I looked at that exact page, used my PCIID (10DE:1F07), and it is NOT there. This version of the 2070 is literally ONE iteration too old.

No, this time I avoided Wayland. Yes, I have two monitors.

lsmod | grep nvidia:

i2c_nvidia_gpu 12288 0
i2c_ccgx_ucsi 12288 1 i2c_nvidia_gpu

I am not asking for any past-volunteering, I just know that I have missed something, and dnf reinstall does nothing. As to RTFM, I did, but I have a history of finding myself in the most complicated version of everything. I’m sure, just like last time I can brute force my way, but I am looking to see if anyone sees the obvious mistake.

[zeroability]

@chairmankam

Yes, I have two monitors.

Disconnect one, remove the driver from the terminal, reinstall the driver from the terminal, reboot, and report if the module loads and nouveau does not.

@chairmankam

I am not asking for any past-volunteering, I just know that I have missed something, and dnf reinstall does nothing

I don’t know what you mean by this.

@chairmankam

As to RTFM, I did, but I have a history of finding myself in the most complicated version of everything.

Cool, but no one here is clairvoyant and this is the first time you have posted here. We have a process and I informed you of it.

@chairmankam

I’m sure, just like last time I can brute force my way, but I am looking to see if anyone sees the obvious mistake.

Yup, and if all you have is a hammer then everything is a nail. Many of us had to figure things out with minimal help or knowledge. We hope that most people won’t have to be on an island using a distro and left to fend for themselves.

[zeroability]

@chairmankam

10DE:1F07

Finally, after Ctrl + F on the Github page you can find this:

NVIDIA GeForce RTX 2070	1F07

That is your card.

[chairmankam]

I saw that, but when I look at the format of the PCI IDs on that table, I am fairly certain that is for a different field. This is on top of the fact that during my last installation using the “open source NVIDIA modules” didn’t work. Unless I am mistaken running that command should have made the “Kernel driver in use” be nouveau, correct? Because it had showed “nvidia” from that iteration. I have not attempted to install the open source modules this time, as stated because I managed to cripple the install last time, and that 10DE is nowhere near 1F07 in the listing.

I will attempt your solutions tomorrow.

[zeroability]

@chairmankam

10DE

That is referenced for the same family Quadro card with the same die but different features. I think there are other issues beyond the open or closed driver.

@chairmankam

Unfortunately, it froze during the last step, which I am pretty sure was the switchover command, so I restarted.

Just to come back to this briefly, there isn’t a module switch as part of the install. It copies files, creates initramfs, installs nvidia’s modprobe (because they hate you) and their services, modifies grub, and ends. The reboot has to happen when the package install completes so these steps can be finished. It’s handy to have it in the Welcome app, but when it breaks we really need the output. @rugyada may know how that log is captured.

[rugyada]

@zeroability

It’s handy to have it in the Welcome app, but when it breaks we really need the output. @rugyada may know how that log is captured.

You can start om-welcome from console and look at its output while working, however in this case I’d suggest to run the ~same command OM-welcome would do from a clean console which also creates the log:

sudo dnf --refresh install nvidia --enablerepo=rolling-x86_64-non-free 2>&1 | tee nvidia-install.log.txt

Once finished close console. You will find the file nvidia-install.log.txt in your home.
Upload this log file.

[chairmankam]

Ok, I ran a combination of @zeroability 's task list and @rugyada 's instruction set, though I should point out that the repo in the command had to be modified cause I am using the modern AMD install, not the basic. The results are below:

nvidia-install.log.txt (6.1 KB)

Running lspci -v gave:

29:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce RTX 2070 Rev. A] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Device 37c6
Flags: bus master, fast devsel, latency 0, IRQ 82, IOMMU group 17
Memory at fb000000 (32-bit, non-prefetchable) [size=16M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
Memory at e0000000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [size=128]
Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
Capabilities:
Kernel driver in use: nvidia
Kernel modules: nouveau, nvidia_drm, nvidia

Now, Metro Exodus Enhanced runs!

So I guess there are two things left to check:

1. Will I need to refresh plasma when I come out of sleep this time?
2. Will Steam function properly or be stuck with invisible windows again?

Also I noticed that like my last install NVIDIA seems to run monitors darker and dim them earlier.

I really want to thank the both of you for this.

And I guess after I test that tomorrow, the final question will be should I switch to NVIDIA open instead?

[zeroability]

I believe there is a suspend service for nvidia that might be disabled by default. Mostly because the majority of people that want the nvidia made driver (open or closed) will want to game and it could impact performance.

Keep in mind, the drivers were packaged with limited testing due to the lack of hardware. We could really use feedback on if things are broken so they can be researched and possibly fixed. If you are able to go the extra bit more and talk with nvidia directly (since it’s easier to relay to them directly what your hardware is doing instead of playing the telephone game) then we can take their guidance and start to adjust things so they can work for everyone.

[rugyada]

@chairmankam

I should point out that the repo in the command had to be modified cause I am using the modern AMD install, not the basic

Command provided based on:

@chairmankam

OpenMandriva Lx 25.06 (ROME) Rolling x86_64

Glad that you managed to edit it anyway.
Next time you may want to specify your architecture znver1

Your’re welcome

[chairmankam]

Whelp. Both bugs did in fact occur. Upon waking from sleep, the lock screen was significantly slower, and then when I got in it was empty. Window bars are missing, Steam is completely unusable (yes I turned off all GPU settings in the Interface tab), items in the taskbar appeared only after being hovered over, no wallpaper, text like time and date are just gone. The computer is usable, and typing “plasma --replace &” and then after the output “Ctrl + c” and quiting the terminal remains stable.

journalctl -r yields this:

NVIDIA Sleep Log.txt (68.8 KB)

plasmashell --replace yields:

[1] 32260
 kf.plasma.quick: Applet preload policy set to 1
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:178:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth":
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:201:9
Toolbox not loading, toolbox package is either invalid or disabled.
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:178:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth":
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:201:9
Toolbox not loading, toolbox package is either invalid or disabled.
file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/main.qml:310:13: QML Image: Cannot open: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/om-start-kde
org.kde.applets.brightness: D-Bus action "KeyboardBrightnessControl" is not available at service "org.kde.Solid.PowerManagement"
qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
org.kde.pulseaudio: No object for name "alsa_output.usb-1130_USB_AUDIO-00.iec958-stereo.monitor"
file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/SwitchPanel.qml:52:5: QML TabBar: Binding loop detected for property "implicitWidth":
qrc:/qt/qml/org/kde/plasma/components/TabBar.qml:17:5
file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/SwitchPanel.qml:60:23: QML TabButton: Binding loop detected for property "implicitWidth":
qrc:/qt/qml/org/kde/plasma/components/TabButton.qml:22:5
file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/SwitchPanel.qml:60:23: QML TabButton: Binding loop detected for property "implicitWidth":
qrc:/qt/qml/org/kde/plasma/components/TabButton.qml:22:5
file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/SwitchPanel.qml:60:23: QML TabButton: Binding loop detected for property "implicitWidth":
qrc:/qt/qml/org/kde/plasma/components/TabButton.qml:22:5
file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/SwitchPanel.qml:60:23: QML TabButton: Binding loop detected for property "implicitWidth":
qrc:/qt/qml/org/kde/plasma/components/TabButton.qml:22:5
file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/SwitchPanel.qml:52:5: QML TabBar: Binding loop detected for property "implicitWidth":
qrc:/qt/qml/org/kde/plasma/components/TabBar.qml:17:5
file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/SwitchPanel.qml:60:23: QML TabButton: Binding loop detected for property "implicitWidth":
qrc:/qt/qml/org/kde/plasma/components/TabButton.qml:22:5
file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/SwitchPanel.qml:60:23: QML TabButton: Binding loop detected for property "implicitWidth":
qrc:/qt/qml/org/kde/plasma/components/TabButton.qml:22:5
file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/SwitchPanel.qml:60:23: QML TabButton: Binding loop detected for property "implicitWidth":
qrc:/qt/qml/org/kde/plasma/components/TabButton.qml:22:5
file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/SwitchPanel.qml:60:23: QML TabButton: Binding loop detected for property "implicitWidth":
qrc:/qt/qml/org/kde/plasma/components/TabButton.qml:22:5
file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/SwitchPanel.qml:60:23: QML TabButton: Binding loop detected for property "implicitWidth":
qrc:/qt/qml/org/kde/plasma/components/TabButton.qml:22:5
file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/SwitchPanel.qml:60:23: QML TabButton: Binding loop detected for property "implicitWidth":
qrc:/qt/qml/org/kde/plasma/components/TabButton.qml:22:5
file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/SwitchPanel.qml:60:23: QML TabButton: Binding loop detected for property "implicitWidth":
qrc:/qt/qml/org/kde/plasma/components/TabButton.qml:22:5
file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/SwitchPanel.qml:60:23: QML TabButton: Binding loop detected for property "implicitWidth":
qrc:/qt/qml/org/kde/plasma/components/TabButton.qml:22:5

I will forward to NVIDIA if I can figure out a point of contact.

Would you recommend I attempt to remove NVIDIA, use the install open modules command, and see if I get my RTX2070 recognized AND plasmashell stability? Otherwise I will keep working this nonsense.

Update: closing Steam windows after the --replace and opening them again fixed that error.

[zeroability]

Were you able to enable and start the suspend service for nvidia?

[chairmankam]

To be clear, you are not talking about the sleep function in the KDE settings? If yes I admit I haven’t tried that.

[zeroability]

The service names listed here:

nvidia.spec

[chairmankam]

I have enabled all of them, apparently successful.

Created symlink '/etc/systemd/system/systemd-suspend.service.wants/nvidia-suspend.service' → '/usr/lib/systemd/system/nvidia-suspend.service'.
Created symlink '/etc/systemd/system/systemd-suspend.service.wants/nvidia-resume.service' → '/usr/lib/systemd/system/nvidia-resume.service'.
Created symlink '/etc/systemd/system/systemd-hibernate.service.wants/nvidia-resume.service' → '/usr/lib/systemd/system/nvidia-resume.service'.
Created symlink '/etc/systemd/system/systemd-suspend-then-hibernate.service.wants/nvidia-resume.service' → '/usr/lib/systemd/system/nvidia-resume.service'.
Created symlink '/etc/systemd/system/multi-user.target.wants/nvidia-powerd.service' → '/usr/lib/systemd/system/nvidia-powerd.service'.
Created symlink '/etc/systemd/system/systemd-hibernate.service.wants/nvidia-hibernate.service' → '/usr/lib/systemd/system/nvidia-hibernate.service'.
Created symlink '/etc/systemd/system/systemd-suspend-then-hibernate.service.wants/nvidia-suspend-then-hibernate.service' → '/usr/lib/systemd/system/nvidia-suspend-then-hibernate.service'.

I will report back how the next sleep cycle goes.

[chairmankam]

Success! Thank you!

So since we are here, I noticed that using the default start menu applet could sometimes freeze and crash the entire system when rapidly mousing between Multimedia and Internet categories. I just switched to Application Launcher instead. Is this a known issue or?

[zeroability]

@chairmankam

So since we are here, I noticed that using the default start menu applet could sometimes freeze and crash the entire system when rapidly mousing between Multimedia and Internet categories. I just switched to Application Launcher instead. Is this a known issue or?

You may want to start a new thread for this so someone doesn’t miss it searching.

[chairmankam]

Only app I found with issues was Xemu (Flatpak). Just had to reinstall it and it worked.

[zeroability]

@zeroability

The service names listed here:

nvidia/nvidia.spec at 29c7073af3986c6c4b3cbd92292774a0800f9932 · OpenMandrivaAssociation/nvidia · GitHub

If this has resolved the suspend/wake problem, please mark it as Solution.