15h.org - User contributions [en]

Home

2026-10-08T00:41:32Z

Dodoid: change EHCI debugging to Serial Debugging in quick links

{{Excerpt|Showcase|hat=no|templates=Infobox, Excerpt}}

Welcome to 15h.org, a resource for documentation and open source support for AMD's [[Family 15h]] (fam15h) and other related processors and platforms.

{| class="wikitable" style=""
| style="width: 33.33%"| {{center|'''🖥️ Get Started with Hardware'''}}
| style="width: 33.33%"| {{center|'''⚙️ Build your Firmware'''}}
| style="width: 33.33%"| {{center|'''👋 Join Us!'''}}
|-
|
* [[Build Guide]]
* [[Motherboards]]
* [[Coolers|CPU Coolers]]
|
* [[coreboot-15h]]
* [[External Flashing]]
* [[Serial Debugging]]
* [https://git.15h.org/explore/repos Browse our Git forge]
|
* Join us on [[Matrix]]
* [[Editing This Wiki|Edit this wiki!]]
* [[Add your build]]
* [[Community Todo List]]
|-
|colspan=3|
{{center|'''📰 News'''}}
<div class="blogembed" style="text-align: center;">
{{Excerpt|News|Posts|subsections=yes|hat=no|only=templates|templates=1-3}}
</div><br>
|} __NOTOC__

=== Why 15h? ===
Released between 2011 and 2014, AMD's [[fam15h]] (and its approximately-contemporaneous relatives, [[fam10h]], [[fam14h]] and [[fam16h]]) are the final high-performance x86_64 microprocessors lacking most of the limitations newer x86 platforms are encumbered by. In many cases, fam15h hardware can provide a performant, full-featured system, using entirely free and open source software. It enforces no firmware signing (allowing things such as [[coreboot]]), can be booted entirely with free firmware (including memory initialization), and it requires no privileged management coprocessor (such as the Platform Security Processor or Management Engine, found on newer AMD and Intel platforms respectively). Where a [[Board Management Controller]] is present, it can usually reliably disabled, or better yet, flashed with [[OpenBMC]]. On fam10h, even microcode is unencrypted and unsigned, and can be modified by the user.

Beyond their currently-unparalleled degree of firmware freedom for a modern x86_64 platform, AMD hardware of this era (in particular, 6200 and 6300-series [[Opteron]] platforms) remains a powerful and cost-effective option for many systems, especially under parallel workloads. Despite this, the comparative popularity of competing Intel processors during this era has limited the familiarity and uptake of these pre-Zen AMD platforms among many enthusiasts.

If you are looking for an x86_64 platform under your complete control, this website serves to demystify fam15h and its relatives, so that these systems can remain in operation well into the future.

=== What hardware was that again? ===
Robust support for coreboot on select fam15h motherboards has been developed and thoroughly tested at 15h.org. The current, production ready motherboards are [[KGPE-D16]], [[KCMA-D8]], [[H8QG6]], [[H8SGL]], and [[H8SCM]]. A handful of other fam15h motherboards have [[Motherboards|preliminary support]]. For these motherboards, the [[Bulldozer]] and [[Piledriver]] microarchitectures are supported by [[coreboot-15h]].


{{:Board Grid}}

Orochi

2026-10-07T12:26:28Z

Dodoid: Changed redirect target from Family 15h#Overview to Family 15h#Orochi

#REDIRECT [[Family_15h#Orochi]]

15or

2026-10-07T12:24:11Z

Dodoid: Redirected page to Orochi

#REDIRECT [[Orochi]]

15tn

2026-10-07T12:23:48Z

Dodoid: Redirected page to Trinity

#REDIRECT [[Trinity]]

Jingsha

2026-10-03T04:41:14Z

Dodoid:

[[File:Jingsha_X89L.jpg|thumb|300px|A Jingsha X89-L]]

Jingsha is a Chinese manufacturer of G34 motherboards, apparently using repurposed components from scrapped boards. Their boards appear to have been manufactured new through approximately 2023, though they have become harder to purchase recently. Branding of Jingsha boards was inconsistent - the boards and firmware were seemingly unbranded, while packaging and product listings variously identified them as Jingsha, MACHINIST (in actuality an apparently-separate Chinese company manufacturing similar boards with salvaged Intel hardware), or one of several other seemingly one-off names. Branding usually included the term "X89" in an apparent reference to Intel's X79 and X99 chipsets (commonly used on similar modern boards for repurposed Intel Xeons), even though there is no such "X89" chipset (from AMD or Intel). In reality, these boards used the [[AMD SR5650]].

Jingsha motherboards include only two DIMM slots. While these slots are on two separate memory channels, both of these channels are on the same die of the CPU, resulting in performance losses for memory accesses by cores on the other die (which must instead access memory entirely via NUMA).

== Server and Workstation Motherboards ==
{| class="wikitable sortable"
|-
! Motherboard !! Sockets !! Form Factor !! Coreboot Status
|-
| [[X89]] || 1x [[Socket G34|G34]] || u-ATX ||style="background-color:#FAA"| No
|-
| [[X89-L]] || 1x [[G34]] || ATX ||style="background-color:#FAA"| No
|}

Board Management Controller

2026-10-03T04:36:05Z

Dodoid:

A '''Board Management Controller''' (BMC) is a chip found on most server and many workstation motherboards, used to provide networked monitoring and control of the system. They generally allow for remote monitoring of power and cooling systems, remote power and reset controls, access to server consoles, and access to "KVM" functions (remote keyboard and mouse input, and viewing the display). On many server motherboards, the BMC doubles as the onboard video controller, providing a basic, unaccelerated framebuffer for video output over VGA. Most BMCs can also provide fan control, though systems including them usually also offer other ways to control fans. BMCs generally connect to a network via an additional dedicated Ethernet port on motherboard, but some can also connect via onboard Ethernet ports shared with the host.

Stock BMC firmware typically complies with the IPMI (Intelligent Platform Management Interface) specification, and the BMC and its user interface are sometimes referred to as "the IPMI". However, IPMI is simply a standard for BMC functionality, and non-IPMI BMC firmware exists. In some cases, motherboard vendors charge extra for use of a BMC included on a board, often by selling its firmware on a separate removable flash module, or by selling a licensing dongle which enables use of the BMC.

The functionality of a BMC overlaps with the functionality of Intel's AMT, which provides remote administration via the Intel Management Engine. Like the Management Engine, the ability of a BMC to provide remote control of a system over the internet via proprietary firmware has been characterized as a security threat, and some users may avoid connecting their BMC to a network or installing its firmware flash module for this reason. Maintenance of BMC firmware for a board is frequently abandoned by board vendors long before customers have stopped using the board, default credentials for remote management are a well-known issue, and BMC firmware security is often worse than that of the host system's operating system.

[[OpenBMC]] is an open-source project maintained by the Linux Foundation, which provides Yocto Linux-based alternative firmware for the BMCs on some motherboards, including the AST2050 BMC found in the ASUS [[KGPE-D16]]. While current versions of OpenBMC no longer support the AST2050 (similar to the situation with upstream [[Coreboot]]), older versions of OpenBMC can still be used on it.

Evil Qubesotron

2026-10-03T04:20:34Z

Dodoid:

{{Infobox individual system
|name = Evil Qubesotron
|owner = Dodoid
|built = Frantically, following Qubesotron's issues

|motherboard = ASUS PRIME X299-A
|cpu = Intel Core i7 7820X
|gpu = AMD Radeon Pro W5500
|ram = 48GB assorted DDR4
|storage1 = 2x 1.6TB Samsung PM1725a Enterprise HHHL NVMe SSD
|psu = Thermaltake SMART Series 700W
|chassis = Cooler Master Storm Enforcer
|cooler = Hyper 212 Evo
|nic = Onboard

|firmware = Stock AMI Firmware
|payload = Some Kinda UEFI
|oproms = you bet
|os = Debian Stable
|filesystem = ZFS
|workload = "oh shit"
}}

'''Evil Qubesotron''' was the temporary host of 15h.org while [[Qubesotron]] was down in September, 2026, following a motherboard failure. It was built in approximately 30 minutes, from spare parts on hand, plus Qubesotron's SSDs and GPU - as such, unusually for our systems, it had an Intel CPU and did not run [[coreboot]].

Serial Debugging

2026-10-01T08:27:43Z

Dodoid: /* But what IS a Null Modem? */

[[File:RS-232_DE-9_Connector_Pinouts.png|thumb|Pinouts for the RS-232 serial port]]
If you are developing or debugging coreboot, it is helpful to receive coreboot's console logs from the system as early as possible. Where available, the best option for this is serial debugging, using an RS-232 serial port - this is generally reliable and can become available very early in the boot process (in most cases, the only earlier diagnostic tool available will be POST codes). If you do not have a serial port, you can consider [[EHCI Debugging]] instead.

== Tools ==
[[File:Serialheader.jpg|thumb|A serial slot bracket adapter]]
You will need:
* The system you wish to debug
* If your device has only an internal serial header, an appropriate serial breakout
* A null modem serial cable, OR a straight-through serial cable and a null modem adapter. You cannot use a null modem cable AND a null modem adapter together.
* Another device on which to view your logs (commonly a laptop)
* If your other device does not have a built-in serial port, a USB-to-Serial adapter
* A coreboot build configured to use a serial console. coreboot-15h builds and default configurations do this by default.

== Usage ==
Begin with your console machine running and the system you are testing powered off.

If necessary, install your serial slot bracket adapter in your chassis. Many boards have housings around their headers which will prevent you from connecting the cable backwards. If your board does not have this, note that one edge of the adapter's cable should be colored red - that edge signifies Pin 1. Connect the header, covering all 9/10 pins, with the red edge pointing towards the header's Pin 1 (likely marked with a white box or dot printed on the board beside the pin, on the opposite end from the missing 10th pin in the corner). Plug the IDC connector onto the motherboard's lowest-numbered COM header (usually labeled COM or COM1).

Connect the serial cable from the system you are testing's serial port to your other device's serial port (or to your USB-to-serial adapter). Ordinarily, you can do this using a single female-to-female DE-9 null modem cable and no additional adapters, or a single female-to-female DE-9 straight-through cable and a null-modem adapter. If for some reason this is not practical, in theory, you can use any combination of serial cables and adapters that includes any odd number of null modems. Connect your USB-to-serial adapter to your console machine if needed.

Find out the path of your serial port. For USB serial devices, typically this will be something like /dev/ttyUSB0. For onboard serial ports, typically this will be something like /dev/ttyS1.

Start a serial console application. tio is a good command-line serial console tool, available on Linux and many other platforms. In the case of tio, you can launch it using, for example:
<nowiki>
tio /dev/ttyUSB0 -b 115200</nowiki>

This means connect to /dev/ttyUSB0, at 115,200 bits per second (the default bitrate used by coreboot console and many other things). Other serial port parameters (8 data bits/no parity/1 stop bit) should be correct by default.

You should see e.g.

<nowiki>
[15:10:51.502] tio 3.9
[15:10:51.502] Press ctrl-t q to quit
[15:10:51.503] Connected to /dev/ttyUSB0</nowiki>

Start the system you are testing. If your setup is configured correctly, you should see coreboot logs begin to appear on the console, e.g.

<nowiki>
coreboot-57e26bdcd9 Wed May 27 19:45:28 UTC 2026 romstage starting (log level: 6)...
...WARM RESET...

board_reset() called!
system_reset() called!

coreboot-57e26bdcd9 Wed May 27 19:45:28 UTC 2026 romstage starting (log level: 6)...
SPD: Socket 0, Channel 0, Dimm 0
SPD: Socket 0, Channel 0, Dimm 1
...</nowiki>

== Internal Serial Headers ==
[[File:Dtkintel_ateverex.jpg|thumb|The DTK/Intel and AT/Everex serial header pinouts]]
If your machine has an external serial port, it virtually certainly uses the DE-9 Male DTE-side connector shown above (left, blue). If you have an internal serial port, you can use an adapter (typically in place of an an unused PCI slot's slot cover) to add one of these external connectors to your system. Unfortunately, while the external connector is standard, there are ''two'' incompatible common internal header pinouts - DTK/Intel and AT/Everex both using the same 10-pin 2.54mm-pitch IDC connector. You will need an adapter wired properly for the connector on your motherboard - most boards supported in coreboot-15h are AT/Everex, but you should check your manual before connecting an adapter to a motherboard of unknown pinout.

If you are purchasing an adapter, make sure the seller specifies which type it is, and that it matches which one you need. A seemingly-"defective" adapter, sold without a clearly-specified pinout, is sometimes simply the wrong pinout for your board.

== But what IS a Null Modem? ==
[[File:Null modem.jpg|thumb|A null modem adapter]]
RS-232 is a standard from the 1960s, and it was primarily designed for connecting communications equipment which would carry data a long distance (primarily modems) to the terminal equipment which the user operated (such as teletypes, terminals, and computers). As such, RS-232 defines two types of device - Data Communications Equipment (DCE) and Data Terminal Equipment (DTE), and ordinarily assumes you are using it to connect a DTE (like your computer) to a DCE (like a modem). Because they were intended to connect to computers (DTEs), RS-232 peripherals which were not "communications" devices (serial mice, printers, cameras, etc) were also wired as DCEs.

Any two RS-232 devices - DCE or DTE - can communicate, provided one's RX (Receive) pin is wired to the other's TX (Transmit) pin, and vice-versa. The difference between DCE and DTE is simply that where a DCE's connector has its TX pin, the DTE's connector has its RX pin, and vice-versa. This means that a simple straight-through cable (pin 1 to pin 1, pin 2 to pin 2, etc.) will work to connect a DCE to a DTE.

You, however, are not connecting a modem to your computer - you're connecting a computer (running coreboot, to debug) to your computer (where you will view the logs). Since these are both DTEs, this will not work with a straight-through cable - you need a null modem, which is simply an adapter that swaps the RX and TX pins, allowing two DTEs or two DCEs to communicate with eachother despite their RX/TX wiring. The adapter is a "modem" in the sense that RS-232 assumes that a pair of DTEs (computers) will always communicate through a pair of DCEs (their respective modems, via the network connecting the modems), and the adapter's wiring provides the RX/TX swap that these back-to-back modems would.

To add to the confusion, some ''cables'' are themselves wired as a null modem, and serial cables are frequently not labelled as either straight-through or null-modem. Two null modems in a row acts as a straight-through cable - if you have a null modem cable, you should NOT use a null modem adapter between two DTEs (i.e. for coreboot debugging). Some null modem adapters and cables also cross the hardware flow control pins of the serial ports. Hardware flow control is generally unused in coreboot debugging, and the presence or lack of this functionality can generally be ignored.

External RS-232 ports on "modern" (post-1996-ish) PCs are typically male DE-9 connectors, but DCE and DTE have nothing to do with male and female connectors - either device can have either type of connector, and cables and adapters are available in all combinations.

== Compatibility ==
Serial debugging can be used on most motherboards with a serial port in their rear I/O, or on a serial header. However, on some motherboards (particularly those with [[BMC]]s), the external serial port(s) may not be usable for coreboot console, or may work only when the BMC is enabled and running.

The following boards are known to have WORKING serial coreboot console:
* [[ASUS KGPE-D16]]
* [[ASUS KCMA-D8]]
* [[Supermicro H8DGi]]
* [[Supermicro H8QG6]]

The following boards are known to have BROKEN serial coreboot console:
* [[Supermicro H8SGL]]
* [[Supermicro H8SCM]]
* [[Supermicro H8SML]]

If your board is not listed here, find it on the [[Motherboards]] page and consult its own wiki page. In general, motherboards which have an officially-documented serial port (external or internal), which do not have a BMC, and which use an ordinary Super I/O (as opposed to a laptop-style EC), will almost always have a working serial console.

Serial Debugging

2026-10-01T08:25:06Z

Dodoid: /* But what IS a Null Modem? */

[[File:RS-232_DE-9_Connector_Pinouts.png|thumb|Pinouts for the RS-232 serial port]]
If you are developing or debugging coreboot, it is helpful to receive coreboot's console logs from the system as early as possible. Where available, the best option for this is serial debugging, using an RS-232 serial port - this is generally reliable and can become available very early in the boot process (in most cases, the only earlier diagnostic tool available will be POST codes). If you do not have a serial port, you can consider [[EHCI Debugging]] instead.

== Tools ==
[[File:Serialheader.jpg|thumb|A serial slot bracket adapter]]
You will need:
* The system you wish to debug
* If your device has only an internal serial header, an appropriate serial breakout
* A null modem serial cable, OR a straight-through serial cable and a null modem adapter. You cannot use a null modem cable AND a null modem adapter together.
* Another device on which to view your logs (commonly a laptop)
* If your other device does not have a built-in serial port, a USB-to-Serial adapter
* A coreboot build configured to use a serial console. coreboot-15h builds and default configurations do this by default.

== Usage ==
Begin with your console machine running and the system you are testing powered off.

If necessary, install your serial slot bracket adapter in your chassis. Many boards have housings around their headers which will prevent you from connecting the cable backwards. If your board does not have this, note that one edge of the adapter's cable should be colored red - that edge signifies Pin 1. Connect the header, covering all 9/10 pins, with the red edge pointing towards the header's Pin 1 (likely marked with a white box or dot printed on the board beside the pin, on the opposite end from the missing 10th pin in the corner). Plug the IDC connector onto the motherboard's lowest-numbered COM header (usually labeled COM or COM1).

Connect the serial cable from the system you are testing's serial port to your other device's serial port (or to your USB-to-serial adapter). Ordinarily, you can do this using a single female-to-female DE-9 null modem cable and no additional adapters, or a single female-to-female DE-9 straight-through cable and a null-modem adapter. If for some reason this is not practical, in theory, you can use any combination of serial cables and adapters that includes any odd number of null modems. Connect your USB-to-serial adapter to your console machine if needed.

Find out the path of your serial port. For USB serial devices, typically this will be something like /dev/ttyUSB0. For onboard serial ports, typically this will be something like /dev/ttyS1.

Start a serial console application. tio is a good command-line serial console tool, available on Linux and many other platforms. In the case of tio, you can launch it using, for example:
<nowiki>
tio /dev/ttyUSB0 -b 115200</nowiki>

This means connect to /dev/ttyUSB0, at 115,200 bits per second (the default bitrate used by coreboot console and many other things). Other serial port parameters (8 data bits/no parity/1 stop bit) should be correct by default.

You should see e.g.

<nowiki>
[15:10:51.502] tio 3.9
[15:10:51.502] Press ctrl-t q to quit
[15:10:51.503] Connected to /dev/ttyUSB0</nowiki>

Start the system you are testing. If your setup is configured correctly, you should see coreboot logs begin to appear on the console, e.g.

<nowiki>
coreboot-57e26bdcd9 Wed May 27 19:45:28 UTC 2026 romstage starting (log level: 6)...
...WARM RESET...

board_reset() called!
system_reset() called!

coreboot-57e26bdcd9 Wed May 27 19:45:28 UTC 2026 romstage starting (log level: 6)...
SPD: Socket 0, Channel 0, Dimm 0
SPD: Socket 0, Channel 0, Dimm 1
...</nowiki>

== Internal Serial Headers ==
[[File:Dtkintel_ateverex.jpg|thumb|The DTK/Intel and AT/Everex serial header pinouts]]
If your machine has an external serial port, it virtually certainly uses the DE-9 Male DTE-side connector shown above (left, blue). If you have an internal serial port, you can use an adapter (typically in place of an an unused PCI slot's slot cover) to add one of these external connectors to your system. Unfortunately, while the external connector is standard, there are ''two'' incompatible common internal header pinouts - DTK/Intel and AT/Everex both using the same 10-pin 2.54mm-pitch IDC connector. You will need an adapter wired properly for the connector on your motherboard - most boards supported in coreboot-15h are AT/Everex, but you should check your manual before connecting an adapter to a motherboard of unknown pinout.

If you are purchasing an adapter, make sure the seller specifies which type it is, and that it matches which one you need. A seemingly-"defective" adapter, sold without a clearly-specified pinout, is sometimes simply the wrong pinout for your board.

== But what IS a Null Modem? ==
[[File:Null modem.jpg|thumb|A null modem adapter]]
RS-232 is a standard from the 1960s, and it was primarily designed for connecting communications equipment which would carry data a long distance (primarily modems) to the terminal equipment which the user operated (such as teletypes, terminals, and computers). As such, RS-232 defines two types of device - Data Communications Equipment (DCE) and Data Terminal Equipment (DTE), and ordinarily assumes you are using it to connect a DTE (like your computer) to a DCE (like a modem). Because they were intended to connect to computers (DTEs), RS-232 peripherals which were not "communications" devices (serial mice, printers, cameras, etc) were also wired as DCEs.

Any two serial devices - DCE or DTE - can communicate, provided one's RX (Receive) pin is wired to the other's TX (Transmit) pin, and vice-versa. The difference between DCE and DTE is simply that where a DCE's connector has its TX pin, the DTE's connector has its RX pin, and vice-versa. This means that a simple straight-through cable (pin 1 to pin 1, pin 2 to pin 2, etc.) will work to connect a DCE to a DTE.

You, however, are not connecting a modem to your computer - you're connecting a computer (running coreboot, to debug) to your computer (where you will view the logs). Since these are both DTEs, this will not work with a straight-through cable - you need a null modem, which is simply an adapter that swaps the RX and TX pins, allowing two DTEs or two DCEs to communicate with eachother despite their RX/TX wiring. The adapter is a "modem" in the sense that RS-232 assumes that a pair of DTEs (computers) will always communicate through a pair of DCEs (their respective modems, via the network connecting the modems), and the adapter's wiring provides the RX/TX swap that these back-to-back modems would.

To add to the confusion, some ''cables'' are themselves wired as a null modem, and serial cables are frequently not labelled as either straight-through or null-modem. Two null modems in a row acts as a straight-through cable - if you have a null modem cable, you should NOT use a null modem adapter between two DTEs (i.e. for coreboot debugging). Some null modem adapters and cables also cross the hardware flow control pins of the serial ports. Hardware flow control is generally unused in coreboot debugging, and the presence or lack of this functionality can generally be ignored.

External RS-232 ports on "modern" (post-1996-ish) PCs are typically male DE-9 connectors, but DCE and DTE have nothing to do with male and female connectors - either device can have either type of connector, and cables and adapters are available in all combinations.

== Compatibility ==
Serial debugging can be used on most motherboards with a serial port in their rear I/O, or on a serial header. However, on some motherboards (particularly those with [[BMC]]s), the external serial port(s) may not be usable for coreboot console, or may work only when the BMC is enabled and running.

The following boards are known to have WORKING serial coreboot console:
* [[ASUS KGPE-D16]]
* [[ASUS KCMA-D8]]
* [[Supermicro H8DGi]]
* [[Supermicro H8QG6]]

The following boards are known to have BROKEN serial coreboot console:
* [[Supermicro H8SGL]]
* [[Supermicro H8SCM]]
* [[Supermicro H8SML]]

If your board is not listed here, find it on the [[Motherboards]] page and consult its own wiki page. In general, motherboards which have an officially-documented serial port (external or internal), which do not have a BMC, and which use an ordinary Super I/O (as opposed to a laptop-style EC), will almost always have a working serial console.

Serial Debugging

2026-10-01T08:10:26Z

Dodoid: Created page with "Pinouts for the RS-232 serial port If you are developing or debugging coreboot, it is helpful to receive coreboot's console logs from the system as early as possible. Where available, the best option for this is serial debugging, using an RS-232 serial port - this is generally reliable and can become available very early in the boot process (in most cases, the only earlier diagnostic tool available will be POST codes). If..."

[[File:RS-232_DE-9_Connector_Pinouts.png|thumb|Pinouts for the RS-232 serial port]]
If you are developing or debugging coreboot, it is helpful to receive coreboot's console logs from the system as early as possible. Where available, the best option for this is serial debugging, using an RS-232 serial port - this is generally reliable and can become available very early in the boot process (in most cases, the only earlier diagnostic tool available will be POST codes). If you do not have a serial port, you can consider [[EHCI Debugging]] instead.

== Tools ==
[[File:Serialheader.jpg|thumb|A serial slot bracket adapter]]
You will need:
* The system you wish to debug
* If your device has only an internal serial header, an appropriate serial breakout
* A null modem serial cable, OR a straight-through serial cable and a null modem adapter. You cannot use a null modem cable AND a null modem adapter together.
* Another device on which to view your logs (commonly a laptop)
* If your other device does not have a built-in serial port, a USB-to-Serial adapter
* A coreboot build configured to use a serial console. coreboot-15h builds and default configurations do this by default.

== Usage ==
Begin with your console machine running and the system you are testing powered off.

If necessary, install your serial slot bracket adapter in your chassis. Many boards have housings around their headers which will prevent you from connecting the cable backwards. If your board does not have this, note that one edge of the adapter's cable should be colored red - that edge signifies Pin 1. Connect the header, covering all 9/10 pins, with the red edge pointing towards the header's Pin 1 (likely marked with a white box or dot printed on the board beside the pin, on the opposite end from the missing 10th pin in the corner). Plug the IDC connector onto the motherboard's lowest-numbered COM header (usually labeled COM or COM1).

Connect the serial cable from the system you are testing's serial port to your other device's serial port (or to your USB-to-serial adapter). Ordinarily, you can do this using a single female-to-female DE-9 null modem cable and no additional adapters, or a single female-to-female DE-9 straight-through cable and a null-modem adapter. If for some reason this is not practical, in theory, you can use any combination of serial cables and adapters that includes any odd number of null modems. Connect your USB-to-serial adapter to your console machine if needed.

Find out the path of your serial port. For USB serial devices, typically this will be something like /dev/ttyUSB0. For onboard serial ports, typically this will be something like /dev/ttyS1.

Start a serial console application. tio is a good command-line serial console tool, available on Linux and many other platforms. In the case of tio, you can launch it using, for example:
<nowiki>
tio /dev/ttyUSB0 -b 115200</nowiki>

This means connect to /dev/ttyUSB0, at 115,200 bits per second (the default bitrate used by coreboot console and many other things). Other serial port parameters (8 data bits/no parity/1 stop bit) should be correct by default.

You should see e.g.

<nowiki>
[15:10:51.502] tio 3.9
[15:10:51.502] Press ctrl-t q to quit
[15:10:51.503] Connected to /dev/ttyUSB0</nowiki>

Start the system you are testing. If your setup is configured correctly, you should see coreboot logs begin to appear on the console, e.g.

<nowiki>
coreboot-57e26bdcd9 Wed May 27 19:45:28 UTC 2026 romstage starting (log level: 6)...
...WARM RESET...

board_reset() called!
system_reset() called!

coreboot-57e26bdcd9 Wed May 27 19:45:28 UTC 2026 romstage starting (log level: 6)...
SPD: Socket 0, Channel 0, Dimm 0
SPD: Socket 0, Channel 0, Dimm 1
...</nowiki>

== Internal Serial Headers ==
[[File:Dtkintel_ateverex.jpg|thumb|The DTK/Intel and AT/Everex serial header pinouts]]
If your machine has an external serial port, it virtually certainly uses the DE-9 Male DTE-side connector shown above (left, blue). If you have an internal serial port, you can use an adapter (typically in place of an an unused PCI slot's slot cover) to add one of these external connectors to your system. Unfortunately, while the external connector is standard, there are ''two'' incompatible common internal header pinouts - DTK/Intel and AT/Everex both using the same 10-pin 2.54mm-pitch IDC connector. You will need an adapter wired properly for the connector on your motherboard - most boards supported in coreboot-15h are AT/Everex, but you should check your manual before connecting an adapter to a motherboard of unknown pinout.

If you are purchasing an adapter, make sure the seller specifies which type it is, and that it matches which one you need. A seemingly-"defective" adapter, sold without a clearly-specified pinout, is sometimes simply the wrong pinout for your board.

== But what IS a Null Modem? ==
[[File:Null modem.jpg|thumb|A null modem adapter]]
RS-232 is a standard from the 1960s, and it was primarily designed for connecting communications equipment which would carry data a long distance (primarily modems) to the terminal equipment which the user operated (such as teletypes, terminals, and computers). As such, RS-232 defines two types of device - Data Communications Equipment (DCE) and Data Terminal Equipment (DTE), and ordinarily assumes you are using it to connect a DTE (like your computer) to a DCE (like a modem). Because they were intended to connect to computers (DTEs), RS-232 peripherals which were not "communications" devices (serial mice, printers, cameras, etc) were also wired as DCEs.

Any two serial devices - DCE or DTE - can communicate, provided one's RX (Receive) pin is wired to the other's TX (Transmit) pin, and vice-versa. The difference between DCE and DTE is simply that where a DCE's connector has its TX pin, the DTE's connector has its RX pin, and vice-versa. This means that a simple straight-through cable (pin 1 to pin 1, pin 2 to pin 2, etc.) will work to connect a DCE to a DTE.

You, however, are not connecting a modem to your computer - you're connecting a computer (running coreboot, to debug) to your computer (where you will view the logs). Since these are both DTEs, this will not work with a straight-through cable - you need a null modem, which is simply an adapter that swaps the RX and TX pins, allowing two DTEs or two DCEs to communicate with eachother despite their RX/TX wiring. The adapter is a "modem" in the sense that RS-232 assumes that a pair of DTEs (computers) will always communicate through a pair of DCEs (their respective modems, via the network connecting the modems), and the adapter's wiring provides the RX/TX swap that these back-to-back modems would.

To add to the confusion, some ''cables'' are themselves wired as a null modem, and serial cables are frequently not labelled as either straight-through or null-modem. Two null modems in a row acts as a straight-through cable - if you have a null modem cable, you should NOT use a null modem adapter between two DTEs (i.e. for coreboot debugging). Some null modem adapters and cables also cross the hardware flow control pins of the serial ports. Hardware flow control is generally unused in coreboot debugging, and the presence or lack of this functionality can generally be ignored.

External RS-232 ports on "modern" (post-1996-ish) PCs are typically female DE-9 connectors, but DCE and DTE have nothing to do with male and female connectors - either device can have either type of connector, and cables and adapters are available in all combinations.

== Compatibility ==
Serial debugging can be used on most motherboards with a serial port in their rear I/O, or on a serial header. However, on some motherboards (particularly those with [[BMC]]s), the external serial port(s) may not be usable for coreboot console, or may work only when the BMC is enabled and running.

The following boards are known to have WORKING serial coreboot console:
* [[ASUS KGPE-D16]]
* [[ASUS KCMA-D8]]
* [[Supermicro H8DGi]]
* [[Supermicro H8QG6]]

The following boards are known to have BROKEN serial coreboot console:
* [[Supermicro H8SGL]]
* [[Supermicro H8SCM]]
* [[Supermicro H8SML]]

If your board is not listed here, find it on the [[Motherboards]] page and consult its own wiki page. In general, motherboards which have an officially-documented serial port (external or internal), which do not have a BMC, and which use an ordinary Super I/O (as opposed to a laptop-style EC), will almost always have a working serial console.

File:Dtkintel ateverex.jpg

2026-10-01T07:43:51Z

Dodoid:

File:Serialheader.jpg

2026-10-01T07:29:18Z

Dodoid:

Build Guide

2026-10-01T04:51:58Z

Dodoid: Fix unfinished sentence

[[File:Komos_sabertooth.png|thumb|[[Komos]] - a build using the [[AM3+]] [[Sabertooth 990FX R2.0]]]]
Since you're reading the 15h.org build guide, we'll assume you're interested in building a fully-FOSS-firmware-compatible AMD system to run [[coreboot-15h]]. This guide assumes you're looking to build a new desktop, server, or workstation system from separately-purchased components.

If you are ''not'' building from separate components (such as for the various prebuilt [[Supermicro]] servers which included compatible motherboards), head over to the [[Motherboards]] page and look for your board's model. For laptops, see the [[Laptops]] page.

== Choosing a Platform ==
coreboot-15h is available for many motherboards, across several different AMD sockets - which one you should choose depends on the balance of performance, cost, power consumption, and physical size you want for your system.

[[#Building with AM3+|Choose AM3+]] if you are looking for higher single-thread performance in a desktop or gaming system with up to 8 cores and 64GB of memory. Desktop users will generally find high-clocking AM3+ systems "feel" faster than lower-clocking server platforms, and they are likely to perform better in gaming and web browsing.

[[#Building with G34|Choose G34]] if you are building a server or workstation system requiring higher multicore performance (at the cost of lower single-thread performance). Most G34 motherboards are dual-socket (up to 32 cores, 512GB RAM), but boards with 1 (up to 16 cores, 256 GB RAM) and 4 (up to 64 cores, 1TB RAM) sockets are also available.

[[#Building with C32|Choose C32]] for a middle-ground between these - 1 or 2 sockets, up to 16 cores, clockspeeds in between AM3+ and G34, and up to 512GB of RAM.

All of these platforms support ECC memory, IOMMU, SLAT, PCI-e ACS and are based on [[Orochi]] - AMD's high-power, high-performance platform for [[Family 15h]] systems. If you're looking to build a lower-power quad-core system (such as for an efficient router or media player machine), you may be interested in a [[Trinity|Trinity/Richland]] or [[Kabini]] APU instead. For these, choose an [[FM2]] board for midrange desktop systems, or [[AM1]] for low-power systems with lightweight applications although please note that the AM1 currently lacks a functional IOMMU.

It is recommended to purchase later revision boards without visible dust buildup as they will likely be in better condition.

== Building with AM3+ ==
coreboot-15h supports [[Socket AM3+]] on the ASUS [[Sabertooth 990FX R2.0]] and [[Crosshair V Formula-Z]]. The fastest AM3+ is the 8-core FX-9590. This platform uses DDR3 UDIMM (ordinary desktop RAM) in the usual dual-channel, 2-DIMM-per-channel configuration, and also optionally supports (UDIMM) ECC memory - DIMMs up to 16GB each are supported, for up to 64GB total.

As a consumer gaming platform, CPU coolers for AM3+ are common and still widely-available.

Unlike modern desktop CPUs (and other CPUs of its time), AM3+ is PGA socket, with pins on the CPU and holes in the socket. Be careful to avoid bending pins on the CPU during installation and removal. The socket on the motherboard is typically harder to damage.

AM3+ is currently the best option if you desire a comparatively fast libre firmware system for playing your proprietary games or 3D applications.

== Building with G34 ==
[[File:Qubesotron_2026.jpeg|thumb|[[Qubesotron]] - a build using the [[G34]] [[KGPE-D16]]]]

[[Socket G34]], usually on the [[ASUS KGPE-D16]], is probably the most popular and best-known platform for FOSS firmware on AMD systems. G34 motherboards were made with 1, 2, and 4 sockets, and coreboot-15h supports boards covering all of these configurations. The fastest G34 CPU is the 16-core Opteron 6386 SE, and UDIMM, RDIMM, and LRDIMM memory are all supported. Each CPU supports 4 memory channels, and all coreboot-15h-supported boards are 2-DIMM-per-channel. RDIMMs up to 32GB, or LRDIMMs up to 64GB each, are both supported. Despite this, two 32GB RDIMMs can be used per channel, versus only one 64GB LRDIMM - this means that the memory limit is 256 GB per socket, whether you use RDIMM or LRDIMM memory. RDIMM is generally the fastest, least-expensive and most-compatible option.

Good G34 CPU coolers can be difficult to find - many G34 servers used passive CPU coolers reliant on specific fan and baffle arrangements, which are not easily adapted for standard PC cases in custom-built systems. A list of relevant CPU coolers is available on the [[Coolers]] page - the rare Noctua G34 coolers are well-regarded and highly-prized, while Dynatron active server coolers are sometimes still available used. Depending on what you can find, it may be easier to [[Cooler_Adapter|adapt a modern CPU cooler to fit]] instead.

G34 CPUs use LGA sockets, like Intel or newer AMD CPUs. This generally makes the CPU less fragile, but the socket on the motherboard more so. As with modern PC hardware, if you purchase a G34 motherboard without CPUs installed, inspect its sockets closely for bent, damaged, or dirty pins and the CPU for damage to the components or contacts on the bottom.

There are several pre-built KGPE-D16 systems commonly available with low wear such as the Barracuda Opteron G34 which may be a good choice as they already come with the hard to find heatsinks and 16 core CPU's.

== Building with C32 ==
[[Socket C32]] motherboards covering both 1 and 2 socket configurations are supported. The fastest C32 CPU is the 8-core Opteron 4386, and UDIMM, RDIMM, and LRDIMM memory are all supported. Each CPU supports 2 memory channels, and all coreboot-15h-supported boards are 2-DIMM-per-channel. Unlike with G34, C32 CPUs support 64GB LRDIMMs in ''all'' slots - this means that, despite having half as many slots, C32 motherboards surprisingly support the same 256 GB per socket as G34, albeit with fewer channels.

C32 CPUs use LGA sockets, like Intel or newer AMD CPUs. This generally makes the CPU less fragile, but the socket on the motherboard more so. As with modern PC hardware, if you purchase a C32 motherboard without CPUs installed, inspect its sockets closely for bent, damaged, or dirty pins.

Socket F 3.5 pitch coolers can be used for C32 and can be far more affordable and more widely available new, see the [[Coolers]] page for more information.

Some early revision Socket C32 motherboards only support the 41xx CPU and should be avoided.

== PCI Express Devices ==
[[File:PM1725a.jpg|thumb|A Samsung PM1725a HHHL SSD - note the PCIe x8 card edge]]

The [[Family 15h]] and [[Family 16h]] platforms supported by coreboot-15h support up to PCI Express 2.0 ("Gen2") - a single Gen2 x16 slot delivers 8 GB/s of bandwidth. Compared to newer platforms, this can be a notable limitation for bandwidth-intensive devices such as GPUs or NVMe storage. For this reason, it's a good idea to select PCIe devices with more lanes whenever possible.

{| class="wikitable" style="text-align:left"
|+ PCI Express link performance
|- style="line-height:120%"
! scope="col" rowspan=2 | Version
! scope="col" rowspan=2 | Year introduced
! scope="col" rowspan=2 colspan=2 | Line code
! scope="col" rowspan=2 | Transfer rate<br>(per lane)
! scope="col" colspan=5 | Throughput (GB/s)
|-
! scope="col" | x1
! scope="col" | x2
! scope="col" | x4
! scope="col" | x8
! scope="col" | x16
|-
! scope="row" | 1.0
| 2003
| rowspan=5 | NRZ
| rowspan=2 | 8b/10b
| 2.5 GT/s
| {{shade|1.25|0.25|align=left}}
| {{shade|2.5|0.5|align=left}}
| {{shade|5|1|align=left}}
| {{shade|10|2|align=left}}
| {{shade|20|4|align=left}}
|-
! scope="row" | 2.0
| 2007
| 5.0 GT/s
| {{shade|2.5|0.5|align=left}}
| {{shade|5|1|align=left}}
| {{shade|10|2|align=left}}
| {{shade|20|4|align=left}}
| {{shade|40|8|align=left}}
|-
! scope="row" | 3.0
| 2010
| rowspan=3 | 128b/130b
| 8.0 GT/s
| {{shade|4.925|0.985|align=left}}
| {{shade|9.845|1.969|align=left}}
| {{shade|19.69|3.938|align=left}}
| {{shade|39.385|7.877|align=left}}
| {{shade|78.77|15.754|align=left}}
|-
! scope="row" | 4.0
| 2017
| 16.0 GT/s
| {{shade|9.485|1.969|align=left}}
| {{shade|19.69|3.938|align=left}}
| {{shade|39.385|7.877|align=left}}
| {{shade|78.77|15.754|align=left}}
| {{shade|157.54|31.508|align=left}}
|-
! scope="row" | 5.0
| 2019
| 32.0 GT/s
| {{shade|19.69|3.938|align=left}}
| {{shade|39.385|7.877|align=left}}
| {{shade|78.77|15.754|align=left}}
| {{shade|157.54|31.508|align=left}}
| {{shade|315.075|63.015|align=left}}
|}

This table shows the throughput of all PCIe lane widths, from Gen1 through Gen5. The advantages of additional PCIe lanes on a Gen2 chipset should be clear - a Gen2 x16 link provides comparable bandwidth to a Gen3 x8, or a Gen4 x4.

Extended PCI-e features such as Above 4G Decoding, Large/Resizable BAR, SR-IOV and ATS are currently not supported by 15h coreboot but could potentially be added in the future as the chipset should support them.

PCI-e ACS is fully supported with the excellent IOMMU groups required by Qubes/Xen and VFIO device assignment.

=== Networking Cards: ===
Almost any modern networking device should be compatible if it doesn't require large BAR support:

Most 15h workstation/server boards come with dual onboard Intel 82574L interfaces, since they do not feature an on-board flash chip they are safer for direct device assignment performed without the use of SR-IOV. Not assigning the ROM BAR to the guest may improve security for direct-attach.

'''1Gbps:'''

'''Intel i350:'''

This bridgeless and switchless PCI-e device is available used and new in a variety of different configurations if you desire additional 1Gbps ports or the use of SR-IOV when it is eventually added.

The dual port i350 may be able to enable SR-IOV with 15h coreboots outdated "resource allocater v3" as the BAR fits inside the small provided host bus window.

It is advised to use an intel firmware tool to ensure that iPXE/iSCSI is disabled on the re-writable ROM.

'''Broadcom BCM5719:'''

Considered a more free device than the i350 as substantially more logic is performed by the host loaded firmware instead of the card ROM. FOSS firmware has been developed for the RaptorCS Talos 2 LOM's which should also work in independent 5719 PCI-e cards for iPXE or BMC communication.

Removing the firmware from the card and locking the flash is considered best for security as the Linux drivers should provide general functionality without it and would likely make this the most secure option.

https://github.com/meklort/bcm5719-fw

https://github.com/meklort/bcm5719-fw/issues/232 (includes a list of card part numbers)

'''Intel 82576:'''

The quad port '''82576''' supports SR-IOV but it is a switched design and thus requires larger amounts of resources, their use could result in your graphics devices not receiving the proper BAR's. Security and flexibility is also reduced as each pair of ports shares an IOMMU group.

'''10Gbps:'''

(10/40 Cards without large BAR requirements, binary blobs or re-writable on-board firmware required for basic functionality should be listed here.)

TBD

'''25/40Gbps:'''

TBD

=== GPUs ===
Most high-end PCIe GPUs (old and new) support using all 16 lanes, but certain newer midrange cards are x8 or x4 and could potentially limit your 3D performance when limited to PCI-e 2.0

Newer cards will likely be highly CPU limited on the fastest available 15h CPU's.

''Recommended cards:''

AMD Polaris as the last generation of graphics cards without the vPSP, such as the Radeon RX590 8GB, the single slot Radeon Pro WX 7100 8GB or the low profile WX 4100.

Although the vPSP is restricted by the IOMMU and has nowhere near the level of access of it's mainboard counterparts it does prevent the theoretical development of owner controlled firmware for a video card which is already considered a very complex undertaking.

If you do not care about that or consider the claim of the vPSP theoretically preventing hostile internal firmware re-writes as a benefit then potentially a newer x16 card could be purchased.

=== NVMe SSDs ===
[[File:M.2 Adapter.webp|thumb|A common generic M.2 adapter card kit. The bottom slot is for PCIe M.2 drives, the top slot (and cable) are for SATA M.2 drives.]]

Few motherboards supported by coreboot-15h have built-in M.2 slots. However, a PCIe M.2 SSD can be used in a PCIe slot using a common NVMe-to-x4 adapter card (many also allow an additional M.2 SATA SSD to be connected to a SATA port). A Gen2 x4 slot provides 2 GB/s of PCIe bandwidth - if your SSD's sequential read and write speeds are below 2000 MB/s, PCIe 2.0 will not bottleneck it. However, many NVMe SSDs are capable of more.

The D16 systems support PCI-e Bifurcation via the staging branch with an x16 slot convertible to x8/x8 in menuconfig thus making a four slot NVMe Cassette able to use two cards in position one and three.

It has yet to be added to the D8 but it should also work on this platform or any other with an electrical x16 slot.

Higher NVMe bandwidth on these platforms requires a directly attached SSD with more than 4 PCIe lanes - since the M.2 connector is only x4, this means using an AIC (Add-In Card)-format SSD, which installs directly in a PCIe slot. The following AIC SSDs are known to be capable of more than 2000 MB/s sequential throughput over at least 8 PCIe lanes:

{| class="wikitable sortable"
|+ Add-In Card SSD examples:
|-
! Model !! Capacity !! PCIe Width !! Sequential Read (MB/s) !! Sequential Write (MB/s) !! Random Read IOPS !! Random Write IOPS
|-
| Samsung PM1725a HHHL || 1.6/3.2/6.4 TB || x8 (up to Gen3) || 6200 (~3600 on Gen2) || 2600 || 1,000,000 || 180,000
|-
| Samsung PM1735a HHHL || 1.6/3.2/6.4/12.8 TB || x8 (up to Gen4) || 7000 (~3600 on Gen2) || 3200 || 800,000 || 135,000
|}
Another choice is a four slot switched NVMe PCI-e x16 card as this would enable the full usage of multiple modern PCI-e x4 SSD's with an oversubscribed PCI-e 2.0 x16 uplink if the switch supports lane rate conversion on the uplink. If you wish to assign NVMe devices to virtual machines one at a time the switch must also support ACS.

Northbridge adapters can also be used and in a single oversubscribed x4 link could add both NVMe holders and several of the controllers that you may be missing such as USB 3.0 and SATA 6Gbps at a more affordable price than purchasing separate expansion cards.

File:FlashkeeperPresentation.pdf

2026-09-25T16:22:50Z

Dodoid:

Template:Infobox motherboard

2026-09-18T13:20:15Z

Dodoid: Multiple USB and Storage Controllers

{{ infobox
| aboveclass = fn
| above = {{{name|<includeonly>{{PAGENAMEBASE}}</includeonly>}}}
| abovestyle = background-color:#C0C0C0; padding:4px; text-align:center; font-size:1.35em
| bodyclass = hproduct
| bodystyle = width:25em
| image = {{#invoke:InfoboxImage|InfoboxImage|image={{{image|}}}|size={{{image_size|}}}|sizedefault=frameless|alt={{{alt|}}}|upright={{{upright|1.25}}}|suppressplaceholder=yes}}
| captionstyle = font-size: 95%; font-style: italic;
| caption = {{{caption|}}}
| headerstyle = background-color: #C0C0C0

| header1 = Overview

| label2 = Introduced
| data2 = {{{introduced|}}}

| label3 = Manufacturer
| data3 = {{{manufacturer|}}}

| header4 = Specifications

| label5 = [[Socket]]
| data5 = {{{socket|}}}

| label6 = [[Northbridge]]
| data6 = {{{northbridge|}}}

| label7 = [[Southbridge]]
| data7 = {{{southbridge|}}}

| label8 = [[FCH|Chipset]]
| data8 = {{{fch|}}}

| label9 = [[Super I/O]]
| data9 = {{{superio|}}}

| label10 = [[BMC]]
| data10 = {{{bmc|}}}

| label11 = BMC Flash Location
| data11 = {{{bmcflash|}}}

| label12 = Memory
| data12 = {{{ram|}}}

| label13 = [[BIOS Flash]]
| data13 = {{{bios|}}}

| label14 = Form Factor
| data14 = {{{formfactor|}}}

| label15 = Power Inputs
| data15 = {{{power|}}}

| label16 = Expansion Slot{{ #if: {{{slot2|}}}|s}}
| data16 = {{unbulleted list
| {{{slot1|}}}
| {{{slot2|}}}
| {{{slot3|}}}
| {{{slot4|}}}
| {{{slot5|}}}
| {{{slot6|}}}
| {{{slot7|}}}
| {{{slot8|}}}
| {{{slot9|}}}
| {{{slot10|}}}
}}

| header17 = Onboard Peripherals

| label18 = Graphics Adapter
| data18 = {{{gpu|}}}

| label19 = Network Interface
| data19 = {{{nic|}}}

| label20 = Storage Controller{{ #if: {{{storagecontroller22|}}}|s}}
| data20 = {{unbulleted list
| {{{storagecontroller|}}}
| {{{storagecontroller2|}}}
| {{{storagecontroller3|}}}
| {{{storagecontroller4|}}}
}}

| label21 = USB Controller{{ #if: {{{usbcontroller2|}}}|s}}
| data21 = {{unbulleted list
| {{{usbcontroller|}}}
| {{{usbcontroller2|}}}
| {{{usbcontroller3|}}}
| {{{usbcontroller4|}}}
}}

| label22 = Serial Interface
| data22 = {{{serial|}}}

| label23 = Audio Interface
| data23 = {{{audio|}}}

}}<noinclude>{{documentation}}</noinclude>

Rules

2026-09-14T16:37:41Z

Dodoid: Redirected page to Matrix#Rules for the 15h.org Matrix Room

#REDIRECT [[Matrix#Rules for the 15h.org Matrix Room]]

Matrix

2026-09-14T16:36:01Z

Dodoid: change to heading to allow redirect to section

The 15h.org community began as a '''[https://matrix.org Matrix]''' room, originally named '''The D16 Club''' , and originally focused specifically on the [[KGPE-D16]]. The room is now open to the public, and open to discussion of all hardware for FOSS firmware, as well as of 15h.org itself.

[https://matrix.to/#/!OkpUfvLEYpLyALVvaW:dodoid.com?via=matrix.org Click Here] to join the Matrix room via your client of choice. Consider letting us know how you heard about us, as well as what relevant hardware you have or want.

== Rules for the 15h.org Matrix Room ==
* Any discussion related to technology is welcome
* No harassing room members or hostile dialogue
* No spamming the room or room members

Evil Qubesotron

2026-09-04T07:18:03Z

Dodoid: Created page with "{{Infobox individual system |name = Evil Qubesotron |owner = Dodoid |built = Frantically, following Qubesotron's issues |motherboard = ASUS PRIME X299-A |cpu = Intel Core i7 7820X |gpu = AMD Radeon Pro W5500 |ram = 48GB assorted DDR4 |storage1 = 2x 1.6TB Samsung PM1725a Enterprise HHHL NVMe SSD |psu = Thermaltake SMART Series 700W |chassis = Cooler Master Storm Enforcer |cooler = Hyper 212 Evo |nic = Onboard |firmware = Stock AMI Firmware |p..."

{{Infobox individual system
|name = Evil Qubesotron
|owner = Dodoid
|built = Frantically, following Qubesotron's issues

|motherboard = ASUS PRIME X299-A
|cpu = Intel Core i7 7820X
|gpu = AMD Radeon Pro W5500
|ram = 48GB assorted DDR4
|storage1 = 2x 1.6TB Samsung PM1725a Enterprise HHHL NVMe SSD
|psu = Thermaltake SMART Series 700W
|chassis = Cooler Master Storm Enforcer
|cooler = Hyper 212 Evo
|nic = Onboard

|firmware = Stock AMI Firmware
|payload = Some Kinda UEFI
|oproms = you bet
|os = Debian Stable
|filesystem = ZFS
|workload = "oh shit"
}}

'''Evil Qubesotron''' is the temporary host of 15h.org while [[Qubesotron]] is down.

Home

2026-08-24T19:35:02Z

Dodoid:

{{Excerpt|Showcase|hat=no|templates=Infobox, Excerpt}}

Welcome to 15h.org, a resource for documentation and open source support for AMD's [[Family 15h]] (fam15h) and other related processors and platforms.

{| class="wikitable" style=""
| style="width: 33.33%"| {{center|'''🖥️ Get Started with Hardware'''}}
| style="width: 33.33%"| {{center|'''⚙️ Build your Firmware'''}}
| style="width: 33.33%"| {{center|'''👋 Join Us!'''}}
|-
|
* [[Build Guide]]
* [[Motherboards]]
* [[Coolers|CPU Coolers]]
|
* [[coreboot-15h]]
* [[External Flashing]]
* [[EHCI Debugging]]
* [https://git.15h.org/explore/repos Browse our Git forge]
|
* Join us on [[Matrix]]
* [[Editing This Wiki|Edit this wiki!]]
* [[Add your build]]
* [[Community Todo List]]
|-
|colspan=3|
{{center|'''📰 News'''}}
<div class="blogembed" style="text-align: center;">
{{Excerpt|News|Posts|subsections=yes|hat=no|only=templates|templates=1-3}}
</div><br>
|} __NOTOC__

=== Why 15h? ===
Released between 2011 and 2014, AMD's [[fam15h]] (and its approximately-contemporaneous relatives, [[fam10h]], [[fam14h]] and [[fam16h]]) are the final high-performance x86_64 microprocessors lacking most of the limitations newer x86 platforms are encumbered by. In many cases, fam15h hardware can provide a performant, full-featured system, using entirely free and open source software. It enforces no firmware signing (allowing things such as [[coreboot]]), can be booted entirely with free firmware (including memory initialization), and it requires no privileged management coprocessor (such as the Platform Security Processor or Management Engine, found on newer AMD and Intel platforms respectively). Where a [[Board Management Controller]] is present, it can usually reliably disabled, or better yet, flashed with [[OpenBMC]]. On fam10h, even microcode is unencrypted and unsigned, and can be modified by the user.

Beyond their currently-unparalleled degree of firmware freedom for a modern x86_64 platform, AMD hardware of this era (in particular, 6200 and 6300-series [[Opteron]] platforms) remains a powerful and cost-effective option for many systems, especially under parallel workloads. Despite this, the comparative popularity of competing Intel processors during this era has limited the familiarity and uptake of these pre-Zen AMD platforms among many enthusiasts.

If you are looking for an x86_64 platform under your complete control, this website serves to demystify fam15h and its relatives, so that these systems can remain in operation well into the future.

=== What hardware was that again? ===
Robust support for coreboot on select fam15h motherboards has been developed and thoroughly tested at 15h.org. The current, production ready motherboards are [[KGPE-D16]], [[KCMA-D8]], [[H8QG6]], [[H8SGL]], and [[H8SCM]]. A handful of other fam15h motherboards have [[Motherboards|preliminary support]]. For these motherboards, the [[Bulldozer]] and [[Piledriver]] microarchitectures are supported by [[coreboot-15h]].


{{:Board Grid}}

Build Guide

2026-08-24T01:23:16Z

Dodoid: recommend RDIMM

Build Guide

2026-08-24T00:47:51Z

Dodoid: CPUs don't directly handle PCIe on most 15h

PCI Express

2026-08-24T00:47:03Z

Dodoid: Redirected page to Build Guide#PCI Express Devices

#REDIRECT [[Build_Guide#PCI_Express_Devices]]

Build Guide

2026-08-24T00:45:44Z

Dodoid:

File:PM1725a.jpg

2026-08-24T00:35:13Z

Dodoid:

File:M.2 Adapter.webp

2026-08-24T00:15:57Z

Dodoid:

Module:Color

2026-08-23T23:44:53Z

Dodoid: Created page with "-- Introduction: https://colorspace.r-forge.r-project.org/articles/color_spaces.html local p = {} local function isempty(v) return v == nil or v == '' end local function hexToRgb(color) local cleanColor = color:gsub("#", "#"):match('^[%s#]*(.-)[%s;]*$') if (#cleanColor == 6) then return { r = tonumber(string.sub(cleanColor, 1, 2), 16), g = tonumber(string.sub(cleanColor, 3, 4), 16), b = tonumber(string.sub(cleanColor, 5, 6), 16) } elseif (#cleanCo..."

-- Introduction: https://colorspace.r-forge.r-project.org/articles/color_spaces.html

local p = {}

local function isempty(v)
return v == nil or v == ''
end

local function hexToRgb(color)
local cleanColor = color:gsub("#", "#"):match('^[%s#]*(.-)[%s;]*$')
if (#cleanColor == 6) then
return {
r = tonumber(string.sub(cleanColor, 1, 2), 16),
g = tonumber(string.sub(cleanColor, 3, 4), 16),
b = tonumber(string.sub(cleanColor, 5, 6), 16)
}
elseif (#cleanColor == 3) then
return {
r = 17 * tonumber(string.sub(cleanColor, 1, 1), 16),
g = 17 * tonumber(string.sub(cleanColor, 2, 2), 16),
b = 17 * tonumber(string.sub(cleanColor, 3, 3), 16)
}
end
error("Invalid hexadecimal color " .. cleanColor, 1)
end

p._hexToRgb = hexToRgb

local function round(v)
if (v < 0) then
return math.ceil(v - 0.5)
else
return math.floor(v + 0.5)
end
end

local function rgbToHex(r, g, b)
return string.format("%02X%02X%02X", round(r), round(g), round(b))
end

p._rgbToHex = rgbToHex

local function rgbToCmyk(r, g, b)
if (r > 255 or g > 255 or b > 255 or r < 0 or g < 0 or b < 0) then
error("Color level out of bounds")
end
local c = 1 - r / 255
local m = 1 - g / 255
local y = 1 - b / 255
local k = math.min(c, m, y)
if (k == 1) then
c = 0
m = 0
y = 0
else
local d = 1 - k
c = (c - k) / d
m = (m - k) / d
y = (y - k) / d
end
return { c = c * 100, m = m * 100, y = y * 100, k = k * 100 }
end

p._rgbToCmyk = rgbToCmyk

local function rgbToHsl(r, g, b)
if (r > 255 or g > 255 or b > 255 or r < 0 or g < 0 or b < 0) then
error("Color level out of bounds")
end
local channelMax = math.max(r, g, b)
local channelMin = math.min(r, g, b)
local range = channelMax - channelMin
local h, s
if (range == 0) then
h = 0
elseif (channelMax == r) then
h = 60 * ((g - b) / range)
if (h < 0) then
h = 360 + h
end
elseif (channelMax == g) then
h = 60 * (2 + (b - r) / range)
else
h = 60 * (4 + (r - g) / range)
end
local L = channelMax + channelMin
if (L == 0 or L == 510) then
s = 0
else
s = 100 * range / math.min(L, 510 - L)
end
return { h = h, s = s, l = L * 50 / 255 }
end

p._rgbToHsl = rgbToHsl

local function rgbToHsv(r, g, b)
if (r > 255 or g > 255 or b > 255 or r < 0 or g < 0 or b < 0) then
error("Color level out of bounds")
end
local channelMax = math.max(r, g, b)
local channelMin = math.min(r, g, b)
local range = channelMax - channelMin
local h, s
if (range == 0) then
h = 0
elseif (channelMax == r) then
h = 60 * ((g - b) / range)
if (h < 0) then
h = 360 + h
end
elseif (channelMax == g) then
h = 60 * (2 + (b - r) / range)
else
h = 60 * (4 + (r - g) / range)
end
if (channelMax == 0) then
s = 0
else
s = 100 * range / channelMax
end
return { h = h, s = s, v = channelMax * 100 / 255 }
end

p._rgbToHsv = rgbToHsv

-- c in [0, 255], condition tweaked for no discontinuity
-- http://entropymine.com/imageworsener/srgbformula/
local function toLinear(c)
if (c > 10.314300250662591) then
return math.pow((c + 14.025) / 269.025, 2.4)
else
return c / 3294.6
end
end

local function toNonLinear(c)
if (c > 0.00313066844250063) then
return 269.025 * math.pow(c, 1.0/2.4) - 14.025
else
return 3294.6 * c
end
end

local function srgbToCielchuvD65o2deg(r, g, b)
if (r > 255 or g > 255 or b > 255 or r < 0 or g < 0 or b < 0) then
error("Color level out of bounds")
end
local R = toLinear(r)
local G = toLinear(g)
local B = toLinear(b)
-- https://github.com/w3c/csswg-drafts/issues/5922
local X = 0.1804807884018343 * B + 0.357584339383878 * G + 0.41239079926595934 * R
local Y = 0.07219231536073371 * B + 0.21263900587151027 * R + 0.715168678767756 * G
local Z = 0.01933081871559182 * R + 0.11919477979462598 * G + 0.9505321522496607 * B
local L, C, h
if (Y > 0.00885645167903563082) then
L = 116 * math.pow(Y, 1/3) - 16
else
L = Y * 903.2962962962962962963
end
if ((r == g and g == b) or L == 0) then
C = 0
h = 0
else
d = X + 3 * Z + 15 * Y
if (d == 0) then
C = 0
h = 0
else
-- 0.19783... and 0.4631... computed with extra precision from (X,Y,Z) when (R,G,B) = (1,1,1),
-- in which case (u,v) ≈ (0,0)
local us = 4 * X / d - 0.19783000664283678994
local vs = 9 * Y / d - 0.46831999493879099801
h = math.atan2(vs, us) * 57.2957795130823208768
if (h < 0) then
h = h + 360
elseif (h == 0) then
h = 0 -- ensure zero is positive
end
C = math.sqrt(us * us + vs * vs) * 13 * L
if (C == 0) then
C = 0
h = 0
end
end
end
return { L = L, C = C, h = h }
end

p._srgbToCielchuvD65o2deg = srgbToCielchuvD65o2deg

local function srgbMix(t, r0, g0, b0, r1, g1, b1)
if (t > 1 or t < 0) then
error("Interpolation parameter out of bounds")
end
if (r0 > 255 or g0 > 255 or b0 > 255 or r1 > 255 or g1 > 255 or b1 > 255 or r0 < 0 or g0 < 0 or b0 < 0 or r1 < 0 or g1 < 0 or b1 < 0) then
error("Color level out of bounds")
end
local tc = 1 - t
return {
r = toNonLinear(tc * toLinear(r0) + t * toLinear(r1)),
g = toNonLinear(tc * toLinear(g0) + t * toLinear(g1)),
b = toNonLinear(tc * toLinear(b0) + t * toLinear(b1))
}
end

local function formatToPrecision(value, p)
return string.format("%." .. p .. "f", value)
end

local function getFractionalZeros(p)
if (p > 0) then
return "." .. string.rep("0", p)
else
return ""
end
end

function p.hexToRgbTriplet(frame)
local args = frame.args or frame:getParent().args
local hex = args[1]
if (hex) then
local rgb = hexToRgb(hex)
return rgb.r .. ', ' .. rgb.g .. ', ' .. rgb.b
else
return ""
end
end

function p.rgbTripletToHex(frame)
local args = frame.args or frame:getParent().args
local r = tonumber(args[1])
local g = tonumber(args[2])
local b = tonumber(args [3])
if (isempty(r) or isempty(g) or isempty(b)) then
return ""
else
return rgbToHex(r,g,b)
end
end

function p.hexToCmyk(frame)
local args = frame.args or frame:getParent().args
local hex = args[1]
if (hex) then
local p = tonumber(args.precision) or 0
local s = args.pctsign or "1"
local rgb = hexToRgb(hex)
local cmyk = rgbToCmyk(rgb.r, rgb.g, rgb.b)
local fk = formatToPrecision(cmyk.k, p)
local fc, fm, fy
local fracZeros = getFractionalZeros(p)
if (fk == 100 .. fracZeros) then
local fZero = 0 .. fracZeros
fc = fZero
fm = fZero
fy = fZero
else
fc = formatToPrecision(cmyk.c, p)
fm = formatToPrecision(cmyk.m, p)
fy = formatToPrecision(cmyk.y, p)
end
if (s ~= "0") then
return fc .. "%, " .. fm .. "%, " .. fy .. "%, " .. fk .. "%"
else
return fc .. ", " .. fm .. ", " .. fy .. ", " .. fk
end
else
return ""
end
end

function p.hexToHsl(frame)
local args = frame.args or frame:getParent().args
local hex = args[1]
if (hex) then
local p = tonumber(args.precision) or 0
local rgb = hexToRgb(hex)
local hsl = rgbToHsl(rgb.r, rgb.g, rgb.b)
local fl = formatToPrecision(hsl.l, p)
local fs, fh
local fracZeros = getFractionalZeros(p)
local fZero = 0 .. fracZeros
if (fl == fZero or fl == 100 .. fracZeros) then
fs = fZero
fh = fZero
else
fs = formatToPrecision(hsl.s, p)
if (fs == fZero) then
fh = fZero
else
fh = formatToPrecision(hsl.h, p)
if (fh == 360 .. fracZeros) then
fh = fZero -- handle rounding to 360
end
end
end
return fh .. "°, " .. fs .. "%, " .. fl .. "%"
else
return ""
end
end

function p.hexToHsv(frame)
local args = frame.args or frame:getParent().args
local hex = args[1]
if (hex) then
local p = tonumber(args.precision) or 0
local rgb = hexToRgb(hex)
local hsv = rgbToHsv(rgb.r, rgb.g, rgb.b)
local fv = formatToPrecision(hsv.v, p)
local fs, fh
local fracZeros = getFractionalZeros(p)
local fZero = 0 .. fracZeros
if (fv == fZero) then
fh = fZero
fs = fZero
else
fs = formatToPrecision(hsv.s, p)
if (fs == fZero) then
fh = fZero
else
fh = formatToPrecision(hsv.h, p)
if (fh == 360 .. fracZeros) then
fh = fZero -- handle rounding to 360
end
end
end
return fh .. "°, " .. fs .. "%, " .. fv .. "%"
else
return ""
end
end

function p.hexToCielch(frame)
local args = frame.args or frame:getParent().args
local hex = args[1]
if (hex) then
local p = tonumber(args.precision) or 0
local rgb = hexToRgb(hex)
local LCh = srgbToCielchuvD65o2deg(rgb.r, rgb.g, rgb.b)
local fL = formatToPrecision(LCh.L, p)
local fC, fh
local fracZeros = getFractionalZeros(p)
local fZero = 0 .. fracZeros
if (fL == fZero or fL == 100 .. fracZeros) then
fC = fZero
fh = fZero
else
fC = formatToPrecision(LCh.C, p)
if (fC == fZero) then
fh = fZero
else
fh = formatToPrecision(LCh.h, p)
if (fh == 360 .. fracZeros) then
fh = fZero -- handle rounding to 360
end
end
end
return fL .. ", " .. fC .. ", " .. fh .. "°"
else
return ""
end
end

function p.hexMix(frame)
local args = frame.args or frame:getParent().args
local hex0 = args[1]
local hex1 = args[2]
if (isempty(hex0) or isempty(hex1)) then
return ""
end
local t = tonumber(args[3])
if not t then
t = 0.5
else
local min = tonumber(args.min) or 0
local max = tonumber(args.max) or 100
if (min >= max) then
error("Minimum proportion greater than or equal to maximum")
elseif (t < min) then
t = 0
elseif (t > max) then
t = 1
else
t = (t - min) / (max - min)
end
end
local rgb0 = hexToRgb(hex0)
local rgb1 = hexToRgb(hex1)
local rgb = srgbMix(t, rgb0.r, rgb0.g, rgb0.b, rgb1.r, rgb1.g, rgb1.b)
return rgbToHex(rgb.r, rgb.g, rgb.b)
end

return p

Template:Color

2026-08-23T23:42:28Z

Dodoid: Created page with "{{<includeonly>safesubst:</includeonly>ifsubst|1=<span|2=<templatestyles src="Template:Color/styles.css" /><span class="tmp-color"}} style="color:{{{1|}}}">{{{2|{{{1|}}}}}}<includeonly></span></includeonly><noinclude>{{Documentation}}</noinclude>"

{{<includeonly>safesubst:</includeonly>ifsubst|1=<span|2=<templatestyles src="Template:Color/styles.css" /><span class="tmp-color"}} style="color:{{{1|}}}">{{{2|{{{1|}}}}}}<includeonly></span></includeonly><noinclude>{{Documentation}}</noinclude>

Template:Color/styles.css

2026-08-23T23:42:22Z

Dodoid: Created page with "/* {{pp-template}} */ /* phab:T360683: This stylesheet removes the function of this template in * dark mode */ @media screen { html.skin-theme-clientpref-night div:not(.notheme) > .tmp-color, html.skin-theme-clientpref-night p > .tmp-color, html.skin-theme-clientpref-night table:not(.notheme) .tmp-color { color: inherit !important; } } @media screen and ( prefers-color-scheme: dark) { /* automatic mode */ html.skin-theme-clientpref-os div:not(...."

/* {{pp-template}} */
/* [[phab:T360683]]: This stylesheet removes the function of this template in
* dark mode
*/

@media screen {
html.skin-theme-clientpref-night div:not(.notheme) > .tmp-color,
html.skin-theme-clientpref-night p > .tmp-color,
html.skin-theme-clientpref-night table:not(.notheme) .tmp-color {
color: inherit !important;
}
}

@media screen and ( prefers-color-scheme: dark) {
/* automatic mode */
html.skin-theme-clientpref-os div:not(.notheme) > .tmp-color,
html.skin-theme-clientpref-os p > .tmp-color,
html.skin-theme-clientpref-os table:not(.notheme) .tmp-color {
color: inherit !important;
}
}

Build Guide

2026-08-23T23:40:04Z

Dodoid:

Since you're reading the 15h.org build guide, we'll assume you're interested in building a fully-FOSS-firmware-compatible AMD system to run [[coreboot-15h]]. This guide assumes you're looking to build a new desktop, server, or workstation system from separately-purchased components.

If you are ''not'' building from separate components (such as for the various prebuilt [[Supermicro]] servers which included compatible motherboards), head over to the [[Motherboards]] page and look for your board's model. For laptops, see the [[Laptops]] page.

== Choosing a Platform ==
coreboot-15h is available for many motherboards, across several different AMD sockets - which one you should choose depends on

[[#Building with AM3+|Choose AM3+]] if you are looking for higher single-thread performance in a desktop or gaming system with up to 8 cores and 64GB of memory. Desktop users will generally find high-clocking AM3+ systems "feel" faster than lower-clocking server platforms, and they are likely to perform better in gaming and web browsing.

[[#Building with G34|Choose G34]] if you are building a server or workstation system requiring higher multicore performance (at the cost of lower single-thread performance). Most G34 motherboards are dual-socket (up to 32 cores, 512GB RAM), but boards with 1 (up to 16 cores, 256 GB RAM) and 4 (up to 64 cores, 1TB RAM) sockets are also available.

[[#Building with C32|Choose C32]] for a middle-ground between these - 1 or 2 sockets, up to 16 cores, clockspeeds in between AM3+ and G34, and up to 512GB of RAM.

All of these platforms support ECC memory, and are based on [[Orochi]] - AMD's high-power, high-performance platform for [[Family 15h]] systems. If you're looking to build a lower-power quad-core system (such as for an efficient router or media player machine), you may be interested in a [[Trinity|Trinity/Richland]] or [[Kabini]] APU instead. For these, choose an [[FM2]] board for midrange desktop systems, or [[AM1]] for low-power systems with lightweight applications.

== Building with AM3+ ==
coreboot-15h supports [[Socket AM3+]] on the ASUS [[Sabertooth 990FX R2.0]] and [[Crosshair V Formula-Z]]. The fastest AM3+ is the 8-core FX-9590. This platform uses DDR3 UDIMM (ordinary desktop RAM) in the usual dual-channel, 2-DIMM-per-channel configuration, and also optionally supports (UDIMM) ECC memory - DIMMs up to 16GB each are supported, for up to 64GB total.

As a consumer gaming platform, CPU coolers for AM3+ are common and still widely-available.

Unlike modern desktop CPUs (and other CPUs of its time), AM3+ is PGA socket, with pins on the CPU and holes in the socket. Be careful to avoid bending pins on the CPU during installation and removal. The socket on the motherboard is typically harder to damage.

== Building with G34 ==
[[Socket G34]], usually on the [[ASUS KGPE-D16]], is probably the most popular and best-known platform for FOSS firmware on AMD systems. G34 motherboards were made with 1, 2, and 4 sockets, and coreboot-15h supports boards covering all of these configurations. The fastest G34 CPU is the 16-core Opteron 6386 SE, and UDIMM, RDIMM, and LRDIMM memory are all supported. Each CPU supports 4 memory channels, and all coreboot-15h-supported boards are 2-DIMM-per-channel. RDIMMs up to 32GB, or LRDIMMs up to 64GB each, are both supported. Despite this, two 32GB RDIMMs can be used per channel, versus only one 64GB LRDIMM - this means that the memory limit is 256 GB per socket, whether you use RDIMM or LRDIMM memory.

Good G34 CPU coolers can be difficult to find - many G34 servers used passive CPU coolers reliant on specific fan and baffle arrangements, which are not easily adapted for standard PC cases in custom-built systems. A list of relevant CPU coolers is available on the [[Coolers]] page - the rare Noctua G34 coolers are well-regarded and highly-prized, while Dynatron active server coolers are sometimes still available used. Depending on what you can find, it may be easier to [[Cooler_Adapter|adapt a modern CPU cooler to fit]] instead.

G34 CPUs use LGA sockets, like Intel or newer AMD CPUs. This generally makes the CPU less fragile, but the socket on the motherboard more so. As with modern PC hardware, if you purchase a G34 motherboard without CPUs installed, inspect its sockets closely for bent, damaged, or dirty pins.

== Building with C32 ==
[[Socket C32]] motherboards covering both 1 and 2 socket configurations are supported. The fastest C32 CPU is the 8-core Opteron 4386, and UDIMM, RDIMM, and LRDIMM memory are all supported. Each CPU supports 2 memory channels, and all coreboot-15h-supported boards are 2-DIMM-per-channel. Unlike with G34, C32 CPUs support 64GB LRDIMMs in ''all'' slots - this means that, despite having half as many slots, C32 motherboards surprisingly support the same 256 GB per socket as G34, albeit with fewer channels.

C32 CPUs use LGA sockets, like Intel or newer AMD CPUs. This generally makes the CPU less fragile, but the socket on the motherboard more so. As with modern PC hardware, if you purchase a C32 motherboard without CPUs installed, inspect its sockets closely for bent, damaged, or dirty pins.

== PCI Express Devices ==
The [[Family 15h]] and [[Family 16h]] CPUs supported by coreboot-15h support up to PCI Express 2.0 ("Gen2"). A single Gen2x16 slot delivers Compared to newer platforms, this can be a notable limitation for bandwidth-intensive devices such as GPUs or NVMe storage. For this reason, it's a good idea to select PCIe devices with more lanes where possible. Most high-end PCIe GPUs (old and new) support using all 16 lanes, but certain newer midrange cards are x8 or x4.

{| class="wikitable" style="text-align:left"
|+ PCI Express link performance
|- style="line-height:120%"
! scope="col" rowspan=2 | Version
! scope="col" rowspan=2 | Year introduced
! scope="col" rowspan=2 colspan=2 | Line code
! scope="col" rowspan=2 | Transfer rate<br>(per lane)
! scope="col" colspan=5 | Throughput (GB/s)
|-
! scope="col" | x1
! scope="col" | x2
! scope="col" | x4
! scope="col" | x8
! scope="col" | x16
|-
! scope="row" | 1.0
| 2003
| rowspan=5 | NRZ
| rowspan=2 | 8b/10b
| 2.5 GT/s
| {{shade|0.25|align=left}}
| {{shade|0.5|align=left}}
| {{shade|1|align=left}}
| {{shade|2|align=left}}
| {{shade|4|align=left}}
|-
! scope="row" | 2.0
| 2007
| 5.0 GT/s
| {{shade|0.5|align=left}}
| {{shade|1|align=left}}
| {{shade|2|align=left}}
| {{shade|4|align=left}}
| {{shade|8|align=left}}
|-
! scope="row" | 3.0
| 2010
| rowspan=3 | 128b/130b
| 8.0 GT/s
| {{shade|0.985|align=left}}
| {{shade|1.969|align=left}}
| {{shade|3.938|align=left}}
| {{shade|7.877|align=left}}
| {{shade|15.754|align=left}}
|-
! scope="row" | 4.0
| 2017
| 16.0 GT/s
| {{shade|1.969|align=left}}
| {{shade|3.938|align=left}}
| {{shade|7.877|align=left}}
| {{shade|15.754|align=left}}
| {{shade|31.508|align=left}}
|-
! scope="row" | 5.0
| 2019
| 32.0 GT/s
| {{shade|3.938|align=left}}
| {{shade|7.877|align=left}}
| {{shade|15.754|align=left}}
| {{shade|31.508|align=left}}
| {{shade|63.015|align=left}}
|-
! scope="row" | 6.0
| 2022 (first implemented 2025)
| {{Nowrap|PAM-4}}<br />FEC
| 1b/1b<br />242B/256B FLIT
| 64.0 GT/s
| {{shade|7.563|align=left}}
| {{shade|15.125|align=left}}
| {{shade|30.25|align=left}}
| {{shade|60.5|align=left}}
| {{shade|121|align=left}}
|}

Template:Efn

2026-08-23T23:33:33Z

Dodoid: Created page with "<includeonly>{{safesubst<noinclude />:#if:{{{name|}}} |{{#tag:ref|{{{1|{{{reference|{{{content|{{{text|}}}}}}}}}}}}|name={{{name|}}}|group={{safesubst<noinclude />:#switch: {{{group|}}} | note | upper-alpha | upper-roman | lower-alpha | lower-greek | lower-roman = {{{group|}}} | #default = lower-alpha }}}} |{{#tag:ref|{{{1|{{{reference|{{{content|{{{text|}}}}}}}}}}}}|group={{safesubst<noinclude />:#switch: {{{group|}}} | note | up..."

<includeonly>{{safesubst<noinclude />:#if:{{{name|}}}
|{{#tag:ref|{{{1|{{{reference|{{{content|{{{text|}}}}}}}}}}}}|name={{{name|}}}|group={{safesubst<noinclude />:#switch: {{{group|}}}
| note
| upper-alpha
| upper-roman
| lower-alpha
| lower-greek
| lower-roman = {{{group|}}}
| #default = lower-alpha
}}}}
|{{#tag:ref|{{{1|{{{reference|{{{content|{{{text|}}}}}}}}}}}}|group={{safesubst<noinclude />:#switch: {{{group|}}}
| note
| upper-alpha
| upper-roman
| lower-alpha
| lower-greek
| lower-roman = {{{group|}}}
| #default = lower-alpha
}}}}
}}</includeonly><noinclude>
{{documentation}}
</noinclude>

Template:Efn-lr

2026-08-23T23:32:59Z

Dodoid: Created page with "<includeonly>{{efn|name={{{name|}}}|group=lower-roman|reference={{{1|{{{reference|{{{content|{{{text|}}}}}}}}}}}}}}</includeonly><noinclude>{{documentation}}</noinclude>"

<includeonly>{{efn|name={{{name|}}}|group=lower-roman|reference={{{1|{{{reference|{{{content|{{{text|}}}}}}}}}}}}}}</includeonly><noinclude>{{documentation}}</noinclude>

Template:Shade

2026-08-23T23:29:23Z

Dodoid: Created page with "<noinclude>{|class="wikitable" |- |</noinclude>rowspan="{{{rowspan|1}}}" style="background:#{{#invoke:Color |hexMix |F8F9FA |{{#switch:{{{color|}}} |green=92EE92 |blue=73CEFF |gold=F6D770 |violet=FFA5FF |orange=FBB775 |grey=C5C5C5 |FFA9A9}} |{{#expr:{{#if:{{{inv|}}} |{{{max|100}}}-}}{{{1|0}}}}} |max={{{max|100}}}}};color:black;vertical-align:{{{valign|middle}}};text-align:{{{align|center}}};{{{style|}}}"|{{{2|{{{pre|}}}{{formatnum:{{{1|0}}}}}{{{suff|}}}}}}<noinclude> |}..."

<noinclude>{|class="wikitable"
|-
|</noinclude>rowspan="{{{rowspan|1}}}" style="background:#{{#invoke:Color |hexMix |F8F9FA |{{#switch:{{{color|}}} |green=92EE92 |blue=73CEFF |gold=F6D770 |violet=FFA5FF |orange=FBB775 |grey=C5C5C5 |FFA9A9}} |{{#expr:{{#if:{{{inv|}}} |{{{max|100}}}-}}{{{1|0}}}}} |max={{{max|100}}}}};color:black;vertical-align:{{{valign|middle}}};text-align:{{{align|center}}};{{{style|}}}"|{{{2|{{{pre|}}}{{formatnum:{{{1|0}}}}}{{{suff|}}}}}}<noinclude>
|}
{{documentation}}
</noinclude>

Build Guide

2026-08-23T21:06:56Z

Dodoid: Created page with "Since you're reading the 15h.org build guide, we'll assume you're interested in building a fully-FOSS-firmware-compatible AMD system to run coreboot-15h. This guide assumes you're looking to build a new desktop, server, or workstation system from separately-purchased components. If you are ''not'' building from separate components (such as for the various prebuilt Supermicro servers which included compatible motherboards), head over to the Motherboards page..."

Mullins

2026-08-23T20:55:48Z

Dodoid: Redirected page to Family 16h#Muillins

#REDIRECT [[Family_16h#Muillins]]

Family 16h

2026-08-23T20:55:28Z

Dodoid: Change Jaguar/Puma to Kabini/Mullins to match Family 15h page's Orochi/Trinity and Richland/Stoney Ridge

{{Infobox cpu family
|image = JaguarDieshotFromPS4.jpg
|image_size = 300
|caption = The die from the [[Jaguar]] APU used in the PlayStation 4
|introduced = 2013
|processnode = 28nm, except 16nm in some game consoles
|uarch1 = [[Jaguar]]
|uarch2 = [[Puma]]
|predecessor = [[Family 14h]]
|successor = Zen APUs
}}

'''Family 16h''' (also known as '''fam16h''', or ambiguously as '''fam16''') is a [[CPU Families Overview|family of AMD microprocessors]] corresponding to the [[Jaguar]] and [[Puma]] microarchitectures. All Family 16h processors were APUs, combining a CPU and a "fast-by-integrated-standards" GPU on a single die. Outside the PC hardware space, it is notable for use in the Xbox One and PlayStation 4 families of eighth-generation game consoles.

"16h" (16-hexadecimal) is most correctly pronounced as "one-sixteen six", but most people say "sixteen‑aitch".

Like other AMD family names, 16h ("16 hexadecimal") is a mostly-arbitrary, somewhat-sequential (new processor families receive unused higher family numbers) number, returned by the x86 <code>CPUID</code> instruction as a "Family number", and commonly written in hexadecimal. 16 in hexadecimal corresponds to the number 22 in decimal, meaning that while "Family 22" would also be a valid, if confusing, name for these CPUs, "Family 16" could also refer to [[Family 10h]].

== Overview ==
{| class="wikitable" style="text-align:center;"
|+
!
!Jaguar
!Puma
|-
!
!Kabini
!Mullins
|-
|Models
|00h-0Fh
|30h-3Fh
|-
|Release Date
|2013/05
|2014/04
|-
|[[AGESA]]
|[http://review.coreboot.org/3836 Open Source]
|Closed Source
|-
|BKDG
|[https://15h.org/images/4/4a/48751_16h_bkdg_-_BIOS_and_Kernel_Developer%E2%80%99s_Guide_%28BKDG%29_for_AMD_Family_16h_Models_00h-0Fh_Processors.pdf 48751]
|[https://15h.org/images/6/61/52740_16h_Models_30h-3Fh_BKDG.pdf 52740]
|-
|coreboot
| style="background-color:#AFA" | [[Family_16h#Jaguar|Yes]]
| style="background-color:#AFA" | [[Family_16h#Puma|Yes]]
|-
|Microcode ROM
| colspan="2" |Undocumented
|-
|Microcode Patches
|Unencrypted
|TBD
|-
|[[PSP]]
|No
|Online
|}
''For other CPU families besides Family 16h, see [[CPU Families Overview]]''

== coreboot Compatible Motherboards ==
=== Kabini ===
* Socket [[FT3]]
** [[Lenovo ThinkPad X140e]] (laptop)
* Socket [[AM1]]
** [[AM1I-A|ASUS AM1I-A]] (mini-ITX)
=== Mullins ===
* Socket [[FT3b]]
** [[PC Engines APU2]]

== See Also ==

* [[AMD Codenames]]

Kabini

2026-08-23T20:53:58Z

Dodoid: Redirected page to Family 16h#Kabini

#REDIRECT [[Family_16h#Kabini]]

Stoney Ridge

2026-08-23T20:41:12Z

Dodoid: Redirected page to Family 15h#Stoney Ridge

#REDIRECT [[Family_15h#Stoney_Ridge]]

Richland

2026-08-23T20:40:36Z

Dodoid: Redirected page to Family 15h#Trinity and Richland

#REDIRECT [[Family_15h#Trinity and Richland]]

Trinity

2026-08-23T20:40:12Z

Dodoid: Redirected page to Family 15h#Trinity and Richland

#REDIRECT [[Family_15h#Trinity and Richland]]

Orochi

2026-08-23T20:39:49Z

Dodoid: Redirected page to Family 15h#Orochi

#REDIRECT [[Family_15h#Orochi]]

Family 15h

2026-05-20T01:56:17Z

Dodoid: Clarifications regarding microcode and SMU firmware

{{Infobox cpu family
|image = E422-opteron-6300-die-shot-16-core.jpg
|image_size = 300
|caption = The die of a 6300-series [[Opteron]], implementing the [[Piledriver]] microarchitecture.
|introduced = October 12, 2011
|processnode = GlobalFoundries 32nm SOI
|uarch1 = [[Bulldozer]]
|uarch2 = [[Piledriver]]
|uarch3 = [[Steamroller]]
|uarch4 = [[Excavator]]
|predecessor = [[Family 10h]]
|successor = Zen
}}

'''Family 15h''' (also known as '''fam15h''', or ambiguously as '''fam15''') is a [[CPU Families Overview|family of AMD microprocessors]] corresponding to the [[Bulldozer]], [[Piledriver]], [[Steamroller]], and [[Excavator]] microarchitectures.

"15h" (15-hexadecimal) is most correctly pronounced as "one-sixteen five", but most people say "fifteen‑aitch".

Like other AMD family names, 15h ("15 hexadecimal") is a mostly-arbitrary, somewhat-sequential (new processor families receive unused higher family numbers) number, returned by the x86 <code>CPUID</code> instruction as a "Family number", and commonly written in hexadecimal. 15 in hexadecimal corresponds to the number 21 in decimal, meaning that while "Family 21" would also be a valid, if confusing, name for these CPUs, "Family 15" could also refer to fam0Fh (K8 CPUs, first released in 2003).

== Overview ==
{| class="wikitable" style="text-align:center;"
|+
!
!Bulldozer
! colspan="3" |Piledriver
! colspan="2" |Steamroller
! colspan="3" |Excavator
|-
!
! colspan="2" |Orochi
!Trinity
!Richland
!Kaveri
!Godavari
!Carrizo
!Bristol Ridge
!Stoney Ridge
|-
|Models
| colspan="2" |00h-0Fh
| colspan="2" |10h-1Fh
| colspan="2" |30h-3Fh
|60h-6Fh
| colspan="2" |70h-7Fh
|-
|Release Date
|2011/10/12
|2012/05/15
|2012/10
|2013/06
|2014/01/14
|?
|2015/07/02
|?
|?
|-
|[[AGESA]]
| colspan="2" |[https://review.coreboot.org/c/coreboot/+/554 Open Source]
| colspan="2" |[http://review.coreboot.org/1155 Open Source]
| colspan="5" |Closed Source
|-
|BKDG
| colspan="2" |[https://15h.org/images/b/be/42301_15h_Mod_00h-0Fh_BKDG.pdf 42301]
| colspan="2" |[https://15h.org/images/4/49/42300_15h_Mod_10h-1Fh_BKDG.pdf 42300]
| colspan="2" |[https://15h.org/images/0/02/49125_15h_Models_30h-3Fh_BKDG.pdf 49125]
|[https://15h.org/images/3/3f/50742_15h_Models_60h-6Fh_BKDG.pdf 50742]
| colspan="2" |[https://15h.org/images/c/c8/55072_AMD_Family_15h_Models_70h-7Fh_BKDG.pdf 55072]
|-
|coreboot
| colspan="2" style="background-color:#AFA" | [[Family_15h#Orochi|Yes]]
| colspan="2" style="background-color:#AFA" | [[Family_15h#Trinity_and_Richland|Yes]]
| colspan="5" style="background-color:#FAA" | No
|-
|Microcode ROM
| colspan="9" |Undocumented
|-
|Microcode Patches
| colspan="4" |Encrypted
| colspan="5" |?
|-
|[[PSP]]
| colspan="4" |No
| colspan="2" |Offline
| colspan="3" |Online
|}

== coreboot Compatible Motherboards ==
=== Orochi ===
* Socket [[AM3+]]
** [[ASUS Crosshair V Formula-Z]] (ATX)
** [[ASUS Sabertooth 990FX R2.0]] (ATX)
** [[H8SML|Supermicro H8SML]] (μ-ATX)
* Socket [[C32]]
** [[ASUS KCMA-D8]] (SSI CEB)
** [[Supermicro H8SCM]] (μ-ATX)
* Socket [[G34]]
** [[ASUS KGPE-D16]] (SSI EEB)
** [[Supermicro H8SGL]] (ATX)
** [[Supermicro H8QG6]] (SWTX)
=== Trinity and Richland ===
* Socket [[FS1|FS1r2]]
** [[G505s|Lenovo G505s]] (Laptop, 15.6in)
* Socket [[FM2]]
** [[F2A85-M|ASUS F2A85-M]] (μ-ATX)

== Microcode Patches ==
All microcode patches released after [[Family 10h]] are encrypted.<ref>https://www.dcddcc.com/docs/2014_paper_microcode.pdf</ref>

{| class="wikitable"
|+Below is the list of ucode versions that could be pulled from the container files in the linux kernel
!commit
!comment
!date
!ucode version
!Microarchitecture
|-
|[https://kernel.googlesource.com/pub/scm/linux/kernel/git/firmware/linux-firmware/+archive/31f6b3076bab3c4b65f67fdb232f4579ed828b4f.tar.gz 31f6b30]
|linux-firmware: Add AMD microcode patch firmware files
|Jul 11 2013
|06000822
|
|-
|[https://kernel.googlesource.com/pub/scm/linux/kernel/git/firmware/linux-firmware/+archive/8ac569dd3ca3ca685bd47ee86c1eeb6050864db3.tar.gz 8ac569d]
|linux-firmware: Update AMD microcode patch firmware files
|Nov 30 2014
|06000832
|
|-
|[https://kernel.googlesource.com/pub/scm/linux/kernel/git/firmware/linux-firmware/+archive/5f8ca0c1db6106a2d6d7e85eee778917ff03c3de.tar.gz 5f8ca0c]
|linux-firmware: Update AMD microcode patch firmware
|Mar 18 2016
|0600084f
|
|-
|[https://kernel.googlesource.com/pub/scm/linux/kernel/git/firmware/linux-firmware/+archive/77101513943ef198e2050667c87abf19e6cbb1d8.tar.gz 7710151]
|linux-firmware: Update AMD cpu microcode
|May 18 2018
|06000852
|Piledriver
|-
|[https://kernel.googlesource.com/pub/scm/linux/kernel/git/firmware/linux-firmware/+archive/7518922bd5b98b137af7aaf3c836f5a498e91609.tar.gz 7518922]
|Update AMD cpu microcode for family 15h
|May 25 2018
|0600063e
|Bulldozer
|}
[[File:Socket G34 pinmap.svg|thumb|G34 socket pinout]]

== Models ==
{| class="wikitable"
|+Below is the documentation for all 15h model revisions
!Model rage
!Date
!Revision
!Link
|-
|00h-0Fh
|September 2014
|3.24
|[https://web.archive.org/web/20220321092743/https://www.amd.com/system/files/TechDocs/48063_15h_Mod_00h-0Fh_Rev_Guide.pdf 48063_15h_Mod_00h-0Fh_Rev_Guide.pdf]
|-
|10h-1Fh
|August 2012
|3.08
|[https://web.archive.org/web/20220129072252/https://www.amd.com/system/files/TechDocs/48931_15h_Mod_10h-1Fh_Rev_Guide.pdf 48931_15h_Mod_10h-1Fh_Rev_Guide.pdf]
|-
|30h-3Fh
|April 2014
|1.06
|[https://web.archive.org/web/20220121164248/https://www.amd.com/system/files/TechDocs/51603_Rev_Guide_15h_Models_30h-3Fh.pdf 51603_Rev_Guide_15h_Models_30h-3Fh.pdf]
|}

== Notes and Status ==

* All x86 CPUs include proprietary microcode, in ROM on the CPU itself. Later vendor-provided patches, which update part of this microcode, can be loaded at runtime - these patches are proprietary blobs.
* All fam15h CPUs are vulnerable to speculative execution exploits if a microcode patch is not loaded.
* Apart from the above, Bulldozer CPUs are generally stable without microcode updates.
* A microcode update is strongly recommended for Piledriver CPUs because of known virtualization-related bugs in their ROM microcode.
* Trinity APUs and Richland APUs additionally require the SMU firmware blob to run. The SMU (System Management Unit) is the microcontroller inside AMD SoCs/APUs that handles low-level platform management: power, clocks, voltage, thermal control, power states, power-gating, and related sensors/interrupts. The firmware for this microcontroller is a blob, [https://git.15h.org/mrothfuss/coreboot-15h/src/branch/4.11_branch/src/vendorcode/amd/agesa/f15tn/Proc/GNB/Modules/GnbInitTN/GnbSmuFirmwareTN.h included as a large array] in f15tn AGESA. Orochi fam15h platforms (non-APU CPUs with separate northbridges and southbridges) do not require this blob.

== See Also ==

* [[CPU Families Overview]]
* [[AMD Codenames]]
* [[Abbreviations and Acronyms List]]

== References ==

15h.org:Copyrights

2026-05-20T01:25:45Z

Dodoid: Add license text

Content on the 15h.org wiki is available under the Creative Commons Attribution-ShareAlike 4.0 International license. An explanation of this license, and its legal text, is available at https://creativecommons.org/licenses/by-sa/4.0/. A copy of the plain-text version of the license is included below:

<pre>
Attribution-ShareAlike 4.0 International

=======================================================================

Creative Commons Corporation ("Creative Commons") is not a law firm and
does not provide legal services or legal advice. Distribution of
Creative Commons public licenses does not create a lawyer-client or
other relationship. Creative Commons makes its licenses and related
information available on an "as-is" basis. Creative Commons gives no
warranties regarding its licenses, any material licensed under their
terms and conditions, or any related information. Creative Commons
disclaims all liability for damages resulting from their use to the
fullest extent possible.

Using Creative Commons Public Licenses

Creative Commons public licenses provide a standard set of terms and
conditions that creators and other rights holders may use to share
original works of authorship and other material subject to copyright
and certain other rights specified in the public license below. The
following considerations are for informational purposes only, are not
exhaustive, and do not form part of our licenses.

Considerations for licensors: Our public licenses are
intended for use by those authorized to give the public
permission to use material in ways otherwise restricted by
copyright and certain other rights. Our licenses are
irrevocable. Licensors should read and understand the terms
and conditions of the license they choose before applying it.
Licensors should also secure all rights necessary before
applying our licenses so that the public can reuse the
material as expected. Licensors should clearly mark any
material not subject to the license. This includes other CC-
licensed material, or material used under an exception or
limitation to copyright. More considerations for licensors:
wiki.creativecommons.org/Considerations_for_licensors

Considerations for the public: By using one of our public
licenses, a licensor grants the public permission to use the
licensed material under specified terms and conditions. If
the licensor's permission is not necessary for any reason--for
example, because of any applicable exception or limitation to
copyright--then that use is not regulated by the license. Our
licenses grant only permissions under copyright and certain
other rights that a licensor has authority to grant. Use of
the licensed material may still be restricted for other
reasons, including because others have copyright or other
rights in the material. A licensor may make special requests,
such as asking that all changes be marked or described.
Although not required by our licenses, you are encouraged to
respect those requests where reasonable. More considerations
for the public:
wiki.creativecommons.org/Considerations_for_licensees

=======================================================================

Creative Commons Attribution-ShareAlike 4.0 International Public
License

By exercising the Licensed Rights (defined below), You accept and agree
to be bound by the terms and conditions of this Creative Commons
Attribution-ShareAlike 4.0 International Public License ("Public
License"). To the extent this Public License may be interpreted as a
contract, You are granted the Licensed Rights in consideration of Your
acceptance of these terms and conditions, and the Licensor grants You
such rights in consideration of benefits the Licensor receives from
making the Licensed Material available under these terms and
conditions.

Section 1 -- Definitions.

a. Adapted Material means material subject to Copyright and Similar
Rights that is derived from or based upon the Licensed Material
and in which the Licensed Material is translated, altered,
arranged, transformed, or otherwise modified in a manner requiring
permission under the Copyright and Similar Rights held by the
Licensor. For purposes of this Public License, where the Licensed
Material is a musical work, performance, or sound recording,
Adapted Material is always produced where the Licensed Material is
synched in timed relation with a moving image.

b. Adapter's License means the license You apply to Your Copyright
and Similar Rights in Your contributions to Adapted Material in
accordance with the terms and conditions of this Public License.

c. BY-SA Compatible License means a license listed at
creativecommons.org/compatiblelicenses, approved by Creative
Commons as essentially the equivalent of this Public License.

d. Copyright and Similar Rights means copyright and/or similar rights
closely related to copyright including, without limitation,
performance, broadcast, sound recording, and Sui Generis Database
Rights, without regard to how the rights are labeled or
categorized. For purposes of this Public License, the rights
specified in Section 2(b)(1)-(2) are not Copyright and Similar
Rights.

e. Effective Technological Measures means those measures that, in the
absence of proper authority, may not be circumvented under laws
fulfilling obligations under Article 11 of the WIPO Copyright
Treaty adopted on December 20, 1996, and/or similar international
agreements.

f. Exceptions and Limitations means fair use, fair dealing, and/or
any other exception or limitation to Copyright and Similar Rights
that applies to Your use of the Licensed Material.

g. License Elements means the license attributes listed in the name
of a Creative Commons Public License. The License Elements of this
Public License are Attribution and ShareAlike.

h. Licensed Material means the artistic or literary work, database,
or other material to which the Licensor applied this Public
License.

i. Licensed Rights means the rights granted to You subject to the
terms and conditions of this Public License, which are limited to
all Copyright and Similar Rights that apply to Your use of the
Licensed Material and that the Licensor has authority to license.

j. Licensor means the individual(s) or entity(ies) granting rights
under this Public License.

k. Share means to provide material to the public by any means or
process that requires permission under the Licensed Rights, such
as reproduction, public display, public performance, distribution,
dissemination, communication, or importation, and to make material
available to the public including in ways that members of the
public may access the material from a place and at a time
individually chosen by them.

l. Sui Generis Database Rights means rights other than copyright
resulting from Directive 96/9/EC of the European Parliament and of
the Council of 11 March 1996 on the legal protection of databases,
as amended and/or succeeded, as well as other essentially
equivalent rights anywhere in the world.

m. You means the individual or entity exercising the Licensed Rights
under this Public License. Your has a corresponding meaning.

Section 2 -- Scope.

a. License grant.

1. Subject to the terms and conditions of this Public License,
the Licensor hereby grants You a worldwide, royalty-free,
non-sublicensable, non-exclusive, irrevocable license to
exercise the Licensed Rights in the Licensed Material to:

a. reproduce and Share the Licensed Material, in whole or
in part; and

b. produce, reproduce, and Share Adapted Material.

2. Exceptions and Limitations. For the avoidance of doubt, where
Exceptions and Limitations apply to Your use, this Public
License does not apply, and You do not need to comply with
its terms and conditions.

3. Term. The term of this Public License is specified in Section
6(a).

4. Media and formats; technical modifications allowed. The
Licensor authorizes You to exercise the Licensed Rights in
all media and formats whether now known or hereafter created,
and to make technical modifications necessary to do so. The
Licensor waives and/or agrees not to assert any right or
authority to forbid You from making technical modifications
necessary to exercise the Licensed Rights, including
technical modifications necessary to circumvent Effective
Technological Measures. For purposes of this Public License,
simply making modifications authorized by this Section 2(a)
(4) never produces Adapted Material.

5. Downstream recipients.

a. Offer from the Licensor -- Licensed Material. Every
recipient of the Licensed Material automatically
receives an offer from the Licensor to exercise the
Licensed Rights under the terms and conditions of this
Public License.

b. Additional offer from the Licensor -- Adapted Material.
Every recipient of Adapted Material from You
automatically receives an offer from the Licensor to
exercise the Licensed Rights in the Adapted Material
under the conditions of the Adapter's License You apply.

c. No downstream restrictions. You may not offer or impose
any additional or different terms or conditions on, or
apply any Effective Technological Measures to, the
Licensed Material if doing so restricts exercise of the
Licensed Rights by any recipient of the Licensed
Material.

6. No endorsement. Nothing in this Public License constitutes or
may be construed as permission to assert or imply that You
are, or that Your use of the Licensed Material is, connected
with, or sponsored, endorsed, or granted official status by,
the Licensor or others designated to receive attribution as
provided in Section 3(a)(1)(A)(i).

b. Other rights.

1. Moral rights, such as the right of integrity, are not
licensed under this Public License, nor are publicity,
privacy, and/or other similar personality rights; however, to
the extent possible, the Licensor waives and/or agrees not to
assert any such rights held by the Licensor to the limited
extent necessary to allow You to exercise the Licensed
Rights, but not otherwise.

2. Patent and trademark rights are not licensed under this
Public License.

3. To the extent possible, the Licensor waives any right to
collect royalties from You for the exercise of the Licensed
Rights, whether directly or through a collecting society
under any voluntary or waivable statutory or compulsory
licensing scheme. In all other cases the Licensor expressly
reserves any right to collect such royalties.

Section 3 -- License Conditions.

Your exercise of the Licensed Rights is expressly made subject to the
following conditions.

a. Attribution.

1. If You Share the Licensed Material (including in modified
form), You must:

a. retain the following if it is supplied by the Licensor
with the Licensed Material:

i. identification of the creator(s) of the Licensed
Material and any others designated to receive
attribution, in any reasonable manner requested by
the Licensor (including by pseudonym if
designated);

ii. a copyright notice;

iii. a notice that refers to this Public License;

iv. a notice that refers to the disclaimer of
warranties;

v. a URI or hyperlink to the Licensed Material to the
extent reasonably practicable;

b. indicate if You modified the Licensed Material and
retain an indication of any previous modifications; and

c. indicate the Licensed Material is licensed under this
Public License, and include the text of, or the URI or
hyperlink to, this Public License.

2. You may satisfy the conditions in Section 3(a)(1) in any
reasonable manner based on the medium, means, and context in
which You Share the Licensed Material. For example, it may be
reasonable to satisfy the conditions by providing a URI or
hyperlink to a resource that includes the required
information.

3. If requested by the Licensor, You must remove any of the
information required by Section 3(a)(1)(A) to the extent
reasonably practicable.

b. ShareAlike.

In addition to the conditions in Section 3(a), if You Share
Adapted Material You produce, the following conditions also apply.

1. The Adapter's License You apply must be a Creative Commons
license with the same License Elements, this version or
later, or a BY-SA Compatible License.

2. You must include the text of, or the URI or hyperlink to, the
Adapter's License You apply. You may satisfy this condition
in any reasonable manner based on the medium, means, and
context in which You Share Adapted Material.

3. You may not offer or impose any additional or different terms
or conditions on, or apply any Effective Technological
Measures to, Adapted Material that restrict exercise of the
rights granted under the Adapter's License You apply.

Section 4 -- Sui Generis Database Rights.

Where the Licensed Rights include Sui Generis Database Rights that
apply to Your use of the Licensed Material:

a. for the avoidance of doubt, Section 2(a)(1) grants You the right
to extract, reuse, reproduce, and Share all or a substantial
portion of the contents of the database;

b. if You include all or a substantial portion of the database
contents in a database in which You have Sui Generis Database
Rights, then the database in which You have Sui Generis Database
Rights (but not its individual contents) is Adapted Material,
including for purposes of Section 3(b); and

c. You must comply with the conditions in Section 3(a) if You Share
all or a substantial portion of the contents of the database.

For the avoidance of doubt, this Section 4 supplements and does not
replace Your obligations under this Public License where the Licensed
Rights include other Copyright and Similar Rights.

Section 5 -- Disclaimer of Warranties and Limitation of Liability.

a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.

b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.

c. The disclaimer of warranties and limitation of liability provided
above shall be interpreted in a manner that, to the extent
possible, most closely approximates an absolute disclaimer and
waiver of all liability.

Section 6 -- Term and Termination.

a. This Public License applies for the term of the Copyright and
Similar Rights licensed here. However, if You fail to comply with
this Public License, then Your rights under this Public License
terminate automatically.

b. Where Your right to use the Licensed Material has terminated under
Section 6(a), it reinstates:

1. automatically as of the date the violation is cured, provided
it is cured within 30 days of Your discovery of the
violation; or

2. upon express reinstatement by the Licensor.

For the avoidance of doubt, this Section 6(b) does not affect any
right the Licensor may have to seek remedies for Your violations
of this Public License.

c. For the avoidance of doubt, the Licensor may also offer the
Licensed Material under separate terms or conditions or stop
distributing the Licensed Material at any time; however, doing so
will not terminate this Public License.

d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
License.

Section 7 -- Other Terms and Conditions.

a. The Licensor shall not be bound by any additional or different
terms or conditions communicated by You unless expressly agreed.

b. Any arrangements, understandings, or agreements regarding the
Licensed Material not stated herein are separate from and
independent of the terms and conditions of this Public License.

Section 8 -- Interpretation.

a. For the avoidance of doubt, this Public License does not, and
shall not be interpreted to, reduce, limit, restrict, or impose
conditions on any use of the Licensed Material that could lawfully
be made without permission under this Public License.

b. To the extent possible, if any provision of this Public License is
deemed unenforceable, it shall be automatically reformed to the
minimum extent necessary to make it enforceable. If the provision
cannot be reformed, it shall be severed from this Public License
without affecting the enforceability of the remaining terms and
conditions.

c. No term or condition of this Public License will be waived and no
failure to comply consented to unless expressly agreed to by the
Licensor.

d. Nothing in this Public License constitutes or may be interpreted
as a limitation upon, or waiver of, any privileges and immunities
that apply to the Licensor or You, including from the legal
processes of any jurisdiction or authority.

=======================================================================

Creative Commons is not a party to its public
licenses. Notwithstanding, Creative Commons may elect to apply one of
its public licenses to material it publishes and in those instances
will be considered the “Licensor.” The text of the Creative Commons
public licenses is dedicated to the public domain under the CC0 Public
Domain Dedication. Except for the limited purpose of indicating that
material is shared under a Creative Commons public license or as
otherwise permitted by the Creative Commons policies published at
creativecommons.org/policies, Creative Commons does not authorize the
use of the trademark "Creative Commons" or any other trademark or logo
of Creative Commons without its prior written consent including,
without limitation, in connection with any unauthorized modifications
to any of its public licenses or any other arrangements,
understandings, or agreements concerning use of licensed material. For
the avoidance of doubt, this paragraph does not form part of the
public licenses.

Creative Commons may be contacted at creativecommons.org.
</pre>

15h.org talk:Copyrights

2026-05-19T23:52:57Z

Dodoid: Created page with "Prior to May 19th, 2026, the 15h.org wiki had no configuration (e.g. $wgRightsPage) to display any content license to readers or contributors. By community consensus, we have chosen to adopt Creative Commons Attribution-ShareAlike 4.0 International as the license for wiki content going forward - this is the same license used for the content on Wikipedia, and a close relative of the license used by coreboot's documentation (CC-BY 4.0). This talk page should document the..."

Prior to May 19th, 2026, the 15h.org wiki had no configuration (e.g. $wgRightsPage) to display any content license to readers or contributors. By community consensus, we have chosen to adopt Creative Commons Attribution-ShareAlike 4.0 International as the license for wiki content going forward - this is the same license used for the content on Wikipedia, and a close relative of the license used by coreboot's documentation (CC-BY 4.0).

This talk page should document the agreement of every user who contributed to the 15h.org wiki prior to this date to release their contributions under the CC BY-SA 4.0 license.

=== Existing Contributions ===

I agree to release all contributions I have made to the 15h.org wiki, including those made before the wiki documented the use of any license, under the CC BY-SA 4.0 license.
--[[User:Dodoid|Dodoid]] ([[User talk:Dodoid|talk]]) 23:52, 19 May 2026 (UTC)

15h.org:Copyrights

2026-05-19T23:36:43Z

Dodoid: Created page with "Content on the 15h.org wiki is available under the Creative Commons Attribution-ShareAlike 4.0 International license. An explanation of this license, and its legal text, is available at https://creativecommons.org/licenses/by-sa/4.0/."

15h.org:About

2026-05-19T23:35:43Z

Dodoid: Created page with "The 15h.org wiki is a collaborative documentation project for for AMD's Family 15h (fam15h) and other related processors and platforms. For more information, see Home."

The 15h.org wiki is a collaborative documentation project for for AMD's Family 15h (fam15h) and other related processors and platforms. For more information, see [[Home]].

ASUS Sabertooth 990FX R2.0

2026-05-12T02:39:20Z

Dodoid:

{{Infobox motherboard
|image = Sabertooth 990FX R2 Motherboard.png
|image_size = 300

|introduced = 2012
|manufacturer = [[ASUS]]

|socket = 1x [[AM3+]]
|northbridge = [[AMD 990FX]]
|southbridge = [[AMD SB950]]
|superio = ITE IT8721F
|ram = 4 slots (2 channels) DDR3-1600 ECC UDIMM, up to 64GB
|bios = 8 MiB socketed DIP-8 (W25Q64FVAIG)
|formfactor = ATX
|power = 1x 8-pin EPS

|slot1 = PCIe Gen2 x16
|slot2 = PCIe Gen2 x1
|slot3 = PCIe Gen2 x16 (electrically x4)
|slot4 = PCIe Gen2 x16
|slot5 = PCI
|slot6 = PCIe Gen2 x16 (electrically x8)

|serial = One internal
|audio = Integrated ([[SB950]] HD Audio), ALC892 codec
}}

The ASUS Sabertooth 990FX R2.0 motherboard well supported by [[coreboot-15h]].

== Open Source Firmware ==
Open source firmware for the Sabertooth 990FX R2.0 is provided by [[coreboot-15h]] utilizing AMD's open source AGESA and CIMx releases for platform initialization. The git repository for the firmware can be reviewed [https://git.15h.org/mrothfuss/coreboot-15h here].

=== coreboot-15h ===
{{Excerpt|Coreboot-15h|[[ASUS Sabertooth 990FX R2.0]]|hat=no|bold=1}}

=== Missing Features ===
* SeaBIOS does not respond to keyboards behind a USB hub.
* Hibernation and Suspend/Resume are unsupported.
* CPUs using the K10 microarchitecture are unsupported.

=== Flashing ===
To switch from the stock firmware to coreboot, [[External Flashing | external flashing]] is required. It is recommended to update the OEM BIOS to the latest version (2901) before switching to coreboot-15h, this will update the EC firmware to the latest version (MBECI-0006). The DIP-8 flash chip is located near the legacy PCI slot (labeled BIOS in the motherboard diagram). A 3.3V CH341a programmer can be used to flash coreboot onto the Sabertooth 990FX R2.0. When switching to coreboot-15h from the OEM BIOS, clearing the CMOS is required. The original DIP-8 flash chip requires the following flashrom argument:

<nowiki>
flashrom -c "W25Q64BV/W25Q64CV/W25Q64FV" </nowiki>

'''Clearing the CMOS'''
# Turn off the computer, disconnect the power cord and any powered peripherals (Monitors, USB devices, etc)
# Move the CLRTC jumper (located at the bottom of the board) to positions 2-3
# Wait 20 seconds
# Restore the CLRTC jumper to positions 1-2
# Connect the power cord
# Wait 2 minutes
# Turn on the motherboard

'''CMOS Battery'''

The motherboard requires a 3V CR2032 battery for reliable operation. Without a working CMOS battery, a two minute wait is always needed between connecting the motherboard to power and turning it on. This requirement is shared both by the OEM BIOS and coreboot-15h.

== Motherboard Diagrams ==
[[File:Sabertooth 990FX R2 Motherboard Diagram.png|frameless|400x400px]]

== Motherboard Components ==
=== Socket AM3+ ===
{{Excerpt|Socket AM3+|inline=yes|bold=yes}}
==== AMD Opteron 3200 and 3300 Series ====
{{Excerpt|AMD Opteron 3200 and 3300 Series|inline=yes|bold=yes}}
=== DDR3 Memory ===
[[File:Sabertooth 990FX R2 RAM Layout.png|frameless|1000x1000px]]
=== AMD 990FX ===
{{Excerpt|AMD 990FX|inline=yes|bold=yes}}
=== AMD SB950 ===
{{Excerpt|AMD SB950|inline=yes|bold=yes}}
=== ITE IT8721F ===
{{Excerpt|ITE IT8721F|hat=no}}

== References ==

SR5670

2026-05-12T02:19:02Z

Dodoid: Redirected page to AMD SR5670

#REDIRECT [[AMD SR5670]]

SR5650

2026-05-12T02:18:44Z

Dodoid: Redirected page to AMD SR5650

#REDIRECT [[AMD SR5650]]

SR5690

2026-05-12T02:18:26Z

Dodoid: Redirected page to AMD SR5690

#REDIRECT [[AMD SR5690]]

990FX

2026-05-12T02:17:42Z

Dodoid: Redirected page to AMD 990FX

#REDIRECT [[AMD 990FX]]