As I mentioned in comments to the report on the related Bug 190378, several weeks ago I had used nvidia-xconfig in an attempt to enable the proprietary driver. That might be the source of the bad settings for my monitor.
However, until I can figure out why X is crashing using the "non-tainted" nv driver, I do not have access to X in Hardy.
As I mentioned in comments to the report on the related Bug 190378, several weeks ago I had used nvidia-xconfig in an attempt to enable the proprietary driver. That might be the source of the bad settings for my monitor.
However, until I can figure out why X is crashing using the "non-tainted" nv driver, I do not have access to X in Hardy.
Please see the attachments to Bug 190381.