Closed AkinoKaede closed 12 months ago
In my view, I think multi-user.target
should be reached after TLP started. But TLP will be started after multi-user.target
currently .
Hi. Works as designed. tlp.service
should run as late as possible in the boot process, hence the After=multi-user.target
.
Generally I require complete outputs as described in the issue template. Provide them via https://gist.github.com/ please.
Hi. Works as designed.
tlp.service
should run as late as possible in the boot process, hence theAfter=multi-user.target
.
- Does this happen during boot or only when you start the service manually?
- What exactly is meant by stucks: does the command hang/not complete or does the system freeze?
Generally I require complete outputs as described in the issue template. Provide them via https://gist.github.com/ please.
Thanks, the issues is solved.
Both, this is because the system hangs before reach the multi-user.target
, so TLP can not be started. This is expected behavior for TLP. And this is caused by other programs, so there is no need to debug TLP。
I see. Thanks for the feedback.
When I exec
systemctl start tlp
to start tlp, it will be stucks.multi-user.target
was not reached which caused by udev stucks.I deleted
multi-user.target
inAfter
from systemd file, it was fixed.So should TLP run after multi-user.target?
I had a similar problem with other software. EmixamPP/linux-enable-ir-emitter#101