Too high refresh rate on i810

Bug #47309 reported by Matthew Lange
14
Affects Status Importance Assigned to Milestone
xserver-xorg-video-i810 (Ubuntu)
Invalid
Medium
Ubuntu-X

Bug Description

After long struggle with my Compaq EVO D510 and buggy GRUB loader finally got Dapper running with LILO just to run in to another problem. Whatever I do with XORG config I can’t get it to initialize i810 driver to a lower refresh rate than 85 Hz. Normally it shouldn’t be a problem but my monitor can’t run higher than 75 Hz. Can anyone hlp me with this one please?

Revision history for this message
Matthew Lange (matthewlange) wrote :

Created bug report for tepaks from Ubuntu Ticket #958 https://launchpad.net/distros/ubuntu/+ticket/958/

Revision history for this message
tepaks (nimda-quicknet) wrote :

Manually adding “Modeline” entry to monitor section partially solves the problem but involves a lot of guess work and try end error approach. Not advisable method to users who are unfamiliar with terminal console. As a IT professional but a newbie to Linux I spend whole evening to figure it out. Still this bug points to a driver problem because graphics acceleration doesn’t work to. Searching the web I found a lot similar stories but no solution. Can anyone confirm this and/or point out any solution for this bug?

Revision history for this message
Paul Sladen (sladen) wrote :

The likely cause is the monitoring providing false information (the monitor is asked what its capabilities and limitations are). To override this, edit:

  /etc/X11/xorg.conf

and find the Monitor section that begins with:

  Section "Monitor"

then add a line that says:

  VertRefresh 74-76

The above is a workaround for you; If possible and to allow us to find the cause, please attach you:

  /var/log/Xorg.0.log

and the results from:

  sudo ddcprobe

Revision history for this message
tepaks (nimda-quicknet) wrote :
Download full text (100.3 KiB)

Thanks for your reply!

The VertRefresh 74-76 line doesn't work, looks like xserver ignores it. Strange enough same pc and same monitor can produce 1024x768@85 under XP?!? output from ddc probe looks ok to me and original xorg.comfig to but i still get a blank screen at 1024x768@85. Right now xorg.conf is:
Section "Monitor"
 Identifier "F715"
 Option "DPMS"
 HorizSync 30-68
 VertRefresh 50-75
 Modeline "1024x768@75" 85.52 1024 1056 1376 1408 768 782 792 807
EndSection

But my monitor's on-screen display reports FH 63.7 k HzFV 79.3 Hz
Comfusing isn't it?
---------------------------------------------------------------------------
/var/log/Xorg.0.log
---------------------------------------------------------------------------
X Window System Version 7.0.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 7.0
Build Operating System:Linux 2.6.12 i686
Current Operating System: Linux D510UBUNTU 2.6.15-23-386 #1 PREEMPT Tue May 23 13:49:40 UTC 2006 i686
Build Date: 16 March 2006
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Jun 1 18:56:24 2006
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "F715"
(**) | |-->Device "Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device"
(**) |-->Input Device "Generic Keyboard"
(**) |-->Input Device "Configured Mouse"
(**) |-->Input Device "stylus"
(**) |-->Input Device "cursor"
(**) |-->Input Device "eraser"
(WW) The directory "/usr/share/X11/fonts/cyrillic" does not exist.
 Entry deleted from font path.
(**) FontPath set to "/usr/share/X11/fonts/misc,/usr/share/X11/fonts/100dpi/:unscaled,/usr/share/X11/fonts/75dpi/:unscaled,/usr/share/X11/fonts/Type1,/usr/share/X11/fonts/100dpi,/usr/share/X11/fonts/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
(==) RgbPath set to "/etc/X11/rgb"
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Module ABI versions:
 X.Org ANSI C Emulation: 0.2
 X.Org Video Driver: 0.8
 X.Org XInput driver : 0.5
 X.Org Server Extension : 0.2
 X.Org Font Renderer : 0.4
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so
(II) Module bitmap: vendor="X.Org Foundation"
 compiled for 7.0.0, module version = 1.0.0
 Module class: X.Org Font Renderer
 ABI class: X.Org Font Renderer, version 0.4
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules/libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
 compiled for 7.0.0, module version = 1.0.0
 ABI class: X.Org Video Driver, version 0.8
(++) using VT number 7

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,2560 card 103c,1298 rev 01 class 06,00,00 hdr 00
(II) PCI: 00:02:0: chip 8086,2562 card 103c,1298 rev 01 class 03...

Revision history for this message
Conn O Griofa (psyke83) wrote :

I addition to Paul's suggestion, add to Section "Monitor":

Option "DDC" "false"

That may allow the driver to use the VertRefresh setting you specify; it's the only workaround that works on my system (not a laptop).

Revision history for this message
unggnu (unggnu) wrote :

Could you please recheck it with Gutsy Final Live CD? In Gutsy i810 driver is deprecated and intel driver is used instead.

Changed in xserver-xorg-video-i810:
status: New → Incomplete
Revision history for this message
unggnu (unggnu) wrote :

I am closing this bug report since this issue should be fixed in Ubuntu Gutsy Gibbon 7.10 and there is no response for more than two months.
Feel free to open it again if it still happens in Gutsy with the -intel driver.

Changed in xserver-xorg-video-i810:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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