We see that kind of issue frequently and in the majority of cases it is not a Linux fault, but manufacturer firmware. It is such a frequent issue I wrote an ar

We see that kind of issue frequently and in the majority of cases it is not a Linux fault, but manufacturer firmware. It is such a frequent issue I wrote an article 10 years ago that is still extremely relevant with simple instructions to enable a kernel work-around [0]. Specifically the problem is the ACPI DSDT (Differentiated System Description Table) - which is actually byte-code installed by the device manufacturer (but executed by the host OS) that handles device power states and enablement. The problem is almost always DSDT methods are written to conditionally configure system hardware optimally ONLY when the host OS is a version of Windows as declared by the host OS's ACPI OSI (Operating System Identification). When Linux boots only a minimal configuration is applied which very often has never been tested and thus devices fail to work reliably, especially for suspend/resume, in interesting ways. Fortunately, Linux has a WORKAROUND that allows passing a 'fake' OSI on the kernel command-line in the form: acpi_osi=! "acpi_osi=Windows XXXX" The first instance (=!) clears all built-in kernel OSIs to avoid confusion. The second string sets the 'best' and only OSI value which has been found in the DSDT of that PC. That can be discovered from a Linux boot using: sudo strings /sys/firmware/acpi/tables/DSDT | grep -i 'windows ' | sort E.g: on my Lenovo E495 (AMD Ryzen 7 3700U) I have: Microsoft Windows NT Windows 2001 Windows 2001.1 Windows 2001 SP1 Windows 2001 SP2 Windows 2001 SP3 Windows 2006 Windows 2006 SP1 Windows 2009 Windows 2009 Windows 2012 Windows 2013 Windows 2015 Windows 2015 Windows 2016 So, on the basis that "Windows 2016" is the 'latest' and likely the OSI expected to enable all features optimally I use that. On Debian/Ubuntu I therefore have: /etc/default/grub.d/local.cfg GRUB_CMDLINE_LINUX="acpi_osi=! \"acpi_osi=Windows 2016\" " Notice the escaped quote-marks inside the shell string since the argument contains a space. (some folks might prefer to edit the package-shipped /etc/default/grub but I prefer to leave that virgin to avoid package-upgrade prompts when that file is replaced.) After: sudo update-grub /boot/grub/grub.cfg will have the acpi_osi= entries added to all the "linux ..." command lines E.g: $ grep acpi_osi= /boot/grub/grub.cfg linux /vmlinuz-5.12.0-rc5+ root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" systemd.unified_cgroup_hierarchy=1 nosplash [0] https://iam.tj/prototype/enhancements/Windows-acpi_osi.html https://iam.tj/prototype/enhancements/Windows-acpi_osi.html