From: Roel Janssen <roel@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Xorg tearing fix on Intel HD Graphics 4000
Date: Wed, 21 Jun 2017 15:26:53 +0200 [thread overview]
Message-ID: <87d19xwjxe.fsf@gnu.org> (raw)
In-Reply-To: <87k24539rz.fsf@elephly.net>
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..
Thanks for your snippet! I've done a system reconfigure and the extra
configuration applied as expected.
If there is anyone with the same problem, we could look further into
upstreaming it.
Thanks,
Roel
next prev parent reply other threads:[~2017-06-21 13:27 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d19xwjxe.fsf@gnu.org \
--to=roel@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.