Summary: | [EDID] failure to retrieve EDID when monitor is off | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Akim <administrator> | ||||||||||
Component: | DRM/Intel | Assignee: | Jesse Barnes <jbarnes> | ||||||||||
Status: | CLOSED FIXED | QA Contact: | |||||||||||
Severity: | normal | ||||||||||||
Priority: | medium | Keywords: | NEEDINFO | ||||||||||
Version: | unspecified | ||||||||||||
Hardware: | x86 (IA32) | ||||||||||||
OS: | Linux (All) | ||||||||||||
Whiteboard: | |||||||||||||
i915 platform: | i915 features: | ||||||||||||
Attachments: |
|
Description
Akim
2010-06-30 03:24:48 UTC
Please attach X logs for both cases. Clear the NEEDINFO keyword when that's done. Thanks. Created attachment 36631 [details]
Xorg.log when monitor switched on
Created attachment 36632 [details]
Xorg.log when monitor swiched off
(In reply to comment #1) > Please attach X logs for both cases. Clear the NEEDINFO keyword when that's > done. > > Thanks. done WBR Weird, the driver doesn't seem to get EDID from the monitor when it's off... Reassigning to intel drm. Created attachment 37251 [details] [review] drm framework for flexible edid fetch First patch Created attachment 37252 [details] [review] add gmbus edid fetch Second patch Can you try the two patches I just attached? Apply them in order of first, second. Hopefully the EDID that comes back will be correct in both cases. (In reply to comment #8) > Can you try the two patches I just attached? Apply them in order of first, > second. Hopefully the EDID that comes back will be correct in both cases. Which kernel version shall I apply the patches to? (In reply to comment #8) > Can you try the two patches I just attached? Apply them in order of first, > second. Hopefully the EDID that comes back will be correct in both cases. Which kernel version shall I apply the patches to? On Tue, 20 Jul 2010 23:46:53 -0700 (PDT) bugzilla-daemon@freedesktop.org wrote: > https://bugs.freedesktop.org/show_bug.cgi?id=28843 > > --- Comment #10 from Akim <administrator@makc.san.ru> 2010-07-20 23:46:53 PDT --- > (In reply to comment #8) > > Can you try the two patches I just attached? Apply them in order of first, > > second. Hopefully the EDID that comes back will be correct in both cases. > > Which kernel version shall I apply the patches to? I generated it against the drm-intel-next branch of Eric's git tree (git://git.kernel.org/pub/scm/linux/kernel/git/anholt/drm-intel.git). But it will probably apply to 2.6.35-rc5 as well. Any news? (In reply to comment #12) > Any news? I'm sorry, I was busy and to be honest, I forgot :((. News. I tried to patch 2.6.32 kernel (from repo - Ubuntu Lucid), unsucsessfully. Whith 2.6.35 i'll try soon. It is need to say, these mashines are in the office and I don't have much time to use them not for a work. I plan to finish at this weekend. One more thing. Is it possible, that trouble is not in the driver, but monitors? I got a new monitor (LCD) and this bug is absent; the refresh rate is the same (60 and 75 Hz) when monitor switched off or swithed on at boot time. Other CRT monitor I dont have yet. Sorry my language :) (In reply to comment #12) > Any news? Well, I'm finished. And patches are working! Congratulations! Now, after booting it is possible set any refresh rate other than 60 Hz. But the refresh rate by default is still 60 Hz, and it is need to set another one every time you boot with the switched off monitor (not a driver problem?) Excellent news! I spent sometime this week rewriting those patches for -next (and will push them as soon as I am home and able to boot test them on a couple more machines). As soon as that branch is available, I'll ask you test drm-intel-next and then we can be confident that the issue will be fixed in 2.6.37. The drm driver will choose a mode that is suitable for all outputs connected on boot, you can override this with the video= boot parameter (iirc). Marking fixed as the GMBus patches have landed in -next. (And hopefully I've ironed out all the regressions...) |
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.