[Bug 23421] dualhead - 2. monitor off (not just blank / black) on radeon; xrandr

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Sep 3 01:02:53 PDT 2009


http://bugs.freedesktop.org/show_bug.cgi?id=23421





--- Comment #15 from kapetr <kapetr at mizera.cz>  2009-09-03 01:02:52 PST ---
(In reply to comment #14)
> 
> With the --addmode ...
> 
> I will try it and report...
> See also my last comment - I'm little afraid of make the test ?:-(
> 

I have try it.

IT REALLY WORKS.  GREAT.  Thank You very much !

Interesting is:

1. after reboot from (working) U9.04 in Fedora 11 with "nomodeset" - first time
ever: both monitors were ON - probably from HW setting from Ubuntu ?!
2. with "nomodeset" - the 2. monitor was switched off like usual. But with
Yours xrandr --addmode ...   it comes up :-)  The dualhead is now working.

?? Also after --admode and switching On, xrander reports this output like
disconnected:
<code>
[liveuser at localhost ~]$ xrandr
Screen 0: minimum 320 x 200, current 2048 x 768, maximum 4096 x 4096
VGA-0 connected 1024x768+1024+0 (normal left inverted right x axis y axis)
300mm x 230mm
   1024x768       75.1*    60.0  
   832x624        74.6  
   800x600        75.0     60.3  
   640x480        75.0     60.0  
   720x400        70.1  
   0x0             0.0  
VGA-1 disconnected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm
x 0mm
   1024x768       75.1* 
[liveuser at localhost ~]$ 
</code>

3. After switching to "text" console and back, the monitor goes OFF again. To
switch it ON is necessary to first switch it off with xrand:

- xrandr --output VGA-1 --off       and only then --output VGA-1 --mode
1024x768

4. The names of outputs are contrariwise ?!



I hope, that this behaviour (especially switching off) will be changed.

Once again - thank You.


P.S. 
- How to set mode (resolution, ...) 
- and dualhead on startup ? 
- With kernel mode setting ?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the xorg-driver-ati mailing list