Screen Tear issue

Issues & Assistance Newbies
1

Hello,

I have a fresh install of the Garuda Dragonized edition, and I am having an issue with my Desktop, everything else works flawlessly and it is a treat to look at.
There is a tear in the windows of the system around the 1080p mark so one third of the screen from the bottom seems to missalign with the top while draging , scrolling and video playback, the monitor question is a 1440p ultrawide dell monitor.
I would love to show it through screenshots but the issue is not captured by the tool.
Naturally I though this is an issue of my Monitor, which is brand new 2 days old, and DOA issues are always a possiblity.
Following that i boot into windows and all is fine, no tear no graphical issue.
The install of the Garuda OS is fresh, only thing I did so far, is install the archer tu2 plus drivers
and apps through the garuda assistant.

Can anyone help ? I am also unsure what I am supposed to post from terminal that would be relevant ot your issue. But here is the specifications

OS: Garuda Linux
Kernel: 5.15.3-zen1-1-zen
Uptime: 11 hours, 32 mins
Packages: 1434 (pacman)
Shell: bash
DE: Plasma 5.23.3
WM: KWin
WM Theme: Sweet-Dark
Terminal: konsole
CPU: AMD Ryzen 9 3900X (24) @ 3.8GHz
GPU: AMD ATI Radeon RX 6700/6700 XT / 6800M
Memory: 8.89GiB / 31.32GiB

Also I would like to state I am a fresh user of any for of Arch Previously I was on Linux Mint.

Thank all who spare some time for me.

2

kindly provide the output of inxi -Faz in a proper format as told in the new post template.

1 Like
3

Garuda (and Arch generally) has been pretty good for me when it comes to automatically dealing with screen tear, but if you're having problems it might be worth checking out the following: AMDGPU - ArchWiki

1 Like
4

Thank you for your reply. Below the output for checking purposes.

I think, i solved the issue, it was of course something tiny and a stupid oversight on my part.

The display config has defaulted to 60HZ instead of 144hz. Reconfiguring the screen at 120 hz seem to have resolved the issue.

I was confused mainly because the tear happened always, only and consistently along the same line, the aforementioned 1080p line counted from above.

Reading through the inxi -Faz File i see the driver is for 6800/xt series gpu, while my gpu is sthe 6700XT I doubt it might affect the system as I presume the drivers are always made for the top of the line and below instead of per gpu basis.

Can someone confirm this ?

System:    Kernel: 5.15.3-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=02520476-020d-42fb-b534-ba28f5e8bcbf
rw rootflags=subvol=@ quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3
Desktop: KDE Plasma 5.23.3 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME X570-PRO v: Rev X.0x serial: <filter>
UEFI: American Megatrends v: 4021 date: 08/09/2021
CPU:       Info: 12-Core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 2 family: 17 (23)
model-id: 71 (113) stepping: 0 microcode: 8701021 cache: L2: 6 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 182043
Speed: 3617 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz): 1: 3617 2: 3597
3: 3592 4: 3593 5: 3588 6: 4090 7: 3686 8: 3805 9: 3726 10: 3634 11: 3584 12: 3432 13: 3601
14: 3891 15: 3700 16: 4013 17: 3595 18: 4200 19: 4045 20: 4261 21: 3850 22: 3555 23: 3599
24: 3879
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown 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: Full AMD retpoline, IBPB: conditional, STIBP: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:  Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT / 6800M] vendor: Tul driver: amdgpu v: kernel
bus-ID: 0a:00.0 chip-ID: 1002:73df class-ID: 0300
Display: x11 server: X.Org 1.21.1.1 compositor: kwin_x11 driver: loaded: amdgpu,ati
unloaded: modesetting,radeon alternate: fbdev,vesa display-ID: :0 screens: 1
Screen-1: 0 s-res: 3440x1440 s-dpi: 96 s-size: 910x381mm (35.8x15.0") s-diag: 987mm (38.8")
Monitor-1: DisplayPort-2 res: 3440x1440 dpi: 110 size: 797x334mm (31.4x13.1") diag: 864mm (34")
OpenGL:
renderer: AMD Radeon RX 6700 XT (NAVY_FLOUNDER DRM 3.42.0 5.15.3-zen1-1-zen LLVM 13.0.0)
v: 4.6 Mesa 21.2.5 direct render: Yes
Audio:     Device-1: AMD Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT] driver: snd_hda_intel
v: kernel bus-ID: 0a:00.1 chip-ID: 1002:ab28 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus-ID: 0c:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Logitech G733 Gaming Headset type: USB driver: hid-generic,snd-usb-audio,usbhid
bus-ID: 5-4:5 chip-ID: 046d:0ab5 class-ID: 0300
Sound Server-1: ALSA v: k5.15.3-zen1-1-zen running: yes
Sound Server-2: JACK v: 1.9.19 running: no
Sound Server-3: PulseAudio v: 15.0 running: no
Sound Server-4: PipeWire v: 0.3.40 running: yes
Network:   Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel port: f000
bus-ID: 04:00.0 chip-ID: 8086:1539 class-ID: 0200
IF: enp4s0 state: down mac: <filter>
Device-2: TP-Link Archer T2U PLUS [RTL8821AU] type: USB driver: rtl8821au bus-ID: 1-1.3:3
chip-ID: 2357:0120 class-ID: 0000 serial: <filter>
IF: wlp5s0f1u1u3 state: up mac: <filter>
Bluetooth: Device-1: D-Link System DBT-120 Bluetooth Adapter type: USB driver: btusb v: 0.8 bus-ID: 5-1:2
chip-ID: 07d1:fc01 class-ID: fe01
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:    Local Storage: total: 689.33 GiB used: 21.56 GiB (3.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: HP model: SSD EX900 500GB size: 465.76 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: S0614B0 temp: 49.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Kingston model: SUV400S37240G size: 223.57 GiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 87RA
scheme: GPT
Partition: ID-1: / raw-size: 223.27 GiB size: 223.27 GiB (100.00%) used: 21.56 GiB (9.7%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 576 KiB (0.2%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 223.27 GiB size: 223.27 GiB (100.00%) used: 21.56 GiB (9.7%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 223.27 GiB size: 223.27 GiB (100.00%) used: 21.56 GiB (9.7%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 223.27 GiB size: 223.27 GiB (100.00%) used: 21.56 GiB (9.7%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.32 GiB used: 2.2 MiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:   Message: No sensor data found. Is lm-sensors configured?
Info:      Processes: 463 Uptime: 12h 4m wakeups: 0 Memory: 31.32 GiB used: 9.41 GiB (30.1%) Init: systemd
v: 249 tool: systemctl Compilers: gcc: 11.1.0 clang: 13.0.0 Packages: pacman: 1434 lib: 432
Shell: fish v: 3.3.1 default: Bash v: 5.1.8 running-in: konsole inxi: 3.3.08
5

you can check screen tear properly on https://www.vsynctester.com/
also you can check your refresh rate https://www.displayhz.com/ (might not work with firefox and derivatives)
these will help you making sure your display is fixed.

4 Likes
6

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.