unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: 28578@debbugs.gnu.org
Subject: bug#28578: xorg not starting on x200 due to recent commit
Date: Sun, 24 Sep 2017 17:15:02 -0700	[thread overview]
Message-ID: <87fubb1vnd.fsf@gmail.com> (raw)
In-Reply-To: <87a81k86jt.fsf@dustycloud.org> (Christopher Allan Webber's message of "Sun, 24 Sep 2017 10:23:02 -0500")

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

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?

-- 
Chris

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

  reply	other threads:[~2017-09-25  0:16 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 [this message]
2017-09-25 14:45   ` Christopher Allan Webber
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

  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=87fubb1vnd.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=28578@debbugs.gnu.org \
    --cc=cwebber@dustycloud.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).