[Desktop/General] better control early Systemd boot level + fix console setup

and don't disable console completely: this caused issues like not
setting up keyboard layout correctly, for instance.
This commit is contained in:
Antoine Viallon 2024-02-20 00:44:17 +01:00
parent 05a54f03b5
commit 506bd4e1f0
Signed by: aviallon
GPG key ID: 186FC35EDEB25716

View file

@ -78,14 +78,15 @@ in {
preempt = "full"; preempt = "full";
"usbhid.mousepoll" = 1; # 1ms latency for mouse "usbhid.mousepoll" = 1; # 1ms latency for mouse
"usbhid.kbpoll" = 4; # 4ms latency for kb "usbhid.kbpoll" = 4; # 4ms latency for kb
"systemd.log_level" = config.boot.initrd.systemd.managerEnvironment.SYSTEMD_LOG_LEVEL;
}; };
boot.initrd.verbose = generalCfg.debug; boot.initrd.verbose = generalCfg.debug;
boot.consoleLogLevel = mkIf (!generalCfg.debug) 1; boot.consoleLogLevel = mkIf (!generalCfg.debug) 1;
boot.initrd.systemd.managerEnvironment = { boot.initrd.systemd.managerEnvironment = {
SYSTEMD_LOG_LEVEL = toString config.boot.consoleLogLevel; SYSTEMD_LOG_LEVEL = if generalCfg.debug then toString config.boot.consoleLogLevel else "crit";
}; };
console.enable = mkDefault false; # Completly disable console by default #console.enable = mkDefault false; # Completly disable console by default
security.polkit.enable = true; # Better interactive privilege prompts security.polkit.enable = true; # Better interactive privilege prompts
# Enable running X11 apps on Wayland # Enable running X11 apps on Wayland