Results 1 to 9 of 9

Thread: Why fglrx drivers dont like higher vertical refreshes?

  1. #1
    Join Date
    Mar 2009
    Posts
    27

    Default Why fglrx drivers dont like higher vertical refreshes?

    Hello. Why the hell fglrx drivers have so much problems with verfresh settings (at least at my CRT Compaq P700?). My monitor should work good at 1024x768@110. Unfortunately i cannot force fglrx to work with that vrefresh. I hardly forced it to sometimes (1/20 of computer reboots. i could understand if it wouldn't accept 100MHz at all, but only sometimes?) accept 100Hz modeline, now im using 99Hz modeline which is accepted 9/10 times, but still any resolution change i do (for example running opengl game, or going to console with ctrl+alt+1, and back, causes monitor changing refresh to 60Hz, and then i cannot chaneg back to 99Hz.

    Im a bit frustrated, because i fight with this vrefresh about month now, ive tried everything that i thought of still fglrx dont want to obey my modeline settings.

    My modeline:
    Code:
        HorizSync   30-92
        VertRefresh 50-120
    # this are from my monitor manual
        ModeLine "1024x768"  112.04  1024 1096 1208 1392  768 769 772 813  -HSync +Vsync
    #   1024x768@99
    Even then monitor is set to 60Hz, xrandr and ati control center reports that i have 99Hz refresh.

  2. #2
    Join Date
    Aug 2007
    Posts
    6,497

    Default

    I gave up with that issue and bought a TFT. I guess CRT is not really tested well, at least a TFT only needs 60 hz even in analog mode and that works. But with some driver releases you still can enjoy analog flickering on every

    xrandr

    run - I always know when PTS checks it that way

  3. #3
    Join Date
    Jul 2008
    Location
    Germany
    Posts
    424

    Unhappy

    I have the same Problem the fglrx say always my Display can only 60hz

  4. #4
    Join Date
    Aug 2007
    Posts
    6,497

    Default

    Nvidia has this problem too with some monitors where DDC is not working correctly, then you need stupid workarounds in the xorg.conf. Check the log file if it detects EDID.

  5. #5
    Join Date
    Mar 2009
    Posts
    27

    Default

    Code:
    └─[$]> cat /var/log/Xorg.0.log | grep EDID
    (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.
    Code:
    └─[$]> cat /var/log/Xorg.0.log | grep DDC
    (II) fglrx(0):  Display1: No EDID information from DDC.
    But ive earlier tried to manualy turn of edid and/or ddc in xorg.conf, both in Monitor section, and FGLRX option, and always the same.

  6. #6
    Join Date
    Aug 2007
    Posts
    6,497

    Default

    I guess it would be a good time to replace something.

  7. #7
    Join Date
    Jul 2008
    Location
    Germany
    Posts
    424

    Default

    Quote Originally Posted by Kano View Post
    Nvidia has this problem too with some monitors where DDC is not working correctly, then you need stupid workarounds in the xorg.conf. Check the log file if it detects EDID.
    The Problem is the the fglrx can read my EDID Data.

  8. #8
    Join Date
    Oct 2007
    Location
    Roanoke, VA
    Posts
    228

    Default

    Load up the open source radeon driver and see if it makes any difference to EDID being detected.

    I suspect a monitor problem or possibly even a partially bad cable.

  9. #9
    Join Date
    Mar 2009
    Posts
    27

    Default

    This is a very, very old monitor, so maybe it dont have EDID at all? But also it is in a very good shape, and have beautyful image, so i dont want to change it now.
    So how to force fglrx to omit ddc/edid info and pyt monitor in mode strictly defined by modeline ?
    Code:
    └─[$]> cat /var/log/Xorg.0.log |grep mode
    (WW) fglrx(0): Only one display is connnected,so single mode is enabled
    (==) fglrx(0): TMDS coherent mode is enabled
    (II) fglrx(0): Total of 11 modes found for primary display.
    (**) fglrx(0):  Default mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.0 Hz
    (**) fglrx(0):  Default mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.0 Hz
    (**) fglrx(0):  Default mode "800x600": 29.6 MHz (scaled from 0.0 MHz), 29.8 kHz, 47.0 Hz (I)
    (**) fglrx(0):  Default mode "720x480": 26.7 MHz (scaled from 0.0 MHz), 29.8 kHz, 60.0 Hz
    (**) fglrx(0):  Default mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
    (**) fglrx(0):  Default mode "640x400": 24.9 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
    (**) fglrx(0):  Default mode "512x384": 19.8 MHz (scaled from 0.0 MHz), 29.8 kHz, 60.0 Hz
    (**) fglrx(0):  Default mode "400x300": 22.3 MHz (scaled from 0.0 MHz), 45.0 kHz, 60.0 Hz (D)
    (**) fglrx(0):  Default mode "320x240": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz (D)
    (**) fglrx(0):  Default mode "320x200": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz (D)
    (**) fglrx(0):  Default mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.0 Hz
    (**) fglrx(0):  Default mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.0 Hz
    (**) fglrx(0):  Default mode "800x600": 29.6 MHz (scaled from 0.0 MHz), 29.8 kHz, 47.0 Hz (I)
    (**) fglrx(0):  Default mode "720x480": 26.7 MHz (scaled from 0.0 MHz), 29.8 kHz, 60.0 Hz
    (**) fglrx(0):  Default mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
    (**) fglrx(0):  Default mode "640x400": 24.9 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
    (**) fglrx(0):  Default mode "512x384": 19.8 MHz (scaled from 0.0 MHz), 29.8 kHz, 60.0 Hz
    (**) fglrx(0):  Default mode "400x300": 22.3 MHz (scaled from 0.0 MHz), 45.0 kHz, 60.0 Hz (D)
    (**) fglrx(0):  Default mode "320x240": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz (D)
    (**) fglrx(0):  Default mode "320x200": 12.6 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz (D)
    (II) fglrx(0): Restoring recent mode: 1024x768@99Hz
    I found almost identical bug : http://ati.cchtml.com/show_bug.cgi?id=160 but its marked as resolved from fglrx 8.30 version.
    Last edited by Dinth; 03-25-2009 at 09:39 AM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •