From: Daniel Vetter <daniel@ffwll.ch>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Daniel Vetter" <daniel.vetter@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Sonika Jindal" <sonika.jindal@intel.com>,
"Shashank Sharma" <shashank.sharma@intel.com>,
"Gary Wang" <gary.c.wang@intel.com>
Subject: Re: [REGRESSION] i915: No HDMI output with 4.4
Date: Tue, 16 Feb 2016 13:54:09 +0100 [thread overview]
Message-ID: <20160216125409.GC32705@phenom.ffwll.local> (raw)
In-Reply-To: <20e547eacc03eef67541c56e85612d0c@natalenko.name>
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?
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2016-02-16 12:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 10:17 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 [this message]
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=20160216125409.GC32705@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary.c.wang@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr@natalenko.name \
--cc=shashank.sharma@intel.com \
--cc=sonika.jindal@intel.com \
--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
Powered by JetHome