Monitor blanking issue after changing video settings

So, ever since I switched over to Garuda linux as my daily driver early last year, I have had this aggrevating issue… I use a 4k monitor via a VESA certified displayport, and whenever I have the desktop resolution at full, the screen blanks out for a second or two at random intervals… It hasn’t been a big deal cuz when I set it to 2560x1440, I don’t have any such issues… Until yesturday…

I thought I might as well check to see if a recent update may have fixed the problem, so I switched to 4k, messed around a little bit… And then when it was clear nothing changed, I switched back to the other resolution… But this time it decided to bring the glitch with it… So now, I have to figure this out because my computer is barely usable. To add to this, it seems to have developed some new consistancies at this lower resolution. It blanks whenever I bring up that window menu through the top left corner, and it goes wild blanking when certain windows are maximized, esp Pamac for some bizarre reason. It still does it randomly too. But it won’t do it at all when certain applications like VLC are fullscreened… I have been searching everywhere for even a place to start figuring ou what is going on without much luck, and so after gaining a blistering headache from it all, I signed up here…

I have an AMD R9 390 GPU, and a Z-Edge 4k monitor. I also have an old 1440x900 Viewsonic via DVI as a secondary monitor that I mostly use for widgets so I can keep an eye on temps, activity, etc. at a glance. I am using the default Zen Kernel, and the KDE Plasma 6 Desktop Environment with the default Dragonized setup.

I know this isn’t a hardware issue because I do technically dual boot Windows (I only have a small partition of 10 for like 2 things.) and in spite of having it at full resolution and refresh rate, I have had zero blanking problems, wven after this expanded version started. It also doesn’t happen in X11 at my normal res (though still does in 4k)

I’ve tried messing more with the video settings lowering the DPI scaling to 100%, etc, but I’m genuinely at a loss… I even checked to make sure it hadn’t reset my prioritizing of the AMDGPU drivers over the Radeon ones through the GRUB menu, but no… So if anyone has any knowledge or can at least give me an idea of where to start, please let me know.

It could simply be the DP-cable. With a cheap DP-cable it happens often for me. It picks up electric disturbances very easily, like opening microwave door, turning on a CFL-light, etc, and monitor gets no signal for a second or two.

I feel like if it was merely the DP cable, it would be consistant regardless of settings and completely random… It might explain the way it functions on X11, blanking only on full 4k, but it doesn’t explain the issues on Wayland… I can literally deliberately trigger it by simply maximizing Pamac. And it does it every so often, even at the resolutions that run flawlessly on X11… I really want to keep using Wayland, but it’s just unusable right now, and all that changed was I changed the resolution to 4k, and then changed it back… That’s the only difference between it worki g flawlessly and bugging out… I’d try to reinstall Wayland, see if that fixes it, but it’s built into KDE, so that’s just gonna break everything…

Does it do the same on the other DP ports of the gpu? Have you tried the mesa-tkg-git driver?

The best thing to do is to start by posting your garuda-inxi. That way we would have all the information we need about your hardware, drivers and the exact model of the monitor. That makes it easier to help.

Furthermore, Linux is not Windows - just because something works on Windows doesn’t mean it will work on Linux.

You have an old R9 390 with 1x DisplayPort 1.2 - maybe Linux doesn’t like the fact that your unknown monitor model may have a different DP version set or that 4K doesn’t work properly for some other reason. And obviously it hasn’t worked for over a year…if there is a problem you fix it immediately and don’t wait until it gets worse btw…


Edit: Take a look on this:

This may not be the same, but it gets the idea across for your troubleshooting.

2 Likes

I only have one displayport on my GPU…

Sorry, been busy a few days, I will post that when I find the time. And thing is, it hasn’t gotten worse so to speak. It just has started happening on Wayland at lower resolutions. TBH I think it might be two seperate issues. I’ll check out that other post as well. Thank you.

On the monitor itself in its menu can you set the display port version on my lg the option is in menu → general an lets me pick from dp 1.0 on up

Are you on kde 6.1 turn off adaptive sync tell me if it does anything

I can’t find such an option in my monitor’s display settings…

Yes, I am, and I did that, and no change.

As for my inxi

System:
Kernel: 6.9.5-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=d350dd15-d185-412d-b75a-6ce316958c35 rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
amdgpu.si_support=1 amdgpu.cik_support=1 radeon.si_support=0
radeon.cik_support=0 ibt=off
Desktop: KDE Plasma v: 6.1.0 tk: Qt v: N/A info: frameworks v: 6.3.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: M5A97 R2.0 v: Rev 1.xx
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 2601 date: 03/24/2015
CPU:
Info: model: AMD FX-6300 bits: 64 type: MCP arch: Piledriver level: v2
built: 2012-13 process: GF 32nm family: 0x15 (21) model-id: 2 stepping: 0
microcode: 0x6000852
Topology: cpus: 1x cores: 6 smt: <unsupported> cache: L1: 288 KiB
desc: d-6x16 KiB; i-3x64 KiB L2: 6 MiB desc: 3x2 MiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 1894 high: 3793 min/max: 1400/3500 boost: enabled
scaling: driver: acpi-cpufreq governor: ondemand cores: 1: 1572 2: 1400
3: 1517 4: 1683 5: 1400 6: 3793 bogomips: 45513
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Hawaii PRO [Radeon R9 290/390] vendor: Micro-Star MSI
driver: amdgpu v: kernel alternate: radeon arch: GCN-2 code: Sea Islands
process: GF/TSMC 16-28nm built: 2013-17 pcie: gen: 2 speed: 5 GT/s
lanes: 16 link-max: gen: 3 speed: 8 GT/s ports: active: DP-1,DVI-D-1
empty: DVI-D-2,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 1002:67b1 class-ID: 0300
temp: 49.0 C
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.0
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu d-rect: 2859x960 display-ID: 0
Monitor-1: DP-1 pos: primary,left res: 1707x960 size: N/A modes: N/A
Monitor-2: DVI-D-1 pos: right res: 1152x720 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
drv: radeonsi inactive: gbm
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.1.1-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon R9 390 Series (radeonsi
hawaii LLVM 17.0.6 DRM 3.57 6.9.5-zen1-1-zen) device-ID: 1002:67b1
memory: 7.81 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 13 device: 0 type: discrete-gpu name: AMD
Radeon R9 390 Series (RADV HAWAII) driver: mesa radv v: 24.1.1-arch1.1
device-ID: 1002:67b1 surfaces: xcb,xlib,wayland device: 1 type: cpu
name: llvmpipe (LLVM 17.0.6 256 bits) driver: mesa llvmpipe
v: 24.1.1-arch1.1 (LLVM 17.0.6) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: AMD SBx00 Azalia vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus-ID: 00:14.2 chip-ID: 1002:4383 class-ID: 0403
Device-2: AMD Hawaii HDMI Audio [Radeon R9 290/290X / 390/390X]
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.1
chip-ID: 1002:aac8 class-ID: 0403
Device-3: Corsair VOID PRO Wireless Gaming Headset
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 10-2:2 chip-ID: 1b1c:0a1a class-ID: 0300
API: ALSA v: k6.9.5-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 1.0.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK P8 series driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 02:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: pvpnksintrf1 state: unknown speed: N/A duplex: N/A mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd
Bluetooth:
Device-1: Broadcom BCM20702A0 Bluetooth 4.0 driver: btusb v: 0.8 type: USB
rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 7-2:2 chip-ID: 0a5c:21e8
class-ID: fe01 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
rfk-block: hardware: no software: no address: <filter> bt-v: 4.0 lmp-v: 6
status: discoverable: no pairing: no
Drives:
Local Storage: total: 2.73 TiB used: 2.4 TiB (87.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WDS100T2B0A-00SM50 size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 00WD
scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WDS100T2G0A-00JH30 size: 931.52 GiB block-size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 0000
scheme: MBR
ID-3: /dev/sdc maj-min: 8:32 vendor: Western Digital model: WDS100T2B0A
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 90WD scheme: GPT
Partition:
ID-1: / raw-size: 773.3 GiB size: 773.3 GiB (100.00%)
used: 684.53 GiB (88.5%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 25.9 MiB (26.9%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 773.3 GiB size: 773.3 GiB (100.00%)
used: 684.53 GiB (88.5%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
ID-4: /var/log raw-size: 773.3 GiB size: 773.3 GiB (100.00%)
used: 684.53 GiB (88.5%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
ID-5: /var/tmp raw-size: 773.3 GiB size: 773.3 GiB (100.00%)
used: 684.53 GiB (88.5%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15.53 GiB used: 153.8 MiB (1.0%)
priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 6
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 37.0 C mobo: 30.0 C gpu: amdgpu temp: 49.0 C
Fan Speeds (rpm): cpu: 1383 fan-2: 0 fan-3: 1175 gpu: amdgpu fan: 1919
Power: 12v: N/A 5v: N/A 3.3v: 3.22 vbat: 3.29 gpu: amdgpu watts: 42.19
Info:
Memory: total: 16 GiB available: 15.53 GiB used: 2.62 GiB (16.9%)
Processes: 253 Power: uptime: 1m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 6.19 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: 2191 pm: pacman pkgs: 2151 libs: 592 tools: paru pm: flatpak
pkgs: 40 Compilers: clang: 17.0.6 gcc: 14.1.1 Shell: garuda-inxi
default: Bash v: 5.2.26 running-in: konsole inxi: 3.3.34
Garuda (2.6.26-1):
System install date:     2023-07-12
Last full system update: 2024-06-20
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:            fancontrol.service

Edit: I just noticed that it is listing the resolutions of my monitors wrong… That seems really bizarre… It seems to list them correctly on X11, so maybe that’s a hint?

Yes, use X11 and wait for upstream Nvidia fixes :slight_smile:

2 Likes

Nvidia fixes? But my card’s AMD. Am I missing something?

No, it looks like I need more sleep or coffee. :smiling_face:

2 Likes

I’m having the same problem. Whenever I switch 144hz my screen starts to blinking if there is a change on the screen. So right now I’m using at 120hz. 120hz more stable than 144hz but when I fullscreen a program it turns black then gets normal. I tested with different HDMI cables it still happening but noticed something that if I boot garuda iso there is no problem. I also use AMD and there is my garuda-inxi:

System:
Kernel: 6.9.5-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=d52237ff-a7a0-4331-8886-9ee88dd36458 rw rootflags=subvol=@
quiet resume=UUID=cd40837e-8789-45da-9064-aa348baee28e loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.1.0 tk: Qt v: N/A info: frameworks v: 6.3.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: PRIME B550M-K v: Rev X.0x
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 2803 date: 04/28/2022
CPU:
Info: model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 2 microcode: 0xA20120A
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 3674 high: 3700 min/max: 2200/4650 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3700 2: 3700
3: 3700 4: 3700 5: 3648 6: 3700 7: 3700 8: 3700 9: 3635 10: 3598 11: 3700
12: 3617 bogomips: 88797
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] vendor: ASUSTeK
driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm)
built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
active: HDMI-A-1 empty: DP-1, DP-2, DP-3, Writeback-1 bus-ID: 0d:00.0
chip-ID: 1002:73bf class-ID: 0300
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.0
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: 0
Monitor-1: HDMI-A-1 res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
drv: radeonsi inactive: gbm
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.1.1-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6800 (radeonsi navi21
LLVM 17.0.6 DRM 3.57 6.9.5-zen1-1-zen) device-ID: 1002:73bf
memory: 15.62 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 13 device: 0 type: discrete-gpu name: AMD
Radeon RX 6800 (RADV NAVI21) driver: mesa radv v: 24.1.1-arch1.1
device-ID: 1002:73bf surfaces: xcb,xlib,wayland device: 1 type: cpu
name: llvmpipe (LLVM 17.0.6 256 bits) driver: mesa llvmpipe
v: 24.1.1-arch1.1 (LLVM 17.0.6) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0d:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0f:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: ASUSTek ROG DELTA S driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 1.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-4:2
chip-ID: 0b05:1943 class-ID: 0300
API: ALSA v: k6.9.5-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.0.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 06:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp6s0 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK RTL8111H driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 0a:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp10s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-8:5 chip-ID: 8087:0029
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
rfk-block: hardware: no software: no address: <filter> bt-v: 5.2 lmp-v: 11
status: discoverable: no pairing: no
Drives:
Local Storage: total: 2.3 TiB used: 104.09 GiB (4.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: WD Blue SN570 500GB size: 465.76 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 234110WD temp: 39.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000DM008-2UB102
size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: 0001 scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: SanDisk model: Cruzer Blade
size: 29.25 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 2.0 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter>
fw-rev: 1.00 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 448.39 GiB size: 448.39 GiB (100.00%)
used: 104.09 GiB (23.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 448.39 GiB size: 448.39 GiB (100.00%)
used: 104.09 GiB (23.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 448.39 GiB size: 448.39 GiB (100.00%)
used: 104.09 GiB (23.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 448.39 GiB size: 448.39 GiB (100.00%)
used: 104.09 GiB (23.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15.53 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
ID-2: swap-2 type: partition size: 17.08 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
System Temperatures: cpu: 46.5 C mobo: N/A gpu: amdgpu temp: 46.0 C
mem: 46.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Memory: total: 16 GiB available: 15.53 GiB used: 3.02 GiB (19.5%)
Processes: 353 Power: uptime: 0m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 6.2 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 2009 libs: 583 tools: octopi,paru Compilers:
clang: 17.0.6 gcc: 14.1.1 Shell: garuda-inxi default: fish v: 3.7.1
running-in: konsole inxi: 3.3.35
Garuda (2.6.26-1):
System install date:     2024-06-22
Last full system update: 2024-06-22
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       No/Undetected
Failed units:

That is similar though not quite the same. Also, I figured out the weird nonmatching resolution. It seems to be referencing the DPI scaling for the res, so back to square one…

I feel like a complete fool rn… I blew some compressed air into both ends of the cable and the sockets, and now it works flawlessly… It still does it in 4k but to a significantly reduced degree, so I’m fairly confident a deeper cleaning will fix the issue… Mind you, I dunno why none of my previous attempts to clean it fixed it but regardless, this did it… I am happy I figured it out.

1 Like

Perhaps you might want to invest in a higher quality cable, as cabling causes far more issues than most would suspect.

2 Likes

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