dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Paul Wise <pabs3@bonedaddy.net>
To: Jani Nikula <jani.nikula@intel.com>
Cc: "Abdiel Janulgue" <abdiel.janulgue@linux.intel.com>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Daniel Vetter" <daniel.vetter@ffwll.ch>,
	"Gustavo Padovan" <gustavo@padovan.org>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Sean Paul" <seanpaul@chromium.org>,
	"David Airlie" <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: linux: REGRESSION: drm: cmdline EDID override mechanisms broken since 4.15
Date: Thu, 16 Aug 2018 10:29:32 +0800	[thread overview]
Message-ID: <10df62228da4824d65f3f4765657ef776833d12c.camel@bonedaddy.net> (raw)
In-Reply-To: <87h8jw7wqc.fsf@intel.com>

[-- Attachment #1: Type: text/plain, Size: 570 bytes --]

On Wed, 2018-08-15 at 13:25 +0300, Jani Nikula wrote:

> Please file a bug over at [1], describe the symptomps of how it doesn't
> work (black screen, wrong mode, what?), add drm.debug=14 module
> parameter, attach dmesg for before/after the bisected commit.

Filed the bug here:

https://bugs.freedesktop.org/show_bug.cgi?id=107583%27

> Does adding video=VGA-1:e parameter make a difference?

That works around the issue. I assume this means the VGA will always be
enabled even if it is not plugged in?

-- 
bye,
pabs

https://bonedaddy.net/pabs3/

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2018-08-16  2:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-15 10:00 linux: REGRESSION: drm: cmdline EDID override mechanisms broken since 4.15 Paul Wise
2018-08-15 10:25 ` Jani Nikula
2018-08-16  2:29   ` Paul Wise [this message]

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=10df62228da4824d65f3f4765657ef776833d12c.camel@bonedaddy.net \
    --to=pabs3@bonedaddy.net \
    --cc=abdiel.janulgue@linux.intel.com \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gustavo@padovan.org \
    --cc=jani.nikula@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=seanpaul@chromium.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;
as well as URLs for NNTP newsgroup(s).