Jump to content

fabiosun

Supervisor
  • Posts

    10,511
  • Joined

  • Days Won

    434

Everything posted by fabiosun

  1. also about this if you read well only few users need of this patch. newer one has a problem with clover masking system , and you can also see in AMD OSX Github why they left Clover without an official patches support.. Then is it possible to have it working well..and we have this from months
  2. this statement is no correct and using masks as some people do in a fancy way is risky! 😉 Thanks for writing to us too after reading a lot from us. If you want to put credits and a link to this forum we are happy .. but don't feel obligated to do it It is not needed If SavageAUS had come to macOS86 right away, the problem would have been solved right away We only lacked his type of problem Patches were never "borked" for any of us..just using "yours" could that error happen. But it is important that it is now clear how clover works to all people who have their system working with Opencore have a nice day! ps: by the way, can you check if do you have multiple accounts in our forum? I see your avatar and alpha name in different users. if you have and you decide which one to use, an admin will correct this situation! Thank you
  3. Yep you are using patches posted in previous config. If you use only Big Sur and Monterey you can also disable patches 0,6,16,17 About preferred bootloader I do not like Clover, but I prefer to have the chance to have a choice. I don't like Clover because since using the opencore method to work it has several unresolved problems from R5124, which I have reported in a couple of issues to the developers. The GetOSDetection problem is very serious especially for us AMD users. But that said, thank you for posting your problem here as well. As a case study I was missing your combination of problems with clover: ) We just doubted it was a topology patch issue, but having read that everything worked on opencore, we understood that there was a chance for you too. On the other hand, Clover has always worked for us only by applying a little patience and workaround 🙂
  4. Thank you @SavageAUS i will check your debug log later was it useful for you old topology patch to have success?
  5. Hi @SavageAUS with this clover EFI insert only in it this config.plist config.plist.zip with the help of @AudioGodwho have a X570 motherboards which needs of a working topology patch..we have had success without this patch he has same your problem with topology error in verbose we see on your verbose (he has a 12 cores 5900x) so it should pass also for you this error..if so then you can refine better with all stuff you use in your attached here clover working EFI In clover we can't use new topology patch but algrey old ones work well also in Monterey b4
  6. con che sistema operativo, qui sei in configurazioni di riferimento, se mi dici un sistema spostiamo in generale di quel sistema Hai provato con o senza weg? oppure a mettere un SMBIOS tipo MacPro7.1 se la tua macchina riesce a partire con questo? se vuoi, posta il tuo config eo se non hai messo il -v prova, magari si capisce di piu'
  7. https://github.com/trulyspinach/SMCAMDProcessor/releases/tag/0.7 new version for AMD Power Gadget
  8. and this should work almost fine in Big Sur (if previous your EFI was working in Big Sur..) and maybe also in latest beta if old topology patch is good EFI-2-2.zip inserted here old topology patch you used ps do not modify with clover configurator this config
  9. also post config.plist you used in good boot with clover 5136 I think sorry I have it but you say 5138--and in log I see 5136 for this I have done a mistake 🙂 Thank you
  10. @SavageAUSadded here a patch which we do not use (Topology patch) this is one of the Problematic patch I see people try to solve in very weird ways and it is not advised to do in that way In all system tested here it is not mandatory to boot. I should do a similar test with opencore, disabling ProvideCurrentCPUInfo add two patches for vid and tsc and try without adding topology patch these three patches are included in OpenCore quirk. in clover it is not present and if topology patch I inserted here does not work could be a problem always if you like to try then post debug and hang photo if it is different EFI-2.zip
  11. config-02_SAVAGEAUS.plist.zip then try this I added Macpro7.1 Smbios data and minimal modify post always debug for BS and MR thanks
  12. doesn't start? could you post a working debug with Big Sur and clover? GetOSDetectio is fine for both system so problem stays in another part @SavageAUScould you post a photo where it hangs for both systems? thank you
  13. config-01_SAVAGEAUS.plist.zip @SavageAUS rename this and put inside your smbios data only I have enabled debug try to start only one time Big Sur and then also Monterey post debug you will find in your misc folder thanks
  14. Ok I have read on IM you have done many test with others user..you should have only to do a simple verify for me: see plist in your preboot partition if it is correct for system you are trying to boot: https://github.com/CloverHackyColor/CloverBootloader/issues/283#issuecomment-718109276 as explained here from Clover Devs (for many user this is the main problem to boot fine) if you have this problem @carlo_67could explain how to solve easily if you do not understand jief example however I will try to give you a config to try to boot with few patches only on bs for now then will proceed if you like for newer system 😉
  15. @SavageAUSin clover config.plist I can't see any SMBios data... Can you hide only sensible data and live your SMBIOS?
  16. ciao @Marcocrambenvenuto prova a postare il tuo config.plist e se qualcuno conosce se il tuo notebook e' compatibile con High Sierra ti darà una mano quel messaggio indica che si blocca nella fase iniziale e non e' di aiuto
  17. in a rush searching I have found this in his post: https://www.macos86.it/applications/core/interface/file/attachment.php?id=26325 you can examine this configs to understand a bit more "how to"
  18. Ciao @jude your EFi is a bit distant to be working for your system Dortania guide is not so precise for trx40, and you should read a bit here (where trx40 system start to work first time with proxmox virtualization and then with memory manger supports with opencore also in standard bare metal way) things to do if you like should be these: 1)create your MMIO whitelist (follow here @iGPUguide: 2) with bit patience search here for @Driftwooduser, because you can find here his EFI that it is a good point to start if you find his EFI you can change on his config MMIO whitelist with yours (but it could work also with his one (better to use yours)) these two one are steps in my opinion you have to do to have your system working at its best I suggest to install from Catalina or greater OSX, because USB better support than macOSHigh Sierra or Mojave!
  19. Hi @jude welcome here post your config.plist and your efi if you like because with this we can understand if you did all the initial steps to try to install and boot fine Usually you have to define your mmio whitelist and others stuff to have success
  20. @dreamwhitenon sono solo graditi i link e il consigliare metodi di installazione leggermente opachi come quelli che si utilizzano nelle "bestie" ma il forum che citi e' gradito per le informazioni utili che puo' dare.. interessante Comunque questo argomento
  21. @eniac quella e' una schermata di OpenCore Add device Properties
  22. No @tuxy purtroppo il PR di Shaneee non e' stato ancora approvato devi trovare quello e compilarlo da te per avere a disposizione alcune patches incluse nel PR mi pare di averlo scritto nel thread internazionale..nel caso basta che vai sul GitHub di Opencore e vedi nei PR chiusi eccolo https://github.com/acidanthera/OpenCorePkg/pull/277
  23. @SavageAUS thank you to come back here Yes , if possible I would like to see a your working EFI with BigSur both with Clover bootloader and OpenCore If we start from here in a couple of tries we can have succes also with your rig
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.