Board:asus/kgpe-d16
The wiki is being retired!
Documentation is now handled by the same processes we use for code: Add something to the Documentation/ directory in the coreboot repo, and it will be rendered to https://doc.coreboot.org/. Contributions welcome!
To boot with a second CPU package installed, the 2nd EPS12V connector MUST be connected to a 8-pin power source that has sufficient amperage (Using a converter is risky).
General Information
The KGPE-D16 is a AMD Family 10h / 15h, dual-CPU server and workstation motherboard released in 2009 (ASUS). It is well supported and stable under Coreboot, with all CPUs, RAM, and peripherals functioning normally. Family 10h (61xx) processors do not currently support the isochronous mode required to enable the IOMMU, but Family 15h (62xx, 63xx) processors work well with the IOMMU enabled.
This board is automatically tested by Raptor Engineering's test stand. For more details please visit AutoTest/RaptorEngineering.
A basic system diagram is available in the official manual, Appendix A.1 and has been confirmed to match the hardware shipping from ASUS. Not indicated are the PCIe lane widths for the gigabit network controller, which are both x1. All legacy PCI devices share the same bus, and partially due to this design the SP5100 has severe issues with bridging high-bandwidth PCI peripherals. As such, an external PCI-PCIe bridge is recommended should you need to interface a high bandwidth legacy PCI device to this system; ASMedia controllers have been verified to function correctly.
Northbridge functions are distributed between the CPU internal northbridge and the SR5690 northbridge, which is effectively a HyperTransport to ALink/PCIe translator and switch. There is a separate SP5100 southbridge device, adjacent to the northbridge and residing under the smaller heatsink of the two. This device provides all traditional southbridge services including the LPC bridge and SATA controllers. All southbridge-destined messages, including CPU-originated power state control messages over HyperTransport, pass through the CPU northbridge and are routed to the southbridge via the SR5690 northbridge device.
Incidentally, this design places the IOMMU, which is part of the SR5690, in the correct location to properly shield the main CPU from all unauthorized traffic. If the southbridge connected directly to a HyperTransport link there would be no way to prevent unauthorized DMA from legacy PCI devices connected to the southbridge, or even from the southbridge's embedded microprocessor.
Installation Notes
- You MUST use at least one real 8PIN EPS12V cable for one CPU, and two real 8PIN EPS12V cables for two CPU's (Adapters may catch fire!)
- coreboot must be flashed externally when migrating from the proprietary BIOS. After coreboot has been flashed and booted at least once, flashrom can safely reprogram the ROM under Linux.
- When migrating from the proprietary BIOS, after flashing coreboot the CMOS memory must be cleared. Failing to clear the CMOS will typically result in odd hangs during the boot process.
- Enabling the serial console or EHCI debug console will drastically increase the time needed to boot.
- The proprietary BMC module must be removed for coreboot to function.
- The 63xx "Piledriver" series processors require microcode updates to enable IOMMU (Errata) and may require microcode updates for safe operation due to the 2016 gain-root-via-NMI exploit.
- Fan control is via software with coreboot, you can use fancontrol/pwmconfig to control your 4pin PWM fans - coreboot sets them = 100% at boot-time.
- 12 and 16 core CPU's are split in to two NUMA nodes, memory is divided based on NUMA nodes (1 6282SE 16 core CPU, 2 Nodes, 32GB RAM, 16GB per node)
- Turbo 2 and power saving seems to require a tickless system to function (nohz=on in the kernel cmdline), otherwise the extra cores are always woken up and will never enter CC6.
Features
| Format | SSI-EEB | |
|---|---|---|
| Socket | G34 | |
| Max Processors | 2 | |
| Max RAM | 128 GB | |
| PCI-e slots | 4 | 5 physical, 4 concurrent |
| PCI slots | 1 | Via PCI Bridge that also connects onboard AST graphics chip |
| Other Expansion Slots | 1 PIKE | ASUS Proprietary I/O Expansion Slot, Insert PIKE RAID card for second half of the motherboard SATA/SAS ports |
| EEPROM Type | DIP 8 SPI Socket | |
| Factory EEPROM Size | 2MB | |
| Max EEPROM Size | ??? | |
| TPM | YES | With Owner Controlled CRTM - TPM is an option addon module |
| Crossfire XDMA | ??? | Has ACS and dual PCI-e 2.0 x16 slots, so it should work (reported working on vendor bios, need tester for coreboot) |
| Blob Free Operations | YES | ||
|---|---|---|---|
| Native GFX Init | Partial | Text Mode Only | Now features proper EDID parsing. |
| OpenBMC Network KVM Firmware | Soon | See Below |
| HVM | YES | |
|---|---|---|
| SLAT (RVI) | YES | |
| IOMMU | YES | v1.26 with Interrupt Remapping |
| IOMMU for Graphics | YES | Near-Native 3D gaming performance with proper software configuration |
| PCI-e ACS | YES | |
| SR-IOV | ??? | Coreboot doesn't support SR-IOV |
| PCI-e ARI | ??? | Required for more than 8 SR-IOV VF per device, AMD's docs say the chipset supports it however there are no firmware implementations that feature it. |
OpenBMC - Network KVM
Raptor Engineering is working on porting OpenBMC to the KGPE-D16 and KCMA-D8 under a crowdfunded contract, it should be done in a few months.
https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php
Note: You will probably require the ASUS ASMB4-iKVM module to use it.
RAM HCL
The following RAM models and configurations have been tested by either Raptor Engineering or a third party and are know to work as of the stated GIT revision.
| Manufacturer | Model | Max working RAM / CPU | Size | Speed | Type | ECC | Populated Slots | CPU | Mainboard Type | Firmware |
|---|---|---|---|---|---|---|---|---|---|---|
| Micron | 36KSF2G72PZ-1G4E1 (N/A) | 16GB | DDR3-1333 | Registered | Yes | A2 / C2 | Opteron 6378 | Coreboot 2268e0d or later | ||
| Micron | MT36KSF1G72PZ-1G6M1FF | 32GB | 8GB | DDR3-1600 | Registered | Yes | All orange slots | Opteron 6262HE | 1.03G | Internal development version of coreboot |
| Micron / HP | MT36JSF2G72PZ-1G6E1LG (HP: 672612-081) | 32GB | 16GB | DDR3-1600 | Registered | Yes | A2 / C2 / E2 / G2 | Opteron 6276 | 1.03G | Libreboot 20160907 |
| Hynix/Hyundai | HMT151R7BFR4C-H9 | 16GB | 4GB | DDR3-1333 | Registered | Yes | A2 / C2 / E2 / G2
A2 / B2 / C2 / D2 |
Opteron 6276 | 1.03G | Libreboot 20160907 |
| Kingston | 9965525-055.A00LF | 8GB | DDR3-1600 | Unbuffered | Yes | A2 / C2 / E2 / F2 | Opteron 6328 | Coreboot 9fba481 | ||
| Kingston | KVR16R11D4/16 (9965516-483.A00LF) | 64GB | 16GB | DDR3-1600 | Registered | Yes | All orange slots (128GB) | Opteron 6278/6262HE | Libreboot 20160907 | |
| Kingston | KVR16R11D4K4/64I (9965516-477.A00LF) | 64GB | 16GB | DDR3-1600 | Registered | Yes | All orange slots (128GB) | Opteron 6278/6262HE/6284SE | Libreboot 20160907 | |
| crucial ("crucial by Micron") | CT16G3ERSLD4160B (MT36KSF2G72PZ-1G6P1NE) | 64GB | 16GB | DDR3-1600 | Registered | Yes | All orange slots (128GB) | Opteron 6278/6282SE/6284SE/6287SE | 1.03G, 1.04 | Libreboot 20160907 |
| Micron | MT36KSF2G72PZ-1G6E1FE | 64GB | 16GB | DDR3-1600 | Registered | Yes | All orange slots | Opteron 6378 | 1.04 | Internal development version of coreboot (2017) |
| Micron | MT36KSF2G72PZ-1G6N1KG | 64GB | 16GB | DDR3-1600 | Registered | Yes | All orange slots | Opteron 6378 | 1.04 | Internal development version of coreboot (2017) |
| crucial ("crucial by Micron") | CT16G3ERSLD4160B (MT36KSF2G72PZ-1G6P1NE) | 192GB | 16GB | DDR3-1600 | Registered | Yes | A2,A1,B2,B1,C2,C1/G1,G2,F1,F2,E1,E2 (see page 2-16 in the ASUS manual), LVDDR3_SEL1 can be set to "Force 1.35V" | Opteron 6278/6282SE/6284SE/6287SE | 1.03G, 1.04 | coreboot d6735b0 |
Processor Summary
In addition to the 1 or 2 main CPUs, there are no less than three known secondary processors present on the mainboard. All are disabled when running under coreboot.
- There is a very poorly documented microprocessor inside the SR5690; purpose and type unknown. It is believed this processor requires a firmware upload from the main platform firmware or via JTAG in order to start execution.
- A single 8051 processor core is present inside the SB700 southbridge. It normally handles errata related to power states and may also be responsible for the blinking power LED in S3 suspend under the proprietary BIOS. It is believed accesses made by this processor are responsible for the flashrom write failure when the board is booted from the proprietary BIOS. This processor also requires a firmware upload from the main platform firmware or via JTAG in order to start execution.
- The BMC has an integrated ARM core. This is disabled by pin strap when the BMC firmware module is not installed.
Some processors may be present on or activated by add-on modules:
- The optional PIKE add-on cards use ARM cores to handle the SAS protocol, though this firmware is directly loaded from a Flash chip on the module and does not involve any non-local components (e.g. the main CPU never touches the firmware on these modules outside of a manual reflash operation). Raptor Engineering is currently unaware of any SAS controllers that operate without a secondary processor or use libre firmware; the protocol is simply too complex to handle via a mask ROM, and as there are only one or two suppliers of SAS controllers there is very little incentive to release the source code to the firmware. Writing a libre firmware to replace the existing firmware may technically be possible, however it is extremely unlikely this will ever happen due to the man-decades required.
- Installing an ASUS iKVM firmware module will activate the ARM core in the BMC, which has full system access to all peripherals and possibly memory. It is not recommended to use this module as the firmware is both highly privileged and proprietary, and is known to contain at least one critical security bug.
Known Issues
EHCI debug console
The EHCI debug console causes severe USB problems under both Libreboot and coreboot. This typically manifests as very slow boot / slow typing on USB keyboards. This issue appears to extend to the KCMA-D8 and KFSN4-DRE boards as well.
MMIO Resources Limit
The coreboot 32bit MMIO space limits the use of large amounts of PCI-e devices, such as more than a few network interfaces or graphics cards with the limit coming up sooner for older multi-port NIC's that have a switched design (ex: 82576), vs the newer style native multi-port pci-e setup (i350)
This is the reason for the "Not enough MMIO resources for SR-IOV" error when you attempt to enable SR-IOV on a system with both a quad port NIC and the onboard interfaces.
RAM
- Certain models and populations of DIMMs do not function under either coreboot or the proprietary BIOS. These failures may also be contingent on the exact PCB revision and / or CPU model installed. For a list of known failing combinations please visit KGPE-D16 Known Bad Configurations.
> 192 GB of RAM not working
The KGPE-D16 doesn't work with more than 192 GB RAM (reported by ThomasUmbach) and would need further work by coreboot developers. To use 192 GB RAM it's necessary to leave the DIMM slots next to the CPUs unpopulated (reported by ThomasUmbach).
Miscellaneous Notes
The 4 total PCI-e slots may be limiting, but as the board has PCI-e ACS you may be able to use an external ACS supporting PCI-e expansion system - you would still have IOMMU security and performance as ACS support means that the devices beyond the external switch will be placed in separate IOMMU groups and thus you will maintain security and not have to use the unsafe attachment override for attaching devices to virtual machines.
NOTE: MMIO space limit dependent.
Free Software Foundations "Respects Your Privacy" (RYF) certification
The Vikings D16 (a relabelled KGPE-D16) board is being sold with coreboot/Libreboot pre-installed. It is the first workstation/server mainboard that has been "RYF - Respects Your Freedom" certified by the Free Software Foundation on March 6th, 2017.
FAQ
Recommended CPU's
| Processor sold by AMD | Part Number | Cores | Requires microcode updates for secure operation (ref) | Notes |
|---|---|---|---|---|
| Opteron 6386 SE | OS6386YETGGHK | 16 | Yes | |
| Opteron 6328 | OS6328WKT8GHK or OS6328WKT8GHKWOF | 8 | Yes | |
| Opteron 6287 SE | ? | 16 | No | |
| Opteron 6284SE | ecx-Off-US-917385 | 16 | No | |
| Opteron 6282SE | OS6282YETGGGU | 16 | No |
An 8 Core CPU is not really worth it unless you need the better single threaded performance more than the second set of cores, such if the software you use is not highly multithreaded.
https://en.wikipedia.org/wiki/List_of_AMD_Opteron_microprocessors