Red Hat Bugzilla – Bug 485898
KMS:M56GL:Mobility FireGL V5200 DVI screen remains blank when enabled with xrandr
Last modified: 2010-06-28 07:18:14 EDT
Created attachment 332208 [details]
xorg log file
Description of problem:
DVI screen remains blank when enabled with xrandr
ATI FireGL V5200
xorg.conf set for a virtual 3200x1200 screen & using radeon driver with EXA
Also occurs with no xorg.conf
WHen system boots it typically has only the internal LCD connected.
When the laptop is docked it acquires an additional DVI connected screen
Both are 1600x1200
a few days ago this was working but appears to have stopped with recent X/kernel/driver updates
These commands are normally used to enable the second screen
xrandr --output LVDS --left-of DVI-0 --mode 1600x1200
xrandr -q is now reporting
[jonesn@snowdon ~]$ xrandr -q
Screen 0: minimum 320 x 200, current 3200 x 1200, maximum 3200 x 1600
VGA-0 disconnected (normal left inverted right x axis y axis)
LVDS connected 1600x1200+0+0 (normal left inverted right x axis y axis) 304mm x 228mm
1600x1200 60.0*+ 60.0 50.0
DVI-0 connected 1600x1200+1600+0 (normal left inverted right x axis y axis) 518mm x 324mm
1280x1024 70.0 60.0
1024x768 85.0 75.0 60.0
800x600 85.1 75.0 60.3
640x480 85.0 75.0 59.9
[jonesn@snowdon ~]$ xdpyinfo | grep dimensions
dimensions: 3200x1200 pixels (608x228 millimeters)
Yet the DVI screen remains blank. It is active as the power led is lit and crucially the mouse pointer can be seen on it. However if any windows are dragged over, the portion on the DVI screen remains black-on-black and not visible.
No kernel messages in dmesg when xrandr used
Some kind of palette/reset issue perhaps?
Version-Release number of selected component (if applicable):
every time with current sw levels
Occurs with or without an xorg.conf
Steps to Reproduce:
second screen not usable
second screen works ok
still occuring with current rawhide updates upto/including 2.6.29-0.137.rc5.git4.fc11.i686.PAE
However noticed that if I run the script above to enable screen #2. then suspend/resume, the second screen then works correctly.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command
yum upgrade --enablerepo='*-updates-testing'
Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .
Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.
If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
This problem no longer occurs with F12 gold and may be closed. Thanks.
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora Bugzappers volunteer triage team
[This triage is part of collective effort done by students of University of
Rijeka Department of Informatics.]
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.