Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to Fix Screen Tearing in 4.1 / XFCE 4.14 #7591

Open
SenorFusion opened this issue Jun 28, 2022 · 7 comments
Open

Unable to Fix Screen Tearing in 4.1 / XFCE 4.14 #7591

SenorFusion opened this issue Jun 28, 2022 · 7 comments
Labels
affects-4.1 This issue affects Qubes OS 4.1. C: other hardware support needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.

Comments

@SenorFusion
Copy link

SenorFusion commented Jun 28, 2022

Qubes OS release

4.1 current

Brief summary

Extreme screen tearing during video playback

Steps to reproduce

Open Firefox or Chromium
Play a youtube video

Expected behavior

video plays without tearing

System

Lenovo Thinkpad P70 Skylake
Nvidia M3000 Quadro
noveau
xen 4.14.5
kernel 5.10.112

What I have Tried

All of the suggestions in #4208 #3194 #4943 #5092 #5244
None of these work and all of the issues are nearly 3 years old at this point and none are about Qubes 4.1

The suggestions mostly boil down to 2 things:

Window Tweak Settings > Compositor> Synchronize drawing on the vertical blank.

This is no longer available in Xfce 4.14 so cannot be done that I can find.

I also tried disabling the compositor completely under WIndows Tweaks, that did not help either.

Add items to a xorg config file as listed in the GUI Configuration Doc

Section "Device"
		Identifier "Intel Graphics"
		Driver "intel"
		Option "TearFree" "true"
EndSection

I've tried multiple other variations on this file with i915, vsync, and triplebuffer.

After every attempt at adding this file qubes GUI does not boot and I have to log in from the terminal and rm the file.

It hangs on the screen that shows all boot checks (which do not normally show during boot) and then stops at Starting Hold until boot process finishes up.... but it never finishes

Attached is a picture of the boot hang, and a copy of Xorg log

qubes-boot

Xorg.0.log

@SenorFusion SenorFusion added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. labels Jun 28, 2022
@marmarek
Copy link
Member

You have two graphics cards, try adding BusID "PCI:0@0:2:0" to the Device section to be specific which one to use. Otherwise, connecting intel driver to Nvidia card indeed may result in Xorg not starting at all.

@SenorFusion
Copy link
Author

Thank you for the help! I tried the following in /etc/X11/xorg.conf.d/90-intel.conf

Section "Device"
		Identifier "Intel Graphics"
                BusID "PCI:0@0:2:0"
		Driver "intel"
		Option "TearFree" "true"
EndSection

It didn't work but it failed at a slightly different place in the boot process:

qubest-boot-2
Xorg.0.log

@marmarek
Copy link
Member

Are you sure this log if from the time you tried with /etc/X11/xorg.conf.d/90-intel.conf ? I don't see any mention of using "intel" driver there, but only "modeset" one.

@andrewdavidwong andrewdavidwong added C: other hardware support needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. labels Jun 29, 2022
@andrewdavidwong andrewdavidwong added this to the Release 4.1 updates milestone Jun 29, 2022
@SenorFusion
Copy link
Author

SenorFusion commented Jun 29, 2022

Are you sure this log if from the time you tried with /etc/X11/xorg.conf.d/90-intel.conf ? I don't see any mention of using "intel" driver there, but only "modeset" one.

I am sure it is the most recent copy of that log. But does Xorg log even get generated if X11 never starts?

After your first post I:

-Created the new 90-intel.conf file
-Restart
-Hangs at boot as seen in picture on my last post
-login via console
cd /etc/X11/xorg.conf.d
sudo rm 90-intel.conf
sudo reboot now
-Login normally
-Go to Dom0 Terminal and qvm-copy xorg log to this VM and post it for you

@SenorFusion
Copy link
Author

boot.log

Here is the boot log from yesterday when I was trying this if that is helpful

@marmarek
Copy link
Member

In that case, copy somewhere Xorg.0.log (just to avoid overriding it by subsequent Xorg start) before removing 90-intel.conf.
You can also take a look at Xorg.0.log.old, maybe it's still there.

@marmarek marmarek reopened this Jun 29, 2022
@SenorFusion
Copy link
Author

Some improvement! For whatever reason I was able to boot this time. Maybe I had a typo before.

Section "Device"
		Identifier "Intel Graphics"
                BusID "PCI:0@0:2:0"
		Driver "intel"
		Option "TearFree" "true"
EndSection

Positive: The tearing is not happening anymore, at least on the laptop screen.

Negative: System is not recognizing any external displays. xrandr shows in eDP1 (built in display) Nothing else, even though 2 external displays are still plugged in exactly as before I rebooted - 1 DP, 1 HDMI.

hybrid systems are such a pain!

Here is the xorg log from this current boot (laptop screen only). I looked at xor.log.old but it was last edited over a month ago so I dont think it will have anything useful.

Xorg.0.log

@andrewdavidwong andrewdavidwong added the affects-4.1 This issue affects Qubes OS 4.1. label Aug 8, 2023
@andrewdavidwong andrewdavidwong removed this from the Release 4.1 updates milestone Aug 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-4.1 This issue affects Qubes OS 4.1. C: other hardware support needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Development

No branches or pull requests

3 participants