| Summary: | Display will not wake from DPMS since 5.25 (Wayland Nvidia) | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | tsweet64 |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | andrej.halv, me, nate, xaver.hugl |
| Priority: | NOR | Keywords: | regression |
| Version: | 5.25.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/plasma/kwin/commit/d0634166267c6ee02b4a4caeaa945e07302e222f | Version Fixed In: | 5.25.3 |
| Sentry Crash Report: | |||
| Attachments: |
output of journalctl --boot 0 | grep kwin_wayland_drm
dmesg output with drm debugging |
||
|
Description
tsweet64
2022-06-22 21:57:01 UTC
*** This bug has been marked as a duplicate of bug 455795 *** I have tried using the master version and the 5.25 branch and I still experience this issue. I still get this when viewing the journalctl with "journalctl -b | grep kwin" "kwin_wayland_drm: Couldn't parse EDID for connector DrmConnector(id=78, gpu=KWin::DrmGpu(0x55e8f0bbe0e0), name="eDP-1-unknown", connection="Connected", countMode=14)" Although the "kwin_wayland_drm: Setting dpms mode failed!" doesn't appear anymore with the latest commits. Operating System: Arch Linux KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.18.5-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: AMD Ryzen 9 4900HS 8-Core Processor Memory: 16GB of RAM Graphics Processor: Integrated: Vega 8 Dedicated: NVIDIA GeForce RTX 2060 Max-Q Manufacturer: ASUS Bug 455795 was just fixed yesterday; are you sure you have https://invent.kde.org/plasma/kwin/-/commit/ea8b0d962be15fbf5c4c29ac4dd657ff34344e17? (In reply to Nate Graham from comment #3) > Bug 455795 was just fixed yesterday; are you sure you have > https://invent.kde.org/plasma/kwin/-/commit/ > ea8b0d962be15fbf5c4c29ac4dd657ff34344e17? Yes, I can assure you that I had that commit when compiling kwin. I have used the Plasma/5.25 branch and I have checked that those changes were actually there. The steps I have made: 1. (in kwin git folder) mkdir build && cd build 2. cmake .. 3. make -j8 4. sudo pacman -R kwin (to uninstall my current kwin package) 5. sudo make install (to install newly compiled kwin) 6. restarted my machine I have updated to Plasma 5.25.2 but the issue still persists. But as I previously said, this error doesn't appear anymore. >kwin_wayland_drm: Setting dpms mode failed! But this one still does: >kwin_wayland_drm: Couldn't parse EDID for connector DrmConnector(id=78, gpu=KWin::DrmGpu(0x55d5c9178250), name="eDP-1-unknown", connection="Connected"```, countMode=14) For now I use a really hacky workaround where I basically enable the dpms back on with "kscreen-doctor --dpms on" by using systemd to execute it before suspending. After that resuming works perfectly. And btw how can I make sure that Xaver Hugl has been CC'd or "pinged" again? I am not sure how all of this works exactly. Thanks! The EDID problem is known but shouldn't cause any real problems. To help debug this, please add > QT_LOGGING_RULES="kwin_*.debug=true" to /etc/environment, reboot, reproduce the problem and upload the output of > journalctl --boot 0 | grep kwin_wayland_drm (or --boot -1" if you have to reboot afterwards) Created attachment 150244 [details] output of journalctl --boot 0 | grep kwin_wayland_drm Yeah, I think the >Atomic test for (0) failed! Invalid argument is the main culprit here, I hope... Not sure what's going on there - it's failing to disable the output, not enable it... Can you execute > echo 0x1FF | sudo tee /sys/module/drm/parameters/debug to enable debug logging, and then > sudo dmesg -w > dmesg.log (leave that running), reproduce the problem and upload the generated file? Created attachment 150274 [details] dmesg output with drm debugging > So I started the logging > turned off dpms > closed the lid to put the system to sleep > resumed from suspend by opening the lid > SSH'd to my laptop from another computer > killed kwin with "sudo pkill -9 kwin" A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/2599 I think I see what is going on. After suspend, the driver appears to enable the display again behind KWin's back and KWin doesn't handle that situation correctly. Can you test the merge request and check if that fixes the problem? The merge request @ https://invent.kde.org/plasma/kwin/-/merge_requests/2599 did indeed fix the issue for me. Can you check if https://invent.kde.org/plasma/kwin/-/merge_requests/2602 works as well? That would be abit less risky to backport Btw, the bug report will be closed automatically once a commit is merged that fixes it, there's no need to change the status yourself Oh, ok. Anyways, https://invent.kde.org/plasma/kwin/-/merge_requests/2602 does not work/improve anything, screen stays black and keyboard is unresponsive like on the "stock" build Sorry, there was one bug left in it. Can you re-test? Sadly, it's the same Can you do one more test? If this doesn't work then maybe I misjudged where the bug came from This time it works! Git commit 0d302d5c66924ea061db5cf8059887911f7c8831 by Xaver Hugl. Committed on 11/07/2022 at 14:31. Pushed by zamundaaa into branch 'master'. backends/drm: also check for properties in DrmPipeline::needsModeset Otherwise we may be missing situations where a modeset is needed M +14 -0 src/backends/drm/drm_pipeline.cpp https://invent.kde.org/plasma/kwin/commit/0d302d5c66924ea061db5cf8059887911f7c8831 Git commit d0634166267c6ee02b4a4caeaa945e07302e222f by Xaver Hugl. Committed on 11/07/2022 at 18:17. Pushed by zamundaaa into branch 'Plasma/5.25'. backends/drm: also check for properties in DrmPipeline::needsModeset Otherwise we may be missing situations where a modeset is needed (cherry picked from commit 0d302d5c66924ea061db5cf8059887911f7c8831) M +14 -0 src/backends/drm/drm_pipeline.cpp https://invent.kde.org/plasma/kwin/commit/d0634166267c6ee02b4a4caeaa945e07302e222f |