Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Nezhevenko <dion@inhex.net>
To: Eugeni Dodonov <eugeni@dodonov.net>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: HDMI TV doesn't work over HDMI cable
Date: Sun, 15 Apr 2012 22:51:39 +0300	[thread overview]
Message-ID: <20120415195138.GH4446@laptop.local> (raw)
In-Reply-To: <CAC7Lmns=Yix-RfejZ3nbL9ijbafNRBbevmS8PY5PsaeORsQg7Q@mail.gmail.com>

On Sun, Apr 15, 2012 at 12:27:00PM -0300, Eugeni Dodonov wrote:
> could you open a bug on this and attach those Xorg log files together with
> the 'dmesg' output when booting with the 'drm.debug=0xe' kernel parameter?
> And also your kernel version? The
> http://intellinuxgraphics.org/how_to_report_bug.html has a nice summary on
> how to collect all the data we need.

Hi,

I've added all of this: https://bugs.freedesktop.org/show_bug.cgi?id=48740

> One thing that would certainly help is if you could attach the diff between
> running 'intel_reg_dumper' with DVI and HDMI connections (running it over
> ssh for example, if you don't have any valid output with HDMI). The 'no
> signal' message means that we are sending TV data that it does not
> understands, but there are many possible cases why it could happen..
> Intel_reg_dumper should give us a summary of what bits and registers could
> be wrong.
> 

Output looks same :(

--- reg_dumper_dvi.txt  2012-04-15 22:31:26.548920891 +0300
+++ reg_dumper_hdmi.txt 2012-04-15 22:31:31.212984536 +0300
@@ -150,8 +150,8 @@
                    FDI_RXB_IIR: 0x00000000
                    FDI_RXB_IMR: 0x000000ff
                       PCH_ADPA: 0x00f40018 (disabled, transcoder A, +hsync, +vsync)
-                         HDMIB: 0x80000adc (enabled pipe A 8bpc TMDS HDMI audio enabled +vsync +hsync detected)
-                         HDMIC: 0x0000001c (disabled pipe A 8bpc SDVO DVI audio disabled +vsync +hsync detected)
+                         HDMIB: 0x00000adc (disabled pipe A 8bpc TMDS HDMI audio enabled +vsync +hsync detected)
+                         HDMIC: 0x8000025c (enabled pipe A 8bpc SDVO HDMI audio enabled +vsync +hsync detected)
                          HDMID: 0x0000001c (disabled pipe A 8bpc SDVO DVI audio disabled +vsync +hsync detected)
                       PCH_LVDS: 0x40000000 (disabled, pipe B, 18 bit, 1 channel)
                      CPU_eDP_A: 0x00000018

I've added to bugreport that over HDMI cable TV doesn't work even in
BIOS/GRUB screen. Maybe it's intended or maybe not...
 
Thanks

-- 
WBR, Dmitry

      reply	other threads:[~2012-04-15 19:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-14 18:08 HDMI TV doesn't work over HDMI cable Dmitry Nezhevenko
2012-04-15 15:27 ` Eugeni Dodonov
2012-04-15 19:51   ` Dmitry Nezhevenko [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120415195138.GH4446@laptop.local \
    --to=dion@inhex.net \
    --cc=eugeni@dodonov.net \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox