unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Roel Janssen <roel@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Xorg tearing fix on Intel HD Graphics 4000
Date: Wed, 19 Jul 2017 19:43:49 -0700	[thread overview]
Message-ID: <87zibz6d5m.fsf@gmail.com> (raw)
In-Reply-To: <87lgog31zi.fsf@gnu.org> (Roel Janssen's message of "Sun, 25 Jun 2017 10:28:33 +0200")

[-- Attachment #1: Type: text/plain, Size: 2810 bytes --]

Roel Janssen <roel@gnu.org> writes:

> Chris Marusich writes:
>
>> 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.
>>
>> Why wouldn't you be able to do a 'guix pull && guix system reconfigure'?
>
> Because that would build a system generation which doesn't contain the
> patched Xorg config.  Ricardo's snippet solved that.
>
>>
>>> I wonder if anyone else is having the same problem on this hardware..
>>
>> Yes, I have this problem.  I use a Lenovo X200.  Like Mark, graphical
>> Emacs doesn't display characters right, and it's difficult to tell what
>> the buffer actually contains, sometimes.  I've reconfigured my system to
>> use the extra Xorg config you've provided in this thread, and I'll let
>> you know in a week or two if it seems to have fixed the problem.
>
> Thanks.
>
> Kind regards,
> Roel Janssen

Just wanted to close the loop here: I have not had any tearing problems
since applying the patch.  Sounds like the problem has been resolved
through a slightly different means, though (with commit
b049ae2f9708794f83c41171c19ffdfe4f11807e).  Accordingly, I've removed
the extra xorg configuration from my operating system configuration file
and simply reconfigured using the latest origin/master.

Thank you for starting this discussion!  It's really nice to be able to
use graphical emacs now without needing to frequently invoke M-x
redraw-display.

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-07-20  2:44 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
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 [this message]
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=87zibz6d5m.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --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).