Compiled and installed on Arch-based (Garuda Dragonized) with systemd - spontaneous shutdown

[shayaknyc]

I know this repo is a bit old, which is totally fine. I have an old Lenovo Yoga 13 (20175 model) that's quite old. I decided to revive this old laptop by installing Garuda Dragonized (arch-based) and it's been working great. That said, there's very little in the way of cpu sensor info, and NO fan control at all. Happily discovered this repo with some fancy google fu, and managed to adapt the compile and install instructions.

Running sudo ./yoga_fan seemed to work, and there was no output to the console. Running ps aux|grep yoga showed it was running. So, manually copied the binary to /usr/bin/yoga_fan and copied yoga_fan.service to /etc/systemd/system and ran the appropriate Enable and Start commands with systemctl.

Shortly after rebooting and confirming the service was running at boot. I ran sensors in the terminal, and now see the two CPU Core temps displayed (prior to yoga_fan, the sensors didn't show cpu temps for some reason). However, after about 15 mins or so of the comp running, it would go into an immediate shutdown (not a crash) - where it would close down all the running programs, and then I'd see the shutdown animation and the computer would poweroff. Any ideas why this is happening? I can confirm that the 2 cpu cores' reported temp was only at around 58°C when the shutdown occurred.

[senior-sigan]

@shayaknyc Hello.
I'm sorry you experienced this problem with rebooting. Unfortunately, I'm not using Lenovo and don't have one. So I cannot debug the error.
I can remember I had something like this while developing the app. The problem was a wrong register number here:

lenovo-yoga-fan-control/main.cpp

Line 14 in 2f272c3

#define READ_EC 0x80

I don't know how to help you :( . Try to dig into DMESG or another logging system on your Linux distro. Probably, You will find some clues.

If you find any solution, please, write me about it so we can update the code.

[shayaknyc]

Hmmm, thanks for the tip. I'll take a look and see. I've had to, since, remove it from systemd, and have been somewhat reticent to install it as I'm no software engineer and not really sure where to begin. Your tip to look through dmesg and see if I should update the READ_EC register address sounds good, and I'll take a look as soon as I have a chance. That said, any string of text I should use to help narrow down what I'm looking for in the dmesg output?