Installation Requirements
Hardware and software prerequisites for installing to an actual system (bare metal). What you need before installing Forest OS: supported hardware, firmware settings, install media, and VM host prerequisites. Check everything here first — most install failures trace back to one of these rows.
If you only want to try in a VM, see the virtualization docs. This page covers real hardware installs.
Quick Checklist
- 64-bit (x86_64) or 32-bit (i686) PC with CPUID support
- 256MB+ RAM (512MB+ recommended, 1GB+ with GUI)
- 512MB+ disk (2GB+ recommended, 8GB comfortable)
- 2GB+ USB stick for installer (8GB+ for persistent live USB)
- BIOS/CSM or UEFI x64 firmware, Secure Boot OFF
- Second machine / working OS to download ISO and flash USB
- Backup of target disk completed
Install guides: Install on a VM · Install on Real Hardware · USB Persistence · Installation Overview
Contents
- Quick checklist
- Supported hardware
- CPU details
- RAM details
- Disk / storage details
- Firmware setup
- Install media
- Needed tools / software
- VM host prerequisites
- Networking
- Backup reminder
- Pre-install checklist
Supported hardware
| What | Minimum | Recommended |
|---|---|---|
| CPU | x86 or x86_64, 1 vCPU (qemu64 / qemu32) | 2 vCPU + KVM (-enable-kvm -cpu host) on VMs |
| RAM | 256 MiB | 512 MiB – 1024 MiB (full userspace + X11) |
| Target disk | 512 MiB | 2 GiB+ (ext2/ext4 root + FAT ESP if UEFI) |
| Display | Bochs BGA (-vga std), VESA VBE, or UEFI GOP | Same; Cirrus as fallback; VBoxVGA on VirtualBox, default SVGA on VMware |
| Input | PS/2 keyboard | PS/2 keyboard + mouse, or USB keyboard / USB tablet |
| Storage controller | IDE/ATA | AHCI (SATA set to AHCI, not RAID/Optane/IDE) |
| Network (optional) | None — install works offline | Intel PRO/1000 (e1000) or AMD PCNet; VirtIO-net only if ENABLE_VIRTIO_NET is built in |
ARM/AArch64/RISC-V guests boot with -kernel directly (no ForeB) and are serial-only. This page covers x86/x86_64 installs.
CPU details
| Tier | Requirement |
|---|---|
| Minimum | i686 (Pentium Pro / Athlon+) with CPUID |
| Recommended | x86_64 (any 64-bit Intel / AMD, 1GHz+) |
| Comfortable | Dual-core x86_64, 2GHz+ |
CPUIDinstruction is required. 486 and early 586 without CPUID will not boot.- PAE is not strictly required for base install, but recommended for 32-bit systems with 4GB+ RAM.
- ARM, RISC-V, PPC, and other non-x86 CPUs are not supported by this installer.
Check on Linux:
grep -o 'cpuid\|lm' /proc/cpuinfo | sort -u
# lm flag = 64-bit (x86_64) capable
RAM details
| Install type | Minimum | Recommended |
|---|---|---|
| Text / console only | 256MB | 512MB+ |
| With GUI / desktop | 512MB | 1GB+ |
| Live ISO boot | 512MB | 1GB+ |
- Installer itself needs ~256MB to unpack and run.
- Less than 256MB will likely panic, hang, or OOM during install.
- Swap is optional but recommended if RAM < 1GB (512MB–1GB swap partition).
Disk / storage details
| Tier | Size | Notes |
|---|---|---|
| Minimum | 512MB | Base console system only, no extras, tight |
| Recommended | 2GB+ | Base + tools + logs + updates |
| Comfortable | 8GB+ | Desktop / GUI + apps + user data |
Supported:
- Internal SATA / PATA / IDE HDD and SSD
- NVMe (if visible as
/dev/nvme*to installer) - USB HDD / SSD as install target (slower, but works)
- VirtIO / SCSI virtual disks (bare-metal pass-through / KVM hosts)
Not recommended as install target:
- SD cards / raw flash without wear-leveling (works but wears fast)
- The same USB stick you booted the installer from
Partitioning checklist:
- Target disk identified correctly (
lsblk/fdisk -l) - At least one partition for root (
/) - Optional: separate
/home - Optional: swap if RAM < 1GB
- No valuable data left on target disk
Firmware setup
Forest OS boots both ways from the same hybrid ISO:
| Firmware | Support |
|---|---|
| Legacy BIOS | Yes |
| CSM (Legacy mode on UEFI) | Yes |
| UEFI x64 | Yes |
| UEFI IA32 (32-bit) | No |
| Secure Boot | Must be OFF |
| Path | What the firmware loads | Requirements |
|---|---|---|
| BIOS / CSM / Legacy | ForeB stage1 (MBR + 55AA) → stage2 → stage3 → kernel | CSM/Legacy boot enabled, or an old BIOS-only board |
| UEFI | \EFI\BOOT\BOOTX64.EFI from the ESP | 64-bit UEFI with Secure Boot off |
- Disable Secure Boot. Forest OS ships an unsigned
BOOTX64.EFI; with Secure Boot on, firmware refuses to load it. - Set SATA to AHCI (not RAID/Optane/IDE) if the option exists. AHCI is the tested path.
- Fast Boot / Fast Startup: disable if the USB stick or ISO is not detected; it skips USB enumeration.
- Boot order: optical/USB first for install, internal disk first afterwards. On UEFI you may see two stick entries (
UEFI: <stick>andUSB: <stick>) — pick the one matching the path you want. - Firmware set to BIOS/CSM or UEFI x64 mode; boot menu key known (
F12/F8/Esc/Del— varies by vendor).
Checklist:
- Firmware set to BIOS/CSM or UEFI x64 mode
- Secure Boot DISABLED
- Fast Boot / Rapid Start DISABLED (if it skips USB boot)
- Boot order set to USB first, or boot menu key known
- SATA mode set to AHCI (not RAID / Optane) unless you have drivers for it
Install media
| Image | What it is | Use it for |
|---|---|---|
forebo.iso | Hybrid BIOS + UEFI ISO | Default — VM installs and USB sticks |
forebo.img | Raw BIOS disk image (~10 MiB, MBR layout) | Boot as a hard disk (-drive), or dd straight to USB/disk |
esp.img | FAT EFI System Partition (~48 MiB) | UEFI path only (/EFI/BOOT/BOOTX64.EFI, /forebo/) |
| Use case | Size |
|---|---|
| Installer only | 2GB+ |
| Live + persistent storage | 8GB+ |
cd forest/fern
./conf.sh --defconfig && ./conf.sh --generate
make all
ls -lh ../foreboots/build/ # forebo.iso / forebo.img / esp.img
- A USB stick ≥ 256 MiB for the ISO itself (any USB 2.0/3.0 stick works; all data on it is erased). For installer use 2GB+; for live + persistent storage 8GB+. USB 2.0 works; USB 3.0+ recommended for speed.
- Write with
ddon Linux (bs=4M oflag=sync+sync), or Rufus in DD mode on Windows — ISO mode extracts files and breaks the ForeB sector layout, so the stick will not boot. DVD/CD also works if ISO fits and drive is bootable, but USB is recommended. - Verify before rebooting: MBR signature
55aaat bytes 510–511, stage2 magic0xFEB1at sector 1, kernel ELF magic (7F 45 4C 46) at the kernel sector. Full checks: Install on a VM. - You need a second machine (or the same one booted into Linux/Windows) to write the USB.
Warning: dd to the wrong device destroys data. Triple-check of= with lsblk before every write.
Needed tools / software
You need a working machine (any OS) to prepare the installer:
| Tool | OS | Notes |
|---|---|---|
dd | Linux / macOS | dd if=*.iso of=/dev/sdX bs=4M status=progress sync — triple-check of= target |
| Rufus | Windows | DD mode recommended |
| balenaEtcher | Linux / Win / macOS | Beginner-friendly, verifies write |
Also needed:
- ISO image downloaded (plus checksum if provided)
- Checksum verified (
sha256sum/certutil/ Etcher verify) - One empty USB stick (see sizes above)
- Keyboard + display attached to target machine (serial/headless only if image documents it)
VM host prerequisites
# QEMU (test, install target, rescue)
sudo apt install qemu-system-x86 qemu-utils ovmf xorriso mtools
# Verify KVM (strongly recommended — install without it is ~10x slower)
ls -la /dev/kvm
sudo usermod -aG kvm $USER # re-login after
# Verify OVMF firmware files (paths vary by distro)
ls /usr/share/edk2/x64/OVMF_CODE.4m.fd /usr/share/edk2/x64/OVMF_VARS.4m.fd
# Debian/Ubuntu alt paths:
ls /usr/share/ovmf/OVMF.fd
ls /usr/share/OVMF/OVMF_CODE.fd
- QEMU needs split CODE + writable VARS pflash drives — copy VARS to a per-VM file, never point both at the same read-only file.
- Keep serial logging on (
-serial stdio) — kernel banners andforinstallerrors land there. - VirtualBox: VBoxVGA display, IDE/SATA disk 2 GiB+, e1000/PCNet NIC. VMware: LSI Logic SCSI or SATA disk 2 GiB+, e1000 NIC, BIOS firmware for MBR installs or UEFI for ESP installs.
Networking
Optional, but recommended.
| Item | Required? |
|---|---|
| Offline install | No — base install works without network |
| Updates / packages | Yes — Ethernet or supported Wi-Fi |
| Ethernet (DHCP) | Recommended — works out of the box in most cases |
| Wi-Fi | Optional — needs supported chip + credentials at hand |
Bring if needed:
- Ethernet cable / LAN access
- Wi-Fi SSID + password
- Proxy URL / static IP details (only if your network needs them)
Backup reminder
Installing WILL WIPE the target disk.
- Full backup of target machine completed
- Backup verified (can list / restore files from it)
- Product keys / licenses / passwords exported
- Installer USB and target disk are different devices
- Unplug other external disks to avoid overwriting the wrong one
When in doubt: lsblk before and after plugging in the USB stick. The device that appears is the stick — never dd to a device you cannot re-identify. See Backup.
Pre-install checklist
- Back up the target disk —
forinstallformats it. Confirm you picked the empty disk, never the installer media (cd0). - Confirm display, keyboard, and network in the live session before installing.
- Keep ~100–200 MiB free on the root after install (
df -h). - Snapshot the VM (QEMU
savevm, VirtualBox/VMware snapshot) right after the first successful boot, before experimenting.
See Also
- Installation Overview — install process at a glance
- Install on a VM — QEMU/VirtualBox/VMware walkthrough
- Install on Real Hardware — USB install, firmware setup, bootloader sectors
- USB Persistence — live vs persistent vs full USB install
- Installer —
forinstall+forupdatereference - Disk Tools —
fdisk,mkfs,mount,fsck - ISO Creation — hybrid ISO / IMG / ESP internals
- BIOS Boot — stage layout, sector map, error catalog
- UEFI Boot — ESP layout,
forebo.cfg, chainloading