Help needed with Ryzen 9 7950x and MSI x670 MAG ACE

ninjaskija

Member
AMD OS X Member
Joined
Nov 12, 2024
Messages
36
Hey guys,

This is my first time posting here. It's been a long time since I've used a Hackintosh (the last was Sierra), and I was thinking of giving it another try.
I have some issues posting (see the attached screenshot).
I've also attached the EFI folder that I have been using along with the OpenCore logs.

Configuration:
CPU: Ryzen 9 7950x
MB: MSI x670 MAG ACE
RAM: 96GB Crucial 5600 DDR5
NVME: Samsung 990 Pro 2TB

Bios settings:
Secure Boot: disabled
CSM: disabled
RBAR: enabled

Any input help will be greatly appreciated.

Thanks!
WhatsApp Image 2024-11-13 at 13.46.41_19341ed3.jpg
 

Attachments

  • EFI.zip
    5.2 MB · Views: 9
  • opencore-2024-11-12-140940.txt
    256 KB · Views: 5

ninjaskija

Member
AMD OS X Member
Joined
Nov 12, 2024
Messages
36
Hey! I've just tested it and it does not seem to work.
Here are the logs and SysReport folder.
The only notable thing I did was to disable SATA and Internal GPU. Anyways, even with them activated has the same effect.
I've attached the EFi folder as well for reference.
 

Attachments

  • SysReport.zip
    146.3 KB · Views: 0
  • EFI.zip
    6.2 MB · Views: 2

fabiosun

Guru
Guru
AMD OS X Member
Joined
Oct 9, 2022
Messages
635
@ninjaskija check mmio part in debug log if it is the same you had with other motherboard
 

fabiosun

Guru
Guru
AMD OS X Member
Joined
Oct 9, 2022
Messages
635
Mmio seems fine so problem is elsewhere
 

ninjaskija

Member
AMD OS X Member
Joined
Nov 12, 2024
Messages
36
If it helps, here are some screenshots.
 

Attachments

  • WhatsApp Image 2024-11-23 at 22.59.43_4d1a32cf.jpg
    WhatsApp Image 2024-11-23 at 22.59.43_4d1a32cf.jpg
    347.4 KB · Views: 8
  • WhatsApp Image 2024-11-23 at 22.59.43_021f53d2.jpg
    WhatsApp Image 2024-11-23 at 22.59.43_021f53d2.jpg
    175.9 KB · Views: 8

fabiosun

Guru
Guru
AMD OS X Member
Joined
Oct 9, 2022
Messages
635
Are you booting from an usb device?
Usb mapped?
 
Last edited:

Edhawk

Guru
Guru
Joined
May 2, 2020
Messages
2,798
The highlighted section of text in the screenshot below says, 'Still waiting for root device'.

Which indicates that your USB mapping isn't in place or is wrong. As the USB port you are using is being dropped when controller is passed from the BIOS/Bootloader to the Installer.

Try using the installer in a Physical USB2 port on the rear I/O plate (Black coloured Tang), if there are any on your motherboard. If you have the ASUS ProArt x870e Creator board same as @fabiosun then the USB2 port should be located to the left of the 2.5GB Ethernet port (lowest of the two Ethernet ports).
 

ninjaskija

Member
AMD OS X Member
Joined
Nov 12, 2024
Messages
36
No my USB ports were not mapped, and yes plugging the USB in the back did the trick and the installation started. Thanks! I'll keep you posted!
 

ninjaskija

Member
AMD OS X Member
Joined
Nov 12, 2024
Messages
36
I managed to finish the installation.
Of course, none of the LAN ports are working out of the box. So, what remains to be done is:
1. Make at least one of the LAN ports work
2. Make the GPU work
3. Map USBs
3. Maybe buy a wireless+bluetooth card but I don’t think I will miss it that much.

Any idea were I may find how I can make the 2.5g LAN work?

Thanks!
 

fabiosun

Guru
Guru
AMD OS X Member
Joined
Oct 9, 2022
Messages
635
it should be realtek 2,5 so i think lucykext could be working
 

Edhawk

Guru
Guru
Joined
May 2, 2020
Messages
2,798
LucyRTL8125Ethernet.kext can be downloaded from the link below.


Regarding your USB ports, as you don’t have a mapping kext make sure the Kernel > Quirks > XhciPortLimit entry is Enabled in your config.plist.
 

fabiosun

Guru
Guru
AMD OS X Member
Joined
Oct 9, 2022
Messages
635
Use the kext in my folder
It is an updated version done by lorys89 if i am not wrong
It works in my proart
 

Edhawk

Guru
Guru
Joined
May 2, 2020
Messages
2,798
You need to use RestrictEvents.kext and the correct boot argument or NVRAM entries in your config.plist for the correct CPU name to show.


Have a look at the Readme for RestrictEvents in the link above.
 

ninjaskija

Member
AMD OS X Member
Joined
Nov 12, 2024
Messages
36
You need to use RestrictEvents.kext and the correct boot argument or NVRAM entries in your config.plist for the correct CPU name to show.


Have a look at the Readme for RestrictEvents in the link above.
Thanks! worked like a charm
 

leesurone

Donator
Donator
AMD OS X Member
Joined
May 6, 2020
Messages
526
He did for you and i configured them in your config.plist
Let see if you go further :)
I saw this post a while back and wanted to try those ACPI patches with a second hand MSI X670E board I have. I didn't have an extra processor so I waited and then the other day purchased a Ryzen 5 8600G ( which is probably not the best choice for a ryzentosh but its relatively inexpensive for an AM5 CPU). Long story short version, latest bios and a simplified EFI worked. Loading Sequoia now.
 

ninjaskija

Member
AMD OS X Member
Joined
Nov 12, 2024
Messages
36
Hey guys, I had some errors lately (restart during boot) with the following error:

Code:
Panic(CPU 20, time 6173406814): NMIPI for spinlock acquisition timeout, spinlock: 0xffffffa08b3d9450, spinlock owner: 0xffffff9a271a5b40, current_thread: 0xffffff9a271a5b40, spinlock_owner_cpu: 0x14
RAX: 0x000000015e3b0d5c, RBX: 0xfffffffa3b537788, RCX: 0x0000000038e3959e, RDX: 0x0000000000000001
RSP: 0xfffffffa3b537760, RBP: 0xfffffffa3b537770, RSI: 0x0000000000000002, RDI: 0xffffff801d16b590
R8:  0x0000000000000082, R9:  0x0000000000000000, R10: 0x0000000000f14358, R11: 0x0000000000000007
R12: 0x0000000000000000, R13: 0x0000000000000000, R14: 0x00000005d21dba00, R15: 0xffffff8bc62430b0
RFL: 0x0000000000000246, RIP: 0xffffff801c3e53df, CS:  0x0000000000000008, SS:  0x0000000000000010
Panicked task 0xffffff909157c110: 244 threads: pid 0: kernel_task
Backtrace (CPU 20), panicked thread: 0xffffff9a271a5b40, Frame : Return Address
0xffffffd77c07df80 : 0xffffff801c547845
0xffffffd77c07dfe0 : 0xffffff801c381a9a
0xfffffffa3b537770 : 0xffffff801e5a599f
0xfffffffa3b5377a0 : 0xffffff801e59d947
0xfffffffa3b5377f0 : 0xffffff801e5aa0c3
0xfffffffa3b5378c0 : 0xffffff801e95cfea
0xfffffffa3b537920 : 0xffffff801e95fa36
0xfffffffa3b5379d0 : 0xffffff801efbc092
0xfffffffa3b537a30 : 0xffffff801e966444
0xfffffffa3b537ae0 : 0xffffff801c61d4f2
0xfffffffa3b537b40 : 0xffffff801c5b6e64
0xfffffffa3b537bc0 : 0xffffff801c5b5a4e
0xfffffffa3b537bf0 : 0xffffff801ef737a6
0xfffffffa3b537c40 : 0xffffff801ef7335d
0xfffffffa3b537c90 : 0xffffff801ef73ab1
0xfffffffa3b537d50 : 0xffffff801ef72c29
0xfffffffa3b537d70 : 0xffffff801f09e1de
0xfffffffa3b537dd0 : 0xffffff801f09ded8
0xfffffffa3b537e50 : 0xffffff801f0bf9fe
0xfffffffa3b537f20 : 0xffffff801f0bf21f
0xfffffffa3b537fa0 : 0xffffff801c38119e
      Kernel Extensions in backtrace:
         com.apple.iokit.IOStorageFamily(2.1)[4B0CF2F6-B2D4-37B7-BD27-A96CBA970155]@0xffffff801e957000->0xffffff801e96dfff
         com.apple.filesystems.apfs(2313.41.1)[7911AA10-1792-30C0-8595-72FA9CD01694]@0xffffff801ef60000->0xffffff801f120fff
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[3F1A6025-6D21-30D4-81D2-9271CF2B2E6B]@0xffffff801d892000->0xffffff801d89cfff
            dependency: com.apple.driver.AppleEffaceableStorage(1.0)[6BF4BAA2-B98E-3399-81EF-70D7656B6FAE]@0xffffff801d8a9000->0xffffff801d8aefff
            dependency: com.apple.iokit.CoreAnalyticsFamily(1)[6F70014E-2C14-329A-8717-CBE3FE6019FF]@0xffffff801deaf000->0xffffff801deb8fff
            dependency: com.apple.iokit.IOStorageFamily(2.1)[4B0CF2F6-B2D4-37B7-BD27-A96CBA970155]@0xffffff801e957000->0xffffff801e96dfff
            dependency: com.apple.kec.corecrypto(14.0)[448CF70B-11BD-39F2-B6D4-119DE29D7940]@0xffffff801f166000->0xffffff801f1e7fff
            dependency: com.apple.security.AppleImage4(7.0.0)[4DC04697-80EC-30EF-A52B-5811575D725A]@0xffffff801d91e000->0xffffff801d942fff
         com.apple.iokit.IONVMeFamily(2.1)[6E144D00-F81A-3E15-BEBC-E0CA76D6BFDC]@0xffffff801e590000->0xffffff801e5b8fff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[9EC9CB9D-5FAA-3E54-A9E8-C76887F6C9D4]@0xffffff801da92000->0xffffff801dacbfff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[356D7C71-CB4B-37B3-9AB2-7160A434CC2A]@0xffffff801e823000->0xffffff801e856fff
            dependency: com.apple.iokit.IOReportFamily(47)[DCBEB7F4-9899-3FDE-8285-620F8C87B32A]@0xffffff801e867000->0xffffff801e869fff
            dependency: com.apple.iokit.IOStorageFamily(2.1)[4B0CF2F6-B2D4-37B7-BD27-A96CBA970155]@0xffffff801e957000->0xffffff801e96dfff

Process name corresponding to current thread (0xffffff9a271a5b40): kernel_task
Boot args: -v revpatch=cpuname,sbvmm

Mac OS version:
24B91

Kernel version:
Darwin Kernel Version 24.1.0: Thu Oct 10 21:02:27 PDT 2024; root:xnu-11215.41.3~2/RELEASE_X86_64
Kernel UUID: 15F8E5B4-41DF-31C2-8CF5-F486066C59B9
roots installed: 0
KernelCache slide: 0x000000001c000000
KernelCache base:  0xffffff801c200000
Kernel slide:      0x000000001c0e4000
Kernel text base:  0xffffff801c2e4000
__HIB  text base: 0xffffff801c100000
System model name: MacPro7,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Panic diags file available: NO (0xe00002bc)
Hibernation exit count: 0

System uptime in nanoseconds: 6295922027
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x00000001778a7a9c
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x00000049400527fe 0x0000000000000000
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
  Zone map: 0xffffff808b5d4000 - 0xffffffa08b5d4000
  . PGZ   : 0xffffff808b5d4000 - 0xffffff80975d5000
  . VM    : 0xffffff80975d5000 - 0xffffff85625d4000
  . RO    : 0xffffff85625d4000 - 0xffffff86fb5d4000
  . GEN0  : 0xffffff86fb5d4000 - 0xffffff8bc65d4000
  . GEN1  : 0xffffff8bc65d4000 - 0xffffff90915d4000
  . GEN2  : 0xffffff90915d4000 - 0xffffff955c5d4000
  . GEN3  : 0xffffff955c5d4000 - 0xffffff9a275d4000
  . DATA  : 0xffffff9a275d4000 - 0xffffffa08b5d4000
  Metadata: 0xffffffa08b5e4000 - 0xffffffa0ab5e4000
  Bitmaps : 0xffffffa0ab5e4000 - 0xffffffa0bb5e4000
  Extra   : 0 - 0

panic(cpu 22 caller 0xffffff801c53e15e): Spinlock[0xffffffa08b3d9450] timeout after 523892295 ticks ;lock owner thread=0xffffff9a271a5b40, current_thread: 0xffffff9a265500e0, lock owner active on CPU 20, start time: 341167229910, now: 341691122205, timeout: 523867909 @locks_i386.c:487
Panicked task 0xffffff90908e2110: 39 threads: pid 266: lghub_updater
Backtrace (CPU 22), panicked thread: 0xffffff9a265500e0, Frame : Return Address
0xfffffffa3b58e970 : 0xffffff801c3ebc91
0xfffffffa3b58e9c0 : 0xffffff801c558a0c
0xfffffffa3b58ea00 : 0xffffff801c5482b3
0xfffffffa3b58ead0 : 0xffffff801c381971
0xfffffffa3b58eaf0 : 0xffffff801c3ebf87
0xfffffffa3b58ebf0 : 0xffffff801c3eb622
0xfffffffa3b58ec60 : 0xffffff801cbd4078
0xfffffffa3b58ed50 : 0xffffff801c53e15e
0xfffffffa3b58edb0 : 0xffffff801c405184
0xfffffffa3b58ee30 : 0xffffff801c53e1b5
0xfffffffa3b58ee50 : 0xffffff801e59d6c1
0xfffffffa3b58ee80 : 0xffffff801e59d8f5
0xfffffffa3b58eed0 : 0xffffff801e5aa0c3
0xfffffffa3b58efa0 : 0xffffff801e95cfea
0xfffffffa3b58f000 : 0xffffff801e95fa36
0xfffffffa3b58f0b0 : 0xffffff801e966444
0xfffffffa3b58f160 : 0xffffff801c61d4f2
0xfffffffa3b58f1c0 : 0xffffff801c610c44
0xfffffffa3b58f1f0 : 0xffffff801ef745dd
0xfffffffa3b58f240 : 0xffffff801ef74690
0xfffffffa3b58f2b0 : 0xffffff801ef74297
0xfffffffa3b58f370 : 0xffffff801ef72bc4
0xfffffffa3b58f390 : 0xffffff801f0a2a06
0xfffffffa3b58f3d0 : 0xffffff801f0a1cd9
0xfffffffa3b58f4a0 : 0xffffff801f077997
0xfffffffa3b58f560 : 0xffffff801f0820ad
0xfffffffa3b58f630 : 0xffffff801f0829c7
0xfffffffa3b58f6a0 : 0xffffff801f030f3a
0xfffffffa3b58f8f0 : 0xffffff801f030069
0xfffffffa3b58f990 : 0xffffff801f02ff97
0xfffffffa3b58f9d0 : 0xffffff801efd783e
0xfffffffa3b58faa0 : 0xffffff801f030cc0
0xfffffffa3b58fce0 : 0xffffff801efd34ae
0xfffffffa3b58fdf0 : 0xffffff801c5aff84
0xfffffffa3b58ff40 : 0xffffff801ca3a862
0xfffffffa3b58ffa0 : 0xffffff801c381db6
      Kernel Extensions in backtrace:
         com.apple.iokit.IOStorageFamily(2.1)[4B0CF2F6-B2D4-37B7-BD27-A96CBA970155]@0xffffff801e957000->0xffffff801e96dfff
         com.apple.filesystems.apfs(2313.41.1)[7911AA10-1792-30C0-8595-72FA9CD01694]@0xffffff801ef60000->0xffffff801f120fff
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[3F1A6025-6D21-30D4-81D2-9271CF2B2E6B]@0xffffff801d892000->0xffffff801d89cfff
            dependency: com.apple.driver.AppleEffaceableStorage(1.0)[6BF4BAA2-B98E-3399-81EF-70D7656B6FAE]@0xffffff801d8a9000->0xffffff801d8aefff
            dependency: com.apple.iokit.CoreAnalyticsFamily(1)[6F70014E-2C14-329A-8717-CBE3FE6019FF]@0xffffff801deaf000->0xffffff801deb8fff
            dependency: com.apple.iokit.IOStorageFamily(2.1)[4B0CF2F6-B2D4-37B7-BD27-A96CBA970155]@0xffffff801e957000->0xffffff801e96dfff
            dependency: com.apple.kec.corecrypto(14.0)[448CF70B-11BD-39F2-B6D4-119DE29D7940]@0xffffff801f166000->0xffffff801f1e7fff
            dependency: com.apple.security.AppleImage4(7.0.0)[4DC04697-80EC-30EF-A52B-5811575D725A]@0xffffff801d91e000->0xffffff801d942fff
         com.apple.iokit.IONVMeFamily(2.1)[6E144D00-F81A-3E15-BEBC-E0CA76D6BFDC]@0xffffff801e590000->0xffffff801e5b8fff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[9EC9CB9D-5FAA-3E54-A9E8-C76887F6C9D4]@0xffffff801da92000->0xffffff801dacbfff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[356D7C71-CB4B-37B3-9AB2-7160A434CC2A]@0xffffff801e823000->0xffffff801e856fff
            dependency: com.apple.iokit.IOReportFamily(47)[DCBEB7F4-9899-3FDE-8285-620F8C87B32A]@0xffffff801e867000->0xffffff801e869fff
            dependency: com.apple.iokit.IOStorageFamil
If it boots successfully then it is stable, with no errors.
Any Idea where should I look?
 

Edhawk

Guru
Guru
Joined
May 2, 2020
Messages
2,798
I would look at the NVMe M.2 drive, which one are you using as your macOS boot drive?
 
Back
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.