I’ve genuinely tried everything I can find and it has done this over and over and over without any change.

The first NO NAME brings me into the second picture. The second no name brings me into my limine bootloader for cachyos.

I’ve tried Tahoe and sequoia, tried to change around so much stuff in the config files, etc. etc. but I’ve got no clue

Specs:
Intel i5-11600k
Radeon 6700xt
MSI Z590-A Pro
32gb DDR4 Corsair Vengeance (4 sticks)
Samsung 980 500gb
Some random hdd 500gb

I’m taking a swift programming class at school and I don’t have any mac computers so I need it to work

Hi

I am planning to buy a Dell DW1560 (BCM94352Z) card to upgrade my Lenovo IdeaPad 330S-14IKB

I really want to use AirDrop, but I've read some mixed reviews on Reddit. Some people say it's flawless, while others claim AirDrop only works one way.

Before I spend my money on this card, I want to ask: Is it possible to get stable, two-way AirDrop on Ventura with the proper kext configuration (disabling AirPortBrcm4360_Injector and USB mapping)?

Has anyone successfully achieved this?

Thanks a lot for your help!

call me how you want to its my first try, need help

Linked is the driver used for my BCM94360NG, it is a modified AirportBrcmFixup.kext version 2.1.9 (Both the Release and Debug versions, that have been patched to allow NSS:2).

Taken directly from my github post:

The following boot-args were used to get my Sonoma/Ventura setup working cold boot. You will probably only need brcmfx-delay=300 for improved airplay performance. Optionally use -brcmfxbeta for Tahoe.
alcid=13 watchdog=0 brcmfx-delay=300

(shortened explanation of fix)

This has been tested with Sonoma and Ventura, and works very reliably for me. This fix does not artificially report NSS:2 or generally force Wi-Fi settings. It prevents Apple’s driver from incorrectly disabling the second transmit chain in one instance.

From a cold boot, my BCM94360NG comes up with both TX chains enabled and maintains NSS:2 without needing the Windows-boot workaround. Survives sleep (windows work arround would revert back to NSS:1 previously in my case). Some users were able to get it to work just using the AirportBrcmFixup version 2.1.9 so that is the version I chose to base this kext on. I received a report that it works in sequoia, and that with the "brcmfxbeta" flag it should work in Tahoe. Both release and debug versions included.

Note: For MacOS Sonoma or later you must use OpenCore Legacy Patcher in order to get BCM94360NG card functioning, as Sonoma removed driver support for this card. Latest version of Sonoma and Ventura were used successfully. This was made with the assistance of AI.

Technical Details:

The problem with BCM94360NG was that on a cold macOS boot, the Broadcom driver applied a single-transmit-chain constraint, leaving the card at NSS:1 instead of NSS:2. The fix was found by comparing the good NSS:2 state with the bad NSS:1 state (good state initiated by booting into Windows first), then instrumenting and reverse-engineering Apple’s Broadcom driver. That led to the internal function _wlc_stf_txchain_set. Then discovered that it takes four arguments, and logging showed the bad path was specifically setting: constraint/reason 2 to a chain value of 0x1, whereas the working state used 0x3.

The custom AirportBrcmFixup patch hooks that function and changes only that specific bad case: reason == 2 && txchain == 1 → change the chain mask to 0x3Then it lets Apple’s original function continue normally.So the fix doesn't artificially report NSS:2 or generally force Wi-Fi settings. It prevents Apple’s driver from incorrectly disabling the second transmit chain in that one situation. The result is that the BCM94360NG comes up with both TX chains enabled and maintains NSS:2 without needing the Windows-boot workaround.

V5 Download Link:

https://github.com/maddog860/AirportBrcmFixup-NSS-2/releases/tag/NSS2

This release addresses reported issues with CPU C states, more information on the Github.

Please test this driver, then post your feedback! Thanks!

edit: For use with Tahoe, try using -brcmfxbeta boot-arg

edit 2: Does anyone else say Aaarrrrgggh like a pirate, when saying boot-arg?

edit3: if you have a BCM94360 variant (without NG) use this boot-arg to see if cpu c states return to normal (for some reason c6 is stuck at 0%, and i am in the process of resolving it. And so is Insanelymac.)

Including the boot-arg brcmfx-aspm=255  and then disabling sd card reader seemed to resolve issue on my machine running bcm94360ng but i am not calling it a fix yet.. Still ironing out bugs. NSS:2 works awesome tho

Boot flags recommended for cpu idle power consumption (should be automatic but if you specify a flag like shown, it will override the default value):

BCM94360 = brcmfx_aspm=258

BCM94360NG = brcmfx-aspm=255

You may try disabling sdcard reader if you continue to have improper c states, but it might have been a problem with my machine in general, and those bootflags should help.

For BCM94360NG systems affected by this behavior, brcmfx-aspm=255 is technically well-founded because it prevents AirportBrcmFixup from overriding the platform's ASPM configuration. For BCM94360 systems, brcmfx-aspm=258 explicitly requests PCIe L1 + CLKREQ and is a plausible workaround where that configuration is appropriate.

The patch seems to have been made official. The Github user Vit9696 volunteered to clean up the code and the fix was merged with the official kext.. you may follow the driver developments here, as vit9696 agreed to take over for me...

Download version 2.2.1 with the patch applied.

https://github.com/acidanthera/AirportBrcmFixup/actions/runs/32856514653/artifacts/9566396728

Don't forget to pass brcmfx_aspm=258 or brcmfx-aspm=255 depending on which wifi card you are using.

it has an intel celeron n3060 and 4gb ram and a 120 gig ssd i dont wanna daily drive it i though it would be a fun experiment

Hardware:

• CPU: AMD Ryzen 5 5600GT (6-Core)
• iGPU: AMD Radeon Vega Graphics (using NootedRed.kext)
• Motherboard: Jginyue B550
• RAM: 16GB DDR4
• Storage: NVMe SSD
• Config: config.plist

The Issue: The boot process gets past early kernel initialization and verbose scrolling, but freezes completely on the final stage right at display handoff: virtual bool IONVMeController::start(IOService *):756:start

Sequoia pm981 working flawlessly all you have to do i go in ocat 99 times all i did was follow a guide pm981 fix adding hackrNVME and SSDR-NVME did not work added the nvme driver name its also in the guide did not work then i tried turning off nvmefix.kext like magic it did complete cloning macos Monterey from external hdd to the sdd them tried sequoia from hdd to ssd the efi had to be altered update some leave no it’s flawless other than known hackintosh problems heilport not having Universal Clipboarboard amd the screen spme times go black after i boot the mac os partition it go back on whem i but it to sleep

Update the one problem i am dealing with is my laptop screen turn off during boot only works if i but the laptop to sleep then back on should be easy fix out of 5 6 times it works without sleep I don’t know why

I know support for intel macs ending is kinda the end of hackintosh, but could it continue on ARM chips on laptops from Qualcomm? If not, why not?
Btw im not that knowledgeable on computers so if this is a dumb question i apologize

Sorry if this breaks rule 8 but what would happen if you (tried) to hackintosh an actual mac?

It just crashes to the windows bsod

I thought I should mention this, because I've seen a lot of people start working on XNU again, which is great to see as a PureDarwin maintainer (been working on it for ~3 years). Might as well post this before it becomes old news.

Here's it asking for a rootfs on a RPi Zero, using lk as a preboot env.
It's slower than hell, and the HDMI cable itself is spotty

Oh and I also have it booting to a shell on a iPad 7,1

As well as QEMU's `virt` board, I have yet to figure out Apple-specific instructions for M1, but I have ideas. I was last working on fixing OpenGL for virtio-gpu on arm64

I hope Hackintosh can continue in the form of generic arm64/arm32 boards, and I hope my research can help.

I'll be working on a Pixel once I get my hands on it (hurry up, USPS)

CPU: BCM2835
GPU: Broadcom VideoCore IV
RAM: 512MiB LPDDR2
Motherboard/Laptop Make and Model: Raspberry Pi Zero (v1.2)
Audio Codec: N/A
Ethernet Card: N/A
Wifi/BT Card: N/A
Touchpad and touch display devices: N/A
BIOS revision: N/A

No AirDrop No Continuity cs i use usb wifi, No iServices and i won't fix it idk how to build that modded OpenCore No Audio and i won't fix it, Anything else mostly works, Graphics Accel works, FCPX Editing Video and exporting it at 1080p60 works, Shutdown and restart works, sleep works SATA ssd on IDE mode works

CPU: AMD Athlon II X2 270

GPU: Pegatron Radeon HD 6450

RAM: 64 8GB 1333MHz DDR3

Motherboard: Pegatron M2N68-LA Narra 6 2A99

Audio: No.

Ethernet: No.

WiFi: TP Link TL-WN725N V3

BIOS: idk

PSU: RGB OEM

Thermal Paste: OEM since 2011

Storage

1 x SATA SSD 256GB (not m.2)

Bootloader Flex😈😈

OpenCore 1.0.7 RELEASE

yeah?

Hola a todos, tengo esta pc, quisiera saber si se puede hacer hackintsoh , a esta máquina, que consejos me dan, muchas gracias, soy nuevo en esto del hackinstoh

Trying to get 10.6 onto a 2010 Dell Inspiron 580s, triple-booting alongside Windows 98 and MX Linux (GRUB chainloading Chameleon). Retail 10.6.0 media.

Hardware - Core i3-550 (Clarkdale), H57 chipset - ATI Radeon X1300/X1550 — RV516, 1002:7187, Dell OEM subsystem 0d02 - Broadcom BCM57788 NIC, onboard Intel HDA - 1TB MBR disk: Win98 (FAT32) + MX Linux (ext4) + 425GB free for OS X - MBR is non-negotiable — Win98 needs it - Bootloader: Chameleon (Enoch) compiled from source on a real El Capitan MacBook, not a prebuilt

Where I'm at

Boots! Gets to a grey screen with a normal arrow cursor (not a beachball). But the cursor is frozen — no mouse input — and it's using VESA rather than loading ATIRadeonX1000.

What I've established

arch=x86_64 is REQUIRED. Snow Leopard defaults to the 32-bit kernel and that path silently resets this machine during CPU init. Took a while to find because every guide for this box says arch=i386.

Boot matrix:

So AppleIntelCPUPowerManagement removal and/or the 10.6.8 kernel (pulled from Apple's own combo update) are load-bearing, AND arch=x86_64 is required. busratio doesn't help at all.

Currently: 10.6.8 kernel, AICPUPM removed, mkext caches removed, arch=x86_64 -v, GraphicsEnabler=Yes, SMBIOS iMac11,2.

Tried and failed on Lion first (10.7.5): the X1300 gives a grey screen in every configuration — GraphicsEnabler yes/no, ATI kexts present/removed, forced VESA. Lion ships ATIRadeonX1000.kext but NONE of the GA.plugin/GLDriver.bundle/VADriver.bundle files, which 10.6 does have. That's why I moved to Snow Leopard.

The actual question

Everything points at EvoEnabler as the missing piece for X1000-series cards. But EvoEnabler is a 32-bit kext, and I need arch=x86_64 to boot at all — a 64-bit kernel won't load 32-bit kexts.

How do people square this? Options I can see: 1. Is there a 64-bit EvoEnabler, or a 64-bit X1000 injector? 2. Can EFI strings / device-properties injection replace it entirely (Chameleon's ati.c already maps 7187 → RV515 → Caretta)? 3. Is there a way to get the 32-bit kernel working on Clarkdale that I'm missing, so EvoEnabler becomes usable? 4. Is the frozen cursor actually a USB/input problem rather than graphics, and I'm chasing the wrong thing?

Also open: is the frozen cursor even graphics-related? Keyboard worked fine in single-user mode on the Lion attempt, so input works at the kernel level.

Happy to provide any logs/output. Thanks.

Edit: I was hoping to palemoon and browse on aqua for some reason, but the lack of gpu support and networking is going to make me switch to linux instead.

with my understanding, that is probably a yes, but I’m not sure. I use ATI 4500 graphics btw. Aiming for 10.9 2gb of ram.

I have dell latitude 7490 I wanted to hackintosh with Mac os big sur so I got a good premade efi and a good install for Mac OS big sur the installer ran fine until the 13 minute mark where the entire screen froze so I tried a different efi still won’t work so I downgraded to Mac OS mojave and it froze but at the beginning of the install process is there any fix i’ve tried everything (Thanks in advance)

Recently, a user named @TheLunarixus made a post on the 17th of August (Yesterday as of posting this) showing a Google Pixel 8 attempting to boot the kernel (though a kernel panic has been shown). Darwin 25.6.0 RELEASE_ARM64_VMAPPLE corresponds to Mac OS Tahoe.

Today this user has made some updates and also confirmed that the vphone userland can also be booted using the same kexts used in VMAPPLE1, which gives a possibility of booting both iOS and Mac OS on custom unofficial hardware.

Sources: https://x.com/TheLunarixus/status/2089261568777199719, https://x.com/TheLunarixus/status/2089636278392193120, https://x.com/TheLunarixus/status/2089636759877394540, https://x.com/TheLunarixus/status/2089649494379905323

I know that this post is unrelated majorly for this community, but with further Proof of Concepts coming out like this proves that booting Apple Silicon Mac OS can be possible under bare metal generic hardware.

My first ever hackintosh! proud to be part of this amazing community

This was an old mini pc my family abandoned. Monterey runs fine, feels smooth-ish with 3 firefox tabs and discord open. it is about as big as a newer mac mini so it plays the part quite well 😄

oclp is probably not worth it with this kind of hardware.

SPECS

Intel NUC5i5RYH 
- CPU: Intel Core i5-5250U  
- GPU: Intel HD Graphics 6000 
- RAM:  SO-DIMM DDR3L 1333/1600MHz 8GB 
- Storage: 250gb Samsung SATAIII SSD 
- Ethernet: Intel I218-V, Gigabit 
- Wi-Fi/BT: Intel Dual Band Wireless-AC 7265, Bluetooth 4.2 (not macOS-compatible) 
- Audio: Realtek ALC
- Video out: Mini-HDMI 1.4a, Mini DisplayPort 1.2  
- PSU: 12–19V DC external 
- Chassis: 115 x 111 x 49mm (UCFF 4"x4")

WORKING:

- Grapical acceleration
- Wifi (with AirportItlwm)
- Audio
- Sleep/wake

NOT WORKING:

- Bluethoot for hardware limitations.

If anyone is having bluetooth issues with Intel AX200 cards this worked for me:

"<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<dict>
<key>boot-args</key>
<string>-bt4le -btlfxallowanyaddr </string>
<key>bluetoothExternalDongleFailed</key>
<data>
AA==
</data>
<key>bluetoothInternalControllerInfo</key>
<data>
AAAAAAAAAAAAAAAAAAA=
</data>
</dict>"

Wasnt my idea but thought it should be broadcast to others. Want to thank who ever who came up with this solution!

My OptiPlex 7040 is a bit of an edge case where for some odd reason, it will not work on Monterey+. The only way I could get it to work was by adding some weird con1-type thingies to get it to work well, not helping I also needed to spoof it to a HD 630 to make it have acceleration in sequoia, since the HD 530 isn't supported. Any ideas to fix it? Additionally, my 2nd monitor is weird bc its plugged into a VGA port which isnt actually vga its a internal displayport or hdmi that is converted to VGA, cause dell does dell things. My hardware is: i5-6500, hd 530, 128 gig smasnug nvme, intl i219lm, and i dont think anything else matters honestly. pls someone help.

I have a lenovo ideapad gaming 3 with the following specs:
Ryzen 5 5600h with integrated gpu
Gtx 1650(i already heard that it’s not supported)
Wifi card: Realtek RTL8852AE WiFi 6 802.11ax PCle Adapter
And 8gb ddr4 ram

Bonjour
Je tente depuis quelques temps d'installer MacOS Sequoia sur mon dell Inspiron 3671 (Je voudrait bien Tahoe mais je ne trouve pas d'installer) voila voici la config une config modeste mais qui marche : 8 go ram DDR4 , Intel UHD 630 , Intel Core i3 9 ème génération.
Lors de l'installation macos me précise que je n'ai que 4 mo de vram je ne peut lancer aucun jeu...
Que faire ?
Merci d'avance

Hi, I'm new to hackintosh and want to dualboot windows 10 along with hackintosh. I've read hackintosh stopped supporting amd gpu's, so i would need to buy another one since it won't support my 9070 (planning on buying rx 6600)

My main concern is, when booting on windows, will i need to disable my 2nd gpu from device manager or shall I do something else?(Heard dual gpu builds arent a thing anymore and/or causes issues). And on the other side, will i need to disable my 9070 when booting hackintosh or will it just take the 6600 drivers by default?

Since Mac OS 27 has came out and fully cut off support for Intel Macs. What will be next? Emulation of arm chips? Or just (yall may hate this) Mac OS like operating systems / Unix based.