Core with slot C enabled
Follow the four steps above. Maintenance and confirmation are automatic. Later R1 signed updates use this same process.
BRIMSTONE CORE R1 · 1.0.0-rc.2 · 4 NOVEMBER 2026
Update Core.
Keep your collection.
The R1 release candidate brings together the current listening, metadata and Meridian fixes. Install the signed update through Core’s existing update screen. Your music and library stay where they are.
Release candidate · planned 1.0.0 launch: 14 November 2026. Final release remains subject to the remaining checks.
Already have Core? Use the update archive, not the fresh installer. A fresh installation erases the system disk you select; an application update preserves persistent DATA, media, accounts and metadata.
FOR CORE WITH THE SLOT-C UPDATER INSTALLED
One update.
Core handles the rest.
The new R1 installer includes the trusted slot-C updater. Existing installations may have it from a separate support setup. The updater decides the route; you do not need to choose a boot slot yourself.
Finish what is running
Finish playback, ripping, recording, imports and downloads. Leave Core connected to power.
Upload and activate
Open Settings → Updates & Recovery. Upload the complete signed
.tar.gzarchive without extracting it. Check the verified version is 1.0.0-rc.2, then choose Activate.Choose Restart Core
Core makes its database backup, boots maintenance slot C, updates the inactive system slot and boots back into the new Core. Allow both restarts to finish.
Check your music
Refresh the Core page. Check the installed version, open an album and try your usual speaker. A healthy exact-version boot is confirmed automatically. Your previous system slot remains available for rollback.
Let Core select C. Do not manually boot Recovery C to upload or run a patch. The signed package and backup must be queued by the running Core first.
WHICH CORE ARE YOU UPDATING?
The right route for your installation.
A version number alone does not tell you which privileged updater has been installed. An ordinary application archive cannot silently replace that trusted component.
Earlier Core with the A/B web updater
Upload the same signed update in Settings and follow the route your installed helper offers. It stages the inactive A/B application. After restarting and checking playback, use Confirm update if shown.
The application patch preserves that earlier helper; it does not add C automatically. Contact support for the separate one-time C setup.
Rev29 / Rev48 without the web helper
Use the administrator-console instructions below for the first update. A modified or unknown installation must be reviewed rather than forced through.
First-update instructions ↗Core running inside LXC
A container has no independent A/B/C boot slots. Use its managed application update or administrator-supported native-service update. Do not run the disk installer or A/B patch command inside LXC.
WHAT R1 1.0.0-rc.2 INCLUDES
The current Core, brought together.
Playback and podcasts
Core-first album selection, improved lyric timing and DruidCast podcast queues through supported native Meridian receivers. MS200 listening has been confirmed; other physical models retain their individual acceptance requirements.
Your metadata stays
Enhanced album and artist information, artwork, credits, booklets and manual corrections remain part of the current baseline. Updating does not rebuild your collection from scratch.
A clear release identity
Core, the signed update and the new installer use 1.0.0-rc.2. 1.0.0 is reserved for the planned R1 launch.
Administrator console: first update for supported Rev29 / Rev48 systems
Download the update and its matching checksum into a folder on persistent DATA. Verify the checksum before extracting or running it. These commands are for a normally booted full Core A/B system, not LXC or manually selected recovery C.
sha256sum -c Brimstone-Core-R1-1.0.0-rc.2-Update-20261104.tar.gz.sha256
mkdir r1-1.0.0-rc.2-update
tar -xzf Brimstone-Core-R1-1.0.0-rc.2-Update-20261104.tar.gz -C r1-1.0.0-rc.2-update
cd r1-1.0.0-rc.2-update
sudo python3 apply_patch.py --check
sudo python3 apply_patch.py --apply --activate
sudo rebootAfter a healthy boot, return to the same directory on DATA and run sudo python3 apply_patch.py --confirm. This route adds the earlier trusted A/B web helper. Separate C setup is still required.
If validation refuses the signature, baseline, layout or database, stop and send the error to support. Do not change the checks or select another disk.
If an update does not start
Refresh the update status and read the saved result. Do not repeatedly upload or restart while an operation is in progress. The new C updater confirms the exact healthy release or selects the previous system slot if the new Core fails its startup check.
Use Roll back application in the update screen if needed. Application rollback retains current DATA; it does not rewind your library or media.
Fresh installation
The new 1.0.0-rc.2 ISO is built with the C updater and has passed image-integrity checks. Fresh BIOS/UEFI boot and installation qualification is still pending, so its download is held. The existing tested installer remains on the installation page.
Fresh-install guidance ↗Verify your download.
R1 1.0.0-rc.2 update · 6,869,999 bytes · signed application archive
a742ecbb1b48508c43320626285c311a7d3f161137fb8c8eb341429275f6c9c0