![]() ![]() You might even want to try suspend again on the latest version of 5.4, in case they finally ported the fix for the issue to that version (if there is one), if you haven’t already. I would guess the OEM one would be available at least. If your Mint uses 4.15 by default, it sounds like it is a Bionic-based release, so I don’t know what the repo holds in that case. I just installed 5.13 OEM into my Dell G3 laptop, and I am about to do it on my Dell XPS 13 also (which actually came with the Ubuntu OEM kernel from the factory). The Ubuntu repo for 20.04 has the 5.8 kernel (HWE stack), 5.11 kernel (HWE-Edge stack), and as I discovered just today, the 5.13 kernel (OEM stack). Have you considered a newer kernel, to see if whatever issue is in 5.4 has been fixed? ![]() IOW a long standing issue on this device with the 5.4 xxx kernel, which is why I prefer the 4.15 xxx. Masked Hiber/standby as a precaution to clicking it by accident. ![]() I’m just gonna stick with 5.4.0.80 and wait for the next 4.15.0 xxx.xxx kernel to be released. – debian/patches/CVE-2021-33910.patch: do not use strdupa() on a path in src/basic/unit-name.c. * SECURITY UPDATE: denial of service via stack exhaustion – debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEWĬommand in src/libsystemd-network/sd-dhcp-client.c. * SECURITY UPDATE: DoS via DHCP FORCERENEW Well after reading this article over on Bleeping Computer I re-checked the Mint update manager and lo and behold, patches were waiting for systemd and initramfs (which were not there 10 minutes previous) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |