[coreboot] Asus KGPE-D16 with latest coreboot errors with Unsupported Hardware on Qubes 4 install missing IOMMU?

petecb petecb at protonmail.com
Tue Nov 27 18:12:09 CET 2018


Thanks for your reply.

I have built a version of coreboot with the “use binary only repo” and “generate microcode updates from tree”. I presume by selecting “from tree” I do not need to fill in the “Mircrocode binary path and filename”.
The output of the make command to build the rom provides the following at the end:

Name                           Offset     Type           Size   Comp
cbfs master header             0x0        cbfs header        32 none
fallback/romstage              0x80       stage          171020 none
config                         0x29d00    raw               281 none
revision                       0x29e80    raw               576 none
cmos_layout.bin                0x2a100    cmos_layout      3524 none
fallback/dsdt.aml              0x2af00    raw              9895 none
payload_config                 0x2d600    raw              1682 none
payload_revision               0x2dd00    raw               236 none
microcode_amd_fam15h.bin       0x2de40    microcode        7876 none
(empty)                        0x2fd80    null               24 none
s3nv                           0x2fdc0    raw             65536 none
fallback/ramstage              0x3fe00    stage           88643 none
vgaroms/seavgabios.bin         0x55880    raw             28160 none
img/coreinfo                   0x5c700    simple elf      50606 none
fallback/payload               0x68d00    simple elf      68119 none
img/memtest                    0x79780    simple elf      47555 none
microcode_amd.bin              0x85180    microcode       12684 none
(empty)                        0x88380    null          1537368 none
bootblock                      0x1ff900   bootblock        1184 none

>From this it looks as though it is being built with the microcode. If I boot into a Fedora Live CD dmesg does show me that the AMD microcode is being applied. However I presume this is Fedora doing this because when I boot into Qubes it does not detect IOMMU.

Does this indicate an issue with how I have built coreboot?
Is there a way to get Qubes to apply microcode updates in the same way Fedora does?

Have you successfully got a 6386 on this board running with Qubes and all the microcode updates?

I have attached a copy of my serial output booting the system with 2 sticks of 16Gb ECC RAM (32Gb total) in case this is of any help.

Many thanks for your help, it is much appreciated.

Kind regards,


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, November 26, 2018 10:14 PM, Taiidan at gmx.com <Taiidan at gmx.com> wrote:

> On 11/26/2018 09:15 AM, petecb via coreboot wrote:
> > Hi,
> > I have an Asus KGPE-D16 motherboard I am trying to get working with Coreboot and use with Qubes 4. It has a single AMD 6386 CPU and 128Gb DDR3 ECC RAM.
> > I have successfully cloned the git repository and built the coreboot.rom. However when I flash it on to the board and then run the Qubes installer it complains that there is an “Unsupported Hardware Error” and I get the text "This hardware lack features requred by Qubes OS. Missing features: IOMMU/VT-d/AMD-Vi , Interrupt Remapping”
> > If I install Fedora and run dmesg, AMD-Vi and the IOMMU all appear to be fine.
> As it applies microcode updates.
> > I have tried flashing the board with an older version of Libreboot and can confim this proceeds through the Qubes 4 installation without issue. However, I wish to use a recent version of Coreboot for support of a Pci-E SSD and to ensure I am running the latest microcode updates.
> > Can anyone offer me some guidance please?
> > Is it possible I am not selecting the right options when I do “make nconfig” before building the rom?
> 63xx CPU's need a microcode update for working IOMMU and to fix a
> critical security error thus you can't use libreboot.
> I noted this on the wiki which is sadly now gone.
> In the coreboot config enable "use binary only repo" and "generate
> microcode update from tree" and then use the cbfstool and a livecd
> (check dmesg) to verify it has been updated to the latest version that
> includes the spectre protections as well as the IOMMU/NMI fixes.
> Congrats on your libre purchase and let us know if you need help :D
> I also suggest checking out the OpenPOWER9 Raptor Blackbird if you want
> another owner controlled computer that is newer and faster.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> coreboot mailing list: coreboot at coreboot.org
> https://mail.coreboot.org/mailman/listinfo/coreboot

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: SerialOutputCorebootKGPED16AMD6386Nov27v2.txt
URL: <http://mail.coreboot.org/pipermail/coreboot/attachments/20181127/3ddf54fd/attachment-0001.txt>

More information about the coreboot mailing list