Leaderboard

Grande, Domani ci provo Grazie

<dict> <key>AAPL,slot-name</key> <string>Internal@0,1,1/0,0</string> <key>device_type</key> <string>Non-Volatile memory controller</string> <key>model</key> <string>NVMe SSD Controller SM981/PM981/PM983</string> </dict> questo e' il tuo disco Samsung inseriscilo in Device Properties nel config.plist...dopo aver fatto un backup del config stesso e vedi se l'icona ti diventa interna (se e' arancione <dict> <key>AAPL,slot-name</key> <string>Internal@0,1,2/0,0/1,0/0,0</string> <key>device_type</key> <string>Non-Volatile memory controller</string> <key>model</key> <string>E12 NVMe Controller</string> </dict> questo invece e' l'altro Nvme..puoi fare la stessa cosa sono in windows e al momento non ho un plist editor da usare... ma e' abbastanza semplice fare da se in questo caso disaabilita anche external icons e vedi se almeno questi due ti diventano grigi

non funge @carlo_67 stessa cosa per @AlexAMD ma mi sa che se trovo qualcuno vendo l'unita centrale ma non so neanche quanto chiedere

I will simplify those lists of devices and see system must start also without nothing there ...

hum weird I have only disabled your huge device properties list.. if you compare with your config posted

config.plist.zip try this, but you have too many stuff in device properties 🙂 backup your config before I can't read your IOREG by now because I have a different software to read it sorry use this if you want to save it

fiuuu it is hackintool 🙂 joking this for me is wrong I do not thing is an error of Hackintool you have to check well

hi @cleverhome I'm happy that Dortania is adjusting the game regarding our platform, maybe they are following our progress too 🙂 Regarding MMIOs, each motherboard has its own and even the same motherboard with a different Bios version can have different ones. It is important to use and calculate your own and not to take those posted by other people. The explanation is a little out of our thread and my knowledge, I can tell you that OSX writes on some parts of memory and it can happen that some devices do when used. If these memory areas are not available for OSX, we have problems (ie kernel panic or other problems) for that we tend to where it is possible to give them back to OSX management by putting them to skip = 1) As for Device properties, I personally use an app that @Gengik84 is developing Soon it will be available for everyone in our download area. For the moment it is possible to use either systemsearch (an app in the download area) or Hackintool, an app that provides you with the plist to insert in your config.plist to get this:

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

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 🙂

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

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

ok so, by now no Catalina OS and No Big Sur OS complete first step installation when you choose from recovery install OS With your Work with Big Sur EFI , could you change USB ports for mouse and keyboard? I think problem is there and we have to understood why your system loose Mouse and keyboard at early installation step things I can say is that MMIO are fine and your problem it is not MMIO dependant Your motherboard should have different USB controllers (as media and AMD I mean) you can try to swap ports has I said above then I do not know if this are useful for you (I think no) for sure you can avoid to use first one because I do not think we have more than 15 USB ports for controllers (this is an Intel problem not AMD) and you have also a quirk for this in config.plis (XhciPortLimit I mean, you can not use USBinject kext and eventually put to yes this kernel quirk) I am trying to see how to solve I will try to simplify more your kext folder and config also I will try Dummypower quirk on/off in your emulate kernel config.plis section (for me not necessary..I do not know on Asus )

EFI.zip if you want try with this always with wired mouse and keyboard

have you a mouse and USB keyboard?

thanks for the zip 😛 never seen a more complete bios for a trx40 motherboard great 🙂 MSI bios is a toy in front of this but , I can't see any parameter could avoid the fine booting of it in OSX I know as media SATA controller is not supported by OS X if you do not use any kext.. your problem is before however I would like to suggest to unmount all disk and try only with one name on your M1_1 slot and put all to auto after a load optimize settings.. but..it is a "desperate" try 🙂

you have to try also with CSM OFF Sometimes it depends also from your GPU your system hangs too fast in an early stage.. have you the same Asus Bios of @valmeida? good luck

No sorry not possible that kind of help my advice is to try with another disk if you can't define better if is a firmware related problem Your system should start easily as we did with @valmeidasome months ago so problems is elsewhere and I can't figure where by now sorry by the way..MMIO is important for post installation steps for a full functionality in installation steps you could also null all of the to zero have you 4g parameter in bios? ON/off

Archive.zip replace the config.plist and put ssdt you find in zip file inside ACPI folder (thanks @Gengik84to advice to try this)

config.plist 4.zip this is last thing to try by now..with opencore) I have no others ideas to try for now... sorry

usually in Windows with Samsung magician utility I do not know if it could help in the past there was a problem with some Samsung NVME firmware

ehm bios of your Samsung 970 is updated to work with OS X? I have also this doubt

ok try latest EFi I have put above change completely the previous one (backup it ) below two configs are for opencore EFI I have nulled AMD Power tools kext for now try with Opencore EFI config.plist 3.zip config.plist 2.zip

Big Sur release or beta?

MMIO are loaded fine try this if you want config.plist.zip

config.plist.zip your bios settings seem to be good try only to enable ERP after first try of above config if it fails in this config I have added for you all MMIO resulting from your previous debug If you change some parameters on bios they could change and you have to recalculate them properly

@cleverhomeHi try this and see if it does better things EFI_cleverhome.zip try with CSM Disabled in your Bios then if it starts or not post debug log thanks

@cleverhome if your system never booted in OS X post here if you want in exact order this stuff: 1) your bios version and all configuration settings 2) use an OpenCore debug version to have your exact MMIO list 3) DO NOT use as is other user EFI after this, we have to simplify a bit your EFI to start, then, when it will boot, you can add all you need As I have said to @valmeidawhen I helped him with his rig, your motherboard in my opinion is the best one available... So it works and maybe better of others...

for Clover's Lovers 🙂 Do not do it at home 🙂

@jsl2020 if you want post here your working config with OpenCore and your actual clover EFI you want to try to boot 🙂

Proxmox / OSX Pros: Stability No need of any kernel patches to boot OSX All apps are working well without any need of patching (Adobe suite, many audio plugin, all stuff intel based) Pretty same performances in both CPU/GPU benchmarks vs vanilla patches method you can install and do all by yourself..without waiting from others to discover new kernel patches Cons: The need of a linux system PCIE passthrough success dependant of many factors For AMD GPU reset bug Audio problems (in some situations) Vanilla Patches method Pros: All AMD users use this method from the start Stability less learning curve process to setup a "patches & play" system 🙂 Cons: no availability of a clear method to find kernel patches by yourself, and, if no maintainer available..no JOY 😉 Kernel Patches could change and if you like to update often your rig...could be a problem No support from boot loader Devs for AMD system A lack of support for old OSX as High Sierra 🙂 Some App have to be patched and some time a bit of functionality could be lost I have created this thread because many unexperienced users ask in private or DM about this If you want to share your experiences to help people from your point of view you are welcomed as always😉

config2.plist.zip config1.plist.zip

@obus post here your Original ACPI and some people of goodwill will help you 🙂 On IM it is impossible to navigate these days 😉

yes it is the best we can reach by now You cpu is well represented I think you have a 14 cores? (14/28) hoping in a better support for app devs in new VirtualSMC kext technology Ha scritto dopo 2 minuti 13 secondi: you have a different HWsensor I think https://sourceforge.net/projects/hwsensors3.hwsensors.p/">https://sourceforge.net/projects/hwsens ... sensors.p/">https://sourceforge.net/projects/hwsensors3.hwsensors.p/ try this if you want no need to install it

ciao Obus you and yapan4 have to understand if your MSR0xe2 is really unlocked for all cores of your cpu to do this task you can use @vit9696 tools first of all VirtualSmc.efi in driver64uefi then delete your fakesmc and all kext related to it (sensors, acpi an so on) put in kext/others VirtualSMC.kext SMCProcessor.kext then put https://github.com/acidanthera/AptioFixPkg/releases Aptiofix..../tools/VerifyMsrE2.efi inside clover/drivers64uefi you should see some lines before clover bootmenu like this one if you see all your cores and similar text you have a really unlocked bios 🙂

Use other software to check (Istat menu IE) and test with cinebench single core or Geekbench or cinebench graphics test with all of this you will use less cores and frequency should bounce higher

Ciao @obus IPG graphics are pretty similar You should do also 3 test if you can Geekbench (CPU and GPU) in free version only OpenCL is available and it is ok then in cinebench do some test also for gpu (as I was asking before) and for cpu single core like you can see in my attachment I am asking because I can't see in both IPG graphics higher freq than 3.3 or 3.4 I think In some condition you should see some peak around 4.0 and more however outpinfo show all states so your cpu scales well in both case (few missing states are irrelevant..they could come far in time during testing Ha scritto dopo 7 secondi: Ha scritto dopo 1 minuto 9 secondi: then important other things..stability is the same? temperature seems pretty identical in both cases Ha scritto dopo 9 minuti 58 secondi: Ha scritto dopo 4 minuti : during single CPU and Graphic cinebench run

load and idle load and idle normal usage...

check your PM

yep another input https://ark.intel.com/products/130046/Intel-Xeon-W-2175-Processor-19_25M-Cache-2_50-GHz">https://ark.intel.com/products/130046/I ... e-2_50-GHz">https://ark.intel.com/products/130046/Intel-Xeon-W-2175-Processor-19_25M-Cache-2_50-GHz see your CPU specs turbo for few cores is @4300 so CPU P states must be 43 and you have to see all in CPU PSTATES your cpu has 14 cores / 28 Threads this means you have to see in CPU C6 states all from 0 to 27.. when you see this situation without any hole..you are gold (technically speaking) :) in Italian way is simple to figure out this technically speaking..I don't know in English if it is the same :)

uhm for me today is enough if you can try boot strap togheter fakecpuid..and test if XCPM and Frequency Vectors are set to 1 good evening :) Ha scritto dopo 40 secondi: tomorrow we will try other solution :)

It is the one you use in your config.plist use it togheter boot strap and see (without fakecpuid obviusly) :) Ha scritto dopo 1 minuto 35 secondi: if possible put also here actual efi you are using in the tries Thanks Ha scritto dopo 5 minuti 53 secondi: obus, if you can download from here this tool https://www.macos86.it/MacOS86_Downloads/Applicazioni/Info/Hack_Info.zip">MacOS86_Downloads/Applicazioni/Info/Hack_Info.zip">https://www.macos86.it/MacOS86_Downloads/Applicazioni/Info/Hack_Info.zip post zip it produce. in this way is it possible to check other aspect

in processor tab you see unknown or your processors? obviously if you have not modified it manually..as I do in my case

ok from from clover boot menu press O and disable alternatively kernel patches above leave only and always active boot strap and cycle the others ie bootstrap scope bootstrap core boot strap MSR boot strap pkg and see also, when system starts try to open terminal window and run: sysctl -n machdep.xcpm.mode and sysctl -n machdep.xcpm.vectors_loaded_count post results

first try in config 1 state flag Kernel PM on config.plist with clover configuration Ha scritto dopo 4 minuti 18 secondi: then try this kernel patches togheter bootstrap patch find 31D2E87E FCFFFF replace 31D29090 909090 comment_xcpm_smt_scope find 31D2E891 FCFFFF replace 31D29090 909090 comment_xcpm_core_scope find 31D2E8AE FCFFFF replace 31D29090 909090 comment_pkg_core_scope Ha scritto dopo 1 minuto 16 secondi: do not do any changes in bios during this test also we know using fakecpuid is helping..but we have a goal to avoid it :)

ciao obus Have you tried these two config .plist?