[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#28578: xorg not starting on x200 due to recent commit
From: |
Christopher Lemmer Webber |
Subject: |
bug#28578: xorg not starting on x200 due to recent commit |
Date: |
Sun, 24 Dec 2017 11:59:11 -0600 |
User-agent: |
mu4e 0.9.18; emacs 25.3.1 |
Mark H Weaver writes:
> Danny Milosavljevic <address@hidden> 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, 2017/12/23