Bug 707766 - [Sandybridge] only the highest display resolution is available in 16:9 mode
Summary: [Sandybridge] only the highest display resolution is available in 16:9 mode
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: [cat:rendering]
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-25 21:01 UTC by tony
Modified: 2018-04-11 10:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 14:42:04 UTC
Type: ---


Attachments (Terms of Use)
dmesg standard output (122.91 KB, text/plain)
2011-05-27 21:50 UTC, tony
no flags Details
/var/log/messages (28.68 KB, text/x-log)
2011-05-27 21:53 UTC, tony
no flags Details
/var/log/Xorg.*.log (26.65 KB, text/plain)
2011-05-27 21:55 UTC, tony
no flags Details
/var/log/Xorg.*.log (28.68 KB, text/plain)
2011-05-27 21:56 UTC, tony
no flags Details
/var/log/messages (502.65 KB, text/plain)
2011-05-27 21:59 UTC, tony
no flags Details

Description tony 2011-05-25 21:01:56 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.  install Fedora 15 on laptop with sandybridge technology.  I'm using a thinkpad T520s ( sandybridge HD3000 intel core i5-2520M )

2. In Gnome 3, navigate to Applicatons, System tools, system settings, displays.

3. change resolution to lower setting then default.
  
Actual results:
when i applied the change to a lower resolution it failed to expand to full length of screen.

Expected results:
when i applied the change to a lower resolution it should expand to full length of screen



Additional info:
I trying to change it 1024x768.  

[barbaricht@ana ~]$ xrandr
Screen 0: minimum 320 x 200, current 1600 x 900, maximum 8192 x 8192
LVDS1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 310mm x 174mm
   1600x900       60.0*+
   1024x768       60.0  
   800x600        60.3     56.2  
   640x480        59.9  
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)

Comment 1 Matěj Cepl 2011-05-27 15:34:46 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 2 tony 2011-05-27 21:28:18 UTC
Dear Matej Cepl:

I will be sending the information you requested at 2011-05-27 11:34:46 EDT by tuesday May 31 2011.


Also, i want to update my bug description.  I noticed that only the highest resolution that my machine supports is available.  The highest resolution for my machine is:  1600x900 16:9

Thus, all the other modes with 16:9 are not being detected.   I know this because i installed windows 7 64BIT along with the video driver; and all these modes below were available! Therefore, the modes that are not detected with Fedora 15 at 16:9 are the following:

1440x900  16:9
1366x768  16:9
1360x768  16:9
1280x800  16:9
1280x768  16:9
1280x720  16:9
1024x768  16:9
960x600   16:9
800x600   16:9

In Fedora 15, only 1600x900 shows up with 16:9 mode. The other three modes below are using 4:3

1024x768        
800x600          
640x480

Comment 3 tony 2011-05-27 21:50:36 UTC
Created attachment 501411 [details]
dmesg standard output

Comment 4 tony 2011-05-27 21:53:19 UTC
Created attachment 501412 [details]
/var/log/messages

Comment 5 tony 2011-05-27 21:55:07 UTC
Created attachment 501413 [details]
/var/log/Xorg.*.log

Comment 6 tony 2011-05-27 21:56:53 UTC
Created attachment 501414 [details]
/var/log/Xorg.*.log

Comment 7 tony 2011-05-27 21:59:39 UTC
Created attachment 501415 [details]
/var/log/messages

Comment 8 Fedora End Of Life 2012-08-07 14:42:08 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

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:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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