Leaderboard

26.2 build 25C5048a tutto ok su amd

Tahoe 26.2 Beta 3

😁 Aggiornamento Disponibile ! Beta 4 (25B5072a)

😅 macOS Tahoe 26.2 (25C5031i)

Tahoe 26.2 Beta2 (25C5037j) Full Installer https://swcdn.apple.com/content/downloads/55/17/089-37246-A_YR03P2A5PV/lzis1io0n333tre6c2m3eoapcj0t9d1ops/InstallAssistant.pkg

Evvai 😄

updated 😄

Aggiornamento fluido

Risolto Grazie al grande maestro @Anto65 tutto funzionante al 100/% Grazie di cuore

macOS Sequoia 15.7.3 (24G407)

macOS Tahoe 26.1 ( 25B78 )

👍

macOS Sonoma 14.8.3 - 23J213- 👍

Tahoe 26.2 beta 2 (25C5037j)

👍 Grazieeee 1.mov

Volevo solo far vedere perché siete "Grandi" e condividere ciò che con il vostro aiuto, sicuramente non sarei mai riuscito a fare e ringraziarvi, come credo molti altri qui devono ai vostri consigli....tutto qui.

👍

macOS Sequoia 15.7.2 (24G325) ( Stessa Build della RC ) Full Installer https://swcdn.apple.com/content/downloads/23/34/093-99065-A_B4TEYIISAM/1a1ddvynvgdh82ev879kh13y2a3trwr18v/InstallAssistant.pkg

macOS Sonoma 14.8.3 - 23J208- 👍

macOS Tahoe 26.2 - 25C5031i- 👍

🫶 e vaiiiii👍

👍 anche il piccinino

👍

macOS Tahoe 26.2 (25C5031i) Full Installer https://swcdn.apple.com/content/downloads/61/38/089-21532-A_YQKEJT7V5Q/p2q4el4he34xsqqpno2guqhkrmxdgmp24a/InstallAssistant.pkg

Anto65, ho aggiornato a Tahoe 26.2 beta e tutto è filato liscio e funzionante ma una curiosità: come mai a te, nell'immagine di sopra porta l'aggiornamento incrementale di soli 1,75 GB ed ha me (sia attivanto in EFI kernel weg versione modificata 1.7.1d7 che disattivandolo completamente) mi è uscito sempre l'aggiornamento completo di 17 e rotti GB?

Hi @yandong31, I saw that you also asked the question on Discord to get CorpNewt (aka CorpGhost) involved in this topic. I'm happy about that and would like him to participate as well to shed some light on this topic, even though it may not be his area of expertise 🙂 (sorry) Getting back to us, you're not considering the fact that when these discussions first started, the DevirtualizeMMIO quirk wasn't so “famous” and the version of OpenCore (0.6.x) was much less refined than the one we use today (see, for example, the quirk section and the bootloader's memory manager itself). I and other users who had bought an AMD trx40 (top of the range at the time) clashed over the fact that OSX would not start on these machines. The first consideration that came up was that AMD's kernel patches needed to be updated (but this was not the case with subsequent tests). From here, the questions I asked vit9696 on Insanelymac at the time also consider the fact that DevirtualizeMMIO was used exclusively to run old OSes on Intel and for little else. So, with my obvious shortcomings on the subject, I started doing some debugging to understand why OSX wasn't working on my PC and those of other unfortunate colleagues (TRX40 users). Vit9696 and DownloadFritz (chief developers of the OpenCore project) tried to explain to me in a cryptic way (at the time) how to debug, and you can find these tests on InsanelyMac. It wasn't easy to talk to them for two reasons... the first is that I'm not a technician on these topics, and the second is that they consider the kernel patches we use to be junk. That said, after running all the tests (and there were 19 MMIO areas for my system at the time), they said that the AMD patches for the kernel were “borked.” * Here I'll open a small parenthesis for further explanation. None of us could understand at the time whether this statement was correct or not, so we devoted ourselves completely to virtualizing OSX with ProxMox. and it was a wonderful experience for all of us 🙂 Some time later, without any changes to the AMD kernel patches, in a more recent version of opencore (with new quirks and openruntime), the TRX40 systems began to overcome the initial hang due to lack of memory space, but any attempt to start OSX failed miserably.* So we started reviewing the various combinations of quirks and MMIO areas, and one user (Pavo) announced that he had managed to run the OSX of the time (perhaps Mojave or Catalina) in “bare metal” (without virtualizing in ProxMox). There were several problems, but the system worked 🙂 From there, further questions arose about how to optimize our systems. Some restarted instead of shutting down, others gave KP errors under certain conditions (sleep/wake). And much more. And so began the story that more is better! 😛 We started trying all the combinations and got to the point where, by reassigning all the MMIO areas (skip 1) except the last three of each motherboard manufacturer at the time, we were able to get OSX working perfectly in all its parts Now, I don't want to bore you and any other readers with other studies and tests carried out at the time, but we achieved a system of exceptional usability for all users. Some time later, a user who had studied some patches for Adobe products (XLNC) posted a new method on the trx40 thread. Without making the MMIO declaration in the whitelist but activating the DisableWriteVariable quirk, the same results were achieved! Personally, I never applied it on TRX40 except to verify what he said about his method, but it worked. Now I often use it with new users who are unable to do things themselves to get the correct MMIO for their machines, just to get them started and make them enthusiastic that the money they spent on their PC wasn't wasted 🙂 I hope that with this long explanation, you have a better understanding of my point of view, and I reiterate my happiness that others today (which is easier than it was then) are showing interest in this topic 🙂 Ah, another topic we tried to understand was associating these MMIO areas with parts of the BIOS of motherboards and controlled devices (USB, SATA, NVMe, NVRAM, PCIe slots, and so on). We didn't succeed, and no one has ever done so to date 🙂

Ciao, il buon Anto non ha modificato il kext ma lo ha riportato da noi dando anche le indicazioni di chi lo sta modificando Diventerà ufficiale quando sarà approvato da vit9696 (curatore di opencore e di quei kext), e lo diventerà solo quando avranno testato lo stesso con vecchi sistemi e piu' pc/mac possibili..pero' come ho fatto io..se ne trovi uno che ti va bene e non ti da problemi per te...lo utilizzerei (io lo faccio con uno ancora piu' vecchio di questo di loabmac (lo sviluppatore cinese) Detto cio' non credo che sia il kext modificato a crearti il problema del riavvio o del doppio monitor che si aggancia o meno con gli altri kext...

macOS 26.1 RC - 25B77 - 👍

updated 😄

macOS 26.1 RC ( 25B77 )

RC…

( Notebook HP EliteBook 840 G4 )

L'ho scritto al contrario ed è andata 😄 😄 GRAZIE mille fabiosun 😄 😄

Se non ti carica il file ssdt puoi provare con le proprietà all'interno del config.plist come si fa ad esempio con le schede piu' moderne: in blu il percorso della mia gpu e in device-id lo spoof verso una gpu supportata puoi vedere se una cosa del genere e' applicabile anche al tuo caso, magari controllando il file ssdt

Eccomi un po lentuccio nei primi avvi, poi torna alla normalità.

macOS Sequoia 15.7.2. - 24G322 - 👍.

macOS Tahoe 26.1 Beta 4 - 25B5072a-

Beta 4 (25B5072a) Full Installer https://swcdn.apple.com/content/downloads/41/52/093-85252-A_MV4AZOFO08/ldthfqyadch8d0o06hcl1q34lxlxqb75ug/InstallAssistant.pkg

Mi ha fatto un po penare per la lentezza iniziale dell'apertura del programma dopo l'installazione, ma credo sia dovuto alla poca potenza dell'i3 e della poca ram...boo comunque una volta che ha memorizzato l'apertura va come una scheggia

😻

macOS Sequoia 15.7.2. (24G322)

macOS Tahoe 26.1 Beta 3 - 25B5062e - 👍

macOS Sequoia 15.7.3 -24G412-👍

RDR della USB per l'installazione di Windows XP, completamente automatizzata, con tutti gli update usciti, Framework, DirectX ecc. Completa di driver per tutte le periferiche "esistenti" (no video), in KTD quindi rimangono residenti per nuovo hardware futuro, un gioiello che vale la pena rivivere. Messa in RETE con Windows 11 25H2, ovviamente SMB1 e crittografia a 40. Tutti i driver Storage esistenti in Text Mode per l'installazione RAID AHCI di qualsiasi hardware commercializzato 🙂 In root c'è il Change Serial per l'attivazione. -

🤣 Se sostituivi il boot di Win non avviava piu' ( Win ) solo copiare i 2 file .visibility nella cartella Boot di Win La cartella Boot completa invece nella EFI di OC come hai fatto appunto 👍

L'architettura delle 2 schede è simile, cambia pochissimo. Secondo me non avrai problemi con il cambio

😅 Cimabue taggale , magari questo ti aiuta a identificarle meglio sopratutto quando fai copia incolla se nella partizione EFI di destinazione , trovi poi quella di defalut ( o solo Boot e OC o EFI dentro la EFI 🫣 ) vuol dire che non hai messo quella giusta / colorata ( ... Comunque una sola EFi dovrebbe avviare tutto )