fabiosun
-
Posts
11,397 -
Joined
-
Days Won
546
Content Type
Profiles
Forums
Events
Downloads
Everything posted by fabiosun
-
post your config because some time in monterey it hangs for many seconds with apple and loading bar then it logs You can try to clear Nvram and also to use weg with some bootarg you coold also try to boot with boot debug enabled and the post misc/boot txt file
-
@jsl2000 Gpu?
-
@iCanaronot works for you could you post a debug log when it does not work and also relative config.plist maybe we will discover that it is the same problem we had in the past
-
@jsl2000 you have to use patches related to your cpu branch mine are 17h 19h
-
@jsl2000i think you can try to adapt minimal patches set posted above to put also with your FX CPU..it would be interesting to know 🙂
-
Un fattore che spesso si ignora quando si eseguono test di stabilità o di temperature sui propri sistemi AMD di ultima generazione, e' come si e' configurato il Precision Boost Overdrive o in forma abbreviata PBO. Il PBO non e' altro che una gestione avanzata del power management delle CPU AMD , che, in base ad una serie di condizioni, spinge la nostra CPU ai suoi limiti. Il PBO e' una sorta di overclock di fabbrica, molto piu' avanzato del SynchCPUALL che troviamo nei vari bios intel.. Per definirlo in maniera leggermente colorita una grande paraculata! Nel BIOS, la voce e' definita come PBO e si trova di solito nei parametri avanzati della CPU. Quando postiamo un benchmark o il valore delle temperature raggiunte , bisognerebbe sempre specificare come si e' impostato nel BIOS il valore PBO. Di seguito due immagini di un test effettuato con Cinebench 23 avendo impostati i valori nel bios prima in PBO=Auto e poi in PBO=Enabled: Da notare in particolare modo i valori delle Temperature e del Power. Ringraziamo un buon alimentatore che subisce circa 400 Watt nella condizione PBO enabled. Questo per dire che anche quando scegliamo alcune componenti base come il dissipatore della CPU o l'alimentatore dobbiamo fare particolare attenzione. Affinando il valore di PBO in enable e modalità avanzata e' possibile "tirare" i watt a piu' di 400 e ovviamente con un aumento proporzionale delle temperature e dei benchmark. Il mio AIO ha un valore supportato di 500 Watt e la cpu di base ha un TDP di 280 Watt. Quindi tornando al termine colorito di prima..AMD ha dato ,con questo sistema, la possibilità di avere un overclock avanzato di fabbrica con un click, garantendo di fatto la massima stabilità in quanto il PBO analizza vari fattori e poi si auto configura in base alle risposte del sistema in uso...
-
@iGPU I just asked to test that EFI in the conditions that are necessary to make it go and see if on yours or on other trx40 systems there is the same decrease in temperature at the moment it was not possible. To explain me better, with the new patch system, converting a 30-minute 4k video with Davinci resolve to DCP format I usually reach temperatures of 70 degrees with the efi in OP With the new patches, quirks and so on about 84 degrees t's too much for me EFI can also be completely adhering to the principles of configuration.pdf, but that's not good for me and I wanted to understand why At the moment it was not possible but I remind you if we had followed the specifications and indications of the manual or the opencore devs, perhaps today we would still be in ProxMox 🙂 I don't want to remind you how they define an amd system that uses" junk kernel patches to boot", also called "borked" Fortunately, we tried other things .. and it's going well. thanks anyway for your detailed messages 🙂
-
A spike of 63 degrees when system is doing nothing for me it is no good the sense of the test I was asking is to see if also for other users with that Efi is possible to have a temperatures reduction as I see of 10 degrees and more. then we can also discute about mat or what it is correct for an Apple system with an unsupported thread ripper Cpu
-
@iGPUEFI you have downloade is only till Big Sur beta 4 so you have to leave "my" patches and try with your BS 11.5 beta 4 . I think temperatures are too elevate and for now I do not know why I can use your EFi without touching nothing obviously I miss a couple of MMIO if I do in that way but system starts and works.. For now I can't have a system as I like if I include new Monterey b1 patches... if you use your patches in my 070 EFi couldn't work because you disable two patches as we said and you discovered yesterday and without them I need of RebuilAppleMemoryMap quirk ..to see if your system boots you should only change your MMIO and maybe something with WEG I do not use as kext and either as bootlargs..but it is only a my curiosity to see also for you some degrees less happen to summarise with a 13 patches combination my system needs RebuilAppleMemoryMap that usually I do not use) if you put your complete set of patches in my 070 EFi you have to enable that quirk..and to gain some degrees also DisableIOMapper.. but my goal is always to reduce stuff 🙂
-
@iGPUi have 10 ° in all 3 system I can boot, my results in temperature are similar to yours With previous EFI posted in this thread I have had 10° less I am investigating this (not happy for this I mean) I didn't do an accurate testing (sorry) because I am trying to have patches working also for Clover Bootloader and a X570 system confirmed your update about AMD PowerGadget to explain better this assertion 🙂 I usually do not use RebuildAppleMemoryMap quirk and without two patches I have a pretty instant reboot Bios and hardware settings are not involved in my opinion
-
@jsl2000good could you share patches plist you used? maybe could be useful for other people use the same CPU
-
grazie @iGPU i can confirm all system booting fine from 11.4 release to Monterey B1 (tested also 11.5b4) with above limited set of patches I am investigating some stuff about temperatures
-
ciao @VinX360benvenuto se non trovi un thread nell'area apposita per Big Sur Se vuoi aprine uno tu e li chi puo' di darà una mano sicuramente. Se ti e' possibile metti il tuo hardware in firma in modo tale che l'eventuale aiuto sia piu' mirato. grazie
-
sometime before login you have apple logo with bar for more than 20s or colourful beachball before to see login mask not always..but it is a beta1 and something wrong could happen
-
@jsl2000enable boot debug many useful info there also with clover bootloader
-
And this should help people to understand for many does not work above part of attachment is first Monterey beta 1 installation part. Clover bootloader looses GetOS detection and in this way it applies all patches it finds in kernel patches config.plist section (OLD BUG) In below part of the picture, it is the second installation reboot, Clover Bootloader recognise GetOS Detection and applies correct and declared patch I want So if you have @converted@ all 40 AMD OSX Github patches...in the first step clover bootloader applies all of them..and this is not good at all 🙂 I leave out the fact that there are some issues with Clover-defined names for patches arguments, and sometimes also with type definitions (data, string, boolean and so on) But that's another story ....
-
@iGPU @jsl2000 poporopo patch edition was a my fault too much joy after Italian football team game and I have posted bad patches Sorry attached 3 debug log clover 5137 and....listen well less patches than poropopo edition 🙂 It should work in the same way in iGPU rig, maybe jsl2000 has to do some add (patches and quirks) I will happy if you can try! During nomenclature conversion I have understood a few things analysing debug log, picture below should be updated or explained in a better way (I mean For Identifier---> Name and others) meanwhile is better to not use it UPDATE 18-07-2021 https://www.macos86.it/topic/4913-amd-clover-bootloader-monterey-beta-1-installation-patches/?do=findComment&comment=116586 DBG_11.4_11.5b4_12b1.zip
-
Hi @iGPUMonterey is yet installed or you are trying to update it form BigSur? Have you a debug log? thanks then are you sure you are installing (if you are updating) beta 1?
-
in teoria si ma non ho la tua piattaforma..
-
se e' uno degli ultimi dovrebbe andare pero' cerca di avere una soluzione solo se...diciamo just in case (non te parta piu' una ceppa) 🙂
-
@wolvherin78se hai scaricato l'installer d icosa vuoi mettere su catalina puoi provare a lanciarlo e scegliere il disco dove hai installato Catalina per Big Sur devi avere i kext aggiornati ed il bootloader che usi anche poi una volta partito il sistema dovrai lanciare il patcher e fare ridare i valori corretti del sistema in uso al plist se ti funziona nvram e se hai icona Nvidia sulla barra in alto metti li nvidiaweb riavvii e dovrebbe essere fatta se cosi' non fosse..capire cosa accade da te potrebbe essere meno semplice 🙂
-
Hi @jsl2000 i am trying to reduce patches I use on my trx40 system they should work also for you if it works or not it is also a combination of quirks you use and bios parameters important thing to say is that people could try to add some others official patches using the same nomenclature I used in posted patches if you want post your debug log when your system hangs or check by yourself if inside it you see GetOS string with right os data version it should be also an old clover bug😉
