AMD Rayon R7 5800H Install Monterey kernel Panic

[zxc2689963]

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

 

[Middleman]

Even from the Broadcom m.2 cards?

If you're using Broadcom cards you'll need to update to the latest AirportBrcmFixup.kext which has support for Ventura just added > https://github.com/acidanthera/AirportBrcmFixup

 

[Middleman]

@zxc2689963, I noticed on your config you filed the the device property of the RX6600m. What does this do?

View attachment 6102

Was this to avoid the white noise when getting to the installer screen?

Reason I ask:
In have 3 laptops with 2X with RX580's and 1X with Vega 56. and none allow me to enter the installer page after Mojave. From Catalina to Monterey I get white noise instead of the installer page. I dont have that issue with High Sierra and Mojave. I noticed that the GPU device property differs from your config. Now, have you ever witnessed the white noise and if so, how did you solve it?

@Jo-Toku
Actually that should be quite easy to fix. I have a RX550 set up for my B550 here >

[GUIDE] OC Monterey Gigabyte B550 Vision D + AMD Ryzen 5900X + RX550 + Samsung 1TB 970 Evo Plus

This is an update for Monterey on my existing Gigabyte B550 Vision D build that was originally built for Catalina. COMPONENTS & SPECS Gigabyte B550 Vision D board https://www.amazon.com/dp/B08C9GJ49M/?tag=tonymacx86com-20 Corsair Vengeance RGB RS 16GB 3200MHz DDR4 RAM...

www.tonymacx86.com

In addition to the device-id I use the setting no-gfx-spoof set to 01000000 using Type: Data. This allows any AMD card with similar specs to be used. It also needs the boot-arg npci=0x2000 agdpmod=ignore (this is for RX580 cards). This could work for Vega64 too.

On laptops you may also need the PEGP to GFX0 ACPI patch.

 

[OG Nerd]

I have a Hackintosh desktop with the Vision D Z590, RX580/ RX 6900(I swap them). Will check "PEGP to GFX0 ACPI " because that desktop hack havent been an issue. It has been mainly an issue specifically under laptops.

Agreed, I have a couple desktops with RX 570’s & 580’s & none have that acpi. So that must be motherboard specific or laptop issue maybe, but good to know in case I come across that.

 

[OG Nerd]

Let me have a look. I have a working build for Monterey 12.4 I am currently still working on which is actually working not only for my Ryzen 5900X setup
but also my Atari VCS with the Ryzen 1606G. I'll try and get it for you soon.

In the meantime if you want, you can try this. Install NVMEFix.kext in your Kernel, and also add this to your config under NVRAM:

View attachment 6104

For the WiFi you could try updating it to the latest Alpha 2.2.0 Airportitlwm.kext for Monterey.

Thank you.... On another note.... the Big Sur USB installer seems to not like any of the back ports, it would not boot into the installer even, as soon as I stuck in in the right side USB, boots up to the installer. (Hoping to get past the first reboot now, will post my success or failure shortly)

UPDATE: I got past the first time reboot of Big Sur installer! Something I did notice is that the trackpad does not work with the EFI from post #98, but I will fix that if I get Big Sur installed. (26 mins remaining lol) I have never been so dam excited to install an OS before that I plan on upgrading immediately lol

 

[OG Nerd]

That's brilliant! That sounds like the NVMEFix kext is doing its job.
Just need to see if it gets to the installer...

As for the trackpad, the fix is actually this using the VoodooInput & PS2 kexts and no SSDT-GPIO installed. The kexts need to be in this order:
View attachment 6105
If the trackpad doesn't work, enable the VoodooPS2Trackpad.kext as well.

OK, the nvmefix.kext got me into the installation and Big Sur Install successfully! As for the voodoo kexts. When I installed them and rebooted and reset nvram, it causes a kernal panic so I removed them for now. As for upgrading to Monterey, do we start the upgrade from the apple menu and use the EFI for Monterey on the next reboot or do we update the EFI then boot into Big Sur and start the upgrade?

 

[OG Nerd]

OK, I got to Monterey with Jo-Tuku's EFI, However I do not have touchpad and the bluetooth is not working, but the Wireless is. Going to work on the bluetooth right not.

 

[Middleman]

The last efi you supplied (with suggested settings) produced a kernel panic at boot, so I reverted back to the old efi, I am trying the RyzenUSBFix now. Will post update

Right. I am thinking maybe because it is missing the cpus=1 setting? I didn't add that unfortunately.

That's the reason why I included SSDT-CPUR and SSDT-CPUR-5800H-2. Reason being is the ones marked 5800H should be technically correct because they do follow the settings based on the actual DSDT output - so if it crashes again you'll have to change the kernel quirks to the ones that work with your other Monterey build. Technically it shouldn't because I had based the main EFI settings on both of my working Monterey 12.4 builds.

However I would also be interested to know what that earlier kernel panic was about.

 

[OG Nerd]

It might be a long shot but try the old GenericUSBXHCI kext.

I already tried that, I think it’s on the efi middleman supplied as well.

Right. I am thinking maybe because it is missing the cpus=1 setting? I didn't add that unfortunately.

That's the reason why I included SSDT-CPUR and SSDT-CPUR-5800H-2. Reason being is the ones marked 5800H should be technically correct because they do follow the settings based on the actual DSDT output - so if it crashes again you'll have to change the kernel quirks to the ones that work with your other Monterey build. Technically it shouldn't because I had based the main EFI settings on both of my working Monterey 12.4 builds.

However I would also be interested to know what that earlier kernel panic was about.

Ahhh…. That was something I didn’t even check, I will retry the efi with cpus=1 tomorrow!

 

[zxc2689963]

As for THE USB port mapping, I have customized the USB interface in system 10.15.7. What we need to solve is the kernel Panic caused by the installation of Monterey system in AMD notebook CPU. I know that there are several other AMD notebook CPUS that have such a situation.

 

[ExtremeXT]

Alright, I already see an issue. Your VirtualSMC is in the wrong place. VirtualSMC is a primary OC kext so must be loaded after Lilu and Whatevergreen and AppleALC.
Then underneath VirtualSMC we load AMDRyzenCPUPowerManagement and SMCAMDProcessor.kext in that order.

If it also helps, this kext list is from OGNerd's working Legion 5 build afaik. You'll notice he added GenericUSBXHCI.kext as well to the build. However he had put UTBMap up top which I don't agree with. It usually must come after VirtualSMC:

View attachment 7253

This is wrong. VirtualSMC IS in fact critical to booting, but it doesn't HAVE to be loaded BEFORE the kexts that DON'T require it. The kext list order was done by ProperTree's OC Clean Snapshot function which checks all prerequisites of all the kexts and generates a CORRECT and CLEAN order.

Also, we are now trying to fix the non-monotonic time AppleACPIPlatform, not the issue when using cpus=1.

- ExtremeXT

 

[zty199]

@Shaneee Thanks for your input. I'm pretty sure it would fix it since that's where it panics, but I'm guessing that it's not worth the time.

On another note, this seems like what we need! (Image)

@zty199 Please try this EFI.

@craighazan Do you also have this laptop? If so can you test it?

- ExtremeXT

Seems to be the same panic with TSC_sync_margin=0

 

[zxc2689963]

Install Big Sur 11.6.5 There is no kernel panic
I want to install Monterey. Rx6600m in Monterey driver

 

[Middleman]

Okay that's good to hear (because yours is the first known AMD CPU & IGPU I've encountered that works). If you've managed to install Big Sur on this and it's working that is extremely good news for the community.

Okay onto setting up the Monterey - have you created a custom USB map kext yet? It is vital that you do. You need to ideally create from within Big Sur.
Use the following USBMap script from here and once you've created it and reduced your USB port map down to less than 15 ports, disable your USBInjectAll and XHCIPortLimit setting to try to boot into Monterey.

https://github.com/corpnewt/USBMap

If anything else try to also make sure agdpmod=pikera is enabled in the NVRAM boot-arg (to enable the RX6600M).

 

[Middleman]

On a separate note, I had a quick look at your EFI, and find it totally odd you'd even managed to boot Big Sur! I noticed you hadn't even enabled SMCAMDProcessor.kext and a
whole load of other important kexts like AppleALC, Whatevergreen, SMCSuperIO, or AMDRyzenCPUPowerManagement. You also don't have the device properties set for the RX6600, which should be these:

 

[zxc2689963]

Yes, my OC configuration KEXT is all selected. You can enter the Big Sur installation screen. But most cases stop at the following code. You can only force the restart to try more times. Also, the Big Sur installation screen is slow to respond. The mouse can only move slowly. The graphics card has no driver. Therefore, the installation fails.

 

[Middleman]

Yes, my OC configuration KEXT is all selected. You can enter the Big Sur installation screen. But most cases stop at the following code. You can only force the restart to try more times. Also, the Big Sur installation screen is slow to respond. The mouse can only move slowly. The graphics card has no driver. Therefore, the installation fails.

Okay I've looked at it and done some changes. One of the biggest was adding some missing ACPIs plus adding some USB kexts and SMCBatteryManager.

During install it is best to use USBInjectAll but switching on XHCIPortLimit to enabled (for Big Sur) - and then switch over to USBMap but turn off XHCIPortLimit once you manage to boot into the system to install Monterey as Monterey needs this.

Anyways give it a try.

 

[zxc2689963]

Okay I've looked at it and done some changes. One of the biggest was adding some missing ACPIs plus adding some USB kexts and SMCBatteryManager.

During install it is best to use USBInjectAll but switching on XHCIPortLimit to enabled (for Big Sur) - and then switch over to USBMap but turn off XHCIPortLimit once you manage to boot into the system to install Monterey as Monterey needs this.

Anyways give it a try.

Thank you for your answer, I tried to stop at [EB LOG:EXITBS]

I want to solve the problem of installing Monterey. The test started the Big Sur installation, but failed to start Monterey.

kernel panic: AppleACPIPlatform





Installation mode: Hard disk Create 1 GB EFI partition. The com.apple.recovery.boot and OC files are placed on the hard drive EFI. Start the installation on a hard disk. Troubleshoot USB port faults. Of course I customized usbmap.kext.

 

[Middleman]

Thank you for your answer, I tried to stop at [EB LOG:EXITBS]

I want to solve the problem of installing Monterey. The test started the Big Sur installation, but failed to start Monterey.

kernel panic: AppleACPIPlatform





Installation mode: Hard disk Create 1 GB EFI partition. The com.apple.recovery.boot and OC files are placed on the hard drive EFI. Start the installation on a hard disk. Troubleshoot USB port faults. Of course I customized usbmap.kext.

Did you try the latest EFI I uploaded in the last post? That has a special kernel patch for Monterey, which you must use in conjunction with the USBMap.

 

[Middleman]

Did you try the latest EFI I uploaded in the last post? That has a special kernel patch for Monterey, which you must use in conjunction with the USBMap.

Oh in addition, you must also add AppleMCEReporterDisable.kext. That's for the latest 12.3 bug.