Why Hardware Reports Are 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
Customized Hardware
If your desktop is customized (common), use “Custom” for the Vendor category and insert the motherboard and CPU vendor/model in the Model category.
pciutils log to the Community Hardware document to help with probable porting.
Compatibility Status Definitions
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.
Broken
The boot loader doesn’t work or can’t bootstrap the operating system.
General Limitations
- ACPI support is incomplete (some things are hardcoded in 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
- Automatic operating system discovery is not implemented in the boot loader yet
Recommended Hardware
These devices boot successfully with full or near-full functionality:Booting with Issues
These devices boot but have partial functionality or known issues:Broken Hardware
These devices fail to boot or have critical issues:Contributing Hardware Reports
1
Test Redox on your hardware
Download and run the latest Redox image on your device.
2
Document your results
Note the hardware details, boot behavior, and any issues encountered.
3
Submit your report
Follow the guidelines in CONTRIBUTING.md to submit your hardware report.
Report Template
Use this format when submitting reports:The Redox image date should use the ISO format (YYYY-MM-DD).