Summary: | [amdgpu] all displays reconnect after failed EDID read | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Matthias <mail> | ||||||
Component: | DRM/AMDgpu | Assignee: | Default DRI bug account <dri-devel> | ||||||
Status: | RESOLVED MOVED | QA Contact: | |||||||
Severity: | major | ||||||||
Priority: | medium | CC: | harry.wentland, mail | ||||||
Version: | XOrg git | ||||||||
Hardware: | x86-64 (AMD64) | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
Matthias
2018-05-30 15:05:04 UTC
Created attachment 139862 [details]
Xorg.log
Should I try to force a binary EDID for the connected PSVR? maybe like the solution proposed here: http://hotcashew.com/2013/08/fixing-invalid-edid-in-linux-wit-fglrx/ (In reply to Matthias from comment #2) > Should I try to force a binary EDID for the connected PSVR? At this time, I would recommend against this: I experience consistent crashes on evey S3 resume if use the kernel command line parameter to force a certain binary EDID. Which is a pity, because (a) this worked fine with prior kernel versions until early October 2017 and (b) it was useful when waking up the computer remotely while the connected display is still switched off. See also: https://bugs.freedesktop.org/show_bug.cgi?id=103277 -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/408. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.