Fedora Linux Support Community & Resources Center
  #1  
Old 22nd April 2009, 02:39 PM
jrevillug Offline
Registered User
 
Join Date: Apr 2009
Location: Bristol, UK
Posts: 12
[SOLVED] Refresh rate fixed at 60Hz, Fglrx + Ati 3200HD (780G) + RandR1.2 (F10)

Hi everyone,

Sorry for posting this, but I can't seem to find a solution anywhere.

I recently re-installed Fedora 10 on my desktop (when installing it previously I made the mistake of trying lots of different programs, and I just overloaded the system with junk...).

Then I ran a full system update, installed Presto for yum and followed Leigh's HowTo to install fglrx for the on-board graphics. During this I was stuck with the 1024x768 at 60Hz, since I was using the Vesa driver.

After a re-boot (for the akmod) I got a 1600x1200 desktop, but at a refresh rate of 60Hz. I can't change that setting.

The monitor (a Dell D1626HT 21" CRT) and graphics card will support at least 85Hz. Before re-installing Fedora, I was running Fedora 10 with fglrx and was able to run at a resolution of 1600x1200 at 85Hz.

My Kernel release:
Code:
2.6.27.21-170.2.56.fc10.x86_64
Here is my xorg.conf:

Code:
# Xorg configuration created by system-config-display

Section "ServerLayout"
	Identifier     "single head configuration"
	Screen      0  "Screen0" 0 0
EndSection

Section "Files"
	ModulePath   "/usr/lib64/xorg/modules/extensions/fglrx"
	ModulePath   "/usr/lib64/xorg/modules"
EndSection

Section "ServerFlags"
	Option	    "AIGLX" "on"
EndSection

Section "Monitor"
	Identifier   "Monitor0"
	ModelName    "Dell D1626HT"
	HorizSync    31.0 - 107.0
	VertRefresh  50.0 - 160.0
	Option	    "dpms"
EndSection

Section "Device"
	Identifier  "Videocard0"
	Driver      "fglrx"
	Option	    "OpenGLOverlay" "off"
	Option	    "VideoOverlay" "on"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Videocard0"
	Monitor    "Monitor0"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection

Section "Extensions"
	Option	    "Composite" "Enable"
EndSection
Here is the section of the /var/log/Xorg.0.log relating to setting up the display refresh rate and resolution:
Code:
***Display: ConnectedDisplayTypes=0x00000001, disabled=0x00000000
(II) fglrx(0): Connected Display1: CRT on primary DAC [crt1]
(II) fglrx(0):  Display1: No EDID information from DDC.
(EE) fglrx(0): Unknown EDID version 0
(II) fglrx(0):  Display1: Failed to get EDID information. 
(II) fglrx(0): Output DFP2 using monitor section Monitor0
(II) fglrx(0): Output CRT1 has no monitor section
(II) fglrx(0): EDID for output DFP2
(II) fglrx(0): EDID for output CRT1
(II) fglrx(0): Not using default mode "640x350" (vrefresh out of range)
(II) fglrx(0): Not using default mode "640x400" (vrefresh out of range)
(II) fglrx(0): Not using default mode "720x400" (vrefresh out of range)
(II) fglrx(0): Not using default mode "640x480" (unknown reason)
(II) fglrx(0): Not using default mode "640x480" (vrefresh out of range)
(II) fglrx(0): Not using default mode "640x480" (vrefresh out of range)
(II) fglrx(0): Not using default mode "640x480" (vrefresh out of range)
(II) fglrx(0): Not using default mode "800x600" (vrefresh out of range)
(II) fglrx(0): Not using default mode "800x600" (vrefresh out of range)
(II) fglrx(0): Not using default mode "800x600" (vrefresh out of range)
(II) fglrx(0): Not using default mode "1024x768" (vrefresh out of range)
(II) fglrx(0): Not using default mode "1024x768" (vrefresh out of range)
(II) fglrx(0): Not using default mode "1024x768" (vrefresh out of range)
(II) fglrx(0): Not using default mode "1152x864" (vrefresh out of range)
(II) fglrx(0): Not using default mode "1280x960" (vrefresh out of range)
(II) fglrx(0): Not using default mode "1280x1024" (vrefresh out of range)
(II) fglrx(0): Not using default mode "1280x1024" (vrefresh out of range)
(II) fglrx(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) fglrx(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) fglrx(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) fglrx(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) fglrx(0): Not using default mode "1792x1344" (hsync out of range)
(II) fglrx(0): Not using default mode "1792x1344" (vrefresh out of range)
(II) fglrx(0): Not using default mode "1856x1392" (hsync out of range)
(II) fglrx(0): Not using default mode "1856x1392" (vrefresh out of range)
(II) fglrx(0): Not using default mode "1920x1440" (hsync out of range)
(II) fglrx(0): Not using default mode "1920x1440" (vrefresh out of range)
(II) fglrx(0): Not using default mode "832x624" (vrefresh out of range)
(II) fglrx(0): Not using default mode "1400x1050" (unknown reason)
(II) fglrx(0): Not using default mode "1400x1050" (vrefresh out of range)
(II) fglrx(0): Not using default mode "1920x1440" (vrefresh out of range)
(II) fglrx(0): Not using default mode "2048x1536" (hsync out of range)
(II) fglrx(0): Not using default mode "2048x1536" (vrefresh out of range)
(II) fglrx(0): Not using default mode "2048x1536" (vrefresh out of range)
(II) fglrx(0): Printing probed modes for output CRT1
(II) fglrx(0): Modeline "1600x1200"x60.0  162.00  1600 1664 1856 2160  1200 1201 1204 1250 +hsync +vsync (75.0 kHz)
(II) fglrx(0): Modeline "1400x1050"x60.0  121.75  1400 1488 1632 1864  1050 1053 1057 1089 -hsync +vsync (65.3 kHz)
(II) fglrx(0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(II) fglrx(0): Modeline "1280x1024"x47.0   85.51  1280 1344 1480 1680  1024 1025 1028 1083 interlace -hsync +vsync (50.9 kHz)
(II) fglrx(0): Modeline "1280x1024"x43.0   77.80  1280 1344 1480 1680  1024 1025 1028 1077 interlace -hsync +vsync (46.3 kHz)
(II) fglrx(0): Modeline "1440x900"x60.0  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz)
(II) fglrx(0): Modeline "1280x960"x60.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz)
(II) fglrx(0): Modeline "1152x864"x60.0   81.62  1152 1216 1336 1520  864 865 868 895 -hsync +vsync (53.7 kHz)
(II) fglrx(0): Modeline "1152x864"x47.0   64.67  1152 1208 1328 1504  864 865 868 915 interlace -hsync +vsync (43.0 kHz)
(II) fglrx(0): Modeline "1152x864"x43.0   58.28  1152 1200 1320 1488  864 865 868 911 interlace -hsync +vsync (39.2 kHz)
(II) fglrx(0): Modeline "1280x768"x60.0   79.50  1280 1344 1472 1664  768 771 778 798 -hsync +vsync (47.8 kHz)
(II) fglrx(0): Modeline "1280x720"x60.0   74.48  1280 1336 1472 1664  720 721 724 746 -hsync +vsync (44.8 kHz)
(II) fglrx(0): Modeline "1280x720"x50.0   60.46  1280 1328 1456 1632  720 721 724 741 -hsync +vsync (37.0 kHz)
(II) fglrx(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
(II) fglrx(0): Modeline "1024x768"x43.0   44.90  1024 1032 1208 1264  768 768 772 817 interlace +hsync +vsync (35.5 kHz)
(II) fglrx(0): Modeline "800x600"x60.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(II) fglrx(0): Modeline "800x600"x56.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz)
(II) fglrx(0): Modeline "800x600"x47.0   29.60  800 816 896 992  600 601 604 635 interlace -hsync +vsync (29.8 kHz)
(II) fglrx(0): Modeline "720x480"x60.0   26.71  720 736 808 896  480 481 484 497 -hsync +vsync (29.8 kHz)
(II) fglrx(0): Modeline "640x480"x60.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
(II) fglrx(0): Modeline "640x400"x60.0   24.92  640 664 760 792  400 460 462 525 +hsync +vsync (31.5 kHz)
(II) fglrx(0): Modeline "512x384"x60.0   19.81  512 544 624 664  384 451 453 497 +hsync +vsync (29.8 kHz)
(II) fglrx(0): Modeline "400x300"x60.0   22.33  400 416 480 496  300 601 605 742 doublescan +hsync +vsync (45.0 kHz)
(II) fglrx(0): Modeline "320x240"x60.0   12.59  320 328 376 400  240 491 493 525 doublescan +hsync +vsync (31.5 kHz)
(II) fglrx(0): Modeline "320x200"x60.0   12.59  320 336 384 400  200 457 459 524 doublescan +hsync +vsync (31.5 kHz)
(II) fglrx(0): Output DFP2 disconnected
(II) fglrx(0): Output CRT1 connected
(II) fglrx(0): Using exact sizes for initial modes
(II) fglrx(0): Output CRT1 using initial mode 1600x1200
(==) fglrx(0): DPI set to (96, 96)
(==) fglrx(0): Using gamma correction (1.0, 1.0, 1.0)
(==) fglrx(0): QBS disabled
(==) fglrx(0): FAST_SWAP disabled
(==) fglrx(0):  PseudoColor visuals disabled
(II) Loading sub module "fb"
(II) LoadModule: "fb"
Here is Xrandr:
Code:
Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 3520 x 1600
DFP2 disconnected (normal left inverted right x axis y axis)
CRT1 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1600x1200      60.0*+
   1400x1050      60.0
   1280x1024      60.0     47.0     43.0
   1440x900       59.9
   1280x960       60.0
   1152x864       60.0     47.0     43.0
   1280x768       59.9
   1280x720       60.0     50.0
   1024x768       60.0     43.5
   800x600        60.3     56.2     47.0
   720x480        60.0
   640x480        60.0
   640x400        59.9
   512x384        60.0
   400x300        60.7
   320x240        60.0
   320x200        60.1
I can't see where I've gone wrong - the Xorg.conf 'VertRefresh' line doesn't seem to be recognised.

I've also tried enabling and disabling the atuo config in livna-display-config, the system-config-display gui (which created the current Xorg monitor section), adding 'nomodeset' to the kernel arguments and probably some other things. it doesn't seem to make any difference.

The really annoying thing is that I have had it working before (with an older kernel, I think). I had much the same problem, and seem to remember it being a fairly simple fix, but I can't find it or remember what it was.

My suspicion is that it's the modelines in xorg.conf that are the issue, but I don't know how to find or calculate the dotclock - the only documentation that I can find for my monitor is the basic info from Dell.

Any ideas would be gratefully received.

Many thanks,
James

Last edited by jrevillug; 25th April 2009 at 04:35 PM.
Reply With Quote
  #2  
Old 22nd April 2009, 04:11 PM
jrevillug Offline
Registered User
 
Join Date: Apr 2009
Location: Bristol, UK
Posts: 12
Smile

Posting reply because an edit takes me over the character limit.

I added a modeline to xorg.conf, and referenced it int he display subsection.

New xorg.conf:
Code:
Section "Monitor"
        Identifier   "Monitor0"
        ModelName    "Dell D1626HT"
        HorizSync    31.0 - 107.0
        VertRefresh  50.0 - 160.0
        Modeline "1600x1200_85.00"  234.76  1600 1720 1896 2192  1200 1201 1204 1260  -HSync +Vsync
        Option      "dpms"
EndSection

Section "Device"
        Identifier  "Videocard0"
        Driver      "fglrx"
        Option      "OpenGLOverlay" "off"
        Option      "VideoOverlay" "on"
EndSection

Section "Screen"
        Identifier "Screen0"
        Device     "Videocard0"
        Monitor    "Monitor0"
        DefaultDepth     24
        SubSection "Display"
                Viewport   0 0
                Depth     24
                Modes "1600x1200_85.00" "1600x1200"
        EndSubSection
This hasn't worked. It seems from the log as if Xorg isn't trying the new mode. It is almost as though Xorg isn't reading xorg.conf.

James

EDIT - I think I have found the problem.

Code:
(II) fglrx(0): Connected Display1: CRT on primary DAC [crt1]
(II) fglrx(0):  Display1: No EDID information from DDC.
(EE) fglrx(0): Unknown EDID version 0
(II) fglrx(0):  Display1: Failed to get EDID information.
(II) fglrx(0): Output DFP2 using monitor section Monitor0
(II) fglrx(0): Output CRT1 has no monitor section
(II) fglrx(0): EDID for output DFP2
(II) fglrx(0): EDID for output CRT1
My old CRT monitor is CRT1. I have nothing connected to DFP2 - which would be either my HDMI or DVI port. So the Xserver is trying to use my Monitor0 section for the digital screen, and relying on non-existant information from the monitor for the CRT.

Just need to fix it now. I'm going to try to trun the DVI port off in the bios.

Last edited by jrevillug; 23rd April 2009 at 05:00 PM.
Reply With Quote
  #3  
Old 24th April 2009, 04:48 PM
jrevillug Offline
Registered User
 
Join Date: Apr 2009
Location: Bristol, UK
Posts: 12
Right, well. I can't disable my DVI port in the BIOS.

So the driver/Xserver is applying my xorg.conf monitor section to a port that doesn't have a monitor connected.

At the same time, EDID doesn't report any specs of the connected analogue monitor to the driver.

As can be seen in my Xorg.0.log file, the driver recognises that there is no monitor connected to the DVI port, but only after applying my Xorg setting to it.

If you want to see any more of the Xorg.0.log file, just ask - I can't post the whole thing for obvious reasons (like it's 60,000 characters).

I tried changing the screen number in the ServerLayout section to 1 instead of 0, and it didn't work.

I suspect that I'm going to have to try to set it up my xorg.conf for dual head mode, with a fake screen, and hope that the driver is smart enough to allow that to work.

Can anyone else see a sensible way forward? I reached the limit of my knowledge of the software components a while ago, and have been extending it a little at a time.

James
Reply With Quote
  #4  
Old 24th April 2009, 08:24 PM
jrevillug Offline
Registered User
 
Join Date: Apr 2009
Location: Bristol, UK
Posts: 12
I'm not alone - there's a guy running Ubuntu that is having similar problems, and his Xorg.0.log has a similar list of errors - EDID not working, and the xorg.conf monitor section being applied to the wrong videocard output.

Here is a link.

James
Reply With Quote
  #5  
Old 24th April 2009, 08:41 PM
Hlingler Offline
Administrator
 
Join Date: Sep 2006
Location: Connellsville, PA, USA
Posts: 11,291
If you can get the EDID info for the monitor saved to a file, you can specify a custom EDID to use in xorg.conf - that's what I did, using NVidia driver's built-in config utility to save the EDID info to a file. I got one or two extra options that way. The EDID info is stored in a coded way, so you can't really create one using a text editor or such, as far as I know. Perhaps you can use M$ Win to get this file, or get it from the MFR??

If you can, save that file to, for example: /etc/X11/edid.bin
Then in xorg.conf:
Code:
[...]
Section "Device"
        Identifier  "Videocard0"
        Driver      "nvidia"
        VendorName  "NVIDIA Corporation"
        BoardName   "GeForce 6150 LE"
        Option      "CustomEDID" "CRT-0:/etc/X11/edid.bin"
        Option      "TripleBuffer" "True"
        Option      "Coolbits" "1"
        Option      "MultisampleCompatibility" "true"
        Option      "UseEvents" "true"
        Option      "BackingStore" "true"
        Option      "OnDemandVBlankInterrupts" "true"
EndSection
[...]
V
Reply With Quote
  #6  
Old 24th April 2009, 10:26 PM
jrevillug Offline
Registered User
 
Join Date: Apr 2009
Location: Bristol, UK
Posts: 12
Thanks for that hint, Hlingler. I'll see if I can find the EDID data.

James

EDIT - found the EDID, but I think the CustomEDID option is Nvidia only. I will try it tomorrow.

EDID for ref:
00,FF,FF,FF,FF,FF,FF,00,10,AC,5B,51,32,55,4E,30,16 ,09,01,01,0E,26,1D,96,E8,0D,C9,A0,57,47,98,27,12,4 8,4C,A5,4B,00,31,59,45,59,61,59,81,99,A9,4F,A9,59, 01,01,01,01,10,0B,D0,B4,20,5E,63,10,12,6C,62,08,84 ,23,11,00,00,1A,00,00,00,FF,00,35,35,33,34,38,42,3 0,4E,55,32,35,39,0A,00,00,00,FC,00,44,45,4C,4C,20, 44,31,36,32,36,48,54,0A,00,00,00,FD,00,32,A0,1E,6B ,FF,00,0A,20,20,20,20,20,20,00,1E

Last edited by jrevillug; 24th April 2009 at 10:31 PM.
Reply With Quote
  #7  
Old 25th April 2009, 12:11 AM
Hlingler Offline
Administrator
 
Join Date: Sep 2006
Location: Connellsville, PA, USA
Posts: 11,291
Oops! Well, poo, I thought that it was a generic X11/X.Org option. You can still try adding it, it should simply be ignored if not used. I hope.

Note that you must edit xorg.conf as root user or sudo, and such a change requires a re-start of X11.

V
Reply With Quote
  #8  
Old 25th April 2009, 10:22 AM
jrevillug Offline
Registered User
 
Join Date: Apr 2009
Location: Bristol, UK
Posts: 12
Unfortunately that option hasn't been recognised.

Indeed you must be the super user to edit xorg.conf and need to restart X.

I'm very tempted to try the RadeonHD open-source driver. Last time I used it (in November) it was quick, but kept crashing my system. The Catalyst driver was slower, but worked.
Reply With Quote
  #9  
Old 25th April 2009, 11:09 AM
Hlingler Offline
Administrator
 
Join Date: Sep 2006
Location: Connellsville, PA, USA
Posts: 11,291
I would suggest that you try the open-source X.Org radeonhd driver. It has come a long way - but not all the way yet, so don't be shocked if it fails miserably. Or, it may surprise you pleasantly. However, in either case, it may not yield the desired refresh rate availability(ies).

The only other suggestion that I have is to scour the ATI FGLRX documentation for an option that gives the equivalent of that CustomEDID option. Please let us know how you make out.

Good Luck,
V
Reply With Quote
  #10  
Old 25th April 2009, 11:12 AM
jrevillug Offline
Registered User
 
Join Date: Apr 2009
Location: Bristol, UK
Posts: 12
Quote:
ATI FGLRX documentation
There doesn't seem to be a huge amount of that about, unfortunately.

I'll certainly keep you updated.

James
Reply With Quote
  #11  
Old 25th April 2009, 12:23 PM
jrevillug Offline
Registered User
 
Join Date: Apr 2009
Location: Bristol, UK
Posts: 12
FIXED IT!

I disabled RandR1.2 by doing the following:

Code:
su
nano /etc/ati/amdpcsdb
In the section
Code:
 [AMDPCSROOT/SYSTEM/DDX]
add
Code:
 EnableRandR12=Sfalse
Save and exit.

Then
Code:
su
nano /etc/X11/xorg.conf
and add to the 'Device' Section
Code:
Option "EnableRandR12" "false"
I then restarted X (Ctrl+Alt+bakspace) and opened both xorg.conf and xorg.0.log as root. I set ignoreEDID to true (since my monitor isn't giving decent results) and took a modeline out of the log file, copied it into xorg.conf and added the name of that mode to the list of modes under the display subsection.

Here is my new xorg.conf:
Code:
# Xorg configuration created by livna-config-display

Section "ServerLayout"
	Identifier     "single head configuration"
	Screen      0  "Screen0" 0 0
EndSection

Section "Files"
	ModulePath   "/usr/lib64/xorg/modules/extensions/fglrx"
	ModulePath   "/usr/lib64/xorg/modules"
EndSection

Section "Module"
EndSection

Section "ServerFlags"
	Option	    "AIGLX" "on"
	Option	    "Xinerama" "off"
EndSection

Section "Monitor"
	Identifier   "aticonfig-Monitor[0]-0"
	VendorName   "Dell"
	ModelName    "D1626HT"
	HorizSync    31.0 - 107.0
	VertRefresh  50.0 - 160.0
Modeline "1600x1200x85.0"  229.50  1600 1664 1856 2160  1200 1201 1204 1250
Modeline "1600x1200x75.0"  202.50  1600 1664 1856 2160  1200 1201 1204 1250
  
	Option	    "DPMS" "true"
EndSection

Section "Device"
	Identifier  "Videocard0"
	Driver      "fglrx"
	Option	    "OpenGLOverlay" "off"
	Option	    "VideoOverlay" "on"
#	Option	    "ForceMonitors" "crt1"
	option	    "EnbleRandR12" "false"
#	option	    "ignoreEDID" "true"
	BusID       "PCI:1:5:0"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Videocard0"
	Monitor    "aticonfig-Monitor[0]-0"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes "1600x1200x85.0" "1600x1200x75.0"
	EndSubSection
EndSection

Section "Extensions"
	Option	    "Composite" "Enable"
EndSection
I know that modelines are old, but it works - I have 1600x1200 resolution with no flickering. I'm happy.

James
Reply With Quote
  #12  
Old 25th April 2009, 08:16 PM
jrevillug Offline
Registered User
 
Join Date: Apr 2009
Location: Bristol, UK
Posts: 12
Oh, yes.

If you are having any difficulty with FGLRX and EDID, disable RandR 1.2 - once I did so EDID was trying to work. However, it seems that the memory in my Monitor has become corrupt at some point.

I hope this helps someone.
James
Reply With Quote
Reply

Tags
3200hd, 780g, ati, changed, chipset, fedora, fglrx, rate, refresh

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Fedora Core 4 - Greeter - change monitor refresh rate eichenma Installation, Upgrades and Live Media 0 11th April 2006 12:34 PM
Regarding refresh rate in Fedora core 2 propellen Hardware & Laptops 11 30th October 2004 02:50 AM
raise refresh rate in fedora core 2 crisdawg Hardware & Laptops 7 24th June 2004 11:53 AM
Refresh rate fjleal Using Fedora 1 11th May 2004 12:28 AM


Current GMT-time: 18:41 (Thursday, 17-04-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat