Bug 433876 - switching to "both" mode with alt-f7 on t60w results in both screens blank
Summary: switching to "both" mode with alt-f7 on t60w results in both screens blank
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xorg-x11-drv-i810
Version: 5.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Adam Jackson
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 436140
TreeView+ depends on / blocked
 
Reported: 2008-02-21 21:58 UTC by Cameron Meadors
Modified: 2008-03-27 15:13 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-03-27 15:13:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Xorg log (50.58 KB, text/plain)
2008-03-11 18:59 UTC, Cameron Meadors
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2008:0420 0 normal SHIPPED_LIVE xorg-x11-drv-i810 enhancement update 2008-05-19 22:35:38 UTC

Description Cameron Meadors 2008-02-21 21:58:57 UTC
Description of problem:
When I cycle through the video display options with alt-f7 on a t60w, the
primary display works alone, external display works alone, but both are blank if
both are enabled.

Version-Release number of selected component (if applicable):
xorg-x11-drv-i810-1.6.5-9.6.0.3.el5
xorg-x11-server-Xorg-1.1.1-48.36.el5

How reproducible:
every time

Steps to Reproduce:
1. plug in an external monitor
2. hit alt-f7 twice
3.
  
Actual results:
both displays are blank

Expected results:
both displays light up

Additional info:

Comment 1 Matěj Cepl 2008-02-22 11:29:24 UTC
information about the system are NEEDINFOed in bug 433875

Comment 2 Cameron Meadors 2008-02-22 15:01:42 UTC
See attachment in bug 433875

Comment 3 RHEL Program Management 2008-02-25 15:07:21 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 4 Adam Jackson 2008-03-05 22:34:45 UTC
Again, you're testing with the i810 driver.  This functionality is not expected
to work with the i810 driver.  Are you sure you're testing what you mean to be
testing?

Comment 5 Cameron Meadors 2008-03-10 12:47:33 UTC
I will retest with intel driver.

Comment 6 Cameron Meadors 2008-03-11 18:58:54 UTC
With intel driver, I now get the wrong resolution on both screens (1680x1680
according to xrandr).  It does not cycle through the states but just turns on
the external display and primary display with the wrong resolution.

When trying to get back to a good resolution, I unplugged the external display
and hit fn-f7 again with not effect.  I then switched to vc1 and back to vc7
(where X was) and X crashed.  I will attach the log.

Comment 7 Cameron Meadors 2008-03-11 18:59:21 UTC
Created attachment 297660 [details]
Xorg log

Comment 8 RHEL Program Management 2008-03-11 19:36:02 UTC
This request was previously evaluated by Red Hat Product Management
for inclusion in the current Red Hat Enterprise Linux release, but
Red Hat was unable to resolve it in time.  This request will be
reviewed for a future Red Hat Enterprise Linux release.

Comment 12 Cameron Meadors 2008-03-27 15:13:02 UTC
Apparently the expected results when hitting Fn+F7 has changed.  From what was
explained to me by an X developer, Fn+F7 does not cycle through the displays. 
Now it triggers X to rescan the display ports.  Then X configures the resolution
for the larger of the two displays.  Thus resulting in the display with the
smaller max resolution to only show part of the desktop.

This resolves all issues in this bug except for the crash.  I will file a
different bug for that when I see it again. 


Note You need to log in before you can comment on or make changes to this bug.