All Activity

👍

macOS Sonoma 14.8.7 (23J516)

macOS Sequoia 15.7.7 (24G716)

Tahoe 26.5 Beta 3 (25F5058e)

thanks to the AMD OSX Discord user @KWODOi did some tries with new ASUS Hero bios 2202 (using old 2001 patches and my working EFI now i see all my sata disks 🙂 some problems here so i have to investigate better So now this pc is ready for new incoming CPU 🙂

sembra risolto il problema della schermata grigia prima del login con l'HD630

quando installi, metti il KDK della relativa versione del tuo OS? di solito quella schermata la fa perché non hai quella versione

👍

@audiomanno che io sappia

@fabiosun @carlo_67 esiste un modo per fare funzionare il Wi-Fi e il bluetooth su sequoia che non sia OCLP ???? La mia scheda e' una broadcom modello BCM43602, e con le patch di Open core Legacy patcher funziona perfettamente però c'è un glitch grafico all'avvio di macos sequoia appena prima della schermata di login , dove si visualizza per un istante lo sfondo grigio del monitor sottostante le icone che sparisce immediatamente dopo l'arrivo alla pagina di login, se tolgo le root patch non lo fa più ma ovviamente il WiFi e Bluetooth non funziona.

You did try without smc dell sensors? In my experience it hurts performance terribly to have it enabled

Ho sbagliatoooooo........non è per processori Intel.....tardi ma ci sono arrivato....tardi....ma meglio che mai😁

Yes, I did try that, and I went quite deep into it. I worked through the ACPI and EFI side, dumped the relevant addresses with different tools, checked the drivers, and looked at the address tables to see whether I could patch or override the thermal behavior there. So the usual PROCHOT / ACPI / EFI path was definitely part of the process and not something I skipped. From what I found, though, that was not the real blocker. The actual problem seems to sit deeper in the platform. The temperature sensor path appears to be handled through the embedded controller, most likely over SPI/eSPI, which means the important logic is not really exposed in a way that can be cleanly patched through EFI or ACPI alone. I could inspect parts of the firmware-facing side, but I had no real access to the controller logic that actually handles the sensor behavior and triggers the throttling response. I was able to confirm the sensor behavior under Windows with a sensor tool. That tool even offers a slower protocol mode, and when I warmed up the area slightly, I could clearly see the temperature rising there. So the sensor itself was definitely reacting. The interesting part was that it did not behave the same way under Windows as it did under macOS. Under Windows, the whole system was much more usable, and the thermal reaction kicked in noticeably later. Under macOS, the throttling was far more aggressive and started too early, which is why I believe Windows is applying a different thermal policy or handling the controller path differently. If that same behavior could be reproduced under macOS, the device would probably be fine. I also tested this across three different mainboards and saw the same pattern every time, so it was not just a one-off faulty board. I tried a hardware-side fix for the sensor as well, but that did not solve it reliably, especially once the case was closed again. I also looked into solving it in software, but without proper access to the embedded controller or its command set, there was no safe or reliable way to change the reported values or the thermal thresholds. So yes, I tried the EFI / ACPI / driver route. I tried reading and analyzing the relevant addresses and tables. I verified the sensor behavior under Windows. I tested multiple boards. I even tried a hardware fix. In the end, the real limitation was that the decisive thermal behavior seems to be controlled behind the embedded controller, and without access to that layer, I could not properly solve it. That is why I eventually shelved the project. It was not because macOS itself would not run. It was because the thermal path was being handled in a way I could analyze to a point, but not truly control.

1.mov

https://github.com/perez987/About-This-Hack/releases/tag/4.2.0

1 2 e 3

Buongiorno @Anto65 potresti darmi il link di questo immaggine di rapporto

👍

👍

Did you try the prochot disable in EFI by ACPI or EFI driver? I have seen ppl doing both

macOS Sonoma 14.8.6 (23J511)