ROME(rolling) nVidia proprietary users

[zeroability]

@Draguljche

I checked this already since that was mentioned on Mart this year.

This has been addressed for a while as part of the packaging so that VT’s work with the proprietary driver.

This was probably the most helpful information you uploaded from your original post here in July:

Plasma6 Wayland + Nvidia drivers Problem

Aaand its same. Black screen like before I mention in first place. [stefanm@Draguljche-PC ~]$ inxi -Fza System: Kernel: 6.10.0-desktop-1omv2490 arch: x86_64 bits: 64 compiler: clang v: 18.1.8 clocksource: tsc avail: hpet,acpi_pm parameters: BOOT_IMAGE=/@boot/vmlinuz-6.10.0-desktop-1omv2490 root=UUID=2c93c1c3-3480-4056-8a01-51eb7c4469f6 ro rootflags=subvol=@ nouveau.modeset=0 nvidia-drm.modeset=1 nvidia-drm.fbdev=1 quiet splash logo.nologo audit=0 rd.timeout=120 dm_mod.use_…

From it, I found this (which is more helpful than works on distro “X” or sysinfo gathered when the .run file is installed):

Jul 21 02:23:12 Draguljche-PC kwin_wayland[1269]: kwin_scene_opengl: failed to import dmabuf KWin::LinuxDmaBufV1ClientBuffer(0x563b4d91d9f0)
Jul 21 02:23:13 Draguljche-PC kwin_wayland_wrapper[1374]: EGL setup failed, disabling glamor
Jul 21 02:23:16 Draguljche-PC kwin_wayland[1269]: kwin_scene_opengl: failed to import dmabuf KWin::LinuxDmaBufV1ClientBuffer(0x563b517535d0)
Jul 21 02:23:17 Draguljche-PC kwin_wayland[1269]: kwin_scene_opengl: failed to import dmabuf KWin::LinuxDmaBufV1ClientBuffer(0x563b4d8d8cb0)
Jul 21 02:23:18 Draguljche-PC kwin_wayland[1269]: kwin_scene_opengl: failed to import dmabuf KWin::LinuxDmaBufV1ClientBuffer(0x563b51a63b70)
Jul 21 02:23:18 Draguljche-PC kwin_wayland[1269]: kwin_scene_opengl: failed to import dmabuf KWin::LinuxDmaBufV1ClientBuffer(0x563b51a63b70)

I realize the process is probably frustrating and no one likes it when their stuff doesn’t work. If you could please refrain from hijacking other posts because yours autoclosed:

Nvidia Installation

Those drivers doesnt work. They do not apply even when they install successfuly. I installed Nvidia 565.77 .run file. Followed that guide. Buuuut, that does not to be the solution, it must someone who are developer or programmer to look at that. Or try to port Drivers from Rosa Fresh Desktop in x11_backports

@ben79 worked very hard at trying to get information from you to address the issue you were having in your first post. Everyone here is volunteering their free time to this project. Please remember that.

Since I package the driver, I have made other devs aware of the issue you are having and if we can reasonably resolve it, we will try to. The nature of proprietary drivers is that the source code is closed. Wayland is also very unstable and adding nVidia proprietary drivers is always going to complicate that.

There are currently the following resolutions we can offer:

1. Use X11 and forego the eye-candy (i.e. No Transparency Blur on Kvantum themes)
2. Use the .run file and maybe have the eye-candy
3. Use a distribution that works out of the box

OM 5.0 may also work if you wanted to install that and report your findings.

One last piece of genuine advice I can give you is to ask when you don’t know how to do something. If you don’t want that immortalized on a forum, you can ask us in our Matrix chat:

You're invited to talk on Matrix

We need the right information to help properly and it will help reduce frustration while also giving you more knowledge.

[Mordechai (Morris)]

@ben79

ould appreciate reports on if this new software does/does not work

Hi Ben - I gave it a try on my AMD Ryzen 5 2600 Desktop, which has a 1660 TI.

Steps:
Install OpenMandriva (I tried both the standard x86-64 image and the custom Ryzen image from December)

Update to latest bits

Reboot Machine

Install NVIDIA 565.77-2 through the welcome App

Reboot Machine

Log back in and there was a significant lag in launching the desktop versus Nouveau driver, and once it loaded Plasma it was extremely unstable. After a minute or so, the screen went black and when it came back it was on the login screen.

I couldn’t log in as touching the keyboard caused the screen to go black again.

For the time being, I can’t use it as is on my two desktops.

Thanks for the hard work.

[zeroability]

This continues to be a known issue with the (open and proprietary) driver version and we are investigating:

KDE nvidia constant frame drops in desktop use with nvidia-dkms-open 565...

[ben79 (Ben Bullard)]

@Mordechai

Install Mandriva

Y’all need to stop this. It is OpenMandriva or OMLx or OM. Or more specifically and better if you are trying to solve a problem ROME or Rock. There was legal stuff when OpenMandriva was created and we can not afford attorneys.

[Mordechai (Morris)]

Fixed it, wasn’t aware of that.

[ben79 (Ben Bullard)]

Thanks @Mordechai. I don’t much like having to do this either. We try to moderate with a light hand unless there is spam or an abusive individual.

Edit: Might as well make this official:

Official Naming Policy

[zeroability]

If people do slip up, the trademark is no longer valid and the company that would have had claim to it went defunct in 2015.

[dutsky]

I’m sorry for asking it here, but are there any (official) guides how to install proprietary nvidia driver on ROME? Sorry, didn’t found any.

I tried to install it on fresh system (via om-welcome “install nvidia driver” tool), but after reboot i’d got nouveau and nvidia conflicting with each other, so Xserver dies after some seconds after login.

[ben79 (Ben Bullard)]

A how to that says (if and only if your hardware is supported by latest nvidia proprietary driver):

sudo dnf in nvidia

So no, there is no how to for that. In ROME that is the only proprietary nVidia driver provided. For older hardware you need to install driver from nvida.com. I do not have nVidia hardware but as far as I know if you install the OM nvida package then nouveau should be automatically blacklisted somewhere. If it isn’t then blacklist it. Google it. I can guess that you would do that in /etc/modprobe.d/dlblacklist-omv.conf and I can guess you would put blacklist nouveau.

But also be sure that the driver you installed actually works with your hardware. Again google it. I can say you find that somewhere at nVidia’s website.

Edit: Changed the possible, my guess, location to blacklist nouvear to /etc/modprobe.d/dlblacklist-omv.conf.

[omvfan]

It’s been a long time since I installed my nvidia but iirc with a reboot it worked out of the box and had set all the kernel parameters needed by itself. What is your particular model, maybe it is not supported anymore by the (precompiled) 565 drivers and you need to compile those with dkms.

[ben79 (Ben Bullard)]

Yes, you would need to reboot. Anyone using nVidia graphics with Linux should know that.

Edit: The OM nvidia stuff may or may not work with dkms.

[Mordechai (Morris)]

I recently ran through this on two desktops with 1660 TI.

What I recorded here worked, but for one of the boxes, Steam does not run Proton layer games.

Desktop logs out to lock screen (nvidia)

Status: Computer 1: Ryzen 5 2600 GeForce 1660 TI 16 GB RAM Booted into live cd fine, followed steps got a working install. Computer 2: Ryzen 5 5600X GeForce 1660 TI 32 GB RAM Locks up after loading “Plymouth” (Which I believe is Wayland loader right?) I used the same ISO on both, the official X11 linked on the main page. To get the second computer working, I just moved up the steps in the process. From ISO Grub menu select Advanced Options Then boot to the CLI type live and press e…

[Omv3690]

@zeroability

What type of monitor and connection? Have you tried other connections? Do you have a more targeted log of the wayland failure? I found this command:

journalctl -b -1 | grep -i "drm\|nvidia\|NVRM\|09:00.0\|wayland"

I’ve gotten this with the command if it helps. GTX 1070, connection is DVI-D
wlog.txt (115.7 KB)
Same issue here. Nvidia drivers from OM rolling cause black screen with a blinking cursor upon logging into wayland session, a few crash report pop ups then I’m kicked out to login screen (seems like SDDM falls back to X11 too)
I was going to stay on the .run drivers but I’ve kinda got fed up with the stuttering so I decided to try out the repo driver again. somehow uninstalling the .run driver bricked my OS lol resulting in a reinstall, so at this point I’m willing to help out with any kind of info you need, especially since I really do need wayland working.

[zeroability]

This may be the issue:

Jan 12 23:17:12 openmandriva-x8664 kernel: [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to map NvKmsKapiMemory 0x00000000953e8b6f
Jan 12 23:17:12 openmandriva-x8664 kernel: [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to map NvKmsKapiMemory 0x00000000953e8b6f
Jan 12 23:17:12 openmandriva-x8664 kernel: [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to map NvKmsKapiMemory 0x00000000953e8b6f
Jan 12 23:17:12 openmandriva-x8664 kernel: [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to map NvKmsKapiMemory 0x00000000953e8b6f

@Omv3690

I really do need wayland working

What is the critical requirement for wayland, if you don’t mind me asking?

[Omv3690]

Jan 12 23:16:37 openmandriva-x8664 kwin_wayland[1198]: kwin_core: Failed to open drm node: ""
This line also seemed concerning, but I’m not experienced with this stuff

@zeroability

What is the critical requirement for wayland, if you don’t mind me asking?

Basically performance and proper multi-monitor support (it’s bad on X). On X11 launching an app (worst offenders being steam, system settings, system monitor, firefox), opening overview cause awful stuttering, resizing/maximizing windows even with floating taskbar/translucency disabled is slow, laggy gwenview and etc, some windows not remembering their size. Also prefer the tear-free experience in wayland that I can toggle with a window rule if needed. There’s more but can’t recall right now. Don’t know why X is so bad on my GPU in particular, probably has to do with pascal preceding the nvidia GSP stuff.

[zeroability]

Yeah, the performance between the two is usually the inverse of what you are describing. The devs are looking into it as much as they can with the driver being proprietary. Thank you for your patience and understanding.

[Omv3690]

@zeroability

Yeah, the performance between the two is usually the inverse of what you are describing. The devs are looking into it as much as they can with the driver being proprietary. Thank you for your patience and understanding.

NVIDIA has it’s own thing going on in userland instead of using Mesa (hence no DRI3 and etc), so Xorg was always worse on nvidia than AMD/Intel as far as I know, at least before GSP, dunno much about that part
Anyway, absolutely appreciate the team’s work here all constraints considered, no sweat.
Let me know if I can be of any help, I have a fresh ROME installation with the OM repo nvidia drivers (currently with X session as a stopgap)

[dutsky]

Thank you, but unfortunately reboot didn’t help. For some reason, installing proprietary nvidia driver didn’t blacklist nouveau driver.

So for my experience, after installing nvidia driver you need blacklist nouveau by hands and adding modprobe blacklist stanza isn’t enough, you must blacklist nouveau in grub like this rd.driver.blacklist=nouveau modprobe.blacklist=nouveau and regenereate config.

it helps, at least for me(RTX 3070)

[zeroability]

Did you install from the repos? It looks like you did not. We do disable the nouveau modules in the boot configuration as that is the requirement of newer nvidia cards, not blacklist.

[dutsky]

as i said early, all i did is just open om-welcome and run “install nvidia-driver” option from it.
Fresh installation of ROME/amd64/nonslim/x11