LG Gram 17 2020 Won't Shut Down on Kernel 5.5+

origamisith

New Member
Credits
125
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.
 


origamisith

New Member
Credits
125
Did this nommconf trick work for you? I'm scared to install fedora on my gram because of this.
It did not :(
If you want to help find out the cause of the problem, you can try bisecting different releases of the kernel to find exactly which patch breaks things. In the Arch forum I linked, someone explains how to it on Arch, but I am getting errors in the build process. If someone else can build and test kernel versions on their LG Gram 2020, that would be great. I'm struggling to find the time right now.
 

tpetersohn

New Member
Credits
91
I turned off suspend/hibernate in gnome energy settings (manjaro 5.7). So far it seems to work ... it did reboot after 40 minutes without hanging.
 

origamisith

New Member
Credits
125
@tpetersohn You are a madlad. How in the world did you discover that. It worked for me, installing the latest Arch release. I still need to find which exact kernel release necessitates that BIOS tweak, but for now we have a fix.
 

wizardfromoz

Super Moderator
Staff member
Gold Supporter
Credits
15,812
Legend folks :)

Love it when they solve their own probs, sort of makes us redundant, but I can live with that - more time for me :cool:

Enjoy your Linux

Wiz
 

wizardfromoz

Super Moderator
Staff member
Gold Supporter
Credits
15,812
BTW @studesom - you might want to try the above as well?

If you need help, swing around to here.

Cheers

Wiz
 

tpetersohn

New Member
Credits
91
ehm I have to add something ... this time I turned on everything in system agent except for ITBT root port and iTBT PCIe on Extra Segment ... because I still had an error or two in dmesg mmconfig something and something else i cant remember. Now all errors are gone. I mean really ALL errors ;-)
 

jglen490

Well-Known Member
Credits
4,106

jglen490

Well-Known Member
Credits
4,106
Glad that you have a really out of the blue fix for this? So just out of curiosity, in your UEFI settings what SATA boot parameter is set? AHCI or something else?
 

May Ismyauntie

New Member
Credits
9
I can't stop tweaking the bios :) Set "Enable the iTBT PCIe on Extra Segment" inside the TCSS xHCI thing to ENABLE and that finally fixes the hang problem !!!
TPetersohn,

Good afternoon. I have struggled to find this setting in BIOS having searched through it.

May I cordially request added (or maximal, preferrably) specific info on where this setting is located?

Thank you.

Edit: Do you have BIOS is Phoenix version C2ZE0131 in your LG Gram 17? An update C2ZE0160 was released recently. Superficially, it looks cosmetically the same as C2ZE0131 when I tab through the two BIOS menus side-by-side.
 
$100 Digital Ocean Credit
Get a free VM to test out Linux!

Staff online

Members online


Latest posts

Top