Installing the current NVIDIA Driver requieres exiting the x server.
How can that be done?
# sh NVIDIA-Linux-x86_64-340.106.runVerifying archive integrity... OK
Uncompressing NVIDIA Accelerated Graphics Driver for Linux-x86_64 340.106..................................................................................................................................................................................................................................
Welcome to the NVIDIA Software Installer for Unix/Linux
The file '/tmp/.X0-lock' exists and appears to contain the process ID '32209' of a
runnning X server.
ERROR: You appear to be running an X server; please exit X before installing. For further
details, please see the section INSTALLING THE NVIDIA DRIVER in the README
available on the Linux driver download page at www.nvidia.com.
ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for
details. You may find suggestions on fixing installation problems in the README
available on the Linux driver download page at www.nvidia.com.
Thank you Sauerland for your detailed explanation.
I will follow those instructions, which should resolve the problem.
(Warnings given when attempting to update state that the noveau driver currently installed is not recommended with the pending upgrades and I am already using the nvidia driver with good results on other systems - i.e. Leap 42.3).
Yes, you need to have gcc installed (and kernel-default-devel), as the installation needs to compile a kernel module.
In your first post I notice that you tried to install version 340.106 of the nvidia driver though.
That’s old and will NOT work on current Tumbleweed!
Download and install the latest version, 340.111 instead.
After that the system wouldn’t load, in rebooting.
And what exactly happens?
(The instructions work fine. Maybe I had the installation file in the wrong place (/home/user/downloads).
That’s important information. But I’m not sure whether gcc was installed or not.
Do you have a url for that?
The nviida website referred me to the 340.106 driver (the date of which is this month), based the GPU installed on the motherboard, a GeoForce GTS 250.
Leap 42.3 (which I am using now) is using the 340.104 and nvidia’s rpm specific version shown at
Yes, sorry, I mixed up the version numbers. There were too many threads about the 384.xx driver not working recently…
340.106 should be new enough of course.
FYI, a 340.xx driver is not available in the repo for Tumbleweed, because that version doesn’t support libnvglnd.
What happens is after a start job finishes I get a blank screen with a and nothing else.
Hm, I’m not at all sure what “after a start job finishes” means.
But you should still be able to boot to text mode and get to a login prompt then, by pressing ‘e’ in the boot menu and appending ‘3’ to the line starting with “linux” or “linuxefi” to do that.
But I suppose the problem just was that nvidia couldn’t be used because of the missing kernel module, and OpenGL support wasn’t working because the nvidia installer replaced the Mesa libraries by its own incompatible versions that only work with the nvidia driver.
One thing that did happen is that I was unable to active the nvidia repository for Tumbleweed using YAST though
Just enter the URL in YaST.
But that won’t help you as the repo for Tumbleweed only contains the G04 driver (384.xxx) which doesn’t support your card.
Although, using Leap (and the nvidia repo) is definitely less problematic if you rely on the nvidia driver.
If you install it via nvidia’s .run installer, you’d need to reinstall it after every kernel update (and it may happen that it doesn’t support the latest kernel yet), and after some other updates too.
That patch should work for a Gigabyte NVidia GeForce GTS250 GPU?
(I suppose if the 340.104 controller runs with it on Tumbleweed the answer is yes).
My principle problem was being unable to update since doing so triggered a warning that part of the update was incompatible with Qt (this is LXQt) and the noveau driver.
I’m not sure either but it it happens frequently with some systems and usually requires a 1 and a half minute wait.
I’ll try that.
Yes.
I tried several times, unsuccessfully
Correct.
My principle problem was being unable to update since doing so triggered a warning that part of the update was incompatible with Qt (this is LXQt) and the noveau driver.
Not being able to update motivated making the change. (Also it’s working well on some other systems).
That patch is unrelated to the exact kind of GPU.
It’s purpose is to make the nvidia driver work with the latest kernel.
It might be that it’s no longer necessary with 340.106, I don’t know.
My principle problem was being unable to update since doing so triggered a warning that part of the update was incompatible with Qt (this is LXQt) and the noveau driver.
You mean the warning when installing/updating Mesa-dri-nouveau?
You will get the same with Tumbleweed.
If you want to get rid of the warning, uninstall and lock Mesa-dri-nouveau, irrelevant whether you use Leap or Tumbleweed.
Btw, it’s not specifically incompatible with Qt per se, it just has problems in general. This was particularly a problem with QtWebEngine, but this go patched to use software rendering if nouveau is in use.
But that’s irrelevant anyway if you use the nvidia driver.
These are just remnants of the boot messages in text mode, and don’t indicate a problem.
Apparently it’s just that the login screen takes that long to start and/or fails completely. (which is to be expected if nvidia is installed but not working)