Jump to content
3741 posts in this topic

Recommended Posts

20 hours ago, strangeron said:

VoodooHDA is a good solution. However, I have Ventura, Sequoia and Tahoe with the same EFI. If I remove AppleALC.kext I will have to install VoodooHDA on all of them. So I looked for another solution.😂

Try using Min/Max kernel settings for AppleALC.kext.

If you limit the the Max setting to 24.9.9 it won't load in Tahoe and you can use VoodooHDA just for Tahoe.

 

image.thumb.png.da5893ad0742dbda55e214814e5ce883.png

  • Like 3
  • Thanks 1
1 hour ago, Cyberdevs said:

Try disabling DisableIoMapper in Kernel -> Quirks, on my Z690 rig when I enable DisableIoMapper it shows the same behavior.

Thanks :)

I just lose ethernet when I do that. Got the 1225-V. I'll try to find another way to get that working.

  • Like 1

Hey guys!

 

I was just wondering (and, in my case, it is related to Tahoe, but it's also more of a general question): if someone would want to learn how to do device properties patching the right way, where would they go? Is there a tutorial on that somewhere? More like a book maybe? :)) I tried to search the forum for something like that, but I couldn't find it.

 

I know it will be different stuff, different patches, depending on what you're trying to patch. But still, I'm more interested in the general workflow. I mean, what kind of information do you need to add? Where would you get that information? For example, do I still need to patch device properties for my RX 580 if I'm using WEG? Do they conflict with each other? Can I achieve full functionality only with device properties? When should someone patch device properties, and why? Is it just "cosmetic"? Or is it also functional? (My guess is that it's probably both.) What are the best practices when doing something like this? And stuff like that.

 

Do we already have a topic dedicated to this? If so, can someone please point me to it? Or is there another resource online I can use to learn more about it? 

Edited by arsradu
  • Like 2
34 minutes ago, surfinchina said:

Thanks :)

I just lose ethernet when I do that. Got the 1225-V. I'll try to find another way to get that working.

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.

2 hours ago, Montblanc said:

Try using Min/Max kernel settings for AppleALC.kext.

If you limit the the Max setting to 24.9.9 it won't load in Tahoe and you can use VoodooHDA just for Tahoe.

Thanks. For now, I solved the sound problem with the USB sound card. But I am backing up this solution. Thanks again for the information.

  • Like 2
2 hours ago, arsradu said:

Hey guys!

 

I was just wondering (and, in my case, it is related to Tahoe, but it's also more of a general question): if someone would want to learn how to do device properties patching the right way, where would they go? Is there a tutorial on that somewhere? More like a book maybe? :)) I tried to search the forum for something like that, but I couldn't find it.

 

I know it will be different stuff, different patches, depending on what you're trying to patch. But still, I'm more interested in the general workflow. I mean, what kind of information do you need to add? Where would you get that information? For example, do I still need to patch device properties for my RX 580 if I'm using WEG? Do they conflict with each other? Can I achieve full functionality only with device properties? When should someone patch device properties, and why? Is it just "cosmetic"? Or is it also functional? (My guess is that it's probably both.) What are the best practices when doing something like this? And stuff like that.

 

Do we already have a topic dedicated to this? If so, can someone please point me to it? Or is there another resource online I can use to learn more about it? 


Hi my friend. We are at the same boat. I need said that people who have knowledge advanced not share at all. I try use my little knowledge to search for GitHub pages, another forums and using ChatGPT. This is sad 😞 but the true story for all beginners and more advanced hackintoshers. We not have a book. Need search and save for years. 

  • Like 4

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 config.plist

Edited by ANTIKO
  • Like 2
On 6/27/2025 at 11:38 AM, dogansan said:

Do you mean you did run Tahoe with iMacPro1.1.  I was told it is incompatible . Would you mind to share your EFI ?

Any comment or help is appreciated on how you could run Tahow with iMacPro1.1

8 minutes ago, eSaF said:

@ANTIKO Good day Bro,

CPU is definitely not supported by Mac.

 

Thanks, but Tahoe supports Mac Pro 7.1, there's no video core either. I will definitely study the link. In the meantime, I'll be sitting on the riverbank.

23 minutes ago, dogansan said:

Any comment or help is appreciated on how you could run Tahow with iMacPro1.1

I don't know what kind of error you are getting. However, Booter/Patch is sufficient for installation with imacPro 1.1.

image.png

  • Like 1
9 hours ago, Max.1974 said:


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

36 minutes ago, dogansan said:

Any comment or help is appreciated on how you could run Tahow with iMacPro1.1

 

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

Edited by Stefanalmare
  • Like 2
  • Thanks 1

Just used the BOOTCAMP Assistant and partitioned my 1TB NVME from Samsung 980 Pro to 350GB (macOS Tahoe Beta 2) and 650GB to my Windows 11 25H2.

 

In my first try it not installed windows and give me an error over Windows 11 Installer, changed a bit in Bios and voila Windows 11 25H2 started the installer and I was able to install Windows without any issues...

 

Now I had both systems in dual boot with OC 1.0.5.

 

I´m installing Forza Motor Sport 7 witch has 99GB and eFootball (78GB) - Speaking from windows with you guys...

 

Nice Graphics Card everything on Ultra 4K HDR, and was smooth..

 

DS4Windows + my PS4 controller.

And my G920 Wheel with Shifter 6 gears manual.

Working Like a charm.

 

Regards,

Fernando.

Edited by fernando.c.neves
  • Like 1

Aaa little games of a few mb 🤭

I would have used WindowsInstall.app (you can find it here on ( sergeygalan ) IM ... I'm not at the PC right now)
No bootcamp needed

no need to create a bootable USB
enable in the app No Esp and it does not overwrite the OC boot, it will only place the Microsoft directory in Efi

Edited by Anto65
  • Like 4

Good day to all,

Yesterday pissed at the lack of network and my inability to make it work I decide to reinstall Tahoe, at the reboot I'm confronted with the inability of the general EFI from Olaria to boot the installer. Ater that I have used all EFI's that are laying around to try and install Tahoe, with no success.

i made and EFI from scratch and it boots the system until it arrives at this part and the installion stops.

Could anyone see the above picture and point me in the right direction.

thanks

IMG_0922.jpg

EFI.zip

Edited by MorenoAv
  • Like 2
  • Sad 1

Enable IGPU and -wegnoegpu boot-arg. HDMI to MB. BIOS first boot IGPU. After install, return all. I assume you have another MacOS installed. Do it from there. If you can boot to working MacOS with IGPU main, you can install also Tahoe.

For IGPU use this:
<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
                <dict>
                    <key>#AAPL,ig-platform-id</key>
                    <data>AwCSPg==</data>
                    <key>#disable-external-gpu</key>
                    <data>AQAAAA==</data>
                    <key>#hda-gfx</key>
                    <string>onboard-1</string>
                    <key>#igfxfw</key>
                    <data>AgAAAA==</data>
                    <key>#rps-control</key>
                    <data>AQAAAA==</data>
                    <key>AAPL,ig-platform-id</key>
                    <data>BwCbPg==</data>
                    <key>AAPL,slot-name</key>
                    <string>Internal@0,2,0</string>
                    <key>device-id</key>
                    <data>kj4AAA==</data>
                    <key>device_type</key>
                    <string>Display controller</string>
                    <key>enable-hdmi20</key>
                    <data>AQAAAA==</data>
                    <key>framebuffer-con0-enable</key>
                    <data>AQAAAA==</data>
                    <key>framebuffer-con0-pipe</key>
                    <data>EgAAAA==</data>
                    <key>framebuffer-con0-type</key>
                    <data>AQAAAA==</data>
                    <key>framebuffer-con1-busid</key>
                    <data>AgAAAA==</data>
                    <key>framebuffer-con1-enable</key>
                    <data>AQAAAA==</data>
                    <key>framebuffer-con1-pipe</key>
                    <data>EgAAAA==</data>
                    <key>framebuffer-con1-type</key>
                    <data>AAgAAA==</data>
                    <key>framebuffer-con2-busid</key>
                    <data>BAAAAA==</data>
                    <key>framebuffer-con2-enable</key>
                    <data>AQAAAA==</data>
                    <key>framebuffer-con2-pipe</key>
                    <data>EgAAAA==</data>
                    <key>framebuffer-con2-type</key>
                    <data>AAgAAA==</data>
                    <key>framebuffer-patch-enable</key>
                    <data>AQAAAA==</data>
                    <key>framebuffer-unifiedmem</key>
                    <data>AAAAgA==</data>
                    <key>model</key>
                    <string>Intel CoffeeLake-S GT2 [UHD Graphics 630]</string>
                </dict>

Edited by Stefanalmare
  • Like 3
6 minutes ago, MorenoAv said:

Good day to all,

Yesterday pissed at the lack of network and my inability to make it work I decide to reinstall Tahoe, at the reboot I'm confronted with the inability of the general EFI from Olaria to boot the installer. Ater that I have used all EFI's that are laying around to try and install Tahoe, with no success.

i made and EFI from scratch and it boots the system until it arrives at this part and the installion stops.

Could anyone see the above picture and point me in the right direction.

thanks

IMG_0922.jpg

EFI.zip 5.41 MB · 0 downloads

I just posted it for you, but the same thing was happening to me. The solution is to create an installation USB with the default IGPU active and the Radeon graphics disabled via OpenCore.

 

revpatch=sbvmm  -lilubetaall -alcbeta -wegbeta -wegnoegpu

  • Like 3
38 minutes ago, kaoskinkae said:

I just posted it for you, but the same thing was happening to me. The solution is to create an installation USB with the default IGPU active and the Radeon graphics disabled via OpenCore.

 

revpatch=sbvmm  -lilubetaall -alcbeta -wegbeta -wegnoegpu

Following your advice it stops here, again...

IMG_0923.jpg

  • Sad 1
15 minutes ago, chris1111 said:

Creative Sound Blaster PLAY! 3, USB DAC Amp and External Sound Card

Perfect

image.png.220aac179c078abcbba9ed644ad51e20.png

 

Cool @chris1111 

Honestly, I've connected a sound card to the USB port, but I'm getting no sound from my laptop's internal speakers on macOS 26. And I don't have any external speakers, just Bluetooth. 😁

  • Like 1
2 hours ago, strangeron said:

I don't know what kind of error you are getting. However, Booter/Patch is sufficient for installation with imacPro 1.1.

image.png

 

I used the the booter/patch as recommended by you. I then was able to boot into Sonoma as iMacPro1.1 once , but it booted Tahoe as MacPro7.1 ,  not iMacPro1.1 More interesting thing is it did not boot as iMacPro1.1 in my later attempts to Sonoma/Sequoia and Tahoe. 

Edited by dogansan
1 hour ago, MorenoAv said:

Good day to all,

Yesterday pissed at the lack of network and my inability to make it work I decide to reinstall Tahoe, at the reboot I'm confronted with the inability of the general EFI from Olaria to boot the installer. Ater that I have used all EFI's that are laying around to try and install Tahoe, with no success.

i made and EFI from scratch and it boots the system until it arrives at this part and the installion stops.

Could anyone see the above picture and point me in the right direction.

thanks

IMG_0922.jpg

EFI.zip 5.41 MB · 2 downloads

Try with this EFI, is universal...

 

 

  • Like 2
  • Haha 1
Guest
This topic is now closed to further replies.
×
×
  • Create New...