From 98ac1af883a7362b94eb2d03c16776e0a8f3e55d Mon Sep 17 00:00:00 2001 From: vasilito Date: Sat, 25 Jul 2026 16:15:52 +0900 Subject: [PATCH] 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. --- config/redbear-mini.toml | 16 +++++----------- 1 file changed, 5 insertions(+), 11 deletions(-) diff --git a/config/redbear-mini.toml b/config/redbear-mini.toml index 578dd800a1..9fb4c978ee 100644 --- a/config/redbear-mini.toml +++ b/config/redbear-mini.toml @@ -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"