redbear-mini: drop duplicate 30_cpufreqd (double-run + buries login prompt)

cpufreqd was started twice: 15_cpufreqd (redbear-device-services.toml, early)
and a redundant 30_cpufreqd here (at getty time). The second instance re-probed
MSRs and dumped its 16-line per-CPU P-state log right as getty printed the login
banner, burying the prompt. Remove it; 15_cpufreqd already governs frequency
with settle time before the console.
This commit is contained in:
2026-07-25 16:15:52 +09:00
parent c3f8c89856
commit 98ac1af883
+5 -11
View File
@@ -509,17 +509,11 @@ args = ["-A", "2", "-K", "us"]
type = "oneshot_async"
"""
[[files]]
path = "/etc/init.d/30_cpufreqd.service"
data = """
[unit]
description = "CPU frequency governor (throttles CPU on bare metal to prevent overheating)"
requires_weak = ["00_base.target"]
[service]
cmd = "cpufreqd"
type = "oneshot_async"
"""
# NOTE: cpufreqd is already started earlier by 15_cpufreqd.service (from
# redbear-device-services.toml). A second 30_cpufreqd instance used to live here
# and (a) ran cpufreqd twice — double MSR probing + a duplicate 16-line P-state
# dump — and (b) fired at getty time, burying the login banner/prompt under its
# output. Removed; the 15_ instance covers it with settle time before the prompt.
[[files]]
path = "/etc/init.d/30_console.service"