Leaderboard
Popular Content
Showing content with the highest reputation on 01/16/2021 in all areas
-
Buona sera a tutti, vi scrivo perchè ho un notebook HP 250 G7 CPU Intel Core i5 8265U @ 1.60GHz Kaby Lake-U/Y 14nm Technology Motherboard HP 8532 (U3E1) Graphics Generic PnP Monitor (1920x1080@60Hz) Intel UHD Graphics 620 (HP) Audio Realtek High Definition Audio. Pensate che si possa installare OSX Catalina? Anticipatamente ringrazio , File1 point
-
<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 grigi1 point
-
non funge @carlo_67 stessa cosa per @AlexAMD ma mi sa che se trovo qualcuno vendo l'unita centrale ma non so neanche quanto chiedere1 point
-
I will simplify those lists of devices and see system must start also without nothing there ...1 point
-
hum weird I have only disabled your huge device properties list.. if you compare with your config posted1 point
-
1 point
-
@cleverhomedownload PowerTool app from our download area (always @Gengik84app) π see this videos to understand better: compare also with my files: txt files are from PowerTool save plist is my device properties, you can check here how you have to name stuff π Pci Devices.txt.zip DeviceProperties.txt.zip my device.plist.zip1 point
-
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:1 point
-
Hi π (obscure your above pictures (it is better if it is your name π π ) I use to have in my EFi both VirtualSMC and FakeSMC kext..but only one enabled Ii do many test so I have both for this) in the past that kext solved memory error popup..I can't say more because I use iMacPro1.1 Smbios happy you solved many of your initial problems! to other tasks to do..you can now follow general discussion for trx40 π1 point
-
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 , sorry1 point
-
1 point
-
you have to try to put all kext you have had in initial your experiment (about wifi / BT related ones I mean) and see if it works1 point
-
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 π1 point
-
1 point
-
1 point
-
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 π1 point
-
please disable from bios wifi Bluetooth and try again no log need1 point
-
1 point
-
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 )1 point
-
no I mean a more simple ones usb mouse/keyboard I think there is something wrong using those SSDT and maybe that part is not well functioning now by the way, sorry for my pic device properties π forgot to remove it 16:633 00:018 OCABC: MMIO devirt 0xCB100000 (0x81 pages, 0x8000000000000001) skip 1 16:652 00:018 OCABC: MMIO devirt 0xD7180000 (0x81 pages, 0x8000000000000001) skip 1 16:671 00:018 OCABC: MMIO devirt 0xE3180000 (0x81 pages, 0x8000000000000001) skip 1 16:690 00:019 OCABC: MMIO devirt 0xE3300000 (0x100 pages, 0x8000000000000001) skip 1 16:709 00:018 OCABC: MMIO devirt 0xEF100000 (0x181 pages, 0x8000000000000001) skip 1 16:728 00:018 OCABC: MMIO devirt 0xFEA00000 (0x100 pages, 0x8000000000000001) skip 1 16:747 00:018 OCABC: MMIO devirt 0xFEC00000 (0x1 pages, 0x8000000000000001) skip 1 16:767 00:019 OCABC: MMIO devirt 0xFEC10000 (0x1 pages, 0x8000000000000001) skip 1 16:786 00:019 OCABC: MMIO devirt 0xFED00000 (0x1 pages, 0x8000000000000001) skip 1 16:805 00:019 OCABC: MMIO devirt 0xFED40000 (0x5 pages, 0x8000000000000001) skip 1 16:824 00:018 OCABC: MMIO devirt 0xFED80000 (0x10 pages, 0x8000000000000001) skip 1 16:843 00:018 OCABC: MMIO devirt 0xFEDC2000 (0xE pages, 0x8000000000000001) skip 1 16:863 00:019 OCABC: MMIO devirt 0xFEDD4000 (0x2 pages, 0x8000000000000001) skip 1 16:882 00:019 OCABC: MMIO devirt 0xFEE00000 (0x100 pages, 0x8000000000000001) skip 1 16:901 00:019 OCABC: MMIO devirt 0xFF000000 (0x1000 pages, 0x8000000000000001) skip 1 16:920 00:019 OCABC: MMIO devirt 0x2040000000 (0x10400 pages, 0x8000000000000001) skip 0 16:939 00:019 OCABC: MMIO devirt 0x3830000000 (0x10400 pages, 0x8000000000000001) skip 0 17:022 00:082 OCABC: MMIO devirt 0x5020000000 (0x10400 pages, 0x8000000000000001) skip 0 17:041 00:019 OCABC: MMIO devirt 0x6810000000 (0x10400 pages, 0x8000000000000001) skip 0 MMIO posted above in your log are good not changed with your latest config and BIOS settings1 point
-
1 point
-
in my trx40 help users history..I have had only a trx40 user unsuccessful π @thedantee but NVIDIa and some sip problems were a pain to adjust Your system should start easily...I have only some doubt about Samsung 970 pro firmware..but unsure if this could be the culprit of our NOT successπ1 point
-
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 π1 point
-
it is uefi so use in BIOS CSM off And 4G On always when testing and if you have time put here all settings (screenshot) of your bios settings1 point
-
could you execute GPUZ on your windows os and post the first screenshot here? thanks1 point
-
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 luck1 point
-
finish to try the others.. I have a big doubt also π your GPU has a UEFI bios? could you try to enable CSM in ASUS bios and see if it works in a different way? pS out of ideas1 point
-
Archive.zip replace the config.plist and put ssdt you find in zip file inside ACPI folder (thanks @Gengik84to advice to try this)1 point
-
config.plist 4.zip this is last thing to try by now..with opencore) I have no others ideas to try for now... sorry1 point
-
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 firmware1 point
-
ehm bios of your Samsung 970 is updated to work with OS X? I have also this doubt1 point
-
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.zip1 point
-
1 point
-
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 properly1 point
-
@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 thanks1 point
-
No Post your mmio proper list It seems so but to be sure we have to wait1 point
-
1 point
-
first try to delete matchOS data in your config.. Follow also indication @iCanarodid in OP because he has a similar CPU than your π post also your debug log if system hangs1 point
-
if possible when we say..it works or it doesn't work a config.plist, we have also specify well with which clover commit exactly it is work or not IE I have posted a plist which generate some of the plist posted here and also on IM working with Big Sur my plist does not work anymore in 5125 in my rig in 5124 it is working the same so I think we have to be more clear about config and commit used if possible1 point
-
@obus post here your Original ACPI and some people of goodwill will help you π On IM it is impossible to navigate these days π1 point
-
I am using both but maybe VboxExt2-64 is not mandatory for boot no attachment here Ha scritto dopo 15 secondi: SMC21 point
-
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 it1 point
-
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 run1 point
-
1 point
-
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 :)1 point
-
Ciao obus It seems we can not avoid using fakecpuid.. Probably also others like Broadwell Ep 0x40764 (I don't remember well) do the same job It is very strange also you can use Appleintelinfo kext because in new I9 architecture it is not working well if MSR is checked in option Analyzing it you miss C3 states in output but it is pretty normal Previously when I had an unsupported cpu there was a kernel patches by SammlerG to activate C3 output, in real use however no difference to come back to our "issue" I am searching a kernel patch for adding cpu id in kernel section..but I can't find it Also it would be the same thing of using fakecpuid, so no great catch No I do not thing it is a clover bug? but also it is strange if you use KernelXCPM flag is not working for you.. this flag was an automated way to patch unsupported Cpu we had asked the past to clover's coders to not use in automatic way. My advice is to launch appleintelinfo and use your system loaded/unloade for few time and see if all CPU pSTATES come out then evaluate if for you it is better to use a Broadwell EP fakecpuid or Skilake X in terms of stability and performances Hoping Apple programmers include your cpu in next OSX release Ha scritto dopo 1 minuto 51 secondi: PS remember also to try unlock MSR bios option to see if you can avoid using MSR patch or any kernel patches Using a fakecpuid you are using a way to use XCPM of another family of CPU But it not should be your case because Xeon W family is A CPU supported in iMac Pro...( ;( )1 point
-
Sorry @obus your first MSR patch togheter fakecpuid produces 1 for both terminal command?1 point
-
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 aspect1 point
-
in processor tab you see unknown or your processors? obviously if you have not modified it manually..as I do in my case1 point
-
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 :)1 point