Jump to content
3741 posts in this topic

Recommended Posts

4 hours ago, MorenoAv said:

@fernando.c.neves why dot have all the tools showing at boot, how do I shut them down?

And another question, why the boot is so slow, and we can't move the cursor of the mouse, or moving the cursor normally?

Thanks for your help

CapturadeTela2025-06-29s22_50_36.thumb.png.fd7bd802c19254bf295ea710e273118d.png

First things first... In Devices (List) PciRoot.......... every single one of these, delete. After click in List of PCI Devices and Add All PCI Devices.

Then Delete the two devices related to your Graphics card (VGA and HDMI Audio) the rest let as they are.

 

Save config.plist and reboot... All troubles will be solved... I guess is that.

 

Tools can be disable with OpenCore Configurator. (Misc section => Tools)

 

Link to download OpenCore Configurator...

 

https://mackie100projects.altervista.org/download/occ/?wpdmdl=811&refresh=6861b8fd3e0921751234813

 

My boot for Tahoe Beta 2 is at least 5 to 8sec...

 

Regards,

Fernando.

  • Like 3
  • Thanks 1
20 hours ago, jsl said:

After struggling for about 4 weeks at last my ASUS PRIME Z690-P D4 Hackintosh can boot Tahoe beta 2 with RX570 now !

No such issues of Finder, Firefox, LucyRTL8125Ethernet or Audio output.

The only problem waiting for fix is unable to wake-up from S3 sleep.

[Edit]

It seems FL1100 USB 3.0 adapter may interfere its power management of MB.

After removal of it and modified my config-new.plist it can wake-up from S3 sleep now !

 

 

 

 

 

config.plist 24.77 kB · 14 downloads

config-new.plist 25.82 kB · 0 downloads

I have this same motherboard and cannot get Tohoe's setup to load.  Do you mind sharing your EFI folder?

  • Like 2

DIY version for Audio fix with beta 1 Apple HDA

 

Spoiler

Screenshot2025-06-30at10_56_48.thumb.png.11d9ebf5f6dce09aaf57371fc7883be5.png

 

https://github.com/aryajuanda/OpenCore-Legacy-Patcher/blob/main/RUN-MODE.md

 

Note : its use OCLP root patching, so all root patch requirement needed, it can be use for revert root patch also 

its run on terminal for personal use only (its use debug mode for privilege helper so we can do root patch), not gonna build it and publish the app  

Edited by arya
  • Like 3

Hey guys,

 

Posting this from my own experience with Beta 2, in case it helps anyone.

 

FileVault encryption: it was turned on automatically, but only when upgrading from Sequoia. For the fresh installation, and at least in my case, it wasn't.

Upgrade process (from Sequoia to Tahoe): with WEG enabled, I was getting stuck while loading. Disabled it, and I was able to move forward with the upgrade process and finished successfully with the RX580.

 

Also, I was just wondering, if you already have your FileVault support configured in config, would you still have issues with Tahoe? I tried to enable it on one of the two partitions running it and I couldn't. I get a prompt with the recovery key, for a second, and then a blank pop-up with no information. Could be a bug, could be something else. But I was just curious: if you already have FV configured in config, do you still need to worry about Tahoe enabling FV during installation? Or would it just work like you would expect?

  • Like 4
2 minutes ago, arsradu said:

Hey guys,

 

Posting this from my own experience with Beta 2, in case it helps anyone.

 

FileVault encryption: it was turned on automatically, but only when upgrading from Sequoia. For the fresh installation, and at least in my case, it wasn't.

Upgrade process (from Sequoia to Tahoe): with WEG enabled, I was getting stuck while loading. Disabled it, and I was able to move forward with the upgrade process and finished successfully with the RX580.

 

Also, I was just wondering, if you already have your FileVault support configured in config, would you still have issues with Tahoe? I tried to enable it on one of the two partitions running it and I couldn't. I get a prompt with the recovery key, for a second, and then a blank pop-up with no information. Could be a bug, could be something else. But I was just curious: if you already have FV configured in config, do you still need to worry about Tahoe enabling FV during installation? Or would it just work like you would expect?

 

update from beta 1 to beta 2 will also trigger the automatic FileVault to enable... so prepare for next update.. make are to disable it again on first boot.. 

  • Like 4
11 minutes ago, arya said:

 

update from beta 1 to beta 2 will also trigger the automatic FileVault to enable... so prepare for next update.. make are to disable it again on first boot.. 

I guess it makes sense. If there is user data to be encrypted, then it triggers FileVault. If not, and it's just the OS, then it doesn't. I still wish Apple would add a button to Skip/Reject FV Encryption during installation.

 

I disabled it now...but it's kind of a pain in the rear to always having to disable what you don't want enabled in the first place.

 

Personally I didn't have any issues with FV since, after the upgrade, I waited for FV to complete encryption, just to turn it Off again.

 

But the question remains: assuming everything is set up properly for FV...should we even worry about it? I mean, yeah, it's annoying if you don't want it enabled. But if you don't mind, or if you do want it enabled, will it work...?

 

Edit: I just remembered this now. On my MBP M1, FV was indeed turned on by default when upgrading from Sequoia, but I don't remember having to disable it (and it's not enabled now) with the upgrade to Beta 2... Hmm...interesting. So it did enable it on the first time, but it also remembered I don't want it, and did not re-enable it when upgrading from Beta 1 to Beta 2.

Maybe it's just the hacks then...? Donno. I guess we'll see with the next update. :D

Edited by arsradu
  • Like 2
12 minutes ago, arsradu said:

Hey guys,

 

Posting this from my own experience with Beta 2, in case it helps anyone.

 

FileVault encryption: it was turned on automatically, but only when upgrading from Sequoia. For the fresh installation, and at least in my case, it wasn't.

Upgrade process (from Sequoia to Tahoe): with WEG enabled, I was getting stuck while loading. Disabled it, and I was able to move forward with the upgrade process and finished successfully with the RX580.

 

Also, I was just wondering, if you already have your FileVault support configured in config, would you still have issues with Tahoe? I tried to enable it on one of the two partitions running it and I couldn't. I get a prompt with the recovery key, for a second, and then a blank pop-up with no information. Could be a bug, could be something else. But I was just curious: if you already have FV configured in config, do you still need to worry about Tahoe enabling FV during installation? Or would it just work like you would expect?

 

Only for my Lenovo happens that with OTA Upgrade / Update FV is enable. With my Hacks using OTA or "fresh" install or command from scratch, never happens...my B360 + RX 580 Sapphire 4GB USB installer without WEG and after install no need use too, is working like a charme. Without WEG. Running OCLP-Mod fine, all doing good. 

  • Like 1
1 minute ago, arsradu said:

I guess it makes sense. If there is user data to be encrypted, then it triggers FileVault. If not, and it's just the OS, then it doesn't. I still wish Apple would add a button to Skip/Reject FV Encryption during installation.

 

I disabled it now...but it's kind of a pain in the rear to always having to disable what you don't want enabled in the first place.

 

Personally I didn't have any issues with FV since, after the upgrade, I waited for FV to complete encryption, just to turn it Off again.

 

But the question remains: assuming everything is set up properly for FV...should we even worry about it? I mean, yeah, it's annoying if you don't want it enabled. But if you don't mind, or if you do want it enabled, will it work...?

the problem is if FileVault enable we can't enter the desktop and our password will not work... its quite hard to disable FileVault from recovery

  • Like 3
14 minutes ago, arya said:

the problem is if FileVault enable we can't enter the desktop and our password will not work... its quite hard to disable FileVault from recovery

Yeah, but does this occur even with everything properly set up for FV in OC Config? This is my question. :) 

For reference, this is what I'm talking about. 

15 minutes ago, Max.1974 said:

 

Only for my Lenovo happens that with OTA Upgrade / Update FV is enable. With my Hacks using OTA or "fresh" install or command from scratch, never happens...my B360 + RX 580 Sapphire 4GB USB installer without WEG and after install no need use too, is working like a charme. Without WEG. Running OCLP-Mod fine, all doing good. 

Yeah, I had the same experience. All good without WEG, but stuck in installation with it. :)) The only thing (and I know it's just cosmetic, but still wondering if you, or other RX4xx/RX5xx users are encountering the same thing) is right before the Desktop comes up, there are a few horizontal purple lines displayed on the upper side of the screen. For me, WEG gets rid of that and it was one of the reasons I was using it.


Do you have those too? Or do you know of another fix that doesn't involve using WEG kext?

Edited by arsradu
  • Like 3
18 minutes ago, arsradu said:

Yeah, but does this occur even with everything properly set up for FV in OC Config? This is my question. :) 

For reference, this is what I'm talking about. 

Yeah, I had the same experience. All good without WEG, but stuck in installation with it. :)) The only thing (and I know it's just cosmetic, but still wondering if you, or other RX4xx/RX5xx users are encountering the same thing) is right before the Desktop comes up, there are a few horizontal purple lines displayed on the upper side of the screen. For me, WEG gets rid of that and it was one of the reasons I was using it.


Do you have those too? Or do you know of another fix that doesn't involve using WEG kext?

 

in my opinion, I think it need update in the OC to work with new FileVault, some say its need apfs_aligned.efi to fix the FV, its added in https://github.com/acidanthera/OcBinaryData now

Edited by arya
  • Like 3
  • Thanks 1
13 hours ago, Stefanalmare said:

 

Genuine iMacPro1,1 has MCHC. MacPro7,1 doesn't. ADBG to XDBG it was a fix made by @Casey to fix sleep in certain BIOS release. For me, with next BIOSs it was not necessary.

Exactly, for the moment I am not updating the bios because the PC behaves well using these patches

  • Like 2
21 minutes ago, arya said:

 

in my opinion, I think it need update in the OC to work with new FileVault, some say its need apfs_aligned.efi to fix the FV, its added in https://github.com/acidanthera/OcBinaryData now

Cool! Thank you! I didn't know about this.

  • Like 1
3 hours ago, fernando.c.neves said:

CapturadeTela2025-06-29s22_50_36.thumb.png.fd7bd802c19254bf295ea710e273118d.png

First things first... In Devices (List) PciRoot.......... every single one of these, delete. After click in List of PCI Devices and Add All PCI Devices.

Then Delete the two devices related to your Graphics card (VGA and HDMI Audio) the rest let as they are.

 

Save config.plist and reboot... All troubles will be solved... I guess is that.

 

Tools can be disable with OpenCore Configurator. (Misc section => Tools)

 

Link to download OpenCore Configurator...

 

https://mackie100projects.altervista.org/download/occ/?wpdmdl=811&refresh=6861b8fd3e0921751234813

 

My boot for Tahoe Beta 2 is at least 5 to 8sec...

 

Regards,

Fernando.

I use your EFI but I have to modify several parts to successfully boot into the installation screen. Then remove this part -radvesa and add this part Devices (List) PciRoot to access the desktop screen.
https://www.insanelymac.com/forum/topic/361162-pre-release-macos-tahoe/page/81/#findComment-2835464
But the bigger problem that I can't fix is that when I use it for 5-10 minutes, it will always reset itself. Especially when I open Google Chrome, it will restart itself faster than others. Does anyone else have the same problem as me?

  • Like 1
1 hora atrás, arsradu disse:

Sim, mas isso ocorre mesmo com tudo configurado corretamente para FV no OC Config? Esta é a minha pergunta.:) 

Para referência, é disso que estou falando.

Sim, eu tive a mesma experiência. Tudo bem sem WEG, mas preso na instalação com ele. :)) A única coisa (e eu sei que é apenas cosmético, mas ainda me pergunto se você, ou outros usuários de RX4xx/RX5xx estão encontrando a mesma coisa) é que logo antes do Desktop aparecer, há algumas linhas roxas horizontais exibidas no lado superior da tela. Para mim, a WEG se livra disso e foi uma das razões pelas quais eu estava usando.


Você também tem isso? Ou você conhece outra correção que não envolva o uso de WEG kext?

Yes, I do get some small purple artifacts, but they don’t affect the usability of my Sapphire RX 580. I haven’t tested with WEG because everything works fine without it, and it’s actually my wife’s and daughter’s Hackintosh — I just set it up that way. Great operating system  ;) 

Edited by Max.1974

I installed Tahoe with RX570 as only card and all is fine with Clover and without WhateverGreen.

I encounter same FileVault problem. I can't enter password until encoding is finished. Now I can and I can use the encrypted system.

But I encounter a new problem and I want to ask here if anyone else see this.

My HDD said "clack-clack and stopped". I decided it is dead and bought new one. It also said "clack-clack..."

I rebooted into Sequoia and see all HDDs are very good. 

  • Like 3
  • Sad 1
27 minutos atrás, eSaF disse:

Bom dia Bud, minha própria experiência instalando o Tahoe RX580 como placa principal, as linhas roxas não estão lá, mas a instalação fica pendurada sem avançar.

Desativando o WEG kext, a instalação progride, mas inicia em uma tela preta. Para combater isso, tive que usar os gráficos da CPU como fonte principal com o plugue do cabo D/P removido do RX580 e conectado à porta de exibição da CPU.

 

A outra etapa também teve que ser definir a exibição de gráficos dedicados para Integrado nas configurações de salvamento do BIOS.

Na inicialização, a instalação seria concluída com sinal de vídeo para o monitor.

 

A situação louca é que eu posso então trazer o RX580 de volta on-line como o cartão principal com todas as alterações necessárias e tudo seria bom carregar e inicializar.

Então, por que o RX580 é problemático inicialmente em Tahoe, fazer uma instalação limpa é um mistério para mim.

 

Eu tentei uma instalação limpa com o primeiro Beta e todos vocês conhecem minha jornada traumática com esse.

Tentei uma instalação limpa com o Beta 2 e a situação não mudou, tive que seguir a rota da CPU Graphics primeiro e depois trazer o RX580 na linha.

 

Tentarei novamente com o próximo Beta quando um link for fornecido para um D/Load para construir um USB de instalação.

Tahoe está definitivamente jogando duro para conseguir.;)

 

 

 

 

@eSaF are you using DP or HDMI? I used DP form Corsair 27" Monitor, mouse looping left 25 - 30 min run install and them turn back once run more 10 min and get logon screen normally without FV 

 

 

3 minutos atrás, Slice disse:

Instalei o Tahoe com RX570 como único cartão e está tudo bem com o Clover e sem o WhateverGreen.

Eu encontro o mesmo problema do FileVault. Não consigo inserir a senha até que a codificação seja concluída. Agora eu posso e posso usar o sistema criptografado.

Mas eu encontro um novo problema e quero perguntar aqui se mais alguém vê isso.

Meu HDD disse "clack-clack e parou". Eu decidi que está morto e comprei um novo. Também dizia "clack-clack..."

Eu reiniciei o Sequoia e vejo que todos os HDDs são muito bons.

 

Hi my friend, I think HDD its not compatible yet ;)  are you get some special config to use FakeSMC in Clover ? I could not boot ... but if I can will change for Clover. Using 5162 and trying last of your build from FakeSMC - Thanks !! 

29 minutes ago, eSaF said:

Good Day Bud, my own experience installing Tahoe RX580 as main card, the purple lines are not there but the installation hangs without moving forward.

Disabling WEG kext the install progresses but boots to a black screen. To combat this, I had to use the CPU Graphics as the main source with the D/P cable plug removed from the RX580 and plugged into the CPU display port.

 

The other step also had to be set the display from dedicated graphics to Integrated in the BIOS save settings.

At boot up the installation would complete with video signal to the monitor.

 

The crazy situation is, I can then bring the RX580 back on line as the main Card with all the necessary changes and all would be fine loading and booting.

So why the RX580 is problematic initially in Tahoe doing a clean install is a mystery to me.

 

I tried a clean install with the first Beta and you all know my traumatic journey with that one.

Tried a clean install with Beta 2 and the situation is unchanged, had to go the CPU Graphics route first then bring on line RX580.

 

Will try again with the next Beta when a link is provided for a D/Load to build an install USB.

Tahoe is definitely playing hard to get. ;)

 

 

If you're currently using an iMac SMBIOS, try with a MacPro7,1 SMBIOS. I remember having some issues with iMac SMBIOSes.

 

My setup for the upgrade was:

1. PEG with multi-monitor in BIOS. iGPU set as if it would need to output signal. But there's nothing connected to it. I'm connected to the RX580. It might be the same with multi-monitor disabled, which also disables the iGPU. I disabled the option after the installation completed, since it boots much faster this way.

2. WEG, previously enabled in config, I had to disable, otherwise it wouldn't move forward with the installation. What's interesting is that WEG doesn't seem to be an issue for normal boots.On the contrary, as was saying above, it helps with those purple lines (and probably other things, too). But it is an issue for fresh installs and upgrades.

Weird.

Could be a bug or something. After all, it's only the second beta. But yeah, weird...

 

Also, I have to agree, I've never encountered such a bumpy installation process before. :))

I haven't tried clean installing Tahoe again...but yeah, I don't see why it would be any different.

@Arsradu maybe you need test this for avoid FV enable: 

 

 

"Misc > Security > AuthRestart" define false
 

Check first on Recovery or  Installer Off-line  Terminal: 

 

sudo fdesetup status
 

sudo fdesetup disable

 

 

image.png.cf7cb254899b8340d0616fd4a47e441e.png

 

Edited by Max.1974
6 minutes ago, Max.1974 said:

@Arsradu myabe you need test this for avoid FV enable: 

 

 

"Misc > Security > AuthRestart" define disable 
 

Check first on Recovery or  Installer Off-line  Terminal: 

 

sudo fdesetup status
 

sudo fdesetup disable

 

 

image.png.cf7cb254899b8340d0616fd4a47e441e.png

 

Yeah, it's enabled in Misc > Security > AuthRestart.

 

So, you're saying I should try to disable this...? As far as I understood, this option is only for restarts. Like, if FV is enabled, you are already authenticated, and you restart, it won't prompt FV again. Meaning, you will log into the OS the usual way, not through FV. I'm not sure if this prevents FV encryption during installation in any way though...

 

Anyway, I'll try to disable it and wait for the next update to test if it re-enables it.

Edited by arsradu
  • Like 1
1 minute ago, arsradu said:

Yeah, it's enabled in Misc > Security > AuthRestart.

 

So, you're saying I should try to disable this...? As far as I understood, this option is only for restarts. Like, if FV is enabled, you are already authenticated, and you restart, it won't prompt FV again. 

Anyway, I'll try to disable it and wait for the next update to test if it re-enables it.

 

Check my plist is set "false"

 

 image.thumb.png.0f21b14ee7bc7885f49ff7ca89955748.png

 

Vault you can try 

 

Vault = Disabled
 

 

 

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