From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110371] HP Dreamcolor display *Error* No EDID read
Date: Wed, 15 May 2019 05:02:14 +0000 [thread overview]
Message-ID: <bug-110371-502-0wwAXQs9fe@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110371-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2573 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110371
--- Comment #11 from Babblebones@gmail.com ---
Created attachment 144277
--> https://bugs.freedesktop.org/attachment.cgi?id=144277&action=edit
EDID file
Don't know if this helps but ALL kernels seem affected by not being able to
grab EDID on startup but the changes after 4.18 break something further as to
make the display unusable by changing the default behavior of the panel's mode
without EDID.
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.18.20
root=/dev/sdb2 ro amdgpu.ppfeaturemask=0xffffffff amdgpu.dpm=1 amdgpu.dc=1
amdgpu.gpu_recovery=1 amdgpu.powerplay=1 drm.edid_firmware=eDP-1:edid/edid.bin
[ 4.340989] [drm] Got external EDID base block and 0 extensions from
"edid/edid.bin" for connector "eDP-1"
[ 4.451624] drm_do_probe_ddc_edid+0xb9/0x130
[ 4.451628] ? drm_edid_block_valid+0x180/0x180
[ 4.451629] drm_do_get_edid+0xb1/0x330
[ 4.451631] drm_get_edid+0x61/0x380
[ 4.451671] dm_helpers_read_local_edid+0x4c/0xe0 [amdgpu]
[ 4.630956] drm_do_probe_ddc_edid+0xb9/0x130
[ 4.630966] ? drm_edid_block_valid+0x180/0x180
[ 4.630969] drm_do_get_edid+0xb1/0x330
[ 4.630972] drm_get_edid+0x61/0x380
[ 4.631115] dm_helpers_read_local_edid+0x4c/0xe0 [amdgpu]
[ 4.801879] drm_do_probe_ddc_edid+0xb9/0x130
[ 4.801889] ? drm_edid_block_valid+0x180/0x180
[ 4.801892] drm_do_get_edid+0xb1/0x330
[ 4.801895] drm_get_edid+0x61/0x380
[ 4.802006] dm_helpers_read_local_edid+0x4c/0xe0 [amdgpu]
[ 4.972889] drm_do_probe_ddc_edid+0xb9/0x130
[ 4.972900] ? drm_edid_block_valid+0x180/0x180
[ 4.972903] drm_do_get_edid+0xb1/0x330
[ 4.972907] drm_get_edid+0x61/0x380
[ 4.973028] dm_helpers_read_local_edid+0x4c/0xe0 [amdgpu]
[ 5.145825] drm_do_probe_ddc_edid+0xb9/0x130
[ 5.145835] ? drm_edid_block_valid+0x180/0x180
[ 5.145837] drm_do_get_edid+0xb1/0x330
[ 5.145841] drm_get_edid+0x61/0x380
[ 5.145942] dm_helpers_read_local_edid+0x4c/0xe0 [amdgpu]
[ 5.170556] [drm:dc_link_detect [amdgpu]] *ERROR* No EDID read.
Is what happens when I set the edid manually from the kernel commandline.
Setting it manually freaks out newer kernels and my display won't modeset
properly making it a mess but on 4.18 it seemed to drop this.
Any debug patches I can run to help you guys figure it out?
I have included my EDID file if you want to run it through anything to see what
breaks.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3457 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-05-15 5:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 3:38 [Bug 110371] HP Dreamcolor display *Error* No EDID read bugzilla-daemon
2019-04-10 7:38 ` bugzilla-daemon
2019-04-13 2:14 ` bugzilla-daemon
2019-04-18 14:40 ` bugzilla-daemon
2019-04-18 14:59 ` bugzilla-daemon
2019-04-18 15:11 ` bugzilla-daemon
2019-04-18 15:29 ` bugzilla-daemon
2019-04-19 17:59 ` bugzilla-daemon
2019-05-02 3:09 ` bugzilla-daemon
2019-05-05 17:48 ` bugzilla-daemon
2019-05-05 18:31 ` bugzilla-daemon
2019-05-10 22:32 ` bugzilla-daemon
2019-05-15 5:02 ` bugzilla-daemon [this message]
2019-10-15 2:28 ` bugzilla-daemon
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=bug-110371-502-0wwAXQs9fe@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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