Glen <stormbind@xxxxxxxxx> wrote: > > For laptop panels, the resolution is read directly from the > > registers > > on startup (it relies on the BIOS having programmed the correct > > resolution -- this works independently from the resolution you set > > at > > boot). > > In all other cases, it uses EDID information. The common code will > > just > > fill the missing mode information; > > In any case, it's all in mode.cpp in the Intel driver. > Arr. That would explain the problem. > > It has correctly stored the height/width from the BIOS, and then it > has later added the EDID information. However, it has combined the > different sets of data to derive ambiguous display settings. > > I'll print off a load of code and pin it to my wall. Thanks. Maybe the debug output can already help :-) Bye, Axel.