[coreboot] KGPE-D16 coreboot support open call

Hi all, since Immunefi was so kind to put 15k EUR pledge for [1] we host open call where we will discuss future of KGPE-D16 and its coreboot support. If you interested about this hardware feel free to join at 15:00 UTC: https://meet.3mdeb.com/kgpe-d16-refresh We will post minutes on github. [1]

[coreboot] KGPE-D16: Working single-CPU configuration with 96 GB of RAM

Hi folks, albeit the board has been deprecated in coreboot 4.11, I wanted to contribute a working RAM setup for all who still use it. I managed to run a KGPE-D16 with a single CPU (Opteron 6380) and 96 GB of RAM and the following LRDIMMs: orange slots: 4x Samsung 16 GB DDR3L reg ECC

[coreboot] KGPE-D16 maintainership

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi all, we see a lot of attention around KGPE-D16 maintainership problems. After discussion with Thierry Laurion (Insurgo) at OSFC2019 3mdeb decided to help in maintaining that platform by organizing crowd founding campaign or getting founds in

[coreboot] KGPE-D16: using linux kernel with SLUB MEM_ALLOCATOR -> KERNEL SPINLOCK PANIC

not sure if coreboot or kernel related. vanila kernel 4.19.62 with SLAB allocater build works fine. Debians Busters default kernel 4.19.x with SLUB panics. see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930029 see Bootlog: oading Linux 4.19.0-5-amd64 ...Loading Linux 4.19.0-5-amd64

[coreboot] KGPE-D16: coreboot-4.5 stuck in boot loop. Help on getting the system to boot or flash newer version

Hello and thank you in advance for your time.  I recently bought a KGPE-D16 motherboard with a single AMD Opeteron 8262SE and coreboot installed. I bought from another supplier 4 memory sticks Samsung 8GB (M393B1K70DH0-YK0) that per this thread[1] should work with coreboot. I am able to start the

Re: [coreboot] KGPE-D16/KCMA-D8 Tip: Force sensor module load order to avoid the improper changing of hwmon paths which breaks fancontrol

Hi, >> Side note: I still wish there was an easier way to do this; I never >> bothered transferring documentation to GIT because of the added time / >> complexity vs. the Wiki WYSIWYG editor. we are writing documentation in markdown now. IMHO, a much better choice than WYSIWYG because you can

Re: [coreboot] KGPE-D16/KCMA-D8 Tip: Force sensor module load order to avoid the improper changing of hwmon paths which breaks fancontrol

On 12/11/2018 05:34 PM, Timothy Pearson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 12/10/2018 07:48 PM, taii...@gmx.com wrote: >> Applicable to: >> SP5100 AMD C32/G34 systems such as the KCMA-D8 and KGPE-D16. >> >> Situation: If you don't have OpenBMC installed you need to

Re: [coreboot] KGPE-D16/KCMA-D8 Tip: Force sensor module load order to avoid the improper changing of hwmon paths which breaks fancontrol

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/10/2018 07:48 PM, taii...@gmx.com wrote: > Applicable to: > SP5100 AMD C32/G34 systems such as the KCMA-D8 and KGPE-D16. > > Situation: If you don't have OpenBMC installed you need to run > pwmconfig/fancontrol to manage fan speeds. > >

[coreboot] KGPE-D16/KCMA-D8 Tip: Force sensor module load order to avoid the improper changing of hwmon paths which breaks fancontrol

Applicable to: SP5100 AMD C32/G34 systems such as the KCMA-D8 and KGPE-D16. Situation: If you don't have OpenBMC installed you need to run pwmconfig/fancontrol to manage fan speeds. Problem: Normally the hwmon paths will change almost every boot resulting in the need to run pwmconfig repeatedly

[coreboot] KGPE-D16/KCMA-D8 "PIKE" LSI SAS 2308 addon cards are going for $22 on fleabay

Thought y'all should know. This is what installs in the weird reversed pci-e x4 slot at the bottom of the motherboard. Notes: * It will obstruct the usage of the PCI slot and the use of a dual slot card in the bottom most PCI-e slot (the white one not the blue "graphics" slots) * KCMA-D8 has a

Re: [coreboot] KGPE-D16: Trouble using three PCIe cards simultaneously

Forgot to say - a theory is that the issue may be that you lack enough lanes in the slot you are using. As ASUS was cheap they didn't add a second northbridge to obtain more PCI-e lanes as was done with the TYAN boards so while the slots are x16 physical you can't run all of them at that all the

Re: [coreboot] KGPE-D16: Trouble using three PCIe cards simultaneously

Did you get my email? can you provide a: dmesg # lspci -t -v # lspci -vv Thanks Most quad adapters use PCI-e bifurcation not a PCI-e switch and AFAIK not many boards support bifurcation so you would need a switched model which you might have (I am not sure) if you do have a switched card I would

Re: [coreboot] KGPE-D16: Trouble using three PCIe cards simultaneously

Thank you for your answers, Jason and Alberto. While it's true that the hypercard is a PCIe 3.0 device, I did not see the reason yet why it would not operate in a PCIe 2.0 slot with lower throughput. And I am not sure but - is Intel VROC required to use all four M.2 slots? Anyways, I am happy

Re: [coreboot] KGPE-D16: Trouble using three PCIe cards simultaneously

On 02/06/2018 22:03, Daniel Kulesz via coreboot wrote: > Hi folks, > > maybe this is not really coreboot-related, but I am experiencing an issue > with the KGPE-D16 that there seems to be no working constellation how the > following three cards can be put into service: > > - nvidia GPU (PCIe

Re: [coreboot] KGPE-D16: Trouble using three PCIe cards simultaneously

Hi Daniel, I also have a coreboot KGPE-D16 but am using different accessory cards. I took a look at the specs on your Hyper card and compared it to KGPE specs and I think one or more of the following might be the issue: * It looks like the Hyper card is a PCIE 3.0 device and the KGPE-D16 has

[coreboot] KGPE-D16: Trouble using three PCIe cards simultaneously

Hi folks, maybe this is not really coreboot-related, but I am experiencing an issue with the KGPE-D16 that there seems to be no working constellation how the following three cards can be put into service: - nvidia GPU (PCIe 3 x16, takes 1 slot but occupies two) - ASUS hypercard (PCIe 3 x16,

Re: [coreboot] KGPE-D16 / Problem booting with two CPUs

Hi Kyösti, I will try to boot again with 6276+6238 with the current build and I will inform the result. Regards, - Eli On 03/05/18 20:07, Kyösti Mälkki wrote: > On Thu, May 3, 2018 at 8:57 PM, Elisenda Cuadros wrote: >> Finally I acquired another 6276 CPU (it was the fastest

Re: [coreboot] KGPE-D16 / Problem booting with two CPUs

On Thu, May 3, 2018 at 8:57 PM, Elisenda Cuadros wrote: > Finally I acquired another 6276 CPU (it was the fastest and cheapest > option). > > It works perfect. > Maybe not related, but KGPE-D16 was affected by a regression [1] on SMP init. That was present on master from Aug 2017

Re: [coreboot] KGPE-D16 / Problem booting with two CPUs

Finally I acquired another 6276 CPU (it was the fastest and cheapest option). It works perfect. If I can try (in the future) another different 16-core CPU, I will report the result. Thank you for you kind support. Regards, - Eli On 11/04/18 21:30, Timothy Pearson wrote: > This may be a

Re: [coreboot] KGPE-D16 / Problem booting with two CPUs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 That should work, yes. It's the very early init code that is getting confused with the differing core counts, likely related to APIC setup or similar. On 04/11/2018 03:26 PM, taii...@gmx.com wrote: > But it would be possible to have two CPU's with

Re: [coreboot] KGPE-D16 / Problem booting with two CPUs

But it would be possible to have two CPU's with the same core count but differing frequencies? Thanks 0xDF372A17.asc Description: application/pgp-keys -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] KGPE-D16 / Problem booting with two CPUs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This may be a general coreboot limitation at the moment. The compatibility sections for mixed CPUs in the BKDG are more concerned with total power delivery and proper P-state setup than anything else. If I recall correctly, coreboot assumes both

Re: [coreboot] KGPE-D16 / Problem booting with two CPUs

Thank you for your reply Timothy. Vendor Bios doesn't print any special message regarding this. In fact it shows a total of 28 cores (16+12). I thought mixing CPUs from same families was supported. Regards, - Eli On 11/04/18 20:44, Timothy Pearson wrote: > I don't know if coreboot has

Re: [coreboot] KGPE-D16 / Problem booting with two CPUs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I don't know if coreboot has support for differing CPUs in the same mainboard; it's not something I can recall testing at any point. The failure is occurring far before memory initialization, in CAR, in core setup. I'd guess it has something to do

[coreboot] KGPE-D16 / Problem booting with two CPUs

Hello, After testing the board for some weeks I bought another CPU (6276). I installed this into CPU1 slot and a 6238 in CPU2. I checked that both CPUs are shining and also the memory (Micron MT18JSF25672PDZ-1G4F1DD, populated in A2/C2/E2/G2 slots). The problem is that Coreboot seems to hang at

Re: [coreboot] KGPE-D16 AMD-vi fails because combined sata is enabled

I am curious as to why the emulated combined IDE/SATA mode would be on in the first place if anyone knows, what is the use case for this? -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] KGPE-D16 AMD-vi fails because combined sata is enabled

Hmm it works for me on Xen 4.10 (I don't normally use xen but I installed it to check for you) (XEN) AMD-Vi: Disabled HAP memory map sharing with IOMMU (XEN) AMD-Vi: IOMMU 0 Enabled. (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Strict (XEN) Interrupt remapping enabled Btw does anyone

Re: [coreboot] KGPE-D16 AMD-vi fails because combined sata is enabled

Thank you for the clarification. I'll try to figure this out later this week. Any help would be appreciated. I suppose I should file an issue. Will do. Le ven. 3 nov. 2017 04:19, Patrick Georgi a écrit : > That's the bitfield item's size field, not its default value. > > >

Re: [coreboot] KGPE-D16 AMD-vi fails because combined sata is enabled

That's the bitfield item's size field, not its default value. Am Fr., 3. Nov. 2017 um 04:56 Uhr schrieb Thierry Laurion < thierry.laur...@gmail.com>: > As I understand the code, KGPE-d16 doesn't use AGESA part (nor any?). > > Any reason why this value would be defaulting to enabled for whole

Re: [coreboot] KGPE-D16 AMD-vi fails because combined sata is enabled

As I understand the code, KGPE-d16 doesn't use AGESA part (nor any?). Any reason why this value would be defaulting to enabled for whole sb700 dependents? --- a/src/vendorcode/amd/cimx/sb700/SBTYPE.h +++ b/src/vendorcode/amd/cimx/sb700/SBTYPE.h @@ -133,7 +133,7 @@ typedef struct _AMDSBCFG

Re: [coreboot] KGPE-D16 AMD-vi fails because combined sata is enabled

Thierry Laurion wrote: > ENABLE_IDE_COMBINED_MODE available for sp800 but not for sp700, for ewhich > sp5100 is derived from: .. > Suggested Workaround > Disable combined mode by setting a platform BIOS callback option to CIMx > called "SataIdeCombinedMode" to 0. .. > Is there something i'm

[coreboot] KGPE-D16 AMD-vi fails because combined sata is enabled

Xen error: (XEN) AMD-Vi: SP5100 erratum 28 detected, disabling IOMMU. (XEN) If possible, disable SATA Combined mode in BIOS or contact your vendor for BIOS update. (XEN) AMD-Vi: Error initialization (XEN) I/O virtualisation disabled -but HAP is working, (XEN) HVM: SVM enabled (XEN) HVM: Hardware

Re: [coreboot] [KGPE-D16] No video output with Ati x600se GPU

Hello, > No, afaik the VGA rom is only needed for native gfx init on (some) devices > with embedded graphics but not for add-on pci(e) cards. Ok. > It seems like you are not using SeaBIOS. Normally, Seabios initializes PCI > devices. > Are you sure you are using the same coreboot

Re: [coreboot] [KGPE-D16] No video output with Ati x600se GPU

On 10/15/2017 09:18 AM, Daniel Kulesz via coreboot wrote: Hi, I'm having issues to use an Ati x600se 128mb GPU (OEM DELL) with my KGPE-D16. With ASUS BIOS, the card works fine (either in first or second pcie-x16 slot) With coreboot, no video output. The board still boots but the card isn't

Re: [coreboot] [KGPE-D16] No video output with Ati x600se GPU

Hi, > I'm having issues to use an Ati x600se 128mb GPU (OEM DELL) with my KGPE-D16. > With ASUS BIOS, the card works fine (either in first or second pcie-x16 slot) > With coreboot, no video output. The board still boots but the card isn't > detected at all. (either in first or second pcie-x16

Re: [coreboot] KGPE-D16/KCMA-D8 TPM support?

On 10/07/2017 11:14 AM, Thierry Laurion wrote: Any input on TPM since that post? I am planning on beginning to work on heads KGPE-D16 heads support, server/workstation on which Qubes v4 actually works. Initialisation of TPM throws errors on from Qubes, but it isn't owned yet, and haven't played

Re: [coreboot] KGPE-D16/KCMA-D8 TPM support?

Any input on TPM since that post? I am planning on beginning to work on heads KGPE-D16 heads support, server/workstation on which Qubes v4 actually works. Initialisation of TPM throws errors on from Qubes, but it isn't owned yet, and haven't played with it yet. Bought this

Re: [coreboot] KGPE-D16 PCI passthrough

On 09/12/2017 02:06 AM, Iru Cai wrote: I seem to know what happened to me. Now I pass throught 00.12.{0,1,2} and there's no problem now. But if I plug in my keyboard and mouse, then because of the USB controller is passed to the VM, then I have no keyboard or mouse to use, so the system seems

Re: [coreboot] KGPE-D16 PCI passthrough

I seem to know what happened to me. Now I pass throught 00.12.{0,1,2} and there's no problem now. But if I plug in my keyboard and mouse, then because of the USB controller is passed to the VM, then I have no keyboard or mouse to use, so the system seems to hang. However, I still don't know why

Re: [coreboot] KGPE-D16 PCI passthrough

On 09/08/2017 02:12 AM, Iru Cai wrote: On Fri, Sep 8, 2017 at 2:02 PM, taii...@gmx.com wrote: On 09/08/2017 12:44 AM, Iru Cai wrote: On Fri, Sep 8, 2017 at 11:42 AM, taii...@gmx.com wrote: On 09/07/2017 11:21 PM, Iru Cai wrote: Hi, I have a problem

Re: [coreboot] KGPE-D16 PCI passthrough

On Fri, Sep 8, 2017 at 2:02 PM, taii...@gmx.com wrote: > On 09/08/2017 12:44 AM, Iru Cai wrote: > > On Fri, Sep 8, 2017 at 11:42 AM, taii...@gmx.com wrote: >> >> On 09/07/2017 11:21 PM, Iru Cai wrote: >>> >>> Hi, >>> I have a problem about PCI passthrough

Re: [coreboot] KGPE-D16 PCI passthrough

On 09/08/2017 12:44 AM, Iru Cai wrote: On Fri, Sep 8, 2017 at 11:42 AM, taii...@gmx.com wrote: On 09/07/2017 11:21 PM, Iru Cai wrote: Hi, I have a problem about PCI passthrough on KGPE-D16. I plugged in a PCI to USB adapter to the PCI slot, and it's in IOMMU group 7 with

Re: [coreboot] KGPE-D16 PCI passthrough

On 09/07/2017 11:21 PM, Iru Cai wrote: Hi, I have a problem about PCI passthrough on KGPE-D16. I plugged in a PCI to USB adapter to the PCI slot, and it's in IOMMU group 7 with the ASpeed video card and the LSI 1394a controller. I try to pass them all to a VM, but then kernel crashes. I tried

[coreboot] KGPE-D16 PCI passthrough

Hi, I have a problem about PCI passthrough on KGPE-D16. I plugged in a PCI to USB adapter to the PCI slot, and it's in IOMMU group 7 with the ASpeed video card and the LSI 1394a controller. I try to pass them all to a VM, but then kernel crashes. I tried in Linux 4.9.47 and Linux 4.12.10. Does

Re: [coreboot] KGPE-D16 BMC port

Q Who has Self-hosting option? A https://en.wikipedia.org/wiki/Comparison_of_source_code_hosting_facilities#Features On Wed, Aug 30, 2017 at 1:18 AM, taii...@gmx.com wrote: > On 08/29/2017 02:24 PM, Timothy Pearson wrote: > >> Let me know what you think of the OpenBMC system.

Re: [coreboot] KGPE-D16 BMC port

On 08/29/2017 02:24 PM, Timothy Pearson wrote: Let me know what you think of the OpenBMC system. We're considering allowing bugs to be tracked on GitHub; is this something the community wants to see or would a separate Bugzilla type install be preferred? We want to provide the infrastructure

[coreboot] KGPE-D16 BMC port

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 We are pleased to announce that the OpenBMC port for the KGPE-D16 has reached the first release stage! https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php While it has inherited some of the rough edges of its Facebook predecessor

Re: [coreboot] KGPE-D16/KCMA-D8 TPM support?

taii...@gmx.com wrote: > Does anyone know what TPM's are compatible? Sorry, can't help with that. > I also want to know what coreboot's tpm support is like these days, such > as how can you perform an erase/reset like one could with a standard OEM > bios. Is that in the realm of the BIOS?

[coreboot] KGPE-D16/KCMA-D8 TPM support?

Does anyone know what TPM's are compatible? I also want to know what coreboot's tpm support is like these days, such as how can you perform an erase/reset like one could with a standard OEM bios. - Thanks in advance -- coreboot mailing list: coreboot@coreboot.org

[coreboot] KGPE-D16: More power drain experiments with coreboot vs. vendor bios

Hi all, I did some more testing with the Opteron CPUs, and it seems there is some defect in coreboot as it does not report the state P5. I attached the output of "cpupower frequency-info" which I obtained on a 1x6220/64G configuration running coreboot and running the vendor bios. I also did

[coreboot] KGPE-D16 - how to get PCI-e x16 on Slot 4?

According to the asus documentation it should be x16 if slot 2 is unoccupied, which it is. I currently only have x8, I have tried changing the gpp config in devicetree.cb based on the SR5690 documentation but that results in a coreboot bootloop. How many PCI-e slots can you use concurrently

Re: [coreboot] KGPE-D16: Most severe hang failure sorted out + boot time measures

On Thu, 13 Apr 2017 17:17:03 -0500 Timothy Pearson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > > > Unfortunately, I had the option already enabled when using the > > "config-unreliable" in my initial posting. So it looks like this setting is

Re: [coreboot] KGPE-D16: Most severe hang failure sorted out + boot time measures

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > > Unfortunately, I had the option already enabled when using the > "config-unreliable" in my initial posting. So it looks like this setting is > not effective in stopping the hangs. > > Cheers, Daniel After further external analysis once the

Re: [coreboot] KGPE-D16: Most severe hang failure sorted out + boot time measures

Hi Timothy, On Tue, 21 Mar 2017 10:32:46 -0500 Timothy Pearson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 03/12/2017 07:58 PM, Daniel Kulesz via coreboot wrote: > > Hi folks, > > > > as reported, the KGPE-D16 was mostly unusable for me in

Re: [coreboot] KGPE-D16: Most severe hang failure sorted out + boot time measures

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/12/2017 07:58 PM, Daniel Kulesz via coreboot wrote: > Hi folks, > > as reported, the KGPE-D16 was mostly unusable for me in my 2x Opteron 6276 + > 128 GB RAM configuration as it simply did not boot reliably - even with > serial console

[coreboot] KGPE-D16: Most severe hang failure sorted out + boot time measures

Hi folks, as reported, the KGPE-D16 was mostly unusable for me in my 2x Opteron 6276 + 128 GB RAM configuration as it simply did not boot reliably - even with serial console debugging disabled completely. After experimenting with various config options and comparing my best "known

[coreboot] KGPE-D16: More insights on the PCI hang failure

Hi folks, as we know, the KGPE-D16 is likely to hang during PCI init, especially if the serial console is enabled (Timothy mentioned that he did not observe failures with the debug level of the console lowered - however, for me this did not work). Typical symptoms look like the following:

Re: [coreboot] KGPE-D16 and Samsung DDR3L memory sticks

Hi, > > after a lengthy bisection run I was able to nail down the commit which is > > causing the MC4 errors in the configurations I tested. I reverted the > > commit on top of current master, and now my KGPE-D16 fully works without > > MC4 errors in both 1-CPU-package und 2-CPU-package

Re: [coreboot] KGPE-D16 and Samsung DDR3L memory sticks

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/15/2017 08:07 AM, Daniel Kulesz via coreboot wrote: > Hi folks, > > after a lengthy bisection run I was able to nail down the commit which is > causing the MC4 errors in the configurations I tested. I reverted the commit > on top of current

Re: [coreboot] KGPE-D16 and Samsung DDR3L memory sticks

Hi folks, after a lengthy bisection run I was able to nail down the commit which is causing the MC4 errors in the configurations I tested. I reverted the commit on top of current master, and now my KGPE-D16 fully works without MC4 errors in both 1-CPU-package und 2-CPU-package configurations -

Re: [coreboot] KGPE-D16 and Samsung DDR3L memory sticks

Hi folks, here's a short update regarding the beforementioned DDR3L Samsung memory sticks on the KGPE-D16 running coreboot. Thanks to help and hints from Timothy, I experimented with different cpu/memory configurations and have done some stress and memory testing. So far, I have a few

Re: [coreboot] KGPE-D16 and Samsung DDR3L memory sticks

Dear Daniel, Thank you for keeping us in the loop. Am Samstag, den 11.02.2017, 16:14 +0100 schrieb Daniel Kulesz: > To answer my question myself: It works partially. > > > 1.) Samsung M393B1K70DH0-YK0 > > > > Type: DDR3 DIMM 240-Pin, reg ECC • Ranks/Banks: dual rank, x4 • Modules: 1x > >

Re: [coreboot] KGPE-D16: Excessive power consumption in idle

On Fri, 10 Feb 2017 00:37:57 -0500 "taii...@gmx.com" wrote: > On 02/09/2017 06:46 PM, Daniel Kulesz via coreboot wrote: > > > Hi, > > > > I just compiled and flashed the lastest master on my KGPE-D16 with pretty > > much the default config. My board has only one of the CPU

Re: [coreboot] KGPE-D16 and Samsung DDR3L memory sticks

To answer my question myself: It works partially. > 1.) Samsung M393B1K70DH0-YK0 > > Type: DDR3 DIMM 240-Pin, reg ECC • Ranks/​Banks: dual rank, x4 • Modules: 1x > 8GB • JEDEC: PC3L-12800R • Voltage: 1.35V > I got 8 of these working with one CPU package on the KGPE-D16 with one of the latest

Re: [coreboot] KGPE-D16: Excessive power consumption in idle

On 02/09/2017 06:46 PM, Daniel Kulesz via coreboot wrote: Hi, I just compiled and flashed the lastest master on my KGPE-D16 with pretty much the default config. My board has only one of the CPU sockets populated with an Opteron 6276. Things seem to work fine so far, except the power

[coreboot] KGPE-D16: Excessive power consumption in idle

Hi, I just compiled and flashed the lastest master on my KGPE-D16 with pretty much the default config. My board has only one of the CPU sockets populated with an Opteron 6276. Things seem to work fine so far, except the power consumption. The "sensors" command reports a CPU power consumption

[coreboot] KGPE-D16 and Samsung DDR3L memory sticks

Hi folks, I spent some time checking the available RAM options for the KGPE-D16. The current list in the wiki is not very comprehensive and the models listed there are not easy to find on the market. After some research, I identified two "promising" candidates: 1.) Samsung M393B1K70DH0-YK0

Re: [coreboot] KGPE-D16 with over 128GB RAM - works reliably yet?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/29/2017 09:38 AM, Peter Stuge wrote: > Timothy Pearson wrote: >> Populating all four slots closest to CPU1 with large ECC registered >> DIMMs is a surefire way to recreate the instability -- note a >> training failure is not common, the main

Re: [coreboot] KGPE-D16 with over 128GB RAM - works reliably yet?

Timothy Pearson wrote: > Populating all four slots closest to CPU1 with large ECC registered > DIMMs is a surefire way to recreate the instability -- note a > training failure is not common, the main issue is that the marginal > routing causes severe memory corruption when the BKDG-recommended >

Re: [coreboot] KGPE-D16 with over 128GB RAM - works reliably yet?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/27/2017 03:27 PM, taii...@gmx.com wrote: > Is anyone using this configuration? does it work reliably? I am asking > as I don't know if this has been fixed yet. > > For a real server platform this is a must have, the ram issues are the > one

[coreboot] KGPE-D16 with over 128GB RAM - works reliably yet?

Is anyone using this configuration? does it work reliably? I am asking as I don't know if this has been fixed yet. For a real server platform this is a must have, the ram issues are the one valid point that leah made... - Thanks in advance for any replies -- coreboot mailing list:

Re: [coreboot] KGPE-D16 BMC Port Offer (was: Fund a TALOS Secure Workstation as coreboot build system)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/19/2017 11:36 AM, Martin Roth wrote: > Hey Merlin, > I was taking and keeping track of the pledges for Talos, so I'd be > happy to continue. > > Martin I just wanted to bring this back up for discussion. Raptor is chipping in funding for

Re: [coreboot] KGPE-D16 SR-IOV problems (iommu groups) - Anyone else tried this?

On 01/23/2017 09:23 AM, Timothy Pearson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/21/2017 02:57 AM, taii...@gmx.com wrote: It seems the PCI-e root ports on the KGPE-D16 have ARI which is needed for SR-IOV, however it is not reported via # lspci -vv I assume that is why the

Re: [coreboot] KGPE-D16 SR-IOV problems (iommu groups) - Anyone else tried this?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/21/2017 02:57 AM, taii...@gmx.com wrote: > It seems the PCI-e root ports on the KGPE-D16 have ARI which is needed > for SR-IOV, however it is not reported via # lspci -vv > I assume that is why the VF's are not assigned to IOMMU groups and thus

Re: [coreboot] KGPE-D16 SR-IOV problems (iommu groups) - Anyone else tried this?

Logs (thought I would separate them) ARI-fwd+ on the root port devcap and devctl but it doesn't have ARI listed in capabilities, I am not sure if lspci should report that on a root port as there is so little documentation for IOMMU/SR-IOV on the internet 07:00.3 Ethernet controller: Intel

Re: [coreboot] KGPE-D16 SR-IOV problems (iommu groups) - Anyone else tried this?

It seems the PCI-e root ports on the KGPE-D16 have ARI which is needed for SR-IOV, however it is not reported via # lspci -vv I assume that is why the VF's are not assigned to IOMMU groups and thus can't be assigned. I am running coreboot v4.5 (I forgot to note this as it is another late

[coreboot] KGPE-D16 SR-IOV problems (iommu groups) - Anyone else tried this?

Assigning regular devices such as a graphics card to a VM works just fine, but when I try to assign an intel i350 virtual function I receive the error "error: internal error: Invalid device :07:10.0 iommu_group file /sys/bus/pci/devices/:07:10.0/iommu_group is not a symlink" The

Re: [coreboot] KGPE-D16 Coreboot SR-IOV support?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/16/2016 07:42 PM, taii...@gmx.com wrote: > Hey does this have SR-IOV support? I want to know before I get a card. > > - thanks While I have not directly tested this functionality, there is no reason it shouldn't work with the existing AMD

[coreboot] KGPE-D16 Coreboot SR-IOV support?

Hey does this have SR-IOV support? I want to know before I get a card. - thanks -- coreboot mailing list: coreboot@coreboot.org https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] kgpe-d16 and usb boot

never mind, pilot error, I did not realize it was a linux partition, not fat32. oops. On Tue, Dec 13, 2016 at 3:20 PM ron minnich wrote: > we have a kgpe-d16 with seabios as the payload and would like to usb boot. > We have two sticks which work fine on other systems. > >

[coreboot] kgpe-d16 and usb boot

we have a kgpe-d16 with seabios as the payload and would like to usb boot. We have two sticks which work fine on other systems. seabios is not seeing the usb sticks. Anyone have configuration or other hints about what I might be doing wrong? thanks -- coreboot mailing list:

[coreboot] KGPE-D16 SR-IOV support?

Hello I am wondering if this motherboard supports with coreboot SR-IOV and PCI-e Access Control Services (needed for secure sr-iov apparently) Information: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US=displayKC=1036811

Re: [coreboot] KGPE-D16 Black SATA2 ports do not work

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/09/2016 03:50 AM, aet...@openmailbox.org wrote: > Hello, > > I have a small issue with KGPE-D16. > The two black sata2 ports do not work. (The SATA2 red ones work fine. > All SAS/SATA3 work fine as well with Pike 2008 card.) > > With Asus BIOS

[coreboot] KGPE-D16 Black SATA2 ports do not work

Hello, I have a small issue with KGPE-D16. The two black sata2 ports do not work. (The SATA2 red ones work fine. All SAS/SATA3 work fine as well with Pike 2008 card.) With Asus BIOS they work fine. I tried with several HDD just to make sure but they are not detected at all. Please find my

Re: [coreboot] kgpe-d16

* ron minnich [160620 20:19]: > I have a kgpe-d16 with coreboot and it *was* working with linux. I now have a > linux kernel that won't boot on fuctory bios or coreboot. I can't recall > changing anything ... > > If somebody's got a known good .config for linux I could sure

[coreboot] kgpe-d16

I have a kgpe-d16 with coreboot and it *was* working with linux. I now have a linux kernel that won't boot on fuctory bios or coreboot. I can't recall changing anything ... If somebody's got a known good .config for linux I could sure use it. I'm booting stock tinycore and it seems to hang a lot.