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.
For those of you who own NVIDIA cards and are attempting to run the 4.20-rcX series of kernels, please be advised that a patch is required for the driver to work. (Patch is at bottom of page).
Fixed a regression that prevented applications based on the Unity engine from starting.
Added support for VK_EXT_transform_feedback. Fixed a build failure, "unknown type name 'ipmi_user_t'", when building the NVIDIA kernel module for Linux kernel 4.20 release candidates.
Last edited by cwizardone; 12-07-2018 at 10:28 AM.
Slackbuilds no have this , and when kernel update need to rebuild manually.
Thanks!
When you boot into console mode and execute the .run file, it will offer to register the driver with DKMS automatically. Select 'yes', and that's all you need to do.
When you boot into console mode and execute the .run file, it will offer to register the driver with DKMS automatically. Select 'yes', and that's all you need to do.
I use the slackbuild package , NO DKMS support.
But i understand , need to exec the run file , in a init3 (console) , and install again (i supossed only one time cause after this DKMS registered).
I prefer DKMS , support in the slackbuild , but at the moment i go run the file in console.
Fixed a build failure, "implicit declaration of function 'vm_insert_pfn'", when building the NVIDIA DRM kernel module for Linux kernel 4.20 release candidates.
Slackbuilds no have this , and when kernel update need to rebuild manually.
Thanks!
I very much doubt I will add DKMS to the SBo nvidia slackbuild scripts. There are serveral nvidia kernel modules (nvidia-modeset, nvidia-drm, nvidia-uvm, nvidia) and the added dkms dependency and complexity is not worth the effort. After updating the kernel, you only need to re-run the nvidia-kernel script and upgradepkg. This is not that hard and very reliable.
After all, Slackware is not Ubuntu, etc or a rolling release like Arch.
Added support for the following GPU:
TITAN RTX
Fixed a bug that could prevent display detection from working on displays connected to some notebook docking stations.
Fixed a bug which could cause VK_KHR_external_semaphore_fd operations to fail.
Question: What can one do with a $10,000.00US graphics card to make it worth the price?
The last couple of NVIDIA driver updates seem to mess up Plasma 5 occasionally when starting using startx with multiple monitors. I boot up to a blank screen and have to use computer shortcuts to navigate Plasma 5 (alt+space for krunner, etc). I usually F1+Ctrl+Alt and startx again to get it to work correctly. I had the 3 screens off for a couple hours and it did it. I notice it pauses at a blank screen longer than it used to between switching accounts with SDDM. Any ideas?
I would use the appropriate device and screen entries in /etc/X11/xorg.conf.d to configure multiple monitors instead of letting X.org and KDE automagically configure. This seems to work ok for 1 monitor, but 2+ seems to be unstable, at least here, given how nvidia stomps on various X server and mesa components.
I sent over nvidia-410.78 LLB updates to Slackbuilds.org for those installing that way. The "beta" version is at linuxgalaxy.org. I think I fixed the libglx.so error. Working fine so far here.
I would use the appropriate device and screen entries in /etc/X11/xorg.conf.d to configure multiple monitors instead of letting X.org and KDE automagically configure. This seems to work ok for 1 monitor, but 2+ seems to be unstable, at least here, given how nvidia stomps on various X server and mesa components.
I used nvidia-settings to create my xorg.conf. I do not know how to do more than this in my xorg.conf:
Well, for one thing you don't have one monitor - you have 3 - and using metamodes with nvidia-auto-select can confuse X and your DE, especially when powering down. On power up it autodetects wrong. Also in KDE/Plasma make sure their settings utility isn't trying to override xord.conf settings. Set up the monitor sections, then attach each to one or more screens. you also need a server layout section, for example,
I use 2 independent X screens on 2 GPUs so yours will be a bit different. Once you get ANY screen up, run the nvidia-settings gui (advanced) to configure size and position and then save that configuration to an xorg.conf file; it should save more details than you showed. With the proprietary Nvidia drivers, you need to use nvidia-xconfig and nvidia-settings to configure, not the DE tools or xrandr as these can be problematic.
I can probably dredge up some examples once I find them.
Thank you for the information. I tried using different Screens before but it didn't work too well. I couldn't move my cursor from one screen to the next. I have one GPU. I'll try again with your suggestions.
Added support for the following GPUs:
Quadro RTX 8000
Fixed a bug that could prevent display detection from working on displays connected to some notebook docking stations.
Fixed a bug which could cause VK_KHR_external_semaphore_fd operations to fail.
Fixed a build failure, "implicit declaration of function
'vm_insert_pfn'", when building the NVIDIA DRM kernel module for Linux
kernel 4.20 release candidates.
Fixed a build failure, "unknown type name 'ipmi_user_t'", when building the NVIDIA kernel module for Linux kernel 4.20 release candidates.
Fixed a bug that caused kwin OpenGL compositing to crash when launching certain OpenGL applications.
Added a new kernel module parameter, NVreg_RestrictProfilingToAdminUsers, to allow restricting the use of GPU performance counters to system administrators only.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.