Ryzen 9000

Ejh4286

Member
AMD OS X Member
Oct 30, 2021
77
1
15
8
CPU:
Ryzen5950
I installed a Ryzen 9700 into a Asus Strix B650E-
F (latest BIOS) that was successfully booting Sequoia Beta 4. Using latest kexts, patches, etc. I was not really expecting it to boot on the first try and I was right. See screen shot attached. Has anyone else tried to Hackintosh a Ryzen 9000 series yet?
 

Attachments

@Ejh4286 @Alex4querty Please test this build. It should now work. I had misdefined the CPU Family by mistake...
 

Attachments

  • Like
Reactions: fabiosun
@Ejh4286 @Alex4querty Please test this build. It should now work. I had misdefined the CPU Family by mistake...
Well, it got further but went into a boot loop. I erased the drive tried to install from scratch still getting boot loop.

UPDATE: I updated the EFI on my Ryzen 9700 with this and it booted fine.
 

Attachments

Last edited:
  • Like
Reactions: fabiosun
i see only two main differences from my 9950x log
1)mp service is failing to read exact core count in 9900x
2) @Ejh4286 it seems you are using a patched DSDT and no new method found by CorpGhost to patch only things usuful to patch via ACPI patches

however thanks @Shaneee for his wonderful job also with a lack of interested testers :)
 
The AMD part is calculating the cores correctly but it’s not reading them from firmware correctly. This is out of our control.

So the 9700 boots? Where does the 9900X get stuck?
 
This is all correct,

Code:
01:006 00:841 OCCPU: Signature B40F40 Stepping 0 Model 44 Family F Type 0 ExtModel 4 ExtFamily B uCode 0 CPUID MAX (10/80000028)
01:959 00:952 OCCPU: Entering AMD CPU detection routine...
02:811 00:852 OCCPU: Detected AMD Family 1Ah
03:663 00:852 OCCPU: MaxExtId = 0x80000028
03:832 00:169 OCCPU: Attempting to read CPUID(0x8000001E)
03:859 00:027 OCCPU: CPUID(0x8000001E) EBX=00000100
03:887 00:027 OCCPU: Before Calculation: TotalThreadCount=24, ThreadsPerCore=2, CoreId=0
03:914 00:027 OCCPU: After Calculation: CoreCount=12
03:941 00:027 OCCPU: FID 48 DID 0 Divisor 0 MaxBR 48
03:968 00:027 OCCPU: CPUFrequencyFromTSC  4391747927Hz  4391MHz
03:995 00:027 OCCPU: CPUFrequency  4391747927Hz  4391MHz
04:023 00:027 OCCPU: FSBFrequency    91494748Hz    91MHz
04:856 00:833 OCCPU: Pkg 1 Cores 12 Threads 24

Here's a complete updated version. Please test on all 9000 chips.

@Ejh4286 You said it went into a boot loop... Where exactly?
 

Attachments

  • Like
Reactions: etorix
This is all correct,

Code:
01:006 00:841 OCCPU: Signature B40F40 Stepping 0 Model 44 Family F Type 0 ExtModel 4 ExtFamily B uCode 0 CPUID MAX (10/80000028)
01:959 00:952 OCCPU: Entering AMD CPU detection routine...
02:811 00:852 OCCPU: Detected AMD Family 1Ah
03:663 00:852 OCCPU: MaxExtId = 0x80000028
03:832 00:169 OCCPU: Attempting to read CPUID(0x8000001E)
03:859 00:027 OCCPU: CPUID(0x8000001E) EBX=00000100
03:887 00:027 OCCPU: Before Calculation: TotalThreadCount=24, ThreadsPerCore=2, CoreId=0
03:914 00:027 OCCPU: After Calculation: CoreCount=12
03:941 00:027 OCCPU: FID 48 DID 0 Divisor 0 MaxBR 48
03:968 00:027 OCCPU: CPUFrequencyFromTSC  4391747927Hz  4391MHz
03:995 00:027 OCCPU: CPUFrequency  4391747927Hz  4391MHz
04:023 00:027 OCCPU: FSBFrequency    91494748Hz    91MHz
04:856 00:833 OCCPU: Pkg 1 Cores 12 Threads 24

Here's a complete updated version. Please test on all 9000 chips.

@Ejh4286 You said it went into a boot loop... Where exactly?
I’ll give this one a try. The output from verbose mode flys by fast. I don’t know how to isolate the last line of output before the screen goes blank and it reboots.

I’m using two different machines for the 9700x and 9900x. Same motherboard model, bios version and settings, and same video card. Only the cpu is different.

I’ve attached a photo of where it pauses for about a minute before a bunch of output flys by at light speed, then goes dark and reboots.
 

Attachments

Last edited:
Easiest way is to record a video to see what it's doing. On the plus side it's no longer an OC issue :D
 
Yes. Once OpenCore has handed over to the kernel it becomes either a config issue with something not being applied to the kernel or a kext issue. Could also be a BIOS issue.
 
  • Like
Reactions: Edhawk
I gave this a try on my Asus ROG B650E-F, BIOS 2613. Same result. I have attached my EFI and debug output.
Hey, As you also have a B650 Board. Does your USBWakeFixup.kext work? So do you need one or two keypresses to wake the system up with display turning on?

I always need two keypresses so the display turns on.

And do you also have instant wakes after sleep on Windows/Mac?
 
Hey, As you also have a B650 Board. Does your USBWakeFixup.kext work? So do you need one or two keypresses to wake the system up with display turning on?

I always need two keypresses so the display turns on.

And do you also have instant wakes after sleep on Windows/Mac?
I don’t let mine go to sleep, so I don’t know.
 
I don’t let mine go to sleep, so I don’t know.
Can you try for me please? Just send him to sleep. And wake him up after couple of seconds sleeps. First with 1 keystroke. See if display comes up alone. And after 20-30sec hit the second key to see if display turns on then.
 
I've got two Asus B650E-F board, BIOS 2613, same BIOS settings, same graphics card. One has a Ryzen 9700 and boots Sequoia just fine. The other has a Ryzen 9900X that has been very problematic. @Shanee was very helpful in making modifications to Open Core to solve a problem with core counts. I still can't get this thing to boot Sequoia. I've attached my EFI along with the debug output hoping someone more knowledgeable than me can figure out why it won't boot and make some suggestions because I have hit a brick wall with this one. TIA.
 

Attachments

Can you try for me please? Just send him to sleep. And wake him up after couple of seconds sleeps. First with 1 keystroke. See if display comes up alone. And after 20-30sec hit the second key to see if display turns on then.
I tried this. When I purposely put it to sleep, the monitor went dark, but all the fans and lights stayed on, so I don't think it fully went to sleep. When I hit the space bar, the monitor came back on.
 
  • Like
Reactions: SchmockLord
I've got two Asus B650E-F board, BIOS 2613, same BIOS settings, same graphics card. One has a Ryzen 9700 and boots Sequoia just fine. The other has a Ryzen 9900X that has been very problematic. @Shanee was very helpful in making modifications to Open Core to solve a problem with core counts. I still can't get this thing to boot Sequoia. I've attached my EFI along with the debug output hoping someone more knowledgeable than me can figure out why it won't boot and make some suggestions because I have hit a brick wall with this one. TIA.
Hi, debug is not a full debug so it is not useful
Have you patched by yourself DSDT for your ASUS?
have you also tried to use only ACPI patches done by CorpGhost ?
 
@Ejh4286 if you can and like to try these two config.plist
This is my EFI adapted to your 9900x, it uses ACPI patches done for my HERO mtherboard from CorpGhost, in your E-F motherboard it should be useful only the first one (this patches are useful to avoid patching all DSDT or to avoid to use an older one)

this below is a config.plist based to your previous dsdt and ACPi ssdt patch
only to overwrite to my previous EFI

If you use it post a video of booting process and debug log both tests produce
Thank you
 

Attachments

Last edited:
  • Like
Reactions: Shaneee
I've got two Asus B650E-F board, BIOS 2613, same BIOS settings, same graphics card. One has a Ryzen 9700 and boots Sequoia just fine. The other has a Ryzen 9900X that has been very problematic. @Shanee was very helpful in making modifications to Open Core to solve a problem with core counts. I still can't get this thing to boot Sequoia. I've attached my EFI along with the debug output hoping someone more knowledgeable than me can figure out why it won't boot and make some suggestions because I have hit a brick wall with this one. TIA.
I‘ve used your EFI.
 

Attachments

I tried this. When I purposely put it to sleep, the monitor went dark, but all the fans and lights stayed on, so I don't think it fully went to sleep. When I hit the space bar, the monitor came back on.
Thanks. Yeah this is the same behaviour as I have in Sequioia, it doesn't go into sleep. Switching back to Sonoma with the same EFI fixed the problem. Only remaining issue I have left is, that it need two keystrokes to wake the display after sleep. But that is a minor cosmetic.
 
15.1 rc on 9950x🥹👍
 

Attachments

  • image.png.303501ec237cfe3d01edf5f8554f4d60.png
    image.png.303501ec237cfe3d01edf5f8554f4d60.png
    336.6 KB · Views: 40
  • Like
Reactions: sunfish and Shaneee
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.