Bug ID | 106589 |
---|---|
Summary | HP w2207 monitor not waking from sleep |
Product | DRI |
Version | unspecified |
Hardware | x86-64 (AMD64) |
OS | Linux (All) |
Status | NEW |
Severity | normal |
Priority | medium |
Component | DRM/AMDgpu |
Assignee | dri-devel@lists.freedesktop.org |
Reporter | tseewald@gmail.com |
Created attachment 139653 [details]
dmesg on 4.17-rc6
Problem:
After allowing both of my monitors to go to sleep, my HP w2207 is no longer
detected as being connected to the computer, and cannot be woken up. Its
display cable must be removed and reinserted into my AMD gpu for it to be
detected.
Expected:
The monitor, like my other samsung, will wake up and the OS will see it as
connected.
Why I think this is possible to fix in software:
The problem does not occur when using my 660Ti with Nvidia's 390.x driver.
Hardware:
GPU: RX 560 4GB
Monitor 1: HP w2207 (Affected)
Monitor 2: Samsung S23A700 (*Not* affected)
I have tried DVI->DVI and DVI->HDMI cables with the HP w2207, no change in
behavior.
The monitor will not wake even when it is the only monitor connected.
I have tested another monitor (an ancient 4:3 dell) in conjunction with the
S23A700, and both wake normally.
Software:
Mesa version: 18.0
X11 version: 1.19.6
Kernel commandline: See attachment for one example (I have tried disabling
amdgpu.dpm and amdgpu.dc to no effect)
EDID: See attachments
Kernel config: see attachments
The only dmesg output before and after the sleep is:
[drm] SADs count is: -2, don't need to read it
[drm] SADs count is: -2, don't need to read it
Kernels tested:
4.16.9
4.16.10
4.17-rc6
amd-drm-staging-next (current as of May 18th 2018)
No changes between any of them.
I also see that the kernel renames the display after a reconnect, I'm not sure
if that is normal either.
e.g.
At boot: card1-HDMI-A-3
After unplugging/replugging: card1-HDMI-A-4
Please let me know what additional information or troubleshooting steps you
would like me to take.
Thanks for your time.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel