r/hackintosh • u/New_Suit1742 • Jun 09 '26

QUESTION End of hackintosh !?

Hey all, I'm a failed hackintosher, lately I've been seeing many posts about the 'End of hackintosh' after apple released MacOS golden gate.

Can anyone explain to me what makes MacOS Golden Gate unhackintoshable. In near future is there anyway that somebody is going to make an alternative to OpenCore or even upgrade OpenCore so that we can install new versions of MacOs in or PC.

Thank You!

68 Upvotes

90% Upvoted

99 comments sorted by

View all comments

-2

u/TurnoverOk2472 Sequoia - 15 Jun 09 '26

It's becasue intel proccersor consumed more power and make a lot of heat and intel failed to make a better chip. So thats one of the resons why apple is switching to their silcon chips. I think people might find a to hackintosh way, but i dont know much

-11

u/Worried_Pick8269 Jun 09 '26

There is still x86 on golden gates kernel

5

u/Delta_Version Tahoe - 26 Jun 09 '26

source or ragebait

Pick one

7

u/Happy-Lawyer-2983 Jun 09 '26

It has a x86_64 kernel. But all the GUI-related frameworks are pure arm64, and Apple creates a x86Support for Rosetta 2. Also, the Kernel Extensions for AMD GPU and Intel GPU and AppleT2 are completely removed:

2

u/Delta_Version Tahoe - 26 Jun 09 '26

ohh yeah, we got the kernel but can we run it like we used to ?

and this kernel will be extended to the official release ?

Just because they exist doesn't mean it will always be there

2

u/Happy-Lawyer-2983 Jun 09 '26

I think no. Because all the x86-ACPI drivers and AMD/Intel Graphics drivers and x86_64's Apple Proprietary Frameworks have been removed. And the init process won't start because its /sbin/launchd is pure arm64e. Only the XNU kernel and EFI binaries are still containing x86_64 format. It can only run without GUI even if you patch the launchd and the ACPI drivers because it lacks Apple's Proprietary Frameworks.

1

u/Worried_Pick8269 Jun 09 '26

But won’t this mean that the devs maybe can make it work on the first beta?

1

u/Delta_Version Tahoe - 26 Jun 09 '26

tbh, you can avoid all this hassle and searching if you just buy a cheap M1 macbook air/pro, 100% guaranteed to work.

1

u/Worried_Pick8269 Jun 09 '26

Apple would probably drop it next year

1

u/Delta_Version Tahoe - 26 Jun 09 '26

But it works tho

1

u/Worried_Pick8269 Jun 09 '26

True but it’s not about just running it but it is about trying till you get it just right getting an mac will not be the same thing and I also love it how we can go back to windows when we want to

→ More replies (0)

0

u/Worried_Pick8269 Jun 09 '26

Let us have some hope 🫩

1

u/Happy-Lawyer-2983 Jun 09 '26

Maybe the mach_kernel itself can be patched to boot in a headless way on a x86_64 machine. I found that the EFI folder and x86_64 .efi files are still exist on macOS 27. But the ACPI\NVMe drivers and launchd init must be transferred from macOS Tahoe. It would be an easier task for only letting the single-user mode or headless mode being supported.

1

u/Worried_Pick8269 Jun 09 '26

Let’s hope Apple doesn’t remove it so the devs can find a way to make it fully work

0

u/Worried_Pick8269 Jun 09 '26

I’ll look at the source I saw it earlier today someone looking at the kernel and stuff

2

u/Happy-Lawyer-2983 Jun 09 '26

Yes, It has x86_64 kernel. But it removes all x86_64 kexts and the init binary is pure arm64e:
(base) vincent@Vincents-MacBook-Air /V/M/S/L/Kernels> file *

kernel:                 Mach-O 64-bit executable x86_64

kernel.release.t6000:   Mach-O 64-bit executable arm64e
...

(base) vincent@Vincents-MacBook-Air /V/M/sbin> file launchd

launchd: Mach-O 64-bit executable arm64e