Bugzilla – Bug 20639
[KMS] SDVO-TV not detected ( device connected to SDVOC)
Last modified: 2009-09-18 00:22:03 UTC
Created attachment 23823 [details]
Bug detailed description:
Current KMS couldn't detect SDVO-TV correctly. dmesg and xorg.0.log are attached.
Created attachment 23824 [details]
an unimplemented feature
reopen to track this feature
I sent patches to mail list too.
As patches are out, mark this as fixed. Reopen if you have problem in testing.
still cannot work.
Is the SDVO-TV detected in UMS mode?
If so, please attach the output of xorg.log, vbios dump.
Because our latest driver has latest tv detection patch,
haien, could you please update and test it again
(In reply to comment #8)
> Because our latest driver has latest tv detection patch,
> haien, could you please update and test it again
> Ma Ling
I have tested it with the latest kernel. and it still fails.
but UMS works well.
what I means is that TV isn't detected in KMS.I think anything about TV should show in dmesg. after start X, I cann't see any TV information in the Xorg.0.log and there is no display on TV-screen. but with the same card, X can start normally with UMS.
ma ling said UMS has this problem as well. updated the summary line.
After updating UMS code from our master tree, the issue also will occur, randomly the sdvo tv device is disconnect. The sdvo device care shows not reliable.
The symptom is the same with bug #20785 please try the patch
*** This bug has been marked as a duplicate of bug 20785 ***
(In reply to comment #12)
> After updating UMS code from our master tree, the issue also will occur,
> randomly the sdvo tv device is disconnect. The sdvo device care shows not
> The symptom is the same with bug #20785 please try the patch
> *** This bug has been marked as a duplicate of bug 20785 ***
The patch from http://bugs.freedesktop.org/attachment.cgi?id=26795 works fine, so could you try it on the issue again?
thanks for your help
Let's track KMS issue (can't detect SDVO-TV) here, and track UMS issue (SDVO-TV connection unreliable) in bug#20785.
*** Bug 22653 has been marked as a duplicate of this bug. ***
isn't this fixed in
Author: yakui_zhao <email@example.com>
Date: Sun May 31 17:18:07 2009 +0800
drm/i915: Initialize the SDVO device based on the sdvo info parsed from VBT
Signed-off-by: Zhao Yakui <firstname.lastname@example.org>
[anholt: Massive cleanup of the slave addr function]
Signed-off-by: Eric Anholt <email@example.com>
sorry, ignore comment# 16. should be
This is a regression caused by the following commit:
Author: Kristian HÃ¸gsberg <krh at redhat.com>
Date: Fri Mar 13 15:42:14 2009 -0400
drm/i915: Read the right SDVO register when detecting SVDO/HDMI
The corresponding patch is already sent to intel-gfx mailing list.
The patch is already shipped in the Eric's drm-intel-next tree.
Author: Ma Ling <firstname.lastname@example.org>
Date: Mon Aug 24 13:50:23 2009 +0800
drm/i915: Always use SDVO_B detect bit for SDVO output detection
The bug can be resolved by this patch. So this bug will be marked as resolved.
Verified with following commits: