Announcement

Collapse
No announcement yet.

EDID Modelines Direct From Your TV/Monitor (The Collection).

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    @Jade

    REMOVE ALL MODELINES

    Comment


    • #32
      Originally posted by Kano View Post
      @Jade

      REMOVE ALL MODELINES
      The xorg.conf file (used to produce the log of the previous page) had no custom modelines at all.

      It is posted below.
      Last edited by Jade; 11-29-2008, 09:38 AM.

      Comment


      • #33
        Jade, I believe the log contained entries which implied that there were modelines in the conf file.

        I'm pretty far from an expert in that area, but it sure looked like a problem in the conf file to me.

        Comment


        • #34
          Originally posted by bridgman View Post
          Jade, I believe the log contained entries which implied that there were modelines in the conf file.

          I'm pretty far from an expert in that area, but it sure looked like a problem in the conf file to me.
          NOPE. There were no custom modelines in the Sax generated xorg.conf file and I added none before creating the log.

          Below is the exact xorg.config file that produced the log on the previous page.

          It was produced by SaX. It has had few extraneous sections (eg the extra Depth subsections) deleted and the line

          Modes "800x600"

          changed to

          Modes "1280x1024"

          in an attempt to get 1280x1024 resolution.

          The Modes "800x600" line starts the X-server with 800x600 resolution as expected (by viewing the log).

          The Modes "1280x1024" line causes the X-server to die as expected (and produces the log of the previous page).

          --------------------------------------------

          Adding correct modelines causes the X-server to work and produces the correct screen size, even though the X-server explicitly says a mode is bad.

          For example, adding a correct 1152x864 modeline to the Section "Monitor"

          Section "Monitor"
          ......
          ......
          ......
          # 1152x864 @ 60Hz hsync: 53.7kHz
          Modeline "1152x864" 81.642 1152 1216 1336 1520 864 865 868 895 +hsync +vsync
          EndSection

          causes the X-server to bring up an 1152x864 resolution screen, even though the X-server explicitly states this mode is bad:

          (II) CIRRUS(0): Not using default mode "1152x864" (bad mode clock/interlace/doublescan)

          --------------------------------------------

          # /.../
          # SaX generated X11 config file
          # Created on: 2008-10-11T21:20:08+0000.
          #
          # Version: 7.1
          # Contact: Marcus Schaefer <sax@suse.de>, 2002
          #
          # Automatically generated by [ISaX] (7.1)
          # PLEASE DO NOT EDIT THIS FILE!
          #

          Section "Files"
          FontPath "/usr/X11R6/lib/X11/fonts/misc:unscaled"
          FontPath "/usr/X11R6/lib/X11/fonts/local"
          FontPath "/usr/X11R6/lib/X11/fonts/75dpi:unscaled"
          FontPath "/usr/X11R6/lib/X11/fonts/100dpi:unscaled"
          FontPath "/usr/X11R6/lib/X11/fonts/Type1"
          FontPath "/usr/X11R6/lib/X11/fonts/URW"
          FontPath "/usr/X11R6/lib/X11/fonts/Speedo"
          FontPath "/usr/X11R6/lib/X11/fonts/PEX"
          FontPath "/usr/X11R6/lib/X11/fonts/cyrillic"
          FontPath "/usr/X11R6/lib/X11/fonts/latin2/misc:unscaled"
          FontPath "/usr/X11R6/lib/X11/fonts/latin2/75dpi:unscaled"
          FontPath "/usr/X11R6/lib/X11/fonts/latin2/100dpi:unscaled"
          FontPath "/usr/X11R6/lib/X11/fonts/latin2/Type1"
          FontPath "/usr/X11R6/lib/X11/fonts/latin7/75dpi:unscaled"
          FontPath "/usr/X11R6/lib/X11/fonts/baekmuk:unscaled"
          FontPath "/usr/X11R6/lib/X11/fonts/japanese:unscaled"
          FontPath "/usr/X11R6/lib/X11/fonts/kwintv"
          FontPath "/usr/X11R6/lib/X11/fonts/truetype"
          FontPath "/usr/X11R6/lib/X11/fonts/uni:unscaled"
          FontPath "/usr/X11R6/lib/X11/fonts/CID"
          FontPath "/usr/X11R6/lib/X11/fonts/ucs/misc:unscaled"
          FontPath "/usr/X11R6/lib/X11/fonts/ucs/75dpi:unscaled"
          FontPath "/usr/X11R6/lib/X11/fonts/ucs/100dpi:unscaled"
          FontPath "/usr/X11R6/lib/X11/fonts/hellas/misc:unscaled"
          FontPath "/usr/X11R6/lib/X11/fonts/hellas/75dpi:unscaled"
          FontPath "/usr/X11R6/lib/X11/fonts/hellas/100dpi:unscaled"
          FontPath "/usr/X11R6/lib/X11/fonts/hellas/Type1"
          FontPath "/usr/X11R6/lib/X11/fonts/misc/sgi:unscaled"
          FontPath "/usr/X11R6/lib/X11/fonts/xtest"
          FontPath "/opt/kde3/share/fonts"
          EndSection

          Section "ServerFlags"
          Option "AllowMouseOpenFail"
          EndSection

          Section "Module"
          Load "dbe"
          Load "type1"
          Load "freetype"
          Load "extmod"
          Load "glx"
          Load "v4l"
          EndSection

          Section "InputDevice"
          Driver "kbd"
          Identifier "Keyboard[0]"
          Option "Protocol" "Standard"
          Option "XkbLayout" "us"
          Option "XkbModel" "pc104"
          Option "XkbRules" "xfree86"
          EndSection


          Section "InputDevice"
          Driver "mouse"
          Identifier "Mouse[1]"
          Option "Buttons" "7"
          Option "Device" "/dev/input/mice"
          Option "Name" "ImExPS/2 Generic Explorer Mouse"
          Option "Protocol" "explorerps/2"
          Option "Vendor" "Sysp"
          Option "ZAxisMapping" "4 5"
          EndSection


          Section "Monitor"
          HorizSync 31-58
          Identifier "Monitor[0]"
          ModelName "800X600@60HZ"
          Option "DPMS"
          VendorName "--> VESA"
          VertRefresh 50-61
          EndSection

          Section "Screen"
          DefaultDepth 16
          SubSection "Display"
          Depth 16
          Modes "1280x1024"
          EndSubSection
          Device "Device[0]"
          Identifier "Screen[0]"
          Monitor "Monitor[0]"
          EndSection


          Section "Device"
          BoardName "GD 5446"
          BusID "0:2:0"
          Driver "cirrus"
          Identifier "Device[0]"
          VendorName "Cirrus Logic"
          EndSection


          Section "ServerLayout"
          Identifier "Layout[all]"
          InputDevice "Keyboard[0]" "CoreKeyboard"
          InputDevice "Mouse[1]" "CorePointer"
          Option "Clone" "off"
          Option "Xinerama" "off"
          Screen "Screen[0]"
          EndSection

          Section "DRI"
          Group "video"
          Mode 0660
          EndSection

          Section "Extensions"
          EndSection
          Last edited by Jade; 11-29-2008, 09:44 AM.

          Comment


          • #35
            This is not needed, so you can remove:

            HorizSync 31-58
            VertRefresh 50-61

            Also has this card more than 2 MB VRAM? Because

            1280x1024x2 = 2621440
            1152x864x2 = 1990656

            so if you think logical you need more VRAM or you have to try 8 bit.

            Comment


            • #36
              Originally posted by Kano View Post
              Also has this card more than 2 MB VRAM?.
              If you read the log on the previous page, one of the first lines is:

              (--) CIRRUS(0): VideoRAM: 4096 kByte

              So, guess what? The card has more than 2 MB VRAM.

              So the claim of SABOTAGE stands.

              Comment


              • #37
                Originally posted by Jade
                It is an example of how the cirrus X-server and standard modelines were deliberately made to not work for all but a few (5) screen sizes and refresh rates.
                Or, you know, it could be that the Cirrus server hardly gets much testing anymore, since their chips haven't been popular for over a decade (QEMU notwithstanding).

                Comment


                • #38
                  Originally posted by Ex-Cyber View Post
                  Or, you know, it could be that the Cirrus server hardly gets much testing anymore, since their chips haven't been popular for over a decade (QEMU notwithstanding).
                  NOPE. The Vesa driver gives exactly the same results.

                  The SABOTAGE is clear.

                  Comment


                  • #39
                    So, Cirrus cards are sabotaged in X, but others are not?

                    What exactly are you claiming?

                    Comment


                    • #40
                      The VESA driver finds even less suitable modelines (than the cirrus driver).

                      Also, the VESA driver gives much less relevant information.

                      It only tells you that it has found 3 suitable modelines (it doesn't "find" the 1152x768 line at all):

                      (II) VESA(0): Total Memory: 64 64KB banks (4096kB)
                      (II) VESA(0): Monitor[vesa]: Using hsync range of 31.00-48.00 kHz
                      (II) VESA(0): Monitor[vesa]: Using vrefresh range of 50.00-60.00 Hz
                      (II) VESA(0): Not using mode "default" (no mode of this name)
                      (--) VESA(0): Virtual size is 1024x768 (pitch 1024)
                      (**) VESA(0): Built-in mode "1024x768"
                      (**) VESA(0): Built-in mode "800x600"
                      (**) VESA(0): Built-in mode "640x480"
                      (==) VESA(0): DPI set to (75, 75)
                      (**) VESA(0): Option "ModeSetClearScreen" "no"
                      (II) VESA(0): Attempting to use 60Hz refresh for mode "1024x768" (117)
                      (II) VESA(0): Attempting to use 60Hz refresh for mode "800x600" (114)
                      (II) VESA(0): Attempting to use 60Hz refresh for mode "640x480" (111)

                      Comment


                      • #41
                        Isn't the VESA driver limited to the modes supported by the video BIOS ? I'm not 100% sure but 1152xanything doesn't seem like a common BIOS mode.

                        Comment


                        • #42
                          Maybe put it in dustbin

                          Comment


                          • #43
                            Originally posted by Porter View Post
                            So, Cirrus cards are sabotaged in X, but others are not?

                            What exactly are you claiming?
                            I am claiming (among other things) that the xorg.conf file and modelines have been arranged so that they do not provide the correct X-server settings for many popular screen resolutions.

                            It seems that the favorite xorg.conf file misconfiguration is to set the hsync range and vrefresh ranges too low.

                            In order to get them low enough, they are NOT read from the EDID, i.e., probed from the graphics card, and the numbers produced by X configuration programs (like Sax) are deliberately set too low.

                            If you do not set them at all, then an hsync default range of 28.00-33.00 kHz is used. This is clearly too low and too narrow.

                            The hsync and vrefresh ranges are needed for really old monitors without EDID, but if EDID is found, its values should clearly be those used.

                            Since the X-server could very easily read the hsync range and vrefresh ranges from the EDID, why are they always wrongly set in the xorg.conf file?

                            The reason is, that they were set to make it difficult for people to get graphics working properly (or at all) on Linux.

                            I emphasize that:

                            1) the X-server reads hsync and vrefresh ranges that are usually wrong

                            2) the correct hsync and vrefresh ranges could be read from the EDID (just like the dot clock figure and other info is).

                            3) the hsync and vrefresh ranges are usually set incorrectly and cause difficulties

                            This is/was to cause problems getting graphics setup on Linux.
                            Last edited by Jade; 12-02-2008, 08:34 AM.

                            Comment


                            • #44
                              Originally posted by bridgman View Post
                              Isn't the VESA driver limited to the modes supported by the video BIOS ? I'm not 100% sure but 1152xanything doesn't seem like a common BIOS mode.
                              May not be common but they exist.

                              Comment


                              • #45
                                Originally posted by Jade View Post
                                If you do not set them at all, then an hsync default range of 28.00-33.00 kHz is used. This is clearly too low and too narrow.

                                The hsync and vrefresh ranges are needed for really old monitors without EDID, but if EDID is found, its values should clearly be those used.

                                Since the X-server could very easily read the hsync range and vrefresh ranges from the EDID, why are they always wrongly set in the xorg.conf file?
                                My default xorg.conf file has no hsync or vsync ranges. The default xorg.conf file hasn't had that under Ubuntu for quite some time now.


                                Here's the display section of my xorg.conf:

                                Code:
                                Section "Device"
                                           Identifier  "Configured Video Device"
                                EndSection
                                
                                Section "Monitor"
                                           Identifier  "Configured Monitor"
                                EndSection
                                
                                Section "Screen"
                                           Identifier  "Default Screen"
                                           Monitor     "Configured Monitor"
                                           Device      "Configured Video Device"
                                EndSection

                                Comment

                                Working...
                                X