Back to Redox

Hardware Compatibility

HARDWARE.md

0.9.09.3 KB
Original Source

Hardware Compatibility

This document tracks the current hardware compatibility of Redox OS.

Why are hardware reports needed?

Each computer model has different hardware interfaces, firmware implementations, and devices, which can cause the following problems:

  • Boot bugs
  • Lack of device support
  • Performance degradation

These reports helps us to fix the problems above, your report may help to fix many computers affected by the same bugs or missing drivers.

What if my computer is customized?

If your desktop is customized (common) you should use the "Custom" word on the "Vendor" category and insert the motherboard and CPU vendor/model in the "Model" category.

A customized laptop should only be reported if you replaced the original CPU, report the CPU vendor and model in the "Model" category.

We also recommend to add your pciutils log on this document to help us with probable porting.

Status

  • Recommended: The operating system boots with video, sound, PS/2 or USB input, Ethernet, terminal and Orbital working.
  • Booting: The operating system boots with some issues or lacking hardware support (write the issues and what supported hardware is not working in the "Report" section).
  • Broken: The boot loader don't work or can't bootstrap the operating system.

General

This section contain limitations that apply to any status.

  • ACPI support is incomplete (some things are hardcoded on the kernel to work)
  • Wi-Fi and Bluetooth aren't supported yet
  • AMD, NVIDIA, ARM, and PowerVR GPUs aren't supported yet (only BIOS VESA and UEFI GOP)
  • I2C devices aren't supported yet (PS/2 or USB devices should be used)
  • USB support varies on each device model because some USB devices require specific drivers (use input devices with standardized controls for more compatibility)
  • Automatic operating system discovery is not implemented in the boot loader yet (remember this before installing Redox)

Contribute to this document

To contribute to this document, learn how to create your GitLab account, follow the project-wide contribution guidelines and suggestions, please refer to the CONTRIBUTING.md document.

Template

You will use this template to insert your computer on the table.

|  |  |  |  |  |  |  |  |

The Redox image date should use the ISO format

Table row ordering

New reports should use an independent alphabetical order in the "Vendor" and "Model" table rows, for example:

| ASUS | ROG g55vw |
| ASUS | X554L |
| System76 | Galago Pro (galp5) |
| System76 | Lemur Pro (lemp9) |

A comes before S, R comes before X, G comes before L

Each "Vendor" has its own alphabetical order in "Model", independent from models from other vendor.

VendorModelRedox VersionImage DateVariantCPU ArchitectureMotherboard FirmwareReport
LenovoIdeaPad Y510P0.8.02022-11-11desktopx86-64BIOS, UEFIBoots to Orbital
System76Galago Pro (galp5)0.8.02022-11-11desktopx86-64UEFIBoots to Orbital
System76Lemur Pro (lemp9)0.8.02022-11-11desktopx86-64UEFIBoots to Orbital

Booting

VendorModelRedox VersionImage DateVariantCPU ArchitectureMotherboard FirmwareReport
ASUSEee PC 9000.8.02022-11-11desktopi686BIOSBoots to Orbital, No ethernet driver, Correct video mode not offered (firmware issue)
ASUSPRIME B350M-E (custom)0.9.02024-09-20desktopx86-64UEFIPartial support for the PS/2 keyboard, PS/2 mouse is broken
ASUSROG g55vw0.8.02023-11-11desktopx86-64BIOSBoots to Orbital, UEFI panic in SETUP
ASUSX554L0.8.02022-11-11desktopx86-64BIOSBoots to Orbital, No audio, HDA driver cannot find output pins
ASUSVivobook 15 OLED (M1503Q)0.9.02025-08-04desktopx86-64UEFIBoots to Orbital, touchpad and usb do not work, cannot connect to the internet, right maximum display resolution 2880x1620
DellXPS 13 (9350)0.8.02022-11-11desktopi686BIOSBoots to Orbital, NVMe driver livelocks
DellXPS 13 (9350)0.8.02022-11-11desktopx86-64BIOS, UEFIBoots to Orbital, NVMe driver livelocks
HPDev One0.8.02022-11-11desktopx86-64UEFIBoots to Orbital, No touchpad support, requires I2C HID
HPEliteBook Folio 9480M0.9.02025-11-04desktopx86-64UEFIBoots to Orbital, touchpad and usb work, cannot connect to the Internet, install failed, right maximum display resolution 1600x900
LenovoThinkPad Yoga 260 Laptop - Type 20FE0.9.02024-09-07demox86-64UEFIBoots to Orbital, No audio
LenovoYoga S730-13IWL0.9.02024-11-09desktopx86-64UEFIBoots to Orbital, No trackpad or USB mouse input support
Raspberry Pi3 Model B+0.8.0UnknownserverARM64U-BootBoots to UART serial console (pl011)
SamsungSeries 3 (NP350V5C)0.9.02025-08-04desktopx86-64UEFIBoots to Orbital, touchpad works, USB does not work, can connect to the Internet through LAN. Wrong maximum display resolution 1024x768
System76Oryx Pro (oryp10)0.8.02022-11-11desktopx86-64UEFIBoots to Orbital, No touchpad support, though it should be working
System76Pangolin (pang12)0.8.02022-11-11desktopx86-64UEFIBoots to Orbital, No touchpad support, requires I2C HID
ToshibaSatellite L5000.8.02022-11-11desktopx86-64BIOSBoots to Orbital, No Ethernet driver, Correct video mode not offered (firmware issue)

Broken

VendorModelRedox VersionImage DateVariantCPU ArchitectureMotherboard FirmwareReport
ASUSPN410.8.02024-05-30serverx86-64UnknownAborts after panic in xhcid
BEELINKU590.8.02024-05-30serverx86-64UnknownAborts after panic in xhcid
FrameworkLaptop 16 (AMD Ryzen 7040 Series)0.9.02024-09-07server, demox86-64UEFIBlack screen and unresponsive after the bootloader and resolution selection
HPCompaq nc61200.9.02024-11-08desktop, serveri686BIOSUnloads into memory at a rate slower than 1MB/s after selecting resolution. When unloading is complete the logger initializes and crashes after kernel::acpi, some information about APIC is printed. Boot logs do not progress after this point.
HPEliteBook 2570p0.8.02022-11-23demox86-64BIOS (CSM mode?)Gets to resolution selection, Fails assert in src/os/bios/mod.rs:77 after selecting resolution
LenovoG5700.8.02022-11-11desktopx86-64BIOSBootloader panics in alloc_zeroed_page_aligned, Correct video mode not offered (firmware issue)
LenovoIdeaPad Y510P0.8.02022-11-11desktopi686BIOSPanics on phys_to_virt overflow, probably having invalid mappings for 32-bit
LenovoThinkCentre M830.9.02025-11-09desktopx86_64UEFIPresents user with a set of display resolution options. After user selects an option, it takes a long time for the "live" thing to load all the way to 647MiB. Once it does reach 647MiB, however, it dumps a bunch of logs onto the screen. Those logs also happen to be offset so that the leftmost portion of all text "exists" past the leftmost part of the screen, resulting in the logs being only partially visible. The logs appear to include (among other things) 1. "thread 'main' (1) panicked at acpid/src/acpi.rs:256:68: Called Result::unwrap() on an Err value: Aml(NoCurrentOp)"; 2. "thread 'main' (1) panicked at acpid/src/main.rs:147:39:acpid: failed to daemonize: Error I/O error 5"; 3. "... [@hwd:40 ERROR] failed to probe with error No such device (os error 19)..."; etc.
PanasonicToughbook CF-180.8.02022-11-11desktopi686BIOSHangs after PIT initialization
ToshibaSatellite L5000.8.02022-11-11desktopi686BIOSCorrect video mode not offered (firmware issue), Panics on phys_to_virt overflow, probably having invalid mappings for 32-bit
XMG (Schenker)Apex 17 (M21)0.9.02024-09-30demo, serverx86-64UEFIAfter selecting resolution, (release) repeats ...::interrupt::irq::ERROR -- Local apic internal error: ESR=0x40 a few times before it freezes; (daily) really slowly prints statements from ...::rmm::INFO before it abruptly aborts