Reports no results, folder only contains a 00-keyboard.conf file.
Regarding the kernel boot parameters this is what I found through Yast: splash=silent resume=/dev/disk/by-uuid/f234c2cd-2808-467a-973f-6e12e5fa4a8e quiet
pc0:/home/gabrielbyrnei # zypper se -i amdgpu
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
---+------------------------+-----------------------------------------------------------+--------
i | kernel-firmware-amdgpu | Kernel firmware files for AMDGPU graphics driver | package
i | libdrm_amdgpu1 | Userspace interface for Kernel DRM services for AMD Rad-> | package
i | libdrm_amdgpu1-32bit | Userspace interface for Kernel DRM services for AMD Rad-> | package
i | xf86-video-amdgpu | AMDGPU video driver for the Xorg X server | package
the other amdgpu packages are not doing any harm.
After that you should be able to use your new nvidia GPU with open source drivers, check that everything looks normal.
Then you may choose to install the G05 driver again and see how that goes.
Tried that and I an now left with the following results:
pc0:/home/gabrielbyrnei # zypper se -i amdgpu
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
---+------------------------+-----------------------------------------------------------+--------
i | kernel-firmware-amdgpu | Kernel firmware files for AMDGPU graphics driver | package
i | libdrm_amdgpu1 | Userspace interface for Kernel DRM services for AMD Rad-> | package
i | libdrm_amdgpu1-32bit | Userspace interface for Kernel DRM services for AMD Rad-> | package
pc0:/home/gabrielbyrnei # zypper se -i nouveau
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
---+-----------------------+------------------------------------------------------------+--------
i | libdrm_nouveau2 | Userspace interface for Kernel DRM services for NVIDIA c-> | package
i | libdrm_nouveau2-32bit | Userspace interface for Kernel DRM services for NVIDIA c-> | package
i | libvdpau_nouveau | VDPAU state tracker for Nouveau | package
i+ | libvulkan_nouveau | Mesa vulkan driver for NVK (Nouveau Vulkan) | package
i+ | Mesa-dri-nouveau | Mesa DRI plug-in for 3D acceleration via Nouveau | package
i+ | xf86-video-nouveau | Accelerated Open Source driver for nVidia cards | package
I mean, it does still seem broken that doing a zypper dup after a GPU change auto enables the non free repo through openSUSE-repos-Tumbleweed-NVIDIA, tries to install G05 drivers and then after rebooting lands you on a broken GUI into CLI.
A bit unrelated, but what is the advantage or preferred action with xf86-video-nouveau? Having it installed or not installed?
I uninstalled it and Iām not using Modesetting, seems doesnāt seem any slower or faster than with having it installed.
Your card is apparently able to use the modesetting driver, so there is no need for xf86-video-nouveau.
Moreover you are using wayland, so you are likely not using the X interface at all unless you use some ancient apps not yet ready for wayland; that is likely the reason why you donāt see any difference.
Yes, that would be ideal but was the source of my original post.
When installing the G05 Nvidia driver through zypper inr, the system reboots into command line.
Hi, you can possibly edit the nvidia.conf file by using text editor named ājoeā or ānanoā , using nano may be easier from the command line. Edit carefully and then save the file when done. Then powecycle machine. After powercycling machine, you may be able to reach graphical target.
Since ages it is not required to manualy tinker with any configuration files to blacklist nouveau. This is done automatically by the Nvidia driver. This can also easily be seen by having a look at the terminal output when the Nvidia driver is installed. It explicitely states that nouveau gets blacklistedā¦
Inspect 50-nvidia.conf
Adding additional lock files at random places, only makes troubleshooting and installation/deinstallation worse and worseā¦
When the machine ends at a black screen after installation of the Nvidia driver, it is NOT an issue with nouveau not beeing blacklisted. If there would be an issue with missing blacklists, the machine would still boot and the inxi output would show that nouveau is still loaded. This is not the case here.
Just did zypper inr and dup which added the nvidia tumbleweed nvidia repos and installed the suggested G05 packages.
Fortunately system now reboots fine into a graphical KDE, so something was updated in the Tumbleweed repos.
Problem is, system is super unresponsive and laggy, mouse moves with almost a second of delay.