Fwd: Re: Fwd: F2A85M IOMMU still not working for RIchland CPUS

[Kinky Nekoboi]

-------- Weitergeleitete Nachricht --------
Betreff: 	Re: [coreboot] Re: Fwd: F2A85M IOMMU still not working for
RIchland CPUS
Datum: 	Thu, 18 Apr 2019 11:38:16 +0200
Von: 	Kinky Nekoboi 
An: 	Mike Banon

CPU : A8-6600K

[    1.271514] microcode: CPU0: patch_level=0x0600110f
[    1.271521] microcode: CPU1: patch_level=0x0600110f
[    1.271532] microcode: CPU2: patch_level=0x0600110f
[    1.271538] microcode: CPU3: patch_level=0x0600110f
[    1.271583] microcode: Microcode Update Driver: v2.2.
i compiled from the master tree, build on 16. April 2019

no microcode was included in that build.

next step i will try if, the problems occur again if i remove microcode
updates via llinux kernel.

here is cbmem output as attachment

Am 18.04.19 um 06:08 schrieb Mike Banon:
> > also it seems that IOMMU is working now...
>
> Congratulations with these amazing news! Please tell, what version of
> coreboot you've currently installed? Also, have you used this
> microcode updating patch from DangerousPrototypes page before building
> your current coreboot build?
> > maybe cause i have microcode updates in the kernel included this time ?
>
> By the way, the microcode updates provided by Linux are _older_ than
> what this "microcode updating patch" is providing : simply because AMD
> has shared their latest update with some proprietary UEFI makers but
> didn't share them with the opensource world (and so we had to get them
> by manually extracting). But if the kernel sees that a newer microcode
> version is loaded, it doesn't replace it. Please, could you check and
> tell, what microcode version do you see as installed?

[Kinky Nekoboi]

IOMMU and system still booting without linux kernel level microcode

Am 18.04.19 um 11:38 schrieb Kinky Nekoboi:
> -------- Weitergeleitete Nachricht --------
> Betreff: 	Re: [coreboot] Re: Fwd: F2A85M IOMMU still not working for
> RIchland CPUS
> Datum: 	Thu, 18 Apr 2019 11:38:16 +0200
> Von: 	Kinky Nekoboi 
> An: 	Mike Banon
>
> CPU : A8-6600K
>
> [    1.271514] microcode: CPU0: patch_level=0x0600110f
> [    1.271521] microcode: CPU1: patch_level=0x0600110f
> [    1.271532] microcode: CPU2: patch_level=0x0600110f
> [    1.271538] microcode: CPU3: patch_level=0x0600110f
> [    1.271583] microcode: Microcode Update Driver: v2.2.
> i compiled from the master tree, build on 16. April 2019
>
> no microcode was included in that build.
>
> next step i will try if, the problems occur again if i remove microcode
> updates via llinux kernel.
>
> here is cbmem output as attachment
>
> Am 18.04.19 um 06:08 schrieb Mike Banon:
> > > also it seems that IOMMU is working now...
> >
> > Congratulations with these amazing news! Please tell, what version of
> > coreboot you've currently installed? Also, have you used this
> > microcode updating patch from DangerousPrototypes page before building
> > your current coreboot build?
> > > maybe cause i have microcode updates in the kernel included this time ?
> >
> > By the way, the microcode updates provided by Linux are _older_ than
> > what this "microcode updating patch" is providing : simply because AMD
> > has shared their latest update with some proprietary UEFI makers but
> > didn't share them with the opensource world (and so we had to get them
> > by manually extracting). But if the kernel sees that a newer microcode
> > version is loaded, it doesn't replace it. Please, could you check and
> > tell, what microcode version do you see as installed?
>
> coreboot mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

[Mike Banon]

Thank you, Nekoboi. If I understand it correctly: you haven't changed
anything at coreboot or its' configuration, but your IOMMU suddenly started
to work? ;-) (unknown what got it working?) Also, please could you make
almost the same coreboot build, with the only difference is these
microcodes installed by the unofficial patch:
http://dangerousprototypes.com/docs/Lenovo_G505S_hacking#AMD_microcode_updat...
, and then try it again with the same Linux to see if it's still working.
With this patch applied, the microcode level should be 0x0600111f (...1f
instead of ...0f) to confirm the successful installation.

On Thu, Apr 18, 2019 at 1:35 PM Kinky Nekoboi 
wrote:
> IOMMU and system still booting without linux kernel level microcode
> Am 18.04.19 um 11:38 schrieb Kinky Nekoboi:
>
> -------- Weitergeleitete Nachricht --------
> Betreff: Re: [coreboot] Re: Fwd: F2A85M IOMMU still not working for
> RIchland CPUS
> Datum: Thu, 18 Apr 2019 11:38:16 +0200
> Von: Kinky Nekoboi  
> An: Mike Banon 
>
> CPU : A8-6600K
>
> [    1.271514] microcode: CPU0: patch_level=0x0600110f
> [    1.271521] microcode: CPU1: patch_level=0x0600110f
> [    1.271532] microcode: CPU2: patch_level=0x0600110f
> [    1.271538] microcode: CPU3: patch_level=0x0600110f
> [    1.271583] microcode: Microcode Update Driver: v2.2.
> i compiled from the master tree, build on 16. April 2019
>
> no microcode was included in that build.
>
> next step i will try if, the problems occur again if i remove microcode
> updates via llinux kernel.
>
> here is cbmem output as attachment
>
> Am 18.04.19 um 06:08 schrieb Mike Banon:
>
> also it seems that IOMMU is working now...
>
> Congratulations with these amazing news! Please tell, what version of
> coreboot you've currently installed? Also, have you used this microcode
> updating patch from DangerousPrototypes page before building your current
> coreboot build?
>
> maybe cause i have microcode updates in the kernel included this time ?
>
> By the way, the microcode updates provided by Linux are _older_ than what
> this "microcode updating patch" is providing : simply because AMD has
> shared their latest update with some proprietary UEFI makers but didn't
> share them with the opensource world (and so we had to get them by manually
> extracting). But if the kernel sees that a newer microcode version is
> loaded, it doesn't replace it. Please, could you check and tell, what
> microcode version do you see as installed?
>
> coreboot mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>
> coreboot mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]