From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from atuin.qyliss.net (localhost [IPv6:::1]) by atuin.qyliss.net (Postfix) with ESMTP id E4114B01B; Fri, 26 Jun 2026 19:09:41 +0000 (UTC) Received: by atuin.qyliss.net (Postfix, from userid 993) id 0B212B013; Fri, 26 Jun 2026 19:09:40 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on atuin.qyliss.net X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DMARC_PASS,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H5, RCVD_IN_MSPIKE_WL,SPF_HELO_PASS autolearn=unavailable autolearn_force=no version=4.0.1 Received: from mail-106100.protonmail.ch (mail-106100.protonmail.ch [79.135.106.100]) by atuin.qyliss.net (Postfix) with ESMTPS id 513D0B011 for ; Fri, 26 Jun 2026 19:09:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=colbyt.com; s=protonmail; t=1782500978; x=1782760178; bh=vqA6l7oqu5dvINAwaupIXEoAvHs8iSxvjuKjSfsEM10=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=xXk6CwAZ8/Xsa5IXtW1+YMnUlDcig2m4miGoQ1diKB1+dWbUkNfGxrQ6HYnS2WS+f WKEZM/3Hzk3YFhPuPXjclmxe8HAnlaRFXWa21uFQ4vqj1BMIdrhxR35uAKxFbsrI+y BJKdzuILD3t9/SxdH2JlhKCfqitWWCSqXCK+j6HJ5d1dL/oCz+QyKrE+xTSbBULZVf SaCbEZa5dQqx+Eh2/sD6kx0zqM0941mjZY44yEU/VxsvRlksP8HUcmWlQb2KFk9MbI CaVQ14qabouvxHcubF+jcB/TvShlR7aUmqATdyrDX0yoFqPCrdyhSf+xlHZClgKJuJ z7Tmk3FnqyYHw== Date: Fri, 26 Jun 2026 19:09:34 +0000 To: Alyssa Ross From: colby@colbyt.com Subject: Re: [PATCH 5/6] installer: suppress boot console status noise Message-ID: In-Reply-To: <87cxxdfjfy.fsf@alyssa.is> References: <528a34214942d7b316fde5510da03ef91eb9d2cd.1782409229.git.colby@colbyt.com> <87cxxdfjfy.fsf@alyssa.is> Feedback-ID: 70977973:user:proton X-Pm-Message-ID: 72a5175aff183808f07440c211ba9191ed068a0c MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID-Hash: QPD65YKHWIEGNTDZWYKYAJSAW3Q2RXAQ X-Message-ID-Hash: QPD65YKHWIEGNTDZWYKYAJSAW3Q2RXAQ X-MailFrom: colby@colbyt.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-devel.spectrum-os.org-0; header-match-devel.spectrum-os.org-1; header-match-devel.spectrum-os.org-2; header-match-devel.spectrum-os.org-3; header-match-devel.spectrum-os.org-4; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: devel@spectrum-os.org X-Mailman-Version: 3.3.10 Precedence: list List-Id: Patches and low-level development discussion Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: That was just me reading the bugs page and taking a crack at https://pad.la= ssul.us/s/mDfFPvHjA "Make flicker-free boot work more reliably in the installer systemd messages are sometimes displayed in the installer in between Plymou= th exiting and cage starting. Reproduce some of these messages, and figure = out what we need to set to disable them." It seemed to me that was your answer! But I could be wrong, I'm very new h= ere. On Friday, June 26th, 2026 at 7:46 AM, Alyssa Ross wrote: > colbyt writes: >=20 > > The installer can show systemd or udev messages between Plymouth exitin= g > > and cage starting, which breaks the intended flicker-free graphical > > handoff. > > > > Add quiet/systemd/udev kernel parameters to suppress status output and > > stop forcing systemd.journald.forward_to_console in the QEMU runner. > > This keeps the installer VM aligned with the quiet graphical boot path. > > > > Signed-off-by: colbyt > > --- > > release/installer/configuration.nix | 9 ++++++++- > > release/installer/run-vm.nix | 5 +---- > > 2 files changed, 9 insertions(+), 5 deletions(-) > > > > diff --git a/release/installer/configuration.nix b/release/installer/co= nfiguration.nix > > index 3f9ef24..daaf5b7 100644 > > --- a/release/installer/configuration.nix > > +++ b/release/installer/configuration.nix > > @@ -11,7 +11,14 @@ in > > imports =3D [ (modulesPath + "/profiles/all-hardware.nix") ]; > > =20 > > boot.consoleLogLevel =3D lib.mkDefault 2; > > - boot.kernelParams =3D [ "udev.log_priority=3D5" ]; > > + boot.kernelParams =3D [ > > + "quiet" > > + "loglevel=3D3" > > + "systemd.show_status=3Dfalse" > > + "rd.systemd.show_status=3Dfalse" > > + "udev.log_level=3D3" > > + "rd.udev.log_level=3D3" > > + ]; >=20 > Why 3 in particular? Experimentation? Inspiration from some other > distribution? >=20 > > boot.initrd.verbose =3D false; > > =20 > > boot.kernelPackages =3D pkgs.linuxPackages_latest; > > diff --git a/release/installer/run-vm.nix b/release/installer/run-vm.ni= x > > index b9907f7..6639c8b 100644 > > --- a/release/installer/run-vm.nix > > +++ b/release/installer/run-vm.nix > > @@ -40,8 +40,5 @@ writeShellScript "run-spectrum-installer-vm.sh" '' > > -drive file=3D/proc/self/fd/3,format=3Draw,if=3Dvirtio \ > > -kernel ${installer.kernel} \ > > -initrd ${installer.initramfs} \ > > - -append ${escapeShellArg (toString [ > > - installer.kernelParams > > - "systemd.journald.forward_to_console" > > - ])} > > + -append ${escapeShellArg installer.kernelParams} > > '') (_: {}) >=20 > The divergence here was intentional, since in development it's very > useful to be able to see logs on the serial console, and it should have > a minimal impact on anything else. Did you see this causing problems > with flicker-free boot or something? >