Players boot quietly, and the installer now overwrites config.txt

From Anthias 2026.05.1, a Raspberry Pi boots to the Anthias splash without a rainbow screen, scrolling text or a login prompt first, and an x86 player skips the scrolling text too. If you've added your own lines to config.txt on a Raspberry Pi, such as an overlay for a HAT or a forced display mode, copy them somewhere before you run the installer to upgrade, because it now rewrites that file.

A player in a lobby shouldn't show a rainbow screen, scrolling kernel messages or a login prompt before the content starts. The installer sets a Raspberry Pi up for a quiet boot: the firmware's rainbow splash is off, the kernel prints nothing to the screen, and there's no login prompt on the first console. On x86, the installer adds the quiet and splash options to GRUB, so the Anthias splash shows instead of kernel text.

config.txt and cmdline.txt

On a Raspberry Pi, the installer now writes config.txt and cmdline.txt in the boot partition (/boot/firmware on Raspberry Pi OS Bookworm and Trixie) from a template, every time it runs. Before, it changed individual lines in config.txt and left the rest alone.

• Lines you added to config.txt are replaced. A custom dtoverlay, hdmi_group or overscan line won't survive the next run.
• The template sets disable_overscan=1, display_auto_detect=1 and dtparam=audio=on. On a Raspberry Pi 5 it also sets dtoverlay=vc4-kms-v3d,cma-512, which 4K HEVC playback needs.
• cmdline.txt is built from the cmdline.txt.orig copy the installer saved on its first run. Only the root= entry and any cfg80211. options (the Wi-Fi country setting from raspi-config) are kept from it. Other options in that file are dropped.

If this affects you: if you've added your own lines to config.txt or cmdline.txt.orig, such as an overlay for a HAT or a forced display mode, copy them somewhere before you run install.sh to upgrade. Once it runs, they're gone, and adding them back by hand only lasts until the next time it runs.