4 ms·
Fantastic news. AMD's linux graphics drivers have mostly worked great for me but this has been the one exception that I've hit multiple times.
by dralley 2y ago
Fantastic news. AMD's linux graphics drivers have mostly worked great for me but this has been the one exception that I've hit multiple times.
- juujian 2y agoSame great experience, but I experience similar issues when I disconnect thunderbolt with monitors when my machine is asleep. Laptop though, so very different driver set, no GPU via pci
- jorvi 2y agoYou can probably write a udev rule for the Thunderbolt / USB-C port with either ACTION=="offline", "remove" or "online". "offline" is for when your system turns off or suspends, "online" vice versa, and "remove" is self-explanatory. If you go with "offline", I'd look into hard disconnecting the monitors. This might cause monitor rearrangement (= you'll need to manually assign) or blinking on laptop bootup. Might also stop any charging. But that could be mitigated by checking the "subsystems" attribute. If you go with "online", you probably need run some sort of clean-up / refresh script or rule If you go with "remove", you'll need the same clean-up / refresh script. It'll take some trial-and-error, but it'll be satisfying once it works. Also highly recommended to check the NixOS repositories and official wiki and Arch wiki to see if your laptop or monitors have workarounds for their quirks.
- MegaDeKay 2y agoMy luck has been a little less good. Latest problem I'm having is the driver spamming my logs after waking from sleep with "[drm] scheduler comp_1.0.n is not ready, skipping" after "WARNING: CPU: 12 PID: 11871 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:100 generic_reg_update_ex+0x1d2/0x290 [amdgpu]" https://gitlab.freedesktop.org/drm/amd/-/issues/3911 https://gitlab.freedesktop.org/drm/amd/-/issues/3911