Comment 13 for bug 112238

Confirmed here as well. I upgraded from Dapper to Hardy, in Dapper 1600x1200 worked fine, in Hardy I'm dropped to 1280x1024, and Xorg.0.log shows this ('grep 1600x /var/log/Xorg.0.log' - I won't attach the entire files for now):
(II) MGA(0): Not using default mode "1600x1200" (mode clock too high)
(II) MGA(0): Not using default mode "1600x1200" (mode clock too high)
(II) MGA(0): Not using default mode "1600x1200" (mode clock too high)
(II) MGA(0): Not using default mode "1600x1200" (hsync out of range)
(II) MGA(0): Not using default mode "1600x1200" (hsync out of range)
(II) MGA(0): Not using mode "1600x1200" (no mode of this name)

My card is Matrox G450 (16 MB memory), and my monitor's values from 'xorg.conf' are here:
HorizSync 31-92
VertRefresh 50-150

I wonder if this (preceding the list of discared modes ("Not using" lines)) has anything to do with it - i.e. what is the significance of "Using maximum pixel clock of 150.00 MHz", and where does this value come from - and if it has anything to do with the problem, how can it be explicitly changed:
(==) MGA(0): Min pixel clock is 17 MHz
(--) MGA(0): Max pixel clock is 1200 MHz
(II) MGA(0): Fujitsu x174a: Using hsync range of 31.00-92.00 kHz
(II) MGA(0): Fujitsu x174a: Using vrefresh range of 50.00-150.00 Hz
(II) MGA(0): Fujitsu x174a: Using maximum pixel clock of 150.00 MHz
(II) MGA(0): Clock range: 17.75 to 1200.00 MHz

Does anyone have workarounds for this? I wonder if I could find a working 1600x1200 modeline with 'xvidtune', to explicitly specify it. (Had I known about this already in Dapper, I suppose I could've stored a working modeline then...)