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

On Mon, Feb 22, 2016 at 02:32:32PM +0200, Oleksandr Natalenko wrote:
> Ville, Daniel,
> 
> any additional info I could provide? I have to return dual-link DVI 
> cable back, so let me know if I could reveal more details if necessary.

Unfortunately I'm out of ideas for now. Daniel is on vacation.
Anyone else? VPG folks should take the ball here since they broke it.

In the meantime I think as a workaround I think you could use
something like video=HDMI-A-1:e on the kernel command line (not sure
I got the connector name right for your system). I think that should
result in the live status check to be skipped, at least when
populating the mode list.

Might be a good idea to collect all the information here and put in a
bug report (https://bugs.freedesktop.org/ -> DRI -> DRM/Intel) so that
all the logs and such would be in one place.

> 
> Regards,
>    Oleksandr
> 
> 16.02.2016 14:54, Daniel Vetter написав:
> > On Tue, Feb 16, 2016 at 12:58:56PM +0200, Oleksandr Natalenko wrote:
> >> Ville, Daniel,
> >> 
> >> I've just got another monitor and another DVI-HDMI cable, and here 
> >> what I've
> >> got.
> >> 
> >> ===Single Link DVI-D cable with 3 different monitors===
> >> 
> >> Computer DVI ——— DVI-D (Single Link)/HDMI cable ——— HDMI LG 23MP65HQ-P 
> >> ===
> >> not working
> > 
> > I presume the above LG screen is what you've called previously "old
> > monitor"?
> > 
> >> Computer DVI ——— DVI-D (Single Link)/HDMI cable ——— HDMI LG 23MP67HQ-P 
> >> ===
> >> not working
> >> Computer DVI ——— DVI-D (Single Link)/HDMI cable ——— HDMI LG 23MP55HQ-P 
> >> ===
> >> works!
> >> 
> >> ===Dual Link DVI-D cable with monitor that doesn't work with Single 
> >> Link
> >> cable===
> >> 
> >> Computer DVI ——— DVI-D (Dual Link)/HDMI cable ——— HDMI LG 23MP65HQ-P 
> >> ===
> >> works!
> > 
> > Funky. Can you pls grab the debug logs (with the special patches from
> > Ville) for this case? I wonder why suddenly different cable and it 
> > works.
> > 
> > Also: Is this one of these older-ish screens where you must have a
> > dual-link cable to drive it at full resolution&refresh rate?
> > -Daniel
> > 
> > 
> >> ===Laptop with HDMI output===
> >> 
> >> Laptop HDMI ——— HDMI/HDMI cable ——— HDMI LG 23MP65HQ-P === works!
> >> 
> >> I'd say that single link DVI cables are broken with new kernel, but 
> >> one of
> >> monitors could work with such a cable. So I have no idea :(.
> >> 
> >> Regards,
> >>   Oleksandr.
> >> 
> >> 15.02.2016 17:42, Daniel Vetter wrote:
> >> >The other downside is that it'll make us non-compliant, which was the
> >> >point of this entire ordeal: HDMI spec forbids us from starting any i2c
> >> >transactions when the hpd isn't signalling a present screen.
> >> >
> >> >So maybe we need to buy one of these broken screens.
> >> >
> >> >Oleksandr, what exact model are you using? And any chance that you could
> >> >test this on some other machine with intel gfx and latest kernel, just to
> >> >make sure this really is some issue with the sink and not with the machine
> >> >itself? And I guess you've tested with some other hdmi sink, and that
> >> >works?

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-02-23 15:08 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
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ä [this message]
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=20160223150800.GK23290@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --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=oleksandr@natalenko.name \
    /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).