Bought myself a new display card, a Palit GeForce RTX 2070 GamingPro 8GB Graphics Card NVIDIA, not that I am a gamer. Finally got round to installing it, ran zypper up, rebooted with new drivers and I find 1024X768 (4:3) is the only resolution supported by this display. Other resolutions apparently not available in Plasma Wayland!
I committed some time ago to adopting Wayland and cannot believe I can’t get this new card to work so, before I regress to X11, please can somebody advise what is the correct solution for me here.
Hi and many thanks although the news is not great. I read with interest the thread in ?Open Chat? or similar the tales of woe concerning Leap 16 so had avoided changing for now as I have been very please with Leap 15.6. However, since I am in the process of rebuilding this machine I shall bite the bullet now but would very much appreciate your guidance on the best way to upgrade please .
@Budgie2 your way better doing a fresh install, there are so many changes with Leap 16.0. Migration is fine, but there are probably some configs that need removing or updating. Likewise the move to SELinux etc…
Nvidia (rpms) runs fine on Leap 16.0 here with GNOME and Wayland with a similar Turing architecture GPU
Only one available resolution can also be a sign of the nomodeset kernel command line parameter. This could be verified by showing the output of inxi -GSaz
type oalastair@localhost:~> zypper se -i nvidia
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
---+-------------------------------------------+-----------------------------------------------------+--------
i | kernel-firmware-nvidia | Kernel firmware files for Nvidia Tegra and graphi-> | package
i | nvidia-open-driver-G06-signed-kmp-default | NVIDIA open kernel module driver for GeForce 16 s-> | package
alastair@localhost:~>
This is what I have but I am getting advice on how to upgrade to 16.0 and since I have some time and am re-building the machine I shall first get 16 up and running.
I don’t suppose you have tried KDE desktop by any chance?
Doing a fresh install is no problem here, nothing installed yet.
If anybody else has any advice please speak now or forever…
On a slightly OT matter, what exactly are Leap Micro 6.2 and MicroOS and where is Slowroll? I should be reading up on these as I note you refer to them from time to time now.
Yeah. You’re missing packages that are required for driver to work. Here’s what I have on my system:
S | Name | Summary | Type
---+-------------------------------------------+---------------------------------------------------------------------------------------------------------------------------+--------
i | kernel-firmware-nvidia | Kernel firmware files for Nvidia Tegra and graphics drivers | package
i | libnvidia-egl-gbm1 | The GBM EGL external platform library | package
i | libnvidia-egl-wayland1 | The EGLStream-based Wayland external platform | package
i | libnvidia-egl-x111 | NVIDIA XLib and XCB EGL Platform Library | package
i | libnvidia-gpucomp | NVIDIA library for shader compilation (nvgpucomp) | package
i | nvidia-common-G06 | Common files for the NVIDIA driver packages | package
i | nvidia-compute-G06 | NVIDIA driver for computing with GPGPU | package
i | nvidia-compute-utils-G06 | NVIDIA driver tools for computing with GPGPU | package
i | nvidia-gl-G06 | NVIDIA OpenGL libraries for OpenGL acceleration | package
i | nvidia-modprobe | NVIDIA kernel module loader | package
i | nvidia-open-driver-G06-signed-kmp-default | NVIDIA open kernel module driver for GeForce 16 series (GTX 16xx) and newer | package
i | nvidia-open-driver-G06-signed-kmp-meta | Meta package to select open nvidia driver in sync | package
i | nvidia-persistenced | A daemon to maintain persistent software state in the NVIDIA driver | package
i | nvidia-userspace-meta-G06 | Meta package to autoselect NVIDIA userspace packages | package
i | nvidia-video-G06 | NVIDIA graphics driver for GeForce 700 series and newer | package
i | openSUSE-repos-Tumbleweed-NVIDIA | openSUSE NVIDIA repository definitions | package
Add Nvidia repo first:
sudo zypper in openSUSE-repos-Leap-NVIDIA
Then install meta package:
sudo zypper in nvidia-open-driver-G06-signed-kmp-meta
Leap Micro and MicroOS are mostly designed for servers. As a result they have read only filesystem. I wouldn’t recommend running them on desktop unless you know what you’re doing. Slowroll is in between Leap and Tumbleweed. It is getting updates faster than Leap but lags behind Tumbleweed.
@Budgie2 Further to @Lioli7k’s comments, they are also based on transactional updates, so if something goes foobar with an update it just discards and lets the admin figure out what is needed to resolve the issue.
Then there are Aeon (GNOME based) and Kalpa (Plasma based) desktops build on MicroOS (which tracks Tumbleweed), so the OS takes care of it’s self, is also read-only and additional security like full disk encryption OTB etc. For Aeon their are some additional hardware requirements for the full experience with TPM 2.0.
Then the user can just do their thing in user space with the likes of flatpaks, podman, distobox to meet their workflow requirements.
I built up my own instance of MicroOS with Hyprland, works fine
Hi and many thanks for the help. Since you had given me all I needed I have installed the NVIDIA kit you suggested and now I can actually work on the screen.
Thanks also for the comments on Micro and MicroOS and Malcolm’s follow up. Quite a meal has been served me and I had been trying to relax!!! So many questions I shall need to read a bit to make sense of it all. Perhaps after Christmas.
Meanwhile many thanks to all and wishing you all a very Merry Christmas and Happy New Year.
By way of a PS I am trying the network installation of Leap 16.0 from USB. No joy so far, the installation is failing in the background with nothing on screen but a blinking hyphen in top left. Could be the servers are down or unavailable. Have also tried burning a CD and using that to no avail.
Not sure where to go now unless I use the update option and sort out the issues which Malcolm suggest might be an issue. It seems that others have had no problems so may risk it tomorrow.
You need to add nomodeset on the kernel command line. This will overcome the black screen and the installation will be possible afterwards.
When you are at grub boot loader screen, simply hit “e”
Navigate with the arrow keys to the line which starts with “linux”
Hit “end” at your keyboard
Put a blank and nomodeset at the end of this line
Hit “F10”
First my thanks to hui for his advice to add nomodeset in the boot screen. This worked and I was able to install Leap 16.0. Did I miss this advice somewhere when I downloaded the OS I ask?
My next surprise is that installation landed me at a cli login screen. I logged in as local host and now I am at a cli prompt. No gui, just a command console.
I appreciate that a new OS is bound to have a few glitches but I have become used to Tumbleweed and Leap 15.6 so this install has been a bit of a shock. Please can somebody tell me where I am going wrong.
