Bug 20639

Created attachment 23824 [details]
xorg.0.log

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.

Hi, Haien
    Is the SDVO-TV detected in UMS mode?
    If so, please attach the output of xorg.log, vbios dump.
    Thanks.

Because our latest driver has latest tv detection patch, 
haien, could you please update and test it again

Thanks
Ma Ling 

(In reply to comment #8)
> Because our latest driver has latest tv detection patch, 
> haien, could you please update and test it again
> 
> Thanks
> 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.

HaiEn
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 
http://bugs.freedesktop.org/attachment.cgi?id=26795


*** This bug has been marked as a duplicate of bug 20785 ***

(In reply to comment #12)
> HaiEn
> 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 
> http://bugs.freedesktop.org/attachment.cgi?id=26795
> *** This bug has been marked as a duplicate of bug 20785 ***

hi HaiEn

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
Ma Ling

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 

commit 714605e4a05787c51a5ac36c926d2169cfdfbfba
Author: yakui_zhao <yakui.zhao@intel.com>
Date:   Sun May 31 17:18:07 2009 +0800

    drm/i915: Initialize the SDVO device based on the sdvo info parsed from VBT

    http://bugs.freedesktop.org/show_bug.cgi?id=20429

    Signed-off-by: Zhao Yakui <yakui.zhao@intel.com>
    [anholt: Massive cleanup of the slave addr function]
    Signed-off-by: Eric Anholt <eric@anholt.net>

sorry, ignore comment# 16. should be 

http://lists.freedesktop.org/archives/intel-gfx/2009-May/002508.html

This is a regression caused by the following commit:
     commit 13520b051e8888dd3af9bda639d83e7df76613d1
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.
   >http://lists.freedesktop.org/archives/intel-gfx/2009-August/003946.html

Thanks.

The patch is already shipped in the Eric's drm-intel-next tree. 
  commit 27185ae1b795a4ba5e25b95fb5584e950545d774
Author: Ma Ling <ling.ma@intel.com>
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.
Thanks.

Verified with following commits:
Libdrm:  (master)cdd325b59a17a614b90fc2f8b388175e6d79e3cf
Mesa:    mesa_7_6_branch)fac38e8c8f1814ae54703b872db8c6dd21c34a3b
Xserver:   (server-1.6-branch)3044711412d0a08ba65a491bd2441c0c8980f5e2
Xf86_video_intel: (master)b8c5c996e888485c3a16d645c8490592534a7882
Kernel: (master)74fca6a42863ffacaf7ba6f1936a9f228950f657

Closing old verified.