Tahoe not working on Ryzen 5 3500u

[rakismac32]

So currently i have a successful install of macOS Ventura 13.7.8 on my ThinkPad T495s with these specifications:

CPU: AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx
RAM: 16GB DDR4 2400MHz
SSD: 256GB NVMe
Wifi card: Intel Wireless AC 9260
iGPU: AMD Radeon Vega 8 Graphics

My current working efi build is mostly 'inspired' by this repo: https://github.com/PersistentCloud/Thinkpad-T495-Hackintosh

but when i try to upgrade to tahoe i simply get a kernel panic after reboot and trying to get into the installer assistant phase

Things i've tried:
Updating nootedred to a nightly build 0.9.0
Regenerating smbios to macbookpro 15,2

Any ideas to what i should change further to get tahoe working?

 

[rakismac32]

Forgot to include, here's my current EFI build

 

[craighazan]

Any ideas to what i should change further to get tahoe working?

Your config is a bit of a mess if I'm honest, for a start you put the patches in the wrong place!. I've never owned a Laptop hackintosh so I wouldn't be the best person to ask, but if you already have a successful installation of Ventura I suggest looking at the structure of that config to get a better idea of what you did wrong.

 

[rakismac32]

Your config is a bit of a mess if I'm honest, for a start you put the patches in the wrong place!. I've never owned a Laptop hackintosh so I wouldn't be the best person to ask, but if you already have a successful installation of Ventura I suggest looking at the structure of that config to get a better idea of what you did wrong.

Thanks for the response! it's my first time ever getting a reply in a forum site, fun fact.

Anyway, if the misplaced patches you're referring to is patches.plist file in EFI/OC, i remember it's a leftover from AMD_Vanilla patch which the contents i have copied to the config.plist in Kernel -> Patch, so i don't think it's being used by the bootloader.

However, i feel like my config is missing patches specifically required in Tahoe or Sequoia, since this same config can still boot Ventura, unlike other efi build i tried which won't even boot Ventura.

 

[etorix]

Have you adapted your USB map for Tahoe?

What makes you think you need specific patches for Tahoe or Sequoia? You have not mentioned Sequoia otherwise…

 

[Edhawk]

Have a look at the attached revised EFI, it should work with Sequoia, once you have added the SMBIOS data for a MacBookPro16,3 system to the config.plist.

For this to work in Tahoe, the USBMap.kext needs to be updated, i.e. New USB port and name entries added to the kext. This can be done by booting in to an existing macOS (Ventura) and using Hackintool version 4.1.5 Export a new USBPorts.kext, based on the current USB configuration.

For the record, USBToolBox.kext and UTBMap.kext don't work in Tahoe, as they lack this new naming configuration imposed by Apple when Tahoe was released.

I have cleaned up your original EFI - Tahoe folder, removing any unnecessary or duplicate entries. It should hopefully boot quicker than your previous setup, once you have added the MBP 16,3 SMBIOS data to the revised config.plist. Let us know how you get on with this EFI.

 

[Edhawk]

The EFI attached above would probably work with Tahoe as well as Sequoia, but there would be a few components that either won't work or won't work correctly. Those being the Intel AC9620 WiFi card, the USB ports, including the internal Bluetooth and built in Webcam and the Realtek Audio codec.

All of these components/devices except the USB ports and Webcam require specific fixes using OCLP-Plus or a similar post install application, plus specific kexts and config.plist entries to enable or block specific kexts.

As previously stated the USBPorts.kext needs to be updated to work with Tahoe, this will probably fix the USB connected Bluetooth and Webcam devices.

However, some systems don't boot Tahoe when the OCLP kexts are enabled or blocked in the config.plist. My 2 x B550 systems being prime examples. I have tried numerous OCLP versions and forks but can't for the life of me get the Broadcom WiFi working in Tahoe on these two systems. My X570 and B650E systems work perfectly with Tahoe, using the same native Apple Broadcom WiFi/BT cards.

 

[rakismac32]

Have a look at the attached revised EFI, it should work with Sequoia, once you have added the SMBIOS data for a MacBookPro16,3 system to the config.plist.

For this to work in Tahoe, the USBMap.kext needs to be updated, i.e. New USB port and name entries added to the kext. This can be done by booting in to an existing macOS (Ventura) and using Hackintool version 4.1.5 Export a new USBPorts.kext, based on the current USB configuration.

For the record, USBToolBox.kext and UTBMap.kext don't work in Tahoe, as they lack this new naming configuration imposed by Apple when Tahoe was released.

I have cleaned up your original EFI - Tahoe folder, removing any unnecessary or duplicate entries. It should hopefully boot quicker than your previous setup, once you have added the MBP 16,3 SMBIOS data to the revised config.plist. Let us know how you get on with this EFI.

Thanks a lot for the help! It finally booted sequoia past the apple startup error screen, but sadly, not much further.

So here's the steps i did chronologically:

• I installed sequoia on a separate drive by running install assistant on ventura
• While waiting for sequoia installed, i exported USBPorts.kext from Hackintool like you stated, then copied it to EFI/OC/Kexts. But since it also exported some SSDTs, i put them in the EFI/OC/ACPI just to be sure.
• After that done, i opened ProperTree to do OC Snapshot to the config.plist
• Then i opened GenSMBIOS to generate serials for MacBookPro16,3 then copy them to config.plist at NVRAM -> PlatformInfo -> Generic at their appropriate fields
• While still in ProperTree, i enabled ShowPicker so i can make sure it boots from the Sequoia volume
• Then install assistant is finished installing so i rebooted using the new efi build

After reboot, i picked Install macOS to continue the installation, then it rebooted multiple times until the volume name changed to "Sequoia". After that past the apple logo, i only greeted with gray screen for a few seconds, then it hard resets. Retrying that only does the same thing again. Then i booted back to ventura i got this error repport as attached.

 

[rakismac32]

Thanks a lot for the help! It finally booted sequoia past the apple startup error screen, but sadly, not much further.

So here's the steps i did chronologically:

• I installed sequoia on a separate drive by running install assistant on ventura
• While waiting for sequoia installed, i exported USBPorts.kext from Hackintool like you stated, then copied it to EFI/OC/Kexts. But since it also exported some SSDTs, i put them in the EFI/OC/ACPI just to be sure.
• After that done, i opened ProperTree to do OC Snapshot to the config.plist
• Then i opened GenSMBIOS to generate serials for MacBookPro16,3 then copy them to config.plist at NVRAM -> PlatformInfo -> Generic at their appropriate fields
• While still in ProperTree, i enabled ShowPicker so i can make sure it boots from the Sequoia volume
• Then install assistant is finished installing so i rebooted using the new efi build

After reboot, i picked Install macOS to continue the installation, then it rebooted multiple times until the volume name changed to "Sequoia". After that past the apple logo, i only greeted with gray screen for a few seconds, then it hard resets. Retrying that only does the same thing again. Then i booted back to ventura i got this error repport as attached.

UPDATE:
I finally got it working to the desktop by applying this workaround:

[Sonoma+] Specific compute tasks (like from the Wallpaper decoding) may hang · Issue #235 · ChefKissInc/NootedRed

CautionNote by maintainer: Workaround found! see here: #235 (comment) macOS Version Sonoma What is your CPU's model? AMD Ryzen 7 5700U Please describe the behaviour in detail. There is a beach ball...

github.com

But now currently not working components are:
WiFi (currently trying to fix by following this guide: https://github.com/5T33Z0/OCLP4Hackintosh/blob/main/Enable_Features/AirportItllwm_Sequoia.md)
Bluetooth
Battery percentage not showing up but only detects fully charged
Audio (builtin speaker & aux port)

Other than that, everything seems to be working perfectly without running into crashes or bugs.

 

[rakismac32]

UPDATE:
I finally got it working to the desktop by applying this workaround:

[Sonoma+] Specific compute tasks (like from the Wallpaper decoding) may hang · Issue #235 · ChefKissInc/NootedRed

CautionNote by maintainer: Workaround found! see here: #235 (comment) macOS Version Sonoma What is your CPU's model? AMD Ryzen 7 5700U Please describe the behaviour in detail. There is a beach ball...

github.com

But now currently not working components are:
WiFi (currently trying to fix by following this guide: https://github.com/5T33Z0/OCLP4Hackintosh/blob/main/Enable_Features/AirportItllwm_Sequoia.md)
Bluetooth
Battery percentage not showing up but only detects fully charged
Audio (builtin speaker & aux port)

Other than that, everything seems to be working perfectly without running into crashes or bugs.

ANOTHER UPDATE:
I finally got all of them working by updating outdated kexts and applying root patches to get wifi and bluetooth working natively in airport utility.
Just something i realized now is the touch panel built in my laptop doesn't work.

The touchscreen panel is a Raydium Touch System (i can't get any information on the model number) connected via internal USB hub.
It works in opencore gui boot menu, but once it got into the desktop it doesnt detect any touch input.
Though i know macos doesn't natively support touch screens but i've seen other laptops with working touch in hackintosh that only translates to a mouse click, I'll take that.

Any ideas on how to get it working?

 

[Edhawk]

Congrats on setting the system up and running.

You shouldn’t add all the files exported from the Hackintool > USB tab to your OpenCore folder. Just the new USBPorts.kext is needed.

No, I have no idea how to get the Touch Screen working in macOS. It is not something I would expect to work in macOS.

 

[rakismac32]

You shouldn’t add all the files exported from the Hackintool > USB tab to your OpenCore folder. Just the new USBPorts.kext is needed.

But it works anyway? even usb 3.1 type c devices like my usb c ethernet adapter works fine, or are there other side effects from loading the ssdts anyway?

 

[Edhawk]

You are basically duplicating the USB port configuration by having the SSDT’s in the /EFI/OC/ACPI folder and the USBPorts.kext in the /EFI/OC/Kexts folder, especially when using the Clean Snapshot feature in ProperTree. While this works in your case it is a piss poor way to get the USB ports configured when the USBPorts.kext does all you need for the ports to work correctly. It adds nothing helpful to your setup.

 

[rakismac32]

You are basically duplicating the USB port configuration by having the SSDT’s in the /EFI/OC/ACPI folder and the USBPorts.kext in the /EFI/OC/Kexts folder, especially when using the Clean Snapshot feature in ProperTree. While this works in your case it is a piss poor way to get the USB ports configured when the USBPorts.kext does all you need for the ports to work correctly. It adds nothing helpful to your setup.

So to clear things off first, since the original EFI build that you cleaned up already has SSDT-USBX, and Hackintool exported SSDT-USBX and SSDT-UIAC, I'm left with multiple options to clear this redundancy:

• Delete SSDT-USBX and SSDT-UIAC entirely
• Delete SSDT-UIAC and restore the old SSDT-USBX
• Regenerate SSDTs from scratch with SSDTTime

I need your opinion on which option would make my efi build the most stable, since based on your statement "USBPorts.kext does all you need for the ports to work correctly." would mean any of those options would work at front but may cause problems in the future. Thanks!

 

[Edhawk]

Delete SSDT-USBX and SSDT-UIAC entirely

This is what you need to do.

 

[rakismac32]

Thank you so much for the assistance! I’ll be sharing my journey in the Success Stories thread very soon.

Just yesterday, I dared myself to try booting Tahoe on a separate volume using the same EFI build. However, after the Install Assistant step on Sequoia was completed and the system rebooted to continue the installation, I selected the “Install macOS” entry from the boot menu. The Apple logo appeared, and the progress bar moved up a little bit, but then the system hard-reset.

Any idea why this might be happening? Since you mentioned that the same EFI should also work with Tahoe, I’d like to know what further modifications or patches might be required to get Tahoe working from Sequoia.

That said, I’m not taking Tahoe too seriously since Sequoia should already give me enough support to run newer software that I couldn’t run on Ventura. It would just be nice if I could get Tahoe running as a little side quest.

 

[Edhawk]

When installing Tahoe people have found that using a minimalist number of kexts is best, I.e. only the essential kexts should be present and enabled in the OC EFI.

The essential kexts for a desktop setup is very different from the list of kexts that a laptop user would need, due to keyboard, mouse/trackpad, battery and other non Apple components in the system.

What has also been found is that disabling NootedRed for the installation can prevent some unnecessary errors from happening. It can be enabled once you get to the Tahoe desktop, along with any other non-essential kext such as Bluetooth, WiFi and any sensor kexts.