vasilito
6086959b92
This session lands 7 phases from the R11-R22 plan plus 2 deferred landing pads: - R15 (57778e789): ClocksourceQuirkFlags + 3-entry PMTMR blacklist (PIIX4 / ICH4 / ServerWorks LE) - R17 (9e7020bc5): ChipsetQuirkFlags + 11-entry early_qrk[] table (NVIDIA, VIA, AMD K8, ATI, Intel 0x3403/0x3405/0x3406, Intel VGA, Intel Baytrail HPET, Broadcom 4331) - R18 (f0b2b01da): 25-entry storage data (libata 18 + AHCI 3 + PIIX 2 + NVMe 2) - R19 (f0b2b01da): 23-entry network data (RTL8xxx 12 + TIGON3 6 + RTL8169 5) - R20 (f0b2b01da): UsbAudioQuirkFlags + 30-entry USB audio codec table (Logitech / Microsoft / HP / Creative / AB13X-AB17X) - R21 (d78aa7f39): 4-entry AMD IOMMU DMI table (Dell 7375 / 5495, Acer A315-41, Lenovo 330S-15ARR) - R16+R22 (d980dc274): deferred landing pads (algorithmic / imperative sources) QUIRKS-SYSTEM.md updates: - Recent Activity (2026-06) table: 7 new rows for R15-R22 (plus combined R16+R22). - Test count: 158 → 161 (+3 new unit tests across R15, R17, R20). - Headline: 'ALL phases R0-R22 RESOLVED OR DEFERRED.' R11-R21 land data + lookup; R16+R22 documented as deferred. 9 new TOML files total in this session. - Adjusted Phase Estimates updated to reflect that R15-R21 data + lookup landed; R16+R22 carry the full audit estimate since they're deferred (5-7 + 3-4 days of kernel-side work). No blockers or gaps remain. The R1-R10 audit, R11-R21 phases, and 4 medium-low gaps are all in 0.2.3 branch (pushed to gitea.redbearos.org).
Red Bear OS
A microkernel operating system written in Rust, derived from Redox OS
What is Red Bear OS?
Red Bear OS is a general-purpose, Unix-like operating system with a microkernel architecture, written in Rust. It is a full fork of Redox OS, frozen at release 0.1.0, with added hardware support, filesystem drivers, and a KDE Plasma desktop path.
Goals:
- AMD & Intel parity — first-class support for both platforms on bare metal
- KDE Plasma desktop — Wayland-based desktop environment via the KWin compositor
- Hardware GPU acceleration — AMD GPU (amdgpu) and Intel GPU drivers via
redox-drm - Modern subsystems — USB, Wi‑Fi, Bluetooth, ext4, GRUB, D-Bus
- Offline-first builds — reproducible from archived, BLAKE3-verified sources
Quick Start
Prerequisites
Linux x86_64 host with Rust nightly, QEMU, nasm, and standard build tools.
See the Redox Build Guide for full setup.
Build & Run
# Clone
git clone https://gitea.redbearos.org/vasilito/RedBear-OS.git
cd RedBear-OS
# Build and run the desktop target in QEMU
./scripts/run.sh --build
# Build a live ISO for bare metal
./scripts/build-iso.sh redbear-full
# Build the text-only recovery target
./scripts/run.sh --build --config redbear-mini
Repository Hosting
The canonical Red Bear OS Git server is Gitea at
https://gitea.redbearos.org/vasilito/RedBear-OS.git. GitHub is not a Red Bear OS source of
truth and must not be used for pushes, issues, releases, or project coordination.
Public Scripts
| Script | Purpose |
|---|---|
scripts/run.sh |
Build and run in QEMU (-b to build, -c <config> for target) |
scripts/build-iso.sh |
Build a live ISO for bare-metal boot |
scripts/build-all-isos.sh |
Build all live ISO targets |
scripts/network-boot.sh |
PXE network boot helper |
scripts/dual-boot.sh |
Dual-boot installation helper |
Config Targets
| Target | Type | Description |
|---|---|---|
redbear-full |
Desktop | Wayland + KDE + GPU drivers + D-Bus services |
redbear-mini |
Console | Text-only recovery / install target |
redbear-grub |
Console | Text-only with GRUB boot manager |
Current Status
Red Bear OS boots to a login prompt in QEMU with working wired networking, D-Bus system bus, hardware detection daemons, and filesystem support (RedoxFS, ext4, FAT).
| Area | Status |
|---|---|
| Boot (ACPI/x2APIC/SMP) | ✅ Bare-metal proven |
| Userspace drivers (PCI, storage, net) | ✅ Working in QEMU |
| D-Bus system bus + services | ✅ Working (login1, PolicyKit, UDisks, UPower) |
| ext4 / FAT filesystems | ✅ Compiles, installer-wired |
| POSIX gaps (relibc) | 🚧 Bounded Wayland-facing support |
| DRM/KMS display drivers | 🚧 AMD + Intel compile; HW validation pending |
| Wayland compositor | 🚧 Bounded proof; Qt6/KF6 clients crash at init |
| KDE Plasma desktop | 🔄 In progress (Qt6/KF6 compile; KWin/QML blocked) |
| Wi‑Fi / Bluetooth | 📋 Planned (architected, implementation pending) |
How It Works
Red Bear OS uses a userspace driver model — all drivers run as unprivileged daemons:
Kernel (microkernel)
└── schemes: memory, irq, event, pipe, debug
└── Driver daemons (userspace)
├── pcid → PCI enumeration
├── e1000d → Intel ethernet
├── xhcid → USB controller
└── vesad → Display framebuffer
The kernel provides minimal services (memory, interrupts, IPC). Everything else — filesystems, networking, graphics, input — runs in userspace.
Documentation
- Implementation Plan — roadmap and execution model
- Desktop Path Plan — kernel → DRM → Mesa → Wayland → KDE
- D-Bus Integration — session bus architecture
- USB Plan — USB stack design
- Wi‑Fi Plan — wireless architecture
- Bluetooth Plan — BT stack design
- Documentation Index — full doc map
Contributing
Red Bear OS uses a full fork model. Upstream Redox sources are frozen and archived. All custom work lives in local/:
local/
├── sources/ # Red Bear source forks (git repos, directly editable)
├── recipes/ # Custom packages (drivers, GPU, system)
├── docs/ # Integration and planning docs
└── scripts/ # Build, test, and release tooling
We welcome contributions made with or without AI assistance — we care about quality, not how the code was produced.
License
MIT — same as upstream Redox OS.