CoreDoom: Playing Doom Directly from BIOS on Modern Machines
For decades, fans of classic 3D shooters have enjoyed Doom on a variety of devices. What makes this tale even more intriguing is the possibility of running the game without any operating system at all. In a recent development, enthusiasts demonstrated how a full Doom experience can appear inside the very firmware that powers a computer, long before any booted OS takes shape.
The focal point is Coreboot 4.17, a free, open alternative to traditional BIOS and UEFI firmware for PCs and laptops. Embedded within Coreboot is a feature often called a payload, and in this instance it carries a port of the game CoreDoom. The idea is simple yet bold: if the firmware has enough space, it can host additional software, including games. In the past, others have experimented with similar payloads, bringing Space Invaders and Tetris to life in the earliest stages of a system’s startup. The bottom line is that a working game can run without any operating system present.
CoreDoom is derived from the DoomGeneric port and is installed directly into the BIOS chip. The crucial constraint is available space on the firmware image. While there are limitations, control remains possible through a keyboard connected via PS/2, with USB support on the roadmap. Notably, the current version lacks audio, and there is no built-in method to save progress or alter settings during gameplay. Exiting the game can cause the system to freeze, a reminder of the experimental nature of this setup rather than a polished consumer feature.
What stands out is the sheer ingenuity of running a classic title in such a constrained environment. This achievement evokes memories of earlier experimentation, as Doom was once launched in pseudo-graphics mode on a wired phone, on a Sega Genesis console, and even in unlikely places like on potatoes. It showcases the enduring appeal of DOOM and the creativity of the communities that push hardware to its limits.
While the idea excites hobbyists, it also invites practical questions about firmware design, security implications, and the balance between innovation and stability. Coreboot itself represents a movement toward open, auditable firmware that emphasizes speed and transparency. Placing a game inside the firmware is a vivid demonstration of what open systems can enable, beyond traditional operating environments. It invites developers to explore payloads that extend the firmware’s function while remaining mindful of the potential tradeoffs in reliability and maintainability.
The broader takeaway is that modern firmware can host meaningful, interactive experiences, blurring the lines between hardware initialization and software execution. The CoreDoom experiment illustrates how old loves for classic games can find new life at the very first moment a computer powers up. It also underscores a philosophy of openness where power users can experiment with core software layers and push technology forward, one payload at a time.
As this kind of exploration continues, users should approach it with both curiosity and caution. Firmware-level experimentation requires careful planning, adequate documentation, and an understanding of how changes at the lowest levels of a system can affect overall behavior. Yet for those who enjoy hands-on tinkering, the possibility of running Doom without a traditional operating system remains a compelling reminder that hardware and software are parts of a single, unfolding conversation. This ongoing dialogue between open firmware and classic gaming continues to inspire makers and engineers alike.
Attribution note: information reflects reporting on a firmware and game payload demonstration. (attribution: VG Times)