all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: Mark H Weaver <mhw@netris.org>
Cc: Andy Wingo <wingo@pobox.com>, 28578@debbugs.gnu.org
Subject: bug#28578: xorg not starting on x200 due to recent commit
Date: Sun, 24 Dec 2017 11:59:11 -0600	[thread overview]
Message-ID: <87fu800zyo.fsf@dustycloud.org> (raw)
In-Reply-To: <87mv2am92t.fsf@netris.org>

Mark H Weaver writes:

> Danny Milosavljevic <dannym@scratchpost.org> writes:
>
>> (Does anyone mind
>>> pasting their equivalent lspci output who's saying "it works for me" on
>>> an x200?  I wonder if we can find the soruce of the difference.)
>>
>> 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
>> 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
>> 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
>>
>> X works fine here...
>
> X also works fine on my X200 running GuixSD, although I confess I've not
> yet gotten around to reflashing Libreboot on this machine since I had to
> replace its motherboard some months ago.  I'm not sure if the use of
> Libreboot is relevant to this issue, but I would not rule out that
> possibility, since both Libreboot and the X200 proprietary BIOS perform
> early initialization of the graphics hardware.

Yeah, you're quite likely right.

I'm running Libreboot, but it may be a different version than others are.

> Here's the relevant excerpt of my lspci output:
>
> 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
> 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
> 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
>
> Does the lspci output look different for your X200?
>
>        Mark

It looks the same.  Maybe the Libreboot version is responsible... I'm
not sure.

In the meanwhile, I've figured maybe I could test trying to set up xorg
to use a specific driver to see if that fixes it:

  (services (cons*
             ;;; ...
             (modify-services %desktop-services
                              (slim-service-type
                               startx =>
                               (xorg-start-command
                                #:configuration-file
                                (xorg-configuration-file
                                 #:drivers '("intel")))))))

However, Guix is unhappy about this:

gnu/services/xorg.scm:451:28: In procedure slim-shepherd-service:
gnu/services/xorg.scm:451:28: In procedure slim-configuration-auto-login-session: Wrong type argument: #<<program-file> name: "startx" gexp: #<gexp (apply execl #<gexp-input #<<program-file> ... 

it also doesn't work with just (xorg-start-command) either.

I'm nowhere near a modify-services expert.  Anyone have any clues?

Thanks for all the help :)

  reply	other threads:[~2017-12-24 18:00 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
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 [this message]
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=87fu800zyo.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=28578@debbugs.gnu.org \
    --cc=mhw@netris.org \
    --cc=wingo@pobox.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.