Dual-screen setup on a Mobility FireGL 7000M7

[Alex Deucher]

On Sun, Aug 3, 2008 at 2:00 PM, Ludwig Meyerhoff <ludwig at antar.de> wrote:
> Hallo!
>
> It actually turned the LVDS was disabled in the Monitor section (Option
> "Enable" "0").
>
> But what I originally wanted to do was to have one additional desktop on
> :0.1. I read support for this has been removed as it should get task of the
> WM?
>

:0.0 and :0.1 on a single adapter are what we call zaphod mode.  This
works on recent versions of the radeon driver (6.8.0 or newer).
However, there is no mechanism to choose what output get associated
with each "head."

Alex


>
>
> Saluti!
>
> Ludwig
>
> Alex Deucher wrote:
>>
>> On Sat, Aug 2, 2008 at 11:38 PM, Ludwig Meyerhoff <ludwig at antar.de> wrote:
>>>
>>> Hallo!
>>>
>>> I used to have a two-screen setup (0.0 and 0.1) with two device-sections
>>> respectively. Since I updated Xorg from 1.3.0 to 1.4.2 that setup does
>>> not work any more.
>>>
>>> When I plug in the external TFT to VGA-0, the radeon-driver seems to get
>>> confused and "forgets" about the other connectors (in special, LVDS).
>>> xrandr tells me there exists only VGA-0, if the server was not running
>>> before the plugin.
>>> If the server was already running when I plug in VGA-0, xrandr detects
>>> the new monitor and the supported modes correctly.
>>>
>>> A look in the Xorg.0.log shows the driver detects the LVDS-panel
>>> correctly, but then the first instance of the driver "RADEON(0)" says
>>> DVI-0 is connected, while the second instance "RADEON(1)" says VGA-0 is.
>>>
>>>
>>> In single-screen setup Port0 is VGA, Port1 DVI-D, Port2 LVDS and Port3
>>> STV.
>>>
>>> Is there a way to tell the driver instance explicitally what connector
>>> to use?
>>
>> Unfortunately, there is no option at this time to do what you are
>> asking for.  If you want full control of all of your outputs, you'll
>> have to use xrandr rather than zaphod.
>>
>> Alex
>