Some settings made in xorg.conf are ignored/get lost. * The Modeline "1280x1024" 109.00 1280 1368 1504 1728 1024 1027 1034 1069 is never used. * The values HorizSync 30-150 VertRefresh 30-150 are first honored (II) intel(0): Using hsync ranges from config file (II) intel(0): Using vrefresh ranges from config file but then lost (output from xf86ProbeOutputModes after setting the default which was changed in the source to 10-90, 10-150. In other words: The default is used) (II) intel(0): VRefresh-Range 10.0-90.0 Hz (II) intel(0): HSync-Range 10.0-150.0 kHz * The setting DisplaySize 708 398 is ignored, the values reported by EDID are honored
Created attachment 9531 [details] Log
Created attachment 9532 [details] xorg.conf
This bug is still present in 7.3.
I've been using the nv driver. Today I tried the closed-source binary driver from Nvidia, and then DisplaySize is honored. Perhaps it's something driver specific?
Could be related to #12474, fixed in xserver git recently.
After several days of work I finally got git head to compile. I just tested it and none of the three problems is solved. > Could be related to #12474, fixed in xserver git recently. It is solved at the wrong place (look at the new log) and xorg.conf doesn't override the EDID settings. The other two problems are also unchanged.
Created attachment 12336 [details] New log
Section "Monitor" Identifier "Xoro" HorizSync 30-150 VertRefresh 30-150 DisplaySize 709 398 Option "PreferredMode" "1920x1080" UseModes "XoroModes" EndSection
The first two settings are honered after using the patch from http://bugs.freedesktop.org/show_bug.cgi?id=10584 The bug "The setting DisplaySize 708 398 is ignored, the values reported by EDID are honored" is not so important.
It may not be very important, but it's still a bug, right? It can cause strange effects in some, admittedly not very common, cases. If the DisplaySize option is going to be unused then it could at least be removed from the documentation or something. Wouldn't it be better to leave it as a bug but with a low priority? About my silly comments on drivers earlier, I don't know what that was about. The problem persists on my new system with the intel driver.
I still think it's a bug when xorg.conf settings are ignored...
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.