Leaderboard

Chiacchierando su Discord con @fabiosun sono emersi alcuni aspetti interessanti: la degradazione di prestazioni nel 3d è sostanzialmente responsabilità della patch che recita Fix Pat nei commenti. Se viene tolta in sistemi TRX40 le prestazioni 3d sono FINALMENTE PIENE, mentre se viene tolta in sistemi X570 la macchina non è utilizzabile e al 90% degli utenti si blocca ad una schermata gialla. A me si carica il sistema dopo un'infinità di tempo di attesa poco prima della schermata di login... poi si ha il boost prestazionale nel 3d, ma a costo di corruzioni grafiche pazzesche. A questo punto parrebbe che le cpu AMD per TRX40 funzionino correttamente col codice originale Apple per il modulo mtrr.c (quello a destra), mostro in figura quanto gira in rete riguardo alle modifiche che fece Bronzovska (aka Bronya) al kernel di High Sierra nella versione 10.13.3, che, tradotte adeguatamente, sono le attuali patch "vanilla" applicate a tutte le cpu AMD e a tutte le versioni di macOS. https://github.com/AlGreyy/AMD-xnu-4570.41.2-High-Sierra-10.13.3 Inoltre se l'accelerazione 3d non è attiva il boot avviene regolarmente su piattaforme X570 e B550 senza alcuna corruzione grafica... ma chiaramente senza accelerazione 3d non è possibile valutare gli effetti dell'eliminazione della patch 😞 ...qualche esperto di XNU che può aiutarci ad adattare questo codice alle cpu AMD consumer? https://github.com/AMD-OSX/bugtracker/issues/5

CloverX64-5122-jief-2709.1.zip attuale configurazione quirks sulla Z370 se qualcuno usa FakeSMC al posto di VirtiualSMC, meglio inserisca la versione di Slice inclusa in Clover iso o quella di Rehabman modificata da FreeJHack https://www.macos86.it/topic/3210-fix-fakesmc-backtrace-con-opencore/ da me funzionano all'apparenza correttamente, mojave, catalina e BS non fanno il boot e si bloccano immediatamente alle biglie rotanti i win10 e linux mageia, sia che vengano avviati con le custom entries che lasciato il setup nel config su auto.

Ciao, devi aggiungere l'opzione di boot manualmente sul bios per farlo puoi usare la shell (c'è la mia guida per efi shell) oppure app da windows ci sono guide sul forum a riguardo

BIG news (not verified by me, in my case it is not working) It boots 🙂 see video below 😂 It seems @Pavobooted with big Sur in A vanilla mode some problems to solve but for him it is booting now 🙂 for me no... You creators users could try 🙂 ops only you @iGPU others users are Asrock 🙂 fabiosun's EFI and ioreg System Description: Ploddles's EFI and ioreg System Description: Arrakis's EFI and ioreg System Description: mSedek's EFI and ioreg System Description: Rox67er's EFI and ioreg System Description: UPDATE 17-07-2021:

Ciao a tutti, non ho inventato nulla, volevo raccogliere qui tutti i modi per scaricare l'installer dai server Apple, questa guida non è intesa come guida per "novizi" per via del fatto che si deve avere un po' di pazienza e familiarità con il terminale. Come scaricare i programmi di installazione di macOS: 1) Da SoftwareUpdate: Apri App Store e cerca il programma di installazione di macos (solo l'ultima versione dalla normale barra di ricerca) Copia direttamente l'ultimo programma di installazione nella cartella /Applicazioni 2) Da Munki cd /Users/Shared; mkdir macOSInstaller; cd macOSInstaller; curl -O https://raw.githubusercontent.com/munki/macadmin-scripts/main/installinstallmacos.py && sudo /usr/bin/python installinstallmacos.py => Crea un'immagine .dmg alla fine con dentro il programma di installazione .app. Si consiglia di usare la cartella "Shared" come da README su github. 3) Dalla fork di Grahampugh di Munki (dà più info della versione nuda e cruda di munki) cd /Users/Shared; mkdir macOSInstaller; cd macOSInstaller curl -O https://raw.githubusercontent.com/grahampugh/macadmin-scripts/main/installinstallmacos.py && sudo /usr/bin/python installinstallmacos.py => Funzionamento quasi identico a quello dello script menzionato sopra. 4) Utilizzo di gibmacos: Repository originale: https://github.com/corpnewt/gibmacos cd /Users/$(whoami)/Downloads; mkdir macOSInstaller; cd macOSInstaller; git clone https://github.com/corpnewt/gibmacos.git; cd gibmacos; ./gibmacos.command ./gibmacos.command per scaricare i pacchetti, poi il secondo .command per fare il build del .app Guida qui: https://dortania.github.io/OpenCore-Install-Guide/installer-guide/ 5) downloader per macOS: (servono ancora test) https://github.com/rmc-team/macos-downloader/releases fork con readme più dettagliato: https://github.com/SiliconExarch/macos-downloader 6) TINU (fornisce collegamenti diretti all'app store, andando nella sezione in alto sotto help) https://github.com/ITzTravelInTime/TINU/releases 7) applicazione dosdude1 (non ideale) http://dosdude1.com/software.html {Altre versioni più datate} Link per il download diretto da Apple per vecchi installatori con certificati rinnovati:

ah ok, quindi la grafica sembra funzionante il titolo lo correggo io, no problem

dopo semmai posto la efi?

ah meglio così allora 😄

si di fatto è questo, diciamo che non è corretta al 100% Se leggi la mia guida, ormai scritta da anni, quando al tempo 8 persone su 10 se ne fregavano della mappatura solo per il fatto "eh ma tanto ci sono le patch"... poi nel corso del tempo visto i problemi sempre più frequenti, l'instabilità delle patch stesse etc.. è stata poi fatta e usata sempre di più fortunatamente Nella guida vi è proprio scritto la motivazione, il come e perchè si effettua una mappatura, la parte successiva a questa è la definizione dei connettori delle usb, la quale è un ulteriore miglioria ma solo quest'ultima non può essere vista come mappatura sensata nel vero senso della parola quando poi si continua a usare patch etc Ma figurati nessun problema e per come si dice "nessuno nasce imparato" 🙂

https://support.apple.com/kb/DL2053?locale=it_IT https://updates.cdn-apple.com/2020/macos/001-48383-20200924-dfcdb1e6-e5c7-47bf-883c-0808ac829113/SecUpd2020-005HighSierra.dmg

In vm i have a perfect system and i have not problem in bare metal with cinebench 15 i have an instant reboot when i try cpu benchmark sometimes it works and produces a result of about 7800 point often it reboots if it works in catalina for you, can you try to test this for 2/3 times ? ty

hi @iGPU mod you posted for Davinci works, tested yesterday Now I have solved my fresh installation problems (bad EFI structure for my fault) I have a problem with Cinebench 15 running cpu benchmark produces often an instant reboot ah..also Adobe need patching but then works pretty fine (nt tested intensively)

@tsongzmaybe I miss your point but you can upload different efi uploading it via web interface and then declaring it in vm config in this way you can choose efi to boot pressing f2 during Proxmox logo on display but maybe I miss completely your doubt

No Jaidy a minimal functionality to have correct resolutions and 2 monitor connected...this is valid also in Big Sur..but no acceleration is possible

There is no safe efi because this is an unexplored territory patches, boot loader and so on we have to find a proper mix of combinations of it to have, maybe a stable system. if you analyze your boot log I think now you will find in it some errors like unsincronized Tsynch Cpu or similar.. so maybe additional kexts are needed.. in my case executing cpu benchmark with cb 15 or 20 could cause an instant system reset.. using some apps instead like adobe or davinci need perl command patches ..but it is an Amd rig features for now

when we will have more stable bare metal system we could create a sort of database...(config/bios I mean) in my case CSM is off and all settings are the same I use in Proxmox Bare metal for my standard is not stable During benchmark some time it reboots In proxmox I never had a reboot... But happy I can use also this with a proper GPU acceleration

For now I miss only this in Proxmox way...

Ok, I have removed all my ssdt and used some booter quirks I do no use in Proxmox and now system does not reboot randomly 🙂

luxmark is pretty the same:

evvvvivvvvvva..... 🙂

a bit OFF Topic Clover boot loader booting fine on an AMD 3950 x thanks @iCanaro for filming 🙂 more infos here:

Nvram is also used to store nvidia driver status (web driver or OS X default nvidia driver)

Mmio adjustement could be tricky if you do not have any big problem i will stay away from touch it trx40 works for now but it is not clear why.. patches are the same, bios version in my case seems to be irrelevant Only opencore could have done the job for us but opencore’ s devs do not support AMD cpu so it is so difficult to understand and also on AMD-osx people is not interested on a ‘niche’ product as trx40

5) many apps need to be patched to work and some does not work well as in proxmox 6) if some thing change in the kernel...pufff ..our rig does not boot anymore these 2 points are common in every AMD rigs 3) Nvidia web driver seems to have problems to activate (only for me maybe)

I am giving up on bare metal because for now I can’t install nvidia web driver in a correct way i use high Sierra as you know and in proxmox I have not problem i have solved SIP problem which help to load one kext for nvidia others 3 kext s are not loading. to have a correct sip behavior I have enabled AvoidRuntimeDefrag quirk with this I can enable and disable sip totally from high Sierra recovery without nvidia driver loaded I can’t test all the things I have in my mind to do i have an idea that proxmox is far better than bare metal, but thunderbolt study is better in bare metal because it depends only from our efforts and not from Linux missing bridges devices... if I recover my mental energies 😂 I will try to understand well nvram problem latest observation and studies by @igpu are now correct in my opinion On discord thread hackintosh Slav says to isolate mmio which could avoid proper nvram working idk if it is related or not...

I'll lay out the steps I went through to derive the MmioWhitelist. But first I want to say that aside from the slide value of 128, I'd tried various OC combinations to obtain native NVRAM including using the new SSDT-NVRAM. None worked. Only when combining the Quirks reported above and MmioWhitelist and using the SSDT-TRX40-NVRAM did native NVRAM work on bare metal. Steps for deriving MmioWhitelist (make certain that you have an alternative bootable EFI, as you'll see below): A. MmioWhitelist Determination EDIT: Updated from future link at step 4. Initial steps for creating the debug file are still accurate. 1. Run OC debug version (≥ v059; even if you can't fully boot into macOS, you'll have sufficient data written out on the next boot with a non-debug, working version). a. debug OC settings (spoiler): b. after running OC-debug, you'll see following on the EFI boot partition; choose one to open (spoiler): 2. Edit debug text. Once the above text file is open and search for MMIO (spoiler; press press <Cmd><f>, enter "MMIO", then repeatedly press <Cmd><g> until you see list below). a. note the MMIO value range and the permissible Slide value range: b. the 0xYYYYYYYYYY values are copied one-by-one into a calculator (I use the calculator in Hackintool): 3.After converting each of the MMIO hex values into decimals, enter those values (and any optional comments) into Booter/MmioWhilelist (spoiler). Initially, leave all entries disabled (no): 4. Back-to-the-future: we now know a simpler way to create an MmioWhitelist for your mobo. See this to create that list. A proper MmioWhitelist is needed for proper Shutdown functionality as well as native NVRAM. B. Slide Calculation (left as an FYI reference, but not seemingly needed, so don't waste your time with it) 1. memmap calculations a. to run memmap, you need to have OpenShell enabled in OpenCore: b. boot into OC menu system and select "Open Shell" (or however you named it above). you'll then see "shell> ", type "fs0:" then type "ls" and see if you see the EFI folder. Is so, then type: "meemap > meemap.txt" fs0:\> meemap > meemap.txt fs0:\> exit c. after typing exit above, you'll return to the main OC menu and boot normally into macOS d. open the EFI partition (if you have more than one, it may not be on the boot EFI, so look around at other drives) e. locate the file mammal.txt and copy to desktop. once this file is open, you'll see something like this (here, only top portion of the large file): f. OC guides say to start at bottom of list (Start column only). if you do, you'll calculate a slide value something like 2047; some such nonsense. instead start near top and find the largest value that is ≤ 255. The optimum is highlighted by red box above. the value immediately below calculates to a slide of 1018, which is also nonsense. The one in the red box will calculate to 127 as shown next, so this is the largest value that is ≤ 255. g. calculations are done in 2 basic steps using the macOS calculator ( type <cmd> <3> to select the Programmer mode): i. the value from above red box is 000000001000B000 which is 0x1000B000 in hex. we'll do all math in hex. next, subtract and divide this value as follows (copy and paste from here; the trailing zeros are important): ( 0x1000B000 - 0x100000 ) / 0x200000 = 0xFF0B000 / 0x200000 = 0x7F ( 0x7F = 127 in decimal ) ii. the 2nd step is verifying above result to see if the decimal value of 1 needs to be added. verification means taking the above answer, 0x7F and reversing the calculation to see if we get the original hex value. If we do, then 0x7F is our final answer (and slide is the decimal value of this, or 127). If it calculates to a different value, then we must add the decimal value of 1 to 127, which means the true slide value is 128. Reversing the equation: ( 0x7F x 0x200000 ) + 0x100000 = 0xFE00000 + 0x100000 = 0xFF since 0xFF ≠ 0x7F, the actual slide value is 127 + 1 = 128 2. Using the Slide calculation result the result of step 1-g-ii above is your slide value to be entered into the boot arg section as shown in the spoiler below. the ProvideMaxSlide value's default is 0, which means that OC will accept a boot arg slide value ranging from 0 to 254. any value other than 0 will be the maximum value of a slide boot argument; best to leave as default 0. (And oddly enough, this is the same value I'd chosen from above MmioWhiltelist section of 128.)

When you have time try to boot in recovery and from terminal try csrutil status and see the output also try to change sip status and see this could be a big problem if you have to install some kext for not supported device by OS X

Mmmmh interesting..but slide value maybe differs from different pc configuration how do you have calculated this value for your pc? have you have done memmap calculation procedure?

Uhm... my system shutdown normally only in reboot I can see (maybe) a kp but I am not sure because it has no consequences at all Whitelisting is useful togheter the research of a proper slide value for owned system it is possible to calculate your exact memmap and the use a slide value not tested for now because in my bare metal main problem is sip

@iGPUon insanelymac forum, opencore discussion there is a my discussion about whitelisting with download fritz opencore developer it also explained how to i can’t find by now the discussion but was done on January about in that time he stated then patches were borked today I can say maybe he was wrong

Gigabyte users have to compare their bios settings and maybe agesa version in it msi and asrock seem to be less tricky to configure

@iGPUalso SIP acts weird in my system

DSB2 in a working x299 platform shows also hs01 and 02 ot is there a cheaper thunderbolt 3 device to buy to do more precise testing?

thank you, I have to test in HighSierra, in Catalina web driver working is a workaround to have two display I have on

@meina222 I will elaborate better Titan ridge flashing from an unexperienced user point of view

it seems not to add any thing in XHC3: fabio’s iMac Pro 12-08.zip

I think we miss this part : left is mine right is how it should be (maybe 🙂 )

@iGPUI have used previous one these are my results fabio’s iMac Pro IGPU SSDT SET.zip I can't see any device if I connect via usb (type c)

yep and this for me is a big problem

@iGPU I think you win 🙂 fabio’s iMac Pro IGPU DevicePROP.zip

GPU performance is fine in Luxmark (it seems the same as Proxmox) when you have time try with Cinebench R15 (not R20)..it has a GPU testing related section Thank you for plist...I think if we are able to fill port 7 we are in a gold position 🙂

fabio’s iMac Pro IGPU2.zip

@iGPUgood morning I am trying now TY

Baremetal iMac Pro memory tab 🙂

@iGPU and latest for non apple kext loaded sob no Nvidia 😉 fabios-iMac-Pro:~ fabio$ Kextstat | grep -v com.apple Index Refs Address Size Wired Name (Version) UUID <Linked Against> 36 3 0xffffff7f827d5000 0x31000 0x31000 as.vit9696.Lilu (1.4.6) 847B9586-1BE1-315C-B2AC-5E832A407C7B <7 5 4 3 2 1> 37 0 0xffffff7f8283f000 0x72000 0x72000 as.vit9696.WhateverGreen (1.4.2) 9B4CBD0D-14DC-3DA1-B99E-1430023979C2 <36 12 7 5 4 3 2 1> 38 0 0xffffff7f8281f000 0x20000 0x20000 wtf.spinach.AMDRyzenCPUPowerManagement (0.6.4) 1C8D6AF1-3F8A-3298-BCAE-5CAEE5D4A19B <36 12 9 7 5 4 3 2 1> 51 0 0xffffff7f82806000 0x19000 0x19000 as.vit9696.VirtualSMC (1.1.5) E1D2507A-5E1A-328D-85B0-6A8D4263F019 <36 11 7 5 4 3 2 1> 63 0 0xffffff7f828b7000 0x1a000 0x1a000 com.smalltree.driver.SmallTreeIntel82576 (1.0.6) F6C5E33A-97AA-37A0-8794-64FAA19FC153 <15 12 5 4 3 1>

@iGPU thank you i will test later how can i check if they are loaded or not?

Thank you @tsongz i think problem is different, maybe driver related or acquantia id related not investigated so much because using i211 is fine for now..and the big problem for me is to have a working gpu with proper acceleration..i have not for now

Ok it works bare metal works in Catalina 10.15.6 for now I have no audio e no ethernet (aquantia is seen by default but no cable connected message) cpu benchmark are the same like Proxmox i can’t test gpu Performance Ok audio is fine and also ethernet is working (no Aquantia but intel i211 with SmallTreeIntel82576.kext

Non conoscevo questo TINU, ma permette anche l'installazione HFS+..?