Bug#503664: xserver-xorg-core: Dual head with Radeon HD3200 - heads partly overlay each other

["Eneko Lacunza" <enlar@enlar.net>]

Hi,

Sorry for the delay, I've been busy with other things.

On Wed, Oct 29, 2008 at 7:18 AM, Brice Goglin <Brice.Goglin@ens-lyon.org> wrote:
>> I'm unable to make work an external monitor with experimental radeon
>> driver. I tried ModeLine + PreferredMode without luck. I tried the
>> following from the command line:
>> elacunza@elacunza:~$ xrandr --auto
>> xrandr: cannot find crtc for output VGA-0
>> elacunza@elacunza:~$ xrandr --output VGA-0 --mode "1440x900"
>> xrandr: cannot find crtc for output VGA-0
>> Monitor is conected, believe me! :)
> That's because the driver reports a "None" output (see the middle of
> xrandr output). "None" is probably using one CRTC, and LVDS the other
> one, so VGA cannot find an available CRTC (the board only has 2
> rendering pipelines). Try "xrandr --output None --off" first (or disable
> "None" in xorg.conf using the wiki page).

Tried "xrandr --output None --off"  but didn't make any difference.

>> Shall I test Virtual 3000 1600 with Xserver 1.4 as a last test?
> Might be good. But if you're bored with upgrading/downgrading 15
> packages, I'll understand :)

I've downgraded to latest 1.4.2 in testing. Setting virtual to
2720x900 works perfectly, so I'm staying with it :). BTW, seems that
Xserver 1.5 radeon driver is making fonts to appear a bit bigger.

>> - experimental radeon problems with external monitor
> See above. The problem is probably the "None" output. Maybe it's a
> modern output that the driver doesn't detect properly yet? HDMI?
> DisplayPort?



> You might want to open an upstream bug about this "None" output.
> http://bugzilla.freedesktop.org product Xorg component Driver/Radeon.
> Put your xorg.conf and log there, as well as the xrandr output. Don't
> bother talking about Xserver1.4 from testing/unstable, they won't care,
> only experimental matters here.
>
>
>> - experimental radeonhd not auto-adding to layout mouse and keyboard sections
>>
>
> I don't see how radeonhd could impact input device like this. You should
> send the corresponding log, and somebody might understand what's going
> on. Julien isn't available these days, so it might take some time...
>
> Brice
>
>