Hide Forgot
Description of problem: I am using Thinkpad T410 for dual screen extend setup with repo: RHEL6.2-20111005.1 . After power on, the external moditor got black screen but xrandr show it have already set it up with correct resolution. Screen only goes back if unplug and plug again the VGA cable or these commands: ==== if [ $? -eq 0 ]; then xrandr --output VGA1 --off xrandr --output VGA1 --auto xrandr --output LVDS1 --auto --left-of VGA1 ==== Version-Release number of selected component (if applicable): RHEL6.2-20111005.1 kernel-2.6.32-206.el6.x86_64 xorg-x11-xauth-1.0.2-7.1.el6.x86_64 xorg-x11-server-Xorg-1.10.4-3.el6.x86_64 xorg-x11-drv-intel-2.16.0-1.el6.x86_64 xorg-x11-utils-7.4-8.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Connect a external screen via VGA of T410 2. Power on Actual results: external monitor got no display Expected results: external monitor got correctly display Additional info: If screen is online, reboot OS will not got any problem. I try with and without xorg.conf, they are the same issue. Here is the xorg.conf ========== Section "Monitor" Identifier "laptop" EndSection Section "Monitor" Identifier "VGA" Option "PreferredMode" "1680x1050" VertRefresh 60 Option "RightOf" "laptop" # Option "Ignore" "true" EndSection Section "Device" Identifier "Intel Core 5" Driver "intel" BusID "PCI:0:2:0" Option "monitor-VGA1" "VGA" Option "monitor-LVDS1" "laptop" EndSection Section "Screen" Identifier "Screen0" Device "Intel Core 5" Monitor "laptop" DefaultDepth 24 SubSection "Display" Depth 24 EndSubSection EndSection ==========
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
It's my mistake. The running kernel is still 131. After switch to kernel 205, problem gone. CLOSE this bug.