Extreme Tearing on Kernel >= 5.6

I've been using Manjaro since January on my machine, and I've had very little issues with it. I had my initial setup for just a few weeks then reinstalled again I'm thinking near the end of March/ beginning of April. Just a couple of days ago, however, I've had some hardware issues with an M.2 nvme that is having trouble reading huge files that are 20GB in size or more like VMs or blu-ray rips. I have to send it back to the manufacturer, but I want a working system on another drive before I do so. I have another M.2 nvme that's the exact same make and model in the system which I had Windows installed on for gaming, but I've since wiped that off and am attempting to install Manjaro on the other nvme. I've run into issues ever since.

My current working install on the nvme that needs to be returned to the manufacturer was first installed with the 5.4 kernel and has been upgraded ever since, currently using the latest 5.6 kernel. I haven't yet upgraded it to 5.7. Again, I've had ZERO issues with this installation. In fact with every kernel update my video card performance has skyrocketed.

I first downloaded the latest Manjaro KDE ISO (manjaro-kde-20.0.3-200606-linux56) and put it on a USB drive which I used to then attempt to install. When I booted into it, however, it showed significant screen tearing. I installed anyway, and the installation itself had tearing despite its using the exact same kernel as my working installation on the other nvme. Nothing I knew could fix it. It also had a problem where pcsclite wasn't working properly as I use a yubikey as a smartcard for logging into servers.

I then decided to use another ISO I had from earlier which I think is the one I used to install the working installation (manjaro-kde-19.0.2-200311-linux54). No tearing (and pcsclite works). I install and then update all packages. I then update to 5.6 kernel, reboot, and... tearing. This is the exact same kernel with exact driver that I haven't ever had issues out of on my original install. I don't understand what could be happening or what to look for when I have a perfectly working install (minus the slight hardware issue with the nvme) with the exact same OS and hardware.

I have two video cards. The AMD one is my primary one, and the Nvidia card is used with KVM/QEMU for a Windows VM with GPU passthru for work. Below is the output of inxi -FGx --display on my original installation as it's the one booted into at the moment. I am not near the computer right now to show the output, but it should be identical except for the driver for the Nvidia card as I haven't gotten to setting up gpu passthru on the new install yet. I'll post it here when I get back to the computer later today. Could the other card's being there and not told to be ignored be causing the screens to tear? No display is plugged into it currently.

System:    Host: cygnus Kernel: 5.6.15-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.1.0 Desktop: N/A Distro: Manjaro Linux 
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME X299-DELUXE v: Rev 1.xx serial: <root required> UEFI: American Megatrends 
           v: 1401 date: 05/10/2018 
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master 2S charge: 50% (should be ignored) status: N/A 
CPU:       Topology: 8-Core model: Intel Core i7-7820X bits: 64 type: MT MCP arch: Skylake rev: 4 L2 cache: 11.0 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 115232 
           Speed: 1200 MHz min/max: 1200/4500 MHz Core speeds (MHz): 1: 1200 2: 1200 3: 1201 4: 1201 5: 1201 6: 1202 7: 1201 
           8: 1201 9: 1200 10: 1200 11: 1200 12: 1200 13: 1200 14: 1200 15: 1200 16: 1201 
Graphics:  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: eVga.com. driver: vfio-pci v: 0.2 bus ID: 21:00.0 
           Device-2: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu 
           v: kernel bus ID: c3:00.0 
           Display: x11 server: X.Org 1.20.8 driver: amdgpu FAILED: ati unloaded: modesetting,radeon 
           resolution: 2560x1440~60Hz, 2560x1440~60Hz 
           OpenGL: renderer: AMD Radeon RX 5700 XT 50th Anniversary (NAVI10 DRM 3.36.0 5.6.15-1-MANJARO LLVM 10.0.0) 
           v: 4.6 Mesa 20.0.7 direct render: Yes 
Audio:     Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           Device-2: NVIDIA GP106 High Definition Audio vendor: eVga.com. driver: vfio-pci v: 0.2 bus ID: 21:00.1 
           Device-3: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio driver: snd_hda_intel v: kernel bus ID: c3:00.1 
           Device-4: Blue Microphones Yeti Stereo Microphone type: USB driver: hid-generic,snd-usb-audio,usbhid 
           bus ID: 1-6.2:6 
           Sound Server: ALSA v: k5.6.15-1-MANJARO 
Network:   Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: 3.2.6-k port: 3000 bus ID: 00:1f.6 
           IF: enp0s31f6 state: down mac: 18:31:bf:bb:b6:3e 
           Device-2: Wilocity Wil6200 802.11ad Wireless Network Adapter driver: wil6210 v: kernel port: 3000 bus ID: 02:00.0 
           IF: wlp2s0 state: down mac: 3a:c0:ea:6b:d5:8f 
           Device-3: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: 5.6.0-k port: 2000 bus ID: 05:00.0 
           IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: 40:16:7e:a5:28:27 
           Device-4: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter vendor: ASUSTeK driver: ath10k_pci v: kernel 
           port: 2000 bus ID: 06:00.0 
           IF: wlp6s0 state: down mac: fe:7a:b4:3e:1e:c7 
           IF-ID-1: virbr0 state: down mac: 52:54:00:d0:94:92 
           IF-ID-2: virbr0-nic state: down mac: 52:54:00:d0:94:92 
Drives:    Local Storage: total: 720.48 GiB used: 270.91 GiB (37.6%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 500GB size: 465.76 GiB 
           ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO 500GB size: 465.76 GiB 
           ID-3: /dev/sda vendor: Mushkin model: MKNSSDSR250GB size: 232.89 GiB 
           ID-4: /dev/sdb type: USB vendor: Verbatim model: STORE N GO size: 14.46 GiB 
           ID-5: /dev/sdc type: USB vendor: Patriot model: N/A size: 7.38 GiB 
Partition: ID-1: / size: 465.26 GiB used: 270.91 GiB (58.2%) fs: btrfs dev: /dev/nvme1n1p2 
           ID-2: /home size: 465.26 GiB used: 270.91 GiB (58.2%) fs: btrfs dev: /dev/nvme1n1p2 
Sensors:   System Temperatures: cpu: 27.0 C mobo: N/A gpu: amdgpu temp: 64 C 
           Fan Speeds (RPM): N/A gpu: amdgpu fan: 1192 
Info:      Processes: 348 Uptime: 4h 10m Memory: 62.55 GiB used: 1.16 GiB (1.9%) Init: systemd Compilers: gcc: 10.1.0 
           clang: 10.0.0 Shell: bash v: 5.0.17 inxi: 3.0.37

The problem lies here:

Xorg is using the AMD GPU but with a failed driver: X.Org 1.20.8 driver: amdgpu FAILED: ati unloaded: modesetting,radeon

As you have an nVidia GeForce GTX 1060 as well, just do the following to switch to nVidia:

  • Log off

  • Switch to TTY2 by pressing Ctrl+Alt+F2

  • Log in there

  • Execute:

    sudo mhwd --listinstalled
    
  • remove everything you see there with the following command, execute it for each line you see as output of the above command:

    sudo mhwd --remove pci WhateverDriver 
    
  • Now install the nVidia driver for your hardware:

    sudo mhwd --install pci video-nvidia-440xx
    
  • Reboot

Done!

:innocent:

This was output from the working install that doesn't have any tearing. The ati driver is the failed driver. It's using amdgpu. The newer install is exactly the same output for video except the nvidia card is using nouveau instead of the vpio-pci drivers as I haven't set it up for passthru yet. I forgot to paste in the inxi output from the newer install when I got to the computer yesterday afternoon. The AMD card is what I'm wanting to use in Linux. The Nvidia card is for virtual machines.

It doesn't tear on every boot. It'll boot most of the time without tearing now, but it looks like it loads incorrectly when it does? It takes longer to boot when it starts tearing on SDDM. I haven't checked the logs yet to see what it outputs then. I'll report back.

At least I got it to a working state anyway.

You're talking to the wrong person then: I don't have an AMD so know nothing about that. :sob:

Also, for the future, please specify more clearly in your original post what your goal is... :wink:

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

Forum kindly sponsored by