Originally Posted by netllama
I'd need to see a bug report to determine why the "NoDFPNativeResolutionCheck" parameter failed to work.
I'll get that as soon as I can. In the meantime I tried an older version of the driver and it did try to go in to 1680x1050...unfortunately it freaked out and produced no signal. No amount of fiddling with modelines and clock rates helped.