origamisith
New Member
Hello everyone,
I was trying to install Arch dual booted with Windows on my LG Gram 17 2020 laptop. Everything worked as expected, except that shutting down, rebooting or halting would result in an infinite hang on a blank screen. You can read the saga (including logs and such) here. Notably, another user had the same issue. Out of desperation, I tried a few different operating systems, and found that only operating systems that used Linux kernel 5.4 or earlier would shut down properly (such as Linux Mint 20, Arch February release, and Fedora 31). Obviously, I would like to be able to use the most current Linux kernel without having to hold down the power button whenever I reboot (which also messes up the system clock and some bios settings). Given that the most popular distro, Ubuntu, is currently on 5.4, and may use 5.5 next, scores of Gram 17 Linux users may end up with the same problem later this year (unless it is only I and another unlucky user cursed with a Linux-unfriendly laptop). I have little idea where to start, whether some convenient kernel parameter or bios setting will fix all my problems, or whether a major patch needs to exist specifically for my device. I would appreciate any help I can get.
I was trying to install Arch dual booted with Windows on my LG Gram 17 2020 laptop. Everything worked as expected, except that shutting down, rebooting or halting would result in an infinite hang on a blank screen. You can read the saga (including logs and such) here. Notably, another user had the same issue. Out of desperation, I tried a few different operating systems, and found that only operating systems that used Linux kernel 5.4 or earlier would shut down properly (such as Linux Mint 20, Arch February release, and Fedora 31). Obviously, I would like to be able to use the most current Linux kernel without having to hold down the power button whenever I reboot (which also messes up the system clock and some bios settings). Given that the most popular distro, Ubuntu, is currently on 5.4, and may use 5.5 next, scores of Gram 17 Linux users may end up with the same problem later this year (unless it is only I and another unlucky user cursed with a Linux-unfriendly laptop). I have little idea where to start, whether some convenient kernel parameter or bios setting will fix all my problems, or whether a major patch needs to exist specifically for my device. I would appreciate any help I can get.