Thank you: I fixed it by setting the "ignoreABI" switch when starting
Gnome. Not the best way, but it works for now
On 11/1/06, Alexander Federlin <email address hidden> wrote:
> I had the same problems with my ancient Matrox Mystique (Monitor shows
> frequency out of range)
>
> I solved it by turning on the ShadowFB option:
>
> Section "Device"
> Identifier "Matrox Graphics, Inc. MGA 1064SG Mystique]"
> Driver "mga"
> BusID "PCI:0:12:0"
> Option "ShadowFB" "true"
> Option "OldDmaInit" "True"
> EndSection
>
> (The OldDmaInit options seems not to matter)
>
> I had to specify the HorizSync and VertRefresh options for my monitor.
> Now it works with a resolution of "1024x768" and a Depth of 16.
>
> I had the same problem when installing Dapper.
>
> --
> Edgy upgrade breaks multiple Matrox cards
> https://launchpad.net/bugs/58721
>
Thank you: I fixed it by setting the "ignoreABI" switch when starting
Gnome. Not the best way, but it works for now
On 11/1/06, Alexander Federlin <email address hidden> wrote: /launchpad. net/bugs/ 58721
> I had the same problems with my ancient Matrox Mystique (Monitor shows
> frequency out of range)
>
> I solved it by turning on the ShadowFB option:
>
> Section "Device"
> Identifier "Matrox Graphics, Inc. MGA 1064SG Mystique]"
> Driver "mga"
> BusID "PCI:0:12:0"
> Option "ShadowFB" "true"
> Option "OldDmaInit" "True"
> EndSection
>
> (The OldDmaInit options seems not to matter)
>
> I had to specify the HorizSync and VertRefresh options for my monitor.
> Now it works with a resolution of "1024x768" and a Depth of 16.
>
> I had the same problem when installing Dapper.
>
> --
> Edgy upgrade breaks multiple Matrox cards
> https:/
>