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.
Added support for the following GPU:
GeForce RTX 2060
Added a new kernel module parameter, NVreg_RestrictProfilingToAdminUsers, to allow restricting the use of GPU performance counters to system administrators only.
i have my nvidia GeForce installed and running, i tried the linux driver NVIDIA-Linux-x86_64-410 and it works okay, but i the console text mode works okay when i boot up, but after i startx for a desktop then log out of X for console text mode the screen is blank (no visible text) but i can type in startx (in the dark) and the gui comes back up, i cant have a dark screen like that so i switched back to the FOSS Nouveau and so far it works in both text mode console and GUI, so i will stick with nouveau for now
anyone else experience that?
P.S. so far it seems getting rid of the amdgpu radeon card and replacing it with the GeForce card has cured my PC from occasional crashes & lockups
Which version of Slackware, what kernel and what GeForce card (GPU version) are you using?
I am using slackware64 current and the video card is an Asus GeForce 1030 (PCIe x16 card) with passive cooling on a dell inspiron 5675 with a Ryzen 7 1700, while this is a gaming machine i dont use it for gaming (except for freecell and mahjongg), windows-10 was wiped off just about as soon as i got it, i dont use the 500 gigabyte hdd for running Slackware and instead it also has a 250 gig NVME solid state drive which i installed Slackware on and the hdd (spinning platter) drive is just used for storage
now i realise i did not try to run "reset" which could have let me see the text, but nouveau seems to be doing okay on it, i will run it for the time being
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,118
Original Poster
Rep:
Quote:
Originally Posted by Okie
I am using slackware64 current and the video card is an Asus GeForce 1030 (PCIe x16 card) with passive cooling on a dell inspiron 5675 with a Ryzen 7 1700, while this is a gaming machine i dont use it for gaming (except for freecell and mahjongg), windows-10 was wiped off just about as soon as i got it, i dont use the 500 gigabyte hdd for running Slackware and instead it also has a 250 gig NVME solid state drive which i installed Slackware on and the hdd (spinning platter) drive is just used for storage
now i realise i did not try to run "reset" which could have let me see the text, but nouveau seems to be doing okay on it, i will run it for the time being
Just as a suggestion, you might try the 415.13-Beta driver,
From jglisse@redhat ...
Subject [PATCH 00/10] HMM updates for 5.1
Date Tue, 29 Jan 2019 11:54:18 -0500
share
From: Jérôme Glisse <jglisse@redhat.com>
This patchset improves the HMM driver API and add support for hugetlbfs
and DAX mirroring. The improvement motivation was to make the ODP to HMM
conversion easier [1]. Because we have nouveau bits schedule for 5.1 and
to avoid any multi-tree synchronization this patchset adds few lines of
inline function that wrap the existing HMM driver API to the improved
API. The nouveau driver was tested before and after this patchset and it
builds and works on both case so there is no merging issue [2]. The
nouveau bit are queue up for 5.1 so this is why i added those inline.
If this get merge in 5.1 the plans is to merge the HMM to ODP in 5.2 or
5.3 if testing shows any issues (so far no issues has been found with
limited testing but Mellanox will be running heavier testing for longer
time).
To avoid spamming mm i would like to not cc mm on ODP or nouveau patches,
however if people prefer to see those on mm mailing list then i can keep
it cced.
This is also what i intend to use as a base for AMD and Intel patches
(v2 with more thing of some rfc which were already posted in the past).
Added initial support for G-SYNC Compatible monitors. See the README for details.
Added support for stereo presentation in Vulkan.
Fixed a bug that could cause OpenGL applications to crash after repeated VT-switches.
Fixed a bug that could sometimes prevent PRIME displays from being selected in the display settings page of nvidia-settings.
The main features available in this release are listed below:
Support for Turing NVENC/NVDEC.
The NVDECODE API (also known as the NVCUVID API) has been updated to support YUV 4:4:4 decoding for HEVC on Turing GPUs.
NvEncodeAPI has been updated to support HEVC B-frames on Turing GPUs. NvEncodeAPI adds the capability to output the encoded bitstream, and motion vectors from motion estimation-only mode, to video memory. This avoids the overhead of copying the output from system to video memory for processing pipelines operating directly on video memory.
NvEncodeAPI now accepts CUarrays as input buffers. The SDK contains a sample application to demonstrate how to feed a Vulkan image to NVENC using the Vulkan-CUDA interop.
Added NVIDIA optical flow support.
A new library libnvidia-opticalflow.so is included in the driver package. The NVIDIA optical flow library can be used for hardware-accelerated computation of optical flow vectors and stereo disparity values. The API header files, sample applications and documentation will be available in a separate Optical Flow SDK package in Q1 2019.
Removed libnvidia-wfb.so from the driver package. This module was only used on X servers that did not provide their own implementation of libwfb, and all X.Org xserver versions now supported by the driver do so.
Updated the VDPAU driver to reject decoding to YUV 4:2:2 video surfaces. The NVIDIA VDPAU driver always produces YUV 4:2:0 content. Previously, the VDPAU driver implicitly converted a YUV 4:2:2 video surface to YUV 4:2:0 during decode. Now, the VDPAU driver will fail the decode request.
Optimized nvidia-installer to only run depmod(1) once when installing, rather than twice (once during the uninstall phase and again when installing new kernel modules).
Removed the NVreg_UseThreadedInterrupts kernel module parameter from nvidia.ko. This removes the ability to forcibly fall back to an older mechanism (tasklets) for running the bottom-half interrupt handler. Instead, threaded IRQs (the default since 367.44) are always used.
Last edited by cwizardone; 01-30-2019 at 07:46 PM.
For the next SBo release, I'm pulling the plug on 32-bit support. nvidia-390.87 will be the last that supports both arch. Multilib will still be on option for those x86_64 users that need it.
Upgraded my 32-bit 14.2 kernel to 4.4.172 and now the nvidia-legacy390-kernel fails to compile due to the get_user_pages() definition change. Is there any hope for a new version of the legacy 32-bit package, or i must go back to manually installing nvidia drivers?
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,118
Original Poster
Rep:
In the past Nvidia has updated their older drivers when there have been similar problems, so I'm a bit surprised they haven't done so, yet.
We'll have to wait and see.
IIRC, as they announced, the 390.xx was the last Nvidia driver series to be available in 32-bit. However, the 64-bit versions continue to contain the 32-bit compatible drivers for multilib 64-bit systems.
The new 418.30-BETA driver has been working perfectly on this box with the 4.19.19 kernel.
Last edited by cwizardone; 02-01-2019 at 09:53 AM.
I've sent and update for 418-30-BETA to Slackbuilds.org, for lack of anything else since nvidia hasn't back ported any fix for kernel 4.4.172 yet as far as I know. Functionality is good. However, I did have one glitch today when the 2 monitors (GPU?) would not wake up and keyboard response was slow/lagging. ssh in and all looked ok, except 1 physical core was pegged at 100% with X.org for some reason - and wouldn't let go via the usual keyboard short cuts. After a reboot all is back to normal. Nothing in logs. Not really sure what was to blame: nvidia, X, XFCE, kernel, or something else I have running.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
390.87 (32bit) and 4.4.172 kernel
