Summary: | xf86-video-intel 2.9.0 fails to detect DVI monitor on Mac Mini | ||
---|---|---|---|
Product: | xorg | Reporter: | Shawn Rutledge <shawn.t.rutledge> |
Component: | Driver/intel | Assignee: | ykzhao <yakui.zhao> |
Status: | RESOLVED DUPLICATE | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | critical | ||
Priority: | high | Keywords: | NEEDINFO, regression |
Version: | 7.2 (2007.02) | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
URL: | http://bugs.gentoo.org/show_bug.cgi?id=287705 | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Shawn Rutledge
2009-10-09 15:03:11 UTC
Please provide Xorg log and dmesg accroding to http://intellinuxgraphics.org/how_to_report_bug.html. Please try the KMS mode and see whether the issue still exists. In the KMS mode it will try to read the EDID by using the CRT_DDC bus. >commit 57cdaf90f5f607eb029356074fefb66c9b1c0659 Author: Keith Packard <keithp@keithp.com> Date: Fri Sep 4 13:07:54 2009 +0800 drm/I915: Use the CRT DDC to get the EDID for DVI-connector on Mac As the UMS mode is not supported, the above patch is not back-ported to 2.9.0 intel driver. thanks. As this issue is also related with the following commit and it has the same root cause as bug24255, it will be marked as the dup of bug24255. >commit 02fe9be695f7e209944bd0f7b67950f93619feee Author: Zhao Yakui <yakui.zhao@intel.com> Date: Tue Sep 22 10:58:38 2009 +0800 Check whether the DVI-I/D is connected or disconnected based on EDID In fact this issue is already fixed by the following commit. Please try the Eric's drm-intel-next tree and see whether the issue still exists. Of course the 2.6.32-rc1/rc3 is also ok. (it ships the following commit). >commit 57cdaf90f5f607eb029356074fefb66c9b1c0659 Author: Keith Packard <keithp@keithp.com> Date: Fri Sep 4 13:07:54 2009 +0800 drm/I915: Use the CRT DDC to get the EDID for DVI-connector on Mac *** This bug has been marked as a duplicate of bug 24255 *** |
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.