Note: As of coreboot v220.127.116.11 we have noticed an increase in DRAM sensitivity/compbatibility on the FW2B and FW4B platform. v18.104.22.168 for the FW4B has significantly improved compatiblity. However, we still recommend purchasing DRAM from Protectli at the time of purchase so we can ensure that the memory works with the coreboot build.
coreboot is an open source project focused on the boot and BIOS process for initializing hardware (HW) and booting an operating system (OS). coreboot has roots in the Linux community and can be found on the internet at https://www.coreboot.org/.
coreboot describes itself as: “…an extended firmware platform that delivers a lightning fast and secure boot experience on modern computers and embedded systems.” It is an open source alternative to legacy BIOS options with the following properties:
- Fast Boot – Minimal image, removes legacy bloat
- Open Source – The source code is available and can be built without any cost or license
- Secure – Common backdoors of legacy BIOS can be disabled or not even included in the build
- Support for modern HW and Intel CPUs
The coreboot philosophy is to do the absolute bare minimum to discover and initialize hardware (HW), then pass the control to another program called a “payload”. The payload then takes care of user interfaces, drivers, policies, etc. Protectli has implemented coreboot with the SeaBIOS payload.
coreboot is available on the FW2B, FW4B and FW6A/B/C/D series Protectli platforms as an alternative to traditional BIOS.
coreboot is based on legacy BIOS, please see the compatibility table below for software which has been tested with coreboot for full functionality
coreboot can be selected at the time of ordering. It can also be installed in the field. See instructions below for field installation.
Attention: if you wish to use coreboot, we highly recommend choosing coreboot at the time of purchase and allowing Protectli to flash and validate successful installation. Flashing the BIOS is potentially problematic, as if anything goes wrong the entire unit needs to be sent to Protectli in order to be recovered. Flashing is done at your own risk. While we provide instructions on how to do so, if you choose to flash your Vault and it does not flash properly, then recovery by Protectli is not covered under Protectli’s new product warranty. It is important to note that even if you follow all the steps properly, there is still a chance that the flash does not work and the unit will need to be recovered by Protectli.
Protectli is committed to continuing the development of coreboot on each of our compatible platforms. While coreboot images for the Vault may not be available with every minor coreboot project update, we will work diligently to ensure Vault coreboot updates are available to address any serious vulnerabilities. We will also work to contribute our coreboot updates back into the project master. Protectli contributions can be found at this link for version 22.214.171.124. Version 126.96.36.199 is now released and source code contributions will be available once they are approved by the coreboot community. Version 188.8.131.52 includes security enhancements for Intel Spectre-Meltdown vulnerabilities and has a built in MemTest that can be run from the boot menu.
Although this does require software building experience, coreboot build documentation is available in this PDF (link), along with the source code repositories available for the FW2B/FW4B (link) and FW6A/B/C here (link). We do not offer software development support.
coreboot and the Vault
coreboot BIOS Settings
A frequent question that is encountered is “how do I get into the BIOS”. When coreboot is installed on the Vault, there is no way to “get into” the BIOS as there is with traditional BIOS. This is considered a security feature so that there is less possibility to tamper with BIOS settings. The only operation available at boot time is to select the boot device from the Boot Selection Menu. To access the Boot Selection Menu, press the F11 key when the boot splash screen is displayed. Unlike legacy BIOS, selecting the DEL key will not do anything and will not “get into” the BIOS.
As with all of our devices, the “Restore power after loss” functionality is on by default.
COM port functionality is fully supported as well, with the same settings of 115200 baud rate, 8 data bits, 1 stop bit and no parity.
Boot Selection Menu
When coreboot is installed on the Vault, the Vault will first attempt to boot from the internal mSATA. If there is no bootable OS on the mSATA, it will then attempt to boot from any USB that it discovers. If it is desired to boot from a USB rather than mSATA, the boot menu can be accessed by pressing the “F11” key when the splash screen is displayed then selecting the desired boot device. Note that with coreboot, there is no way to “get into” the BIOS to set individual parameters as there is with traditional BIOS. The only other option in the boot menu is to run the built in Memtest on the unit.
If a bootable USB drive is not showing up in the bootmenu, we have noticed some drives respond better to the lower USB port. Using a USB hub also helps some drives to be recognized by the system.
Note: coreboot utilizes Legacy BIOS. If the operating system was previously installed under UEFI BIOS, coreboot may no longer recognize that drive.
Note: As of coreboot 4.12.03 memtest is now included as an option in the boot menu. Once memtest is launched, it does not recognize keyboard inputs. Power cycling is the recommended way to exit.
coreboot Hardware Compatibility
There are some coreboot hardware compatibility issues with specific DRAM vendors and/or specific manufacturing lots.
As of coreboot v184.108.40.206 we have noticed an increase in DRAM sensitivity on the FW2B and FW4B platform. While Kingston and Crucial modules are still recommended, recently we have heard reports of batches that are not compatible. v220.127.116.11 for the FW4B has significantly improved compatibility. We currently recommend selecting DRAM at the time of purchase or directly through our store to ensure compatibility.
For the FW2B we recommend Kingston and Crucial SO-DIMM modules or Samsung RAM modules which were included with pre-configured units.
FW6A/B/C platforms work fine with a majority of RAM SODIMMs . We have seen some compatibility issues with Samsung, PNY and G.Skill brand modules.
We have seen incompatibility with 1440p monitors on coreboot flashed FW2B and FW4B. The FW6A/B/C/D is fully compatible.
In some rare occurrences, customers have reported incompatibility with certain high end keyboards attempting to access the boot menu. If you are unable to access the boot menu, please try a another keyboard or utilizing the COM port (link to our COM port article)
Note: Flashing new firmware onto any hardware is potentially dangerous in that if the procedure is interrupted or otherwise not able to complete, your hardware may be rendered useless. Please proceed with caution only after fully understanding each step of the following instructions. If there are any questions, please contact Protectli support BEFORE proceeding.
Protectli can not be held responsible for devices that are rendered unusable as a result of flashing the BIOS. If your devices becomes unusable as a result of a BIOS flashing operation, we will help recover the device, but the customer will be responsible for all shipping costs.
Below are the manual instructions for flashing coreboot, recently we have released an automated script to help simplify the installation process. The script can be found here (link).
coreboot is installed using a program called ‘flashrom’ which is available for many linux distributions. Protectli validated the installation of coreboot using flashrom on Ubuntu 20.04 (see this link for guidance on installing Ubuntu on the Vault). It is important to use Ubuntu 20.04 or newer because previous versions of Ubuntu used an older version of flashrom that did not support the FW6A/B/C. While flashrom works under other operating systems, this has not been tested by Protectli. As such, we recommend using Ubuntu 20.04 or newer to upgrade your Vault to coreboot.
We have noticed possible odd behavior with coreboot flashes done in a UEFI environment. Verify the following steps are done with a legacy install of Ubuntu. To guarantee a legacy install of Ubuntu follow the steps in this article (link), but selecting “Legacy only” instead of “UEFI only” then proceed with Ubuntu installation. Please out reach out if you are unsure.
In the instructions below, “#” indicates a command line instruction in an Ubuntu Terminal window. “filename” refers to the actual name of the file.
- Install Ubuntu desktop version 20.04 or newer on the Vault to the internal mSATA per the link above (we recommend the “Minimal” version for this task)
- Note: Installing Ubuntu on the mSATA drive will overwrite anything currently installed.
- Note: A clean install of Ubuntu 20.04 or newer is recommended for a clean, controlled environment to ensure a successful BIOS flash.
- Verify that Ubuntu desktop version is installed and reboot the system
- Verify that Ubuntu boots up to the desktop version and the Firefox browser is installed, or install the browser of your choice
- Browse to the appropriate coreboot “filename.rom” file and download it to the Ubuntu system. See the table below for links to the coreboot .rom files.
- Open a terminal window in Ubuntu. (Applications->Terminal)
- Verify the terminal opens and change directory to “Downloads” using the following command:
- Verify the “filename.rom” file has been downloaded to the “Downloads” directory using the following command:
- Download the appropriate SHA256 checksum file per the table below
- Verify the “filename.rom.sha” file has been downloaded to the “Downloads” directory using the following command:
- If the files are compressed, with a suffix of “.zip”, uncompress them with the following commands:
#unzip filename.rom.zip #unzip filename.rom.sha256.zip
- Run the SHA256 program on the filename.rom file using the following command:
- Verify the SHA256 output is the same as the contents of the filename.rom.sha file using the following command:
- Verify the “flashrom” program is present in Ubuntu using the following command:
- If flashrom is not present, get it from the network and install it in Ubuntu using the following command:
#sudo apt install flashrom
Verify flashrom is installed on the system
Flash the coreboot image to the system.
Note: The flashrom command arguments for v18.104.22.168 were different for the FW6 series than the FW2B and FW4B series. Now all of the versions, including FW6D and FW6E use the same flashrom command arguments.
#sudo flashrom -p internal -w filename.rom --ifd -i bios
- After the flash is complete the terminal should output a “VERIFIED” message
- If a “VERIFIED” message does not appear, do NOT power off the device. Verify the flashrom command is correct and re-run the flashrom command again
- Reboot the system
- Verify the system boots and displays the coreboot version string on the screen, then the splash screen
- Verify the system boots up to Ubuntu desktop
- If not using Ubuntu as the OS, power off the system and install the desired OS over the Ubuntu installation or replace the Ubuntu mSATA with a mSATA for the desired OS.
- Reboot the system and verify that it boots to the desired OS
At this point coreboot should be installed. However, as always, feel free to contact us at: firstname.lastname@example.org.
Flash from Coreboot to Original(AMI) BIOS
In case you would like to go to back the OEM BIOS, the steps are relatively straightforward. Following the same procedure as flashing Coreboot. Be sure to use the correct BIOS for your Vault.
Using the same Ubuntu install as the instructions above;
- Verify the correct BIOS is downloaded from this link
- Unzip the BIOS in the Downloads folder
- Open Terminal and change directory to BIOS folder. Example filenames and commands below will depend upon the actual version of the BIOS.
For the FW4B
For the FW2B
For the FW6A/B/C
For the FW6D
For the FW6DE
- Run the flashrom command, using ‘filename.bin’ for legacy BIOS, instead of ‘filename.rom’ for coreboot
FW4B BIOS file example:
#sudo flashrom -p internal -w YLBWL412.bin --ifd -i bios
FW2B BIOS file example:
#sudo flashrom -p internal -w YLBWL212.bin --ifd -i bios
FW6A/B/C BIOS file example:
#sudo flashrom -p internal -w KBU6LA09.bin --ifd -i bios
FW6D BIOS file example:
#sudo flashrom -p internal -w KBR6L132.bin --ifd -i bios
- After the flash is complete the terminal should output a “VERIFIED” message.
- Reboot and verify the legacy BIOS is loaded
coreboot File Table
|Vault||coreboot .rom file||SHA256 file||Notes||Release Date|
|FW4B||fw4b_v22.214.171.124.rom||fw4b_v126.96.36.199.rom.sha||Enhancements for memory compatibility||4/29/2021|
|FW6A/B/C||fw6_v188.8.131.52.rom||fw6_v184.108.40.206.rom.sha||Support for Intel i210, i211 NICs||5/4/2021|
|Vault||coreboot .rom file||SHA256 file||Notes||Release Date|
|FW4B||fw4b_v220.127.116.11.rom||fw4b_v18.104.22.168.rom.sha||Security enhancements for Intel Spectre-Meltdown vulnerabilities, built in MemTest accessible in boot menu||11/11/2020|
|FW6A/B/C||fw6_v22.214.171.124.rom||fw6_v126.96.36.199.rom.sha||Security enhancements for Intel Spectre-Meltdown vulnerabilities, built in MemTest accessible in boot menu||11/11/2020|
|Vault||pfSense 2.4.5||pfSense 2.5||FreeBSD 11.2||Sophos XG 18||OPNsense 21.1||Untangle 14.2.2||Ubuntu 20.04||ESXi 6.7||Windows 10|
|FW2B||Verified||Verified||Verified||Verified||Verified||Verified||Verified||Verified||Verified - Use MBR partition scheme|
|FW4B||Verified||Verified||Verified||Verified||Verified||Verified||Verified||Verified||Verified - Use MBR partition scheme|
|FW6A||Verified||Verified||Verified||Verified||Verified||Verified||Verified||Verified||Verified - Use MBR partition scheme|
|FW6B||Verified||Verified||Verified||Verified||Verified||Verified||Verified||Verified||Verified - Use MBR partition scheme|
|FW6C||Verified||Verified||Verified||Verified||Verified||Verified||Verified||Verified||Verified - Use MBR partition scheme|