missing 100 hz refresh rate in the "Screen Resolution Preferences"

Bug #16429 reported by Martin Bajer on 2005-04-25
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)

Bug Description

100hz refresh rate is missing for 1024x768 and higher modes in x.org
build-in modes. (Ubuntu 5.04)

 TCO'99 recommends 100Hz vertical refresh rate for CRT monitors.

Matt Zimmerman (mdz) wrote :

You have both already raised this issue in other bugs; combining this report
with those.

This bug has been marked as a duplicate of bug 12829.

Mantas Kriaučiūnas (mantas) wrote :

I don't think, that this bug is a duplicate of bug 12829. This bug is about
missing 100Hz modes in X.org build-in modes, but not about selecting default
resolution. At least Package is different for this and 6470 bug.

Mantas Kriaučiūnas (mantas) wrote :

This bug isn't duplicate of bug #12829 (was 6470 in bugzilla) - several users already told me, that Windows and some Linux distributions (e.g. older Mepis versions) are better than Ubuntu, because users can choose 100 Hz refresh in Monitors resolution configuration.

Mantas Kriaučiūnas (mantas) wrote :

Btw, isn't this bug an upstream bug ? Are 100hz modes included in upstream's x.org build-in modes ?

Albrecht Mühlenschulte (a7p) wrote :

No activity for almost a year, I consider this fixed. If this is not the case, please feel free to reopen.

Changed in xorg:
status: Unconfirmed → Rejected
Mantas Kriaučiūnas (mantas) wrote :

This bug still exists in Ubuntu Gutsy - there are no way to set 100Hz refresh rate nor in gnome-display-properties, nor in displayconfig-gtk

Changed in xorg:
status: Invalid → New
Bryce Harrington (bryce) wrote :

Could you please test if this is still occurring for Gutsy-final? It's possible this may have been due to a bug in xresprobe that was fixed in Gutsy.

If not, are you able to see any other refresh rates beyond 60Hz? If not then this would be a dupe of 27508.

If you are able to see other refresh rates, but 100Hz still is not showing up, please attach your /var/log/Xorg.0.log and the output of `xrandr` and `sudo ddcprobe`.

Changed in xorg:
status: New → Incomplete
Timo Aaltonen (tjaalton) wrote :

No reply from the submitter, closing the bug.

Changed in xorg:
status: Incomplete → Invalid
Mantas Kriaučiūnas (mantas) wrote :

100 Hz refresh rate is still missing in Hardy's and Gutsy's System->Preferences->Screen Resolution
I can attach output of ddcprobe and other command's if you need, just tell me what I need to do.
AFAIK X in Hardy doesn't use ddcprobe/xresprobe in Ubuntu Hardy, right ?

Changed in xorg:
status: Invalid → New
John S. Gruber (jsjgruber) wrote :

I'm just a bystander and I don't know the answer to your question about ddcprobe/xresprobe. On my system, under X, a ddc module acquires information through the video display adapter from the monitor and uses frequency, size, and mode information to select available modes.

I'm assuming you are asking about the mechanics of gather information. If you would like to gather the information Bryce Harrington asked for you can do the following:

If you have a default installation, like I do, you would first use the Synaptic Package Manager to install xresprobe.

Then use the applications menu and select accessories and terminal.

Then in that window enter:

sudo ddcprobe >ddcprobe.out

[You will have to respond with your password]

Then enter:

xrandr >xrandr.out

Then come back to thread and start a new comment. On the attachment section below the comment window you can
browse to the two files above and attach them, one per comment. Then open one more comment and in the attach
window browse to the file /var/log/Xorg.0.log and attach it.

What kind of monitor and display adapter are you using?

Bryce Harrington (bryce) on 2008-05-20
Changed in xorg:
status: New → Incomplete
Mantas Kriaučiūnas (mantas) wrote :

Bryce Harrington wrote:
> If you are able to see other refresh rates, but 100Hz still is not showing up, please attach your /var/log/Xorg.0.log and the output of `xrandr` and `sudo ddcprobe`

Yes, I'm able to see all refresh rates except 100 Hz, so, I'm attaching file and output of xrandr and ddcprobe.

John S. Gruber wrote:
>What kind of monitor and display adapter are you using?

My monitor is 17 inch Samsung SyncMaster 757NF (high quality monitor - horizontal sync: 30-96 kHz, vertical refresh: 50-160 Hz, recommended resolutions by TCO 99 are 1024x768@100Hz or 1152x864@100Hz), display adapter is Radeon 9200 (RV280).
I've tested on several different monitors/display adapters (including NVIDIA and Intel) - 100Hz modes are missing in all Ubuntu versions :(

Mantas Kriaučiūnas (mantas) wrote :

Another bug, possibly related to this issue, is 1152x864 mode - in this mode Ubuntu Hardy has only one refresh rate: 75Hz, all other refresh rates - 60 Hz, 85 Hz and 100 Hz are missing :(
Windows 98/2000/XP allows to choose from all refresh rates, including 100 Hz on this computer.
Maybe this is an upstream bug?

John S. Gruber (jsjgruber) wrote :

File of EDID data produced from Xorg.0.log file above.

John S. Gruber (jsjgruber) wrote :

Mantas Kriaučiūnas:

Would you mind attaching the /etc/X11/xorg.conf file related to the above files?

John S. Gruber (jsjgruber) wrote :

This is output from parse-edid <EDID.data. It describes the mode xresprobe misidentified as a 104Hz refresh mode and agrees
with the Xorg.0.log and xrandr. This is the default mode selected by Samsung.

 # EDID version 1 revision 3
Section "Monitor"
 # Block type: 2:0 3:fd
 # Block type: 2:0 3:fc
 Identifier "SyncMaster"
 VendorName "SAM"
 ModelName "SyncMaster"
 # Block type: 2:0 3:fd
 HorizSync 30-96
 VertRefresh 50-160
 # Max dot clock (video bandwidth) 250 MHz
 # Block type: 2:0 3:fc
 # Block type: 2:0 3:ff
 # DPMS capabilities: Active off:yes Suspend:no Standby:no

 Mode "1024x768" # vfreq 84.997Hz, hfreq 68.677kHz
  DotClock 94.500000
  HTimings 1024 1072 1168 1376
  VTimings 768 769 772 808
  Flags "+HSync" "+VSync"
 # Block type: 2:0 3:fd
 # Block type: 2:0 3:fc
 # Block type: 2:0 3:ff

John S. Gruber (jsjgruber) wrote :

In private mail Mantas Kriaučiūnas declined to provide the xorg.conf file for his configuration.

John S. Gruber (jsjgruber) wrote :

I'm sorry. That was ddcprobe that incorrectly listed the above mode as 104HZ.

John S. Gruber (jsjgruber) wrote :

I'm not surprised that there is no 1152x864@60 mode. I don't see where that mode would come from.

There is a default mode for 1152x864@85 in the Ubuntu supplement to extramodes, however. I can't see in the log where defaultmodes are being considered. They are seen clearly with my nv driver. That's one reason I wanted to see the config file. If it is pristine, however, then it won't be at fault.

@Mantas Kriaučiūnas
Is your configuration the default one automatically installed by Hardy, without change? Was the 1152x864@85 mode available when you tried Nvidia and Intel?

Your monitor could ask, in the EDID, for a mode with a vertical refresh of >=100 Hz, but doesn't. There are no VESA established modes, as of the last document I could find, for modes >=100Hz. Therefore if any were to be included automatically they would have to come from a modeline in the extramodes source file in xorg-server. If the radeon driver isn't trying to use these default modes it won't be able to offer 1152x864@85 (or anything around or above 100Hz) unless the monitor requests the modes inclusion or a modeline is added to the configuration. Of course it could be silently trying and rejecting this mode because of some detail I'm not aware of.

I could easily be missing something here.

Please, don't add unneeded comments to launchpad BTS - if you need my
xorg.conf just tell this, attaching my xorg.conf will not change anything,
as my xorg.conf is identifical to other Ubuntu 8.04 systems - have you
noticed, that since Ubuntu 7.10 all monitor settings are detected
automatically (at least for plug-and-play DDC monitors)?

Problem is not in xorg.conf, but in default build-in modes, it seems
xorg has no built-in modes with 100Hz refresh rate :(

On Sat, Jun 07, 2008 at 07:47:24PM -0000, John S. Gruber wrote:
> In private mail Mantas Kriaučiūnas declined to provide the xorg.conf
> file for his configuration.

Labanaktis/Good luck,
Mantas Kriaučiūnas Jabber ID: <email address hidden> GPG ID: 43535BD5
Public organization "Open Source for Lithuania" - www.akl.lt

ram32 (osiris1987) wrote :

I have the same problem with my LG F720P and nVidia 8600GT. There is no ability to select >85 hz.

Bryce Harrington (bryce) on 2008-07-29
Changed in xorg:
status: Incomplete → Triaged
Bryce Harrington (bryce) wrote :

[This is an automatic notification.]

Hi Martin,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:


If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 16429

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 16429 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:


Changed in xorg-server (Ubuntu):
status: Triaged → Incomplete
tags: added: needs-retested-on-lucid-by-june

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in xorg-server (Ubuntu):
status: Incomplete → Invalid

Thank you for taking the time to report this bug and helping to make Ubuntu better. My apologies as I should not have marked this Invalid. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Maverick Meerkat. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

Changed in xorg-server (Ubuntu):
status: Invalid → Incomplete
Bryce Harrington (bryce) wrote :


Changed in xorg-server (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.