Ok, so this sounds like an another HW limitation problem, where the addition of a second head prevents the chipset to drive all screens that the initial resolution and results in poor results.
Intrisically it is a driver bug: the driver shouldn't force the HW to go beyond its limits. Either it should lower the resolution forcefully, or disable support for the 2nd head.
Ok, so this sounds like an another HW limitation problem, where the addition of a second head prevents the chipset to drive all screens that the initial resolution and results in poor results.
Intrisically it is a driver bug: the driver shouldn't force the HW to go beyond its limits. Either it should lower the resolution forcefully, or disable support for the 2nd head.