Asus KGPE-D16 (6386SE)

Here are a few other resources that might have some useful info if you,
or anyone else, has not come across them already.

KGPE-D16 Manual

Tashtari’s KGPE-D16 Tech Notes

qubes-users maling list archives KGPE-D16 mentions

Board:asus/kgpe-d16 - coreboot - Old Coreboot Wiki

coreboot maling list archives KGPE-D16 mentions

KGPE-D16 [# vikings wiki] - Vikings KGPE-D16 Info

3mdeb.com KGPE-D16 search results

Overview - Dasharo Universe - Dasharo Info
Issues · Dasharo/dasharo-issues · GitHub Dasharo github issues

GitHub - kakobrekla/kgpe-d16-opteron: collection of items related to opteron on kgpe-d16 - NVME boot?

Note: On my kgpe-d16, which is currently still running Qubes 4.0 with
stock firmware and not network connected, I have more notes and links that might be helpful depending on your particular issues and use case.

It has been running Q4.0 24/7 without any real issue since before my HCL report at the beginning of this thread. It was used online until 4.0 went EOL (with the ASMB4-IKVM removed).

I never got around to installing and cross-flashing the separately purchased PIKE 2008 to IT mode - to get SATA 3 speeds, flashing BMC with OpenBMC, or installing Heads (although I have two compatible 1.2 TPMs and a 2.0 TPM that I think would work with dasharo). Your question has reminded me of all my original goals for the machine.

Also Note: I have not followed recent kgpe-d16 coreboot/dasharo/libreboot/heads news, if it has occurred in the last 3-6 months both because of personal life challenges and the following:

I have not evaluated the security of Opteron cpus (like Insurgo did for
the Ivy in Short list of laptops/desktops that work well with Qubes OS - #245 by Insurgo).

Additionally, to quote from one of @Insurgo posts in All around Qubes
from July 2023 (I really hope he doesn’t mind) referring to
Thoughts dereferenced from the scratchpad noise. | KGPE-D16 open-source firmware status :

"For those who didn’t follow the story of kgpe-d16, the short story
highlighted above was also its downfall. I have integrated the kgpe-d16
stitching Raptor parts together back in 2016, parts that were partly
upstreamed. Meaning that flashrom, openbmc and coreboot code was not
directly upstreamed. When it was finally ported upstream under coreboot,
lack of testing reports from end-users and downstream projects were not
substantial enough and permitted coreboot 4.12 to drop the kgpe-d16
platform. And then libreboot dropped support of its platform as well.
Insurgo initially wanted to inject funds to re-upstream that board prior
of its upstreaming costs to become exponential. And retracted because of
lack of sustainable income coming from this project. Then the kgpe-d16
was lucky again and received funding from Immunefi. But still no
sustainable funding sources for maintainership of that platform to cover
the 500k fee, and counting, to bring it back in a clean state upstream
under coreboot, to become mainstream again, without any guarantee that
the same story would not happen again. Afterall, the kgpe-d16 is a story
of a board which never received enough love (time, energy, support,
money) from its first coreboot port to now…

So what is the state of kgpe-d16 under Heads?
Same as for other untested platforms, still under coreboot 4.11 branch
with patches needing to be updated, where still awaiting for board
owners to test the dasharo fork instead of 4.11. Without going too much
into the details, its really hard to build roms for older build systems…"

I would love to see things move forward, but do not have 500k, and cannot test much right now.

Slight Explanation

An 85 year old relative currently uses the machine (offline as I mentioned above) as her primary machine. Someday, hopefully soon, I intend to get her a replacement and return to working on kgpe-d16 firmware testing and upgrading Qubes.

Although a “beast” the kgpe-d16 holds a special place in my heart and
if/when I can assist, I will. I think it is worth the effort to get
it working @jr77 but that’s just my opinion.

When you have time please consider

Discussion in the forum would be my preference, but I understand if that you have reasons not to do so.

Still you have peeked my curiousity and would like to help or discuss what / if I can.


Edited 10-11-2023: to fix links and ideally make this post more readable.

1 Like