Bug 96766 - OS doesn't let RetroArch enter exclusive fullscreen at custom resolutions
Summary: OS doesn't let RetroArch enter exclusive fullscreen at custom resolutions
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/DDX/Xorg (show other bugs)
Version: 7.7 (2012.06)
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-01 18:32 UTC by Daniil Zhilin
Modified: 2018-07-23 18:40 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Log (67.54 KB, text/plain)
2016-07-04 09:40 UTC, Daniil Zhilin
no flags Details
xrandr (7.83 KB, text/plain)
2016-07-04 09:40 UTC, Daniil Zhilin
no flags Details
xdpyinfo (118.14 KB, text/plain)
2016-07-04 09:41 UTC, Daniil Zhilin
no flags Details

Description Daniil Zhilin 2016-07-01 18:32:03 UTC
I'm trying to create an ultrawide resolution (namely 3840x480) setup as described there: http://emulation.gametechwiki.com/index.php/Display_FAQ#240p.2F480i, but I get an X error message when trying to enter exclusive fullscreen mode.

Error message:
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  152 (XFree86-VidModeExtension)
  Minor opcode of failed request:  10 (XF86VidModeSwitchToMode)
  Value in failed request:  0x4aa
  Serial number of failed request:  31
  Current serial number in output stream:  33

I've discussed this issue on libretro forums:
http://libretro.com/forums/showthread.php?t=4228&p=39048&viewfull=1#post39048

The only option specified in the device config is "TearFree" "on".
Comment 1 Daniil Zhilin 2016-07-02 18:52:20 UTC
I have just discovered that other custom resolutions like 640x448 don't work in RetroArch either, though this one displays a generic "[GLX]: Entering true fullscreen failed. Will attempt windowed mode." message. I've edited the issue title.
Comment 2 Michel Dänzer 2016-07-04 02:09:51 UTC
Please attach the corresponding Xorg log file and the output of

 xrandr --verbose

and

 xdpyinfo -ext XFree86-VidModeExtension

when the problem occurs.
Comment 3 Daniil Zhilin 2016-07-04 09:40:00 UTC
Created attachment 124888 [details]
Log
Comment 4 Daniil Zhilin 2016-07-04 09:40:35 UTC
Created attachment 124889 [details]
xrandr
Comment 5 Daniil Zhilin 2016-07-04 09:41:11 UTC
Created attachment 124890 [details]
xdpyinfo
Comment 6 Michel Dänzer 2016-07-04 10:01:00 UTC
AFAICT Xorg is probably using DVI-0 as the compatibility output for the XFree86-VidModeExtension extension, so it can't find the mode RetroArch is trying to set.

Ideally, RetroArch would use the RandR extension for changing the mode.
Comment 7 Daniil Zhilin 2016-07-04 14:06:14 UTC
So whose bug is this supposed to be? Here's the report in the RetroArch issue tracker.
https://github.com/libretro/RetroArch/issues/3009
Comment 8 Michel Dänzer 2016-07-05 00:55:55 UTC
I'm not sure if it's a RetroArch or Xorg bug, but I'm quite sure it's not a driver bug, which is why I reassigned it to Xorg for now.
Comment 9 Daniil Zhilin 2016-07-05 09:52:38 UTC
Ah, OK then. Thanks for the help.
Comment 10 Diego Viola 2016-10-10 23:48:25 UTC
I'm having a similar/different issue with RetroArch here: bug 96767

If anyone can help I'd highly appreciate it.
Comment 11 Diego Viola 2018-07-20 03:27:52 UTC
Is this still an issue?
Comment 12 Daniil Zhilin 2018-07-23 18:40:37 UTC
Seems to be fixed now.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.