mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Bowler <nbowler@draconx.ca>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	intel-gfx@lists.freedesktop.org
Subject: Re: PROBLEM: Intel VGA output busticated on 4.3-rc2 (regression)
Date: Wed, 7 Oct 2015 11:44:56 -0400	[thread overview]
Message-ID: <CADyTPEwJhVoWpq5==aBEhxQ+ccRs8WhRB6PCb6Uw_6Z2O2GiZw@mail.gmail.com> (raw)
In-Reply-To: <20151007153202.GN26517@intel.com>

On 10/7/15, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Wed, Oct 07, 2015 at 10:29:22AM -0400, Nick Bowler wrote:
>> On 10/7/15, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
>> > On Tue, Oct 06, 2015 at 11:42:33AM -0400, Nick Bowler wrote:
>> >> On 9/24/15, Nick Bowler <nbowler@draconx.ca> wrote:
>> >> > Testing out 4.3-rc2, first thing I notice is that the VGA output is
>> >> > not working.  Specifically, the display is continuously powering on
>> >> > and off -- at no point is any image visible on the screen (I am
>> >> > expecting to see the console output).  The display connected to the
>> >> > HDMI output is working fine.
>> [...]
> Hmm. You said VGA has the problem, but HDMI does not. Was the problem
> happening even when you have both displays enabled at the same time, or
> just when VGA was enabled alone?

When I boot with HDMI cable disconnected, there is no change in behaviour
for the VGA output.

> I've attached two potential patches that might help. Can you give a try
> to just patch 1, and if that alone doesn't help then both patches
> together?

I will try.

Cheers,
  Nick

  reply	other threads:[~2015-10-07 15:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 21:22 Nick Bowler
2015-09-25 12:25 ` Daniel Vetter
2015-10-06 15:42 ` Nick Bowler
2015-10-07 11:58   ` Ville Syrjälä
2015-10-07 14:29     ` Nick Bowler
2015-10-07 15:32       ` Ville Syrjälä
2015-10-07 15:44         ` Nick Bowler [this message]
2015-10-07 15:47           ` Nick Bowler
2015-10-07 18:50         ` Nick Bowler
2015-10-07 19:04           ` Ville Syrjälä

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='CADyTPEwJhVoWpq5==aBEhxQ+ccRs8WhRB6PCb6Uw_6Z2O2GiZw@mail.gmail.com' \
    --to=nbowler@draconx.ca \
    --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

all inboxes | Powered by JetHome®