I also tested zaphod with KMS and found that xrandr doesn't play nice with DISPLAY=:0.1. I have to log out and back in when I plug the TV.
First tests I made were on U64 karmic + 2.6.33 + xorg-edgers (few weeks ago). My HD3650 AGP (RV635) was able to drive a 1280x1024 LCD via DVI and a 1920x1080 TV via DVI->HDMI, but only if the TV was connected at boot, otherwise xrandr couldn't open display :0.1 like you.
At the time, I did the same tests and had the same results on my laptop with an X1270 (RS690) (or actually worse considering the annoying issue with the mouse cursor able to go to display :0.1 but not back to :0.0).
Then, after testing again with the laptop using today's packages (same results), I did an additional test: TV unplugged at boot -> auto-login (xrandr cannot open display :0.1) -> log out (TV starts displaying image) -> log in -> xrandr OK (lists supported modes) -> unplug TV -> xrandr KO? (see below) -> re-plug TV (image appears without having to use xrandr!)
HDMI-0 disconnected 1920x1080+0+0 (normal left inverted right x axis y axis) 708mm x 398mm
1920x1080 (0x7f) 148.5MHz
h: width 1920 start 2448 end 2492 total 2640 skew 0 clock 56.2KHz
v: height 1080 start 1084 end 1089 total 1125 clock 50.0Hz
So it seems xrandr cannot enable or disable a screen on display :0.1, even when setting DISPLAY variable correctly (or at least I haven't gound a way to do so). Only logging out allows configuration of screens as per xorg.conf.
In the meantime, I tested kde in lucid beta as I heard they are sorting out slowly their multi head support. I can hotplug fine any screen with a script and no xorg.conf. It's not zaphod mode, but IMHO virtual screen handling is a bit better than gnome: backgound image not stretched (and hence not corrupted beyond 2048), window maximizing ok, panel placement mostly ok, other single display benefits...
Hope this helps
PY
First tests I made were on U64 karmic + 2.6.33 + xorg-edgers (few weeks ago). My HD3650 AGP (RV635) was able to drive a 1280x1024 LCD via DVI and a 1920x1080 TV via DVI->HDMI, but only if the TV was connected at boot, otherwise xrandr couldn't open display :0.1 like you.
At the time, I did the same tests and had the same results on my laptop with an X1270 (RS690) (or actually worse considering the annoying issue with the mouse cursor able to go to display :0.1 but not back to :0.0).
Then, after testing again with the laptop using today's packages (same results), I did an additional test: TV unplugged at boot -> auto-login (xrandr cannot open display :0.1) -> log out (TV starts displaying image) -> log in -> xrandr OK (lists supported modes) -> unplug TV -> xrandr KO? (see below) -> re-plug TV (image appears without having to use xrandr!)
HDMI-0 disconnected 1920x1080+0+0 (normal left inverted right x axis y axis) 708mm x 398mm
1920x1080 (0x7f) 148.5MHz
h: width 1920 start 2448 end 2492 total 2640 skew 0 clock 56.2KHz
v: height 1080 start 1084 end 1089 total 1125 clock 50.0Hz
So it seems xrandr cannot enable or disable a screen on display :0.1, even when setting DISPLAY variable correctly (or at least I haven't gound a way to do so). Only logging out allows configuration of screens as per xorg.conf.
In the meantime, I tested kde in lucid beta as I heard they are sorting out slowly their multi head support. I can hotplug fine any screen with a script and no xorg.conf. It's not zaphod mode, but IMHO virtual screen handling is a bit better than gnome: backgound image not stretched (and hence not corrupted beyond 2048), window maximizing ok, panel placement mostly ok, other single display benefits...
Hope this helps
PY
Comment