[coreboot] Re: Status of Board Asus KGPE-d16
> Has [2] updated the default microcode for the G505s to the latest available > version? (no longer requiring patches with a separate script?) Yes, this microcode question is solved for G505S now. But I have some other not-merged patches which are also useful (e.g. dGPU patch), so still need to run some scripts before building a coreboot. Here is the first public version of a ./csb_patcher.sh script I am working on currently - https://pastebin.com/HbTvZUiv . It helps to patch your coreboot more conveniently (with SHA256 verifications as always) and could even download the floppies collection! There are almost 600 lines of code and some parts of it aren't optimized, but it already works great - so, despite there's a long TODO list, I'm not ashamed to release it. And I set the expiration time for this paste because there should be a better version eventually... Hopefully you could test it or take a look on its' code and share some feedback, e.g. regarding its' POSIX compatibility (I'm trying to make this script as portable as possible) Best regards, Mike Banon On Sun, May 26, 2019 at 12:00 PM Kinky Nekoboi wrote: > > Hello Mike, > > thank you for the verbose anwser, as always. > > The board is not in my possession yet. > > I ordered it as upgrade for my Fileserver. > > I will investigate it, after i have it up running. > > Kinky greetings. > > > Am 25.05.19 um 10:15 schrieb Mike Banon: > > 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 > > 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 ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: Status of Board Asus KGPE-d16
Hello Mike, thank you for the verbose anwser, as always. The board is not in my possession yet. I ordered it as upgrade for my Fileserver. I will investigate it, after i have it up running. Kinky greetings. Am 25.05.19 um 10:15 schrieb Mike Banon: > 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 > 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 ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: Status of Board Asus KGPE-d16
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 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
