I need to help with and install issue with Ryzen 9 9900x

[Katanoko1221]

Hi everyone!!!
This is my first Ryzentosh build and i've the each problem; When i select "installMacOS" in OC boot menù, the install rest stuck after few second.
I attach EFI, System report and the boot-log containing the error.
I hope there is someone who can fix the efi so I can install macOS!!!

Thanks in advance

Pc configuration:
Cpu: Ryzen 9 9900x
Gpu: Amd Rx6600
Mbo: MSI x870 Gaming Plus
Ram: Crucial 64 Gb
NvMe: (M2) Crucial P3 plus.

 

[Shaneee]

No I have a 5600X and it works fine. What I mean is I can't build OC just now for some reason. So I can't apply a test fix for you to try just now.

 

[Katanoko1221]

No I have a 5600X and it works fine. What I mean is I can't build OC just now for some reason. So I can't apply a test fix for you to try just now.

Ok, i've understand, so proximally you goes to create a "text fix" on my config?

 

[Shaneee]

Ok, i've understand, so proximally you goes to create a "text fix" on my config?

Please test this out. It's a debug build so ensure you've got the target set to 67 and upload the log file.

 

[Katanoko1221]

Please test this out. It's a debug build so ensure you've got the target set to 67 and upload the log file.

Hi, this is the full debug log, thank you for the effort

 

[Shaneee]

Ok, so it wasn't the reason I thought. Try this instead please,

 

[Katanoko1221]

Ok, so it wasn't the reason I thought. Try this instead please,

Here, it seems to me that from the boot-log the error is always the same.

 

[Shaneee]

Here, it seems to me that from the boot-log the error is always the same.

This seems to be an older build than what I uploaded. Make sure your replacing the OpenCore.efi file

OpenCore DBG-104-2025-03-04

The uploaded version should force the correct ExtFamily signature and run the correct code.

 

[Katanoko1221]

This seems to be an older build than what I uploaded. Make sure your replacing the OpenCore.efi file



The uploaded version should force the correct ExtFamily signature and run the correct code.

I am attaching the new "boot-log" after having verified the "OpenCore.efi" file correctly. I also attach the EFI to verifying if I have updated correctly to "OC_DEBUG". Thank for your efforts

 

[Shaneee]

Ok now I see what I was expecting,

00:268 00:112 OCCPU: Forcing ExtFamily to 0x1A for Ryzen 9 9900X

Does it still not boot?

 

[Katanoko1221]

Ok now I see what I was expecting,



Does it still not boot?

Nothing, don't it still boot again with the "OpenCore.efi" updated. For scruple, try to check and review my "EFI" to avoid some edit issue by me.
Thank for you patience

 

[Shaneee]

Nothing, don't it still boot again with the "OpenCore.efi" updated. For scruple, try to check and review my "EFI" to avoid some edit issue by me.
Thank for you patience

I see the issue now although it's now being read correctly as Family 1Ah.

43:262 00:015 ASSERT [OpenCore] DivU64x64Remainder.c(38): Divisor != 0

This is likely caused because now your FSB is not being read so it's trying to divide it by zero.

00:356 00:012 OCCPU: FSBFrequency 0Hz 0MHz

Try this. I've added extra debug lines and a failsafe for the division by zero.

 

[Katanoko1221]

I see the issue now although it's now being read correctly as Family 1Ah.



This is likely caused because now your FSB is not being read so it's trying to divide it by zero.



Try this. I've added extra debug lines and a failsafe for the division by zero.

I've post the new boot-log. Nothing, looks like that issue persist :-(

Thank you again

 

[Shaneee]

It's not the correct build,

DBG-105-2025-04-22

The one uploaded should have todays date on it. You only need to replace OpenCore.efi and reset the NVRAM.

 

[Katanoko1221]

It's not the correct build,



The one uploaded should have todays date on it. You only need to replace OpenCore.efi and reset the NVRAM.

I've just checked the "OpenCore.efi" file and retryed doing "ResetNVram", but i don't know because the build date rest stuck to "DBG-105-2025-04-22" and the issue at the last string it's always the same .
Also, I tried again with the previous build and the final issue is different, i'm go to post boths "Boot-log" so you can see the different issue about the final string.

Thank you again

 

[Shaneee]

I've just checked the "OpenCore.efi" file and retryed doing "ResetNVram", but i don't know because the build date rest stuck to "DBG-105-2025-04-22" and the issue at the last string it's always the same .
Also, I tried again with the previous build and the final issue is different, i'm go to post boths "Boot-log" so you can see the different issue about the final string.

Thank you again

Hmm if that's correct it's still not running the 1Ah code... Let me add debug strings to all the AMD cases to determine what's being run...

Edit:
Here we go, each AMD Family case now has a debug string so we know exactly where the 9900x is being routed and will help diagnose why.

 

[Katanoko1221]

Hmm if that's correct it's still not running the 1Ah code... Let me add debug strings to all the AMD cases to determine what's being run...

Edit:
Here we go, each AMD Family case now has a debug string so we know exactly where the 9900x is being routed and will help diagnose why.

This is the new boot-log, I hope that was be detected something of new, but i don't know why the date of build don't keep updated despite I've replaced properly the "OpenCore.efi" file.

 

[Shaneee]

That helps... Let me remove something and I'll upload another test for you tomorrow. It's late here and I'm working early.

So it should be running the case for Family 0x1Ah but it wasn't so I was trying to force it by forcing 0x1A which if I'm correct in hex is the same. However it's not working as I thought which is why your log now shows,

Unknown AMD CPU family 0x1A, exiting!

I'll remove this force and upload again so we can see exactly which case is being run for the 9900x. If none are and again it shows Unknown AMD CPU Family "*" then I can define the family shown to support and run the case for family 0x1Ah.

 

[Katanoko1221]

That helps... Let me remove something and I'll upload another test for you tomorrow. It's late here and I'm working early.

So it should be running the case for Family 0x1Ah but it wasn't so I was trying to force it by forcing 0x1A which if I'm correct in hex is the same. However it's not working as I thought which is why your log now shows,

Unknown AMD CPU family 0x1A, exiting!

I'll remove this force and upload again so we can see exactly which case is being run for the 9900x. If none are and again it shows Unknown AMD CPU Family "*" then I can define the family shown to support and run the case for family 0x1Ah.

Ok, I will wait the next test!!!
So, the issue is the system that don't recognize the coding about cpu family?

 

[Shaneee]

Ok, I will wait the next test!!!
So, the issue is the system that don't recognize the coding about cpu family?

That's how it seems yes. This version doesn't try and force the family but will log which case is being entered. If it's using the correct case for 1Ah then it'll log some extra info to try shed some light on why it's not. If it's showing a family that's not declared then it should be a relatively easy fix.

 

[Katanoko1221]

That's how it seems yes. This version doesn't try and force the family but will log which case is being entered. If it's using the correct case for 1Ah then it'll log some extra info to try shed some light on why it's not. If it's showing a family that's not declared then it should be a relatively easy fix.

Same result, but this time the core and thread number seems correct.
But there are something again to define to get it work!!!