I am experiencing extreme screen tearing when running on Internal NVME SSD

This may not actually be a Graphics issue.

When running on an external USB SSD, I do not experience this issue.

Here’s the computer details.

tracy@daphne ~]$ inxi -zv8
System:
  Kernel: 6.18.33-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.18-x86_64
    root=UUID=fced3a62-fe08-4b92-b6b1-ac0f6f2e1b49 rw quiet splash
    resume=UUID=3c71ffc0-8c40-4e43-9a0e-fe1b1e34287b udev.log_priority=3
  Desktop: KDE Plasma v: 6.6.5 tk: Qt v: N/A info: frameworks v: 6.26.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: SLIMBOOK product: Elemental15-I13D5 v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: SLIMBOOK model: Elemental15-I13D5 serial: <superuser required>
    uuid: <superuser required> Firmware: UEFI vendor: INSYDE v: 1.07.02TGO
    date: 10/28/2025
Battery:
  ID-1: BAT0 charge: 48.2 Wh (100%) condition: 48.2/48.3 Wh (99.8%)
    volts: 17.11 min: 15.2 model: Notebook BAT type: Li-ion serial: <filter>
    charging: status: full cycles: N/A
Memory:
  System RAM: total: 8 GiB available: 7.46 GiB used: 4.06 GiB (54.5%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 64 GiB slots: 2 modules: 1 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: Controller0-ChannelA-DIMM0 type: DDR5 detail: synchronous
    size: 8 GiB speed: 5200 MT/s volts: curr: 1 width (bits): data: 64 total: 64
    manufacturer: Wilk Elektronik S.A. part-no: GR5600S564L46S/8G
    serial: <filter>
  Device-2: Controller1-ChannelA-DIMM0 type: no module installed
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core 5 120U bits: 64 type: MST AMCP arch: Raptor Lake
    level: v3 note: check built: 2022+ process: Intel 7 (10nm) family: 6
    model-id: 0xBA (186) stepping: 3 microcode: 0x6134
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 10 threads: 12 mt: 2 tpc: 2
    st: 8 smt: enabled cache: L1: 928 KiB desc: d-8x32 KiB, 2x48 KiB; i-2x32
    KiB, 8x64 KiB L2: 6.5 MiB desc: 2x1.2 MiB, 2x2 MiB L3: 12 MiB
    desc: 1x12 MiB
  Speed (MHz): avg: 400 min/max: 400/5000:3800 scaling: driver: intel_pstate
    governor: powersave cores: 1: 400 2: 400 3: 400 4: 400 5: 400 6: 400 7: 400
    8: 400 9: 400 10: 400 11: 400 12: 400 bogomips: 59904
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_lbr arch_perfmon art avx avx2 avx_vnni bmi1 bmi2
    bts clflush clflushopt clwb cmov constant_tsc cpuid cpuid_fault cx16 cx8
    de ds_cpl dtes64 dtherm dts epb ept ept_ad erms est f16c flexpriority
    flush_l1d fma fpu fsgsbase fsrm fxsr gfni hfi ht hwp hwp_act_window
    hwp_epp hwp_notify hwp_pkg_req ibpb ibrs ibrs_enhanced ibt ida intel_pt
    invpcid lahf_lm lm mca mce md_clear mmx monitor movbe movdir64b movdiri
    msr mtrr nonstop_tsc nopl nx ospke pae pat pbe pcid pclmulqdq pdcm
    pdpe1gb pebs pge pku pln pni popcnt pse pse36 pts rdpid rdrand rdseed
    rdtscp rep_good sdbg sep serialize sha_ni smap smep smx split_lock_detect
    ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc
    tsc_adjust tsc_deadline_timer tsc_known_freq umip user_shstk vaes vme vmx
    vnmi vpclmulqdq vpid waitpkg x2apic xgetbv1 xsave xsavec xsaveopt xsaves
    xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  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: old_microcode status: Not affected
  Type: reg_file_data_sampling mitigation: Clear Register File
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow 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; PBRSB-eIBRS: SW sequence; BHI: BHI_DIS_S
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Intel Raptor Lake-U [Intel Graphics] vendor: CLEVO/KAPOK
    driver: i915 v: kernel alternate: xe arch: Xe process: Intel 7 (10nm)
    built: 2022+ ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, HDMI-A-1
    bus-ID: 00:02.0 chip-ID: 8086:a7ac class-ID: 0300
  Device-2: Chicony USB2.0 Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-7:4 chip-ID: 04f2:b729
    class-ID: fe01 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.22 with: Xwayland v: 24.1.11
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,vesa dri: iris gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: ChiMei InnoLux 0x15e7 built: 2020 res:
    mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 142 gamma: 1.2 chroma: red:
    x: 0.592 y: 0.349 green: x: 0.329 y: 0.557 blue: x: 0.153 y: 0.118 white:
    x: 0.314 y: 0.329 size: 344x193mm (13.54x7.6") diag: 394mm (15.5")
    ratio: 16:9 modes: 1920x1080
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
    drv: iris x11: drv: iris
  API: OpenGL v: 4.6 vendor: intel mesa v: 26.1.1-arch1.2 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel Graphics (RPL-U)
    device-ID: 8086:a7ac memory: 7.28 GiB unified: yes display-ID: :1.0
  API: Vulkan v: 1.4.350 layers: 2 device: 0 type: integrated-gpu
    name: Intel Graphics (RPL-U) driver: mesa intel v: 26.1.1-arch1.2
    device-ID: 8086:a7ac surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyinfo,xprop
Audio:
  Device-1: Intel Raptor Lake-P/U/H cAVS vendor: CLEVO/KAPOK
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl
    bus-ID: 00:1f.3 chip-ID: 8086:51ca class-ID: 0403
  API: ALSA v: k6.18.33-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.6.5 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Raptor Lake PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:51f1 class-ID: 0280
  IF: wlp0s20f3 state: down mac: <filter>
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: CLEVO/KAPOK driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: 3000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>
  IF-ID-1: wg0-mullvad state: unknown speed: N/A duplex: N/A mac: N/A
  IP v4: <filter> scope: global
  IP v6: <filter> scope: global
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-10:5 chip-ID: 8087:0026
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 1.86 TiB used: 24.59 GiB (1.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: GOODRAM
    model: SSDPR-PX600L-01T-80 size: 953.87 GiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: EJFME0.0 temp: 20.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B type: USB
    rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
    scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: SanDisk model: Cruzer Glide
    size: 14.59 GiB block-size: physical: 512 B logical: 512 B type: USB
    rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter>
    fw-rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 63.48 GiB size: 62.18 GiB (97.96%) used: 10.21 GiB (16.4%)
    fs: ext4 dev: /dev/sda2 maj-min: 8:2 label: N/A
    uuid: fced3a62-fe08-4b92-b6b1-ac0f6f2e1b49
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 328 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1 label: N/A
    uuid: 5127-A586
  ID-3: /home raw-size: 832.58 GiB size: 818.44 GiB (98.30%)
    used: 14.38 GiB (1.8%) fs: ext4 dev: /dev/sda4 maj-min: 8:4 label: N/A
    uuid: c084f514-34a5-41ef-91e6-98c6aa025f18
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 35.16 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda3 maj-min: 8:3 label: N/A
    uuid: 3c71ffc0-8c40-4e43-9a0e-fe1b1e34287b
Unmounted:
  ID-1: /dev/nvme0n1p1 maj-min: 259:1 size: 300 MiB fs: vfat label: N/A
    uuid: 2E32-AD6A
  ID-2: /dev/nvme0n1p2 maj-min: 259:2 size: 63.48 GiB fs: ext4 label: N/A
    uuid: f11f2354-595a-4518-88d4-f2e0498acc46
  ID-3: /dev/nvme0n1p3 maj-min: 259:3 size: 20.02 GiB fs: swap label: N/A
    uuid: da167c2a-300a-485b-b202-959f946a116f
  ID-4: /dev/nvme0n1p4 maj-min: 259:4 size: 847.72 GiB fs: ext4 label: N/A
    uuid: 4634127b-b874-49cf-944d-be311c3556a9
  ID-5: /dev/sdb1 maj-min: 8:17 size: 4.56 GiB fs: iso9660
  ID-6: /dev/sdb2 maj-min: 8:18 size: 4 MiB fs: vfat label: MISO_EFI
    uuid: 3353-174A
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-1:2 info: [Maxxter] Optical gaming mouse type: mouse,keyboard
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1
    speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
    chip-ID: 18f8:0f99 class-ID: 0300
  Device-2: 1-3:3 info: SanDisk Cruzer Glide type: mass storage
    driver: usb-storage interfaces: 1 rev: 2.1 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 power: 224mA chip-ID: 0781:5575 class-ID: 0806
    serial: <filter>
  Device-3: 1-7:4 info: Chicony USB2.0 Camera type: video driver: uvcvideo
    interfaces: 3 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0
    power: 500mA chip-ID: 04f2:b729 class-ID: fe01 serial: <filter>
  Device-4: 1-10:5 info: Intel AX201 Bluetooth type: bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 8087:0026 class-ID: e001
  Hub-2: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Device-1: 2-3:2 info: ASMedia ASM1153 SATA 3Gb/s bridge type: mass storage
    driver: usb-storage interfaces: 1 rev: 3.0 speed: 5 Gb/s (596.0 MiB/s)
    lanes: 1 mode: 3.2 gen-1x1 chip-ID: 174c:1153 class-ID: 0806
    serial: <filter>
Sensors:
  System Temperatures: cpu: 39.2 C mobo: N/A
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: pacman pkgs: 1215 libs: 336 tools: pamac
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://ftp.yz.yamagata-u.ac.jp/pub/linux/manjaro/stable/$repo/$arch
    2: https://mirrors.ft.uam.es/manjaro/stable/$repo/$arch
    3: https://mirror.easyname.at/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 326
  1: cpu: 10.6% command: firefox pid: 2153 mem: 527.4 MiB (6.9%)
  2: cpu: 9.8% command: firefox pid: 2529 mem: 404.3 MiB (5.2%)
  3: cpu: 5.6% command: kwin_wayland pid: 946 mem: 248.2 MiB (3.2%)
  4: cpu: 4.2% command: firefox pid: 2386 mem: 611.0 MiB (7.9%)
  5: cpu: 3.1% command: plasmashell pid: 1112 mem: 365.7 MiB (4.7%)
  Memory top: 5 of 326
  1: mem: 611.0 MiB (7.9%) command: firefox pid: 2386 cpu: 4.2%
  2: mem: 527.4 MiB (6.9%) command: firefox pid: 2153 cpu: 10.6%
  3: mem: 408.1 MiB (5.3%) command: firefox pid: 1263 cpu: 2.7%
  4: mem: 404.3 MiB (5.2%) command: firefox pid: 2529 cpu: 9.8%
  5: mem: 365.7 MiB (4.7%) command: plasmashell pid: 1112 cpu: 3.1%
Info:
  Processes: 326 Power: uptime: 5m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 2.93 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 260 default: graphical
    tool: systemctl
  Compilers: gcc: 16.1.1 Shell: Bash v: 5.3.9 default: Zsh v: 5.9
    running-in: konsole inxi: 3.3.40
[tracy@daphne ~]$ 

This is currently running on the external SSD. Both the internal and external SSDs have the same version of Manjaro installed from the same USB key.

smartctl reports the nvme health is good

[tracy@daphne ~]$ sudo smartctl -H /dev/nvme0n1
[sudo] password for tracy: 
smartctl 7.5 2025-04-30 r5714 [x86_64-linux-6.18.33-1-MANJARO] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

There was something recently about mesa and Intel graphics, and a few topics complaining about severe screen tearing. In one of the update announcements I recall the suggestion to revert to the previous mesa (apparently a known issue).

I only saw this in passing and as it didn’t apply to me, I largely dismissed it, but it might be worth following up.

Raptor lake U is a 13th gen cpu. It is not that.

The only thing that comes to mind right off the bat is this:

In this case, I’d take a look at the motherboard manual.

Sometimes PCIe lanes are shared; the manual might state that if you install an SSD in a specific slot, you can’t install PCIe cards in another one — otherwise, you’ll run into issues.

My motherboard definitely has warnings like that in the manual, and I had to do quite a bit of juggling to get everything connected correctly.
:footprints:

3 Likes

I will second that. Your description of the problem sounds very much like an interference issue to me. Perhaps best to shuffle your PCIe devices around to other slots.

The thing is it started, after I rebooted the Laptop, after installing the kernel 7.1 RC, and booted on to that.

After that it did not matter what kernel I booted on to.

Even after I reinstalled the OS on the internal NVME

The only exception is it doesn’t do it on the external USB SSD.

I suppose it could be the solution described.

Well, I’d put that down to coincidence. I’m pretty sure it’s “chatter”, as they call it — electrostatic/electromagnetic interference. There’s a reason why they put the UTP cables for the machines on a professional LAN in separate conduits. :wink:

Things like this can easily be influenced or even triggered by atmospheric conditions. Most people don’t realize this, but unless you’ve got a professional system with ECC on everything — and those machines cost a fortune; trust me — your computer and even smartphones, cellphones, radios and television sets are incredibly susceptible to this kind of interference.

2 Likes

Probably.

At the moment it’s kinda confusing. Because it works perfectly on the external SSD. Which I suppose could point to a Hardware issue, you guys have described.

Well, it’s a no-brainer, really. When you’re running off the internal drive, there is more activity on that PCIe slot, and the temperature will be higher there, which could be the trigger.

When running from the external drive, the devices are sufficiently separated and there is no crosstalk.

2 Likes

It is really strange - that you get notably different experience using the internal disk.

I have no idea where to look - one can only speculate.

The first think I do when dealing with an Intel based system with Iris Xe - is to add in mkinitcpio.conf

MODULES=( xe )

If this changes anything it might be worth doing some kind of maintenance on the internal disk.

I am thinking along the lines of

  • executing a secure erase
  • dd to write zeroes to the entire disk

Depending on mood I could be tempted to recreate the partition layout and copy the content of the working setup to the disk.

In that process it is important to modify /etc/fstab to use the correct UUIDs for the new partition layout.

If one want to avoid fiddling with UUIDs - using partition labels on the working installation and the same labels on the manually partitioned device - one could simply copy the files and it will boot without any hickups.

1 Like

That’s just it. The NVME boots fine.

It’s after loging in that’s when the problen begins.

That’s why I ended up installing to both the External and the Internal.

I have even copied the entire config from the user on the NVME to the External SSD

Here’s the fstab from the internal NVME

[tracy@daphne f11f2354-595a-4518-88d4-f2e0498acc46]$ cat etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=2E32-AD6A                            /boot/efi      vfat    defaults,umask=0077 0 2
UUID=f11f2354-595a-4518-88d4-f2e0498acc46 /              ext4    defaults   0 1
UUID=da167c2a-300a-485b-b202-959f946a116f swap           swap    defaults   0 0
UUID=4634127b-b874-49cf-944d-be311c3556a9 /home          ext4    defaults   0 2
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

Here’s the fstab from the external SSD

[tracy@daphne ~]$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=5127-A586                            /boot/efi      vfat    defaults,umask=0077 0 2
UUID=fced3a62-fe08-4b92-b6b1-ac0f6f2e1b49 /              ext4    defaults   0 1
UUID=3c71ffc0-8c40-4e43-9a0e-fe1b1e34287b swap           swap    defaults   0 0
UUID=c084f514-34a5-41ef-91e6-98c6aa025f18 /home          ext4    defaults   0 2

If it is after login - my initial hunch is your local ~/.cache which needs cleaning.

When it is screen tearing - it is indeed GPU related - I cannot claim to have much knowledge on the inner workings of kwin and wayland.

I know from experience that applications which utilise GPU rendering creates cache files in ~/.cache.

This cache will be used if they exist - but may have been corrupted - sounds bad - it is not that bad - it can happen when a system is updated and the cache has not yet been updated to reflect it.

There is absolutely nothing in ~/.cache that cannot be removed.

To avoid a plasma service to interfere with the cleaning - I prefer to logout and do the cleaning in a TTY.

rm -rf ~/.cache

I remember a couple of folders

mesa_shader_cache, qtshadercache*, plasmashell which contains various caches which may have bearings on screen tearing. There may be other folders with shader and cache as part of their names.

Also in .cache you will find various .kcache file

Any one of these has the potential to influence how the screen is rendered.

I have had screen tearing on older intel GPU devices and it was far more frequent with Plasma 5 - I don’t even recall having it with Plasma 6.

I’m pretty sure I have cleared the cache at least once, I’ve done it again. I’m pretty sure it won’t fix it. though.

Yeah, Deleting the ~/.cache doesn’t fix it. I did delete it before.

The point is I am working on the same computer, only using the External USB SSD, and it’s functioning fine.

So it seems, then, that access to the internal SSD interferes with the graphics card’s (GPU) access to memory.
:footprints:

2 Likes

Maybe try options i915 enable_guc=3 . Also check for BIOS updates, latest is January ‘26, seems only have EC updated to 1.09 but that’s responsible for power and peripherals. There is a ‘feature’ Intel ME that now has a disable option, toggle that, maybe it wasn’t playing ball with the new rc kernel and set some new default.

And finally, since it’s a Clevo with easy access, take the drive out, carefully clean the contacts with a Q-tip and re-seat it.

This is essentially an Alder Lake processor the:

Graphics:
Device-1: Intel Raptor Lake-U

should read Iris Xe 80.

2 Likes

At this point that seems the most likely. I have been around hardware long enough to understand that just because it has been working perfectly for 3 months, doesn’t mean it won’t suddenly stop working. Which seems to be the case, here.

1 Like

I think I did get that - given the text interface - I was just thinking out loud :slight_smile:

Approaching this using a process of elimination - did you do some forensic on the hardware? Unboxing the internal by removing the bottom (the D part) and checking how/if the internal nvme is secure in place?

If you can get your hands on another nvme ssd to test with? I know from experience that Kioxa is a reasonable nvme at a reasonable price - of course I cannot know how it in the other end of the world.

1 Like

I haven’t yet opened up the computer. I’ve been working on something, and wanted to get it finished. So probably tomorrow.

I have now opened up the machine , and removed the NVME SSD, cleaned the contacts, and reseated it. Unfortunately, no change.

It still works fine with the external USB.

This is what the tearing looks like, if anyone is interested. it happens when I move the mouse, and only in Windows, including the Panels.

I am completely at loss - this is really really strange - the fact that the system work with tearing when using an external disk.

If it were me I would be going totally bonkers trying to solve it.

I cannot fathom what difference that would make - except for some weird circuitry issue - but then - it would have been so from day one - please say it didn’t occur from day one :slight_smile:

I am thinking out load - trying to recap

  • an intel based system set aside part of the system memory for GPU
    • this leads to checking perhaps changing or resetting values in the firmware

I vaguely recall and issue I had with my old ThinkStation E32 when it was my primary workstation using Intel Core 5 iGPU. I had occasional screen tearing and I found a way to configure a workaround - but it is a long time ago - I tried searching the forum since it occurred to me that I might have posted about - sharing the method.
If I did it is not in this instance - but a previous one.

I cannot quite let go of the thought that your USB load slightly different because it is USB.

If you did not already think of that - look at /etc/modprobe.d for any Intel and/or GPU related stuff.

The Arch Wiki has a great entry on Intel (as noted by @6x12).

You may also look at the module params for i915 an xe.

modinfo i915
modinfo xe

If you boot the installer ISO - then when booted - look at the mhwd-live.log in /var/log