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

[Kinky Nekoboi]

hello coreboot bois and girlz,i have succesfully booted my system with
the Richland CPU installed with a Nvidia GT210 card.

also it seems that IOMMU is working now... maybe cause i have microcode
updates in the kernel included this time ?

so i have to change my bugreport as it seems that this coreboot port +
Seabios has somehow problems with Radeon Cards .... both the IGPU and
addon cards

will feed your with extra news.

your kinky nekoboi

Am 17.04.19 um 11:23 schrieb Kinky Nekoboi:
> i have tried builds for F2A85M since version 4.8 dating back to mid 2018,
>
> AMD-A8 5500 works properly with IOMMU enabled, still some stabilty
> problems (full system freezes).
>
> AMD A8-6600K shows the described behavior
>
> I also tried that manual microcode update in the past, didnt change
> anything there, i could retry it for the current build.
>
> Serial output gives no information about malfunctioning IOMMU or
> something, the strugle begins as without IOMMU the system is notable to
> initialize add-on videocards or the iGPU.
>
> Am 17.04.19 um 10:50 schrieb Mike Banon:
> > On Tue, Apr 16, 2019 at 11:23 PM Kinky Nekoboi
> >  wrote:
> > > Amd-Vi loopback errors at linux-boot,
> > > several peripherie is not working.
> > >
> > > Surely it needs only minor changes... is there anybody working at this
> > > port at the moment?
> >
> > Hi there Nekoboy (sorry if I'm repeating my older questions, I
> > forgot). Please tell:
> > IOMMU - did it ever work on F2A85M board? If you're unsure, could
> >
> > you try building the older coreboot just to check it?
> > 2) Have you installed the unofficial microcode patches? If not, please
> > run this ./ucode.sh script at your coreboot directory:
> > http://dangerousprototypes.com/docs/Lenovo_G505S_hacking#AMD_microcode_updat...
> > to conveniently and securely patch your cloned coreboot with these
> > updated microcodes, then try running Linux and tell what microcode
> > version do you see (confirmation of successful microcode install) and
> > check if IOMMU got fixed by it.
> >
> > Step "2)" should be tried both for the latest coreboot and some older
> > version. Yes, a bit time consuming, but hopefully you could test it
> > well. By the way, I got A88XM-E which is not merged to coreboot yet
> > but is based on F2A85M port, however I have a lot of parallel projects
> > and didn't have time to even test if my new (actually used) board is
> > working, so you'll have to rely on your own for a while.
> >
> > Best regards,
> > Mike Banon
> > _______________________________________________
> > 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]

Fwd: F2A85M IOMMU still not working for RIchland CPUS

[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?