Leaderboard

AMD Power Gadget on TRX40 (CPU PM management)

Cavolo @iCanarole sa tutte, oltre i Kext aggiornati, ora parte tutto sia con Clover che con OC anche big Purga si è inchinato 👍 Grazie adesso mi studio che cavolo sbagliavo ringrazio tutti i ragazzi per quello che fate per noi poveri apprendisti Grazie di Cuore

@Gengik84grazie mille ora funziona tutto a meraviglia

forse conviene che leggi la sezione notebook di catalina chi ha cosa e come funziona https://www.macos86.it/forum/99-notebook/

È già come si deve, anzi è un miracolo che funziona

su hack Z370 ho avviato aggiornamento a BS 20B5022a con Clover 5126--114854268.efi come boot loader e sono andato a pranzo; al ritorno 😁 per chi usa VirtualSMC consiglio come boot-arg watchdog=0 onde evitare reboot casuali

prova a mettere ReleaseUsbOwnership YES

Risolto grazie ad opencore.... Grazie a tutti ragazzi. Mi sa che è ora di abbandonare clover

Fai foto anche con opencore che misà scegli icona sbagliata anche li

Se vuoi un Sistema nuovo da Ripristinare, la 10.15.7 19H2, puoi metterla su un altro disco e ripetere l'aggiornamento...

se non hai un open core funzionante da te @Fasullo la vedo dura configurare il nuovo clover, in quanto ha qualche problemino di suo ( e vai a capire se il problema sei tu o, probabilmente lui) 😀 prova a spostare i tuoi kext in other e partire sempre dalla icona preboot e non dati ma la vedo dura 🙂

Big Sur 11.0.1 Beta 2 installazione riuscita sempre con OC la vecchia e prima vers. tranne i Kext aggiornati all'ultima versioneper il resto tutto come prima @iCanaro che ringrazio è andata al primo colpo alla prossima

non e' quella l'icona giusta prova a premere F3 vedi se ti compare una icona simile ma con scritto Preboot e' un problema di clover nuovo 😉

ottimo grazie Fabio....magari gli dirò di acquistarla per ultima

Ciao, magari posta la foto del blocco sul verbose

I would try to start from your Proxmox EFi also in Baremetal Adding full set of AMD patches and nulling all ssdt you are using in proxmox Then Devirtualize MMIO on this should be the starting point for all people who have a working Proxmox EFI You (AMD GPU user) should have less problem than I have had because AMD driver is in OSX Evaluate also well, how in your system act some quirk (booter quirk) relative to memory remapping... For me this was the key MMIO whitelisting is useful for debugging restart and shutdown problem you can have This, without using any ssdt only enabling blacklisted MMIO MSI users should not need of npci 0x2000 boot arg, also with 4g disabled in Bios I have the same bios setting I use to boot in Proxmox Now I will test more extensively the apps I usually use, but as first impressions they acts in the same way

Seems old problem with prelinled kernel and big sur

@meina222may I have your fully working EFI in proxmox and your mmio plist (bare metal I mean)? if you want loose some time again with bare metal I will prepare an EFI for your system I would also suggest an important thing to consider Proxmox threats ddr4 in its way so maybe a more conservative memory settings in bare metal could help if system acts weird

Ah..as other infos I would like to share in a very happy way.... Sleep is working 🙂 🙂 🙂 🙂

I still don't know how ... more or less ... but I managed to activate the driver again .... hurray.. the hard head always rewards if it also joins a good blow of .... ass (colorful way to say that I was lucky)

I would like to suggest during testing MMIO stuff to leave verbose boot on to see verbose data during reboot (often during reboot there is a fast KP, you can solve with proper quirks and MMIO skipped)

@Pavo SSDT is loaded and variable stay there also after a reboot same behaviour of emulated NVRAM For now not useful for my problem (Nvidia web driver not loaded properly) @iGPUwaiting for your idea to try... I wonder way during my test..without doing nothing of special I have it loading well then after a problem with default secure boot parameter I have had to clear my cmos and from there no joy fabio’s iMac Pro Pavo SSDT.zip attached my IOREG with Pavo's SSDT

thanks I will try

No I am using emulated one..but it does not solve my Nvidia driver problem

@meina222 our MMIO are pretty similar they diverge in the latest 4, these ones are also problematic to skip in my case

this is what is working for me

opencore-2020-08-26-142151.txt.zip this is my 061 log 🙂 not tested for now, but I think it will be the same.. before I have had the same problem with both OSX now I have to re clone my VM Catalina.. before I would like to solve my real problem in OSX

No I have my idea about ssdt only new open core and MMIO playing with these two I have posted all my logs and you can try with your MMIO address About SSDT I would like to explain better I have no skill to build any SSDT, so I can't do fo my self I do not like to add stuff under PCI tab and some SSDT functionality is possible to have using device properties in OC

Ok..good news playing with MMIO and with opencore 061 i have solved reboot/shutdown problem... now it is working as it must work

In attachement all MMIO I have tested. I can exclude many of them and only a few are problematic these are my logs: Itseems not related to my Nvidia problem MSI_TRX40 Pro-Logs.zip

thanks for this, but also in the past it was possible to install on OSX 10.14 , 10.15 and also in big Sur Nvidia driver with different level of difficulty to do this.. my problem is in High Sierra and bare metal I have had success to install fine ( but I can't reproduce a working method) For now I have no success and I have to boot without acceleration in bare metal No others of you is using Nvidia..so I am alone..and maybe I am doing some errors I can't debug 🙂

What I will write below is a bit OffTopic. I remind everyone, in particular those who read us but do not actively participate in the forum, that it is very important to respect some rules dictated mostly by common sense: 1) give due credit to people who share their experiences for free 2) not to steal, clone users' github without their direct permission The spirit that I would like to create and that in part I think is already in place is to share with all the people with a minimum of salt in the pumpkin (pumpkin is an acronym for head in Italian :)) our experiences on this new and fascinating possibilities we have with the TRX40 I hope you understand. I also take advantage of this OffTopic to remind you that any EFI posted is used at your own risk ... just a simple advice is valid ... do all your necessary checks before using the EFIs provided (kindly and free of charge) by the most 'willing 🙂 users

About your MMIO first two seems identical to mine tomorrow I will check better with a proper device than my mobile doryania guide will be updated i have said to the maintainer there was a problem with suggested value on Amd discord

Now I have understood sorry I am on my mobile only archivio. Zip is mine previous zip is a quote of your message on page 13

As side note npci 0x2000 should not used if you have 4g option in my MSI I can boot without npci and also with 4g on/off i do not also use any ssdt to boot

My efi can’t give that schema errors simply because there are not that voices you have that voices in 061 efi you previously used so do not mix stuff be sure to use a proper version weird the other things which happen if you Have done all in a correct way gigabyte seems to act in a weird mode maybe for bios culprit I can’t say more

and these will be the values: 0xE2100000 ----> 37926993920xE3180000 ----> 3810000896 Note I can't say if these is really related to NVRAm location....but these one are the correct locations for our TRX40 board

common problems for all are: 1)shutdown 2) reboot with this EFI system does not hang, but above points do not work well If EFI starts fine in your system you will find in EFI folder a txt file If you have had USB problems with this EFI you should have the same problems i do not use any of SSDT you are using, I have kept your ACPI folder as is I would also try without SSDT

attached a debug version for your system Add your SMBios data it is based on 060 debug (release) version Archivio.zip let me know

I miss your working EFI upload it so i can re upload it in debug mode thank you @meina222 it is not advisble to play with mmio without knowing what that address do i have seen on dortania guide they advice to use two address that it seems we both do not have i have asked some explanation i would like to understand which motherboard or bios has those address

Now i am out from my pc put if you want your working efi (fully working i mean) tomorrow morning i will upload the debug efi for your system if you search on your config applesecure boot and other name you can see in schema error description you can adjust your config it is not a debug version problem

You should use the same your working non debug Efi change boot folder and opencore.efi file with the same version (only debug) you can find on acidhantera github or download with OC EFI maker app you can find in download forum section Those error are a bad config and maybe you use a 061 version with a previosus config version To enable a proper debug on a debug version of opencore you have to put target value to a value of 69 default is 3 i think

@all could you post a debug open core.txt file of your booting rig in bare metal? I would like to see this part (MMIO Address) thank you: 21:464 00:015 OCABC: MMIO devirt 0xE2100000 (0x81 pages, 0x8000000000000001) skip 0 21:474 00:009 OCABC: MMIO devirt 0xE3180000 (0x81 pages, 0x8000000000000001) skip 0 21:483 00:009 OCABC: MMIO devirt 0xEF100000 (0x181 pages, 0x8000000000000001) skip 0 21:505 00:021 OCABC: MMIO devirt 0xFA180000 (0x81 pages, 0x8000000000000001) skip 0 21:515 00:010 OCABC: MMIO devirt 0xFA300000 (0x100 pages, 0x8000000000000001) skip 0 21:531 00:015 OCABC: MMIO devirt 0xFEA00000 (0x100 pages, 0x8000000000000001) skip 0 21:540 00:009 OCABC: MMIO devirt 0xFEC00000 (0x1 pages, 0x8000000000000001) skip 0 21:550 00:009 OCABC: MMIO devirt 0xFEC10000 (0x1 pages, 0x8000000000000001) skip 0 21:560 00:010 OCABC: MMIO devirt 0xFED00000 (0x1 pages, 0x8000000000000001) skip 0 21:571 00:010 OCABC: MMIO devirt 0xFED40000 (0x5 pages, 0x8000000000000001) skip 0 21:581 00:010 OCABC: MMIO devirt 0xFED80000 (0x10 pages, 0x8000000000000001) skip 0 21:596 00:014 OCABC: MMIO devirt 0xFEDC2000 (0xE pages, 0x8000000000000001) skip 0 21:606 00:009 OCABC: MMIO devirt 0xFEDD4000 (0x2 pages, 0x8000000000000001) skip 0 21:616 00:010 OCABC: MMIO devirt 0xFEE00000 (0x100 pages, 0x8000000000000001) skip 0 21:626 00:009 OCABC: MMIO devirt 0xFF000000 (0x1000 pages, 0x8000000000000001) skip 0 21:636 00:010 OCABC: MMIO devirt 0x4040000000 (0x10400 pages, 0x8000000000000001) skip 0 21:652 00:016 OCABC: MMIO devirt 0x8BB0000000 (0x10400 pages, 0x8000000000000001) skip 0 21:663 00:010 OCABC: MMIO devirt 0x8BE0000000 (0x10400 pages, 0x8000000000000001) skip 0 21:679 00:016 OCABC: MMIO devirt 0xD750000000 (0x10400 pages, 0x8000000000000001) skip 0 21:695 00:016 OCABC: MMIO devirt end, saved 1087664 KB

To avoid bios corruption, I would not use two quirks in booter for now first and last one this also help to have "only" a reboot on restart/shutdown selection.. I think bare metal is to try well..because, performance Is pretty the same in many task and with it we can have the chance to pass all stuff we want (PCIE card) Then it si very young this experience so some problems may occur (in my case I can't enable again my Nvidia driver in High Sierra 🙂

@meina222maybe they are looking here to achieve parameter they put in the guide 😉 without risking being too immodest ... this one created here is the best working and public and free information group for all TRX40 users. and the credit for this great result belongs to all of us 🙂 🙂

If you use some ssdt you have to revisit it because address changed

On second page of this thread you will find my config pretty similar to proxmox one only booter/quirks DevirtualizeMMIO on and patches in kernel the differences You can copy your proxmox efi on an usb pen with only the above differences

Latest available not beta works well as in proxmox

Sometimes usb does not help to solve problem yesterday I have solved problem of continue boot in recovery with clear cmos as you said me but I can’t have again gpu acceleration in high Sierra because not all nvidia kext are loaded this is a problem because it involves SIP and also nvram/web drivers script in proxmox, same disk, kexts are loaded fine