[SOLVED] Screen tearing issues out of the blue

radumitrescu · 2023-05-09 05:40:34

I have recently begun seeing weirdness on my system, and I think it has to do with (either or both) Gnome 44 and kernel 6.3 and xwayland. The weirdness I mention is screen tearing in games and color inconsistencies between apps when using a system-wide calibrated monitor profile, ie, some apps respect the colour profile, while others don't, which I suspect is due to xwayland, which appears to be in use:

Here is my system:

System:
  Kernel: 6.3.1-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
    parameters: BOOT_IMAGE=/vmlinuz-linux
    root=UUID=5e0ebfec-0da3-477c-94b3-25e509fb1aaf rw rootfstype=ext4
    loglevel=3
  Desktop: GNOME v: 44.1 tk: GTK v: 3.24.37 wm: gnome-shell dm: GDM v: 44.1
    Distro: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 82JM v: Legion 5 17ITH6H
    serial: <superuser required> Chassis: type: 10 v: Legion 5 17ITH6H
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: NO DPK serial: <superuser required>
    UEFI: LENOVO v: H1CN49WW date: 08/16/2022
Battery:
  ID-1: BAT0 charge: 46.7 Wh (56.0%) condition: 83.4/80.0 Wh (104.3%)
    volts: 15.4 min: 15.4 model: Celxpert L20C4PC2 type: Li-poly
    serial: <filter> status: not charging cycles: 8
CPU:
  Info: model: 11th Gen Intel Core i7-11800H bits: 64 type: MT MCP
    arch: Tiger Lake gen: core 11 level: v4 note: check built: 2020
    process: Intel 10nm family: 6 model-id: 0x8D (141) stepping: 1
    microcode: 0x42
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 10 MiB desc: 8x1.2 MiB
    L3: 24 MiB desc: 1x24 MiB
  Speed (MHz): avg: 2040 high: 2300 min/max: 800/4600 scaling:
    driver: intel_pstate governor: performance cores: 1: 1072 2: 2154 3: 2300
    4: 2236 5: 2205 6: 2300 7: 2300 8: 2300 9: 2300 10: 2300 11: 1721 12: 801
    13: 1787 14: 2300 15: 2300 16: 2279 bogomips: 73744
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS, IBPB:
    conditional, RSB filling, PBRSB-eIBRS: SW sequence
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel TigerLake-H GT1 [UHD Graphics] vendor: Lenovo driver: i915
    v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21 ports:
    active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5, HDMI-A-1
    bus-ID: 00:02.0 chip-ID: 8086:9a60 class-ID: 0300
  Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] vendor: Lenovo
    driver: nvidia v: 530.41.03 alternate: nouveau,nvidia_drm non-free: 530.xx+
    status: current (as of 2023-03) arch: Ampere code: GAxxx
    process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:2560 class-ID: 0300
  Device-3: Syntek Integrated Camera type: USB driver: uvcvideo
    bus-ID: 3-6:3 chip-ID: 174f:2459 class-ID: fe01 serial: <filter>
  Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.1
    compositor: gnome-shell driver: X: loaded: modesetting,nvidia
    alternate: fbdev,intel,nouveau,nv,vesa dri: iris gpu: i915 display-ID: :1
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: eDP-1 model: AU Optronics 0x449d built: 2018 res: 1920x1080
    hz: 144 dpi: 128 gamma: 1.2 size: 382x215mm (15.04x8.46")
    diag: 438mm (17.3") ratio: 16:9 modes: 1920x1080
  API: OpenGL v: 4.6 Mesa 23.0.3 renderer: Mesa Intel UHD Graphics (TGL GT1)
    direct-render: Yes
Audio:
  Device-1: Intel Tiger Lake-H HD Audio vendor: Lenovo driver: snd_hda_intel
    v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3
    chip-ID: 8086:43c8 class-ID: 0403
  Device-2: NVIDIA GA106 High Definition Audio driver: snd_hda_intel
    v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.1
    chip-ID: 10de:228e class-ID: 0403
  API: ALSA v: k6.3.1-arch1-1 status: kernel-api tools: N/A
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 0.3.70 status: off tools: pw-cli
  Server-3: PulseAudio v: 16.1 status: active tools: pacat,pactl
Network:
  Device-1: Intel Tiger Lake PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:43f0 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    port: 3000 bus-ID: 58:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp88s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 3-14:6 chip-ID: 8087:0026 class-ID: e001
  Report: bt-adapter note: tool can't run ID: hci0 rfk-id: 2 state: down
    bt-service: disabled rfk-block: hardware: no software: yes address: N/A
Drives:
  Local Storage: total: 1.16 TiB used: 616.98 GiB (52.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: SSD 970 EVO Plus 250GB size: 232.89 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 2B2QEXM7 temp: 38.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:3 vendor: SK Hynix model: HFS001TDE9X084N
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: 41010C22 temp: 36.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 232.38 GiB size: 227.68 GiB (97.97%)
    used: 22.77 GiB (10.0%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot raw-size: 511 MiB size: 510 MiB (99.80%)
    used: 94.8 MiB (18.6%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 4 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 33.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 351 Uptime: 33m wakeups: 1 Memory: 31.14 GiB
  used: 9.48 GiB (30.4%) Init: systemd v: 253 default: graphical
  tool: systemctl Compilers: gcc: 13.1.1 clang: 15.0.7 Packages: 1043
  pm: pacman pkgs: 1035 libs: 301 tools: gnome-software,pamac,yay pm: flatpak
  pkgs: 8 Shell: Bash v: 5.1.16 running-in: kgx inxi: 3.3.26

Last edited by radumitrescu (2023-05-17 05:10:19)

seth · 2023-05-09 05:54:24

You're running an X11 session, so you're not using xwayland at all.

Edit: otoh I'm not sure how reliably whatever stufffetch™ tool you used there is.

loginctl session-status

Last edited by seth (2023-05-09 05:56:28)

V1del · 2023-05-09 07:10:23

You're aware that the things affected by xwayland - should such a correlation be present - will simply not work at all anymore in a wayland session (and as stated, be irrelevant if you're on xorg in the first place)? FWIW since tearing (though what - exactly - is it you see? The term normally has a very clear definition but is generally thrown around willy nilly for artefacts that are not at all what's commonly referred to as tearing, so post a video/phone recording if the artifact is visible there) should rather not be present on a wayland session this will be a bug in gnome/mutter

The differences you see in respecting a color profile might simply be up to toolkit differences, actual examples of apps that don't or do have the issue and by which mechanism you are defining the color profile exactly?

Last edited by V1del (2023-05-09 07:14:18)

radumitrescu · 2023-05-09 07:18:20

seth wrote:

You're running an X11 session, so you're not using xwayland at all.
Edit: otoh I'm not sure how reliably whatever stufffetch™ tool you used there is.
loginctl session-status

The tool i used was inxi.

radumitrescu · 2023-05-09 07:24:35

V1del wrote:

You're aware that the things affected by xwayland - should such a correlation be present - will simply not work at all anymore in a wayland session (and as stated, be irrelevant if you're on xorg in the first place)? FWIW since tearing (though what - exactly - is it you see? The term normally has a very clear definition but is generally thrown around willy nilly for artefacts that are not at all what's commonly referred to as tearing, so post a video/phone recording if the artifact is visible there) should rather not be present on a wayland session this will be a bug in gnome/mutter
The differences you see in respecting a color profile might simply be up to toolkit differences, actual examples of apps that don't or do have the issue and by which mechanism you are defining the color profile exactly?

By screen tearing I mean exactly that. A shimmering horizontal line visible when the game frame rate is not in sync with the display frame rate, even though vsync is enabled.

As far as the second question goes, allow me to go into more detail.

For the longest time, the workflow I’m going to describe here worked just fine until a couple of days ago when for reasons unbeknownst to me it didn’t anymore.

Whenever I would do a fresh install, I would fire up DisplaCAL, calibrate my display and subsequently install the resulting .icc colour profile as system-wide. It would, very predictably, reflect this as correct when checking Gnome settings - the profile was loaded and activated.

I would then only need to check “Use system monitor profile” in both RawTherapee and GIMP and that was that - consistent colour across all apps.

However, this stopped being the case a couple of days ago and I don’t know why. Let me describe what is going on now.

Gimp is fine, as is Firefox and gthumb - they are all displaying images in the same maner, as expected.

It’s just RawTherapee that seems to behave strangely. Thumbnails in the browser window and the film-strip in the editor view are displayed with very saturated and vivid colours, nothing like they’re supposed to look like. I can, however, make it display correct colors if I switch the working profile from the default ProPhoto to sRGB or if I enable Soft Proofing underneath the main view in the editor. All this is not something that I had to do before and I find it weird.

seth · 2023-05-09 07:38:02

radumitrescu wrote:

The tool i used was inxi.

It actually says that and nobody asked for this information.

The part where're you're (likely, depending on how broken inxi is) not running a wayland session and hence are not using xwayland kinda escaped you?
…
Check your older journals on whether you were previously running gnome on wayland and then maybe try the behavior when explicitly selecting a wayland session.
Otherwise post your xorg log (because of the tearing) and detail on whether you maybe prime-run the game™

V1del · 2023-05-09 07:59:54

FWIW I happen to have it installed and checking it and the source it will actually say wayland on the Display: line (if WAYLAND_DISPLAY env is set, which I'd assume GDM would do) and not x11 so if that was previously a wayland session it isn't now (maybe the rules GDM uses for that have become yet more stringent?)

Regarding tearing with prime-run (and also whether it might previously have been a wayland session) is https://wiki.archlinux.org/title/NVIDIA … de_setting enabled? You'll generally want that for PRIME sync anyway.

Trilby · 2023-05-09 12:26:20

V1del wrote:

You're aware that the things affected by xwayland - should such a correlation be present - will simply not work at all anymore in a wayland session...

That's not entirely true. There are countless situations in which client programs can run natively on wayland, but if xwalayland is available they'll default to using that with many user configurations. It's a pet peeve of mine as it makes many users think they still "need" xwayland due to all their programs that run on xwayland when most / all of them would run just fine natively under wayland if they set it up properly.

Of course this distinction is not likely relevant here if the OP is running Xorg.

Last edited by Trilby (2023-05-09 12:27:17)

radumitrescu · 2023-05-09 16:34:11

Yes I am running the game with prime-run, and the games in question are Albion Online, an Open-GL, Linux native game and Crusader Kings III, yet another Linux-native game. The latter has been tested running in both Vulkan and OpenGL and the tearing is present in both scenarios.

I have added

 nvidia_drm.modeset=1

as a kernel parameter, but it seems to have had no effect.

Last edited by radumitrescu (2023-05-09 16:46:28)

seth · 2023-05-09 20:33:07

Check whether the tearing exist on the intel driver and whether prime-sync is enabled, https://wiki.archlinux.org/title/PRIME# … ronization
Also you've not addressed whether you've previously been running on wayland (ie. whether this is a regression or you changed the environment - cause the initial post certainly suggested the latter)

radumitrescu · 2023-05-10 04:48:17

seth wrote:

Also you've not addressed whether you've previously been running on wayland (ie. whether this is a regression or you changed the environment - cause the initial post certainly suggested the latter)

Let me first address the issue of whether or not I was previously running wayland. I am fairly confident in saying I have never used wayland, ever. I say this because, while I'm no expert, actually quite the opposite - I'm a bit of a noob, I am pretty good at searching the web and pasting commands, so that's how I've managed to run Linx for the past few years, having had zero training in the matter. My specific needs as a photographer, gamer and video editor, coupled with the fact that I've been using Optimus laptops since 2018, which can be finnicky to set up, have always made me rather aware of and specific about what and how I install on my machine. All this is to say that I am quite confident I have always run X and never Wayland.

Why the confusion? I asked about this issue I'm having on another forum and a user pointed out

Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.1

and said very matter-of-factly that I was wrong in saying I was using X. To be fair, that Xwayland bit in there threw me off and I just thought that perhaps it somehow got installed, without me knowing, maybe when kernel 6.3 was released, or with Gnome 44...

I hope this explains the confusion regarding Wayland.

seth wrote:

Check whether the tearing exist on the intel driver and whether prime-sync is enabled, https://wiki.archlinux.org/title/PRIME# … ronization

I checked and if I understand correctly, prime-sync is not enabled so I did what I understood from the wiki, but got this back.

xrandr --output eDP2 --set "PRIME Synchronization" 1
X Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  11 (RRQueryOutputProperty)
  Serial number of failed request:  72
  Current serial number in output stream:  72

I was not really sure what should go instead of <output-name> so I figured it must be my active display, which judging from xrandr --prop should be eDP2.

Here's the output:

xrandr --prop
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
eDP2 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 380mm x 220mm
	EDID: 
		00ffffffffffff0006af9d4400000000
		001c0104a5261678038915a4554ea028
		0d505400000001010101010101010101
		010101010101ce8f80b6703888403020
		a5007ed7100000180000000f00000000
		00000000000000000020000000fe0041
		554f0a202020202020202020000000fe
		004231373348414e30342e34200a0032
	BACKLIGHT: 96000 
		range: (0, 96000)
	Backlight: 96000 
		range: (0, 96000)
	vrr_capable: 0 
		range: (0, 1)
	Colorspace: Default 
		supported: Default, RGB_Wide_Gamut_Fixed_Point, RGB_Wide_Gamut_Floating_Point, opRGB, DCI-P3_RGB_D65, BT2020_RGB, BT601_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, BT2020_CYCC, BT2020_YCC
	max bpc: 12 
		range: (6, 12)
	Broadcast RGB: Automatic 
		supported: Automatic, Full, Limited 16:235
	panel orientation: Normal 
		supported: Normal, Upside Down, Left Side Up, Right Side Up
	scaling mode: Full aspect 
		supported: Full, Center, Full aspect
	link-status: Good 
		supported: Good, Bad
	non-desktop: 0 
		range: (0, 1)
   1920x1080    144.03*+
DP3 disconnected (normal left inverted right x axis y axis)
	HDCP Content Type: HDCP Type0 
		supported: HDCP Type0, HDCP Type1
	Content Protection: Undesired 
		supported: Undesired, Desired, Enabled
	vrr_capable: 0 
		range: (0, 1)
	Colorspace: Default 
		supported: Default, RGB_Wide_Gamut_Fixed_Point, RGB_Wide_Gamut_Floating_Point, opRGB, DCI-P3_RGB_D65, BT2020_RGB, BT601_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, BT2020_CYCC, BT2020_YCC
	max bpc: 12 
		range: (6, 12)
	Broadcast RGB: Automatic 
		supported: Automatic, Full, Limited 16:235
	audio: auto 
		supported: force-dvi, off, auto, on
	subconnector: Unknown 
		supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native
	link-status: Good 
		supported: Good, Bad
	non-desktop: 0 
		range: (0, 1)
DP4 disconnected (normal left inverted right x axis y axis)
	HDCP Content Type: HDCP Type0 
		supported: HDCP Type0, HDCP Type1
	Content Protection: Undesired 
		supported: Undesired, Desired, Enabled
	vrr_capable: 0 
		range: (0, 1)
	Colorspace: Default 
		supported: Default, RGB_Wide_Gamut_Fixed_Point, RGB_Wide_Gamut_Floating_Point, opRGB, DCI-P3_RGB_D65, BT2020_RGB, BT601_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, BT2020_CYCC, BT2020_YCC
	max bpc: 12 
		range: (6, 12)
	Broadcast RGB: Automatic 
		supported: Automatic, Full, Limited 16:235
	audio: auto 
		supported: force-dvi, off, auto, on
	subconnector: Unknown 
		supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native
	link-status: Good 
		supported: Good, Bad
	non-desktop: 0 
		range: (0, 1)
DP5 disconnected (normal left inverted right x axis y axis)
	HDCP Content Type: HDCP Type0 
		supported: HDCP Type0, HDCP Type1
	Content Protection: Undesired 
		supported: Undesired, Desired, Enabled
	vrr_capable: 0 
		range: (0, 1)
	Colorspace: Default 
		supported: Default, RGB_Wide_Gamut_Fixed_Point, RGB_Wide_Gamut_Floating_Point, opRGB, DCI-P3_RGB_D65, BT2020_RGB, BT601_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, BT2020_CYCC, BT2020_YCC
	max bpc: 12 
		range: (6, 12)
	Broadcast RGB: Automatic 
		supported: Automatic, Full, Limited 16:235
	audio: auto 
		supported: force-dvi, off, auto, on
	subconnector: Unknown 
		supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native
	link-status: Good 
		supported: Good, Bad
	non-desktop: 0 
		range: (0, 1)
DP6 disconnected (normal left inverted right x axis y axis)
	HDCP Content Type: HDCP Type0 
		supported: HDCP Type0, HDCP Type1
	Content Protection: Undesired 
		supported: Undesired, Desired, Enabled
	vrr_capable: 0 
		range: (0, 1)
	Colorspace: Default 
		supported: Default, RGB_Wide_Gamut_Fixed_Point, RGB_Wide_Gamut_Floating_Point, opRGB, DCI-P3_RGB_D65, BT2020_RGB, BT601_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, BT2020_CYCC, BT2020_YCC
	max bpc: 12 
		range: (6, 12)
	Broadcast RGB: Automatic 
		supported: Automatic, Full, Limited 16:235
	audio: auto 
		supported: force-dvi, off, auto, on
	subconnector: Unknown 
		supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native
	link-status: Good 
		supported: Good, Bad
	non-desktop: 0 
		range: (0, 1)
DP7 disconnected (normal left inverted right x axis y axis)
	HDCP Content Type: HDCP Type0 
		supported: HDCP Type0, HDCP Type1
	Content Protection: Undesired 
		supported: Undesired, Desired, Enabled
	vrr_capable: 0 
		range: (0, 1)
	Colorspace: Default 
		supported: Default, RGB_Wide_Gamut_Fixed_Point, RGB_Wide_Gamut_Floating_Point, opRGB, DCI-P3_RGB_D65, BT2020_RGB, BT601_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, BT2020_CYCC, BT2020_YCC
	max bpc: 12 
		range: (6, 12)
	Broadcast RGB: Automatic 
		supported: Automatic, Full, Limited 16:235
	audio: auto 
		supported: force-dvi, off, auto, on
	subconnector: Unknown 
		supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native
	link-status: Good 
		supported: Good, Bad
	non-desktop: 0 
		range: (0, 1)
HDMI2 disconnected (normal left inverted right x axis y axis)
	HDCP Content Type: HDCP Type0 
		supported: HDCP Type0, HDCP Type1
	Content Protection: Undesired 
		supported: Undesired, Desired, Enabled
	max bpc: 12 
		range: (8, 12)
	content type: No Data 
		supported: No Data, Graphics, Photo, Cinema, Game
	Colorspace: Default 
		supported: Default, SMPTE_170M_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, opRGB, BT2020_CYCC, BT2020_RGB, BT2020_YCC, DCI-P3_RGB_D65, DCI-P3_RGB_Theater
	aspect ratio: Automatic 
		supported: Automatic, 4:3, 16:9
	Broadcast RGB: Automatic 
		supported: Automatic, Full, Limited 16:235
	audio: auto 
		supported: force-dvi, off, auto, on
	link-status: Good 
		supported: Good, Bad
	non-desktop: 0 
		range: (0, 1)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
	non-desktop: 0 
		supported: 0, 1
DP-1-0 disconnected (normal left inverted right x axis y axis)
	PRIME Synchronization: 1 
		supported: 0, 1
	CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 
		0 1 
	CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0 
	BorderDimensions: 4 
		supported: 4
	Border: 0 0 0 0 
		range: (0, 65535)
	SignalFormat: DisplayPort 
		supported: DisplayPort
	ConnectorType: DisplayPort 
	ConnectorNumber: 1 
	_ConnectorLocation: 1 
	non-desktop: 0 
		supported: 0, 1
DP-1-1 disconnected (normal left inverted right x axis y axis)
	PRIME Synchronization: 1 
		supported: 0, 1
	CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 
		0 1 
	CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0 
	BorderDimensions: 4 
		supported: 4
	Border: 0 0 0 0 
		range: (0, 65535)
	SignalFormat: TMDS 
		supported: TMDS
	ConnectorType: DisplayPort 
	ConnectorNumber: 1 
	_ConnectorLocation: 1 
	non-desktop: 0 
		supported: 0, 1
DP-1-2 disconnected (normal left inverted right x axis y axis)
	PRIME Synchronization: 1 
		supported: 0, 1
	CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 
		0 1 
	CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0 
	BorderDimensions: 4 
		supported: 4
	Border: 0 0 0 0 
		range: (0, 65535)
	SignalFormat: DisplayPort 
		supported: DisplayPort
	ConnectorType: DisplayPort 
	ConnectorNumber: 2 
	_ConnectorLocation: 2 
	non-desktop: 0 
		supported: 0, 1
DP-1-3 disconnected (normal left inverted right x axis y axis)
	PRIME Synchronization: 1 
		supported: 0, 1
	CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 
		0 1 
	CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0 
	BorderDimensions: 4 
		supported: 4
	Border: 0 0 0 0 
		range: (0, 65535)
	SignalFormat: TMDS 
		supported: TMDS
	ConnectorType: DisplayPort 
	ConnectorNumber: 2 
	_ConnectorLocation: 2 
	non-desktop: 0 
		supported: 0, 1
HDMI-1-0 disconnected (normal left inverted right x axis y axis)
	PRIME Synchronization: 1 
		supported: 0, 1
	CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 
		0 1 
	CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0 
	BorderDimensions: 4 
		supported: 4
	Border: 0 0 0 0 
		range: (0, 65535)
	SignalFormat: TMDS 
		supported: TMDS
	ConnectorType: HDMI 
	ConnectorNumber: 3 
	_ConnectorLocation: 3 
	non-desktop: 0 
		supported: 0, 1
DP-1-4 disconnected (normal left inverted right x axis y axis)
	PRIME Synchronization: 1 
		supported: 0, 1
	CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 
		0 1 
	CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0 
	BorderDimensions: 4 
		supported: 4
	Border: 0 0 0 0 
		range: (0, 65535)
	SignalFormat: DisplayPort 
		supported: DisplayPort
	ConnectorType: Panel 
	ConnectorNumber: 0 
	_ConnectorLocation: 0 
	non-desktop: 0 
		supported: 0, 1

Another thing I noticed, that might be worth mentioning, is that although I set nvidia_drm.modeset=1 as a kernel parameter inxi reports modesetting as not loaded

Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.1
    compositor: gnome-shell driver: X: loaded: intel,nvidia
    unloaded: modesetting alternate: fbdev,nouveau,nv,vesa dri: iris gpu: i915
    display-ID: :1 screens: 1

I even added the modules nvidia, nvidia_modeset, nvidia_uvm and nvidia_drm to the initramfs to make them load early, but nothing helped.

I should perhaps mention that this issue was not something I encountered when I ran Gnome 43 and kernel 6.2.x, and I should also mention that NobaraOS, which is based on Fedora and runs Gnome 43 and kernel 6.2.9 also doesn't exhibit this issue.

Last edited by radumitrescu (2023-05-10 06:47:15)

radumitrescu · 2023-05-10 05:50:56

Oops, miss-quoted myself, please delete.

Last edited by radumitrescu (2023-05-10 05:52:38)

seth · 2023-05-10 06:04:06

Another thing I noticed, that might be worth mentioning, is that although I set nvidia_drm.modeset=1 as a kernel parameter inxi reports modesetting as not loaded

cat /proc/cmdline

However what inxi reports is actually

compositor: gnome-shell driver: X: loaded: intel,nvidia
unloaded: modesetting alternate: fbdev,nouveau,nv,vesa dri: iris gpu: i915

What refers to the ddx drivers (modesetting vs intel) and the firstmost step should be to remove xf86-video-intel which you apparently have installed in the meantime, likely because I phrased this badly

Check whether the tearing exist on the intel driver

What I meant was to try the behavior w/o prime-run

radumitrescu · 2023-05-10 10:37:25

seth wrote:

cat /proc/cmdline

cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux root=UUID=5290e34e-94d2-4b1f-90d7-685fb4b46aa6 rw rootfstype=ext4 loglevel=3 nvidia_drm.modeset=1

seth wrote:

try the behavior w/o prime-run

Do you mean to switch off of hybrid graphics and try the dGPU only mode? Or do you mean to try and run the game on the Intel GPU?

later edit:

So I tried all options: running the game on hybrid graphics mode without prime-run. Poor peformance and still tearing. Then I went into BIOS and switched to discrete graphics mode. Then I tried running the game (first time, by mistake) with prime-run, which gave really bad stuttering, and slightly lower framerates (100-120 instead of the usuall 144 capped) than on switchable graphics with prime-run. Finally I tried running the game without prime-run, still on discrete graphics and this still gave me the same tearing. So no matter what I try, it seems to behave the same.

And yes, I have removed xf86-video-intel.

Last edited by radumitrescu (2023-05-10 11:12:52)

seth · 2023-05-10 12:16:06

Do you get tearing in an openbox session (ie. w/o the gnome compositor)?

radumitrescu · 2023-05-10 16:55:37

seth wrote:

Do you get tearing in an openbox session (ie. w/o the gnome compositor)?

I wouldn't even know how to begin trying that...

seth · 2023-05-10 17:04:43

You install and start openbox? instead of gnome?

radumitrescu · 2023-05-10 17:17:31

seth wrote:

You install and start openbox? instead of gnome?

Uhm... OK... I'm still confused, because I don't ever start gnome. I just turn on my computer and gnome is there... How, specifically, do I start openbox instead of gnome?

seth · 2023-05-10 17:42:43

How did you install archlinux?

radumitrescu · 2023-05-10 18:05:39

seth wrote:

How did you install archlinux?

Via the archinstal script.

And I should add, fwiw, I am pretty confident this is a Gnome issue.

I did a fresh install of Arch with KDE earlier, all vanilla settings, no additional configs, no kernel parameters, no nothing, just what the script installs, and the tearing issue is not present.

Last edited by radumitrescu (2023-05-10 18:10:54)

seth · 2023-05-11 07:15:45

The archinstall script configures https://wiki.archlinux.org/title/GDM#Automatic_login ??
Well, unconfigure that.

radumitrescu · 2023-05-11 07:30:46

seth wrote:

The archinstall script configures https://wiki.archlinux.org/title/GDM#Automatic_login ??
Well, unconfigure that.

Seeing how apparently I am often misunderstood, there may be a bit of a language barrier here, as English is not my mother tongue.

I didn't say the archinstall script configures auto login, merely that it installs and configures Gnome and that I don't have to manually start it. I just turn of my computer and Gnome just starts by default. No configuration required, no manual starting required.

seth · 2023-05-11 07:52:53

I just turn of my computer and Gnome just starts by default.

Means autologin is enabled. Who or what enabled it, I cannot know and you apparently don't either.
The most liekly explanation would be that this isn't actually archlinux…

radumitrescu · 2023-05-11 08:12:20

seth wrote:

I just turn of my computer and Gnome just starts by default.
Means autologin is enabled. Who or what enabled it, I cannot know and you apparently don't either.
The most liekly explanation would be that this isn't actually archlinux…

No, it doesn't mean that. Gnome, as the DE starts automatically, but I still have to enter my password to login.

And it is very much so archlinux.

Last edited by radumitrescu (2023-05-11 08:12:41)

seth · 2023-05-11 08:15:35

Thats not gnome but GDM and you can select a different session there type there.

And it is very much so archlinux.

And you've still no idea about the most basic stuff.

Arch Linux

#1 2023-05-09 05:40:34

[SOLVED] Screen tearing issues out of the blue

#2 2023-05-09 05:54:24

Re: [SOLVED] Screen tearing issues out of the blue

#3 2023-05-09 07:10:23

Re: [SOLVED] Screen tearing issues out of the blue

#4 2023-05-09 07:18:20

Re: [SOLVED] Screen tearing issues out of the blue

#5 2023-05-09 07:24:35

Re: [SOLVED] Screen tearing issues out of the blue

#6 2023-05-09 07:38:02

Re: [SOLVED] Screen tearing issues out of the blue

#7 2023-05-09 07:59:54

Re: [SOLVED] Screen tearing issues out of the blue

#8 2023-05-09 12:26:20

Re: [SOLVED] Screen tearing issues out of the blue

#9 2023-05-09 16:34:11

Re: [SOLVED] Screen tearing issues out of the blue

#10 2023-05-09 20:33:07

Re: [SOLVED] Screen tearing issues out of the blue

#11 2023-05-10 04:48:17

Re: [SOLVED] Screen tearing issues out of the blue

#12 2023-05-10 05:50:56

Re: [SOLVED] Screen tearing issues out of the blue

#13 2023-05-10 06:04:06

Re: [SOLVED] Screen tearing issues out of the blue

#14 2023-05-10 10:37:25

Re: [SOLVED] Screen tearing issues out of the blue

#15 2023-05-10 12:16:06

Re: [SOLVED] Screen tearing issues out of the blue

#16 2023-05-10 16:55:37

Re: [SOLVED] Screen tearing issues out of the blue

#17 2023-05-10 17:04:43

Re: [SOLVED] Screen tearing issues out of the blue

#18 2023-05-10 17:17:31

Re: [SOLVED] Screen tearing issues out of the blue

#19 2023-05-10 17:42:43

Re: [SOLVED] Screen tearing issues out of the blue

#20 2023-05-10 18:05:39

Re: [SOLVED] Screen tearing issues out of the blue

#21 2023-05-11 07:15:45

Re: [SOLVED] Screen tearing issues out of the blue

#22 2023-05-11 07:30:46

Re: [SOLVED] Screen tearing issues out of the blue

#23 2023-05-11 07:52:53

Re: [SOLVED] Screen tearing issues out of the blue

#24 2023-05-11 08:12:20

Re: [SOLVED] Screen tearing issues out of the blue

#25 2023-05-11 08:15:35

Re: [SOLVED] Screen tearing issues out of the blue

Board footer