Last month I got a new EVO 15 AMD Ryzen 7 8845HS with Kubuntu installed on it. I connected it to an external monitor via HDMI. Initially this worked ok, but now if I connect the monitor, it crashes the laptop and I have to do a hard shutdown by pressing the power button for approx 8 seconds. The laptop crashes both when the laptop is connected to the monitor before booting, and when it is connected after booting. Note that the laptop seems to work fine when using its own screen and I have not made any major changes to the laptop's configuration. Is anyone else seeing similar issues?
4 Respuestas
Good morning,
Yes, I have suggested to test 6.11 instead of 6.14, however that was prior to mentioning,in the thread, the DRM patch based on 6.17 Linux kernels
Until the problem's fixed, the only way for the laptop to not crash under recent AMDGPU versions in the 6.1x kernels is to not use the external monitor
We will try releasing a workaround, that is, the 6.17 kernel with the patch, as soon as possible when we confirm 100% that it doesn't crash with said setups (so, monitor connected to the laptop)
Apologies for all the inconveniences
Kind regards,
Hi Samanta, in the thread you linked to above, you suggest using a previous kernel (6.11 instead of 6.14). I tried this and the problem remains, ie the laptop screen still goes blank and there seems to be no way to recover the session, and a hard shutdown is necessary.
Ok, thanks for the response. I guess I'll stick with the laptop's monitor for now, and hope that a solution is on the horizon.
Good afternoon,
TLDR: Refer to this, it's a known issue: https://slimbook.com/en/forum/questions-and-answers-from-the-slimbook-user-community-1/question/problemas-de-apagado-y-congelado-con-un-slimbook-evo-14-nuevo-10833
The current AMDGPU driver in recent kernels seems to be crashing with that setup (external monitor with laptop), there's a current patch for the 6.17 kernel, we have to do further tests with the kernel to verify that it doesn't crash with said setup
https://gitlab.freedesktop.org/drm/amd/-/issues/4129 link to the issue
Regards,