All Activity

Did you remove Whatevergreen? You can't have it enabled when using NootedRed. See the prerequisites here, https://chefkissinc.github.io/nred#prerequisites

I get the same screens again when pressing F12

Hi @yarecco I'm afraid you'll have little success with the integrated graphics card "AMD RX Vega 8," if I'm not mistaken. Make sure to install a macOS-compatible graphics card to boot successfully.

Thank You me Friend Max... is a good Tool !!!!!!

Hi all. I successfully managed to install Mac OS on MSI PRO DP20Z 5M with Ryzen 7 5700G with integrated graphics. System installs properly ( both Ventura and Sonoma tried). I can boot to mac os recovery without any issues. But after installation when system should boot normally it stucks. I did all required settings in BIOS ( disabled fastboot, secure boot, CSM and set VRAM to 4G). I put NootedRed into kexts and enabled it in config.plist. What else am I doing wrong? Any help and suggestions please? Thank you config.zip

right i did add e.g. 0x9A688086 in the kext info.plist, but it still didnt work, still 7mb vram in system info.

The correct name for your GPUID might be 9A68, which is Intel® UHD Graphics on the XE Architecture, the GPUID used for the tests so far by shl and jala appear to be the 9A49 variant which is Intel® Iris® Xe Graphics on the XE Architecture, I am unsure if the nblue binary is hardcoded with 9A49 or if its just pure instructions with the info.plist as a config. See the list of GPU ID's here -> https://dgpu-docs.intel.com/devices/hardware-table.html, 8A96 is not on it. Its always a good idea to test if its possible by modifying the info.plist.

GTX1050 work on 14.4.1 after OCLP 1.4.3 patched.

hey all, so i tried the nblue kext attached here, my laptop has device id 8A968086, i dont know if it can work via nblue, but according to lspci -nn that's what my device id is. It IS tigerlake im using ventura 13.6.5 and i tried adding my device ID to the info.plist it shows as intel iris xe graphics but only 7mb vram and it's not accelerated, i dont know why.

I' m sure it's off topic so I'll not bore you to death with a technical talk on sound recording and reproduction. It' easy ...your cds thought maybe not so good (as the first Genesis editions) will anyway sound better than mp3. Everything sounds better than mp3 even Yoko Ono . No I was just kidding. Cheers

@bluenote56 maybe off topic here but doing the test and playing a few of my music disks, I don't know if it was my old ears but the music sounded crisper and clearer than my stored Mp3 music files. So I know exactly what you mean by not having a functioning CD/DVD player drive in your setup. Hope you find a solution soon.

@jrhende Thank you for the explanation. Nice job.

Well. first thanks all for your replies. Then, I must say I've been working in and with music for about 30 years and I can't live without music. You can imagine how many cds and dvds I have. If you add that I'm not a teenager any more (born in 1956) and that I think that mp3 and other staff but FLAC are absolutely s***t, you can understand my interest in having a full functional CD/DVD player. I don't follow this "so called" trend to consider cds and dvds dead. Liquid music is not the best but since unfortunately I can't always use my turntable and LPs it's a kind of compromise. Anyway I'll work on this issue to understand where the problem is. Otherwise if it's related to my mobo, I'll stay with Monterey but hackintoshers usually don't give up easily it seems... Thanks again. I'll post updates if any.

Does anything not work if you use this HP EFI? You could just use that as a base if it works. Add in any kexts you require. Update SMBios etc.

can i have the efi folder? Im stuck on low backlight.

Reboot, F12 -> and show us the screenshot.

A little more about Sonoma macOS 14.4 1. Starting from version Sonoma macOS 14.4 (including all 14.5 betas), if I restart the computer, the power to the HDD hard drives is turns off. Then, during the BIOS POST, power is turned on to the disks and they spin up one by one. This means longer reboot time, increased disk wear, and simply incorrect behavior. I couldn't solve this problem, so I'm staying with the version Sonoma macOS 14.3.1. To be fair, it must be said that all the machines (with different motherboards and CPUs of different generations) on which I updated the MacOS version to 14.4 or later behave this way. Apparently it's not a Hackintosh problem, it's a MacOS problem. 2. I slightly changed the hardware configuration of my machine (replaced one of the hard drives) and ran into others problems with reboot and shutdown. - When rebooting, it sometimes freezes, forcing me to shut down the computer completely. Sometimes it is enough to wait 30-40 seconds and the reboot occurs. When turning off the computer, sometimes I need to wait 30-40 seconds or hold down (4 sec) the Power button. - When the system boots, sometimes a kernel panic occurs. These problems are related to incorrect memory allocation. The solution can be obtained by carefully following this manual: https://dortania.github.io/OpenCore-Install-Guide/extras/kaslr-fix.html#so-what-is-kaslr The important feature here is that there is no universal solution and everyone must individually carry out this work for their own hardware. I would supplement this guide (kaslr-fix) with the following clarification. After you receive our own MmioWhitelist, do not use it mechanically, i. e. entirely. From this list you need to remove those items that prevent normal booting. Unfortunately, this can only be done manually, carefully selecting suitable positions and deleting unsuitable ones.

@iwissem, try this:AppleALC.kext.zip use layoutID=33.

After not getting any response (so far) This morning I tried rebuilding the EFI from scratch using Ironman's 0.8.8 migration kit and filling the motherboard data from an earlier config.plist. I get exactly the same list of errors. I wonder if the bios settings have somehow gotten screwed up? I haven't made any manual changes. I would normally never touch them. Can someone tell me what the optimum settings should be? Thanks...

Looks good. I think this should work well. There are several options to disable NVRAM protection as listed below: Boot to Recovery open the terminal and enter "csrutil enable --without nvram". Boot to OpenCore menu and select OpenShell then change to the mapping (FS#:) for the EFI partition containing OpenCore. Enter the following "FS#:\EFI\OC\Tools\CsrUtil.efi disable 0x40". Set the NVRAM value (in little-endian) for csr-active-config to 40000000 under NVRAM -> Add -> 7C436110-AB2A-4BBB-A880-FE41995C9F82 then add csr-active-config to NVRAM -> Delete -> 7C436110-AB2A-4BBB-A880-FE41995C9F82 and enable. This configuration will always replace the entire SIP value with the one specified as described here.

Have you updated your drivers from the 'official AceMagic' website?. https://www.acemagic.com/pages/drivers-downloads

I still deploy 2 cases that are fitted with DVD drive bays and in both I have a LG brand BlueRay RW drive installed with both functioning without issues under macOS Big Sur, Monterey, Ventura as well as Sonoma. Just wanted to let you know. Greetings Henties

May be your laptop has white list for allowed wifi?

Apple didn't make exfat driver working in recovery because the is no sense to use exfat during system recovery. System recovery should use only APFS drives, exfat can be used for data store, no more. If you have a system installer on exfat volume then copy it in a bootloader to APFS volume and then use in recovery.

Didn’t work with ExFatDxe.efi but in Ventura exfat volume mountable work fine intel base Mac without ExFatDxe.efi other hand in macOS Sonoma exfat volume is not mount recovery mode under disk utility