{ "numMessagesInTopic": 3, "nextInTime": 306, "senderId": "wVTm5b7BcGetW1OKBud4nPDan4rCl0lXbaG_MYhLCJfLgDTaxltkl5vDTdlYaWs3VTEQzmqkdAVtRjNl141w6vQ1pwg8BsRyDTEc8c6g3Uxv2Qqm", "systemMessage": false, "subject": "Re: [IBM_T2X_LCD] 33Hz refresh with FX600 PCI? (and genlocking with custom timings)", "from": "Wilson John Chan <wilson@...>", "authorName": "Wilson John Chan", "msgSnippet": "... I just did a quick test with PowerStrip. Not changing any of the blanking interval stuff, I was able to get 30Hz with my FX 600 and DG3. Genlocking went", "msgId": 305, "profile": "wilsoncca", "topicId": 302, "spamInfo": { "reason": "0", "isSpam": false }, "replyTo": "LIST", "userId": 20436897, "messageBody": "
>The one problem I see any time I use a custom timing is no genlockingI just did a quick test with PowerStrip. Not changing any of the
\n>between the two monitor halves. If I depart from the default timing
\n>even a little bit, even in the direction of more generous overhead,
\n>the screens are not genlocked. The default timing matches the EDID
\n>Recommended Timing #3. Could it be that the driver won't try to lock
\n>the heads unless the timing in use matches what's in the EDID, or some
\n>values hard coded into the driver? Is everyone else seeing the same
\n>symptoms?
\n>
\n>Chris
\n>
\n>
\n>
\n>
\n