Installed nVidia propiertary driver - couldn't adjust screen resolution

English Hardware
1

Hi,

I have made a fresh install of Leap 15.2. I tried the nouveau driver, but the scrolling in Firefox was stuttering (tearing). (Seeing videos and the over all dekstop experience with nouveau was ok. I then installed the propieratary driver. I had it on my former setup with Leap 15.1 and it worked fairly well in this version. It had the same issues with scrolling in Firefox, but I activated the full composition pipeline, and it worked quite nice. I thought then that the easiest way was to install the propiertary driver. I used the same methode as on 15.1, but the driver could not be loaded properly. I could not launch the nVidia dashboard, and nvidia-smi said the driver was not loaded.

I have two questions is it a setting for nouveau which can be activated and do the same as Force Full Compositing Pipeline, and second is it a problem with the nvidia driver for 15.2?

Dag R

2

Hi
I’m assuming this (based on your previous posts) it’s a GTX970 card?

Did you check the nouveau driver is blacklisted? Did you install via the rpm repository or run file?

3

I did it in Yast. I checked after the install that nouveau was blacklisted. I was. Yes the card is GTX970.

Dag R

4

Hi
As root user run the command;


mkinitrd

Just to be sure it’s gone and reboot.

Can you also show the output fron;


zypper se -si nvidia
5

The output of:

sudo zypper se -si nvidia
[sudo] passord for root: 
Laster pakkebrønndata...
Leser installerte pakker...
No matching items found.

I also ran the mkinitrd. I would prefer to have the proprietary driver installed, but it seems a little wast to try again now. What do you recommend? Wait for a new version of the driver?

Dag R

6

Hi
I’m running the 450.57 driver installed the ‘hard way’ on Leap 15.2 without issues?

So the nvidia rpms are not installed now?

7

No, I removed them. I could not ajust the screen resolution, and the driver was not loaded. I run the nouveau driver now, but the screen freezes quite often. I am not sure what to do now. It seems the screen driver has something to do with this. Is it a way to read the log and see if it is the gpu driver which messes up with mye setup? Alternatively do a reinstall to give it all a new try?

Dag R

8

Hi
Up to you, I would just check there is no /etc/X11/xorg.conf file that has been created, you do have a /etc/modprobe.d/ file that blacklist nouveau and mkinitrd has been run. I would suggest booting to runlevel 3 (multi-user.target) to install the rpms, AFAIK it should just work…

9

Up to you, I would just check there is no /etc/X11/xorg.conf file that has been created, you do have a /etc/modprobe.d/ file that blacklist nouveau and mkinitrd has been run. I would suggest booting to runlevel 3 (multi-user.target) to install the rpms, AFAIK it should just work…

There is not a /etc/X11/xorg.conf file, and I’m running nouveau so it is not blacklisted. I have run mkinitrd several times. It sounds as the best advice for now to try to install the rpms in runlevel 3. If it works, I don’t have to reinstall.

Thanks for your commitment.

Dag R

10

Hi
Yes, you will need to ensure when booting to runlevel three (systemctl set-default multi-user.target) that you stop nouveau from loading at boot via editing the grub entry temporarily to disable it by adding nouveau.modset=0

When finished installing, run systemctl set-default graphical.target to set to runlevel five.

11

It might be worth trying the upstream default DDX (aka “driver”). Read about driver basics and the “default” here.

12

I was unaware of the problem with secure boot. I must have just cliked the EFI tool away when I rebooted the first time. I installed the drivers from Yast again (against your advice) and erolled MOK. Now it works fine. I think maybe the maual should be a little more clear on this procedure. Thanks for your advice anyway. I sure appreciate the service you guys bring on to us, lost souls.

Dag R