Redox OS April update boosts boot reliability and hardware support

Redox OS spent April making the kind of progress that matters most when a Rust operating system leaves the comfort of virtual machines and meets real hardware. The project said booting became more resilient and less likely to get stuck after fixes from Wildan Mubarok, and that the boot process now keeps going even if important drivers exit or become blocked. Redox also said startup got faster on machines with multiple CPU cores, a practical gain that turns into quicker test cycles and less time waiting for a desktop to appear.

The hardware work did not stop at boot speed. Redox rebased and updated its ACPI crate against upstream Rust-OSDev work, a move meant to improve support for a wider range of computers and for VirtualBox. That matters because ACPI is one of the places where operating systems run into the ugliest firmware quirks, and Redox’s own hardware-compatibility guide says different models can expose boot bugs, missing device support, and performance degradation. The same guide still lists incomplete ACPI support, unsupported Wi-Fi and Bluetooth, and missing support for AMD, NVIDIA, ARM, and PowerVR GPUs, which makes April’s ACPI work an important step rather than a finished answer.

Redox also pushed harder on RISC-V, where Aarch Angel switched compatibility work to the Sv39 MMU scheme and added bootloader workarounds. That broadens the project’s reach beyond mainstream x86 machines and keeps it relevant on newer embedded and experimental platforms. At the desktop level, Wildan Mubarok ported tmux, improved the CPU time statistics reported to tools like htop, and implemented partial window pixel updates in Orbital so the desktop redraws only the pixels that changed. Those changes are small on paper, but they directly affect how responsive the system feels.

April’s report also showed a wider ecosystem taking shape around the OS. Cookbook Web Mode enabled package web pages, giving Redox package information pages that resemble the browsers Linux users rely on to inspect repositories. Underneath that, the kernel saw work on deadlocks, a memory leak, multi-threading stability, vector allocation and removal performance, mmap performance, and process CPU affinity reporting. For a project Redox describes as a complete Unix-like, general-purpose microkernel-based operating system written in Rust, that mix of user-facing polish and low-level cleanup is the point.

Redox says it was created in 2015, before Rust 1.0, and was one of the first operating systems written in Rust. It began as an unikernel before being redesigned around a microkernel architecture and a unified system API, with security, reliability, and modest POSIX compatibility at the center of the design. April’s update fits that longer trajectory: Rust is no longer just proving itself in libraries and services, but in boot paths, drivers, and the messy reality of hardware support.