From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199797] New: Low resolution on monitor reconnect with amdgpu and Dell P2715Q
Date: Tue, 22 May 2018 12:15:23 +0000 [thread overview]
Message-ID: <bug-199797-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=199797
Bug ID: 199797
Summary: Low resolution on monitor reconnect with amdgpu and
Dell P2715Q
Product: Drivers
Version: 2.5
Kernel Version: 4.16.10
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: joh@pseudoberries.com
Regression: No
Created attachment 276131
--> https://bugzilla.kernel.org/attachment.cgi?id=276131&action=edit
Verbose drm log (echo 0xff > /sys/module/drm/parameters/debug)
When I unplug and plug in my Dell P2715Q monitor, the resolution is wrong. I
get 800x600@75Hz instead of the native resolution (3840x2160@60Hz). Sometimes
I'm able to switch to the native resolution with xrandr, other times xrandr
reports that it cannot find the mode. In that case it helps to turn the monitor
off and on, after which the mode is available to xrandr (EDID issue?).
dmesg reports the following error:
[drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring old state
failed with -22
I use a kvm switch with the monitor, so the monitor is reconnected quite often.
I've eliminated the kvm switch as the source of the problem by plugging the
monitor directly into the GPU (an AMD RX560), and replugging the displayport
cable.
I've tried dumping the EDID to /lib/firmware and booting with
drm.edid_firmware=edid/DELL-P2715Q.bin, but this doesn't seem to help.
Verbose drm log attached.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2018-05-22 12:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-199797-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.