Nvidia optimus Laptop screen tearing problem

Hello Everyone :
I've se t up optimus driver following Guide: Install and configure optimus-manager for hybrid GPU setups (Intel/NVIDIA) this post .
And I'm heaving screen tearing problem on my second monitor. (also on my main monitor sometimes.)

and I've found this tutorial on youtube
https://www.youtube.com/watch?v=IJeX35wbZY4

He is using bumblebee and mentioned it won't work on Prime . but I'm using Optimus manager .
Can't find another tutorial about prime drivers .

Hope someone can show me the correct way . Thanks .

System:    Host: nuctornal Kernel: 5.4.23-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.2.1 
           Desktop: KDE Plasma 5.17.5 Distro: Manjaro Linux 
Machine:   Type: Laptop System: Acer product: Predator PH317-52 v: V1.26 serial: <filter> 
           Mobo: CFL model: Sienna_CFS v: V1.26 serial: <filter> UEFI: Insyde v: 1.26 date: 03/27/2019 
Battery:   ID-1: BAT1 charge: 34.2 Wh condition: 34.2/48.9 Wh (70%) model: LG PABAS0241231 status: Unknown 
           Device-1: hidpp_battery_0 model: Logitech Marathon Mouse/Performance Plus M705 
           charge: 55% (should be ignored) status: Discharging 
CPU:       Topology: 6-Core model: Intel Core i7-8750H bits: 64 type: MT MCP arch: Kaby Lake rev: A 
           L2 cache: 9216 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 52815 
           Speed: 3521 MHz min/max: 800/4100 MHz Core speeds (MHz): 1: 3113 2: 2958 3: 2932 4: 2905 5: 2940 
           6: 2640 7: 2923 8: 2931 9: 2979 10: 2924 11: 2925 12: 2910 
Graphics:  Device-1: Intel UHD Graphics 630 vendor: Acer Incorporated ALI driver: i915 v: kernel 
           bus ID: 00:02.0 
           Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] vendor: Acer Incorporated ALI driver: nvidia 
           v: 440.59 bus ID: 01:00.0 
           Display: x11 server: X.Org 1.20.7 driver: modesetting,nvidia 
           resolution: 1440x900~60Hz, 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 440.59 direct render: Yes 
Audio:     Device-1: Intel Cannon Lake PCH cAVS vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel 
           bus ID: 00:1f.3 
           Sound Server: ALSA v: k5.4.23-1-MANJARO 
Network:   Device-1: Intel Wireless-AC 9560 [Jefferson Peak] driver: iwlwifi v: kernel port: 5000 
           bus ID: 00:14.3 
           IF: wlp0s20f3 state: up mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Acer Incorporated ALI 
           driver: r8169 v: kernel port: 3000 bus ID: 06:00.1 
           IF: enp6s0f1 state: down mac: <filter> 
Drives:    Local Storage: total: 1.03 TiB used: 11.70 GiB (1.1%) 
           ID-1: /dev/sda vendor: SK Hynix model: HFS128G39TND-N210A size: 119.24 GiB 
           ID-2: /dev/sdb vendor: Toshiba model: MQ04ABF100 size: 931.51 GiB 
RAID:      Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 bus ID: 00:17.0 
Partition: ID-1: / size: 107.92 GiB used: 10.28 GiB (9.5%) fs: ext4 dev: /dev/sda2 
           ID-2: /home size: 380.37 GiB used: 1.41 GiB (0.4%) fs: ext4 dev: /dev/sdb3 
           ID-3: swap-1 size: 8.80 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 55.0 C mobo: N/A gpu: nvidia temp: 44 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 293 Uptime: 39m Memory: 15.48 GiB used: 1.80 GiB (11.7%) Init: systemd Compilers: 
           gcc: 9.2.1 Shell: bash v: 5.0.16 inxi: 3.0.37 

The tearing is on Intel mode with modesetting driver or on Nvidia?

My experience is, that on Nvidia there is no tearing, on modesetting (intel mode) there is a heavy tearing on secondary device. Probably it depends on the device itself and I didn't found any solution to that yet.

Thanks for your reply .
Tearing happening on Nvidia. When I switch to Intel it's kinda smooth .

In this case look for some Nvidia pure solution and remeber, that the fix should be applied to optimus-manager base conf (the one that is used as a base to generate confs for different modes), not to nvidia conf. So don't use nvidia settings, because it will mess with optimus-manager.

2 Likes

I've found this file named 10-optimus-manager.conf under xorg.conf.d . is this the one ?

2020-03-12_20-22

when your on nvidia mode, check the output of xrandr --prop , if you see "PRIME Synchronization: 0" under your laptop display ( probably "eDP-1-1") then prime sync is not working and you'll get a lot of tearing without it.

but why is there a 20-intel.conf there at the same time? did you add this file yourself?

No, use

/etc/optimus-manager/xorg-nvidia.conf

The one in xorg.conf.d is generated from session to session.

And yes, @dglt is right, that intel.conf is not belonging there and most likely interfering with optimus-manager. Rename it by adding .bak to the name.

1 Like

the output was PRIME synchronization : 1

Screen 0: minimum 8 x 8, current 3360 x 1080, maximum 32767 x 32767
HDMI-0 connected 1440x900+1920+0 (normal left inverted right x axis y axis) 410mm x 256mm
        EDID: 
                00ffffffffffff00410c56d001010101
                1c12010380291a782a78f5a655489b26
                125054bdcf0081408180950f01010101
                0101010101019a29a0d0518422305098
                36009a001100001cab22a0a050841a30
                30203600100a0000001a000000fd0038
                4c1e5011000a202020202020000000fc
                00313950464c333430334445550a01ec
                020329f14f1304140506070203111215
                16101f0123090707830100006c030c00
                10008000c001010101011d00bc52d01e
                20b828554034cd3100001e011d801871
                1c1620582c250034cd3100009e011d00
                7251d01e206e28550034cd3100001e01
                1d80d0721c1620102c258034cd310000
                9e000000000000000000000000000047
        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: 2 
        _ConnectorLocation: 2 
        non-desktop: 0 
                supported: 0, 1
   1440x900      59.89*+  74.98    59.90  
   1920x1080     59.94    50.00    60.05    60.00    50.04  
   1280x1024     75.02    60.02  
   1280x960      60.00  
   1280x720      60.00    59.94    50.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32  
   720x576       50.00  
   720x480       59.94  
   640x480       75.00    72.81    59.94    59.93  
eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 382mm x 215mm
        EDID: 
                00ffffffffffff0030e46d0500000000
                001a0104952615780a0bb5a35955a027
                0c505400000001010101010101010101
                0101010101012e3680a070381f403020
                35007ed71000001a0000000000000000
                00000000000000000000000000fe004c
                4720446973706c61790a2020000000fe
                004c503137335746342d5350463500c6
        PRIME Synchronization: 1 
                supported: 0, 1
        scaling mode: Full aspect 
                supported: Full, Center, Full aspect
        max bpc: 12 
                range: (6, 12)
        Broadcast RGB: Automatic 
                supported: Automatic, Full, Limited 16:235
        link-status: Good 
                supported: Good, Bad
        CONNECTOR_ID: 86 
                supported: 86
        non-desktop: 0 
                range: (0, 1)
   1920x1080     60.02*+  60.01    59.97    59.96    59.93  
   1680x1050     59.95    59.88  
   1400x1050     59.98  
   1600x900      59.99    59.94    59.95    59.82  
   1280x1024     60.02  
   1400x900      59.96    59.88  
   1280x960      60.00  
   1440x810      60.00    59.97  
   1368x768      59.88    59.85  
   1280x800      59.99    59.97    59.81    59.91  
   1280x720      60.00    59.99    59.86    59.74  
   1024x768      60.04    60.00  
   960x720       60.00  
   928x696       60.05  
   896x672       60.01  
   1024x576      59.95    59.96    59.90    59.82  
   960x600       59.93    60.00  
   960x540       59.96    59.99    59.63    59.82  
   800x600       60.00    60.32    56.25  
   840x525       60.01    59.88  
   864x486       59.92    59.57  
   700x525       59.98  
   800x450       59.95    59.82  
   640x512       60.02  
   700x450       59.96    59.88  
   640x480       60.00    59.94  
   720x405       59.51    58.99  
   684x384       59.88    59.85  
   640x400       59.88    59.98  
   640x360       59.86    59.83    59.84    59.32  
   512x384       60.00  
   512x288       60.00    59.92  
   480x270       59.63    59.82  
   400x300       60.32    56.34  
   432x243       59.92    59.57  
   320x240       60.05  
   360x202       59.51    59.13  
   320x180       59.84    59.32  
  1280x1024 (0x1ee) 108.000MHz +HSync +VSync
        h: width  1280 start 1328 end 1440 total 1688 skew    0 clock  63.98KHz
        v: height 1024 start 1025 end 1028 total 1066           clock  60.02Hz
  1280x960 (0x1f1) 108.000MHz +HSync +VSync
        h: width  1280 start 1376 end 1488 total 1800 skew    0 clock  60.00KHz
        v: height  960 start  961 end  964 total 1000           clock  60.00Hz
  1024x768 (0x1ff) 65.000MHz -HSync -VSync
        h: width  1024 start 1048 end 1184 total 1344 skew    0 clock  48.36KHz
        v: height  768 start  771 end  777 total  806           clock  60.00Hz
  800x600 (0x20e) 40.000MHz +HSync +VSync
        h: width   800 start  840 end  968 total 1056 skew    0 clock  37.88KHz
        v: height  600 start  601 end  605 total  628           clock  60.32Hz
  640x480 (0x21b) 25.175MHz -HSync -VSync
        h: width   640 start  656 end  752 total  800 skew    0 clock  31.47KHz
        v: height  480 start  490 end  492 total  525           clock  59.94Hz

And for that Intel file I have no clue . Should I name it .bak as well ?

since your using optimus-manager as @michaldybczak already mentioned it creates a xorg configuration on each boot/mode change and having that 20-intel.conf in there can only cause problems so yes, rename/delete it, change modes or restart xorg so the changes get applied and see how things work

1 Like

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

Forum kindly sponsored by