If I enable MergedFB support for my Radeon 9000 but do not connect an extra monitor when X starts up, the X server still seems to report that I have 2 heads connected, which confuses certain programs like XScreensaver and Firefox, which start up taking only part of the screen. For example, here is the output of the text-xinerama program included in the xscreensaver source: test-xinerama: 11:50:30: XineramaQueryExtension(dpy, ...) ==> 0, 0 test-xinerama: 11:50:30: XineramaIsActive(dpy) ==> True test-xinerama: 11:50:30: XineramaQueryVersion(dpy, ...) ==> 1, 1 test-xinerama: 11:50:30: 2 Xinerama screens test-xinerama: 11:50:30: screen 0: 1400x1050+0+0 test-xinerama: 11:50:30: screen 1: 640x1050+760+0
can you attach your full log and config?
Created attachment 2021 [details] Log when running with MergedFB enabled and no extra head connected
Created attachment 2022 [details] X configuration with MergedFB enabled
It's reproting two heads because you have forced mergedfb on (Option "MergedFB" "true"). This option forces mergedfb on even if the driver does not detect two head connected. if you want the driver to attempt to come up in single vs. dualhead based on what's attached, remove that line. The xinerama weirdness comes from the fact that there is no DDC information for your second head so it defaults to 640x480.
Ah, so it does. The man page for radeon under the MergedFB option doesn't really say that it _forces_ xinerama on, only that it turns MergedFB on.
(In reply to comment #5) > Ah, so it does. The man page for radeon under the MergedFB option doesn't really > say that it _forces_ xinerama on, only that it turns MergedFB on. Well, it doesn't exactly force xinerama on, rather it forces both heads on. xinerama is just a byproduct. Still you are right, I should clarify the man page. I'll fix that up soon.
I apologize that I have to re-open this bug. Due to a bios issue of my notebook, I am forced to use the option "MergedFB true" otherwise the external screen will only work in clone modus which is not what I am looking for. The main issue concerns the dialog which asks for a password after standby or screensaver etc. This "re-login window" is not displayed if the framebuffer's size matches the size of the internal display. Example: The internal display supports 1280x800 pixels, the external 640x480. The resolution for the framebuffer is set with xrandr during startup of xorg within some script. This way no window is placed beyond the 1280 pixel border if no second display is attached. After setting the framebuffer size to 1280x800 there is NO login screen display when using lock screen etc. If I set the framebuffers size to anything else, e.g. 1920x800, the dialog is displayed correctly. Only if the framebuffer size (set with xrandr) corresponds to the actual size of the screen, the login dialog will not be displayed. As this works with any other resolution, I suppose the bug comes from MergedFB and not from the login screen of the xscreensaver.
Peter, this is a different issue. Please open a different bug report. Thank you.
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.