From: William <w@vieta.uk>
To: Roel Janssen <roel@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Xorg tearing fix on Intel HD Graphics 4000
Date: Thu, 22 Jun 2017 00:23:03 +0100 [thread overview]
Message-ID: <CAPCYgVe0Ec63Xqw4CNFDLob3FGq9Ync2=xdim4e7QEp7JCNgqQ@mail.gmail.com> (raw)
In-Reply-To: <877f05vv6j.fsf@gnu.org>
The Arch Wiki says that Debian and some others suggest uninstalling
xf86-video-intel and relying on the modesetting driver.
I have personally found this to help with tearing, but naturally YMMV.
See https://wiki.archlinux.org/index.php/Intel_graphics#Installation
for more details.
Good luck
William
On 21 June 2017 at 23:21, Roel Janssen <roel@gnu.org> wrote:
>
> Mark H Weaver writes:
>
>> Hi Roel,
>>
>> Roel Janssen <roel@gnu.org> writes:
>>
>>> Ricardo Wurmus writes:
>>>
>>>> Hi Roel,
>>>>
>>>>> With the following patch to the Xorg configuration file, I have a
>>>>> tear-free GuixSD experience. I wonder if this is upstreameable in some
>>>>> way. This patch is probably too broad in effect. Can I change it so
>>>>> that only the graphics card I have will be affected by this patch?
>>>>
>>>> I’m not sure about this, but you can apply it only to your system by
>>>> changing the slim-service’s “startx” value like this:
>>>>
>>>> --8<---------------cut here---------------start------------->8---
>>>> (modify-services %desktop-services
>>>> (slim-service-type
>>>> config => (slim-configuration
>>>> (inherit config)
>>>> (startx (xorg-start-command
>>>> #:configuration-file
>>>> (xorg-configuration-file
>>>> #:extra-config
>>>> (list your-fix)))))))
>>>> --8<---------------cut here---------------end--------------->8---
>>>>
>>>> But I suppose what you want is to apply it unconditionally in Guix and
>>>> have the X server ignore it for all but this one graphics card, right?
>>>
>>> No, not necessarily. I could no longer do 'guix pull && guix system
>>> reconfigure ...', which I attempted to solve by upstreaming this patch.
>>>
>>> I wonder if anyone else is having the same problem on this hardware..
>>
>> I have the same problem on my Thinkpad X200. For me, it mostly only
>> happens in Emacs graphical frames, and only within GNOME (and I suppose
>> maybe other compositing window managers, though I haven't tried), but
>> the problem for me is quite severe. I've resorted to running Emacs in
>> text mode within GNOME Terminal, because otherwise I cannot trust my
>> editing at all (e.g. I'm not sure if I'm deleting the messages that I
>> intend to delete in Gnus).
>>
>> However, your proposed workaround is not a proper fix, and I don't think
>> we should apply it system-wide in Guix. I don't think it would be
>> accepted upstream. I think there's a real bug somewhere, most likely in
>> Emacs itself, but possibly in the Intel graphics drivers.
>
> Thanks for your response! I look forward to finding out what this bug
> is. If you do, please let us know.
>
>>
>> It's good to have the workaround though. I may apply it to my own
>> system and see how it affects graphics performance. Thank you!
>
> FWIW, I get equal frames per second in SuperTuxKart and Armagetron.
> Anyway, there's nothing like experiencing it yourself of course.
>
> Kind regards,
> Roel Janssen
>
next prev parent reply other threads:[~2017-06-21 23:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 7:55 Xorg tearing fix on Intel HD Graphics 4000 Roel Janssen
2017-06-21 10:38 ` Ricardo Wurmus
2017-06-21 13:26 ` Roel Janssen
2017-06-21 16:27 ` Kei Kebreau
2017-06-21 17:23 ` Mark H Weaver
2017-06-21 22:21 ` Roel Janssen
2017-06-21 23:23 ` William [this message]
2017-06-25 11:59 ` Marius Bakke
2017-06-25 17:13 ` Roel Janssen
2017-06-25 17:39 ` Marius Bakke
2017-06-25 5:47 ` Chris Marusich
2017-06-25 8:31 ` Roel Janssen
2017-06-25 11:38 ` Mark H Weaver
2017-06-25 11:08 ` Mark H Weaver
2017-08-07 21:48 ` Clément Lassieur
2017-06-25 5:46 ` Chris Marusich
2017-06-25 8:28 ` Roel Janssen
2017-07-20 2:43 ` Chris Marusich
2017-07-20 10:57 ` Roel Janssen
2017-06-23 18:00 ` Christopher Baines
2017-06-26 8:55 ` Andy Wingo
2017-06-27 17:43 ` Mark H Weaver
2017-06-28 8:24 ` Andy Wingo
2017-06-28 18:14 ` Mark H Weaver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPCYgVe0Ec63Xqw4CNFDLob3FGq9Ync2=xdim4e7QEp7JCNgqQ@mail.gmail.com' \
--to=w@vieta.uk \
--cc=guix-devel@gnu.org \
--cc=roel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).