From: Hans de Goede <hdegoede@redhat.com>
To: Timo Aaltonen <tjaalton@ubuntu.com>, intel-gfx@lists.freedesktop.org
Cc: Rob Clark <rclark@redhat.com>, Adam Jackson <ajax@redhat.com>
Subject: Re: [RFC/PATCH xf86-video-intel] sna: Let modestting + glamor handle gen9+
Date: Fri, 22 Apr 2016 20:05:12 +0200 [thread overview]
Message-ID: <571A67D8.2090603@redhat.com> (raw)
In-Reply-To: <571A2465.1060702@ubuntu.com>
Hi,
On 22-04-16 15:17, Timo Aaltonen wrote:
> 08.04.2016, 16:21, Hans de Goede kirjoitti:
>> Hi,
>
> Hi, sorry for the delay..
>
>> On 11-03-16 11:07, Timo Aaltonen wrote:
>>>
>>> I've been trying to make this work, but there are cases where it fails
>>> bad:
>>>
>>> # a config file with a Device section that loads 'intel' makes the
>>> server fail
>>> [ 10.153] (EE) No devices detected.
>>> [ 10.153] (EE)
>>> Fatal server error:
>>> [ 10.153] (EE) no screens found(EE)
>>>
>>> ie. no fallback in that case
>>>
>>> # with X run as root (wrapper or not), same thing different cause
>>> [ 145.943] (EE) modeset(0): drmSetMaster failed: Invalid argument
>>> [ 145.943] (EE)
>>> Fatal server error:
>>> [ 145.943] (EE) AddScreen/ScreenInit failed for driver 0
>>>
>>>
>>> but it does work with startx run by a user. Tests done on Debian with
>>> 1.18.1 and intel ddx git.
>>
>> This must be some Debian specific issue, I just tried this with Xorg-1.18.3
>> on Fedora, with a Xwrapper.config forcing X to always run as root and it
>> works
>> fine (using startx).
>
> We have a similar wrapper in 'xserver-xorg-legacy' package, but even
> installing that doesn't make xdm work, the xserver fails the same way.
>
> startx _does_ work though
>
>> In that case systemd-logind integration should still work though, so it may
>> be that the way you are starting Xorg causes the systemd-logind integration
>> to not work though, and that the fallback paths for opening the
>> /dev/drm/card#
>> in the modesetting driver are broken. How exactly are you starting X ?
>
> Trying to use a DM other than gdm, in this case xdm. (iirc lightdm fails
> too)
>
>> Can you provide full logs of a failed start ?
>
> Xorg.0.log
> http://paste.debian.net/440250/
Ok, I've managed to reproduce this, this is caused by a pre-existing bug in
the intel driver. I've just send out a patch fixing this.
Regards,
Hans
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-04-22 18:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 14:47 [RFC/PATCH xf86-video-intel] sna: Let modestting + glamor handle gen9+ Hans de Goede
2016-03-11 10:07 ` Timo Aaltonen
2016-03-13 19:36 ` Rob Clark
2016-03-14 7:39 ` Hans de Goede
2016-04-08 13:21 ` Hans de Goede
2016-04-22 13:17 ` Timo Aaltonen
2016-04-22 18:05 ` Hans de Goede [this message]
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=571A67D8.2090603@redhat.com \
--to=hdegoede@redhat.com \
--cc=ajax@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rclark@redhat.com \
--cc=tjaalton@ubuntu.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.
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.