From: Oleksandr Natalenko <oleksandr@natalenko.name>
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, 16 Feb 2016 15:21:22 +0200 [thread overview]
Message-ID: <266134814abec8f56d12519d27cbb584@natalenko.name> (raw)
In-Reply-To: <20160216125409.GC32705@phenom.ffwll.local>
16.02.2016 14:54, Daniel Vetter wrote:
>> 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"?
Correct.
>> 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.
OK, but will have to steal it again, as it is the only dual link cable I
could find on another workplace.
> 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
Single-link cable is enough to empower LG 23MP65HQ-P as its standard
resolution is 1920×1080@60, which is supported by single-link cable.
Dual-link cable comes with 27MP55HQ-P where it is required to provide
higher resolution. BTW, in my previous email one should read
"27MP55HQ-P" (not "23MP55HQ-P"). It is 27" monitor. Also, this monitor
works with single-link cable (but at lower resolution, I guess).
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-02-16 13:21 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 [this message]
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=266134814abec8f56d12519d27cbb584@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 \
/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).