ASUS KGPE-D16 is using a "microcode update infrastructure" ( which IMHO has some shortcomings, hopefully this will be discussed here - [1] ) which extracts a microcode from a container - and I haven't checked yet if my recently merged "15h microcodes" patch 28273 ([2]) brings any benefit for your board , since this "microcode update infrastructure" might replace this new microcode hardcoded into C file by an older version extracted later from a binary container. If this really happens, we could either wait for a new container released by AMD at linux-firmware.git , or if it takes too long - I could try to make such a container by myself, looking at how a current container is done, and submit for a review.
Please, could you run " cat /proc/cpuinfo | grep microcode " command and tell its' output? Hope it gives "microcode : 0x600111f". [1] - https://review.coreboot.org/c/coreboot/+/29272/2#message-771016d7aa4633189e22b3354dbba0494d8c8d0e [2] - https://review.coreboot.org/c/coreboot/+/28273/6#message-cbbdcce72362a39ad3edb056f25cd54037dce59a Best regards, Mike Banon On Fri, May 24, 2019 at 11:04 PM Kinky Nekoboi <kinky_neko...@nekoboi.moe> wrote: > > Hello fellow corebooters, > > i have succesfully build an rom for the asus kgpe-d16, with microcode > (FAM15h) enabled. > > Does anybody has experience with this systemboard. > > Is the current included ucode working with Opteron 63XX processors? > > best regards > _______________________________________________ > coreboot mailing list -- coreboot@coreboot.org > To unsubscribe send an email to coreboot-le...@coreboot.org _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
