Download the release candidate
Coming soon
This is a free personal-use edition under our own licence (all rights reserved; commercial use needs a separate licence), provided as is, without warranty or liability. It includes several experimental features that may not meet your expectations: voice, camera gestures, the local model, connectors, knowledge work, extensions, cloud drives, the wallet and autofill are built but switched off in this image, and the audit log and root helper run in a lower-assurance mode. Nothing has been booted on real hardware yet. Use a spare laptop or a stick you can wipe. See the terms.
Intel and AMD 64-bit laptops and desktops, and Intel Macs, can run it. Apple Silicon Macs (M1 and later) cannot boot it. It is not an ARM image.
Release
Checking for a release
Coming soon
There is no downloadable file yet, so there is nothing to fetch. Version, date, size and SHA-256 appear here when a release is published.
Email updates are not offered. Check back on this page.
Public distribution is held back until the licence wording has been reviewed. Until then, builds are for testers only. BritOS carries our own branding and logo, with no Fedora marks. The third-party licence notices and source offer are in NOTICES.txt (the full package list ships inside each image, Settings, About, Open-source notices).
Check your download
Pick the file you downloaded and this page works out its SHA-256 on your device. Nothing is uploaded. A large image takes a while; the mark turns once for every twelfth of the file.
Filled in from the release card when the file name matches. Otherwise paste it from the release card or SHA256SUMS.
System requirements
- CPU: 64-bit x86_64, about a 9th-generation Intel Core i5 or equivalent, or better.
- Memory: 4 GB RAM minimum, 8 GB recommended. On 4 GB it runs a smaller assistant and uses your own cloud key for hard questions. The local model scales with the hardware: better and faster with 8 GB, and more so with 16 GB and above or a capable GPU. Not yet tested on real 4 GB hardware.
- Boot: UEFI.
- USB stick: 32 GB or larger for the disk image (the exact size per release is listed in the release card above); USB 3 is much faster.
- Disk for an install: about 20 GB free, and the image’s root filesystem needs at least 24 GiB, so plan on 24 GB or more.
- Apple Silicon Macs cannot run this x86_64 build.
These are targets, not tested results: nothing has run on real hardware yet.
Which file
- USB disk image (
.img.xz): a full system you boot from the stick. Nothing on the laptop is touched. Needs a 32 GB or larger stick; a USB 3 SSD stick is much faster. Best first try. - Installer ISO: asks which disk to install to and erases nothing until you confirm. It installs; it has no live desktop.
- VM disk (
.qcow2): to try it in a virtual machine first.
Live versus install. The USB disk image is the live option: run it from the stick. The ISO is the install option. Installing wipes the disk you choose, so read the installer screen carefully. There is no dual-boot helper; if you want to keep another system, leave its disk alone and use the USB stick.
Write the USB stick
Everything on the stick is erased. Steps for your system are shown first; all three are listed for anyone with JavaScript off.
Windows
- Verify the file: in PowerShell, in the download folder, run
and compare with the SHA-256 above.Get-FileHash -Algorithm SHA256 .\FILENAME - Use Rufus: choose the file, and when asked pick DD Image mode, not ISO mode. If your Rufus cannot read
.xz, unpack it with 7-Zip first. Or use balenaEtcher: Flash from file, pick the stick, Flash. - Do not use UNetbootin; it often produces sticks that do not boot on modern UEFI.
macOS (Intel Macs as the target; any Mac as the writer)
- Verify the file in Terminal:
and compare with the SHA-256 above.shasum -a 256 FILENAME - Use balenaEtcher: Flash from file, pick the stick, Flash. It reads both
.isoand.img.xz. - An Apple Silicon Mac cannot boot the result.
Linux
- Verify the file:
or check against the list:sha256sum FILENAMEsha256sum -c SHA256SUMS --ignore-missing - Write it with balenaEtcher, Fedora Media Writer (Custom image) or
dd. With dd, double-check the device name, because the wrong one destroys that disk:xzcat FILENAME.img.xz | sudo dd of=/dev/sdX bs=4M status=progress conv=fsync
If the file is in parts
Put every part in one folder and join them in order. Then verify the joined file.
# Windows (Command Prompt)
copy /b NAME.part00 + NAME.part01 NAME
# macOS and Linux
cat NAME.part* > NAME
Boot settings (BIOS and UEFI)
- UEFI boot with legacy or CSM off, and the USB stick first in the boot order (F12, F2, Esc or Del at power-on, depending on the maker).
- Turn Secure Boot off for the release candidate. The image uses Fedora’s signed boot files, so Secure Boot on may work, but that is not confirmed.
- Leave the TPM as it is. Plug in AC power. Turn off Fast Boot, and Fast Startup in Windows.
Try it in a virtual machine first
Use the .qcow2 disk. VirtualBox: convert with qemu-img convert -O vdi, create a Fedora 64-bit VM, tick Enable EFI, 4 GB RAM or more. Hyper-V: convert to VHDX, Generation 2. QEMU with UEFI (OVMF) also works. A VM shows that it boots and that the first run works; it says nothing about your Wi-Fi, sound, camera, battery or graphics.
First boot
You create your own account in Plasma Setup; none is built in. A window then asks for your own AI key. Use a new key with a low spend limit and delete it when you finish testing. Closing that window never blocks the desktop.
If something goes wrong
- Black screen after the logo: hold the power button and boot again. The system keeps the last working image and rolls back after failed boots.
- No login screen: press Ctrl+Alt+F3 for a text console.
- Start over: write the stick again. The USB disk image does not touch the laptop’s disk.
Report a problem
In Konsole, run this, then attach the files and say which step failed, your laptop model, RAM, and whether Secure Boot was on:
journalctl -b --no-pager > ~/boot.log
journalctl --user -b --no-pager > ~/user.log
systemctl --failed --no-pager > ~/failed.txt
systemctl --user --failed --no-pager >> ~/failed.txt
If your key was ever typed into a log, treat it as leaked and delete it at the provider. Contact: hello@getbritos.com TODO owner: confirm this mailbox exists.