The following warnings occurred:
Warning [2] count(): Parameter must be an array or an object that implements Countable - Line: 802 - File: showthread.php PHP 7.3.11-1~deb10u1 (Linux)
File Line Function
/showthread.php 802 errorHandler->error





 Post Reply
Max pixel clock is reported wrong, unable to fix it or change it
08-24-2019, 10:45 AM
Post: #1
Max pixel clock is reported wrong, unable to fix it or change it
Hi,

I have "Sony GDM-F520" CRT monitor hooked up to "Geforce 1080ti" GPU through "Sunix DP-3000" DisplayPort>Analog adapter. The built-in DAC on that adapter has like 500-550MHz pixel clock limit.

The monitor info is detected fine as Sony F520 but the reported max pixel clock is only 220MHz. This used to work fine for me with Sony FW900 before, I was able to reach 500MHz resolution modes. But with this new monitor it is stuck at 220MHz.

I have tried changing this value in CRU and selected "Include if slot available", restarted video and even the whole computer. I can see the new value is remembered by CRU but the artificial limit of 220MHz is still in effect somehow from somewhere.

I can add resolutions beyond 220Hz limit via NCP but that way I cannot use DSR and I often lose signal after a few minutes so the screen shuts off. There is no such random signal loss using built-in resolutions, only with high resolutions added via NCP.

Would you have any ideas what I can try to overcome this? Thank you
Find all posts by this user
Quote this message in a reply
 Post Reply


Messages In This Thread
Max pixel clock is reported wrong, unable to fix it or change it - jka - 08-24-2019 10:45 AM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)