Nvidia driver on OpenSuse Tumbleweed require sudo?

[zuo]

I installed the opensuse driver with `sudo zypper install x11-video-nvidiaG06` but when I start KDE show the mouse cursor but not other thinks so I go to tty shell with ctr+alt+F1 and i install the G05 `sudo zypper install x11-video-nvidiaG05`.
Now If I use `nvidia-smi` I have an error but if I use `sudo nvidia-smi` it works. Also trought python with sudo and pytorch I'm able to use it, but for example steam have problem. How to solve this issue and achieve to use it without sudo?
(I try to force reinstall `sudozypperin-f(rpm-q-a--qf'%{x11-video-nvidiaG05}')` but no results)

[thibdb13]

You should choose which driver to install: G05 or G06 but not both together.
If you choose the G06 driver and use KDE-Plasma, you should add nvidia-drm.modeset=1 to the kernel parameters.

[zuo]

You should choose which driver to install: G05 or G06 but not both together.
If you choose the G06 driver and use KDE-Plasma, you should add nvidia-drm.modeset=1 to the kernel parameters.

At first I choose the G06 but I have problem with KDE (maybe because I do not add add nvidia-drm.modeset=1) so I pass to the G05, and it works but It require sudo (if I do sudo nvidia-smi I watch all correctly, but if I do nvidia-smi it say that the GPU are not visible).
I do not think that it is normal, how to fix the sudo required?

[thibdb13]

I would completely remove the G05 driver and adapt the kernel parameters at boot (nvidia-drm.modeset=1).

[mchnz]

If I have any issues with the G05 driver (after a kernel or driver update), they are usually cleared by reinstalling either the module or everything nvidia, from my admin notes:

Nvidia - in the event the kernel module needs a manual rebuild:

• rebuild the module only:
  
  • zypper in -f nvidia-gfxG05-kmp-default
  
  
• if that's not enough force a reinstall of all nvidia repo packages:
  
  • zypper --no-refresh se --installed-only -r NVIDIA | awk '$1 ~ /^i[+]*/ { print $3 }' | xargs zypper in --force

[zuo]

If I have any issues with the G05 driver (after a kernel or driver update), they are usually cleared by reinstalling either the module or everything nvidia, from my admin notes:

Nvidia - in the event the kernel module needs a manual rebuild:

• rebuild the module only:
  
  • zypper in -f nvidia-gfxG05-kmp-default
  
  
• if that's not enough force a reinstall of all nvidia repo packages:
  
  • zypper --no-refresh se --installed-only -r NVIDIA | awk '$1 ~ /^i[+]*/ { print $3 }' | xargs zypper in --force
  
  

I would completely remove the G05 driver and adapt the kernel parameters at boot (nvidia-drm.modeset=1).

I put the kernel param at boot, I also try to reinstall with the suggested command, I also try to remove , reboot and reinstall but the problem is the same, to understad it better that is the commands:

⋊>~nvidia-smi08:09:49
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. 

⋊>~sudonvidia-smi08:09:54
Mon Jan 31 08:10:05 2022        
+-----------------------------------------------------------------------------+ 
| NVIDIA-SMI 470.94       Driver Version: 470.94       CUDA Version: 11.4     | 
|-------------------------------+----------------------+----------------------+ 
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC | 
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. | 
|                               |                      |               MIG M. | 
|===============================+======================+======================| 
|   0  NVIDIA GeForce ...  Off  | 00000000:01:00.0 Off |                  N/A | 
|  0%   35C    P0    36W / 198W |      1MiB /  8119MiB |      0%      Default | 
|                               |                      |                  N/A | 
+-------------------------------+----------------------+----------------------+ 
|   1  Tesla M40 24GB      Off  | 00000000:02:00.0 Off |                    0 | 
| N/A   30C    P0    63W / 250W |      0MiB / 22945MiB |      0%      Default | 
|                               |                      |                  N/A | 
+-------------------------------+----------------------+----------------------+ 
                                                                                
+-----------------------------------------------------------------------------+ 
| Processes:                                                                  | 
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory | 
|        ID   ID                                                   Usage      | 
|=============================================================================| 
|  No running processes found                                                 | 
+-----------------------------------------------------------------------------+

[zuo]

I solve with:

sudo nvidia-smi -acp UNRESTRICTED
sudo usermod -a -G video <MY-USER-NAME>
# relogin

Now nvidia-smi work without sudo.

[awerlang]

Would you post the output of nvidia-smi again?

[Svyatko]

It is better to start with hardware description.
And what about nouveau drivers - you deleted them or what?

[zuo]

Scuse me to all, I do not read the blog for days.I try to describe better the problem:

* Desktop PC
* Opensuse Tumbleweed, KDE
* GPUs: nvidia 1080 + nvidia M40 24 GB
* I install at first G6 driver but KDE do not start correctly (I only see the mouse on screen without the other components of the desktop)
* I use tty to remove and install G5 driver
* KDE started correctly, but to see nvidia-smi I must do sudo, and I'm able to use GPU with python only if sudo
* I made the instruction that I described before and It seams to work for some days
* I installed STEAM and Proton with Battle.net using Proton with command line (maybe I do something else but I do not remember what, maybe zypper dup --allow-vendor-changes)
* now I cannot login, after the password insert (if it is wrong say that is wrong, but if it is correct) it start show very quickly something in the screen and return to login (I also tried wayland)