intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [REGRESSION] i915: No HDMI output with 4.4
Date: Mon, 15 Feb 2016 09:57:06 +0200	[thread overview]
Message-ID: <a90b41a8bf714c9ba5a8f4206c94964f@natalenko.name> (raw)
In-Reply-To: <20160212232329.GS23290@intel.com>

Hi, Ville.

13.02.2016 01:23, Ville Syrjälä wrote:
> Few other ideas:
> - Was the monitor sleeping when you tried this? Can you maybe push
>   some button on it and then immediately run the intel_reg read command
>   again?

Nope. It just goes to sleep mode after (I suppose) drm module is loaded. 
Before module gets loaded monitor displays console as it should and does 
not sleep. However, I've tried to switch monitor inputs as well as 
pushing power button with no luck.

> - Do you have another monitor to try?
> - Do you have another cable to try?

Will find that.

> - Maybe the pullup/down on the hpd line is misconfigured or something.
>   Any chance of updating the BIOS on the machine?

===
Base Board Information
         Manufacturer: ASUSTeK COMPUTER INC.
         Product Name: H61M-K
BIOS Information
         Vendor: American Megatrends Inc.
         Version: 0801
         Release Date: 07/21/2014
===

0801 is the latest available for this board.

> - What does 'intel_reg read 0xc2000 0xc2004 0xc2020' say?

===
                                     (0x000c2000): 0x00000000
                                     (0x000c2004): 0x00000001
                                     (0x000c2020): 0x60004000
===

> - The spec claims the TMDS vs. SDVO select has something to do with
>   hpd generation. I can't see any difference on my IVB though, so not
>   sure it's really true.
> 
>   What does 'intel_reg read 0xe1140 0xe1150 0xe1160' tell us?

===
                               HDMIB (0x000e1140): 0x00000018 (disabled 
pipe A 8bpc SDVO DVI audio disabled +vsync +hsync non-detected)
                               HDMIC (0x000e1150): 0x00000804 (disabled 
pipe A 8bpc TMDS DVI audio disabled -vsync -hsync detected)
                               HDMID (0x000e1160): 0x00000018 (disabled 
pipe A 8bpc SDVO DVI audio disabled +vsync +hsync non-detected)
===

>   Let's try these anyway (with the cable plugged in):
> 
>   intel_reg write 0xe1140 0x0
>   intel_reg write 0xe1150 0x0
>   intel_reg write 0xe1160 0x0
>   sleep 1
>   intel_reg read 0xc4000
> 
>   intel_reg write 0xe1140 0x800
>   intel_reg write 0xe1150 0x800
>   intel_reg write 0xe1160 0x800
>   sleep 1
>   intel_reg read 0xc4000
> 
>   intel_reg write 0xe1140 0x800800
>   intel_reg write 0xe1150 0x800800
>   intel_reg write 0xe1160 0x800800
>   sleep 1
>   intel_reg read 0xc4000
> 
>   intel_reg write 0xe1140 0x800000
>   intel_reg write 0xe1150 0x800000
>   intel_reg write 0xe1160 0x800000
>   sleep 1
>   intel_reg read 0xc4000
> 

Same output for all 4 sets of commands:

===
                                     (0x000c4000): 0x00000000
===

Regards,
   Oleksandr.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-02-15  7:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 10:17 [REGRESSION] i915: No HDMI output with 4.4 Oleksandr Natalenko
2016-02-09 10:11 ` Daniel Vetter
2016-02-09 15:56   ` Oleksandr Natalenko
2016-02-11  7:45   ` Oleksandr Natalenko
2016-02-11  8:21     ` Daniel Vetter
2016-02-11  8:54       ` Oleksandr Natalenko
2016-02-11  9:26         ` Ville Syrjälä
2016-02-11 11:16           ` Oleksandr Natalenko
2016-02-11 14:01             ` Ville Syrjälä
2016-02-12  7:52               ` Oleksandr Natalenko
2016-02-12 23:23                 ` Ville Syrjälä
2016-02-15  7:57                   ` Oleksandr Natalenko [this message]
2016-02-15  8:55                   ` Oleksandr Natalenko
2016-02-15 14:42                     ` Ville Syrjälä
2016-02-15 15:42                       ` Daniel Vetter
2016-02-16 10:58                         ` Oleksandr Natalenko
2016-02-16 12:54                           ` Daniel Vetter
2016-02-16 13:21                             ` Oleksandr Natalenko
2016-02-16 15:51                             ` Oleksandr Natalenko
2016-02-22 12:32                             ` Oleksandr Natalenko
2016-02-23 15:08                               ` Ville Syrjälä
2016-02-24  4:40                                 ` Jindal, Sonika
2016-02-24 14:12                                   ` Oleksandr Natalenko
2016-02-24  6:07                                 ` Sharma, Shashank
2016-02-29 15:13                                   ` Daniel Vetter
2016-02-29 15:16                                     ` Sharma, Shashank
2016-02-29 15:41                                       ` Daniel Vetter
2016-02-29 15:41                                         ` Sharma, Shashank
2016-02-29 17:01                                           ` Daniel Vetter
2016-02-24 14:09                                 ` Oleksandr Natalenko

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=a90b41a8bf714c9ba5a8f4206c94964f@natalenko.name \
    --to=oleksandr@natalenko.name \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ville.syrjala@linux.intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).