fabiosun
-
Posts
10,953 -
Joined
-
Days Won
496
Content Type
Profiles
Forums
Events
Downloads
Everything posted by fabiosun
-
prova a selezionare come da immagine mostra tutti i device (se già non sei cosi')
-
ciao e benvenuto leggendo le due prime righe..avendo fatto tutto bene come dici..sembrerebbe impossibile dare una mano :) Scherzi a parte, se puoi metti in firma il tuo hardware e posta la cartella EFI che stai utilizzando (senza la cartella APPLE o i temi che hai in uso) Sarebbe anche utile anche solo una foto di dove si riavvia, che chi sa e puo' ti darà una mano a sistemare grazie
-
release [Release] macOS Big Sur 11.5-11.5.1-11.5.2
fabiosun replied to Gengik84's topic in General Discussion
@tuxyun po' in OT e mi scuso hai anche provato clover? 😉- 51 replies
-
- 1
-
-
- build 20g71
- 20g80
- (and 1 more)
-
I'm glad you succeeded Allow me to give you a little advice use a debug version of opencore until you are sure everything is fine for your system Activate debugging by putting the value of 67 in place of 3 (debug/target) Then check if in the debug the mmio you have set is on skip 1 If you have any problems check our main thread All the TRX40 users have passed through this forum who in one way or another now have their system working! So here's the guide! 🙂 😛
-
I do not think Dortania is a good guide for trx40 users 😉 Problem could be high Sierra related (many problems with trx40 and Nvidia drivers) Also usb in HighSierra for us is a problem And I'm talking about a topic that I tried on my skin, wasting hours on it (I had a TitanXp GPU) try with this config.plist (rename it and put ssdt in ACPI folder also I have enabled dummypowermanagement kext Archive.zip if it does not work try with a newer OS or download again HS installer from scratch
-
Ei @jude🙂 Your MMIO is fine Explain what do you want to achieve and also which problems your rig has now I do not understand well if it boots or not 🙂
-
I take back this interesting conversion made by iGPU, making only a small modification. In the empty slots I added: Type = DDR4 if clover's config plist is left blank in that memory section we have a non-destructive formal error. to download : Clover Config Plist Validator Clover_memory_mapping.plist.zip
- 3,969 replies
-
- 2
-
-
-
- amd vanilla patches
- amd kernel patches
- (and 3 more)
-
ah also this if you change some bios configuration MMIO list could change So we have to start from a proper bios configuration and then start to configure your plist
-
@jude please put your hardware in signature in your profile option. about your MMIO, see this: 0xC2500000 (0x81 pages, 0x8000000000000001) skip 0 0xC3580000 (0x81 pages, 0x8000000000000001) skip 0 0xDA100000 (0x181 pages, 0x8000000000000001) skip 0 0xFA180000 (0x81 pages, 0x8000000000000001) skip 0 0xFA300000 (0x100 pages, 0x8000000000000001) skip 0 0xFEA00000 (0x100 pages, 0x8000000000000001) skip 0 0xFEC00000 (0x1 pages, 0x8000000000000001) skip 0 0xFEC10000 (0x1 pages, 0x8000000000000001) skip 0 0xFED00000 (0x1 pages, 0x8000000000000001) skip 0 0xFED40000 (0x5 pages, 0x8000000000000001) skip 0 0xFED80000 (0x10 pages, 0x8000000000000001) skip 0 0xFEDC2000 (0xE pages, 0x8000000000000001) skip 0 0xFEDD4000 (0x2 pages, 0x8000000000000001) skip 0 0xFEE00000 (0x100 pages, 0x8000000000000001) skip 0 0xFF000000 (0x1000 pages, 0x8000000000000001) skip 0 0x10000000000 (0x10400 pages, 0x8000000000000001) skip 0 0x3CB90000000 (0x10400 pages, 0x8000000000000001) skip 0 0x3CBC0000000 (0x10400 pages, 0x8000000000000001) skip 0 0x69750000000 (0x10400 pages, 0x8000000000000001) skip 0 You can leave to skip 0 latest four to converti hexadecimal in decimal you can use a scientific calculator (windows or OSX are fine) or download powertool app from our download area and using it to convert in decimal value I will do first 3 for you 0xC2500000 = 3260022784 0xC3580000 = 3277324288 0xDA100000 = 3658481664 go on in this way then post here again also a your complete config.plist Thank you
-
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
-
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
-
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 🙂
-
Thank you @SavageAUS i will check your debug log later was it useful for you old topology patch to have success?
-
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
-
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'
-
https://github.com/trulyspinach/SMCAMDProcessor/releases/tag/0.7 new version for AMD Power Gadget
- 3,969 replies
-
- 2
-
-
-
- amd vanilla patches
- amd kernel patches
- (and 3 more)
-
this is wrong post your debug log
-
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
-
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
-
@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
-
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
-
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
-
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
-
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 😉
-
@SavageAUSin clover config.plist I can't see any SMBios data... Can you hide only sensible data and live your SMBIOS?
