Ryzen 7000 Testing

[ExtremeXT]

The SSDTs are in the EFI, but they are not active...

I use the properties of devices in the GPU because with Belknap the fans are not turned off, it disables the Zero-RPM, but the GPU is always at 60 degrees, even in windows if I do not remove the Zero-RPM it is always at almost 60 degrees ... and so without Zero-RPM it is at 35 degrees

In ACPI, if until now I have been testing it without any patch, it works fine anyway .....but "Replace DP68 with DP60 in AMDTable" is yours, you put it in one of the EFIs from the beginning..

But I would be very grateful if you modify the EFI to your liking and as you see it will work

I know what the Belknap framebuffer does, my point is that you only need @0,name, not @1,name... etc.
Can you send a SysReport zip and OC log from the latest BIOS and with your BIOS settings? I'm pretty sure that the MMIO values changed from the first time we did it.
Are you sure that you need AGPMInjector? Big Navi should have it working OOBE.

 

[CaseySJ]

AMD Ryzen 5 3400G APU also has ExtFamily 8.
00:164 00:022 OCCPU: Signature 810F81 Stepping 1 Model 18 Family F Type 0 ExtModel 1 ExtFamily 8 uCode 0 CPUID MAX (D/8000001F)
Their audio is the same as the patch isn't being applied. Can you only add an AMD check? I'll check if it breaks anything on my AM4 non-APU system.

The patch is checking for Family=F and ExtFamily=A. This is likely too restrictive, hence we need to find which values of Family, ExtFamily, or some other property are needed.

There may be an AMD bit flag, but OpenCore does not currently use it. In other words there is no “IsAMDCpu()” function so we may have to write one.

Heading to gym now. Be back in a couple of hours.

 

[fabiosun]

@CaseySJ added your code by my self Opencore compiled fine and booted fine, I have this:
(so I can't say I have done well)

08:237 00:016 OCAK: Setting FSB and TSC for processors other than Family F and ExtFamily A
08:239 00:001 OCAK: BusFreq = 102777706Hz, BusFCvtt2n = 41788900172, BusFCvtn2t = 441426886
08:240 00:001 OCAK: TscFreq = 3699997445Hz, TscFCvtt2n = 1160802773, TscFCvtn2t = 15891368028

 

[ExtremeXT]

The patch is checking for Family=F and ExtFamily=A. This is likely too restrictive, hence we need to find which values of Family, ExtFamily, or some other property are needed.

There may be an AMD bit flag, but OpenCore does not currently use it. In other words there is no “IsAMDCpu()” function so we may have to write one.

Could you try making it check for ExtFamily=A OR ExtFamily=8 when you get back?

if (CpuInfo->Family == 0xF && (CpuInfo->ExtFamily == 0xA || CpuInfo->ExtFamily == 0x8)) {

 

[PoMpIs]

I know what the Belknap framebuffer does, my point is that you only need @0,name, not @1,name... etc.
Can you send a SysReport zip and OC log from the latest BIOS and with your BIOS settings? I'm pretty sure that the MMIO values changed from the first time we did it.
Are you sure that you need AGPMInjector? Big Navi should have it working OOBE.

Of course, I attached SysReport..

 

[PoMpIs]

@ExtremeXT

And I like to use the AGPMinjector, we already talked about them a long time ago in insanelymac with Pavo-IM when I tried Hackinabox

GitHub - Pavo-IM/Hackinabox: MacOS install using UnRaid

MacOS install using UnRaid. Contribute to Pavo-IM/Hackinabox development by creating an account on GitHub.

github.com

With AGPM:



Without AGPM:

 

[ExtremeXT]

Of course, I attached SysReport..

That is not a debug log, it has to be done with a DEBUG version of OC. Can you send that one?

 

[muehli26]

So Audio is fully Working without speedkeeper on x670 Aorus Elite AX. Thanks to you all!

 

[PoMpIs]

That is not a debug log, it has to be done with a DEBUG version of OC. Can you send that one?

Well, I've tried with the debug version that Shaneee put yesterday with the modifications for the audio and nothing else comes out..

Now I have tried with the debug version from here:

Builds

dortania.github.io

and I think it's the same...

On this motherboard it seems that the debug does not work????

 

[ExtremeXT]

Well, I've tried with the debug version that Shaneee put yesterday with the modifications for the audio and nothing else comes out..

Now I have tried with the debug version from here:

Builds

dortania.github.io

and I think it's the same...

On this motherboard it seems that the debug does not work????

This is a proper debug log, but you need to fully boot macOS before sending it, so it has time to log everything.

 

[PoMpIs]

This is a proper debug log, but you need to fully boot macOS before sending it, so it has time to log everything.

It crashes before reaching the OpenCore menu using the latest Dortania debug build... but that version doesn't have the patches to fix the audio.

With Shaneee's it works but it doesn't get the LOG..

I'm going to try again with Shaneee's version

 

[ExtremeXT]

It crashes before reaching the OpenCore menu using the latest Dortania debug build... but that version doesn't have the patches to fix the audio.

With Shaneee's it works but it doesn't get the LOG..

I'm going to try again with Shaneee's version

Use Casey's version, it's based on the DEBUG version of OpenCore, Shaneee's is based on RELEASE.

 

[fabiosun]

In this I have applied @CaseySJ code
tested on my system it does not produce any damage

 

[CaseySJ]

It crashes before reaching the OpenCore menu using the latest Dortania debug build... but that version doesn't have the patches to fix the audio.

With Shaneee's it works but it doesn't get the LOG..

I'm going to try again with Shaneee's version

Do you have Debug Target set to 0x67?

 

[PoMpIs]

@ExtremeXT

I have left it for 10 minutes, and in the end I have seen a message appear on the screen for a few seconds that says something like:

NVRAM is too large, log not generate...

Anyway this is what has come out once the system has booted

 

[fabiosun]

@PoMpIs now is good your debug

 

[PoMpIs]

Do you have Debug Target set to 0x67?

I have tried with 0x67... but the log shows the same as in the release version...

In the end I changed to:



And it has generated...

But it's weird because on the previous x670e-f board the LOG did come out with 0x67

I will try again with 0x67

 

[ExtremeXT]

@PoMpIs The last log was fine. Give this a try.

 

[PoMpIs]

@PoMpIs The last log was fine. Give this a try.

Tested..

It seems to start a little slower... but it works fine..

Now this appears in the LOG:



I get an ¿error? on DP68... when removing the patch you did for the x670e-f

 

[ExtremeXT]

Tested..

It seems to start a little slower... but it works fine..

Now this appears in the LOG:

View attachment 8547

I get an ¿error? on DP68... when removing the patch you did for the x670e-f

Are you sure it actually boots slower? It should boot faster... I'll look at the patch when I get back home, I wasn't sure if it's still needed on this mobo.