xorg not starting on x200 due to recent commit

  • Done
  • quality assurance status badge
Details
8 participants
  • Chris Marusich
  • Christopher Allan Webber
  • Danny Milosavljevic
  • Leo Famulari
  • Mark H Weaver
  • Mike Gerwitz
  • ng0
  • Ricardo Wurmus
Owner
unassigned
Submitted by
Christopher Allan Webber
Severity
normal

Debbugs page

Christopher Allan Webber wrote 7 years ago
(address . bug-guix@gnu.org)
87a81k86jt.fsf@dustycloud.org
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?
Chris Marusich wrote 7 years ago
(name . Christopher Allan Webber)(address . cwebber@dustycloud.org)(address . 28578@debbugs.gnu.org)
87fubb1vnd.fsf@gmail.com
Christopher Allan Webber <cwebber@dustycloud.org> writes:

Toggle quote (15 lines)
> 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
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlnISoYACgkQ3UCaFdgi
Rp0aWxAAtziN5rtjF7zf6gDQ48/siScMbPESewr87VWFNNIOv6wPaxb8ABJBZNc2
RfItKRWIy6LLEFBvUH8l4xF0BM+RH8Qf7cqZZ+0aelILtNGEQQIkVRj+X14VgiGy
/pnD43TIB+ljvm03ASJt3OzStkHqNEkL/CN6fFw/hMEpZYCMG7bJBWoKz2p+qivd
eGbiwavqTiR4wUNYBMExWecao6AHPfv72u7fx30VRfzpZoXPpRp1pnmPFE1VikOQ
NPSWYALQoW+oZxQz3lO2NoL9Mg1mcTgO65sZtA9htvAvX0q23eXuGZQMP5a0fBoW
mBtNSwDMiahj8Dj/G0bN2GVZXkzGxl6rCMhaRFuaIrN+DkUIRpapm8cjoVYSisoN
JQMMTt1ZilqJSg/ibZrpNBOle1ZlAMJ15uM5IJGaZ9Xe+rYyxw9D7IIxJjK/eabc
lQETecOSo2enAef740V7rbqeYmhCcHLAhpw1izj7mM0/tk259PBbSZHrA7a/53eI
MxltHcyg7JkdO2+vOBrvrIvH/vcV6chGAO2Gwri1htE2WUIO1MdB5Cjb4/sT9mmN
+IPvDq5kkUdAWPyaxXiYD8iwfwxQf6Qhxk2RldW5Iup4Z5HCUiJzeqEARrfKOdHP
wDSqJIkzZE57vi9MSN7+7JD6dnCOon9zTiO3HVoOJAm5i0pP1Jg=
=j5tl
-----END PGP SIGNATURE-----

Christopher Allan Webber wrote 7 years ago
(name . Chris Marusich)(address . cmmarusich@gmail.com)(address . 28578@debbugs.gnu.org)
87y3p2suou.fsf@dustycloud.org
Chris Marusich writes:

Toggle quote (21 lines)
> 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?
Leo Famulari wrote 7 years ago
(name . Chris Marusich)(address . cmmarusich@gmail.com)
20170925193354.GA12982@jasmine.lan
On Sun, Sep 24, 2017 at 05:15:02PM -0700, Chris Marusich wrote:
Toggle quote (21 lines)
> 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.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlnJWiIACgkQJkb6MLrK
fwjxiQ/+Jlsxkssg/324iuXDxCbk79BQID95EBnb6foZjvhWr8MXSeEB7qDeYDoN
Hh+AvEtvHL0TSAzfyKa3ZEtNPaudhyIMUfylncs4Flk2UuN23hsZAfqs2NyGsybu
alAeakac+aHqyXidfmS/0K8Kp4PIxRwP+RnwEpqo35DTYfGw2DQCuiz7liBm7eMm
M9yTkczwTDVjI7hhJwYIaTL2aGo8w1D+Jrl72K3BzNCp/BEe2DN3KQ+S4eGGpj7/
jJFFqWKXIZiqqcsscFlULFBrki2grqGBeGZto4GOeVsLd6iVsrPvmAMdGPS3NH9Y
SvYB0L3G1ZcVyzBCwWnjvQnthvGAADU5ZrYjdCWEvSAmSvd2uB2P+Vrpl1hJicrV
6x1zStrWXEosuQJb9esobozLc/TKccitJmlC5XfgjzVQfcd5lh6u9K5dG1OmiTIn
MaCLBobHDr1nV3MLc9x6NgxV9ArkgZr3AuqVnV9+M17cIrABlHd8s8FVSspuRCoR
27aPmRyt+5q6QAH+wov3gvDDedKHLRcIl3AR9NrP6/4Vhm55dqNnsA5FMaJDtVz0
CNu4xRRMtM93GEzDrpzbVRS/jmJD8gtgiFlVh4tYCMkV778sywHykEf3+oOoKL50
SDONVq6ABWSQsVnw/mXcCN6JBCaEPKxmq47ZHbHJOGbBCSywekM=
=K5SM
-----END PGP SIGNATURE-----


Chris Marusich wrote 7 years ago
(name . Leo Famulari)(address . leo@famulari.name)
87a81izbcd.fsf@gmail.com
Leo Famulari <leo@famulari.name> writes:

Toggle quote (25 lines)
> 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
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlnJfNIACgkQ3UCaFdgi
Rp1v8xAAq23LP2y04Bcf8Q9yWbiaJEBnCTHYf0hn85m1ANXeedu4NLff+6v25pjs
mtgAsVdDM0a9jVK0Ks4VIceccLBp/VoPWfFnIB52oN4OSJyqavfW9goZ+AnTKjwA
zC0g5diRnAXbgwnFT46kKjbKjzzJZEaSDBBHD08yjtXijYi5o6AJmF1jzm3rW+zW
MQCZKr8GvQJ71XAOgUtrxmNSGXgeM1lCnQzcWTixK1jqgCdr+hZxLn+MnUppdzE+
CH7mGM+ZP/DfRp/ssw04pxd2SkrtChZGQYrF6vyMZNnfiLa0yX8Et/uhOg0mIgcL
OhU+AYnqSTS9sAyK4X6nThYb0Ha65xmN4VtgePtFujDVW9yQSnf+fNkLrdhm3saF
nW1zXEqTIONXr5GqDywMSka1VTirIgzybtOPYN/paJ4afjsx2qANFs7T1nvu4XiE
H7AhmhUVWZcom+cZGPfpZDmx3ClTw904prAi9lkH4ufblQd50DdeYHQB9nHYAVsc
TAysd4EqNowW3oWcAam+Hj4QWRz0P4v9iySezgZn2FChADOtzssV0PgCezrz3W3c
E1qWI4j7a3Ah55KALR3rh2sYjQQjSSiyj5aZ5QzeRFgI3gVYdB5VCDYgCmEEeHVT
ck9nO5vZLBifO0S5s1578wia/oUWANlcgxhD4TsG7y4VFue/bCs=
=FHy9
-----END PGP SIGNATURE-----

Ricardo Wurmus wrote 7 years ago
(name . Chris Marusich)(address . cmmarusich@gmail.com)
87o9px68wf.fsf@elephly.net
Chris Marusich <cmmarusich@gmail.com> writes:

Toggle quote (35 lines)
> 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
Christopher Allan Webber wrote 7 years ago
(name . Chris Marusich)(address . cmmarusich@gmail.com)
87k20lsj7i.fsf@dustycloud.org
Chris Marusich writes:

Toggle quote (35 lines)
> 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)
Christopher Lemmer Webber wrote 7 years ago
(address . 28578@debbugs.gnu.org)
87fu82mmm3.fsf@dustycloud.org
Christopher Allan Webber writes:

Toggle quote (22 lines)
> 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.

Toggle quote (22 lines)
>>>> 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
Danny Milosavljevic wrote 7 years ago
(name . Christopher Lemmer Webber)(address . cwebber@dustycloud.org)
20171222232545.1b663977@scratchpost.org
(Does anyone mind
Toggle quote (3 lines)
> 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...
Mark H Weaver wrote 7 years ago
(name . Danny Milosavljevic)(address . dannym@scratchpost.org)
87mv2am92t.fsf@netris.org
Danny Milosavljevic <dannym@scratchpost.org> writes:

Toggle quote (10 lines)
> (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
Mike Gerwitz wrote 7 years ago
(name . Christopher Lemmer Webber)(address . cwebber@dustycloud.org)
87o9mossw4.fsf@gnu.org
On Fri, Dec 22, 2017 at 16:19:48 -0600, Christopher Lemmer Webber wrote:
Toggle quote (15 lines)
>> 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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJaPx+7AAoJEIyRe39dxRuiDEEQAMde9ybut4s8iSkmbz73srom
G7/aOVSJJhjeuKHoNWVfYpNRHwMOA12wKKlkzY0sf7kfvhv+FvbtwTZ/dVBwaMRO
EiH34WcNtxivPzltSfXs5SyTuA44fftBDD0MGidKQmMNEaE85TuncnZkdmzF7GSY
FP7oPv3JeCzkTrrXj7QJB6GOjDRBsZVhTDOTjkwl7ixWOLzH0aduuhaDpJoooqMP
aziW+nRBCZZBwk4ME5aLx8xVaTX65gQW8hYxUolWFQEtljBhz59g4PLqQoDqpozF
Pel0nYBJ72fblRxHYs4E1z5m/NlcAF5HzH92V/utV0gayYKhJQwhReOnOQkaae56
CK0bhOGTLizIH/RhjZGrE5LrRE+HKMkyLpPjJvz0k4ePA1vDJ8NmylAjH4JuLQtj
Dn7iEQqLIyH/9fbVabPSLrb5RQqxS6NY7N2+zF09edXmxiy88SBBQZgom5RmR30I
QteFW2IZQyDlu3+jC7UNxS5so+TJy4uIomb14y4+LvLx6VWQXoRi+Ec/L6T9CU6u
tPv1wLZc3pfi1VCdm/0LHeQubJ37myP031Wuhhlw3iMUZJaubZXVEWy1lgkf53Ni
90SuFC1qVGk8pmULnKAsLynEX3pDE+ouoVlxCZrwMzk0p7Op/pupByOAl86yggG8
wcIq3Ka+5EEuVk4Xvm+Q
=Qqdu
-----END PGP SIGNATURE-----

Christopher Lemmer Webber wrote 7 years ago
(name . Mark H Weaver)(address . mhw@netris.org)
87fu800zyo.fsf@dustycloud.org
Mark H Weaver writes:

Toggle quote (19 lines)
> 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.

Toggle quote (10 lines)
> 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 :)
Mike Gerwitz wrote 7 years ago
(name . Christopher Lemmer Webber)(address . cwebber@dustycloud.org)
877etbqzav.fsf@gnu.org
On Sun, Dec 24, 2017 at 11:59:11 -0600, Christopher Lemmer Webber wrote:
Toggle quote (3 lines)
> 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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJaQGvJAAoJEIyRe39dxRui0SQP/A0SFk3DIWqqh50xbzfdaTeO
PvEj9FlyiWyb4Q6Z9xzMU8frW0JfYVICicqrxm6nYGlfdA7mjE2fN1QBNRQM5bCy
XvYNmvbjBDAEOw2SBRqoeep5zotgYHMzO18cyZqBFiZw1gAZgkrFZ0RCZs7DO1rV
q35H2QkxBNKlWkM5ggbjh39zxMjwbMFPPofwykm3OKYNW6SU3N5WpZUnPI1I6qsx
XfP21+iuYfdzLzc5CNyLYab5RzuNEx94v/V1rgcbPRvF1eI6F3WbeKbV/mo89Pwa
vIkOfcBfmCCOgEp+yzIyuqRfgxrlHU8hgF7xO0EJQDqr2fPkyywi5v6mpX8IQGn9
rGdj5neQGJ784Q2QwMK/I+Q+oiT4Abi1/n2Nrva1imK1CqRId0SUXJD18UxNwOEe
fjznGaKhPamRhZuwjpawZoOI192PXo4bfRvzwIICQQE00f9iY+nVPJwmRB7Nvzss
m7o03DdJlQ9AXYK7zralkTk7eJ68f6K1nOi/Bry/sfLsGalAIlyJL5XVjcnezX68
YpYETZAmoY0slRa/hKDMV+0O2cPzaITnufzEOkOcKST5BvCsDvKg5DeovCzi8Fgq
bouYotkRFWIBdrDQXFUbIHPJf21XmGdPoHZgD1xw0loGWSX25H+6DNpx2//n2sLc
hQHWsrigB5MOBiIjChiz
=Z860
-----END PGP SIGNATURE-----

Ricardo Wurmus wrote 7 years ago
(name . Christopher Lemmer Webber)(address . cwebber@dustycloud.org)
87incvvzmz.fsf@elephly.net
Hi,

Toggle quote (13 lines)
> 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
ng0 wrote 7 years ago
(name . Mike Gerwitz)(address . mtg@gnu.org)
20171225114239.ku5obh7mvtbo6dmb@abyayala
Mike Gerwitz transcribed 1.6K bytes:
Toggle quote (18 lines)
> 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
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAlpA5C8ACgkQ4i+bv+40
hYiyTg//VGD/EdBg+dG1FLUzQFI2Bg4uuFIj0x3JQkKf4uZ6dBvGCthWibf64BY2
GCU/JBNWXvHWcC4hLILDsEwfDq5kSIwBqPTRw+tI62uAJV7a26PX00vJPQ703ApW
zUWphEvKaJITAxhNqN2gQYiJPZ1oneDTkoPTQkREQ3zk0lpSwdFqK2AtyitPSq2S
QhISUJUhqSYMzK8U3ZFxIwldG/SVmJHMHKyX5jVvKOgi8FujDlGjifvUYtrjdNW9
CZnDDl0Tyk5qTr5SS7RZS9YbaXO7aUTo30AIjRNzNufX+Y222RFZ39OxoHgy4eE/
otbHc1FvDIDEQxVQwJF0FRsyRRtDuxxOPrewH03xmbMbCA/aP68QcgTkX060siMq
ZWsv0grg7MaCDizn3gQoQQHiR6sdHj2Wa5yzNSdWXwEN+obBgn5zW3tAy4R93U0/
l8GGSbCaN7rho5ec0UX0ujHIVgKiF9EZD0jITCnix2H+DW85G2x9C0kHEomny+JG
PXCDUKOdK76QiGPejbbVqbzERpzAo7rdS7F6WXyR8kyY+kwt5Fjp06xQWLmbXaHL
L7C5yZcZGjdexmZCFkl3DKaAkC2K31KwKQk0d2GFXCfwsXWBupbEjx0+RYIOi1x4
X0UkJn35N4zawtxJDLE7GJu2Yqp5tPx/jzPBlMDV4QUMcNEFP0w=
=KQ4j
-----END PGP SIGNATURE-----


ng0 wrote 7 years ago
(name . Mike Gerwitz)(address . mtg@gnu.org)
20171225120136.s47pl7mt44cczehu@abyayala
ng0 transcribed 2.1K bytes:
Toggle quote (23 lines)
> 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.

Toggle quote (7 lines)
> --
> GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
> GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
> WWW: https://n0.is



--
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAlpA6KAACgkQ4i+bv+40
hYhIjRAAqDxlqubNAy7pZ+OEODWn6+exAV2kEioZzzNbHFal8hWBDijCNPOaSGyY
9XDX6DLIjH5utOnv9snaODgqEOlsGWzvLdN3RCp78PQxCOh3LrXoEEkBxzmfX4pa
B+aq/i/VK/EWVGA7iRkQuJC3lm1NJ4Fk9YqWCEzH1TgvEauLL9zqVDVmWUrn0e2f
avPA+bLuuXGf17Ht1KR4DK7L3Rw2o40j/SI0oU6Go8dgaS6GI5WrjBjwwykGfYXp
2ukqjK+WVNrFn5pxbYyYsQruKi/zdNcZhXaW5uPhzIeCQMbWLEf8aI7FPRwTbqPi
MWp2JkgVSqHwjsyexNyC8dk8tEhd9sJrtDaTXU4UyVrJ9giLxRHC0T3sC7xaJdgy
frmeoLKEoxN1xrjswALcOk5Hdgp/Z9lbCx1zAVhEmV8t2YPvsgWp0ySJEA2ZalRj
8uUyU+8jKGafErAiS6Vs8rvEgId0b7ydTXxmMnxxJpPs6z28OsRz8Y1R8IVbuLZJ
qtUW2r0w+PHtLtK+APjj3ENQovfsmBDgkdcRHJa5WPZsWmzybrac4ekzEg20ofVB
51nqi1IX3W0o0GZEExkBMHtD8GhrJfuOr8ligK9g8XrerLHQKf8coHni9gn3HJIx
+GJA0YJE+1f6A/vLjEq1r0xwVeBGHj8U+FynQoXg/JLZmAY7bHE=
=ISGx
-----END PGP SIGNATURE-----


Christopher Lemmer Webber wrote 7 years ago
(name . Ricardo Wurmus)(address . rekado@elephly.net)
87a7y2yaso.fsf@dustycloud.org
Ricardo Wurmus writes:

Toggle quote (32 lines)
> 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!
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 28578@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 28578
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch
You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags
mumi command -t +confirmed -t +easy
Or, remove the moreinfo tag and set the help tag
mumi command -t -moreinfo -t +help