Paul,
Understanding that you drive 15 miles for each test, I went back and reread the whole thread and hit on something I hadn't thought of before. I was working under the assumption that you were getting native resolution to work from the VGA connector but I realize that is not the case. It dawned on me that there may be a problem with the timing in Descriptor #0 with respect to the mini. Frame buffers as found in computers build timings using pixels as the basic building blocks. Many frame buffers, especially older ones, were further restricted in that the smallest building block they could use had to be a multiple of 8 pixels, so 8, 16, 24, 32, 40...etc. More modern frame buffers overcome this restriction to some extent, and I am sure the mini can work from building blocks of a 4 pixel minimum, thus 4, 8, 12, 16, 20, 24...etc. What I notice however is that there are parameters in Descriptor #0 that require two pixel building blocks, namely HFront porch, which is 70 pixels, but far worse is the fact that 1366 itself is not divisible by 4. That means you may never be able to drive this display in native mode.
Below is another timing that satisfies the "divide by 4" rule of the GTF for you to try in case the first timing offered doesn't work:
Pixel clock: 76.79 MHz
HActive: 1364 pixels
HFront porch: 72 pixels
HSync width: 40 pixels
HBack porch: 124 pixels
VActive: 768 lines
VFront porch: 5 lines
VSync width: 5 lines
VBack porch: 22 lines
Alternately, you could try this:
Pixel clock: 76.79 MHz
HActive: 1368 pixels
HFront porch: 68 pixels
HSync width: 40 pixels
HBack porch: 124 pixels
VActive: 768 lines
VFront porch: 5 lines
VSync width: 5 lines
VBack porch: 22 lines
What I am unsure of is how the Maxent is going to handle the two less (or two extra) pixels of active video in the horizontal. It may try to stretch (or shrink) the image accordingly and I don't know if that is really going to upset the image quality or not.
Ideally the mini is going to be able to handle timings per "divide by 2" and 1366 as found in the original timing offered, the one based on data from the DDC, won't be a problem. But just in case, consider one of these other two timings as a back up plan. Cheers.