I don't have nvidia but check out willy's blogpost it may be helpful Linux Kernel 5.10.x Goes In and NVidia Legacy Patch (309.138) https://slackblogs.blogspot.com/2020/12/linux-kernel-510x-goes-in-and-nvidia.html

Edit: and this thread from the man himself https://www.linuxquestions.org/quest...-x-4175687158/

I have the same problems when using an external monitor with ThinkPad W520 with enabled optimus. Before major updates Fri Nov 27 06:21:11 UTC 2020 things works just fine with nouveau driver and no additional xorg.conf files. After updates, I have experienced some problems with screen glitching on the external monitor. I disabled optimus and using only a discrete graphic card. All good... After "5.10 kernel" updates system starts freezing when "unlocking" screen saver and also random freezing at normal work, but freezing when unlocking system after the screen saver starts is always reproducible. Without an external monitor, no problems were detected. I'm using Xfce de.

So, back from/to work!

Thank you. I read the link you provided and I, somewhat, understand that this Modesetting DDX driver primer could fix the problem. However, no links anywhere where to find the appropriate driver for my nvidia card.

That's plausible since i blacklisted the nouveau drivers and was trying to install the proprietary nvidia drivers. Now that I am back with nouveau it list the right card and driver again.

and I only mentioned that driver version bcos i was led to believe that, for old nvidia cards, Legacy drivers are working. I will try the 455.45 on the laptop and will post outcome

with the greatest respect, from experience, the reason i often skip on reading through some links that will link to another post, which will link to another link that finally take you to the post adopted be someone with a similar problem but NO EXACTLY the same issue. And i have perhaps learned how to patch something completely unnecessary, maybe learned some new terminology but still I have side-tracked miles away form the solution that works for me.

In the meanwhile today coming form work i was greeted with an immediate system freeze as soon as i moved the mouse

I had this issue with slackware current 2 yrs ago (https://www.linuxquestions.org/quest...es-4175646321/), and I am learning that lots of other people have similar issue with nvidia and the new linux kernel; at least 2 yrs ago i was able to solve it by manually installing the nvidia drivers. Now i cant do it bcos of a new modesetting DDX driver is needed.

p.s. Honestly, i cant be the only only linux/slack user who has a dual screen, or wants to watch a movie on a bigger screen, or needs to do some work requiring more graphic details and I wonder how developers, tech gurus or engineers react when after a kernel update they can't do that any longer )

There's no need to "find" it. If X is installed, then Modesetting is installed. They both come from the very same package, unless Slackware somehow managed to split upstream's X package into more than one. For Xorg versions prior to 1.17.0 (Slackware 14.1 and prior), Modesetting (upstream) was in a separate package named xf86-video-modesetting. Implementing its use can be either a simple matter of not having the Noveau and/or an NVidia package installed, or configuring it via "Driver" in a "Device" section in /etc/X11/xorg.con*, and not disabling KMS via a bootloader command line option (e.g. nomodeset or nouveau.modeset=0), and not blacklisting nouveau.

1 members found this post helpful.

I am sorry sir, i am confused! so how was all this reading through your link and learning about modesetting DDX etc... supposed to help me? Everything was NOT disabled neither/nor blacklisted when i started the thread from which one can assume that this DDX was setup correctly since everything was absolutely fine. What vital point did i miss from your post?


as i mentioned above, this member had an issue similar to mine but the problem was an AMD card not nvidia. I will give it a try to nvidia patch that he says he hacked in his site.

That link is to a primer, foundational information about X drivers.

Most distros install by default xf86-video-nouveau, however named. If Slack is like most in this regard, then you almost certainly were not using the Modesetting DDX. You haven't shown us any Xorg.#.logs, information that typically is crucial in diagnosing trouble with graphics.

1 members found this post helpful.

Dear mrmazda, i respect and appreciate your effort to help me and I may try to understand the pathogenesys of a headache but I don't need to learn its full anatomy&physiology before I go to my GP for a pill.
That aside, it took 21 post before i was asked for the Xorg.log file so I apologize if i didnt post it earlier.
I hope that this helps.

Xorg.0.log

In the meantime, i am trying the patch hack suggested by https://www.linuxquestions.org/quest...-x-4175687158/

The log shows you're currently operating on the crude fallback VESA X driver. This is a typical result of a defective NVidia driver installation or incomplete NVidia driver un-installation. I've never encountered hardware where the VESA driver supports more than 1024x768.

The "(EE) open /dev/dri/card0: No such file or directory" error is a typical result of blacklisting nouveau or otherwise disabling KMS. Both Modesetting DDX and Nouveau DDX require KMS, and no blacklisting of nouveau.

I have uninstalled the nouveau blacklist package and i am back on one working screen. I assume that Modesetting DDX and Nouveaur DDX are back and working; the issue that I cannot plug a second monitor/screen still remains (if i do, the system freeze again after a few mins). How can i install the native proprietary drivers? I must have been very naughty this year to deserve a present like this from Santa

I have tried the kernel patch suggested by willysr on my laptop and it didn't work either.

So far I have no possible solution for my GEFORCE GTX1060. grrrrr

Whenever you make a graphics change and need more help, we need to see the log again. A quick indication of the kernel, X, Mesa and related drivers in use is:

1 members found this post helpful.

I had never come across this command!
Below it's the output:
Interestingly, after learning all these things abut modesetting, i see that it's not loaded!?

My main issue is that the nvidia driver won't build bcos the nvidia kernel won't build on the new linux kernel 5.10.2. Two years ago somehow, i managed to get it to work with manual install of the nvidia driver after every update. (I wish that sbopkg had an nvidia driver built for slackware current-latest kernel)

I reformatted so that it should be clear how the key strings should be read. (Modesetting is loaded.)

I am afraid that i do not undetstand what you mean.
You reformatted what? Once it's clear to read... what? So if modesetting is loaded any advice on what other possible things i could look up to buold this curse of a driver?

Surely, we (flyingv2 above and I) can't be the only one with this issue

Hi everyone,
i reverted everything back to default and I noticed that if i use the same screen resolution for the laptop and the second screen the problem disappear; however on the desktop i have two similar screen sizes but can't get exact resolution from the System Setting > Display and Monitor thus resulting in the secondary screen still glitching continuously and no system freeze yet (almost 24hrs). I am not sure whether the glitching is a matter of the video card controller not being able to handle two different resolutions as it didn't do it before kernel 5.10.X update.
I will keep testing

Ignore it!
As soon as i clicked post desktop crashed and had to hard-reboot.
(