That log was with the nv driver, if you wish to use the binary one please use the new "driver manager" which should configure things correctly.
Looking at the log, it shows correct values for the monitor:
(II) NV(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 81 kHz, PixClock max 170 MHz
...
(II) NV(0): Configured Monitor: Using hsync range of 30.00-81.00 kHz
(II) NV(0): Configured Monitor: Using vrefresh range of 56.00-76.00 Hz
(II) NV(0): Configured Monitor: Using maximum pixel clock of 170.00 MHz
(II) NV(0): Estimated virtual size for aspect ratio 1.5758 is 1920x1200
and it should be using the right resolution as well, so I'm not sure where the bug is?
That log was with the nv driver, if you wish to use the binary one please use the new "driver manager" which should configure things correctly.
Looking at the log, it shows correct values for the monitor:
(II) NV(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 81 kHz, PixClock max 170 MHz
...
(II) NV(0): Configured Monitor: Using hsync range of 30.00-81.00 kHz
(II) NV(0): Configured Monitor: Using vrefresh range of 56.00-76.00 Hz
(II) NV(0): Configured Monitor: Using maximum pixel clock of 170.00 MHz
(II) NV(0): Estimated virtual size for aspect ratio 1.5758 is 1920x1200
and it should be using the right resolution as well, so I'm not sure where the bug is?