bug#28578: xorg not starting on x200 due to recent commit

bug#28578: xorg not starting on x200 due to recent commit

[Christopher Allan Webber]

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?

bug#28578: xorg not starting on x200 due to recent commit

[Chris Marusich]

[-- 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 --]

bug#28578: xorg not starting on x200 due to recent commit

[Christopher Allan Webber]

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?

bug#28578: xorg not starting on x200 due to recent commit

[Leo Famulari]

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

On Sun, Sep 24, 2017 at 05:15:02PM -0700, Chris Marusich wrote:
> 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?

I don't know if it's relevant, but note that the X200 and X200s are
different models.

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

bug#28578: xorg not starting on x200 due to recent commit

[Chris Marusich]

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

Leo Famulari <leo@famulari.name> writes:

> On Sun, Sep 24, 2017 at 05:15:02PM -0700, Chris Marusich wrote:
>> 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?
>
> I don't know if it's relevant, but note that the X200 and X200s are
> different models.

It might be relevant.  I thought Chris was using the word "x200s" as in
"two or more x200 computers", but perhaps he meant the model "x200s".  I
do not have an x200s; I have an x200.

Also, yes, I use Libreboot, but I am not sure why that would matter for
something like xorg, which comes into action late in the boot process,
long after Libreboot hands off control to the operating system.

-- 
Chris

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

bug#28578: xorg not starting on x200 due to recent commit

[Ricardo Wurmus]

Chris Marusich <cmmarusich@gmail.com> writes:

> Leo Famulari <leo@famulari.name> writes:
>
>> On Sun, Sep 24, 2017 at 05:15:02PM -0700, Chris Marusich wrote:
>>> 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?
>>
>> I don't know if it's relevant, but note that the X200 and X200s are
>> different models.
>
> It might be relevant.  I thought Chris was using the word "x200s" as in
> "two or more x200 computers", but perhaps he meant the model "x200s".  I
> do not have an x200s; I have an x200.
>
> Also, yes, I use Libreboot, but I am not sure why that would matter for
> something like xorg, which comes into action late in the boot process,
> long after Libreboot hands off control to the operating system.

FWIW, I use an X200s with Libreboot and I have no problems with Xorg
after reconfiguring the system.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

bug#28578: xorg not starting on x200 due to recent commit

[Christopher Allan Webber]

Chris Marusich writes:

> Leo Famulari <leo@famulari.name> writes:
>
>> On Sun, Sep 24, 2017 at 05:15:02PM -0700, Chris Marusich wrote:
>>> 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?
>>
>> I don't know if it's relevant, but note that the X200 and X200s are
>> different models.
>
> It might be relevant.  I thought Chris was using the word "x200s" as in
> "two or more x200 computers", but perhaps he meant the model "x200s".  I
> do not have an x200s; I have an x200.
>
> Also, yes, I use Libreboot, but I am not sure why that would matter for
> something like xorg, which comes into action late in the boot process,
> long after Libreboot hands off control to the operating system.

I run an x200 as well.  In case it is useful, here is the output of
lspci cut down to video-relevant stuff.

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)

bug#28578: xorg not starting on x200 due to recent commit

[Christopher Lemmer Webber]

Christopher Allan Webber writes:

> Chris Marusich writes:
>
>> Leo Famulari <leo@famulari.name> writes:
>>
>>> On Sun, Sep 24, 2017 at 05:15:02PM -0700, Chris Marusich wrote:
>>>> 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?

It's been several months since I filed this, but I was in last-minute
crunch with ActivityPub so I decided to just hold off on addressing
it... "mabye a later upgrade would fix it" I figured.

Unfortunately, it hasn't. :(  When I try to boot into any newer version
of a system profile since this commit I still can't pull up xorg.  It
just hangs, and xorg's logs tell me nothing useful as to why.  But since
it only happened since *immediately after* this commit, I must assume
it's for that reason.

It's not fun being unable to upgrade your system profile... I'm worried
about falling behind on serious security issues.

>>>> 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?
>>>
>>> I don't know if it's relevant, but note that the X200 and X200s are
>>> different models.
>>
>> It might be relevant.  I thought Chris was using the word "x200s" as in
>> "two or more x200 computers", but perhaps he meant the model "x200s".  I
>> do not have an x200s; I have an x200.
>>
>> Also, yes, I use Libreboot, but I am not sure why that would matter for
>> something like xorg, which comes into action late in the boot process,
>> long after Libreboot hands off control to the operating system.
>
> I run an x200 as well.  In case it is useful, here is the output of
> lspci cut down to video-relevant stuff.
>
> 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)

It seems that others aren't having troubles with this on their x200
machines, but well, I still am (though mine is a refurbished x200, and
there are some differences between different x200 machines anyway, so
maybe that accounts for the difference).  Unfortunately being unable to
upgrade my x200 system profile is fairly serious.  (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.)

Andy, do you know how urgent this patch is?  I'd like to propose
reverting it if it's not serious to anyone else, because otherwise else
it looks like I will be forced to switch machines or something else
drastic, and I'd really rather not...

 - Chris

bug#28578: xorg not starting on x200 due to recent commit

[Danny Milosavljevic]

(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...

bug#28578: xorg not starting on x200 due to recent commit

[Mark H Weaver]

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.

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

bug#28578: xorg not starting on x200 due to recent commit

[Mike Gerwitz]

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

On Fri, Dec 22, 2017 at 16:19:48 -0600, Christopher Lemmer Webber wrote:
>> I run an x200 as well.  In case it is useful, here is the output of
>> lspci cut down to video-relevant stuff.
>>
>> 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)
>
> It seems that others aren't having troubles with this on their x200
> machines, but well, I still am (though mine is a refurbished x200, and
> there are some differences between different x200 machines anyway, so
> maybe that accounts for the difference).  Unfortunately being unable to
> upgrade my x200 system profile is fairly serious.  (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)

I'm running Libreboot.

-- 
Mike Gerwitz
Free Software Hacker+Activist | GNU Maintainer & Volunteer
GPG: D6E9 B930 028A 6C38 F43B  2388 FEF6 3574 5E6F 6D05
https://mikegerwitz.com

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

bug#28578: xorg not starting on x200 due to recent commit

[Christopher Lemmer Webber]

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 :)

bug#28578: xorg not starting on x200 due to recent commit

[Mike Gerwitz]

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

On Sun, Dec 24, 2017 at 11:59:11 -0600, Christopher Lemmer Webber wrote:
> It looks the same.  Maybe the Libreboot version is responsible... I'm
> not sure.

I just received mine recently from Libiquity and I haven't had a chance
to play around with any of the flashing tools, so I don't know my
version atm.  If you know the steps to run a suitable comparison, I'd be
happy to do so.

If you don't have it figured out by March I'll be at LP2018 if you want
to do a more hands-on comparison.

-- 
Mike Gerwitz
Free Software Hacker+Activist | GNU Maintainer & Volunteer
GPG: D6E9 B930 028A 6C38 F43B  2388 FEF6 3574 5E6F 6D05
https://mikegerwitz.com

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

bug#28578: xorg not starting on x200 due to recent commit

[Ricardo Wurmus]

Hi,

> 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")))))))

This is what my modification looks like:

                     (slim-service-type
                      config => (slim-configuration
                                 (inherit config)
                                 (startx (xorg-start-command
                                          #:configuration-file
                                          (xorg-configuration-file
                                           #:extra-config
                                           (list marble-mouse-settings
                                                 dvorak-evdev))))))

i.e. I’m capturing the default config, inherit from it, and the override
the “startx” field.  You are capturing the default config as “startx”
and then replace the configuration with the value returned by
“xorg-start-command”.  That doesn’t look right.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

bug#28578: xorg not starting on x200 due to recent commit

[ng0]

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

Mike Gerwitz transcribed 1.6K bytes:
> On Sun, Dec 24, 2017 at 11:59:11 -0600, Christopher Lemmer Webber wrote:
> > It looks the same.  Maybe the Libreboot version is responsible... I'm
> > not sure.
> 
> I just received mine recently from Libiquity and I haven't had a chance
> to play around with any of the flashing tools, so I don't know my
> version atm.  If you know the steps to run a suitable comparison, I'd be
> happy to do so.
> 
> If you don't have it figured out by March I'll be at LP2018 if you want
> to do a more hands-on comparison.
> 
> -- 
> Mike Gerwitz
> Free Software Hacker+Activist | GNU Maintainer & Volunteer
> GPG: D6E9 B930 028A 6C38 F43B  2388 FEF6 3574 5E6F 6D05
> https://mikegerwitz.com

Chris, fyi libreboot is working towards a new release now (they have started
testing machines and call out for testers), so maybe whatever you experience
will be gone with a new version of libreboot.

-- 
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
  WWW: https://n0.is

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

bug#28578: xorg not starting on x200 due to recent commit

[ng0]

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

ng0 transcribed 2.1K bytes:
> Mike Gerwitz transcribed 1.6K bytes:
> > On Sun, Dec 24, 2017 at 11:59:11 -0600, Christopher Lemmer Webber wrote:
> > > It looks the same.  Maybe the Libreboot version is responsible... I'm
> > > not sure.
> > 
> > I just received mine recently from Libiquity and I haven't had a chance
> > to play around with any of the flashing tools, so I don't know my
> > version atm.  If you know the steps to run a suitable comparison, I'd be
> > happy to do so.
> > 
> > If you don't have it figured out by March I'll be at LP2018 if you want
> > to do a more hands-on comparison.
> > 
> > -- 
> > Mike Gerwitz
> > Free Software Hacker+Activist | GNU Maintainer & Volunteer
> > GPG: D6E9 B930 028A 6C38 F43B  2388 FEF6 3574 5E6F 6D05
> > https://mikegerwitz.com
> 
> Chris, fyi libreboot is working towards a new release now (they have started
> testing machines and call out for testers), so maybe whatever you experience
> will be gone with a new version of libreboot.

Of course I meant to write: _could be_ gone.

> -- 
> GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
> GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
>   WWW: https://n0.is



-- 
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
  WWW: https://n0.is

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

bug#28578: xorg not starting on x200 due to recent commit

[Christopher Lemmer Webber]

Ricardo Wurmus writes:

> Hi,
>
>> 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")))))))
>
> This is what my modification looks like:
>
>                      (slim-service-type
>                       config => (slim-configuration
>                                  (inherit config)
>                                  (startx (xorg-start-command
>                                           #:configuration-file
>                                           (xorg-configuration-file
>                                            #:extra-config
>                                            (list marble-mouse-settings
>                                                  dvorak-evdev))))))
>
> i.e. I’m capturing the default config, inherit from it, and the override
> the “startx” field.  You are capturing the default config as “startx”
> and then replace the configuration with the value returned by
> “xorg-start-command”.  That doesn’t look right.

Thank you!  I switched it to:

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

This solved it for me... xorg is back up and running again!

So I guess if you have an old x200 or so and are having this problem
(which seemingly at the moment nobody else is, so I'm closing this): do
as I did and (hopefully) that should solve it!