If the external monitor is unplugged during startup, but activated later on, the settings for the specified monitor found in xorg.conf should be applied with hindsight. xrandr --output DVI-D_1 --on should suffice to activate the external monitor like configured in xorg.conf. by now: xrandr --output DVI-D_1 --right-of PANEL :does nothing and: xrandr --output DVI-D_1 --right-of PANEL --mode 1920x1200 :does not apply the settings found in xorg.conf. In our case this means the following to DVI-D_1: * the screen resolution is not used at the outset but must be specified * it does not become the primary monitor as specified by RROutputOrder option. * a wrong display size is assumed (--fbmm, DisplaySize-option) Perhaps it will even be possible to automatically activate an external monitor on a specific hotplug event.
Created attachment 20400 [details] xorg log xrandr --output DVI-D_1 --right-of PANEL xrandr --output DVI-D_1 --right-of PANEL --mode 1920x1200
Created attachment 20401 [details] xorg.conf
xrandr --output DVI-D_1 --right-of PANEL --mode 1920x1200 now will make DVI-D_1 become the primary monitor as specified by RROutputOrder in xorg.conf. However with xorg-x11-driver-video-radeonhd-1.2.3_081126_8edc0c6-5.3 DVI-D_1 is now not activated by default on startup as it should be whenever the monitor is already plugged. Will there now be any further effort to unleash something like in the direction of 'xrandr --output DVI-D_1 --on'?
very annoying and still not resolved. If I forget to switch my external monitor on before booting (or if it is left in standby mode: requires switching current on & off) I will have to restart the X-server. Besides this, even worse I often wanna boot my laptop without having access to the external monitor. If I wanna connect my laptop to the external monitor later on I will have to quit all programs to restart the X-server. Please resolve this!! It should not be too hard to do? ... or do you have another opinion about the desireable standard behaviour?
Looks like this is just a bug in the radeonhd driver -- the startup configuration shouldn't restrict what you can do afterwards.
Does this issue occur with the preferred ati driver (xf86-vide-ati)? If so, please move this to the Driver/Radeon component. Development of radeonhd has pretty much halted and development focus is on the ati driver. Please see http://www.x.org/wiki/radeonhd If the issue does not exist in the ati driver (or if there is no response to this message), this bug will be closed as WONTFIX unless someone contributes a patch.
Closing due to lack of response. Please reopen and move to the Driver/Radeon component if this issue persists with xf86-video-ati
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.