Jump to content
3741 posts in this topic

Recommended Posts

2 hours ago, Stefanalmare said:


You don't need Skip Board ID check for MacPro7,1. Try without ctrsmt=full. I have better benchmark.

 

You have to use Skip Board ID check. But taking in consideration today reality is better MacPro7,1.

@Stefanalmare , dear, I tried ctrsmt=full ,  but it did not improve my geekbench 6 results. Tahoe  has lower CPU and GPU figures than Sonoma/Sequoia,  9.000 vs 14.000 in multi-core CPU and 220.000 vs 240.000 in metal GPU. 

17 minutes ago, dogansan said:

@Stefanalmare , dear, I tried ctrsmt=full ,  but it did not improve my geekbench 6 results. Tahoe  has lower CPU and GPU figures than Sonoma/Sequoia,  9.000 vs 14.000 in multi-core CPU and 220.000 vs 240.000 in metal GPU. 

 

"Try without ctrsmt=full."

@MorenoAv i will see your EFI now brother, sorry late ;) 

 

 

1 hora atrás, chris1111 disse:

Creative Sound Blaster PLAY! 3, Amplificador USB DAC e Placa de Som Externa

Perfeito

imagem.png.220aac179c078abcbba9ed644ad51e20.png

 

imagem.png.e26fedd408c14513fe4caf0fba397f4e.png

 

image.thumb.png.2de08806b3f3c656a127f223618ce40f.png

 

Awesome my friend, I remember a long time ago the many sound cards !! 😃 

 

Available on Amazon ;) 

 

 

image.thumb.jpeg.7bea09e17980c056a20b28bce66a5520.jpeg

Some people are just born under a lucky BIOS.

Last year, since I had no real use for two PCs, I generously donated my “old” rig to a friend—Z490 Gigabyte G, 10700K, 5700XT. Not junk, just gently retired.

Fast forward to yesterday, the guy shows up like it’s Christmas morning and asks, “Hey, can you install macOS on it?”

I looked him dead in the eye and said, “Absolutely not. I’m not emotionally prepared to relive the Tahoe Trauma™.”

 

But the man is a Grade-A sweet talker. Before I knew it, I’m sitting there muttering “Just one EFI… just to see.”

Whipped up an EFI folder in under 5 minutes. Tossed in the essentials—some .aml’s, kexts, nothing fancy.

No DeviceProperties, no patching, no voodoo. Fully expecting a kernel panic or at least a dramatic black screen.

 

Plugged my Tahoe SSD into his PC.

Booted from the EFI.

And that cursed machine… booted perfectly. First try. No errors. Like it was born to run macOS.

 

I was so mad. Shut the thing off, yanked my SSD like a dramatic ex, and told him, “Don’t call me. Don’t text me. Not for a week. I need to process this betrayal.”

 

Here is the EFI. I havent tried to use it for installation but it boots perfectly to installed Tahoe.

EFI.zip

  • Like 1
  • Haha 5
4 hours ago, ANTIKO said:

I tried all the combinations that came to my mind. and with and without WhateverGreen, and NootRX and without it. I can't figure out what the problem is, I've been fighting for 3 days. maybe someone will look from the side and see what I don't see?

I downloaded the installer twice, changed the USB ports. kexit used to change Openkore, a long time ago I came across a similar error - the solution was so elementary that I forgot😀

Has the procedure for creating a flash drive with the installer changed? compared to Sequoia?

opencore-2025-06-28-071132.txt 256 kB · 5 downloads config.plist 60.48 kB · 6 downloads

try config.plist, do not use WhateverGreen.kext

from the signature you use I5 13660KF from the config.plist it is marked as I9

 

config.plist.zip

Edited by Alpha22
  • Like 1
  • Thanks 1

@chris1111  @PoMpIs  

 

Tried succesfully the Sound Blaster Play! 3, good quality sound, works OOCB on Tahoe (of course in Ventura - Sonoma - Sequoia too).

Only (small) drawback: when playing music, CPU load is a bit higher than with the motherboard's ALC chip, as expected, but it is a completely acceptable difference.

  • Like 4

@eSaF  @Anto65

 

Dear friends, I've finally been able to work on the EFI that works for both root-patched Sequoia and Tahoe.


@eSaF settings boot Sequoia fine, but not Tahoe. I had to make some small changes:

  • In Kernel >> Add, where Esaf has MaxKernel = 25 (Tahoe won't boot), I set MaxKernel = 24.20.0 (20 is a number chosen to be higher than future versions of Sequoia. 24.99.99 also works, as some users do in cases like this).
  • In Kernel >> Block, where Esaf has no MaxKernel value (Tahoe won't boot), I set MaxKernel = 24.20.0 as well.

MinKernel = 24.0.0, which I left unchanged.


With this, the EFI can boot both root-patched Sequoia (Fenvi Wi-Fi) and Tahoe fine.


I then set MinKernel = 23.0.0 (no other changes) to boot with the same EFI on Ventura, Sonoma (root patched), Sequoia (root patched), and Tahoe beta 2.


Thanks, friends!

 

Spoiler

Kernel-add.thumb.png.8593c339343b893939b3e3b6d35cd025.png

 

Kernel-block.thumb.png.a3b8c9b7c0dc340b94ae08cbefb3b8de.png

 

 

Edited by miliuco
Fix typo
  • Like 4

@MorenoAv try this EFI, I check that your config.plist has many differences, specially Kernel Quirks and missing some SSDTs like HPET. 

 

ResetNvram first ok? ;) 

 

EFI-MorenoAV-Test1.zip

 

5 hours ago, ANTIKO said:

I tried all the combinations that came to my mind. and with and without WhateverGreen, and NootRX and without it. I can't figure out what the problem is, I've been fighting for 3 days. maybe someone will look from the side and see what I don't see?

I downloaded the installer twice, changed the USB ports. kexit used to change Openkore, a long time ago I came across a similar error - the solution was so elementary that I forgot😀

Has the procedure for creating a flash drive with the installer changed? compared to Sequoia?

opencore-2025-06-28-071132.txt 256 kB · 5 downloads config.plist 60.48 kB · 6 downloads

If you can post your hardware info and EFI its more easy to check ;) thks 

Reading the past few posts about the Broadcom WiFi and the Audio and probably few other hardware components being dropped by Apple in macOS Tahoe, Hackintosh term might need to be redefined as Frankentosh because it seems we need to create a Frankenstein's monster to be able to run Tahoe on our beloved Hacks! :hysterical:

 

  • Haha 5

hi im, having a bit of problem with my Lenovo m720q.

Sequoia all good I updated kexts and opncore new install but no audio.

If I install voodoohda I get sound if not nothing I tried both beta1 and beta 2 no diffrence

Wtf........  

 

Screenshot 2025-06-28 at 19.39.08.png

config.plist

  • Like 1
1 hour ago, miliuco said:

@eSaF  @Anto65

 

Dear friends, I've finally been able to work on the EFI that works for both root-patched Sequoia and Tahoe.


@eSaF settings boot Sequoia fine, but not Tahoe. I had to make some small changes:

  • In Kernel >> Add, where Esaf has MaxKernel = 25 (Tahoe won't boot), I set MaxKernel = 24.20.0 (20 is a number chosen to be higher than future versions of Sequoia. 24.99.99 also works, as some users do in cases like this).
  • In Kernel >> Block, where Esaf has no MaxKernel value (Tahoe won't boot), I set MaxKernel = 24.20.0 as well.

MinKernel = 24.0.0, which I left unchanged.


With this, the EFI can boot both root-patched Sequoia (Fenvi Wi-Fi) and Tahoe fine.


I then set MinKernel = 23.0.0 (no other changes) to boot with the same EFI on Ventura, Sonoma (root patched), Sequoia (root patched), and Tahoe beta 2.


Thanks, friends!

 

  Reveal hidden contents

Kernel-add.thumb.png.8593c339343b893939b3e3b6d35cd025.png

 

Kernel-block.thumb.png.a3b8c9b7c0dc340b94ae08cbefb3b8de.png

 

 

 

In my case I tried
both with 23.0.0 > 24.0.0
or
23.0.0 > 24.99.99

Block only Min 23.0.0

It always Boot all OS

  • Like 1
28 minutes ago, robi62 said:

hi im, having a bit of problem with my Lenovo m720q.

Sequoia all good I updated kexts and opncore new install but no audio.

If I install voodoohda I get sound if not nothing I tried both beta1 and beta 2 no diffrence

Wtf........  

 

Screenshot 2025-06-28 at 19.39.08.png

config.plist 61.7 kB · 1 download


With A348 you need to use FakePCIID.kext and FakePCIID_Intel_HDMI_Audio.kext min kernel 25.0.0 if you use voodoohda in Tahoe and applealc in sequoia max kernel 24.99.99. If it doest work with voodoohda 302, try lower versions. If you'll use voodoohda everywhere no need min/max kernel (also you can spoof audio).

9 hours ago, Cyberdevs said:

You're welcome :)

If the system is stable with DisableIoMapper disabled, that's a good idea to find another way to enable the ethernet, in my case I have to use two SSDTs for my 10 Gbps ethernet to work. (SSDT-Aquantia-AQC113C.aml and DTPG.aml), but I'm not sure what options are available for your 2.5Gbps ethernet.

Yeah. I'm a stupid old man. After disabling the disableiomapper, removing IGC kext, taking out the e 1000 boot arg, commenting out the ethernet entry in device properties it now works, is stable and shows up correctly in hackintool.

Intel I225-V is natively supported in Tahoe.

Everything is working well except wifi (Next step is to wait for OCLP but I don't really use wifi anyway so it's not a biggie).

Oddly in hackintool on Tahoe all my USBs show up from my mapping but in Sequoia they don't, even though they all work.

Thanks for the tip around the iomapper instability which led me down that track! And thanks all you guys for your help and patience :)

Here's an EFI for reference.

Asus Z690-I and RX6800, broadcom card.

Geekbench6 CPU 2524/11554, Metal 171522.

EFI_ASUS _Z690.zip

  • Like 5
32 minutes ago, robi62 said:

@Stefanalmare Dont really Want to use voodoohda as I dont get sound through hdmi It just seem weird out of all hacks this one is giving me headacke


Whatever! 8086 A348 need to be spoofed to work with voodoohda.

If you are confused @robi62 read this: https://github.com/RehabMan/OS-X-Fake-PCI-ID

In Sequia look at hackintool/sound and you'll see something about necessity to spoof.

Edited by Stefanalmare
  • Like 1
  • Confused 1
15 hours ago, surenmunoo said:

Time to start surgery. I got a potential buyer for my Asus Z890 ProArt and just picked up the Gigabyte Z890 Top AI. Time to transplant and hope macOS works especially Tahoe. Wish me luck, time to go under :robot:

Surgery has been completed and is a success thanks to @MaLd0n WHo has come to the rescue again. Got my macOS up and running. The Gigabyte board took much less time to get it booting to Tahoe, Sequoia as what the Asus ProArt did. Thanks again @MaLd0n

  • Like 2
48 minutes ago, Stefanalmare said:


Whatever! 8086 A348 need to be spoofed to work with voodoohda.

If you are confused @robi62 read this: https://github.com/RehabMan/OS-X-Fake-PCI-ID

In Sequia look at hackintool/sound and you'll see something about necessity to spoof.

Ok so I can only use voodoohda ??

  • Like 1
23 minutes ago, eSaF said:

All this cash being splash around on high end boards that will see the last of a new Apple OS is remarkable.

If there is all this cash about, maybe I should consider coming out of retirement and try to get my share as well. :lol:

 

Since it's going to be the last Hackintosh, might as well go out in Style EH :euro: I also need a good video processing PC for the Mavic 4 videos. The M2 Mac Studio struggles editing the footage. 

  • Like 2
11 minutes ago, Stefanalmare said:

 

Yes, with FakePCIID.kext and FakePCIID_Intel_HDMI_Audio.kext. Or without but spoofed.

Seems complicated apart of  the kext you have to spoof it too I might have to ask my tech friend for it

Edited by robi62
19 minutes ago, eSaF said:

Bro can you please stop flexing your toys on me. :lol:

The wife put a halt on my spending at the Mini and the Mavic Pro.

 

I am well over due for a big cash splurge.

Spoilt for choice, what do you think.

 

I maybe in the market for a genuine Mac.

Lack of being able to tinker put me off the idea. ;)

My favourite tinkering hackintosh was my first - an X58 with a xeon cpu. As well as MacOS I could tinker with overclocking it. I only upgraded because of the really slow pcie lanes and so a slow SSD. So get one of those off ebay to tinker with and also get a real mac. Go for the EVGA dual CPU one (classified SR2) for double the tinkering.

Edited by surfinchina
Guest
This topic is now closed to further replies.
×
×
  • Create New...