intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Daniel Vetter <daniel.vetter@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [REGRESSION] i915: No HDMI output with 4.4
Date: Tue, 09 Feb 2016 17:56:10 +0200	[thread overview]
Message-ID: <ecbce3bf5c1f09c3af63246fbac72c39@natalenko.name> (raw)
In-Reply-To: <20160209101136.GR11240@phenom.ffwll.local>

4.5-rc3 is affected as well:

===
kernel: [drm] Initialized drm 1.1.0 20060810
kernel: [drm] Memory usable by graphics device = 2048M
kernel: [drm] Replacing VGA console driver
kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
kernel: [drm] Driver supports precise vblank timestamp query.
kernel: [drm] Initialized i915 1.6.0 20151218 for 0000:00:02.0 on minor 
0
kernel: i915 0000:00:02.0: No connectors reported connected with modes
kernel: [drm] Cannot find any crtc or sizes - going 1024x768
kernel: i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
===

Will try to apply the following dirty workaround:

https://lkml.org/lkml/2016/1/19/637

I guess the problem described via the link above is not fixed yet:

> This issue is still present in 4.5-rc1.

Stay tuned.

09.02.2016 12:11, Daniel Vetter написав:
> Can you please retest with latest -rc? There's been some bugs in the 
> HDMI
> detection changes, which should be fixed now.
> 
> If that doesn't help please try to bisect which exact change caused the
> regression.
> 
> Thanks, Daniel

  reply	other threads:[~2016-02-09 15:56 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 [this message]
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ä
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=ecbce3bf5c1f09c3af63246fbac72c39@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).