AMD Rayon R7 5800H Install Monterey kernel Panic

zxc2689963

Active member
AMD OS X Member
Joined
Feb 27, 2022
Messages
135
Hello everyone, the Monterey kernel panic problem has been solved for AMD R7 5800H notebook installation. It is a great thing that the CPU can now run on 8 cores. Thank you guys very much.Thank them for discovering the problem and providing kernel patches @ExtremeX@Visual

Brand: Lenovo
Model: Legion 5 6th Gen
CPU: AMD Ryzen 7 5800h
GPU: AMD Radeon RX 6600m 8GB ( Separate GPU mode)
HDD: Samsung SSD 970 EVO Plus 1TB (1000 GB, PCI-E 3.0 x4)
WDS500G3X0C-00SJG0 (500 GB, PCI-E 3.0 x4)
Network: RealTek Semiconductor RTL8168/8111 PCI-E Gigabit Ethernet NIC
Intel(R) Wi-Fi 6E AX210 160MHz
Ram: x2 8GB 3200mhz ddr4
Display: 15.6 1080p 165HZ

Updated October 5, 2023
Problems solved:
1. You do not need to disable XHCI
2. The microphone problem is rectified
3. Monitor brightness can be adjusted, only in Ventura

Unresolved issues:
Failure to wake from sleep

 

Attachments

  • EFI-2023-10-5.zip
    40 MB · Views: 226
Last edited:
Solution
Panic from Monterey 12.6
View attachment 7258
Thanks. I looked at the sched_prim.c file in the XNU Kernel source code (nice of Apple to let us know exactly where to search) and found that it's related to the TSC (Time Stamp Counter) Syncronization of the CPU cores. The section of the code which gives the panic is: https://github.com/apple-oss-distributions/xnu/blob/xnu-8020.140.41/osfmk/kern/sched_prim.c#L2836
Unfortunately Apple didn't update the XNU Source Code for macOS 12.6 yet, but I still managed to find the place where it calls the panic.
Image 1 is the code of XNU that panics if the time between cores does not match (not syncronized properly).

As seen when comparing the Big Sur and Monterey code (Image 2), Big Sur...

redhorse1990

Member
AMD OS X Member
Joined
Jul 2, 2022
Messages
181
That is a possibility, but it is no more likely to work that disabling each port (individually/one at a time) in a custom UTBMap.kext or USBMap.kext. Rebooting the system to see/check which port has been disabled when the system boots to OpenCore and through to the macOS installer.

Patience would be required as this trial and error check is undertaken. Notes taken to record which port or feature was disabled as each port in the kext was checked.

But to be honest, each port should be identifiable and set with a custom 'Nickname' (shows as 'hashTag comment' in the kext's info.plist ) from when each of the ports were discovered and confirmed in Windows, using USBToolBox Tool. The output would look something like this is Hackintool > USB tab with the populated Comments field.

View attachment 15136 Example of USB ports with comments/Nicknames for each port so they can easily be identified.
Example from an AMD Mini PC system containing Ryzen 5 7530U & APU (laptop CPU).
Unselect the ports in https://github.com/USBToolBox/tool and generates UTBMap.kexk to disable it? Do I understand it right?
 
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.