sna: Let modestting + glamor handle gen9+
sna has no meaningfull accel for gen9+, this causes problems with i.e. apps using XVideo since the sprite XVideo support does not work well for many apps.
Therefor it is better to just let the xserver fall back to modesetting + glamor. This is implemented by returning FALSE from the probe methods, just like how nouveau handles falling back to modesetting for newer cards.
--- src/intel_module.c | 7 +++++++ 1 file changed, 7 insertions(+)
src/intel_module.c +7 -0
@@ -571,6 +571,13 @@ intel_scrn_create(DriverPtr driver,return FALSE; } +/* +* We've no accel support for these, so let modesetting + glamor +* handle them. +*/ +if ((unsigned )((struct intel_device_info *)match_data)->gen >=0110 ) +return FALSE; + scrn =xf86AllocateScreen (driver, flags);if (scrn ==NULL )return FALSE;
Signature · 6 lines
2.7.2 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
29.02.2016, 16:47, Hans de Goede kirjoitti:
Quoted 10 lines
sna has no meaningfull accel for gen9+, this causes problems with i.e. apps using XVideo since the sprite XVideo support does not work well for many apps.
Therefor it is better to just let the xserver fall back to modesetting + glamor. This is implemented by returning FALSE from the probe methods, just like how nouveau handles falling back to modesetting for newer cards.
Signed-off-by Hans de Goede <[email protected]>
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.
Signature · 5 lines
t _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 12 lines · Timo Aaltonen
29.02.2016, 16:47, Hans de Goede kirjoitti:
Quoted 10 lines
sna has no meaningfull accel for gen9+, this causes problems with i.e. apps using XVideo since the sprite XVideo support does not work well for many apps.
Therefor it is better to just let the xserver fall back to modesetting + glamor. This is implemented by returning FALSE from the probe methods, just like how nouveau handles falling back to modesetting for newer cards.
Signed-off-by Hans de Goede <[email protected]>
Quoted 8 lines
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)
I'd be awfully tempted to call that NOTABUG.. I mean, it would fail in same way if you had a .conf that tried to force ati ddx on a system without a radeon card..
BR,
-R
Quoted 12 lines
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 0but it does work with startx run by a user. Tests done on Debian with 1.18.1 and intel ddx git.
Quoted 6 lines
--
t
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Hi,
Quoted 22 lines · Rob Clark
Quoted 12 lines · Timo Aaltonen
29.02.2016, 16:47, Hans de Goede kirjoitti:
Quoted 10 lines
sna has no meaningfull accel for gen9+, this causes problems with i.e. apps using XVideo since the sprite XVideo support does not work well for many apps.
Therefor it is better to just let the xserver fall back to modesetting + glamor. This is implemented by returning FALSE from the probe methods, just like how nouveau handles falling back to modesetting for newer cards.
Signed-off-by Hans de Goede <[email protected]>Quoted 8 lines
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)
Quoted 3 lines
I'd be awfully tempted to call that NOTABUG.. I mean, it would fail in same way if you had a .conf that tried to force ati ddx on a system without a radeon card..
Ack, as for the modesetting driver only working when using the systemd-logind integration and not when running the old way, that needs someone to look into it.
I've put this on my todo list, but I'm not sure when I'll get around to it.
Regards,
Hans
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Hi,
Quoted 30 lines · Timo Aaltonen
29.02.2016, 16:47, Hans de Goede kirjoitti:
Quoted 10 lines
sna has no meaningfull accel for gen9+, this causes problems with i.e. apps using XVideo since the sprite XVideo support does not work well for many apps.
Therefor it is better to just let the xserver fall back to modesetting + glamor. This is implemented by returning FALSE from the probe methods, just like how nouveau handles falling back to modesetting for newer cards.
Signed-off-by Hans de Goede <[email protected]>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
Quoted 2 lines
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).
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 ?
Can you provide full logs of a failed start ?
Regards,
Hans
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
08.04.2016, 16:21, Hans de Goede kirjoitti:
Quoted 1 line
Hi,
Hi, sorry for the delay..
Quoted 21 lines · Timo Aaltonen
Quoted 20 lines
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
Quoted 7 lines
Quoted 2 lines
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
Quoted 5 lines
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)
Quoted 1 line
Can you provide full logs of a failed start ?
Xorg.0.log
http://paste.debian.net/440250/
xdm.log
http://paste.debian.net/440252/
(ignore the first entries with a working driver)
Signature · 5 lines
t _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Hi,
Quoted 45 lines · Timo Aaltonen
08.04.2016, 16:21, Hans de Goede kirjoitti:
Quoted 1 line
Hi,
Hi, sorry for the delay..
Quoted 21 lines · Timo Aaltonen
Quoted 20 lines
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 0Quoted 7 lines
Quoted 2 lines
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
Quoted 5 lines
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 ?
Quoted 7 lines
Trying to use a DM other than gdm, in this case xdm. (iirc lightdm fails too)
Quoted 1 line
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
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx