GeForce GTX 1070, screen tearing w/ Nvidia

AdvancedGans25 · 2020-05-07 14:06:36

I have installed the proprietary nvidia drivers and nothing changed. I have messed in almost every possible setting and still nothing.
This is my config

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 440.82

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 440.82

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Ancor Communications Inc ASUS VP247"
    HorizSync       24.0 - 83.0
    VertRefresh     50.0 - 75.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1070"
    Option         "NoLogo" "1"
    Option         "RenderAccel" "1"
    Option         "TripleBuffer" "true"
    Option         "MigrationHeuristic" "greedy"
    Option         "AccelMethod" "sna"
    Option         "TearFree"    "true"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "UBB" "False"
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-0"
    Option         "metamodes" "DVI-D-0:1920x1080_60 +0+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

And this is the output of xrandr

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DVI-D-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 521mm x 293mm
   1920x1080     60.00*+
   1680x1050     59.95  
   1440x900      59.89  
   1280x1024     75.02    60.02  
   1280x960      60.00  
   1280x720      60.00  
   1152x864      75.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32    56.25  
   640x480       75.00    72.81    59.94  
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 disconnected (normal left inverted right x axis y axis)

Any ideas what I am doing wrong?

I am new to all of this...

Last edited by AdvancedGans25 (2020-05-07 14:48:32)

Trilby · 2020-05-07 14:34:35

You may get better help if you revise your title to mention Nvidia, and perhaps your hardware "GeForce GTX 1070", e.g., "GeForce GTX 1070, screen tearing w/ Nvidia".

Unfortunately, I have no experience with nvidia hardware or drivers, but generally those generated xorg configs are a source of problems, not a solution to them.

AdvancedGans25 · 2020-05-07 14:49:23

Already done, thanks anyway.
The thing is, I have already edit the config, this is not the generated one, and it's still the same...

Last edited by AdvancedGans25 (2020-05-07 14:54:24)

V1del · 2020-05-07 15:02:21

While the generated configs are almost never useful indeed, your edit includes a lot of senseless options that have no relevance at all to an nvidia card and might even break your original intentions used as they are.

Remove the file, reboot/restart xorg. If you still have tearing, post the xorg.0.log. Which environment are you doing this in?

AdvancedGans25 · 2020-05-07 15:18:53

V1del wrote:

While the generated configs are almost never useful indeed, your edit includes a lot of senseless options that have no relevance at all to an nvidia card and might even break your original intentions used as they are.
Remove the file, reboot/restart xorg. If you still have tearing, post the xorg.0.log. Which environment are you doing this in?

I did has you said remove the config rebooted and I still have tearing.

This is the xorg.0.log

[     3.850] 
X.Org X Server 1.20.8
X Protocol Version 11, Revision 0
[     3.850] Build Operating System: Linux Arch Linux
[     3.850] Current Operating System: Linux MUL 5.6.10-arch1-1 #1 SMP PREEMPT Sat, 02 May 2020 19:11:54 +0000 x86_64
[     3.850] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=7d621cb7-f0f8-40ef-ab4a-b0fbe138697c rw loglevel=3 quiet
[     3.850] Build Date: 05 May 2020  05:08:17AM
[     3.850]  
[     3.850] Current version of pixman: 0.40.0
[     3.850] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[     3.850] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     3.850] (==) Log file: "/var/log/Xorg.0.log", Time: Thu May  7 16:11:22 2020
[     3.853] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[     3.854] (==) No Layout section.  Using the first Screen section.
[     3.854] (==) No screen section available. Using defaults.
[     3.854] (**) |-->Screen "Default Screen Section" (0)
[     3.854] (**) |   |-->Monitor "<default monitor>"
[     3.855] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[     3.855] (==) Automatically adding devices
[     3.855] (==) Automatically enabling devices
[     3.855] (==) Automatically adding GPU devices
[     3.855] (==) Automatically binding GPU devices
[     3.855] (==) Max clients allowed: 256, resource mask: 0x1fffff
[     3.856] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/misc".
[     3.856] 	Entry deleted from font path.
[     3.856] 	(Run 'mkfontdir' on "/usr/share/fonts/misc").
[     3.856] (WW) The directory "/usr/share/fonts/TTF" does not exist.
[     3.856] 	Entry deleted from font path.
[     3.856] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[     3.856] 	Entry deleted from font path.
[     3.856] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[     3.856] 	Entry deleted from font path.
[     3.857] (==) FontPath set to:
	/usr/share/fonts/100dpi,
	/usr/share/fonts/75dpi
[     3.857] (==) ModulePath set to "/usr/lib/xorg/modules"
[     3.857] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[     3.857] (II) Module ABI versions:
[     3.857] 	X.Org ANSI C Emulation: 0.4
[     3.857] 	X.Org Video Driver: 24.1
[     3.857] 	X.Org XInput driver : 24.1
[     3.857] 	X.Org Server Extension : 10.0
[     3.858] (++) using VT number 7

[     3.858] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[     3.858] (II) xfree86: Adding drm device (/dev/dri/card0)
[     3.859] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/xorg/modules"
[     3.860] (--) PCI:*(1@0:0:0) 10de:1b81:1458:3772 rev 161, Mem @ 0xde000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
[     3.860] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[     3.860] (II) LoadModule: "glx"
[     3.861] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     3.872] (II) Module glx: vendor="X.Org Foundation"
[     3.872] 	compiled for 1.20.8, module version = 1.0.0
[     3.872] 	ABI class: X.Org Server Extension, version 10.0
[     3.872] (II) Applying OutputClass "nvidia" to /dev/dri/card0
[     3.872] 	loading driver: nvidia
[     3.872] (==) Matched nvidia as autoconfigured driver 0
[     3.872] (==) Matched nouveau as autoconfigured driver 1
[     3.872] (==) Matched nv as autoconfigured driver 2
[     3.872] (==) Matched modesetting as autoconfigured driver 3
[     3.872] (==) Matched fbdev as autoconfigured driver 4
[     3.872] (==) Matched vesa as autoconfigured driver 5
[     3.872] (==) Assigned the driver to the xf86ConfigLayout
[     3.872] (II) LoadModule: "nvidia"
[     3.872] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[     3.878] (II) Module nvidia: vendor="NVIDIA Corporation"
[     3.878] 	compiled for 1.6.99.901, module version = 1.0.0
[     3.878] 	Module class: X.Org Video Driver
[     3.879] (II) LoadModule: "nouveau"
[     3.879] (WW) Warning, couldn't open module nouveau
[     3.879] (EE) Failed to load module "nouveau" (module does not exist, 0)
[     3.879] (II) LoadModule: "nv"
[     3.879] (WW) Warning, couldn't open module nv
[     3.879] (EE) Failed to load module "nv" (module does not exist, 0)
[     3.879] (II) LoadModule: "modesetting"
[     3.879] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[     3.883] (II) Module modesetting: vendor="X.Org Foundation"
[     3.883] 	compiled for 1.20.8, module version = 1.20.8
[     3.883] 	Module class: X.Org Video Driver
[     3.883] 	ABI class: X.Org Video Driver, version 24.1
[     3.883] (II) LoadModule: "fbdev"
[     3.883] (WW) Warning, couldn't open module fbdev
[     3.883] (EE) Failed to load module "fbdev" (module does not exist, 0)
[     3.883] (II) LoadModule: "vesa"
[     3.883] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[     3.884] (II) Module vesa: vendor="X.Org Foundation"
[     3.884] 	compiled for 1.20.8, module version = 2.4.0
[     3.884] 	Module class: X.Org Video Driver
[     3.884] 	ABI class: X.Org Video Driver, version 24.1
[     3.884] (II) NVIDIA dlloader X Driver  440.82  Wed Apr  1 19:50:17 UTC 2020
[     3.884] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[     3.885] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     3.885] (II) VESA: driver for VESA chipsets: vesa
[     3.891] (II) Loading sub module "fb"
[     3.891] (II) LoadModule: "fb"
[     3.891] (II) Loading /usr/lib/xorg/modules/libfb.so
[     3.892] (II) Module fb: vendor="X.Org Foundation"
[     3.892] 	compiled for 1.20.8, module version = 1.0.0
[     3.892] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     3.892] (II) Loading sub module "wfb"
[     3.892] (II) LoadModule: "wfb"
[     3.892] (II) Loading /usr/lib/xorg/modules/libwfb.so
[     3.893] (II) Module wfb: vendor="X.Org Foundation"
[     3.893] 	compiled for 1.20.8, module version = 1.0.0
[     3.893] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     3.894] (II) Loading sub module "ramdac"
[     3.894] (II) LoadModule: "ramdac"
[     3.894] (II) Module "ramdac" already built-in
[     3.896] (WW) Falling back to old probe method for modesetting
[     3.896] (II) NVIDIA(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[     3.896] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[     3.896] (==) NVIDIA(0): RGB weight 888
[     3.896] (==) NVIDIA(0): Default visual is TrueColor
[     3.896] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[     3.896] (II) Applying OutputClass "nvidia" options to /dev/dri/card0
[     3.896] (**) NVIDIA(0): Option "AllowEmptyInitialConfiguration"
[     3.897] (**) NVIDIA(0): Enabling 2D acceleration
[     3.897] (II) Loading sub module "glxserver_nvidia"
[     3.897] (II) LoadModule: "glxserver_nvidia"
[     3.897] (II) Loading /usr/lib/nvidia/xorg/libglxserver_nvidia.so
[     3.949] (II) Module glxserver_nvidia: vendor="NVIDIA Corporation"
[     3.949] 	compiled for 1.6.99.901, module version = 1.0.0
[     3.949] 	Module class: X.Org Server Extension
[     3.950] (II) NVIDIA GLX Module  440.82  Wed Apr  1 19:47:36 UTC 2020
[     3.953] (II) NVIDIA: The X server supports PRIME Render Offload.
[     4.560] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0
[     4.560] (--) NVIDIA(0):     DFP-0 (boot)
[     4.560] (--) NVIDIA(0):     DFP-1
[     4.560] (--) NVIDIA(0):     DFP-2
[     4.560] (--) NVIDIA(0):     DFP-3
[     4.560] (--) NVIDIA(0):     DFP-4
[     4.560] (--) NVIDIA(0):     DFP-5
[     4.560] (--) NVIDIA(0):     DFP-6
[     4.560] (--) NVIDIA(0):     DFP-7
[     4.560] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 1070 (GP104-A) at PCI:1:0:0 (GPU-0)
[     4.560] (--) NVIDIA(0): Memory: 8388608 kBytes
[     4.560] (--) NVIDIA(0): VideoBIOS: 86.04.50.40.4a
[     4.560] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[     4.575] (--) NVIDIA(GPU-0): Ancor Communications Inc ASUS VP247 (DFP-0): connected
[     4.575] (--) NVIDIA(GPU-0): Ancor Communications Inc ASUS VP247 (DFP-0): Internal TMDS
[     4.575] (--) NVIDIA(GPU-0): Ancor Communications Inc ASUS VP247 (DFP-0): 330.0 MHz maximum pixel clock
[     4.575] (--) NVIDIA(GPU-0): 
[     4.575] (--) NVIDIA(GPU-0): DFP-1: disconnected
[     4.575] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[     4.575] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[     4.575] (--) NVIDIA(GPU-0): 
[     4.575] (--) NVIDIA(GPU-0): DFP-2: disconnected
[     4.575] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[     4.575] (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock
[     4.575] (--) NVIDIA(GPU-0): 
[     4.576] (--) NVIDIA(GPU-0): DFP-3: disconnected
[     4.576] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[     4.576] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[     4.576] (--) NVIDIA(GPU-0): 
[     4.576] (--) NVIDIA(GPU-0): DFP-4: disconnected
[     4.576] (--) NVIDIA(GPU-0): DFP-4: Internal DisplayPort
[     4.576] (--) NVIDIA(GPU-0): DFP-4: 1440.0 MHz maximum pixel clock
[     4.576] (--) NVIDIA(GPU-0): 
[     4.576] (--) NVIDIA(GPU-0): DFP-5: disconnected
[     4.576] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[     4.576] (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
[     4.576] (--) NVIDIA(GPU-0): 
[     4.576] (--) NVIDIA(GPU-0): DFP-6: disconnected
[     4.576] (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
[     4.576] (--) NVIDIA(GPU-0): DFP-6: 1440.0 MHz maximum pixel clock
[     4.576] (--) NVIDIA(GPU-0): 
[     4.576] (--) NVIDIA(GPU-0): DFP-7: disconnected
[     4.576] (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
[     4.576] (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
[     4.576] (--) NVIDIA(GPU-0): 
[     4.580] (==) NVIDIA(0): 
[     4.580] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[     4.580] (==) NVIDIA(0):     will be used as the requested mode.
[     4.580] (==) NVIDIA(0): 
[     4.580] (II) NVIDIA(0): Validated MetaModes:
[     4.580] (II) NVIDIA(0):     "DFP-0:nvidia-auto-select"
[     4.580] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[     4.584] (--) NVIDIA(0): DPI set to (93, 94); computed from "UseEdidDpi" X config
[     4.584] (--) NVIDIA(0):     option
[     4.584] (II) UnloadModule: "modesetting"
[     4.584] (II) Unloading modesetting
[     4.584] (II) UnloadModule: "vesa"
[     4.584] (II) Unloading vesa
[     4.584] (II) NVIDIA: Using 24576.00 MB of virtual memory for indirect memory
[     4.584] (II) NVIDIA:     access.
[     4.586] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[     4.586] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[     4.586] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[     4.586] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[     4.586] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[     4.586] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[     4.586] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[     4.586] (II) NVIDIA(0):     Config Options in the README.
[     4.606] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select"
[     4.703] (==) NVIDIA(0): Disabling shared memory pixmaps
[     4.703] (==) NVIDIA(0): Backing store enabled
[     4.703] (==) NVIDIA(0): Silken mouse disabled
[     4.703] (==) NVIDIA(0): DPMS enabled
[     4.704] (II) Loading sub module "dri2"
[     4.704] (II) LoadModule: "dri2"
[     4.704] (II) Module "dri2" already built-in
[     4.704] (II) NVIDIA(0): [DRI2] Setup complete
[     4.704] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[     4.704] (II) Initializing extension Generic Event Extension
[     4.704] (II) Initializing extension SHAPE
[     4.705] (II) Initializing extension MIT-SHM
[     4.705] (II) Initializing extension XInputExtension
[     4.705] (II) Initializing extension XTEST
[     4.705] (II) Initializing extension BIG-REQUESTS
[     4.705] (II) Initializing extension SYNC
[     4.705] (II) Initializing extension XKEYBOARD
[     4.705] (II) Initializing extension XC-MISC
[     4.705] (II) Initializing extension SECURITY
[     4.705] (II) Initializing extension XFIXES
[     4.705] (II) Initializing extension RENDER
[     4.705] (II) Initializing extension RANDR
[     4.705] (II) Initializing extension COMPOSITE
[     4.705] (II) Initializing extension DAMAGE
[     4.705] (II) Initializing extension MIT-SCREEN-SAVER
[     4.705] (II) Initializing extension DOUBLE-BUFFER
[     4.705] (II) Initializing extension RECORD
[     4.705] (II) Initializing extension DPMS
[     4.706] (II) Initializing extension Present
[     4.706] (II) Initializing extension DRI3
[     4.706] (II) Initializing extension X-Resource
[     4.706] (II) Initializing extension XVideo
[     4.706] (II) Initializing extension XVideo-MotionCompensation
[     4.706] (II) Initializing extension GLX
[     4.706] (II) Initializing extension GLX
[     4.706] (II) Indirect GLX disabled.
[     4.706] (II) GLX: Another vendor is already registered for screen 0
[     4.706] (II) Initializing extension XFree86-VidModeExtension
[     4.706] (II) Initializing extension XFree86-DGA
[     4.706] (II) Initializing extension XFree86-DRI
[     4.706] (II) Initializing extension DRI2
[     4.706] (II) Initializing extension NV-GLX
[     4.706] (II) Initializing extension NV-CONTROL
[     4.706] (II) Initializing extension XINERAMA
[     4.774] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[     4.774] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[     4.774] (II) LoadModule: "libinput"
[     4.774] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[     4.778] (II) Module libinput: vendor="X.Org Foundation"
[     4.778] 	compiled for 1.20.7, module version = 0.29.0
[     4.778] 	Module class: X.Org XInput Driver
[     4.778] 	ABI class: X.Org XInput driver, version 24.1
[     4.778] (II) Using input driver 'libinput' for 'Power Button'
[     4.778] (**) Power Button: always reports core events
[     4.778] (**) Option "Device" "/dev/input/event2"
[     4.778] (**) Option "_source" "server/udev"
[     4.784] (II) event2  - Power Button: is tagged by udev as: Keyboard
[     4.784] (II) event2  - Power Button: device is a keyboard
[     4.784] (II) event2  - Power Button: device removed
[     4.810] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[     4.810] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[     4.812] (II) event2  - Power Button: is tagged by udev as: Keyboard
[     4.812] (II) event2  - Power Button: device is a keyboard
[     4.813] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[     4.813] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[     4.813] (II) Using input driver 'libinput' for 'Power Button'
[     4.813] (**) Power Button: always reports core events
[     4.813] (**) Option "Device" "/dev/input/event1"
[     4.813] (**) Option "_source" "server/udev"
[     4.815] (II) event1  - Power Button: is tagged by udev as: Keyboard
[     4.816] (II) event1  - Power Button: device is a keyboard
[     4.816] (II) event1  - Power Button: device removed
[     4.836] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
[     4.836] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[     4.838] (II) event1  - Power Button: is tagged by udev as: Keyboard
[     4.839] (II) event1  - Power Button: device is a keyboard
[     4.840] (II) config/udev: Adding input device Sleep Button (/dev/input/event0)
[     4.840] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[     4.840] (II) Using input driver 'libinput' for 'Sleep Button'
[     4.840] (**) Sleep Button: always reports core events
[     4.840] (**) Option "Device" "/dev/input/event0"
[     4.840] (**) Option "_source" "server/udev"
[     4.842] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[     4.842] (II) event0  - Sleep Button: device is a keyboard
[     4.842] (II) event0  - Sleep Button: device removed
[     4.876] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0/event0"
[     4.876] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[     4.878] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[     4.879] (II) event0  - Sleep Button: device is a keyboard
[     4.880] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event13)
[     4.880] (II) No input driver specified, ignoring this device.
[     4.880] (II) This device may have been added with another device file.
[     4.881] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event14)
[     4.881] (II) No input driver specified, ignoring this device.
[     4.881] (II) This device may have been added with another device file.
[     4.882] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event15)
[     4.882] (II) No input driver specified, ignoring this device.
[     4.882] (II) This device may have been added with another device file.
[     4.883] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event16)
[     4.883] (II) No input driver specified, ignoring this device.
[     4.883] (II) This device may have been added with another device file.
[     4.884] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=10 (/dev/input/event17)
[     4.884] (II) No input driver specified, ignoring this device.
[     4.884] (II) This device may have been added with another device file.
[     4.885] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=11 (/dev/input/event18)
[     4.885] (II) No input driver specified, ignoring this device.
[     4.885] (II) This device may have been added with another device file.
[     4.886] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=12 (/dev/input/event19)
[     4.886] (II) No input driver specified, ignoring this device.
[     4.886] (II) This device may have been added with another device file.
[     4.887] (II) config/udev: Adding input device ASUS ASUS Strix Tactic Pro Gaming Keyboard (/dev/input/event4)
[     4.887] (**) ASUS ASUS Strix Tactic Pro Gaming Keyboard: Applying InputClass "libinput keyboard catchall"
[     4.887] (II) Using input driver 'libinput' for 'ASUS ASUS Strix Tactic Pro Gaming Keyboard'
[     4.887] (**) ASUS ASUS Strix Tactic Pro Gaming Keyboard: always reports core events
[     4.887] (**) Option "Device" "/dev/input/event4"
[     4.887] (**) Option "_source" "server/udev"
[     4.891] (II) event4  - ASUS ASUS Strix Tactic Pro Gaming Keyboard: is tagged by udev as: Keyboard
[     4.891] (II) event4  - ASUS ASUS Strix Tactic Pro Gaming Keyboard: device is a keyboard
[     4.892] (II) event4  - ASUS ASUS Strix Tactic Pro Gaming Keyboard: device removed
[     4.916] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.0/0003:195D:2039.0001/input/input7/event4"
[     4.916] (II) XINPUT: Adding extended input device "ASUS ASUS Strix Tactic Pro Gaming Keyboard" (type: KEYBOARD, id 9)
[     4.920] (II) event4  - ASUS ASUS Strix Tactic Pro Gaming Keyboard: is tagged by udev as: Keyboard
[     4.920] (II) event4  - ASUS ASUS Strix Tactic Pro Gaming Keyboard: device is a keyboard
[     4.922] (II) config/udev: Adding input device ASUS ASUS Strix Tactic Pro Gaming Keyboard Consumer Control (/dev/input/event7)
[     4.922] (**) ASUS ASUS Strix Tactic Pro Gaming Keyboard Consumer Control: Applying InputClass "libinput keyboard catchall"
[     4.922] (II) Using input driver 'libinput' for 'ASUS ASUS Strix Tactic Pro Gaming Keyboard Consumer Control'
[     4.922] (**) ASUS ASUS Strix Tactic Pro Gaming Keyboard Consumer Control: always reports core events
[     4.922] (**) Option "Device" "/dev/input/event7"
[     4.923] (**) Option "_source" "server/udev"
[     4.926] (II) event7  - ASUS ASUS Strix Tactic Pro Gaming Keyboard Consumer Control: is tagged by udev as: Keyboard
[     4.926] (II) event7  - ASUS ASUS Strix Tactic Pro Gaming Keyboard Consumer Control: device is a keyboard
[     4.927] (II) event7  - ASUS ASUS Strix Tactic Pro Gaming Keyboard Consumer Control: device removed
[     4.943] (II) libinput: ASUS ASUS Strix Tactic Pro Gaming Keyboard Consumer Control: needs a virtual subdevice
[     4.943] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.1/0003:195D:2039.0002/input/input10/event7"
[     4.943] (II) XINPUT: Adding extended input device "ASUS ASUS Strix Tactic Pro Gaming Keyboard Consumer Control" (type: MOUSE, id 10)
[     4.943] (**) Option "AccelerationScheme" "none"
[     4.943] (**) ASUS ASUS Strix Tactic Pro Gaming Keyboard Consumer Control: (accel) selected scheme none/0
[     4.943] (**) ASUS ASUS Strix Tactic Pro Gaming Keyboard Consumer Control: (accel) acceleration factor: 2.000
[     4.943] (**) ASUS ASUS Strix Tactic Pro Gaming Keyboard Consumer Control: (accel) acceleration threshold: 4
[     4.947] (II) event7  - ASUS ASUS Strix Tactic Pro Gaming Keyboard Consumer Control: is tagged by udev as: Keyboard
[     4.947] (II) event7  - ASUS ASUS Strix Tactic Pro Gaming Keyboard Consumer Control: device is a keyboard
[     4.949] (II) config/udev: Adding input device ASUS ASUS Strix Tactic Pro Gaming Keyboard (/dev/input/event8)
[     4.949] (**) ASUS ASUS Strix Tactic Pro Gaming Keyboard: Applying InputClass "libinput keyboard catchall"
[     4.949] (II) Using input driver 'libinput' for 'ASUS ASUS Strix Tactic Pro Gaming Keyboard'
[     4.949] (**) ASUS ASUS Strix Tactic Pro Gaming Keyboard: always reports core events
[     4.949] (**) Option "Device" "/dev/input/event8"
[     4.949] (**) Option "_source" "server/udev"
[     4.953] (II) event8  - ASUS ASUS Strix Tactic Pro Gaming Keyboard: is tagged by udev as: Keyboard
[     4.953] (II) event8  - ASUS ASUS Strix Tactic Pro Gaming Keyboard: device is a keyboard
[     4.953] (II) event8  - ASUS ASUS Strix Tactic Pro Gaming Keyboard: device removed
[     4.983] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.1/0003:195D:2039.0002/input/input12/event8"
[     4.983] (II) XINPUT: Adding extended input device "ASUS ASUS Strix Tactic Pro Gaming Keyboard" (type: KEYBOARD, id 11)
[     4.986] (II) event8  - ASUS ASUS Strix Tactic Pro Gaming Keyboard: is tagged by udev as: Keyboard
[     4.987] (II) event8  - ASUS ASUS Strix Tactic Pro Gaming Keyboard: device is a keyboard
[     4.989] (II) config/udev: Adding input device ASUS ASUS Strix Tactic Pro Gaming Keyboard Mouse (/dev/input/event5)
[     4.989] (**) ASUS ASUS Strix Tactic Pro Gaming Keyboard Mouse: Applying InputClass "libinput pointer catchall"
[     4.989] (II) Using input driver 'libinput' for 'ASUS ASUS Strix Tactic Pro Gaming Keyboard Mouse'
[     4.989] (**) ASUS ASUS Strix Tactic Pro Gaming Keyboard Mouse: always reports core events
[     4.989] (**) Option "Device" "/dev/input/event5"
[     4.989] (**) Option "_source" "server/udev"
[     4.992] (II) event5  - ASUS ASUS Strix Tactic Pro Gaming Keyboard Mouse: is tagged by udev as: Mouse
[     4.993] (II) event5  - ASUS ASUS Strix Tactic Pro Gaming Keyboard Mouse: device is a pointer
[     4.993] (II) event5  - ASUS ASUS Strix Tactic Pro Gaming Keyboard Mouse: device removed
[     5.049] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.1/0003:195D:2039.0002/input/input8/event5"
[     5.049] (II) XINPUT: Adding extended input device "ASUS ASUS Strix Tactic Pro Gaming Keyboard Mouse" (type: MOUSE, id 12)
[     5.050] (**) Option "AccelerationScheme" "none"
[     5.050] (**) ASUS ASUS Strix Tactic Pro Gaming Keyboard Mouse: (accel) selected scheme none/0
[     5.050] (**) ASUS ASUS Strix Tactic Pro Gaming Keyboard Mouse: (accel) acceleration factor: 2.000
[     5.050] (**) ASUS ASUS Strix Tactic Pro Gaming Keyboard Mouse: (accel) acceleration threshold: 4
[     5.053] (II) event5  - ASUS ASUS Strix Tactic Pro Gaming Keyboard Mouse: is tagged by udev as: Mouse
[     5.053] (II) event5  - ASUS ASUS Strix Tactic Pro Gaming Keyboard Mouse: device is a pointer
[     5.055] (II) config/udev: Adding input device ASUS ASUS Strix Tactic Pro Gaming Keyboard Mouse (/dev/input/mouse0)
[     5.055] (II) No input driver specified, ignoring this device.
[     5.055] (II) This device may have been added with another device file.
[     5.057] (II) config/udev: Adding input device ASUS ASUS Strix Tactic Pro Gaming Keyboard System Control (/dev/input/event6)
[     5.057] (**) ASUS ASUS Strix Tactic Pro Gaming Keyboard System Control: Applying InputClass "libinput keyboard catchall"
[     5.057] (II) Using input driver 'libinput' for 'ASUS ASUS Strix Tactic Pro Gaming Keyboard System Control'
[     5.057] (**) ASUS ASUS Strix Tactic Pro Gaming Keyboard System Control: always reports core events
[     5.057] (**) Option "Device" "/dev/input/event6"
[     5.057] (**) Option "_source" "server/udev"
[     5.061] (II) event6  - ASUS ASUS Strix Tactic Pro Gaming Keyboard System Control: is tagged by udev as: Keyboard
[     5.061] (II) event6  - ASUS ASUS Strix Tactic Pro Gaming Keyboard System Control: device is a keyboard
[     5.061] (II) event6  - ASUS ASUS Strix Tactic Pro Gaming Keyboard System Control: device removed
[     5.089] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.1/0003:195D:2039.0002/input/input9/event6"
[     5.089] (II) XINPUT: Adding extended input device "ASUS ASUS Strix Tactic Pro Gaming Keyboard System Control" (type: KEYBOARD, id 13)
[     5.093] (II) event6  - ASUS ASUS Strix Tactic Pro Gaming Keyboard System Control: is tagged by udev as: Keyboard
[     5.093] (II) event6  - ASUS ASUS Strix Tactic Pro Gaming Keyboard System Control: device is a keyboard
[     5.095] (II) config/udev: Adding input device Logitech G Pro Gaming Mouse (/dev/input/event9)
[     5.096] (**) Logitech G Pro Gaming Mouse: Applying InputClass "libinput pointer catchall"
[     5.096] (II) Using input driver 'libinput' for 'Logitech G Pro Gaming Mouse'
[     5.096] (**) Logitech G Pro Gaming Mouse: always reports core events
[     5.096] (**) Option "Device" "/dev/input/event9"
[     5.096] (**) Option "_source" "server/udev"
[     5.156] (II) event9  - Logitech G Pro Gaming Mouse: is tagged by udev as: Mouse
[     5.156] (II) event9  - Logitech G Pro Gaming Mouse: device is a pointer
[     5.156] (II) event9  - Logitech G Pro Gaming Mouse: device removed
[     5.209] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.0/0003:046D:C085.0004/input/input13/event9"
[     5.209] (II) XINPUT: Adding extended input device "Logitech G Pro Gaming Mouse" (type: MOUSE, id 14)
[     5.210] (**) Option "AccelerationScheme" "none"
[     5.210] (**) Logitech G Pro Gaming Mouse: (accel) selected scheme none/0
[     5.210] (**) Logitech G Pro Gaming Mouse: (accel) acceleration factor: 2.000
[     5.210] (**) Logitech G Pro Gaming Mouse: (accel) acceleration threshold: 4
[     5.269] (II) event9  - Logitech G Pro Gaming Mouse: is tagged by udev as: Mouse
[     5.269] (II) event9  - Logitech G Pro Gaming Mouse: device is a pointer
[     5.271] (II) config/udev: Adding input device Logitech G Pro Gaming Mouse (/dev/input/mouse1)
[     5.271] (II) No input driver specified, ignoring this device.
[     5.271] (II) This device may have been added with another device file.
[     5.273] (II) config/udev: Adding input device Logitech G Pro Gaming Mouse Keyboard (/dev/input/event10)
[     5.273] (**) Logitech G Pro Gaming Mouse Keyboard: Applying InputClass "libinput keyboard catchall"
[     5.273] (II) Using input driver 'libinput' for 'Logitech G Pro Gaming Mouse Keyboard'
[     5.273] (**) Logitech G Pro Gaming Mouse Keyboard: always reports core events
[     5.273] (**) Option "Device" "/dev/input/event10"
[     5.273] (**) Option "_source" "server/udev"
[     5.276] (II) event10 - Logitech G Pro Gaming Mouse Keyboard: is tagged by udev as: Keyboard
[     5.277] (II) event10 - Logitech G Pro Gaming Mouse Keyboard: device is a keyboard
[     5.277] (II) event10 - Logitech G Pro Gaming Mouse Keyboard: device removed
[     5.303] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.1/0003:046D:C085.0005/input/input14/event10"
[     5.303] (II) XINPUT: Adding extended input device "Logitech G Pro Gaming Mouse Keyboard" (type: KEYBOARD, id 15)
[     5.306] (II) event10 - Logitech G Pro Gaming Mouse Keyboard: is tagged by udev as: Keyboard
[     5.307] (II) event10 - Logitech G Pro Gaming Mouse Keyboard: device is a keyboard
[     5.309] (II) config/udev: Adding input device Logitech G Pro Gaming Mouse Consumer Control (/dev/input/event11)
[     5.309] (**) Logitech G Pro Gaming Mouse Consumer Control: Applying InputClass "libinput keyboard catchall"
[     5.309] (II) Using input driver 'libinput' for 'Logitech G Pro Gaming Mouse Consumer Control'
[     5.309] (**) Logitech G Pro Gaming Mouse Consumer Control: always reports core events
[     5.309] (**) Option "Device" "/dev/input/event11"
[     5.309] (**) Option "_source" "server/udev"
[     5.313] (II) event11 - Logitech G Pro Gaming Mouse Consumer Control: is tagged by udev as: Keyboard
[     5.313] (II) event11 - Logitech G Pro Gaming Mouse Consumer Control: device is a keyboard
[     5.313] (II) event11 - Logitech G Pro Gaming Mouse Consumer Control: device removed
[     5.343] (II) libinput: Logitech G Pro Gaming Mouse Consumer Control: needs a virtual subdevice
[     5.343] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.1/0003:046D:C085.0005/input/input15/event11"
[     5.343] (II) XINPUT: Adding extended input device "Logitech G Pro Gaming Mouse Consumer Control" (type: MOUSE, id 16)
[     5.343] (**) Option "AccelerationScheme" "none"
[     5.343] (**) Logitech G Pro Gaming Mouse Consumer Control: (accel) selected scheme none/0
[     5.343] (**) Logitech G Pro Gaming Mouse Consumer Control: (accel) acceleration factor: 2.000
[     5.343] (**) Logitech G Pro Gaming Mouse Consumer Control: (accel) acceleration threshold: 4
[     5.346] (II) event11 - Logitech G Pro Gaming Mouse Consumer Control: is tagged by udev as: Keyboard
[     5.347] (II) event11 - Logitech G Pro Gaming Mouse Consumer Control: device is a keyboard
[     5.349] (II) config/udev: Adding input device Logitech G Pro Gaming Mouse System Control (/dev/input/event12)
[     5.349] (**) Logitech G Pro Gaming Mouse System Control: Applying InputClass "libinput keyboard catchall"
[     5.349] (II) Using input driver 'libinput' for 'Logitech G Pro Gaming Mouse System Control'
[     5.349] (**) Logitech G Pro Gaming Mouse System Control: always reports core events
[     5.349] (**) Option "Device" "/dev/input/event12"
[     5.349] (**) Option "_source" "server/udev"
[     5.352] (II) event12 - Logitech G Pro Gaming Mouse System Control: is tagged by udev as: Keyboard
[     5.353] (II) event12 - Logitech G Pro Gaming Mouse System Control: device is a keyboard
[     5.353] (II) event12 - Logitech G Pro Gaming Mouse System Control: device removed
[     5.383] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.1/0003:046D:C085.0005/input/input16/event12"
[     5.383] (II) XINPUT: Adding extended input device "Logitech G Pro Gaming Mouse System Control" (type: KEYBOARD, id 17)
[     5.386] (II) event12 - Logitech G Pro Gaming Mouse System Control: is tagged by udev as: Keyboard
[     5.387] (II) event12 - Logitech G Pro Gaming Mouse System Control: device is a keyboard
[     5.388] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event20)
[     5.388] (II) No input driver specified, ignoring this device.
[     5.388] (II) This device may have been added with another device file.
[     5.389] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event21)
[     5.389] (II) No input driver specified, ignoring this device.
[     5.389] (II) This device may have been added with another device file.
[     5.390] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event22)
[     5.390] (II) No input driver specified, ignoring this device.
[     5.390] (II) This device may have been added with another device file.
[     5.391] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event23)
[     5.391] (II) No input driver specified, ignoring this device.
[     5.391] (II) This device may have been added with another device file.
[     5.391] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event24)
[     5.391] (II) No input driver specified, ignoring this device.
[     5.391] (II) This device may have been added with another device file.
[     5.392] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
[     5.392] (II) No input driver specified, ignoring this device.
[     5.392] (II) This device may have been added with another device file.
[     5.402] (**) ASUS ASUS Strix Tactic Pro Gaming Keyboard Consumer Control: Applying InputClass "libinput keyboard catchall"
[     5.402] (II) Using input driver 'libinput' for 'ASUS ASUS Strix Tactic Pro Gaming Keyboard Consumer Control'
[     5.402] (**) ASUS ASUS Strix Tactic Pro Gaming Keyboard Consumer Control: always reports core events
[     5.402] (**) Option "Device" "/dev/input/event7"
[     5.402] (**) Option "_source" "_driver/libinput"
[     5.402] (II) libinput: ASUS ASUS Strix Tactic Pro Gaming Keyboard Consumer Control: is a virtual subdevice
[     5.402] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.1/0003:195D:2039.0002/input/input10/event7"
[     5.402] (II) XINPUT: Adding extended input device "ASUS ASUS Strix Tactic Pro Gaming Keyboard Consumer Control" (type: KEYBOARD, id 18)
[     5.403] (**) Logitech G Pro Gaming Mouse Consumer Control: Applying InputClass "libinput keyboard catchall"
[     5.403] (II) Using input driver 'libinput' for 'Logitech G Pro Gaming Mouse Consumer Control'
[     5.403] (**) Logitech G Pro Gaming Mouse Consumer Control: always reports core events
[     5.403] (**) Option "Device" "/dev/input/event11"
[     5.403] (**) Option "_source" "_driver/libinput"
[     5.403] (II) libinput: Logitech G Pro Gaming Mouse Consumer Control: is a virtual subdevice
[     5.403] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.1/0003:046D:C085.0005/input/input15/event11"
[     5.403] (II) XINPUT: Adding extended input device "Logitech G Pro Gaming Mouse Consumer Control" (type: KEYBOARD, id 19)

I am running Qtile now, but I have used XFCE, GNOME, and i3; I had the same problem in all of them although in XFCE and GNOME was not as bad. But still pretty bad

seth · 2020-05-07 19:58:24

Does it go away for "xrandr --output DVI-D-0 --scale 1.1x1.1"? (This will scale the ouput, make it a bit blurry and enforce the full composition pipeline)
Also please describe the tearing (or make a video if possible) - this is not meant personally, but many ppl. describe all sorts of graphical artifacts as "tearing" - though not related to the tearing problem at all.
Notably where you encouter it (X11 and xrender do not support vblank control - an opengl compositor does, but cannot fix torn input)

AdvancedGans25 · 2020-05-07 20:13:05

seth wrote:

Does it go away for "xrandr --output DVI-D-0 --scale 1.1x1.1"? (This will scale the ouput, make it a bit blurry and enforce the full composition pipeline)
Also please describe the tearing (or make a video if possible) - this is not meant personally, but many ppl. describe all sorts of graphical artifacts as "tearing" - though not related to the tearing problem at all.
Notably where you encouter it (X11 and xrender do not support vblank control - an opengl compositor does, but cannot fix torn input)

I tried the tearing didn't go away.

Basically when there are movements in the screen, videos, games, basic scrolling in the browser, there are cuts, horizontal lines in the screen.

This is a fresh install so I have almost nothing installed yet, I installed picom it didn't run, an error appear with something to do with vsync. Now after I delete the config I had I can use it but I still have the same problem.

Last edited by AdvancedGans25 (2020-05-07 20:13:34)

seth · 2020-05-07 20:28:28

horizontal lines in the screen.

Plural? Are they of static position?

Do you get this in glxgears? (mesa-demos, stop every video playback game and your browser for this test)
Do you get this in "__GL_SYNC_TO_VBLANK=1 glxgears"?
Do you get this in "__GL_SYNC_DISPLAY_DEVICE=DVI-D-0 __GL_SYNC_TO_VBLANK=1 glxgears"?
Do you get this in "__GL_SYNC_TO_VBLANK=0 glxgears"? (Well, you will - but does it get better or worse)

How is the output attached? Actual DVI - DVI?
Is there any adapter involved?
Can you connect it using a different port? (Display Port or HDMI)
Do you have a second output (monitor) you could test? Tv?

AdvancedGans25 · 2020-05-07 20:47:30

seth wrote:

horizontal lines in the screen.
Plural? Are they of static position?
Do you get this in glxgears? (mesa-demos, stop every video playback game and your browser for this test)
Do you get this in "__GL_SYNC_TO_VBLANK=1 glxgears"?
Do you get this in "__GL_SYNC_DISPLAY_DEVICE=DVI-D-0 __GL_SYNC_TO_VBLANK=1 glxgears"?
Do you get this in "__GL_SYNC_TO_VBLANK=0 glxgears"? (Well, you will - but does it get better or worse)
How is the output attached? Actual DVI - DVI?
Is there any adapter involved?
Can you connect it using a different port? (Display Port or HDMI)
Do you have a second output (monitor) you could test? Tv?

Yes, plural. They vary in position .
In the first test I did glxgears I had a bit of tearing

"__GL_SYNC_TO_VBLANK=1 glxgears" with this one I had a bit, but barely any.
With the other two there was no tearing I could notice.

Yes, it is DVI - DVI.

No, no adapter. Monitor to GPU directly.

No, my GPU only as DVI port...
And I don't have any other monitor I can try on...

I think I can make a video if you think it can help

Last edited by AdvancedGans25 (2020-05-07 20:53:11)

jonno2002 · 2020-05-08 05:04:21

create this file

 /etc/X11/xorg.conf.d/20-nvidia.conf

and put this in it

Section "Screen"
    Identifier     "Screen0"
    Option         "metamodes" "nvidia-auto-select +0+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"
    Option         "AllowIndirectGLXProtocol" "off"
    Option         "TripleBuffer" "on"
EndSection

i have a 1070ti in one of my machines and this is the only config i use and it works perfectly on xfce (default compositor) and bspwm (using picom)

did a -Syu before posting this too just to be sure and no tearing in sight.

its all in the wiki anyway: https://wiki.archlinux.org/index.php/NV … en_tearing

InvisibleRasta · 2020-05-08 07:47:50

jonno2002 wrote:

create this file
 /etc/X11/xorg.conf.d/20-nvidia.conf
and put this in it
Section "Screen"
    Identifier     "Screen0"
    Option         "metamodes" "nvidia-auto-select +0+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"
    Option         "AllowIndirectGLXProtocol" "off"
    Option         "TripleBuffer" "on"
EndSection
i have a 1070ti in one of my machines and this is the only config i use and it works perfectly on xfce (default compositor) and bspwm (using picom)
did a -Syu before posting this too just to be sure and no tearing in sight.
its all in the wiki anyway: https://wiki.archlinux.org/index.php/NV … en_tearing

Thank you. this fixed my screen tearing on 1070ti aswell

AdvancedGans25 · 2020-05-08 08:22:18

jonno2002 wrote:

create this file
 /etc/X11/xorg.conf.d/20-nvidia.conf
and put this in it
Section "Screen"
    Identifier     "Screen0"
    Option         "metamodes" "nvidia-auto-select +0+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"
    Option         "AllowIndirectGLXProtocol" "off"
    Option         "TripleBuffer" "on"
EndSection
i have a 1070ti in one of my machines and this is the only config i use and it works perfectly on xfce (default compositor) and bspwm (using picom)
did a -Syu before posting this too just to be sure and no tearing in sight.
its all in the wiki anyway: https://wiki.archlinux.org/index.php/NV … en_tearing

I have tried that before, and I tried it again now and it didn't work...
Do I need a specific picom config? I don't thinks so right?
In most tests I can find online I have massive tearing, in the glxgears one I didn't have as much and in some cases none at all that I could notice.
In web browsing is just really annoying all the tearing...

seth · 2020-05-08 08:31:07

The glxgears test is inconclusive since #1 is equvalent to eihter #2 or #4 for sure.
Try "glsync -sb -i1" to see whether, how many and where the tearline is. Maximize the window. Do not run the command from some GL driven VTE (eg. kitty or I believe alacritty) but eg. xterm.

!!! WARNING !!!
!!! Do not run that command if you're prone to epileptic seizures !!!

Edit: as for "web browsing" in particular (and even more Firefox?): disable "smooth scrolling".

Last edited by seth (2020-05-08 08:31:55)

AdvancedGans25 · 2020-05-08 08:51:25

seth wrote:

The glxgears test is inconclusive since #1 is equvalent to eihter #2 or #4 for sure.
Try "glsync -sb -i1" to see whether, how many and where the tearline is. Maximize the window. Do not run the command from some GL driven VTE (eg. kitty or I believe alacritty) but eg. xterm.
!!! WARNING !!!
!!! Do not run that command if you're prone to epileptic seizures !!!

Edit: as for "web browsing" in particular (and even more Firefox?): disable "smooth scrolling".

I ran it on termite and the screen was just flickering for like 10 minutes noting, was it suppose to happen something?

I had that done once and it solve it, but was no solution, the problem was still there in videos and everything else, and plus it look really clunky...

jonno2002 · 2020-05-08 11:07:58

AdvancedGans25 wrote:

Do I need a specific picom config? I don't thinks so right?

nope just defaults

very strange, what WM/DE are you using ?

AdvancedGans25 · 2020-05-08 12:00:01

jonno2002 wrote:

AdvancedGans25 wrote:
Do I need a specific picom config? I don't thinks so right?
nope just defaults
very strange, what WM/DE are you using ?

I am running Qtile now, but I have used XFCE, GNOME, and i3; I had the same problem in all of them although in XFCE and GNOME was not as bad. But still pretty bad

I had already mention it.
Btw thanks everyone for trying to help

Last edited by AdvancedGans25 (2020-05-08 12:00:59)

AdvancedGans25 · 2020-05-08 12:05:04

I think I should mention as well that the tearing is not consistent it doesn't happen every time.
Normally when I boot the computer and go on to the browser is not that bad, but after loading a few pages it just start to tear a lot

seth · 2020-05-08 12:28:19

I ran it on termite and the screen was just flickering for like 10 minutes noting, was it suppose to happen something?

Yes, if you experience actual tearing, you'll see a tear line very prominently. Apparently that's not the case…

AdvancedGans25 · 2020-05-08 12:35:40

seth wrote:

I ran it on termite and the screen was just flickering for like 10 minutes noting, was it suppose to happen something?
Yes, if you experience actual tearing, you'll see a tear line very prominently. Apparently that's not the case…

No, I got nothing like that

seth · 2020-05-08 12:50:43

Seems like client specific problem.
Let's ignore the browser, FF has a gazillion bug reports about tearing w/ smooth scrolling, and focus on the video playback:
What video player and what kind of video output (GL, vdpau, generic GPU, … - mpv, mplayer and afaik vlc will allow you to configure this)?
Does the video frequency (24/23.976, 25, 30/29.97Hz) matter?

AdvancedGans25 · 2020-05-08 13:11:57

seth wrote:

Seems like client specific problem.
Let's ignore the browser, FF has a gazillion bug reports about tearing w/ smooth scrolling, and focus on the video playback:
What video player and what kind of video output (GL, vdpau, generic GPU, … - mpv, mplayer and afaik vlc will allow you to configure this)?
Does the video frequency (24/23.976, 25, 30/29.97Hz) matter?

I use mpv and I am not sure on what kind of video output I have, how can I check?
I am not sure how can I test it?
I also made a video trying to show the problem, how should I share it in here?

seth · 2020-05-08 13:16:41

Youtube upload or your google drive. Post a link, the board has no support for non-text data.

mpv /path/to/porn.mp4

should already print the used "VO:"
You can control it w/

mpv -vo help

and then pick an output, eg.

mpv -vo gpu /path/to/porn.mp4

AdvancedGans25 · 2020-05-08 13:42:15

seth wrote:

Youtube upload or your google drive. Post a link, the board has no support for non-text data.
mpv /path/to/porn.mp4
should already print the used "VO:"
You can control it w/
mpv -vo help
and then pick an output, eg.
mpv -vo gpu /path/to/porn.mp4

Excuse my poor use of ffmpeg and the lack of video editing
And the -vo I was using in the video was gpu

https://www.youtube.com/watch?v=fblqy7i … e=youtu.be
https://www.youtube.com/watch?v=D8u6uZu … e=youtu.be

seth · 2020-05-08 19:40:42

If you play those videos frame by frame you should find that there's no broken frame - the effect wasn't recorded (what speaks for actual tearing)
The "multiple tearlines" are probably w/ the tearing testvideo and rather a misperception because the tearline jumps between two positions what is a bit too much for your brain so it will just figure that there must be two of them.

Try

mpv --video-sync=display-vdrop --vo=gpu /path/to/porn.mp4

There're various parameters to control the A/V desync. Also there's "--override-display-fps=<fps>" and "--opengl-early-flush=<yes|no|auto>" to play with.

AdvancedGans25 · 2020-05-08 20:18:06

seth wrote:

If you play those videos frame by frame you should find that there's no broken frame - the effect wasn't recorded (what speaks for actual tearing)
The "multiple tearlines" are probably w/ the tearing testvideo and rather a misperception because the tearline jumps between two positions what is a bit too much for your brain so it will just figure that there must be two of them.
Try
mpv --video-sync=display-vdrop --vo=gpu /path/to/porn.mp4
There're various parameters to control the A/V desync. Also there's "--override-display-fps=<fps>" and "--opengl-early-flush=<yes|no|auto>" to play with.

I tried those out in some videos and it always seem like there is tearing or some kind of distortion.
The video don't capture the problem that well...
I have been reading on the issue and what many say is that the problem, many times, comes from the monitor refresh rate not being in sync with the GPU, but I don't know how to check if it is or not

Arch Linux

#1 2020-05-07 14:06:36

GeForce GTX 1070, screen tearing w/ Nvidia

#2 2020-05-07 14:34:35

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#3 2020-05-07 14:49:23

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#4 2020-05-07 15:02:21

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#5 2020-05-07 15:18:53

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#6 2020-05-07 19:58:24

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#7 2020-05-07 20:13:05

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#8 2020-05-07 20:28:28

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#9 2020-05-07 20:47:30

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#10 2020-05-08 05:04:21

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#11 2020-05-08 07:47:50

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#12 2020-05-08 08:22:18

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#13 2020-05-08 08:31:07

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#14 2020-05-08 08:51:25

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#15 2020-05-08 11:07:58

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#16 2020-05-08 12:00:01

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#17 2020-05-08 12:05:04

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#18 2020-05-08 12:28:19

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#19 2020-05-08 12:35:40

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#20 2020-05-08 12:50:43

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#21 2020-05-08 13:11:57

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#22 2020-05-08 13:16:41

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#23 2020-05-08 13:42:15

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#24 2020-05-08 19:40:42

Re: GeForce GTX 1070, screen tearing w/ Nvidia

#25 2020-05-08 20:18:06

Re: GeForce GTX 1070, screen tearing w/ Nvidia

Board footer