Bug 6586 - External screen dark when not using MergedFB
Summary: External screen dark when not using MergedFB
Status: RESOLVED DUPLICATE of bug 5447
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.0.0
Hardware: PowerPC Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-13 17:33 UTC by nix
Modified: 2006-04-13 00:54 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xorg.conf file corresponding to scenarios described. (4.25 KB, text/plain)
2006-04-13 17:35 UTC, nix
no flags Details

Description nix 2006-04-13 17:33:27 UTC
Hi! I have an iBook G4 with a radeon card. I have gotten the external monitor to
work using MergedFB, which gives me a Xinerama display spanning my internal LCD
and my external monitor.

I would like to get two separate desktops instead of one. Unfortunately, if I
turn off MergedFB (either by commenting it out, or setting it to "False"), when
I start X, my external monitor goes dark, and only my LCD displays the root window.

Here's what I'm trying wrt. the attached xorg.conf file:

Scenario 1:
- Set
  Option "MergedFB" "True"
- Run X -layout Plain
Effect: It works great, but /with/ Xinerama

Scenario 2:
- Set
  Option "MergedFB" "False"
- Run X -layout Separate
Effect: External monitor goes dark, and doesn't turn on

http://ozlabs.org/~jk/docs/mergefb/ mentions a radeontool hack that will let you
turn on the external DVI by setting register FP_GEN_CNTL. I would have tried the
hacked-up radeontool, but my card differs from the one documented there, and I'm
reluctant to play around with the card's registers.

How can I get two separate desktops with the "radeon" driver ?
Comment 1 nix 2006-04-13 17:35:47 UTC
Created attachment 5291 [details]
xorg.conf file corresponding to scenarios described.
Comment 2 Michel Dänzer 2006-04-13 17:54:55 UTC

*** This bug has been marked as a duplicate of 5447 ***


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.