[SOLVED] Screen tearing when modesetting intel drivers

ihopeliliadomsme · 2024-01-02 23:27:04

Hello,

This is my first post on this account, I've never had to post something on the forum as ive always found the solution, ive been using arch for the past 2 years or so, i appreciate any help you will give me. (note that English isnt my first language so im sorry for any spelling or grammar mistakes).

Getting to the issue, i got a new laptop with an i5-13420H and integrated intel graphics, and i've been having a hard time fixing the screen tearing i get,

this is my config:-
/etc/X11/xorg.conf.d/20-modesetting.conf

Section "Device"
Identifier "modesetting"
Driver "modesetting"
Option "TearFree" "True"
EndSection

/etc/X11/xorg.conf.d/modesetting.conf

Section "Device"
Identifier "modesetting"
Driver "modesetting"
Option "TearFree" "True"
EndSection

I have tried DRI and AccelMethod but none work.

here are my specs:-

System Information:
-------------------
Kernel: 6.6.8-arch1-1
CPU: 13th Gen Intel(R) Core(TM) i5-13420H
RAM: 7.5Gi
GPU: Intel Corporation Raptor Lake-P [UHD Graphics] (rev 04)
Resolution: 1920x1080
Operating System: Arch Linux

This is the output of lspci -k | grep -A 2 -E "(VGA|3D)"
00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-P [UHD Graphics] (rev 04)
Subsystem: Lenovo Raptor Lake-P [UHD Graphics]
Kernel driver in use: i915

Last edited by ihopeliliadomsme (2024-01-03 22:09:36)

Head_on_a_Stick · 2024-01-02 23:31:24

I don't think the modesetting driver has the TearFree option yet, it isn't in the man page anyway. Check the X.Org log to be sure. You will have to use picom instead. Or switch to Wayland.

Scimmia · 2024-01-03 00:05:28

While TearFree was added to modesetting, it was only merged to Master and not backported to the 21.1 branch. We would need a 21.2 or 22 release to get this option.

ihopeliliadomsme · 2024-01-03 21:32:52

I am using picom currently, but it doesnt matter if i do have picom running or not i still get the same amount of screen tearing.
& modsetting was merged in January or june of 2023 im pretty sure.

Last edited by ihopeliliadomsme (2024-01-03 21:33:52)

seth · 2024-01-03 21:47:39

& modsetting was merged in January or june of 2023 im pretty sure.

No.

Does the tearing (only) affect fullscreen windows?
Try to disable unredirection, "unredir-if-possible" or "unredir-if-possible-exclude", https://man.archlinux.org/man/extra/picom/picom.1.en

ihopeliliadomsme · 2024-01-03 21:54:55

im sorry i phrased it wrong, i meant the option TearFree was merged in January,
no tearing doesnt only affect fullscreen windows,
& i just tried running picom with vsync, which kind of fixed my issue, i dont have anymore "breaking" no its laggy, i think you call this micro stuttering but im not sure.

Thank you for your help.

Last edited by ihopeliliadomsme (2024-01-03 21:57:55)

seth · 2024-01-03 22:00:18

Yes, but there's no release w/ that commit.

xrandr --verbose

ihopeliliadomsme · 2024-01-03 22:08:21

Im sorry for wasting your time seth, i believe i fixed my original problem which was with the insane amount of tearing i had, now i have a little microstutters but thats from another issue that stems from my browser, thanks alot for your help.

I will mark this is as solved now.

Head_on_a_Stick · 2024-01-04 12:05:32

Wayland doesn't tear and doesn't lag. It's simply better than X in that respect.

seth · 2024-01-04 15:52:55

X11 neither lags nor tears because it's ideally not used with GLX clients
"Wayland" tears and stutters if the particular compositor is buggy (feel free to search the mutter bugs)

The conceptual difference is that the wayland protocol mandates the responsibilities where as with X11 environments you can have display server, (optional) compositor and client play The Three Stooges.
There's no inherent superiority, vblank is vblank - it's just very hard to misconfigure wayland itr and very hard to sort out peculiarities of individual clients and compositors on X11

Head_on_a_Stick · 2024-01-04 15:54:50

Let me rephrase that then: sway doesn't lag and it doesn't tear on my AMD hardware. Openbox either tears or lags.

seth · 2024-01-04 16:05:46

Openbox probably neither lags or tears, but some compositor or client you're running along it.
(openbox' only visual elements are the 20px titlebars, you gotta be the unluckiest fella in the world to get tearlines there)

If you ever wonder why and the obvious answer isn't xf86-video-amdgpu/TearFree or drirc/vblank_mode, look around in /usr/share/drirc.d/00-mesa-defaults.conf (and of course non-GL clients are susceptible to tearing because they've no vblank control mechanism)

topcat01 · 2024-01-07 21:57:52

OP, are you using the glx or the xrender backend with picom? I have no issues with the glx backend on either Intel or AMD cards.

Arch Linux

#1 2024-01-02 23:27:04

[SOLVED] Screen tearing when modesetting intel drivers

#2 2024-01-02 23:31:24

Re: [SOLVED] Screen tearing when modesetting intel drivers

#3 2024-01-03 00:05:28

Re: [SOLVED] Screen tearing when modesetting intel drivers

#4 2024-01-03 21:32:52

Re: [SOLVED] Screen tearing when modesetting intel drivers

#5 2024-01-03 21:47:39

Re: [SOLVED] Screen tearing when modesetting intel drivers

#6 2024-01-03 21:54:55

Re: [SOLVED] Screen tearing when modesetting intel drivers

#7 2024-01-03 22:00:18

Re: [SOLVED] Screen tearing when modesetting intel drivers

#8 2024-01-03 22:08:21

Re: [SOLVED] Screen tearing when modesetting intel drivers

#9 2024-01-04 12:05:32

Re: [SOLVED] Screen tearing when modesetting intel drivers

#10 2024-01-04 15:52:55

Re: [SOLVED] Screen tearing when modesetting intel drivers

#11 2024-01-04 15:54:50

Re: [SOLVED] Screen tearing when modesetting intel drivers

#12 2024-01-04 16:05:46

Re: [SOLVED] Screen tearing when modesetting intel drivers

#13 2024-01-07 21:57:52

Re: [SOLVED] Screen tearing when modesetting intel drivers

Board footer