All Activity

Si, certo che ho fatto così, si riapre lo stesso pop up

te lo sta discendo " App consigliate " Clicca su OCAuxiliaryTools e poi sotto , sempre

Non cambia nulla, arrivo alla EFI/OC ma quando selezione config.plist mi apre il pop up

Pensi di trovare la partizione EFI di OC , nella partizione C ? Prova ad aprire le altre partizioni d , d , f , g Nel mio caso OC risiede nella partizione g

Ok, grazie, ho provato, mi apre un pop up che chiede quale app utlizzare per il config.plist ma pur selezionando Ocat si riapre il pop up

Capita a tutti 🙂 su Windows. Ora non ho piu' windows sul mio sistema ma quella e' la schermata standard per poi montare la partizione EFI Se hai un config.plist prova ad aprirlo e dovrebbe venire l'interfaccia standard di OCAT (per montare la EFI e' un po' diverso dalla versione di OSX) PS. prova a controllare se uno dei 4 dischi che si vedono oltre C sono in realtà le EFI montate

Buongiorno, a nessuno è capitato, come si risolve per cortesia? Grazie

Su diskutil list vedo che il nome della partizione è un UUID e non il nome del disco. Se provo il comando bless mi dice che il parametro --last-sealed-snapshot non è riconosciuto. Se provo il comando diskutil apfs list mi dice che il verbo apfs non è riconosciuto. Sono sempre più perplesso...

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 🙂 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 🙂

Sembra strano anche a me, ne ho dovuto mettere 2 come si può vedere dalla foto (così funziona tutto). non c'è verso di risolverlo ho provto tutti i kext che mi hai mandato ma nulla la wifi breadcon non va va solo il buetoot.

ragazzi per audio funziona

You're right, I only need to skip Region 2 to boot. However, since Regions 3 and 4 are quite small, I'm thinking that skipping them as well might improve system stability. I'm testing that theory now.

Thread was created to have a place to discuss freely on this subject, so also your opinion is important and will be useful to other In your test (if you like try to disable MMIO whitelist and use the quirks i said In my opinion your system will be working in the same way! PS: you platform (if it is x670E/X870 E) need only that second area Skipped to 1 (you can check many EFI you see in international forum) Trx40 was different

Just to be clear for anyone else referencing this: for my platform, I only needed to skip Region 2 to get everything working normally. I'm not replying because I have a problem, but to serve as a reference for others — don't fall into the trap of thinking that skipping more regions is always better. To be clear, my view might not be entirely correct either. Let's discuss it and allow everyone to judge for themselves. Regardless, I really appreciate your contributions on the forum.

this is an extract of a my conversation with DF (in 2022) You can try if your platform is an X870E to reassign first four and see if you have problem (Nvram, reboot, boot and so on) Or you can disable MMIO whitelist and use only two quirks i said I am pretty sure your system beahviour will be the same! In the past DF said me MMIO areas are not OSx related but Uefi firmware related (and i respected his words) Ps, i do not have to convince you more or less is better..i have only proposed my experience in a platform that initially was not supported by opencore 😉

Like I said before, with MmioWhitelist, more isn't better. If you skip 4 out of 5 regions, DevirtualiseMmio only reclaims memory from a single region for the system — and it's likely the smallest one. This can actually lead to system instability. When it comes to the TRX40, the 'more isn't better' rule still holds true. However, the reason it might need a longer list is that the platform inherently contains numerous small or defective regions that must be filtered out. Skip in MMIO devirtualisation means exactly what it says. It skips devirtualisation for the particular region found. — If a region is whitelisted, then devirtualisation does not happen, and skip is 1. — Otherwise the region is permitted to be used by the operating system, and skip is 0. To be fair, vit9696 was very clear about this from the start.

on TRX40 more was better. on AM5 this is not valid On am5 i can reassign 4 of 5 MMIO areas, in this way my system loose its stability I only reassign 1 area and system is perfect, or i use DevirtualizeMMIO and DisableWritevariable quirks without whitelisting any MMIO areas (not adviced but on AM5 it works as wit only a MMIO area reassigned. No skill to understand if from 2022 opencore devs or motherboard Uefi firmware creators have changed something

Put another way, enabling DevirtualiseMmio while whitelisting every MMIO region effectively neutralizes it, producing the same outcome as leaving it off.

No it is because i DisableWrite variable I have a question for you: Devirtualize quirk ON you have, let say ,5 MMIO area Skip to 0 in your opencore log you reassign all of them and you see then all MMIO areas to skip 1 What does this mean? (related to DevirtualizeMMIO quirk)

@fabiosun Your testing actually confirms my earlier point perfectly. DevirtualiseMmio works by freeing up more memory for the system to use. The reason you don't need a whitelist is that on your platform, all the memory it reclaims is perfectly usable. However, if some of that reclaimed memory is faulty or problematic, you must use MmioWhitelist to skip over those specific bad regions to prevent system crashes. The trade-off is that the more entries you add to the MmioWhitelist, the fewer available addresses KASLR has to work with, which can cause its own set of problems. So, I still believe the primary function of MmioWhitelist is precisely to identify and filter out the non-usable MMIO regions. In my platform's case, there are four key regions. Skipping only the second one is sufficient for a normal boot. But given that regions three and four are quite small, I think including them in the skip is a viable approach. 21:417 00:057 OCABC: MMIO devirt start 21:430 00:013 OCABC: MMIO devirt 0xE0000000 (0x10000 pages, 0x800000000000100D) skip 0 21:443 00:012 OCABC: MMIO devirt 0xF7000000 (0x7E00 pages, 0x800000000000100D) skip 1 21:475 00:032 OCABC: MMIO devirt 0xFEE00000 (0x1 pages, 0x8000000000000001) skip 0 21:488 00:012 OCABC: MMIO devirt 0xFEE01000 (0x11FF pages, 0x800000000000100D) skip 0 21:544 00:056 OCABC: MMIO devirt 0x860000000 (0x20200 pages, 0x800000000000100D) skip 0 21:558 00:013 OCABC: MMIO devirt end, saved 806912 KB 21:570 00:012 OCABC: Only 128/256 slide values are usable! 21:602 00:031 OCABC: Valid slides - 128-255

@yandong31in my current platform you can see in my signature i skipped totally to build a correct MMIO withelist. on AM5 there are few area compared to trx40 platform and also using MMIO whitelist is pretty simple to have it working (only one must be reassigned to UEFI bios needs) Only to my purposes and funny tests i use DisableWrite Variable quirks without building a MMIO Whitelist area and system is perfect in all its function (sleep, wake, reboot and so on) with trx40 in the past we had to reassign more we can because we had many problem if we thought "less is better" (sleep, restart on shutdown and Nvram problems) Devs documentation in this subject were initially few and cripticed (for non devs users) then (maybe) they clarified better also in opencore documentation (see where and when (Year 2020/1/2) this thread was born and see also their documentation in that time) I had some chit chat (because i have zero skills to understand his friendly lecture) with Download Fritz about MMIO areas in others forum and he explained and clarified stuff about UEFI Bios and how this subjetct was involved in MMIO areas Said this, thank you to renewing this old thread and i renew also the ask if you like to improve your finding in a detailed way i will very happy to add your experience in OP 😉

@fabiosun My understanding is that the DevirtualiseMmio quirk is designed to free up more memory address space for KASLR to use. However, some of these freed-up addresses might be problematic. The purpose of the MmioWhitelist is to filter out these specific problematic addresses. Therefore, the MmioWhitelist shouldn't be considered "the more, the better." A longer list actually means less address space is ultimately freed up for KASLR. The correct approach is to only list the addresses that are genuinely harmful, preventing just those from being released.

Dovrebbe andare solo con la broadcom Tutto sia WiFi che bluetooth Scrivi anche il modello, se andava prima mi sembra strano che devi avere una centrale nucleare per avere i servizi

Ho risolto mettendo tutte e due le wifi e disabilitando la wifi breadcom la quale funzione per il beutoot e la Intel per il wifi....sembra una astronave da dietro ma comunque funziona......in attesa di essere aiutato a risolvere il problema.

quale kext dovrei mettere?