iATKOS | United Kingdom

The screenshot provided from boot manager shows an option to disable the FakeSMC.kext, which is a crucial kext (kernel extension) for Hackintosh systems as it emulates the System Management Controller device found on real Mac hardware. It's unusual that your Hackintosh won't boot unless you disable this kext because macOS typically requires it to boot successfully.

If your Hackintosh only boots when disabling FakeSMC.kext and you have to put Nvidia graphics to VESA mode, there could be several underlying issues. Here's a step-by-step approach to diagnosing and resolving the problem:

1. Check for Correct Version of FakeSMC:

   • Make sure you're using the correct version of FakeSMC.kext that is compatible with the macOS version you're running.

2. Replace FakeSMC with VirtualSMC:

   • Consider replacing FakeSMC.kext with VirtualSMC.kext, which is a modern alternative to FakeSMC and may offer better compatibility with newer versions of macOS.

3. Nvidia Graphics Compatibility:

   • If you need to switch Nvidia graphics to VESA mode, it suggests there might be an issue with the graphics drivers or compatibility. Verify if your Nvidia GPU is supported by the macOS version you're running.

4. EFI Partition Kexts:

   • Double-check the contents of your EFI partition. Even if you do not see FakeSMC.kext in your kexts folder, it might be loading from elsewhere. Use a mounter tool to access your EFI partition and ensure all necessary kexts are properly placed.

5. Config.plist Check:

   • Examine your bootloader's config.plist file for any incorrect settings that could be causing issues with kext loading. Ensure that the settings are consistent with the hardware and macOS version.

6. Kext Caching:

   • Rebuild the kernel cache using the terminal command sudo kextcache -i / and then reboot. This can often resolve issues caused by old or corrupted cache files.

7. Correct Bootloader Flags:

   • Verify the boot flags you are using. Sometimes, boot flags can interfere with the loading of kexts or the proper initialization of hardware.

8. System Integrity Protection (SIP):

   • If SIP is enabled, it can prevent the proper loading of certain kexts. You can disable SIP from the recovery environment by using the csrutil disable command in the terminal.

9. Hardware Check:

   • Ensure there are no underlying hardware issues that might be causing the system to hang, such as faulty RAM or an incompatible piece of hardware.

10. Consult Hackintosh Communities:

    • Look for advice specific to your hardware setup in Hackintosh forums or communities. Users with similar hardware may have encountered and resolved the same issue.

Remember to always backup your current working system before making any changes, and proceed with caution when adjusting kexts and system settings.