Red Hat Bugzilla – Bug 433876
switching to "both" mode with alt-f7 on t60w results in both screens blank
Last modified: 2008-03-27 11:13:02 EDT
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):
Steps to Reproduce:
1. plug in an external monitor
2. hit alt-f7 twice
both displays are blank
both displays light up
information about the system are NEEDINFOed in bug 433875
See attachment in bug 433875
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
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
I will retest with intel driver.
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.
Created attachment 297660 [details]
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.
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.