[SOLVED] Slackware 15, nvidia-legacy340-driver, X server not start
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Slackware 15, nvidia-legacy340-driver, X server not start
Hello all Linux nerds!
I am almost giveup Please help me
I am successfully done FULL install of Slackware 15. And at first of all try to install nvidia proprietary drivers for my gf9800gtx(it old i am know) Nouveau driver works well. Bit proprietary not for me. What i am do:
1. blacklisted nouveau
Code:
/mnt/etc/modprobe.d/BLACKLIST-nouveau.conf 131/131 100%
# Do not load the kernel nouveau dri module, since it interferes with both
# the nv and binary nvidia drivers.
blacklist nouveau
What model nvidia GPU is this? FTR I have Slackware 15 installed on one PC which has a GT 640 GPU. I installed the NVIDIA 47.103.01 driver from runlevel 3 via the NVIDIA-foo.run script. It works very well. It took me longer to find a really proper driver for 32 bit installs and also for my 12+ year old laptop with a Quadro FX570M in it, but I guess I'm saying maybe don't just fall back on the default "Legacy" driver and maybe let nvidia's script recognize conflicts that a package might miss. I'm not at all disrespecting the efforts of slackbuild builders but GPUs are something of a "moving target" and we all know that if you skip a dependency that has changed in a build, it will often still build and install but will just "sit there".
I could be way off not knowing what GPU you have but searching out newer drivers costs little but some time and effort and the results can be superb.
Edit: Just saw Lucky Cyborg's perceptive post and immediately thought of 2 things
1) The NVIDIA-foo.run script would have informed you of the failure - one advantage to the manufacturer's installer.
2) It's a good idea to check if any important module is loaded and a simple "lsmod | grep nvidia" would do so.
I'm puzzled a bit by your "/etc/modprobe.d/blacklist" since all it needs to say is "blacklist nouveau" in most cases though a few add "blacklist nouveau-modeset" for good measure. In either case, "lsmod | grep nouveau" can confirm or deny the success of the blacklist.
And how do you see that its failed? And how fix that?
Quote:
Originally Posted by enorbet
What model nvidia GPU is this? FTR I have Slackware 15 installed on one PC which has a GT 640 GPU. I installed the NVIDIA 47.103.01 driver from runlevel 3 via the NVIDIA-foo.run script. It works very well. It took me longer to find a really proper driver for 32 bit installs and also for my 12+ year old laptop with a Quadro FX570M in it, but I guess I'm saying maybe don't just fall back on the default "Legacy" driver and maybe let nvidia's script recognize conflicts that a package might miss. I'm not at all disrespecting the efforts of slackbuild builders but GPUs are something of a "moving target" and we all know that if you skip a dependency that has changed in a build, it will often still build and install but will just "sit there".
I could be way off not knowing what GPU you have but searching out newer drivers costs little but some time and effort and the results can be superb.
Edit: Just saw Lucky Cyborg's perceptive post and immediately thought of 2 things
1) The NVIDIA-foo.run script would have informed you of the failure - one advantage to the manufacturer's installer.
2) It's a good idea to check if any important module is loaded and a simple "lsmod | grep nvidia" would do so.
I'm puzzled a bit by your "/etc/modprobe.d/blacklist" since all it needs to say is "blacklist nouveau" in most cases though a few add "blacklist nouveau-modeset" for good measure. In either case, "lsmod | grep nouveau" can confirm or deny the success of the blacklist.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,158
Rep:
The 340.108 driver is over two years old. Will it even work with the 5.15.y kernel?
To return to the nouveau driver, go to etc/modprobe.d/
and delete, nvidia-installer-disable-nouveau.conf
(the name might be a little different)
If you have an xorg.conf file in /etc/X11 or /etc/X11/xorg.conf.d/
delete it.
Reboot.
Another case, IMO, of slackpkg causing more trouble than it's worth.
Quote:
Originally Posted by LuckyCyborg
......Until you learn how to build your own kernels, do NOT install Multilib........
As long as the multilib files are properly installed, along with the multilib versions of gcc and glibc, there should NOT be any problems. Remember to reboot after installing the multilib files and before trying to compile anything.
Last edited by cwizardone; 05-07-2022 at 06:04 AM.
In fact, looks like the last two of them aren't required for the kernels from Slackware 15.0 - as I tested too, but good to know that those guys patched it up to latest kernel.
But I have no idea if those kernel modules really works, because I avoid the NVidia crapware like a devil the churches.
Considering your Multilib mess, again I recommend you to reinstall Slackware from scratch.
And again, please do not install Multilib until you really understand how it works and what implies its usage.
Thank you very much for explain. Yes, i do not understand how its all works. But i am curious how its all works. How i can learn and understood all this?
I am installing multilib because i want have driver with 32bit support(but i do not really know why i need 32bit and 64 bit driver in 64 bit OS?)
Here source of manual https://docs.slackware.com/howtos:ha...aphics_drivers
Quote:
After building the module on x86_64 systems, the installer will prompt about installing nVIDIA's 32-bit compatibility OpenGL libraries. You will only need the 32-bit compatibility libraries if your Slackware is 64-bit multilib.
PS Why here in Slackware are so many complexities and inaccuracies? Its all very hard to understood. What is main feature of Slackware and were way to understanding this distro?
As long as the multilib files are properly installed, along with the multilib versions of gcc and glibc, there should NOT be any problems. Remember to reboot after installing the multilib files and before trying to compile anything.
In order to keep up to date, I advise you to keep an eye on the ChangeLog (RSS feed) which I maintain for my multilib packages. Usually, I will have updated glibc and gcc packages available within a day after Slackware has updates to gcc and glibc.
Automation:
Check out compat32pkg by Sėbastien Ballet which automates this process, similar to slackpkg.
If you prefer slackpkg for package management, then it is worthwhile to check out slackpkg+, an extension to slackpkg which manages the packages you installed from 3rd-party repositories - including multilib. When properly configured, keeping your multilib is as easy as running:
That last command will show you if any new packages were added to the collection of “compat32” packages, such as llvm-compat32 and orc-compat32 recently.
This is how a typical configuration would look like - for a computer running Slackware-current and using Alien BOB's KDE testing repository. The PKGS_PRIORITY ensures that multilib packages of gcc and glibc have precedence over the Slackware originals. The keyword “multilib” which defines the name for the repository must be the same keyword used in the “slackpkg” commands above. The choice of the word “multilib” is arbitrary, it could just as well have been “compat32”, as long as you use it consistently.
Contents of an example file “/etc/slackpkg/slackpkgplus.conf” would be as follows:
If you follow the instructions in message #8, above, you should be able to use the nouveau driver by simply rebooting, provided, of course, the nouveau driver is still installed.
Have you removed the Nvidia driver?
sh ./nvidia-whatever-version.run --uninstall
Last edited by cwizardone; 05-07-2022 at 10:08 AM.
How you do that? I see working package with files, but how? Please explain.
IF you really do not figure out how to modify this SlackBuild and to apply the Arch Linux patches, even I explained in detail in the previous post from where to get the patches and which patches to use, then I strongly recommend you to stay in stock Slackware, with no proprietary drivers, no Multilib, nothing.
Please consider to stay in just the stock Slackware, until you gain more knowledge.
Last edited by LuckyCyborg; 05-07-2022 at 10:36 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Slackware 15, nvidia-legacy340-driver, X server not start
Please help me
