Hervé

In the Device Properties->IGPU section of the Clover config, the property that allows framebuffer patching is disabled. As such the fbmem and stolenmem patches are not applied. Oops! Remove the '#' character and Tahoe should boot Ok. ...Clover config of Sequoia and Tahoe bootpacks now fixed.

My E7270 guide is in the usual and expected forum section.

The contents of the Clover bootpack in my E7270 guide not any good???

Same issue as encountered with Sonoma; I've just updated all the guides and added the iGPU DVMT-related patches that were missing in the Clover config of the Sonoma/Sequoia/Tahoe bootpacks. A note was also added for those who do have patched their BIOS to increase DVMT from 32MB to 64MB or above. Once you add this, you'll be Ok: framebuffer-stolenmem 00003001 DATA framebuffer-fbmem 00009000 DATA

No, but you must have had the iGPU patch in your Monterey bootloader config.

Did you patch your BIOS to increase DVMT as explained in the guide's opening post? If you didn't, your E7270's default DVMT is set to 32MB and, indeed, you'll experience KP and resets at startup as the video memory patches are not present in the IGPU's device property settings in the Cover config. You would either need to patch your BIOS or add the patches listed below to your IGPU settings here: framebuffer-stolenmem 00003001 DATA framebuffer-fbmem 00009000 DATA Detailed explanations are available here and don't forget the WEG's user manual.

Of course you can, that's what I've posted in today's revised bootpack of the Sonoma guide (and that's what's posted in the subsequent Sequoia & Tahoe guides). These 3 items are only useful for legacy Broadcom wireless cards once you've applied the OCLP legacy wireless patch so if you're not using that but, say, an Intel wireless card, that's totally Ok. Just delete the kexts + disable the binary patch in your config file and you'll be good on all subsequent reboots.

With a fresh installation, make sure to boot without these 3 elements: BlockSkywalk under Kernel & Kext patch: unselect at Clover boot menu->Options->Binary patching->... IO802FamilyLegacy kext: Clover boot menu->Sonoma->[SPACE]->Block injected kexts->Other->... IOSkywalkFamily kext: Clover boot menu->Sonoma->[SPACE]->Block injected kexts->Other->... Only allow these once Sonoma initial installation is complete and you've applied the OCLP Patcher legacy wireless patch; and only if you have a legacy Broadcom card of course! Below are illustrations re: actions to take from the Clover boot menu: 1) to unselect/uncheck BlockSkywalk binary patch: 2) to block kexts at startup and prevent their injection: I've updated my Sonoma guide to avoid the issue you've encountered and make it similar to what I had posted in my subsequent guides for Sequoia and Tahoe.

Hi @tryit, I fear it's going to be much difficult to provide assistance without knowing if Bluetooth stopped working all of a sudden without you making any changes (in which case you could suspect a hardware failure) or after changes you made. In the latter case, only you can provide the necessary info. No EFI, no bootloader config file, ... I've not crystal ball you know... If you see the device in IOReg, it can only be your setup.

Released July 27th, 2026. Build 25G72. Bug fixes and security update. Safe to install on our Hackintosh platforms. Also released at the same time: macOS Sequoia Security Update 15.7.8 (Build 24G824) macOS Sonoma Security Update 14.8.8 (Build 23J620) View full article

I would recommend a few things to begin with: startup with a minimum set of kexts as in the Github repo; you may add more once macOS boots up and you need more services/hardware supported. the Github repo does stipulates that the posted EFI only works with Ventura. Did you try to install Ventura with it? your set of quirks differs a lot from those enabled in the Github repo. I've not looked at your hardware in details but I would suspect that your current quirks settings is at fault here.

hello, will have a look tonight.

For the who would experiment Bluetooth issues/crashes after wake, Mirone's BluetoolFixup kext v2.7.3 appears to fix the problem. Inject the kext and add -btlfixwakecrash boot parameter to your bootloader config. BlueToolFixup.kext.zip

Following a recent query on the matter, I want to confirm that, whilst there was a time during which it was no longer possible to easily disable Gatekeeper in early versions of macOS Sequoia, the facility described above later returned and still applies to Sequoia and Tahoe. Example in Sequoia 15.7.7: