With my Clarkdale GPU (Core i3) hooked up to a Full HD Samsung LCD, running Xorg i only have one refresh rate available: 60Hz. I tested it with xrandr -q and also XBMC media center which drops out only 60hz as an available rate. If i manually add 50Hz and 24Hz with xrandr --newmode or defining them with modelines in xorg.conf i can use these resolutions with no problem. Also on windows, they get detected with no problem. I enclosed Xorg.log where i found the raw EDID data which gets read perfectly. I translated this code with Entech's Monitor Assets manager ( http://www.entechtaiwan.com/util/moninfo.shtm ) In this EDID data i can find the missing 50, 24 etc Hz 1080p modes. I also enclosed this translation. Also with other non Intel hardware these modes get detected. I also enclosed a Xorg.log with nvidia hardware and the same TV.
Created attachment 41270 [details] Xorg.log with Intel hardware
Created attachment 41271 [details] Xorg.log with Nvidia hardware
Created attachment 41272 [details] Translated EDID from Intel Xorg.log
The issue is that the additional "modes" are in an unparsed extension block of the EDID.
No exact match for EDID parsing, it's both in the kernel and X. Hopefully this will reach Adam Jackson's ears...
(In reply to comment #5) > No exact match for EDID parsing, it's both in the kernel and X. Hopefully this > will reach Adam Jackson's ears... Is there any progress on this ? I made a test with a fresh 2.6.38+git19032011 kernel and i have the same issue. From the kernel log (with drm.debug=7) I see that the CE identifiers still does not get parsed for KMS. http://pastebin.com/cLgKHHfb
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/152.
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.