From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@cs.helsinki.fi>,
"Dave Airlie" <airlied@redhat.com>,
dri-devel@lists.freedesktop.org
Subject: Re: DRM/AST regression (likely 4.14 -> 4.19+), providing EDID manually fails
Date: Wed, 12 Jun 2019 13:55:55 +0300 [thread overview]
Message-ID: <874l4vxebo.fsf@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1905262211270.24390@whs-18.cs.helsinki.fi>
On Sun, 26 May 2019, Ilpo Järvinen <ilpo.jarvinen@cs.helsinki.fi> wrote:
> Hi all,
>
> I've a workstation which has internal VGA that is detected as AST 2400 and
> with it EDID has been always quite flaky (except for some time it worked
> with 4.14 long enough that I thought the problems would be past until the
> problems reappeared also with 4.14). Thus, I've provided manually the EDID
> that I extracted from the monitor using other computer (the monitor itself
> worked just fine on the earlier computer so it is likely fine).
>
> I setup the manual EDID using drm_kms_helper.edid_firmware, however,
> after upgrading to 4.19.45 it stopped working (no "Got external EDID base
> block" appears in dmesg, the text mode is kept in the lower res mode, and
> Xorg logs no longer dumps the EDID info like it did with 4.14). So I guess
> the EDID I provided manually on the command line is not correctly put into
> use with 4.19+ kernels.
>
> The 4.19 dmesg indicated that drm_kms_helper.edid_firmware is deprecated
> so I also tested with drm.edid_firmware it suggested as the replacement
> but with no luck (but I believe also the drm_kms_helper one should have
> worked as it was only "deprecated").
>
> I also tried 5.1.2 but it did not work any better (and with it also tried
> removing all the manual *.edid_firmware from the command line so I still
> need to provide one manually to have it reliable working it seems).
This should be fixed by commit
commit 48eaeb7664c76139438724d520a1ea4a84a3ed92
Author: Jani Nikula <jani.nikula@intel.com>
Date: Mon Jun 10 12:30:54 2019 +0300
drm: add fallback override/firmware EDID modes workaround
in drm-misc-fixes, cc: stable v4.15.
Thanks for the report.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-06-12 10:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-26 19:50 DRM/AST regression (likely 4.14 -> 4.19+), providing EDID manually fails Ilpo Järvinen
2019-05-27 16:42 ` Ashutosh Dixit
2019-05-28 7:30 ` Jani Nikula
2019-05-29 8:31 ` Ilpo Järvinen
2019-05-29 10:22 ` Jani Nikula
2019-06-04 6:15 ` Harish Chegondi
2019-06-04 8:10 ` Ilpo Järvinen
2019-06-07 11:08 ` Jani Nikula
2019-06-04 8:18 ` Jani Nikula
2019-06-05 1:48 ` Harish Chegondi
2019-06-12 10:55 ` Jani Nikula [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=874l4vxebo.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ilpo.jarvinen@cs.helsinki.fi \
/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).