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.
Are these exactly the same on the laptop? There is a very similar option for kernel command line use:
Code:
nouveau.modeset=0
If the . is needed and missing, results will not be as expected.
Quote:
I only have a directory (/etc/share/X11/rorg.conf.d/) containing the following individual *.conf
Code:
bash-5.1# ls -l /usr/share/X11/xorg.conf.d/
-rw-r--r-- 1 root root 92 Oct 11 2019 10-amdgpu.conf
-rw-r--r-- 1 root root 489 Dec 27 23:04 10-nvidia.conf
-rw-r--r-- 1 root root 1350 Dec 17 23:38 10-quirks.conf
-rw-r--r-- 1 root root 92 Oct 15 2019 10-radeon.conf
and here, the '10-monitor.conf' is missing (according to the error msg i get when, after running nvidia-xconfig, i try to startx)
What actually matters is what these four files contain. There names can be anything, as long as their names end in .conf. Whatever content they contain will be utilized in the order found, with extras ignored. If something is present in 10-nvidia and is inconsistent with 10-amdgpu content, the first found 10-amdgpu content will control.
NVIDIA-Linux-x86_64-460.27.04.run (on the desktop) - build available from sklackbuilds.org[/quote]lspci -nnk | grep -iA3 vga produces some good information:
Device ID
Kernel driver in use
Lspci doesn't report the DDX driver in use, which is just as relevant, and can be had with inxi, plus kernel version, plus kernel command line options, all of which is graphics troubleshooting relevant (as long as not using an ancient 3.0.x or even older inxi version):
Update: almost 24hr of heavily testing, windows closing&opening, shading&unshading, moving across screens back&forth, including firefox, kdenlive, GIMP etc... and i have had no glitching, no crashing and faster window behaviour.
I am not technical enough to say whether it's the new kernel or some KDE updates that like/dislike better the Xrender rendering backend, rathen than OpenGL.
I will keep testing
If you look at post #6 in this thread, you should be able to note there exist two Nouveau drivers: 1-the kernel module (required by both competent FOSS DDX drivers suited to NVidia GPUs), and 2-a DDX driver (upstream package: xf86-video-nouveau, which is reverse-engineered), which there shown is not in use for the two 2560 wide displays. The upstream default DDX driver however is newer technology, named Modesetting, which is not reverse-engineered, and is there used. As seen in that thread post here, the Noveau DDX, to be distinguished from the Modesetting DDX, is completely optional, and used by virtually all my installations on NVidia GPUs (and AMD GPUs and IGPs, and Intel GPUs and IGPs). See here for more info.
It seems we might be discussing different things. I'm strictly talking about kernel drivers, not X drivers. The nouveau kernel driver needs to be disabled if the intention is to use the proprietary driver. I don't know enough about Nvidia and X drivers to get into that.
It seems we might be discussing different things. I'm strictly talking about kernel drivers, not X drivers. The nouveau kernel driver needs to be disabled if the intention is to use the proprietary driver. I don't know enough about Nvidia and X drivers to get into that.
that's exactly what i mean! often tech gurus get lost (understandably) in technicalities which are really not relevant to the issue at hand. I have always been taught that,
if it looks like a duck,
it walks like a duck and
it sounds like a duck,
it probably is a duck.
occasionally it might be something else but no need to go back to Darwin's theory to establish it.
I just edited a random clip on kdenlive, while watching news on chromium browser (firefox in-browser videos dont seem to work anymore except from youtube) and continuously have windows open&close and, it works great! Still on Xrender; skipping the proprietary driver issuses, nouveaus issues, and the whole darwin's evolution theory.
If the ugly problem started after the 21st of Dec/20 with kernal 10.X.3, why are we all debating on how video driver and/or nouveau drivers should/should not be considered, etc.? As i linked above there are a number of users having this identical problem, not all with nvidia cards and not all with KDE/nouveau so, as far as my badly uneducated brain goes, for some reason somewhere, the issue must be with the kernel (or at least with how the kernel integrates with some other packaged stuff such as OpenGL, for example).
But, then, what do i know!
p.s.: at the moment, i am not even considering struggling to understand what Darwin thought and I will keep Xrender as Rendering backend to have all 4 monitors working.
After I changed the Rendering backend to Xrender, I had no glitching and no system crash for about 36+hrs.
Last night I upgraded to the latest kernel 5.10.4 and i tried to switch back to OpenGL (tried both 2.0 and 3.1 under KDE, Setting>System Settings>Display and Monitor>Compositor), just for the sake of testing (as I am ok with losing visual desktop effects that are totally insignificant to the actual functioning of my computers).
It was only a matter of seconds before all monitors started glitching and after not even 5mins of opening several windows, including firefox (with/without Hardware acceleration enabled) i had systen crash on both desktop and laptop.
Hard reset, switched back to Xrender and all 4 screens working again: no glitching no crashes (12+hrs now); lost again the desktop effects (don't care) and the only symptom left is a single window flicker when i switch the active window in another monitor.
So, I am assuming it's not a matter of video card and/or desktop but, rather how newer kernels integrate with X
It's probably because the nouveau driver doesn't provide proper support for the OpenGL used with the desktop, so switching to XRender falls back to a simpler method (kinda like vesa support). To get OpenGL to work again, you likely require the proprietary driver.
Possibly the newer technology (upstream default) Modesetting DDX driver can do better than the Nouveau DDX. To find out, uninstall xf86-video-nouveau, and restart X. Or, if Modesetting is already in use, and xf86-video-nouveau is not installed, install it. If it is already installed, configure it using Driver for Device somewhere in /etc/X11/xorg.con*.
It's probably because the nouveau driver doesn't provide proper support for the OpenGL used with the desktop, so switching to XRender falls back to a simpler method (kinda like vesa support). To get OpenGL to work again, you likely require the proprietary driver.
I did try to install the proprietary driver; as a matter of fact, it is still installed but it just won't load. And, I must confess that I rather have the "kinda-like-vesa-support" that works and gives me all 4 screens with correct resolution that working with only 1 monitor on 1024x768 for days (as many days it took me to try to get the proprietary driver to work).
mrmazda
Possibly the newer technology (upstream default) Modesetting DDX driver can do better than the Nouveau DDX. To find out, uninstall xf86-video-nouveau, and restart X. Or, if Modesetting is already in use, and xf86-video-nouveau is not installed, install it. If it is already installed, configure it using Driver for Device somewhere in /etc/X11/xorg.con*.
This is like going round in circles. I have already described above that I don't have a /etc/X11/xorg.conf; if i run nvidia-xconfig one gets created but it won't start X.
Users with Intel GPU and/or different desktop with/without modesetting have identical problems so, i am not banging my head on the wall any longer thinking that it is an nvidia issue; it definitely seems to be a kernel issue (that affects not all slackware systems, for some reason) Kernel 5.10.4 i915 and dual screen freeze on intel GPU
Above shows you were using the Modesetting DDX driver when you ran this inxi. Whether that OpenGL renderer NVCF is appropriate with NVidia GPU and Modesetting DDX driver I can't say. I cannot recall ever having seen NVCF when I've run it here, no matter which AMD, Intel or NVidia GPU or IGP was in use.
Quote:
I have already described above that I don't have a /etc/X11/xorg.conf; if i run nvidia-xconfig one gets created but it won't start X.
Could it be because of conflict(s) from /etc/X11/xorg.conf.d/? Both xorg.conf and xorg.conf.d/ are optional. Most installations have no need for either one. Automagic takes care of X configuration for most installations, dispensing with need for either.
Quote:
Users with Intel GPU and/or different desktop with/without modesetting have identical problems
I'm not aware of any problems here using Modesetting DDX driver with AMD IGP or Intel IGP, e.g.:
Code:
# cat /etc/X11/xorg.conf
cat: /etc/X11/xorg.conf: No such file or directory
# ls -Gg /etc/X11/xorg.conf.d/
-rw-r--r-- 1 311 Jun 25 2018 00-keyboard.conf
-rw-rw-r-- 1 78 Jul 15 2011 70-extensions.conf
# inxi -GISay
System:
Host: gb250 Kernel: 5.9.14-1-default x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: root=LABEL=redact noresume mitigations=auto consoleblank=0
Desktop: Trinity R14.0.9 tk: Qt 3.5.0 info: kicker wm: Twin 3.0 dm: TDM
Distro: openSUSE Tumbleweed 20201231
Graphics:
Device-1: Intel HD Graphics 630 vendor: Gigabyte driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.10 driver: modesetting unloaded: fbdev,vesa
alternate: intel display ID: :0 screens: 1
Screen-1: 0 s-res: 2560x3720 s-dpi: 120 s-size: 541x787mm (21.3x31.0")
s-diag: 955mm (37.6")
Monitor-1: HDMI-1 res: 2560x1080 hz: 60 dpi: 97 size: 673x284mm (26.5x11.2")
diag: 730mm (28.8")
Monitor-2: HDMI-2 res: 1920x1200 hz: 60 dpi: 94 size: 519x324mm (20.4x12.8")
diag: 612mm (24.1")
Monitor-3: DP-1 res: 2560x1440 hz: 60 dpi: 109 size: 598x336mm (23.5x13.2")
diag: 686mm (27")
OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (KBL GT2)
v: 4.6 Mesa 20.2.4 compat-v: 3.0 direct render: Yes
Info:...Shell: Bash v: 5.0.18 running in: konsole inxi: 3.2.01
# xrandr | egrep 'onnect|creen|\*' | grep -v disconn | sort -r
Screen 0: minimum 320 x 200, current 2560 x 3720, maximum 16384 x 16384
HDMI-2 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 519mm x 324mm
HDMI-1 connected 2560x1080+0+1200 (normal left inverted right x axis y axis) 673mm x 284mm
DP-1 connected primary 2560x1440+0+2280 (normal left inverted right x axis y axis) 598mm x 336mm
2560x1440 59.95*+ 74.92
2560x1080 60.00*+
1920x1200 59.95*+
Code:
# cat /etc/X11/xorg.conf
cat: /etc/X11/xorg.conf: No such file or directory
# ls -gG /etc/X11/xorg.conf.d/
total 8
-rw-r--r-- 1 286 May 6 2014 00-keyboard.conf
-rw-r--r-- 1 126 Sep 24 23:29 50-device.conf
root@asa88:~# inxi -GISay
System:
Host: asa88 Kernel: 5.9.0-4-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.0
parameters:...root=LABEL=redact noresume mitigations=auto consoleblank=0 \
radeon.cik_support=0 amdgpu.cik_support=1
Desktop: Trinity R14.0.10 tk: Qt 3.5.0 info: kicker wm: Twin 3.0 dm: startx
Distro: Debian GNU/Linux bullseye/sid
Graphics:
Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASUSTeK driver: amdgpu
v: kernel alternate: radeon bus ID: 00:01.0 chip ID: 1002:130f
Display: server: X.Org 1.20.8 driver: modesetting display ID: :0 screens: 1
Screen-1: 0 s-res: 5120x1440 s-dpi: 120 s-size: 1083x304mm (42.6x12.0")
s-diag: 1125mm (44.3")
Monitor-1: HDMI-1 res: 2560x1080 hz: 60 dpi: 97 size: 673x284mm (26.5x11.2")
diag: 730mm (28.8")
Monitor-2: DP-1 res: 2560x1440 hz: 60 dpi: 109 size: 598x336mm (23.5x13.2")
diag: 686mm (27")
OpenGL: renderer: AMD KAVERI (DRM 3.39.0 5.9.0-4-amd64 LLVM 11.0.0)
v: 4.6 Mesa 20.2.3 direct render: Yes
Info:...Shell: Bash v: 5.1.0-rc3 running in: konsole inxi: 3.2.01
# xrandr | egrep 'onnect|creen|\*' | grep -v disconn | sort -r
Screen 0: minimum 320 x 200, current 5120 x 1440, maximum 16384 x 16384
HDMI-1 connected primary 2560x1080+0+0 (normal left inverted right x axis y axis) 673mm x 284mm
DP-1 connected 2560x1440+2560+0 (normal left inverted right x axis y axis) 598mm x 336mm
2560x1440 59.95*+ 74.92
2560x1080 60.00*+
This is like going round in circles. I have already described above that I don't have a /etc/X11/xorg.conf; if i run nvidia-xconfig one gets created but it won't start X.
If you are going to use nouveau then you'll want to use xorgsetup instead of nvidia-xconfig. The info in your code tag shows that the nouveau driver is being used. https://www.slackbook.org/html/x-win...xorgsetup.html
Thanks for the link but I'm just reminding the OP that he is using an nvidia tool to generate an xorg.conf. Slackware comes with xorgsetup and it will generate an xorg.conf for him for his hardware.
"nvidia-xconfig will find the X configuration file and modify it to use the NVIDIA X driver. In most cases, you can simply answer "Yes" when the installer asks if it should run it. If you need to reconfigure your X server later, you can run nvidia-xconfig again from a terminal. nvidia-xconfig will make a backup copy of your configuration file before modifying it." https://download.nvidia.com/XFree86/...itxconfig.html
Also when trying to use the NVIDIA binary he may have blacklisted Nouveau which appears to be what is being used for his device. Device and Display show nvidia for me. He needs to make sure things are set up for the nvidia binary driver or nouveau. I'm not saying that this is his issue but it will cause issues if he doesn't have this sorted out from my experience. https://forums.opensuse.org/showthre...nVidia-install
If you are going to use nouveau then you'll want to use xorgsetup instead of nvidia-xconfig. The info in your code tag shows that the nouveau driver is being used. https://www.slackbook.org/html/x-win...xorgsetup.html
I must admit that this was a new attempt so it raised my hopes.
So, to run xorgsetup:
left X, init 3
login as root, not SuperUser
bash-5.1$ xorgsetup
the first screen asks me automatically creat an xorg.conf file> i chose YES (if I choose NO the program exits). Then i was asked to choose the color bit and here, no matter what option i pick, the result is thousands (literally) or random symbols and words ($keyb&mouse*sens%etc...) filling up the screen and exit. So, i guess thats another no-go.
Quote:
mrmazda
It might pay to digest this video driver primer.
I have looked at this article again and ready more slowly and carefully scanning every sentence; i also noticed that it is dated July/20. There must have been a dozen kernel upgrade/patches since then and it is strange that you still insist on "digesting" it when it offers no solution but rather explains what KMS and Modesetting drivers are/do.
This morning, bored at work, I read that, from 5.10.X the kernel handling of video drivers has changed completely and is causing many issues with all sort of gpu vendors (intel, AMD, nvidia, etc.).
"As Linux Graphics Subsystem is something very complex, I think what we're seeing here is the result of changes in the way Linux kernel handles GPU drivers (i915, nvidia, ati and others) leading to unexpected results to the applications interacting with them. "Kernel 5.10.4 i915 and dual screen freeze on intel GPU post 20
I have tried everything that you guys kindly suggested, with no success. Perhaps, there will be another major kernel update coming up soon fixing this problem (in the meantime xrender is working ok (not great) so far, despite not having the full GPU capabilities for now).
I will keep an eye on this and other posts linked above with same problems. Thanks everyone for your time and effort.
edit: i just found this /var/log/nvidia/64/libGL.la with the following lines:
Code:
# libGL.la - a libtool library file
# Generated by nvidia-installer: 440.100 (for use by libtool)
#
# Please DO NOT delete this file!
# It is necessary for linking the library.
# The name that we can dlopen(3).
dlname='libGL.so'
# Names of this library.
library_names='libGL.so.440.100 libGL.so.1 libGL.so'
# Libraries that this one depends upon.
dependency_libs=' -L/usr/X11R6/lib -lm -lXext -lX11 -ldl'
# Version information for libGL.
current=1
age=0
revision=440.100
# Is this an already installed library?
installed=yes
# Files to dlopen/dlpreopen
dlopen=''
dlpreopen=''
# Directory that this library needs to be installed in:
libdir='/usr/lib64'
I can see reference to the previous nvidia driver i had installed (when everything was working well). is it of any relevance?
Then run upgradepkg and install them. This will replace the 5.10.XX Kernel with the 5.4.XX one. If this doesn't work then you may want to reinstall Slackware Current. If your home directory is on a different partition then you should be able to keep it. Backup of your data is recommended. If you want to use the NVIDIA binary driver again you may want to use the .run installer instead of the split packages at SBo.
Then run upgradepkg and install them. This will replace the 5.10.XX Kernel with the 5.4.XX one. If this doesn't work then you may want to reinstall Slackware Current. If your home directory is on a different partition then you should be able to keep it. Backup of your data is recommended. If you want to use the NVIDIA binary driver again you may want to use the .run installer instead of the split packages at SBo.
thank you so much for the binaries. I had planned to spend the evening downloading the previous working kernel, compiling and installing (major pain, in my honest opinion).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
