Jump to content
25 posts in this topic

Recommended Posts

The Giant Awakes! Clover Bootloader Updated for macOS Sequoia/Tahoe (GCC 15 Ready) 🍀🚀

Hey everyone, hnanoto here!

I have some exciting news about our good old Clover Bootloader. Tired of seeing the project lagging behind in compatibility, I decided to roll up my sleeves and perform a heavy "under the hood" update.

We've essentially transformed Clover into a beast (in the best way possible!), ready to stand toe-to-toe with any modern bootloader.

Key Recent Improvements (by @Hnanoto):

Recovery DMG Booting (ALREADY MERGED!):
Clover is now capable of booting natively from a recovery BaseSystem.dmg file. Installations and recoveries are now much easier and more robust.
Updated OpenCore Engine (New PR #782):
I've bumped the internal 
OpenCorePkg
 submodule to the latest version. Clover now speaks macOS 15 (Sequoia) and macOS 26 (Tahoe) natively.
Essential New Quirks (Sequoia/Tahoe):
DisableIoMapperMapping
: Goodbye Sequoia WiFi/Ethernet issues! VT-d support is now properly handled.
ResizeGpuBars
: Control Resizable BAR (Smart Access Memory) directly in the bootloader. No more disabling it in BIOS and losing Windows performance.
Modern Compilation (GCC 15):
Major cleanup of C++ code to support modern compilers (GCC 15+). Clean, lean code with no build errors.
Bottom Line: Clover is alive, up-to-date, and future-proof. For those who love the classic GUI and on-the-fly editing, you now have the latest OpenCore V8 engine running underneath, plus exclusive DMG booting features.

Cheers and happy Hackintoshing! — @Hnanoto

Captura de Tela 2026-01-12 às 19.02.25.png

  • Like 2
  • Thanks 4
Link to comment
https://www.insanelymac.com/forum/topic/362206-the-giant-awakes-%F0%9F%8D%80/
Share on other sites

8 minutes ago, LockDown said:

Thanks♥

You think model ID in smbios need updating too on modern OS?

"Hey! Great question. For now, the existing SMBIOS definitions (like MacPro7,1 or iMacPro1,1) still work fine for booting Sequoia/Tahoe, as long as you use -no_compat_check or the correct spoofing if your hardware is older.

However, since we updated the internal OpenCore engine, Clover is now much smarter at handling newer firmware features associated with those IDs. Updating the internal SMBIOS database with newer Mac models (M-series equivalents or newer Intel ones if any exists) would be a nice next step for a future PR! Thanks for the feedback! ♥"

  • Like 2
  • Thanks 1

@Hnanoto 

 

Thank you, my great brother, for all your effort and work on the Clover project, a respect recognized by Slice and by all of us. Thank you for being back in the Hackintosh scene and helping us. Long live the Hack, and may God always bless you with your abilities — we will go a little further beyond.

 

:super-homem: :avião: 

 

Attention, dear colleagues and Clover users: it is still in the approval phase, therefore release 5167 is not yet available, out of respect for the developers.

 

CapturadeTela2026-01-12s20_50_39.png.31e37f6ce83734765c1e46f35ecbe997.png

 

 

Edited by Max.1974
  • Like 4
20 minutes ago, Max.1974 said:

@Hnanoto 

 

Thank you, my great brother, for all your effort and work on the Clover project, a respect recognized by Slice and by all of us. Thank you for being back in the Hackintosh scene and helping us. Long live the Hack, and may God always bless you with your abilities — we will go a little further beyond.

 

:super-homem: :plane: 

"Thank you so much, brother @Max.1974! 🙏

Your words truly mean a lot to me. It is an honor to be back and contributing alongside legends like Slice and dedicated developers like you. I genuinely believe Clover still has incredible potential, and I’m just happy to help keep this legacy alive and evolving for modern hardware.

Let's definitely keep pushing the limits together. To infinity and... Further Beyond! 🚀🍀 Long live the Hack!"

  • Like 1
  • Thanks 1
8 hours ago, Hnanoto said:

"Hey! Great question. For now, the existing SMBIOS definitions (like MacPro7,1 or iMacPro1,1) still work fine for booting Sequoia/Tahoe, as long as you use -no_compat_check or the correct spoofing if your hardware is older.

I am lucky...no need of this boot arg on my AMD you can see in signature ;)

image.thumb.png.8d4925f2ef62937f6a7f8c96a57c333e.png

 

image.thumb.png.abe627a6f9ece05bf0e33b833825fc7d.png

 

Edited by fabiosun
  • Like 2
8 hours ago, Slice said:

"Thanks Slice! I saw the respect commit, huge honor! 🙏 Regarding 
OpenCorePkg
: Yes, I noticed our submodule is pointing to a commit from Dec 2025. My PR updated Clover to work with the latest available on your fork. If you want, I can definitely take a look at syncing CloverHackyColor/OpenCorePkg with upstream Acidanthera to bring even newer improvements, and then bump Clover again. Just let me know if I have permissions or if I should fork/PR there too."

  • Like 1
42 minutes ago, Alpha22 said:

@Hnanoto 

Congratulations on your work on the Clover bootloader

""Thank you very much! It has been a massive effort to keep Clover updated and fully synced with the latest Acidanthera developments.

In this latest update, I’ve managed to:

Sync OpenCorePkg: Fully updated the submodule to valid commits, fixing macro errors and build dependencies.
New CPU Support: Added the latest CPU definitions, including the AMD 1Ah Family (Zen 5).
Quirks Implementation: Ported the ClearTaskSwitchBit quirk and ensured proper handling of the Unload functionality for drivers.
CI/CD Overhaul: Completely fixed the GitHub Actions pipeline, resolving recursive submodule fetching issues and enabling stable builds with GCC 15.2.
I'm glad to preserve Clover as a powerful and updated bootloader for the community. Please test the latest build — feedback is always welcome!"

  • Like 2
  • Thanks 2

@Hnanoto @Slice 

Awesome !! Tested and approved !! Thanks a lot!! 

I am testing the new Clover with the new OpenCore update parameters, and I am impressed with the speed and responsiveness of the application. A major change and of great importance to the community. Thank you!!!!

 

To Infinity and Beyond – Hackintosh & Beyond

 

 

CapturadeTela2026-01-13s20_22_22.png.f375af1c7ab61966366f97ad45dbf736.pngCapturadeTela2026-01-13s20_23_34.thumb.png.925fc8d11b0f189ff1ee88273e02a5c7.png

 

 

Better perfomance on NVme its notorious !! 

CapturadeTela2026-01-13s20_21_28.thumb.png.d0e32b769eee16f96b14018dd5425faf.png

 

 

  • Like 3

Raptor Lake i9-13900K 

 

Hello everyone, I am very impressed with the new Clover 5167 commit, still in the testing phase, and I can assure you that the speed and smoothness are so much better that, to fully enjoy all the advantages of the embedded and updated OpenCore—and with the code cleaned up and redesigned—I tried a clean installation and felt a huge difference. It is really flying, and I am not advertising. The NVMe even dropped in temperature, and I am noticing many improvements, especially a much more responsive Safari. But I did a new installation because the changes are truly modern and up to date. So here is the advice for the future: avoid putting new wine into old wineskins—do a fresh installation.

 

:construction: :superman:

 

Thanks to @Hnanoto @Slice @chris1111 and all developers. ;) 

CapturadeTela2026-01-13s21_24_34.png.8db2ce7bea12b613cf135ea5aa52d0ed.pngCapturadeTela2026-01-13s23_35_26.thumb.png.92bf4b6d919bc637bbda7b966a73ce18.png

 

CapturadeTela2026-01-13s21_13_40.thumb.png.fd186ce5fcab7d745fdb98e8abbe6d09.png

CapturadeTela2026-01-14s00_29_45.thumb.png.7f3d6ab6b5467f957fc1d5508868b5d1.png

 

CapturadeTela2026-01-14s00_28_50.thumb.png.5878ccf9d3d605a8db703a3620b93a92.png

 

 

 

 

 

 

 

Edited by Max.1974
  • Like 2
On 1/13/2026 at 6:14 AM, Hnanoto said:

Essential New Quirks (Sequoia/Tahoe):
DisableIoMapperMapping
: Goodbye Sequoia WiFi/Ethernet issues! VT-d support is now properly handled.
ResizeGpuBars
: Control Resizable BAR (Smart Access Memory) directly in the bootloader. No more disabling it in BIOS and losing Windows performance.

Hi @Hnanoto

Clover official release 5166 has these quirks:

DisableIoMapper
ResizeAppleGpuBars

May i know what differs with your  "New Quirks"?

Should we leave the current Quirks or delete the old and replace it with your new ones?

  • Like 1
8 minutes ago, LockDown said:

Hi @Hnanoto

Clover official release 5166 has these quirks:

DisableIoMapper
ResizeAppleGpuBars

May i know what differs with your  "New Quirks"?

Should we leave the current Quirks or delete the old and replace it with your new ones?

"Hi!

My updates are additions, not replacements. You should keep your current quirks (DisableIoMapper, ResizeAppleGpuBars) if your hardware setup requires them.

What I added is the ClearTaskSwitchBit quirk, which is missing in the official r5166 release. This specific quirk is critical for stability on certain AMD Ryzen CPUs and virtualization scenarios.

I also totally updated the internal OpenCorePkg engine. This brings support for newer CPUs (like AMD Zen 5 / 1Ah Family) and general improvements to the underlying code that powers all quirks.

So, you don't need to delete anything — just use the new options if you need them!"

  • Like 1
  • Thanks 3
3 hours ago, Hnanoto said:

I also totally updated the internal OpenCorePkg engine. This brings support for newer CPUs (like AMD Zen 5 / 1Ah Family) and general improvements to the underlying code that powers all quirks.

Hi Hnanoto

Thanks for your job in clover

Could you explain this part i quoted?

I use 5165 release with a AMD CPU 9950x and X870E platform/chipset

I have a perfect working system with this Clover Release

Which improvments i can have if i update with your latest AMD Zen 5 support?

thank you in advance

  • Like 1
  • Thanks 1
11 hours ago, Hnanoto said:

""Thank you very much! It has been a massive effort to keep Clover updated and fully synced with the latest Acidanthera developments.

In this latest update, I’ve managed to:

Sync OpenCorePkg: Fully updated the submodule to valid commits, fixing macro errors and build dependencies.
New CPU Support: Added the latest CPU definitions, including the AMD 1Ah Family (Zen 5).
Quirks Implementation: Ported the ClearTaskSwitchBit quirk and ensured proper handling of the Unload functionality for drivers.
CI/CD Overhaul: Completely fixed the GitHub Actions pipeline, resolving recursive submodule fetching issues and enabling stable builds with GCC 15.2.
I'm glad to preserve Clover as a powerful and updated bootloader for the community. Please test the latest build — feedback is always welcome!"

Can you pass me the latest version of Clover 5167?
thanks

  • Like 2
8 hours ago, Alpha22 said:

Can you pass me the latest version of Clover 5167?
thanks

As soon as Slice approves the new pull request, you can use it, okay? But if you want to test it from my CloverHackyColor fork, download it from the Artifacts folder; it's version 5166 until Slice approves the PR and releases it, maybe version 5167. link fork https://github.com/hnanoto/CloverBootloader-Hackintosh-and-Beyond

  • Like 2

Hi,
What about the Recovery DMG ( com.apple.recovery.boot ) ?

 

Can you or anyone else boot it?

 

This doesn't work here despite being visible on boot . Try different builds, it doesn't boot .

Tahoe, Sequoia, Sonoma... boot s fine  without any problems.

 

Waiting for your new Merge/Master... in progress.

 

What name should the icon ( Recovery DMG ) in the theme have... os_recovery, os_dmg...?

 

Thanks for your attention.

22 minutes ago, Anto65 said:

Hi,
What about the Recovery DMG ( com.apple.recovery.boot ) ?

 

Can you or anyone else boot it?

 

This doesn't work here despite being visible on boot . Try different builds, it doesn't boot .

Tahoe, Sequoia, Sonoma... boot s fine  without any problems.

 

Waiting for your new Merge/Master... in progress.

 

What name should the icon ( Recovery DMG ) in the theme have... os_recovery, os_dmg...?

 

Thanks for your attention.

The PR has already been accepted by Slice, so in recovery mode the method will appear as shown in the image! The name would be Boot Recovery DMG! To use the method, leave your kexts in the Other folder in kexts because Clover hasn't yet unpacked the DMG that will be installed directly from the Apple server, so Clover doesn't know the macOS version that's in the DMG, okay?

screenshot1.png

  • Like 1

I've always used the "Other" folder for kexts.

 

The Recovery DMG is visible fine

screenshot0.thumb.png.825f1b2169787c1dbe

... but it crashes after a while after launching it.

 

Tried with the Tahoe and Ventura BaseSystem, without success.

 

 

It doesn't reach here... maybe I'm explaining myself badly

factory-reset-macos-tahoe-10.png

 

Spoiler

Screenshot2026-01-14alle18_54_27.png.9028c5e1ca304e3bb18f1ea70d611330.png

 

Edited by Anto65
  • Like 1
3 hours ago, Anto65 said:

Sempre usei a pasta "Other" para kexts.

 

O DMG de Recuperação é visível de forma adequada

screenshot0.thumb.png.825f1b2169787c1dbe

... Mas ele trava depois de um tempo após o lançamento.

 

Tentei com o Tahoe e Ventura BaseSystem, sem sucesso.

 

 

Não chega aqui... talvez eu esteja me explicando mal

factory-reset-macos-tahoe-10.png

 

  Esconder conteúdo

Screenshot2026-01-14alle18_54_27.png.9028c5e1ca304e3bb18f1ea70d611330.png

 

Do you have the logs?

  • Like 1
15 hours ago, fabiosun said:

Hi Hnanoto

Thanks for your job in clover

Could you explain this part i quoted?

I use 5165 release with a AMD CPU 9950x and X870E platform/chipset

I have a perfect working system with this Clover Release

Which improvments i can have if i update with your latest AMD Zen 5 support?

thank you in advance

"Hi there! glad to hear your system is stable.

Even if your 9950x (Zen 5) is booting fine with r5165, here is why this update matters for you:

Native CPU Recognition: The previous Clover versions didn't have the specific CPU definitions for the AMD 1Ah Family (Zen 5). This update adds full native support in the underlying code (OpenCorePkg backend). This means better power management detection and correct topology reporting to macOS, rather than relying on generic fallback codepaths.
ClearTaskSwitchBit Quirk: This is the major fix. On many newer Ryzen platforms, virtualization (running VMs like Parallels/VMware) or certain heavy workloads could cause instability or crashes due to how the CR0 register states are handled during the boot handover. This quirk fixes that at a low level, ensuring rock-solid stability specifically for virtualization and newer instruction sets.
Modernized Engine: We synced the internal OpenCore engine to the absolute latest commit. This brings in silent fixes for newer chipsets (like your X870E) regarding memory mapping and PCIe handling that might not be visible 'on the surface' but prevent edge-case panics in the future.
In short: It makes your "perfect working system" more "natively correct" under the hood and safer for virtualization tasks."

  • Like 3
×
×
  • Create New...