[[!meta title="Supported Hardware"]]

[[!toc startlevel=2 levels=2]]


DragonFly BSD runs on recent PCs (currently only) supporting the amd64 (x86_64) 64-bit architecture. Up to version 3.8, the i386 (x86) 32-bit architecture was also supported.
The UEFI (with GPT) is also supported, but the installer has *not* been updated to work with UEFI, therefore one has to do manual installation and configuration.

This page only references a small part of the hardware which can potentially run with DragonFly BSD; if a piece of hardware is not in this list this only means nobody has tested it or reported its working state.

## Laptops

* Lenovo ThinkPad: X200, X220, X250, X260
* Dell Latitude E7240

## Desktops

Aleutia T2

* 1.8 GHz Intel Atom 64-bit 2-core 2-hyperthread CPU, 4 GB RAM.
* Display (including X), sound (snd_hda), USB (tested by installing from thumb drive), hard drive, network, and PS/2 mouse and keyboard all work.

CompuLab MintBox Mini FITLET
* CPU AMD A4 Micro-6400T , 4GB RAM, 64GB mSATA
* XFCE desktop OK after style and font adjustments in Settings-Appearance
* Sound OK, loaded all drivers by putting snd_driver_load="YES" in /boot/loader.conf
* Sound OK from HDMI to TV monitor
* Sound OK from front headphone jack (hw.snd.default_unit=2 in /etc/sysctl.conf)
* Provided wireless run0 USB adapter OK, if_run_load="YES" in /boot/loader.conf
* Installed from USB flash drive
* Note: poor graphics/font display

Dell Optiplex 740
* AMD Athlon CPU, Nvidia Geforce 6150 LE GPU (304 legacy)

PowerSpec N108
* Celeron G1820 2.7Ghz CPU

## Graphics

* Intel GPUs are supported up to the Skylake generation (2016 machines)

## System Boards and chipsets

Most desktop and server class mainboards using Intel or AMD chipsets are supported; the devices listed in this section are known to run really well with DragonFly BSD.

### Desktop boards

* Gigabyte UD2H / UD3H series (Such as)
* Gigabyte 880GM-UD2H works extremely well, less software RAID AHCI controller, which is not a real RAID controller.
* Asrock H77 boards; Everything is supported.
* Asrock and Gigabyte socket 1150 (Haswell) boards

### Server boards

* Supermicro X7SPA-H (Atom)
* Supermicro X8 series
* Dell r410
* Supermicro X9 series
* Supermicro X10 series (Haswell/Broadwell Xeons)

## Storage

### SATA controllers

* Intel ICH7 and more recent chipsets
* AMD 700-series chipsets
* Silicon Image 3124/3132 chipsets

### SATA RAID controllers

Devices supported by the arcmsr(4) driver

* Areca ARC-1200
* Areca ARC-1210

Devices supported by the twa(4) driver

* 3Ware 9650SE series

### SAS RAID controllers

These controllers are able to use both SAS and SATA hard-drives.

Devices supported by the arcmsr(4) driver

* Areca ARC-1212 and ARC-1222
* Areca ARC-1213 and ARC-1223
* Areca ARC-1680-ix
* Areca ARC-1880 and ARC-1882 series

Devices supported by the mfi(4) driver

* LSI MegaRAID SAS 8408E

Devices supported by the mps(4) driver

* LSI Logic SAS2008-based controllers such as Asus PIKE 2008

Devices supported by the twa(4) driver

* 3Ware 9690SA-4i

Devices supported by the tws(4) driver

* 3Ware 9750-4i

## Networking

### Gigabit ethernet adapters

Devices supported by the em(4) driver:

* Intel 82540, 82541ER, 82541PI, 82542, 82543, 82544, 82545, 82546, 82546EB, 82546GB, 82547
* Intel 82571, 81572, 82573, and 82574

The igb(4) driver provides support for PCI Express Gigabit Ethernet adapters based on the Intel 82575 and 82576 Ethernet controller chips.

The re(4) driver supports Realtek RTL8169, RTL8169S, RTL8110S, RTL8168S, RTL8111S and RTL8101E ethernet chipsets.

### 10 Gigabit ethernet adapters

The mxge(4) driver supports 10 Gigabit Ethernet adapters based on the Myricom LANai Z8E chips.

The ixgbe(4) driver supports the Intel PRO/10GbE adapters based on the 82598 and 82599 chip families.

## Broken hardware

The products listed in this section are known to have some serious problems or not work at all with DragonFly BSD.

* Asus M2N4-SLI: USB is not working on this model

* HP Pavilion dv7 laptops: as of 2012-07 it is impossible to run DragonFly BSD on them due to broken ACPI interrupt routing in their firmware.