Bug 588095 - most modes not used because default hsync/vrefresh range is too small
Summary: most modes not used because default hsync/vrefresh range is too small
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-vmware
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-02 16:29 UTC by Sascha Silbe
Modified: 2011-06-27 16:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-06-27 16:02:19 UTC
Type: ---

Attachments (Terms of Use)

Description Sascha Silbe 2010-05-02 16:29:33 UTC
Description of problem:
When using the "vmware" graphics card "emulation" in KVM, the Xorg server in Fedora 13 uses a resolution of just 800x600 (whereas the X server on the host is running at 2048x1152) because most modes are rejected with either "vrefresh out of range" or "bad mode clock/interlace/doublescan". This is caused by using the default hsync and vrefresh ranges of 31.5-37.9 kHz resp. 50-70 Hz.
Explicitly configuring the hsync / vrefresh ranges in xorg.conf works around the issue.
xorg-x11-drv-vmware should probably report a fake connected monitor with wide hsync / vrefresh ranges.

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

How reproducible:

Steps to Reproduce:
1. kvm -vga vmware -hda ...
2. (inside kvm) startx
Actual results:
Screen is upscaled and blurry because of low resolution in guest. Also screen updates take several seconds (!).

Expected results:
Sharp image, almost instant screen updates by running at a resolution matching the KVM window size.

Additional info:

Comment 1 Bug Zapper 2011-06-02 14:35:57 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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: 

Comment 2 Bug Zapper 2011-06-27 16:02:19 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

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