AMD Rayon R7 5800H Install Monterey kernel Panic

zxc2689963

Active member
AMD OS X Member
Feb 27, 2022
135
92
28
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

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...
For those considering the Legion 7 Slim, whith the 6800h and the 6600s or 6800s, it should be OK to hackintosh at least in that it does have a Mux. Good to see more laptops with Mux and compatible GPU's. The question remains is the hard drive mounting issue will be inherited on the Legion 7.

Screen Shot 2022-11-29 at 10.08.10 PM.png

Here clearly mentioned the Mux addition to the Legion 7
 
For those considering the Legion 7 Slim, whith the 6800h and the 6600s or 6800s, it should be OK to hackintosh at least in that it does have a Mux. Good to see more laptops with Mux and compatible GPU's. The question remains is the hard drive mounting issue will be inherited on the Legion 7.

View attachment 8823

Here clearly mentioned the Mux addition to the Legion 7
Will this laptop still have USB problems? Has anyone ever tried
 
  • Like
Reactions: Jo-Toku
Regarding enabling AMD I2C trackpads, has anyone tried this fork of VoodooI2C from the same devs of Whateverred? It's got something to do with adding AMD support in some of its latest commits apparently. Unfortunately will need some compiling work to make it into a kext so I haven't tried it yet.

 
Regarding enabling AMD I2C trackpads, has anyone tried this fork of VoodooI2C from the same devs of Whateverred? It's got something to do with adding AMD support in some of its latest commits apparently. Unfortunately will need some compiling work to make it into a kext so I haven't tried it yet.

Unfortunately, I haven't been able to find a solution yet because of the USB problem, which may be Insyde BIOS. I dare not easily try to modify the BIOS. I compiled VoodooI2C, it may be invalid due to USB problem
 

Attachments

  • Like
Reactions: alexjaixd
UTBMap.kext should be the finished article, and contain the mapped USB ports from the system it is used in. What is most important is that the UTBMap.kext is set, with the correct USB Port connector Types for each active port.

Whereas the UTBDefault.kext will not, it will contain a generic incorrectly set bunch of USB ports, which may work as part of the USB port discovery but it will be far from the finished article.

Also you are always taking a risk using someone else's UTBMap.kext, as you don't know if they have discovered all the available ports, or if they have set them with the correct connector Type. Always take someone else's USB configuration with a large pinch of salt, as it is likely to contain errors. Even the ones that swear blind they have set the kext correctly.
 
UTBMap.kext should be the finished article, and contain the mapped USB ports from the system it is used in. What is most important is that the UTBMap.kext is set, with the correct USB Port connector Types for each active port.

Whereas the UTBDefault.kext will not, it will contain a generic incorrectly set bunch of USB ports, which may work as part of the USB port discovery but it will be far from the finished article.

Also you are always taking a risk using someone else's UTBMap.kext, as you don't know if they have discovered all the available ports, or if they have set them with the correct connector Type. Always take someone else's USB configuration with a large pinch of salt, as it is likely to contain errors. Even the ones that swear blind they have set the kext correctly.
How should I set UTBMap.kext by myself?
 
I'll be honest, it is not something I use often as most of my Hack's are Intel based. I have a couple of old AMD Hack's (FX-series) and have setup a few Ryzen Hack's for friends and family. Plus it is not something you have to go and edit or change regularly, once you have a working kext you shouldn't need to edit or change it ever, well not unless you change the SMBIOS for your system.

Some basic instructions are included on the USBToolBox Github page linked below.


From what I recall it is all down to how meticulous you are at setting the USB ports with the correct Connector Type, when undertaking the USB port discovery. Get that wrong and the UTBMap.kext will be worthless.

I use images of the motherboard and rear I/O plate (on desktop systems) for noting which port is activated by each physical port.

I found that It is always advisable to include a name for each port, so you can easily identify any incorrectly set ports. There is a function in the script that allows you to edit/add a name for each port you identify. That is as long as the names you used made sense and actually tell you which port is associated with each physical port, and whether it is a USB3 port or a USB3/2 port, which would be the my notation for a virtual USB2 port, each USB3 physical port has as a companion USB2 port. It is important to remember that both the physical and the companion port should be set to match the physical aspects of the port, i.e. set with USB3 (3) connector type. Same for Type-C ports, there will be 2 x ports from each physical port, and both should be set with Type-c as the connector Type.

The USB port discovery process is based on Corpnewt's USBMap script. There are some additional instructions on this page, which allow you to undertake the port discovery in Windows or macOS.


This final link to the USB port mapping guide on the Dortania site is probably the most detailed. Well worth a read, and then another read before you commence the USB port discovery on your system.

 
  • Like
Reactions: Jo-Toku
I have tested many times and found that Venture13.1 can boot successfully without GenericUSBXHCI.kext, even without customizing any USB port.





No USB ports are customized



In most cases, it will be stuck in the position below, which can be skipped only through continuous forced restart. As long as the startup is successful, the USB of the system is completely normal, no matter whether there is a customized USB port or not, I have no relevant knowledge to test why it is stuck randomly, I hope someone can give me some tips, thank you

 

Attachments

Hello everyone,

IMG_20221230_130605.jpg

Getting this problem after a few seconds.

Brand: Lenovo
Model: Legion 5 6th Gen
CPU: AMD Ryzen 7 5800h
GPU: RTX 3050ti (disabled)
HDD: Samsung SSD 980 1TB (1000 GB, PCI-E 3.0 x4)
SKHynix (500 GB, PCI-E 3.0 x4)
Network: RealTek Semiconductor RTL8168/8111 PCI-E Gigabit Ethernet NIC
WIFI : Intel(R) Wi-Fi 6E AX210 160MHz
Ram: x2 8GB 3200mhz ddr4
Display: 15.6 1080p 165HZ

EFI Used
 
Getting this problem after a few seconds.

Brand: Lenovo
Model: Legion 5 6th Gen
CPU: AMD Ryzen 7 5800h
GPU: RTX 3050ti (disabled)
HDD: Samsung SSD 980 1TB (1000 GB, PCI-E 3.0 x4)
SKHynix (500 GB, PCI-E 3.0 x4)
Network: RealTek Semiconductor RTL8168/8111 PCI-E Gigabit Ethernet NIC
WIFI : Intel(R) Wi-Fi 6E AX210 160MHz
Ram: x2 8GB 3200mhz ddr4
Display: 15.6 1080p 165HZ

EFI Used
You have to remove or disable the SKHynix hard drive, which causes kernel panic, and your graphics card has no driver support, which will suck even after installation
 
Holy ****, The New HP G9 can use 128 GB of Ddr5 and 4 slots of G4 NVMe's. Up to a 1250HX desktop class CPU and the Radeon pro w6600m. This would be a beast of a hackintosh

Screen Shot 2022-12-30 at 8.35.13 PM.png

Screen Shot 2022-12-30 at 8.33.54 PM.png
 
Last edited:
  • Like
Reactions: CaseySJ
ANYONE GOT VENTURA WORKING ON THE LEGION?

I am taking the Legion 5 for a spin today with some workstation work. I dumped all of my working files with the Windows partition. So far ok, especially with a Magic Trackpad.
It is quite speedy. I may have to change the ram,. Seems the ram that comes with it is slow.

So far the laptop is behaving quite well. Having the peripherals working still makes it usable. I am doing graphical work and no issues as of jet(y)(y)

Anyone with experience with the laptop?





S__5054486.jpg
 

Attachments

  • S__5054484.jpg
    S__5054484.jpg
    369.3 KB · Views: 16
Last edited:
  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.