fabiosun

Hi, even if you don't quote me directly in this message, I'm glad to reply I start from the part relating to Dortania. Personally I would prefer that everything develop here with us .. on macos86.it This is for several reasons: 1) it all started from here, initially on our discord channel in private only for the staff, then through a heavy debug together with the developers of opencore, who, despite not supporting the AMD platform, for a period have to understand what the problem was . Eventually they concluded that the problem we had was related to "borked" patches 2) I therefore started this journey to understand how to have my system working, regardless of the "borked" said by the developers of opencore. Thus was born the article on ProxMox which initially aroused different interest even in AMD users who did not have the same problem that we all had but who, to quote a user in the hackintosh community ( @Pavo), also for x570 users yes they obtained equal performance, and in some cases better by virtualizing the system with ProxMox. I don't forget the help @tomnic gave me in this period to overcome the points, for me obscure of Linux 🙂 From that moment, a brilliant and reactive community began to form here that slowly, even under the radar, helped the developers to understand better, indirectly, what was the problem for our systems with our logs (maybe also @Apple see us? 🙂).. and in May 2020 it was finally possible start installing vanilla. So, to answer your question about Dortania, I would prefer we continue to support this site that welcomed us, and through its admin ( @Gengik84 )it has also supported us with different scripts and apps that often helped me to move forward I also proposed to everyone to create a database with the EFI of each working system, but at the moment only @Ploddles has accepted this idea I have also created a thread with useful links, where I would like to add everything that has been found useful here ... see for example the story of MMIOs put out in fair copy by @iGPU, after we understand (thanks also to our work) that with that we could solve many other negative situations for our systems (NVram, shutdown, reboot) That's why I'd like to see you still continue here ... by the way .. on Dortania They talk about us? I do not think so. You know that in the beginning, it was me and @DSM2 (another user who happens to occasionally on our forum and who had problems with his CPU initially, but had begun to understand why our problems) Apologizing to the other users I have not mentioned, I would also like to thank long-time users such as @Driftwood and @meina222 who have actively contributed to the success of our mission with their tests and indications. Many users, actually many more than those who then actively participated in our BrainStorming, followed us, even silently ... and passed on to others what we have understood and developed here 😉 Thanks to you too The work is now done, with a little patience you can make everything go as for other less problematic AMD systems The last big challenge I think has remained to have a fully functional thunderbolt. But, our problems with it are similar to those of other AMD platform. That said, any ideas to improve us are useful and I thank all of you for that. I also thank a famous youtubers (Hi hackintosh friends) who stimulated me to produce a free and public guide with her serial videos (such as soapopera) without any info about how to 🙂. Of course with many limits probably .. but, I repeat myself FREE and FREE a warm thanks to all of us ... PS many thanks also to our forum admins and staff Their great support is not evaluable

Ciao puoi fare un hackintosh con il tuo sistema abbastanza facilmente puoi ricreare una penna usb da Windows o tramite una macchina virtuale meglio un ssd/nvme separato per OS X unico dubbio è l’audio usb , su amd per alcuni a volte ci sono dei problemi personalmente non ne ho

Do not worry i had understood well and you confirm it now👍

Sorry I do not understand well here No I do not need debug output if it is working well also for you 🙂 Thank you for testing

in this period I used Clover Bootloader a lot, my aim was to understand which and how many Kernel patches were necessary and sufficient to start with Big Sur (and Catalina) correctly attached here 🙂 they are far fewer than we have always used for the two operating systems in question Let me know if they are working well also for you PS They are in Opencore format 16 patches.plist.zip

Bene, topic chiuso 🙂

Hi 🙂 (obscure your above pictures (it is better if it is your name 🙂 🙂 ) I use to have in my EFi both VirtualSMC and FakeSMC kext..but only one enabled Ii do many test so I have both for this) in the past that kext solved memory error popup..I can't say more because I use iMacPro1.1 Smbios happy you solved many of your initial problems! to other tasks to do..you can now follow general discussion for trx40 🙂

it is only a debug txt useful some time if system does not start you can avoid to print it every time changing to a non debug open core version or to set to 3 this value: Target from 67 as it is now to 3 also this should be to Disable...but if your system starts well leave it as is

hi for point 1) Why? which benefit do yo have with it? if you want to solve memory error you can use this kext: https://github.com/IOIIIO/MacProMemoryNotificationDisabler put in kext and then declare it in your config..but I repeat my self.. why? 😛 point 3) maybe you mixed some stuff? and you have declared all tool you have in OC/Tools folder? I have only two (shutdown and reset Nvram , I use them rarely) check here and put No on item you do not want to see exposed in your boot menu or.. leave it and try to put yes on Auxiliary For bluetooth problem and internal wifi..many people say now it could work with some kext and work to do...no experience on it , sorry

Si ma non è compilato se vedi è dsl e non aml

config.plist 2.zip e poi questo qui

prova questo qui vengo anche un sacco di kernel patches di nmano... casinista guru indiano 🙂 pero' non so onestamente..credo che forse quelle patches sono ora integrate (almeno in parte nel boot loader) config.plist.zip

io con X99 usavo una patch per il kernel di pikeralpha che si chiamava reboot fix e poco altro

non riesco a leggere qui c'e' l'ultimo che nel nome e' anomalo..sembra da compilare e forse e' un doppione del primo anche se..qui ci capisco poco o nulla e servirebbe l'intervento di @Gengik84 quando puo' 🙂

you have to declare also in config.plist I use plistpro editor

you have to try to put all kext you have had in initial your experiment (about wifi / BT related ones I mean) and see if it works

Ok without touching nothing else put in your bios again WIFI an blutooth but I do not know if the internal one are directly supported in OSX There I have no experiences backup this EFI I would like to delete something in it like unflag kernel/emulate/dummypowermanagement better try if you want to see it should boot the same put back also AMD Power Gadget kext in config and download latest 065 app to check your temperature take your time and be happy 🙂

I would like to write in Italian... 🙂 Speriamo bene 🙂

sorry..I confuse again myself delete all I am always starting from a my proper EFi and I forgot to delete sorry again 😉

Archive.zip replace completely

Archive.zipreplace completely with this efi please @cleverhomedo not change any conditions in these tests 🙂 also your chair must be the same 🙂 🙂 we have to win 🙂

please disable from bios wifi Bluetooth and try again no log need

meanwhile I have installed from zero from an USB pen latest Big Sur..used same EFI posted above only changing MMIO with mine! We have had success also with your :)

if so let start from here: EFI 2.zip if it hangs..take a phot o and post a bootlog txt Thanks