Asus KGPE-D16 (6386SE)

Remarks

Hardware Notes:
ASUS KGPE-D16(ASMB4-IKVM) with clear CPU socket covers and 1.05 visible on the board
Only using one CPU (OS6386YETGGHK) and four 16GB RDIMMs (M393B2G70QH0-YK0) config per manual
Only PS/2 keyboard and PS/2 mouse used attached to PS/2 ports
Disabled Aspeed onboard VGA using the board’s jumper setting
Added an ASUS HD 6450 PCIe (EAH6450) graphics card
ASMB4 came installed and was left unaltered (does fan control)
Disabled onboard LAN controllers via the motherboard jumpers Onboard LAN not tested
Added an Atheros Wireless PCI card
Added two 4-Port Type-A USB 3 PCIe cards
Added Asus TPM 1.02g

BIOS Notes:
This is likely incomplete since I didn’t document it well (installed over a year ago). Sorry :frowning:
Changed IOMMU to Enabled
Changed Remote Access to Disabled
Changed Onboard LAN1/LAN2 Chip to Disabled
Changed Boot Device Seeking to Normal
Changed SATA Port1 - Port4 from IDE to AHCI - for the SSD
Made sure VGA ROM Boot Priority was set to PCIE VGA Card

Qubes 4.0 Notes:
Asus TPM 1.02g (TPM 1.2) shows in BIOS and when enabled is identified in dom0 using tpm_version. AEM was not tested. I had difficulties with the onboard USB ontrollers, although I was always using the rear PS/2 ports. This may be due to my configuration in BIOS, in Qubes, both, or something else. Qubes 4.0x installation was accomplished via the USB port on the motherboard (labeled USB9 in the manual). Unfortunately I don’t recall if any special installation steps were required. There is no onboard audio. A USB audio device (attached to an add-on PCIe USB card) is used instead but must be passed to VMs requiring it. In this setup audio is not available system-wide.

Attachments

Qubes-HCL-ASUSTeK_Computer_INC_-KGP_M_E_D16-20210820-153727.yml (2.6 KB)

2 Likes

Thank you @Justin for your HCL report, which is now part of this pull request and will be visible on the website soon!

You put so much work into it… impressive. Unfortunately the ‘remarks’ need to be rather short to display nicely in the table. As in all such cases I put a ‘read more’ link into the remarks which points to your forum post that contains all the details.

Great job!

1 Like

Thank you @Sven
Appreciate all you’ve done and continue to do for Qubes!
btw love the community list of recommended computers

Some Additional KGPE-D16 Hardware Notes:
The working Asus TPM 1.02G is a 20-1 TPM 1.2 module with a capacitor to
the left of the SLB9635 Infineon chip. An Asus TPM-L R2.0 rev 1.00
SLB9665TT20 was also tested and is NOT identified by the OEM BIOS. If
looking for a compatible TPM 1.2 module also try searching for Asus
90-C1B0AU-00XBN0VZ

The BIOS (SPI) flash chip is a socketed 16M-bit/2M-byte Winbond
25Q16BVAIG DIP8 that is fairly easy to remove with a DIP extractor (no
soldering required).

Best regards…

Hi @Justin, I have a similar setup and wanted to know if we could chat about some issues I’m having?

Hi @Justin https://forum.qubes-os.org/u/justin, I have a similar setup
and wanted to know if we could chat about some issues I’m having?

Greetings @jr77 Would you mind describing the issues you are having
and/or posting a HCL Report for your setup?

I would be glad to try to help! Just please understand I interact with
the forum through email, am not an expert, and may be slow to respond.

Using the Forum Via Email and I only
watch certain threads. Please respond here (or in All Around Qubes) if
you open new threads related to your setup so hopefully I don’t miss
them.

Possibly helpful links in the meantime:
https://forum.qubes-os.org/search?q=KGPE

If you would prefer to not post publicly here please feel free to
suggest an alternative. Best regards…

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

I have had difficulty with them as well. But up until 4.2-rc4 I made it work. Just wanted to cross-post my recent post on that here:

I see you are still on 4.0 so can’t compare notes on how 4.2 is working. But these issues have made my D16 (my main driver) not very usable for now, so hoping to find a solution.

1 Like

Pleasure to hear from you scallyob!

Justin:

I had difficulties with the onboard USB controllers, although I was
always using the rear PS/2 ports.

I have had difficulty with them as well. But up until 4.2-rc4 I made it
work. Just wanted to cross-post my recent post on that here:

USB device and PCI Sound card issues persistent with 4.2-rc4
<https://forum.qubes-os.org/t/usb-device-and-pci-sound-card-issues-persistent-with-4-2-rc4/21561> User Support <https://forum.qubes-os.org/c/user-support/5>

Thanks you for the info/link. I’ll try to investigate further and report
anything useful.

After upgrading from 4.1 to 4.2-rc4, what was once an annoyance
seems to be a real problem. Prior to upgrading, the symptoms below
could generally be overcome after a max of 3 reboots. These symptoms
have existed since back in Qubes 3.1 or so. Since fully upgrading to
4.2-rc4, after over a dozen reboots, the problems are persisting.
SYMPTOMS: 1.USB devices aren’t recognized, can’t be attached, or
aren’t recognized. a. trackpad - is often not recognized - this is
my indication that the other p…

It might be useful scallyob if you are willing to share what firmware
are you using dasharo, coreboot 4.11, stock, or something else?

Somewhat reluctantly, I’m going to ping (also known as annoy) a few
experts in the hope they may have some insights they’d be willing to
share. @pietrushnic @miczyg @Insurgo @mike_banon

I see you are still on 4.0 so can’t compare notes on how 4.2 is working.
But these issues have made my D16 (my main driver) not very usable for
now, so hoping to find a solution.

Yeah I’ve pretty much taken this machine offline until I can assess it’s
vulnerabilities and give it the love it deserves (I hope to get back to
it before Christmas 2023).

Since I’m probably annoying lots of my hero’s already, here’s a few
other pings: @marmarek and @Demi

Hope someone can help, or least provide breadcrumbs to follow.
@scallyob I really appreciate you sharing your 4.1 and 4.2-rc4
experience(s).

Somewhat reluctantly, I’m going to ping (also known as annoy) a few
experts in the hope they may have some insights they’d be willing to
share.

I’m not sure where ping == annoy is coming from, especially that you marked us for the first time in this post :slight_smile: Definitely not an annoy.

Thierry from Insurgo (heads maintainer) had been working on KGPE-D16 heads support in free time: WiP: current kgpe-d16 boards against dasharo/coreboot (kgpe-d16 dasharo release 0.4) by tlaurion · Pull Request #1303 · linuxboot/heads · GitHub
Although, as you can see, this is WIP. This PR is using the Dasharo coreboot fork instead of upstream coreboot 4.11, which was repeatedly reported as being more stable than 4.11.

All that said, 3mdeb lacks resources to address lingering issues for this board (despite our best intentions), unfortunately: Issues · Dasharo/dasharo-issues · GitHub

As for USB, we have also noticed that the USB ports are not working reliably, but we do not know the cause yet.

1 Like

That is totally from me. Thank you, so much, for your response.

:frowning:
Stil I really really thank you for your work. When / iI I ever find the money tree :smile:
I promise you wil receive the first harvest

I’m no expert but @Insurgo comment below seems plausible to me, although I’m admittedly ignorant :

I don’t know, you’ve probably already investigated this, but unfortunately I have little else to offer at the moment.

Thanks for replying and tolerating my “ping == annoy” misunderstanding. Best regards…

This was installed on libreboot with petitboot. This was a Vikings setup. I don’t know much more than that.

Thanks for getting this more attention!