> # So my question is--why is Gnome loading in 800x600 
> resolution, when # I don't have it set differently in this 
> file?  What am I missing # here?
> 
> Look at your X log in /var/log/; it may contain messages 
> about how the modes you've requested are not supported by 
> your monitor, which means either your monitor doesn't support 
> those resolutions or X doesn't know enough about your monitor 
> to make an informed decision.  For example, in my xorg.conf 
> file I have:
> 
> Section "Monitor"
>         Identifier      "Generic Monitor"
>         Option          "DPMS"
>         HorizSync       31-80
>         VertRefresh     56-75
> EndSection
> 
> The sync / refresh rates are in the monitor's manual.  "Option 'DPMS'"
> is enough for some monitors, but I always specify the rates 
> manually to be sure that X works correctly.
> 
> --
>   Jonathan Daugherty
>   http://www.parsed.org
> 

Jonathon,

I have the same in my Monitor section:

Section "Monitor"
        Identifier      "Generic Monitor"
        Option          "DPMS"
        HorizSync       30-121
        VertRefresh     48-160
EndSection


Following your advice I looked into the log file, and it states:

(II) VESA(0): Total Memory: 32 64KB banks (2048kB)
(II) VESA(0): Generic Monitor: Using hsync range of 30.00-121.00 kHz
(II) VESA(0): Generic Monitor: Using vrefresh range of 48.00-160.00 Hz
(II) VESA(0): Not using mode "1280x1024" (no mode of this name)
(II) VESA(0): Not using mode "1024x768" (no mode of this name)
(--) VESA(0): Virtual size is 800x600 (pitch 800)
(**) VESA(0):  Built-in mode "800x600"
(**) VESA(0):  Built-in mode "640x480"
(**) VESA(0):  Built-in mode "640x350"
(--) VESA(0): Display dimensions: (400, 300) mm
(--) VESA(0): DPI set to (50, 50)
(II) VESA(0): Attempting to use 85Hz refresh for mode "800x600" (115)
(II) VESA(0): Attempting to use 85Hz refresh for mode "640x480" (112)
(II) VESA(0): Attempting to use 85Hz refresh for mode "640x350" (245)
(**) VESA(0): Using "Shadow Framebuffer"

This leads me to believe that no such mode exists for 1280x1024 and
1024x768.  However, earlier in the log file (it is QUITE detailed), it
loaded the 1280x1024 and 1024x768 modes.  Here's a snippet of one of them
for 1024x768 (there were probably around 15 of these for all types of
resolutions, multiple ones for each resolution):

Mode: 117 (1024x768)
        ModeAttributes: 0xbb
        WinAAttributes: 0x5
        WinBAttributes: 0x3
        WinGranularity: 64
        WinSize: 64
        WinASegment: 0xa000
        WinBSegment: 0xa000
        WinFuncPtr: 0xc0004b80
        BytesPerScanline: 2048
        XResolution: 1024
        YResolution: 768
        XCharSize: 8
        YCharSize: 16
        NumberOfPlanes: 1
        BitsPerPixel: 16
        NumberOfBanks: 1
        MemoryModel: 6
        BankSize: 0
        NumberOfImages: 0
        RedMaskSize: 5
        RedFieldPosition: 11
        GreenMaskSize: 6
        GreenFieldPosition: 5
        BlueMaskSize: 5
        BlueFieldPosition: 0
        RsvdMaskSize: 0
        RsvdFieldPosition: 0
        DirectColorModeInfo: 0
        PhysBasePtr: 0xfc000000

I have no idea what this section is, but the title does include the
resolution size.  Any idea on how to further identify why it is not
recognizing the node name?  In case this is necessary, the monitor is a 21"
Sony Trinitron connected through a KVM.

Thanks!

Kevin Williams

_______________________________________________
PDXLUG (a Portland Linux user group) mailing list
[email protected]
http://lists.pdxlug.org/mailman/listinfo/pdxlug
IRC: irc.freenode.net #pdxlug & #orlug

Reply via email to