Leaderboard

Aggiornate tutte le macchine con OC 0.7.3 , nessun problema rilevato ;)

Beta 7 is out (Monterey) 21A5522h if you do not see it put a securbootmodel value according your used SMBios

🤔 non lo vedo ancora ... devo per forza installare xcdode prima ? ok, che le danze abbiano inizio 😆

beta 7 build 21A5522h

[Release] macOS Big Sur 11.6 Link diretto https://swcdn.apple.com/content/downloads/57/38/071-97382-A_OEKYSXCO6D/97vrhncortwd3i38zfogcscagmpwksdzce/InstallAssistant.pkg

Build 20G165 Questo aggiornamento è consigliato a tutti gli utenti e migliora la sicurezza di macOS.

provato e andato 🙂

sis resettato nvram, ma niente.. non mi vede l'update da beta 6 a beta 7 ... mi sa che per stasera mi fermo qui 🙂

securebootmodel non centra nulla con l'smbios... 🙂 (e l'smbios non centra nulla con il vedo/non vedo l'aggiornamento 🙂 )

for tonite this is my best 😀

@ Gosi Several things: 1) In the config.plist you can delete in DeviceProperties the values of my graphics cards and possibly that of the titan ridge if you do not install it. 2) If you do not use the titan ridge card you can delete the SSDT-DTGP and SSDT-TBOLT3-NVM23 from the config plist and also delete them from the ACPI folder of the EFI 3) The ram values should be replaced by yours in all banks. 4) as part of the installation of the Titan Ridge card, it must be installed in slot 4. 5) Wait until I update Big Sur 11.6 so as not to put a potential problem (I210) on you. I am under the AGESA bios version 1.0.0.4 (FBd). As long as you don't have an AMD 6000 series card, there is no point in upgrading to AGESA version 1.0.0.5 (FBi) which brings Add Re-size bar support on Windows (not supported by MacOS).

if you put GPU in the same slot, maybe nothing will change if you use whatevergreen kext Mac Pro 7.1 smbios and you put a 6900 xt maybe you have to tweak a bit your actual config.plist for the update I read from @Arrakisgigabyte and others manufactured board has some problem with ethernet (i2xx)on board ..I do not know if it is true also in 11.6 or only in Monterey beta I use an Aquantia card so I have not this problem

Ciao secondo me lo switch software non sarà disastroso come quello del 2006, i software si sono evoluti molto in questi 15 anni così come si è evoluto Rosetta

They think that everything is optimized for Intel in every os, it is true but now we have the prove that Intel simply cheats with its own software libraries... faking the AMD cpus to be Intel we get the same performances, and we lack AVX512...

You file works! I have the latest PP as you Thank you Yes it is strange. I think this is because of the adobe AMD fixes github page. People just copy and paste the solution and assume the rest (eg Warp Stabiliser / Tracking / Neural Engine etc... will never work without an intel machine

ah no. Resta la radeon quindi..

in Hachintool devi asportarlo File > Export = Bootloader config.plist dopo aver generato la patch (prova diverse combinazioni ...troverai quella che fa per te 🙂. ) e dopo aver aperto entrambi con plisteditor copi nel tuo plist

@nikoel Yes you need new plugin patching method explained by @tomnic or if you are on 15.4.1 you can use this one attached 🙂 I have tested all others features and to me they seem to work fine If you find some other errors post it please Strangely it seems no many users are interested in public of this subjetct Weird..on OSX Adobe suite is a must from many years and now that it is working pretty perfectly without doing many quirks.... 🙂 🙂 AEFilterRollingShutter.bundle.zip

@gosi You can try this EFI under OpenCore 0.7.2 For me, this is the best since I started. I am using the WIFi AX200 from the motherboard without problems. Under Monterey it also works. Add the kext BlueToolFixup.kext Change the IntelBluetoothFirmware.kext version for Monterey Remove the IntelBluetoothInjector.kext @fabiosun You can put this EFI in OP

Good!

@gosiprobably you are using @ArrakisEFI If you like put in your signature your exact hardware (from user profile you can do it) You have to do also a job to know if your MMIO is identical to ones you use in EFI you downloaded here (probably no) This fact could produce instability in your system About bootarg: Edit your config with plist editor and search this: probably yours is empty. I advice to proceed before all your testing to built a proper MMIO whitelist you can learn How to here : https://www.macos86.it/topic/3307-trx40-bare-metal-vanilla-patches-yes-it-worksbutis-proxmox-better/?do=findComment&comment=85469 If you use internale i21x ethernet It does not work in Monterey by now

presente

YeSsS Presente e funzionante su EliteBook 8470p 😉.

che smbios hai? guarda faccio giusto due prove.. se non va pace 😄 tanto ho ancora Big Sur totalmente funzionante, vorrei fare dei test per poi aggiornare "come-se-fosse-un-vero-mac"

Io ho messo j137 riavviato e l’ha visto. Ora sta installando.🤞

devi modificare securebootmodel per vedere l'aggiornamento...devi mettere un ID relativo a una macchina con chip T2...se no, non te lo vedrà mai... j137 j160 etc...ma tanto poi non si installa xD LoL

vado pero' a dormire sereno 🙂

Sembra lo stia prendendo.... 7 minuti ancora ( con il jolly) 😄

old method to upgrade from beta 5 to beta 6 is not working here

I would like to find a pc faster than one similar to mine on intel side 🙂

...yes, I think it is the same psychological mechanism, and it is easier to sell the AMD rig and buy an Intel CPU + Mainboard or stick with Unraid / Proxmox hypervisors

we we we ci sono anch'io!! ahahah 🤣. ...cioè...spero...vediamo dopo... ahaahha