hi, this is not so much a bug report but a feature request. i tried using fullscreen opengl a few days ago and had some bad results. i'm not sure if this supposed to work this way, or just a bug of the new infrastructure. my setup: r600 chip, ddx,libdrm and mesa from git. drm-next kernel module. kms is enabled at boottime. 2d works perfect, although it feels a bit slower than non kms, nice work :) XINERAMA version 1.1 opcode: 148 head #0: 1280x1024 @ 1280,0 head #1: 1280x1024 @ 0,0 expected behavior: so, #0 is my primary head, #1 is left of #0. if i start an gl fullscreen app i would expect it to use the current head (eg. like metacity placing new windows where the mouse currently is) or the primary head (first xinerama head) and leave the other heads intact. the actual results: i tried this with etracer and doom3-demo, both switched to fullscreen on the second head (which comes first on the framebuffer) and the primary head went blank (invalid mode). after exit the monitors where put in clone mode and the resolution and refresh rate of the secondary head was applied to the primary. fyi, doom3-demo was unplayable (i expected so much), etracer looks good and i had about 50fps in windowed mode (800x600).
This is likely mostly due to the apps or - at least in the case of etracer - SDL not using the RandR extension but older functionality for switching to/from fullscreen. See e.g. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450689
you know of any well behaving apps to test this? i tried glxgears -fullscreen, but this just expands the window to both heads and leaves the gnome-panel on top.
hmm .. i got etracer running ok with: SDL_VIDEO_X11_XRANDR=1 SDL_VIDEO_FULLSCREEN_HEAD=0 etracer but it crashes after exit (not restoring mode) the black screen was due to the 800x600 resolution not working (xrandr shows 60Hz, monitor got 30Hz, this also happens if i switch resolution with xrandr) i'm surprised console switching works that good. no matter how bad x was messed up (even a crashed opengl app, mouse hanging and all), fbcon was always working and setting the right mode.i had some bad experiences in the past with switching from x to console :)
Note: classic r600 driver has been abandoned. Please use r600g (gallium driver) instead. Is this still an issue with a newer driver/kernel?
The classic r600 driver has been abandoned long ago. It was replaced by the Gallium driver r600g. If you have issues with r600g please file a new bug report with component Drivers/Gallium/r600 Thanks.
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.