screen resolution

[starcycle at gmail.com]

On 6/22/06, Jim Cornette <fc-cornette at insight.rr.com> wrote:
> >
>
> The last time that MGA and Intel were both broken was due to a compiler
> error which broke both video controllers in a similar fashion.
>
> Is your X configuration setup as badly as the one someone posted
> earlier? I would not suppose the compiler was amiss again.
>
> https://www.redhat.com/archives/fedora-list/2006-June/msg02385.html
>

i am basically using the default configuration with a few changes, but
it doesn't look all that much different from the one you posted. what
about that is so bad?

anyway, here's the relevant portion of the xorg.conf. it's difficult
working with it, because every error just makes the screen go blank
like it's in "standby" mode -- even just putting another resolution
the mode line -- and the only way to get any screen back at all, even
a console, is to reboot. i guess fedora configured the framebuffer
wrong for the matrox card.

Section "Monitor"

 ### Comment all HorizSync and VertSync values to use DDC:
        Identifier   "Monitor0"
        VendorName   "Monitor Vendor"
        ModelName    "Samsung SyncMaster 172T/176T/CX176T/CX171T (Digital)"
#       DisplaySize  340        270
 ### Comment all HorizSync and VertSync values to use DDC:
        HorizSync    30.0 - 65.0
        VertRefresh  56.0 - 75.0
        Option      "dpms"
EndSection

Section "Device"
        Identifier  "Videocard0"
        Driver      "mga"
        VendorName  "Videocard vendor"
        BoardName   "Matrox Graphics, Inc. G400/G450"
EndSection

Section "Screen"
        Identifier "Screen0"
        Device     "Videocard0"
        Monitor    "Monitor0"
        DefaultDepth     16
        SubSection "Display"
                Viewport   0 0
                Depth     16
                Modes     "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     24
                Modes    "1280x1024"
        EndSubSection