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

[bridgman]

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.

[Kano]

Maybe put it in dustbin

[Jade]

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.

[Jade]

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.

[Porter]

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:

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

[Jade]

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.

Yes, it reads the hsync range and vrefresh ranges from EDID,... just like all Linux graphics configurations should have many years ago.

The Linux X-server used to read values from the EDID,... but then they tossed away the hsync range and vrefresh ranges and used a very low and very narrow (and thus worse than useless) default.

It is good to see that Ubuntu has changed that practice.

[Porter]

I don't think it's an Ubuntu practice... it's common to most recent X.org implementations as far as I know?

[Ex-Cyber]

I don't think it's an Ubuntu practice... it's common to most recent X.org implementations as far as I know?

Fedora 10 doesn't ship with an xorg.conf at all (at least the spin/config that I installed).

[Porter]

^ There you have it.

[Jade]

^ There you have it.

The fact that things are (perhaps) done right now, for one or two distros, does not mean that all is, or has been, well.