Hello, I have an nc6000 HP laptop with Radeon card, as well as a docking station with DVI port, with a flat screen attached to it. Before upgrading to xorg from xfree86 (i.e. Debian Sarge to Etch), I was able to have one configuration and the xserver would do the right thing: - laptop standalone: 1024x768 on the internal display. - laptop in docking station: 1280x1024 on external screen. (I'm *not* trying to have something fancy like dual screen!) Now, I need to have two configurations: the old one (xorg.conf_NoLayout) when undocked, and a new one with MonitorLayout set to TMDS (xorg.conf_TMDSLayout) when docked. It of course makes me the laugh of all my (Windows) colleagues. And if I use the wrong configuration file, I get the following behavior: - laptop standalone: internal display shows completely garbled picture, looks like wrong sync parameters; I suspect trying to represent 1280x1024 on a display with 1024x768. - laptop docked: the external screen doesn't show anything. I suspect it's running on the internal screen. In both cases, the xserver doesn't notice anything strange and runs happily. I would really like to be able to run with only one configuration, without need to switch anything manually. Thanks, Eric
Created attachment 5593 [details] The original xorg.conf (without MonitorLayout)
Created attachment 5594 [details] The xorg.conf with MonitorLayout set to TMDS
Created attachment 5595 [details] Working config without Layout and Laptop being standalone
Created attachment 5596 [details] Working config with TMDS Layout and Laptop being docked
Created attachment 5597 [details] Non-working config without Layout but Laptop being docked
I'd say it smells a lot like the known issues of laptops & primary TMDS. One thing you can try to make your windows friends a bit more silent until those issues are solved is the kind of hacks (hooked to a hotkey) that is described on http://ozlabs.org/~jk/docs/mergefb/
*** This bug has been marked as a duplicate of 3621 ***
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.