Ryzen 9000

E

Ejh4286

Member
AMD OS X Member
Oct 30, 2021
74
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

  • Like
Reactions: camow and centraljava
Sort by date Sort by votes
In theory it should work just fine. Did you modifiy the patches for core count?
 
Upvote 0 Downvote
If you're using a patched DSDT file that was made on a previous BIOS version, chances are it won't work. Disable that and try booting.
 
Upvote 0 Downvote
Ejh4286 said:
Yes. I included the patched DSDT, but I am
Unsure if it works with the latest BIOS (3024 I believe).
Click to expand...
Please see here for a link describing how ACPI patching can be performed and avoid using a DSDT

Asus X670E Gene EFI -- Adaptable to Other X670, X670E, B650 and B650E Boards

I installed Sequoia beta1(24A5264n), but I lost ethernet. Anyone else? I added Sequoia beta pacth and boot-arg -lilubetaall and AppleIntelI210Ethernet.kext to 23.9.9. to the Sonoma’s config. (Asus x670e gene with intel 2.5Gb ethernet) macOS 15 sequoia-beta-1 is now all ok except for wifi.
forum.amd-osx.com forum.amd-osx.com
 
  • Like
Reactions: etorix
Upvote 0 Downvote
leesurone said:
Please see here for a link describing how ACPI patching can be performed and avoid using a DSDT

Asus X670E Gene EFI -- Adaptable to Other X670, X670E, B650 and B650E Boards

I installed Sequoia beta1(24A5264n), but I lost ethernet. Anyone else? I added Sequoia beta pacth and boot-arg -lilubetaall and AppleIntelI210Ethernet.kext to 23.9.9. to the Sonoma’s config. (Asus x670e gene with intel 2.5Gb ethernet) macOS 15 sequoia-beta-1 is now all ok except for wifi.
forum.amd-osx.com forum.amd-osx.com
Click to expand...
ACPI is way beyond my knowledge. I’m an amateur compared to you guys. I tried disabling the patched DSDT and tried the DSDT from the link for my board. Same result. I posted screen shots for my BIOS if that helps. Thank you.
 

Attachments

Upvote 0 Downvote
Ejh4286 said:
ACPI is way beyond my knowledge. I’m an amateur compared to you guys. I tried disabling the patched DSDT and tried the DSDT from the link for my board. Same result. I posted screen shots for my BIOS if that helps. Thank you.
Click to expand...

Your only path as far as I know is to have a new DSDT created or have someone on the Discord create the ACPI patches you would need. Also beyond where I can help except to send you information where to ask for help which I already did.
 
Upvote 0 Downvote
I tried downgrading the BIOS to 2613 since that was the version the patched DSDT is based on. Still no joy. I tried replacing the Ryzen 97000 with a Ryzen 7700 and it booted right up into Sequoia 15 beta 6 with no issues. Tried several successful reboots. Put the 9700 back in and I get the same result as before as shown in the image of my first post. So I’m assuming now it’s some issue with the CPU. I remember the 7000 series had problems initially that were overcome by those more knowledgeable than me. So I’m gonna wait and see what the pros determine.
 
  • Like
Reactions: leesurone
Upvote 0 Downvote
Ejh4286 said:
I tried downgrading the BIOS to 2613 since that was the version the patched DSDT is based on. Still no joy. I tried replacing the Ryzen 97000 with a Ryzen 7700 and it booted right up into Sequoia 15 beta 6 with no issues. Tried several successful reboots. Put the 9700 back in and I get the same result as before as shown in the image of my first post. So I’m assuming now it’s some issue with the CPU. I remember the 7000 series had problems initially that were overcome by those more knowledgeable than me. So I’m gonna wait and see what the pros determine.
Click to expand...
You probably need the newer bios version to run 9000 processors is my guess. It’s very early days yet, if I do decide to upgrade I’ll wait until there are some success stories
 
Upvote 0 Downvote
Ejh4286 said:
This machine is setup for dual boot and windows runs fine on BIOS 2613 which was the first version that supported 9000 series.
Click to expand...
I've read speculation that the 9000 series processors would't be so different than the 7000 but that bios issues might be a road block. That made sense to me being they can run on existing motherboards and could still prove to be true. Hopefully once more people in the community buy 9000 processors and are willing to test this can be fixed.
 
Upvote 0 Downvote
Hi all,

I have a 3x boot (w11, sonoma, sequoia) installation with a 7950x + 6900xt and it works flawlesly.

Yesterday I updated to latest bios (x670 Hero) then swapped Cpu with a 9950x and then macOS doesn't boot anymore.

Swapped back to 7950x, and it boots again.

If anyone can help figuring it out, I can try Debuging, etc (but I would need guidance)

I'm on OC 1.01, latest kexts (tried disabling most of them already)

Please contact/pm me if you think you can help.

If we can Not solve it, I'll be returning the Cpu within 29 days (amazon)

Regards.
 
Upvote 0 Downvote
Can you boot with a debug build of OC and enable SysReport. This can be found under Misc -> Debug in the config,

SysReport
Type: plist boolean
Failsafe: false
Description: Produce system report on ESP folder.
This option will create a SysReport directory in the ESP partition unless already present. The directory will
contain ACPI, SMBIOS, and audio codec dumps. Audio codec dumps require an audio backend driver to be
loaded.
Note: To maintain system integrity, the SysReport option is not available in RELEASE builds. Use a DEBUG build
if this option is required.
Click to expand...

Then zip and upload the generated folder in the EFI.
 
  • Like
Reactions: etorix and fabiosun
Upvote 0 Downvote
Shaneee said:
Can you boot with a debug build of OC and enable SysReport. This can be found under Misc -> Debug in the config,



Then zip and upload the generated folder in the EFI.
Click to expand...
Attached the SysReport trying to boot Sonoma + Sequoia

Should I include -v in bootargs ?

Edit:
attached also, what I see with -v
 

Attachments

Last edited:
  • Like
Reactions: fabiosun
Upvote 0 Downvote
@ssuper2k I believe that the CPU family has moved from 19h. 7000 series must have used 19h too or I'm just completely wrong. Please try this test build of OpenCore and report back.
 

Attachments

  • Like
Reactions: leesurone
Upvote 0 Downvote
Upvote 0 Downvote
I was right in my assumption. Upon checking the linux source Zen 5 is indeed 1Ah now,


C++: 
  if (Cpu->Family == AMD_CPU_FAMILY) {
    Divisor         = 0;
    CoreFrequencyID = 0;
    CoreDivisorID   = 0;
    MaxBusRatio     = 0;

    switch (Cpu->ExtFamily) {
      case AMD_CPU_EXT_FAMILY_17H:
      case AMD_CPU_EXT_FAMILY_19H:
      case AMD_CPU_EXT_FAMILY_1AH: // For Ryzen 9000 series (Zen 5)
        if (Cpu->CPUFrequencyFromVMT == 0) {
          CofVid          = AsmReadMsr64 (K10_PSTATE_STATUS);
          CoreFrequencyID = (UINT8)BitFieldRead64 (CofVid, 0, 7);
          CoreDivisorID   = (UINT8)BitFieldRead64 (CofVid, 8, 13);
          if (CoreDivisorID > 0ULL) {
            //
            // Sometimes incorrect hypervisor configuration will lead to dividing by zero,
            // but these variables will not be used under hypervisor, so just skip these.
            //
            MaxBusRatio = (UINT8)(CoreFrequencyID / CoreDivisorID * 2);
          }
        }

        //
        // Get core count from CPUID
        //
        if (Cpu->MaxExtId >= 0x8000001E) {
          AsmCpuid (0x8000001E, NULL, &CpuidEbx, NULL, NULL);
          Cpu->CoreCount = (UINT16)DivU64x32 (
                                     Cpu->ThreadCount,
                                     (BitFieldRead32 (CpuidEbx, 8, 15) + 1)
                                     );
        }

        break;

The issue must be somewhere else. Problem is I'm not sure if it's in how OC handles it or if it's how the patches handle it...

What would help is if you can boot Linux and run this in Terminal,

Bash: 
sudo rdmsr 0xC0010064

This will tell us if the MSR we use is still valid.

In the mean time here's another build of OC to test,
 

Attachments

  • Like
  • Love
Reactions: craighazan, leesurone, fabiosun and 1 other person
Upvote 0 Downvote
Shaneee said:
What would help is if you can boot Linux and run this in Terminal,

Bash: 
sudo rdmsr 0xC0010064

This will tell us if the MSR we use is still valid.

In the mean time here's another build of OC to test,
Click to expand...
Same error with new OC build

Attaching linux command
 

Attachments

  • Ubuntu_MSR_9950x.jpg
    Ubuntu_MSR_9950x.jpg
    4.1 MB · Views: 36
Upvote 0 Downvote
1725718154072.png

Have you update to this BIOS?
it seems also good with @corpghost acpi patches (with a 7950x cpu)
have you an opencore debug log for 9950x tries?
thank you
 
Upvote 0 Downvote
You must log in or register to reply here.
Top Bottom
✖
  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.