Originally Posted by craigevil
Why not install the nvidia driver? The 173.14.xx driver supports your card.
It's hard to be clear about every detail in a post that is already too long and has lots more relevant facts I couldn't reasonably fit in.
But I tried to be clear about the fact that I did try the 173.14.xx nvidia driver
and I have been unable to make that driver display anything on my LCD display. I tried that without also having a CRT connected and got no GUI at all. I tried it with both CRT and LCD and got only the CRT working.
Also, using the Mepis X Windows assistant program (as described in your second link) seems to install that nvidia driver, but even trying again after the reboot, it doesn't seem to ever enable that driver. Until I manually edited xorg.conf, X continued to start every time using the fbdev driver. After I manually edited xorg.conf to use nvidia, that worked for the CRT but not for the LCD.
I changed many options following the instructions in the nvidia README file. But even using logverbose, I can't get anything in the log file that tells what options it thinks it understands or why it seems to ignore all the important ones.
The Edid info from this LCD seems to be flawed. It lists a min and max horizontal freq that are equal to each other (I forget the exact value) and a min and max vertical that are both 60. Then it provides suggested modes most of which are different from that single horizontal frequency and a few different from 60 vertical.
From other systems, I already know X doesn't properly handle a min and max that are equal to each other. Even a mode chosen to hit that value will be rejected because of floating point rounding differences. So I tried a number of options to override the Edid frequency limits.
Remember, both Windows and Kubuntu/nouveau can configure this LCD at its native resolution with no user tweaks to Edid at all. Also, further testing with Kubuntu showed me that it sometimes obeys changes requested in the dialog that controls whether the displays are side by side vs. overlapped. It won't change directly from its initial fully overlapped state (after each X startup) to side by side, but it does let you switch the second display to a partially overlapped mode via "absolute" position and from there the switch to side by side usually works.