From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 28578@debbugs.gnu.org
Subject: bug#28578: xorg not starting on x200 due to recent commit
Date: Mon, 25 Sep 2017 09:45:53 -0500 [thread overview]
Message-ID: <87y3p2suou.fsf@dustycloud.org> (raw)
In-Reply-To: <87fubb1vnd.fsf@gmail.com>
Chris Marusich writes:
> Christopher Allan Webber <cwebber@dustycloud.org> writes:
>
>> The following commit to guix makes it so that I can't start xorg:
>>
>> c68c201fdd429140da1c606861c9296b9cb01265
>> Author: Andy Wingo <wingo@igalia.com>
>> CommitDate: Wed Sep 20 15:40:31 2017 +0200
>>
>> gnu: xorg-server: Prefer intel driver only for older GPUs.
>>
>> * gnu/packages/xorg.scm (xorg-server): Add patch to only prefer the intel
>> driver for older Intel GPUs.
>>
>> The commit seems useful, but unfortunately I think I'm not the only x200
>> user, and this is breaking things for me! I wonder if there's a way to
>> keep the commit's purpose/feature without breaking xorg on x200s?
>
> For what it's worth, I use an X200, I did a guix pull followed by a
> system reconfigure just yesterday, and it boots fine for me. I wonder
> what is different about my setup compared to yours?
Not sure. Are you running libreboot?
next prev parent reply other threads:[~2017-09-25 14:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 15:23 bug#28578: xorg not starting on x200 due to recent commit Christopher Allan Webber
2017-09-25 0:15 ` Chris Marusich
2017-09-25 14:45 ` Christopher Allan Webber [this message]
2017-09-25 19:33 ` Leo Famulari
2017-09-25 22:01 ` Chris Marusich
2017-09-26 10:39 ` Ricardo Wurmus
2017-09-26 13:06 ` Christopher Allan Webber
2017-12-22 22:19 ` Christopher Lemmer Webber
2017-12-22 22:25 ` Danny Milosavljevic
2017-12-23 3:12 ` Mark H Weaver
2017-12-24 17:59 ` Christopher Lemmer Webber
2017-12-25 3:08 ` Mike Gerwitz
2017-12-25 11:42 ` ng0
2017-12-25 12:01 ` ng0
2017-12-25 11:02 ` Ricardo Wurmus
2017-12-28 18:20 ` Christopher Lemmer Webber
2017-12-24 3:32 ` Mike Gerwitz
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=87y3p2suou.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=28578@debbugs.gnu.org \
--cc=cmmarusich@gmail.com \
/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.