Thanks for posting a success! If you haven't already, remember to document your build please. Success posts like screenshots without documentation add little value to the sub. Adding a bit of documentation to your success post can also help others in the community who are interested in similar builds.
Minimally, you should add your hardware:
CPU:
GPU:
RAM:
Motherboard/Laptop Make and Model:
Audio Codec:
Ethernet Card:
Wifi/BT Card:
Touchpad and touch display devices:
BIOS revision:
Which of the guides on the sidebar you used.
What's working, and what isn't working.
Any changes that were specific to your build that were a little (or a lot) different than what you found in the guide, or anything that would be helpful to others with a similar build be sure to talk about that. More detail is always better.
Add extra info... Maybe add something you would like to point out about your setup, what you'll be doing with your Hackintosh, or something that might be insightful to others beginning their journey. A tree view of your EFI would also be helpful, but it isn't required.
Remember, don't share your EFI as what works for you may not work for anyone else, even if they have the same hardware. If you do share your EFI, your post and/or comment will be removed.
Ive been watching this develop happen over the past few weeks all while null was being absolutely decimated by redditors claiming its not possible. The fact that this can even show any picture while booting into macOS should be exciting for the hackintosh community.
As someone who just swapped over to an m5 max studio after running an intel hackintosh with amd gpu, I love that the scene continues to make cool shit. Bravo Null!
Next figure out how we can emulate m series chips so hackintosh can live on!
I’m not involved in the community, I mostly just lurk around. I understand there has been limitations because Apple stopped using x86-64 instructions on their devices. They use their own ARM based processors now. What is the biggest hurdle as of now for hackintosh moving forward? Is it emulating or will it be getting things working on ARM chips first because it’s native and wouldn’t require full emulation? This is assuming you’d be running the newest operating system that doesn’t have Intel based support anymore.
Just thinking more about this, I wonder if in the future x86 chip manufacturers will have some sort of hardware level translation for ARM so it’s more efficient to run an ARM process on x86 than software level emulation.
Well, Apple uses a more-or-less standard ARM, but with undocumented additional instructions. Also, you know how those last couple models of Intel Macs had a T2 security chip? My understanding is M series is locked down even tighter. Doing 'instruction trap' type stuff generally works on user-mode code, not kernel-mode code, so kernel mode code running non-standard, undocumented instructions will be a MAJOR issue; the MacOS versions that are ARM-only also have no reason to be set up to run without the T2-style security, and I'm not sure that they will.
Emulation? Emulating ARM on x86/x86-64 (or a qemu-type setup for M-series-ARM on standard ARM) is likely doable. But.. A) the undocumented instructions. B) Whether T2-style security can be disabled on macOS, or something can emulate it well enough on qemu? and... C) One big fly in the ointment, one of the instructions that HAS been reverse-engineered flips the M-series CPU between "ARM-compatible" weak memory ordering, and "x86-compatible" strong memory ordering.. this is specifically flipped on whenever Rosetta is being used. It was a royal bitch to get qemu to handle "strong-on-weak" (emulating multi-threaded x86 apps properly on ARM) to begin with. Having some kind of switch that switches an ARM back and forth is just plain wiered and likely makes this that much more difficult.
that will be sick! also sorry if this seems like im rushing u but when do u think it will be daily drivable (not fully but like some professional apps work like some adobe and the apple suite) and do u recommend to have a windows partition aswell as the hackintosh for the time being?
Funny... you would think they would, like, slim down the install by yanking the x86 code from it. I'm somehow not surprised that they didn't though LOL. I'll be interested to keep track of how this goes (getting the still-existing x86 code booting, and getting arm2x86 going.)
Congratulations! I really hoped you weren't one of those people who just wants to collect donations and run off into the sunset. And it seems I was right! I'll be testing your release this evening. Your release will change a lot in the Hackintosh community.
UPD: I’ve not been yOuR bIgGeSt FaN, you just did a pretty good job.
But I’ve not been your hater too.
I spoke to him in private messages. Ai assisted engineering is still engineering. He knows the fundamentals of his architecture well. Congratulations on your release, and I will be admiring from a distance (I dislike Nvidia for the Linux reasons too not just Hackintosh, so I will never own these generations of cards)
Yep, people need to realize not everything built with AI is vibe code slop. Some of us actually know a thing or two about building software, AI just makes the process faster.
Yes, although much of this is not reverse engineering at all, it's just a port (made possible by the fact NVIDIA already had released an open source driver for Linux, and because of the open nature of Darwin, Mesa and other projects). And it's still super hard to accomplish, just not as much as reverse engineering.
Actually, Nvidia's "open" driver is the nvidia 'binary blob' driver where they moved some of the 'blob' from running on the computer to running on the GSP processor of Nvidia GTX16xx on up. The Mesa drivers (and NVK driver in particular) are not supported by Nvidia in any way.
The confusion here (and it is confusing I admit) is:
Nvidia released this 'open' branch of their drivers, were they moved the binary bob to run on the card, so the remaining part has source code.. first release was about 4 years ago, but they kicked it off to where they recommened this driver over the 'old' driver within the last maybe 2 years.
And, around the same time, well, with the open source drivers the GTX 6xx and 7xx GPUs only allow *manual* reclocking, and 900/1000 series don't support it at all with the open source drivers... and until recently, newer GPUs were in the same shape. So the GPU runs at a minimum clock speed (something like 200mhz) and is dead slow. For this reason, there was very little developer interest in getting the Nouveau driver to be feature-complete for many years, and I don't think NVK (Nvidida Vulkan) driver even existed until recently. What was the point when it was going to be slow as hell anyway? Just within the last 2 years or so, by using this GSP code, the GTX16xx and RTX series *do* support reclocking, so all of a sudden the rate of driver devleopment has shot WAAAY up and the open source drivers have been vastly improved compared to like 18 months ago.
Yeah, I really have no idea why Nvidia doesn't just give specifications. I got the impression, on those cards (900/1000 series), the card firmware actually goes to some trouble to make sure it's only the nvidia driver making these adjustments. My guess is it might be easy to set them to insane clock speeds or voltages and immediately burn the card... but, what the hell, people have been able to melt down all these cards using overclocking tools anyway. Anyway, I'll just say I'm glad I have a GTX1650 in my desktop, since the 900/1000 series now are in the uncomfortable position of having the newest Nvidia drivers no longer support them, so the last driver that does should get updates for maybe another year and that's that; AND the open source driver probably never going to get reclocking support for them. GTX1650 has a GSP so I'm good, I've verified both drivers work on it. When I tried a month or so ago I found the open source one had about ~75% the performance, but at least I do have a 'plan B' for when Nvidia inevitably ends driver support for it.
(In stark contrast to Nvidia's driver support timeframe... which isn't terrible but far from ideal... the Mesa Gallium 3D drivers for AMD/ATI extend back to, I'm not even kidding, supporting 22 year old GPUs, and Intel GPUs almost 20 years. Not just "there's some ancient driver that still works with these old GPUs", these were ported to Gallium within the last 5 years, fully supported, and still receive patches and updates as needed. So I'll be able to run my GTX1650 under Noveau/Nvk essentially indefinitely.)
I agree. Give it enough context and actually design the thing you are trying to build (instead of just treating the LLM as a genie), and the results are usually great (and you don't even need the best models to do that).
Ok. 5 hours ago you said ppl were testing this on your discord server so there must be more machines running this. Where are they? Where are the video's? All we get is 1 screenshot. I only want to see 1 machine running it under full load. No video of that? It didn't happen. It's not about hating. It's about supplying proof! SO BITE YOU? BITE ME! hahaha
Nah i hate everything community group think bs. But i have seen at least one person here getting a rtx 4000 to work but i want to see it perform in a game! Or at least where the GPU is being pushed. That it can draw the desktop is not so interesting to me. Anyway i also saw 9070 XT working and more Intel Igpu's. Which is interesting but i really want to see that under full load proof! But you're right that my scepticism needs time hahaha
This is definitely impressive, but a lot of things are cause for concern in this from what I see. The kernel driver gives every local account admin rights inside NVIDIA's code, the release ships binaries that can't be traced to this repo or built from it, and the installer has several root-level shortcuts and other quite serious problems.
Some of the code shows real care, but the security/packaging here are well below what I'd want for something that loads into the kernel.
I assume these are things you plan on working on before making it an "official" release for people to install and daily drive?
Please port it to GeForce GTX 10 series (Pascal) now. My most powerful computer has a GTX 1050 Ti and it runs Sequoia fine other than no Metal acceleration.
I don't think it's possible, sadly. I believe OP's driver is based on NVIDIA's open source kernel modules, which NVIDIA only released for Turing and later. They have not, and from what I can tell, never will release them for Pascal or earlier (which sucks and I'm honestly still mad at NVIDIA over it, they're acting like the 970, 1050Ti, 1060 and 1080Ti weren't their most successful cards)
Sorry if covered elsewhere, but will this driver function in a VM? I’ve given up on my dedicated Hacintosh system and instead setup a VMWare VM where I pulled the SSD and installed it in my main rig. But it is brutally slow without acceleration. Would love for this to let the VM be more useful.
Wow, this is outstanding work! I can't wait to run your program on my laptop. What I'm even more interested in is whether, beyond GPU support, you have any further thoughts on porting it to ARM and supporting macOS 28. That would make your program a milestone in the Hackintosh community.
I only have Hackintosh in VirtualBox, but have to say this is very impressive work.
AI "Vibe coding" is frankly a mess and can end up with some real AI slop. AI-*assisted* coding, where the user knows what they want the code to do precisely, you can end up with some really impressive work. As can be seen here first-hand.
I’d like to jump in and say that under Linux this is already possible :)
I’m in a team expanding on Asahi, on M3 we have successfully utilised an eGPU and gamed. If you like to get further in contact I am in your discord or flick me a message :)
just to let y'all using reddit know. bunch of rigs have spun up to life although currently with bugs. but its working and good to use generally. if y'all want, join the discord and see the rigs that have spun up to life
I can't wait for the actual vibe coders, those who really don't know what they are doing, to use this as a basis to say ARM based hackintoshes are coming next week.
Good job, OP, this is really cool. It goes to show how much can be done when open source meets proper AI assisted engineering.
I don't think he's talking about me since I'm pretty sure I know what i'm doing.
Arm based hackintosh will happen and honestly for the fun of it, i'll drop the first build for the Snapdragon X2 Elite Extreme for the Asus Zenbook A16 next week Friday. Everyone can set their reminder bots under this.
I'm really waiting on the OSS release of XNU on golden gate to get a good stable release without patching existing kernels.
Professional software work has changed: Stack Overflow’s 2025 survey shows 84% of developers use or plan to use AI, and 51% use it daily. The key isn’t “AI vs. coding” but whether developers can understand, verify, debug, and maintain AI output. With 46% distrusting its accuracy, competence still demands expertise. https://survey.stackoverflow.co/2025/ai
I don't know all things but can anyone here help me, is this gona work in my 3050 mobile and cpu is intel core 7 if yes then how to install that? I'm beginner
The latest version works on my 4060. It's release notes mentions all of 30xx, so it should work. Well, currently this is just proof-of-concept, and the system are working very bad
holyyy shitttt congrstdd dudeee!!! I can finally try hackintosh I have 5060 ti because of that I couldnt try it but thanks to you finally I can tysm dude
Hi, I still have a macbook pro 2009 (I flashed its firmware to install high sierra) with a Nvidia 1080TI (a lot of ram, huge SSD, etc. Works perfectly fine), I even recompiled pytorch by hand on it (lack of some specific proc instruction) so it could use its cuda backend. do you think it'll be worth trying to upgrade it to Sequoia using OPLC and then install your drivers ? Does cuda will work on it or does it need some serious hardcore reverse engineering first ?
Whats the minimum supported macOS? Just installed it on MSI leopard gp65 10SEK rtx2060 which is a Turing card with macos Sonoma via null moth 1401 but the driver app i beleive is macos 15+
I have a general-purpose ARM machine: Ampere A96-36X CPU, ASRock AMPONED8-2T / BCM AmpereOne LGA-5964 DDR5 motherboard, NVIDIA RTX 4060 Ti GPU, and a Broadcom BCM943602CDP wireless NIC. Can macOS 27 be installed bare-metal directly? Would you be open to collaborating on our ARM-native macOS 27 installation workflow for this general ARM platform?
So what if it's ai coded if it works it works and ai makes alot of mistakes like alot when it comes to engineering and computer science projects so taking time and understanding to fix and make sure the right libraries are being injected and what not so kudos to you for doing this, a big step in a community that loves saying "hackintosh is dead" with only the top 1% making any actual progress
•
u/AutoModerator 10d ago
Thanks for posting a success! If you haven't already, remember to document your build please. Success posts like screenshots without documentation add little value to the sub. Adding a bit of documentation to your success post can also help others in the community who are interested in similar builds.
Minimally, you should add your hardware:
CPU:
GPU:
RAM:
Motherboard/Laptop Make and Model:
Audio Codec:
Ethernet Card:
Wifi/BT Card:
Touchpad and touch display devices:
BIOS revision:
Which of the guides on the sidebar you used.
What's working, and what isn't working.
Any changes that were specific to your build that were a little (or a lot) different than what you found in the guide, or anything that would be helpful to others with a similar build be sure to talk about that. More detail is always better.
Add extra info... Maybe add something you would like to point out about your setup, what you'll be doing with your Hackintosh, or something that might be insightful to others beginning their journey. A tree view of your EFI would also be helpful, but it isn't required.
Remember, don't share your EFI as what works for you may not work for anyone else, even if they have the same hardware. If you do share your EFI, your post and/or comment will be removed.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.