Jump to content
ErmaC

Clover General discussion

19,245 posts in this topic

Recommended Posts

1 minute ago, Slice said:

Drag the file to trash.

 

Ok. I did that. But Shell.inf is created for each version in EFI/CLOVER/TOOLS, I don't know why.

Share this post


Link to post
Share on other sites
Advertisement
10 hours ago, pkdesign said:

I just built v 4779 using BuildClover command and I still can not boot my legacy machine. All I see it a blinking cursor.

 

I do not have APFS driver in kext since I don’t use it. 

There should be more information about the issue.

Did you try other boot6 or boot7 files? From previous revisions.

Did you set Boot->Debug=YES to get a debug.log?

What efi drivers do you have?

3 minutes ago, Matgen84 said:

 

Ok. I did that. But Shell.inf is created for each version in EFI/CLOVER/TOOLS, I don't know why.

Because of build script.

Share this post


Link to post
Share on other sites
56 minutes ago, Slice said:

Because of build script.

 

I've the same Shell.inf file when I use Makepkg from Source :cry:  I keep searching

 

EDIT: Same issue with Clover Release download from SourceForge

Edited by Matgen84

Share this post


Link to post
Share on other sites
21 hours ago, ellaosx said:

it wont hurt to be in there. or add a command just before the mkpkg to delete it in your script.

 

Thanks :) I can do that in my scripts (Build_clover.command and Dids script). 

 

As I said before  Clover Release download from SourceForge has the same Shell.inf file in EFI/CLOVER/Tools. 

 

EDIT: Thanks @Slice for remove Shell.inf from Clover Package source in commits r4780

Edited by Matgen84

Share this post


Link to post
Share on other sites

For some reason when I have an APFS volume present, Clover takes a very long time to display the GUI (30+ seconds). I am using ApfsDriverLoader and there is no delay when booting without an APFS volume present. In the preboot log it looks like [InitScreen] line is 47 seconds. Any ideas?

preboot.log

Share this post


Link to post
Share on other sites

So I have enabled -v on my clover config.plist but it's too fast to see the messages. Basically, I'm getting a boot loop and wants to see what's causing it. Is there a flag that prevents the auto restart on kernel panic?

 

Thanks!

Share this post


Link to post
Share on other sites
9 hours ago, mrjayviper said:

So I have enabled -v on my clover config.plist but it's too fast to see the messages. Basically, I'm getting a boot loop and wants to see what's causing it. Is there a flag that prevents the auto restart on kernel panic?

 

Thanks!

debug=0x100 keepsyms=1

Share this post


Link to post
Share on other sites
On 11/28/2018 at 2:51 AM, Slice said:

There should be more information about the issue.

Did you try other boot6 or boot7 files? From previous revisions.

Did you set Boot->Debug=YES to get a debug.log?

What efi drivers do you have?

I reinstalled 4779 and was not able to boot again. I never get past a solid cursor on screen after POST so there is no debug file to provide for that.

 

I copied boot file from my 4741 installation in to the 4779 EFI and I was able to boot.

 

These are the drives/kexts I have installed:

 

drivers64
FSInject-64.efi
HFSPlus-64.efi
SMCHelper-64.efi

 

kexts
FakeSMC.kext
realtekALC.kext

 

Attached is the debug file from the successful boot.

debug.log

Share this post


Link to post
Share on other sites
18 hours ago, mrjayviper said:

So I have enabled -v on my clover config.plist but it's too fast to see the messages. Basically, I'm getting a boot loop and wants to see what's causing it. Is there a flag that prevents the auto restart on kernel panic?

 

Thanks!

 

9 hours ago, Slice said:

debug=0x100 keepsyms=1

 

Yeah, you can also easily use these options from the spacebar menu when a boot entry is selected as well.

1 hour ago, pkdesign said:

I reinstalled 4779 and was not able to boot again. I never get past a solid cursor on screen after POST so there is no debug file to provide for that.

 

I copied boot file from my 4741 installation in to the 4779 EFI and I was able to boot.

 

These are the drives/kexts I have installed:

 

drivers64
FSInject-64.efi
HFSPlus-64.efi
SMCHelper-64.efi

 

kexts
FakeSMC.kext
realtekALC.kext

 

Attached is the debug file from the successful boot.

 

Your problem is caused by the firmware emulation if you are not even getting a debug.log and replacing boot with a previous version works. It's much harder to debug that but since you gave a range of revisions where the change occurred that is causing the issue, I imagine it will be easy to find any changes that may have been made to the legacy firmware emulation that are responsible for the issue.

Edited by apianti

Share this post


Link to post
Share on other sites
7 hours ago, pkdesign said:

Attached is the debug file from the successful boot.

debug.log

 

I believe compilation with XCODE 10.1 is the problem.  From your debug log, you are compiling Clover with XCODE 10.1 (with toolchain set to XCODE8) on your system... 

 

Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/pkovacs/src/edk2/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 9 | OS: 10.13.6 | XCODE: 10.1]

 

I already mentioned in this post that other XCODE versions eg 8.2.1, 8.3.3, 9.2, or GCC5.3, generate working boot6 and boot7 for my legacy desktop (system 2 in signature) but not XCODE 10.1 ---> boot hanging on stuck underscore "_" symbol.  Also interesting to note that the officially released Clover r4741 was compiled with XCODE 8.3.3 but r4769 (which also fails for your system) with XCODE 10.1.

 

 

4 hours ago, apianti said:

Does XCODE 10.1 build previous revisions to r4761 without issue? Or does it not build a valid boot firmware at all? Are the different build rules for XCODE 10.1 causing the problem?

 

No, still bad boot6,7 if Clover r4760 compiled with XCODE 10.1 (toolchain set to XCODE8, edk2 r27956).  I think the problem/bug is intrinsic to XCODE 10.1.

Edited by fusion71au
Extra info for @apianti

Share this post


Link to post
Share on other sites

Does XCODE 10.1 build previous revisions to r4761 without issue? Or does it not build a valid boot firmware at all? Are the different build rules for XCODE 10.1 causing the problem?

Share this post


Link to post
Share on other sites
On 11/29/2018 at 1:48 AM, scj312 said:

For some reason when I have an APFS volume present, Clover takes a very long time to display the GUI (30+ seconds). I am using ApfsDriverLoader and there is no delay when booting without an APFS volume present. In the preboot log it looks like [InitScreen] line is 47 seconds. Any ideas?

preboot.log

Do you use a NVMe drive? The same happened to me. I use apfs.efi from 10.13.0 again as it boots way faster. But please somebody have a look into this? NVMe drives should also boot faster isn't it?

Share this post


Link to post
Share on other sites
14 hours ago, fusion71au said:

 

I believe compilation with XCODE 10.1 is the problem.  From your debug log, you are compiling Clover with XCODE 10.1 (with toolchain set to XCODE8) on your system... 

 


Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/pkovacs/src/edk2/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 9 | OS: 10.13.6 | XCODE: 10.1]

 

I already mentioned in this post that other XCODE versions eg 8.2.1, 8.3.3, 9.2, or GCC5.3, generate working boot6 and boot7 for my legacy desktop (system 2 in signature) but not XCODE 10.1 ---> boot hanging on stuck underscore "_" symbol.  Also interesting to note that the officially released Clover r4741 was compiled with XCODE 8.3.3 but r4769 (which also fails for your system) with XCODE 10.1.

 

 

 

No, still bad boot6,7 if Clover r4760 compiled with XCODE 10.1 (toolchain set to XCODE8, edk2 r27956).  I think the problem/bug is intrinsic to XCODE 10.1.

At this moment I can include boot6 and boot7 files from good 4741 revision into next releases until the issue will be resolved.

Share this post


Link to post
Share on other sites
19 hours ago, fusion71au said:

 

I believe compilation with XCODE 10.1 is the problem.  From your debug log, you are compiling Clover with XCODE 10.1 (with toolchain set to XCODE8) on your system... 

 


Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/pkovacs/src/edk2/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 9 | OS: 10.13.6 | XCODE: 10.1]

 

I already mentioned in this post that other XCODE versions eg 8.2.1, 8.3.3, 9.2, or GCC5.3, generate working boot6 and boot7 for my legacy desktop (system 2 in signature) but not XCODE 10.1 ---> boot hanging on stuck underscore "_" symbol.  Also interesting to note that the officially released Clover r4741 was compiled with XCODE 8.3.3 but r4769 (which also fails for your system) with XCODE 10.1.

 

 

 

No, still bad boot6,7 if Clover r4760 compiled with XCODE 10.1 (toolchain set to XCODE8, edk2 r27956).  I think the problem/bug is intrinsic to XCODE 10.1.

Ah, i see. What an odd problem.

Can anyone build current Clover with Xcode 8 and I can try on my machine?

Share this post


Link to post
Share on other sites
20 hours ago, fusion71au said:

No, still bad boot6,7 if Clover r4760 compiled with XCODE 10.1 (toolchain set to XCODE8, edk2 r27956).  I think the problem/bug is intrinsic to XCODE 10.1.

 

Are you sure there is not a problem with the build rules for XCODE 10.1? I don't know if you mean that the problem is an intrinsic function or that it's inherent to XCODE 10.1. If you mean the former, can you narrow down exactly what intrinsic is causing the problem since really all that an intrinsic should be doing is generating an instruction or set of instructions in the same way, this behavior shouldn't really change. For either, the most likely scenario is that optimization is deciding that some needed instructions are not helpful for some reason, have you tried completely disabling optimization?

 

EDIT: Didn't realize you said the toolchain is set to XCODE8, are there no toolchain build rules for XCODE10.1? There may need to be different decisions made, so there should probably be XCODE10 toolchain.

Edited by apianti

Share this post


Link to post
Share on other sites
On 12/1/2018 at 2:47 AM, pkdesign said:

Ah, i see. What an odd problem.

Can anyone build current Clover with Xcode 8 and I can try on my machine?

 

Attached Clover r4784 compiled with XCODE 8.2.1 in 10.11.6: Clover_v2.4k_r4784.zip

 

Alternatively, you can use GCC instead of XCODE to build Clover eg if you use the Build_Clover.command script, edit the BuildCloverConfig.txt file like below...

 

GNU=GCC53
Build_Tool=GNU

 

On 12/1/2018 at 4:35 AM, apianti said:

EDIT: Didn't realize you said the toolchain is set to XCODE8, are there no toolchain build rules for XCODE10.1? There may need to be different decisions made, so there should probably be XCODE10 toolchain.

 Unfortunately, this expertise is beyond my pay grade...calling @Zenith432 for help? :)

 

 

13 hours ago, apianti said:

 

You can try a test by changing the tools_def.txt file in your UDK2018\EDK2/Conf directory and modifying the XCODE8 definitions near the bottom, either line 6227 or line 7000 depending which branch you are using, change the flag -Os to -O0 to disable optimizations for debug. Then build the debug version and see if that results in a working boot firmware. If so, then some specific optimization needs disabled, if not, then new rules need made for XCODE10. In that case, I'll let Zenith432 figure out what that would be since he's much better at that and I don't have the time to screw around to figure out what the problem is...

 

EDIT: You might also want to try adding -O0 to the the ASM rule a few lines before as well to see if that makes a difference.

 

Disabled optimization during compilation with -O0 flag in tools_def.txt still results in bad boot6,7 using XCODE 10.1.  Looks like new rules for XCODE10 will be required...

 

Edited by fusion71au
Tried @apianti's suggestion

Share this post


Link to post
Share on other sites
3 hours ago, fusion71au said:

 Unfortunately, this expertise is beyond my pay grade...calling @Zenith432 for help? :)

 

You can try a test by changing the tools_def.txt file in your UDK2018\EDK2/Conf directory and modifying the XCODE8 definitions near the bottom, either line 6227 or line 7000 depending which branch you are using, change the flag -Os to -O0 to disable optimizations for debug. Then build the debug version and see if that results in a working boot firmware. If so, then some specific optimization needs disabled, if not, then new rules need made for XCODE10. In that case, I'll let Zenith432 figure out what that would be since he's much better at that and I don't have the time to screw around to figure out what the problem is...

 

EDIT: You might also want to try adding -O0 to the the ASM rule a few lines before as well to see if that makes a difference.

Edited by apianti

Share this post


Link to post
Share on other sites

Hi

 

I use Debug kexts function from Clover GUI to diagnose my system. Where I can the log file? Please.

 

Thanks

Share this post


Link to post
Share on other sites
1 hour ago, Slice said:

/EFI/CLOVER/misc/debug.log

For Debug kexts, there is nothing inside the folder. I try again. Thanks.

Share this post


Link to post
Share on other sites
2 hours ago, Matgen84 said:

For Debug kexts, there is nothing inside the folder. I try again. Thanks.

You means Debug in section KextPatches? Log is impossible here. You can see the process only on screen.

Share this post


Link to post
Share on other sites
19 minutes ago, Slice said:

You means Debug in section KextPatches? Log is impossible here. You can see the process only on screen.

Exactly. Thanks you so much.

Share this post


Link to post
Share on other sites

Hi,

 

Despite of localizable.strings file, Theme description for Clovy doesn't exist in clover Package from SourceForge, or build with Build_Clover.command and Did script. 

 

I don't understand, why? Some ideas. Please.

Capture d’écran 2018-12-03 à 17.48.32.png

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   1 member

  • Similar Content

    • By vit9696
      OpenCorePkg / Documentation / Configuration Template / Bugtracker   Discussion and installation should be done in a separate thread! This thread is for development only!
      Current status as of April 2019: Support for UEFI and DuetPkg (legacy) booting APFS and HFS+ compatibility ACPI patcher (adding, dropping, binary patching, relocation) Apple-compatible bless implementation DeviceProperties injection DataHub and SMBIOS generation Symbolic kext and kernel patcher Direct kext injection/patching/blocking within prelinkedkernel Installation/Recovery/FileVault 2 support  Configuration in config.plist with open documentation Simple boot picker for quick launch Direct boot from dmg images  
      Known defects live here.  
      For those, who are not familiar with the history, OpenCore is a project initially born in HermitCrabs Lab that unfortunately almost died before its birth. This release is both a rebirth and a complete rewrite of OpenCore, which brings a number of new ideas, and tries to preserve the smart moves incorporated by iNDi and his team. Other than that, I wish to express my deepest words of gratitude to Acidanthera and WWHC members: your participation was and remains the key for project success, and you are simply the best.
    • By fusion71au
      Clover r4961 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.14 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4961 for VMware.zip". Mount Clover-v2.4k-4961-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By gengik84
      Ciro82==>>Thanks
      Uno dei tre Requisiti:
      Hack funzionante Mac vero Macchina virtuale Impostazioni Bios per il boot:
      Cercate una voce  del tipo “Sata Mode”e settatela  in AHCI
      Secure Boot: disabilitare o altri sistemi operativi
      CSM: UEFI o LEGACY, oppure a secondo del tipo di installazione
      VT-x / VT-d disable
      *Nota: Secure boot e csm valido solo per bios UEFI
      Materiale Occorrente 
      "OS X (Versione App.Store)”
      USB 8GB  *nota: nel caso di usb superiori dovrà essere partizionata, in modo da avere una partizione su cui "lavoreremo,di questa dimensione
      ShowAllfiles 
      kext Wizard 
      Bootloader Clover_2.3k_r xxx:                   http: //sourceforge.n.../cloverefiboot/
      Clover Configurator:                                    http: //mackie100proj...a.org/download/
      FakeSmc.kext:                                            https://github.com/kozlek/HWSensors/releases
      In allegato,a fondo pagina troverete un "pacchetto" contenente : ShowAllfiles, Kext Wizard, FakeSmc.kext: 
      App alternative:
      ESP Mounter Pro: per montare la partizione EFI
      Vi illustrerò tre metodi per creare la usb, ma sono ben distinti… quindi usatene soltanto uno
      Metodo 1: “Install Mac_OS_X.command” Metodo 2: “Create Install Media di Apple” Metodo 3:  Metodo Manuale Alla fine delle preparazione dell’installer, tutti i metodi necessitano l’installazione del Bootloader Clover sulla a vostra USB.
      “CONDIZIONI OBBLIGATORIE”
      PUNTO 1: che la vostra usb sia stata preventivamente nominata USB (caratteri maiuscoli) Tabella di partizione GUID e la formattazione in  Mac esteso Journaled.
      PUNTO 2: che l’installer di OSX si trovi in Applicazioni
      Utility Disco 
      Selezionate la pendrive, andate su “partizione”, selezionate “1 partizione”, impostate Mac OS esteso journaled e date il nome USB, poi in basso cliccate su opzioni e scegliete Tabella partizione (GUID), poi “applica”.
      Immagine 
      Riporto nuovamente l’operazione sopra citata adoperando dal nuovo Utility Disco introdotto su El Capitan.
      Rimane ovviamente invariato nome della usb in ==>> USB (maiuscolo), la formattazione in Mac esteso Journaled e sia la mappa partizione in GUID
      Da utility disco selezionate la usb, cliccate su inizializza.
      dal menù a tendina scegliete la relative impostazioni
      Immagine  
      Procedura effettua da High Sierra è la stessa della precedente, l'unica attenzione e operazione da aggiungere in primis  è cliccare nel menù a tendina in alto sulla sinistra di utility disco e selezionare "mostra tutti i dispositivi"
      Immagine 
       
      =====================
        METODO 1: "Install_Mac_OS_X.Command" Lo script che trovate allegato in fondo alla guida permette la creazione dell’installer in maniera automatica
      Include la possibilità di scelta di tre versioni di osx
      Yosemite El Capitan Sierra Il risultato finale è come quello del metodo "manuale" descritto nella guida, per cui l'installazione avverrà in un solo passaggio, non in due come con il metodo createinstallmedia. 
      Offre inoltre la possibilità di inserire un kernel patchato, utile, per esempio, per chi usa AMD.
      Rimane invariato il nome dato alla usb in USB, mappa partizione e tipo di formattazione
      Se la vostra usb non sarà rinominata nel modo corretto, verrete avvisati dal terminale, quindi non dovrete far altro che apportare la relativa modifica e rilanciare nuovamente lo script
      Esempio
      ===========================
      Metodo 2 
      L'intento è quello di usare la procedura fornitaci direttamente da Apple, "createinstallmedia", introdotta  con Mavericks. 
      Tale metodo prevede l’uso del terminale che via via se ne sta perdendo il “valore e l’uso”
      Inizialmente per i neofiti potrà sembrare problematico ma alla fine non è così.
      Durante il post installazione alcune operazioni ne richiedono l’ uso.
      Perciò mi sono chiesto perchè, qualora uno volesse, non far conoscere da subito un po’ questo “strumento”???
      Per favorirvi vi ho allegato i comandi già  “pronti”, i quali li potrete copiare ed incollare sul terminale.
      A questo punto aprite il terminale, copiate ed incollate il comando sottostante e premete invio, digitate la vostra password e premete nuovamente invio.
      Comando per creare USB con Yosemite:
      sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction  
      Comando per creare USB con El Capitan
      sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction Comando per creare USB con Sierra 
      sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction Per creare USB con Hight Sierra o Mojave usate --> C_I_M (aggiornato per 10.14)
       
      Funziona con il drag & drop sul terminale, in questo caso non vi è necessità che la usb sia nominata in un determinato modo ed essendo basato su create install media ovviamente funziona da 10.9 a 10.14.... 
      BENE…IL PROCESSO DI CREAZIONE E’ INIZIATO…
      AVREMO CIRCA 20/30 MINUTI DI TEMPO LIBERO A CUI DEDICARSI A CIO’ CHE VOGLIAMO………………………………………..  
      COLGO L’OCCASIONE PER FARVI NOTARE LA VELOCITA’ E LA SICUREZZA DI QUESTO METODO
      CONFRONTATE QUESTO CON IL TERZO METODO E NOTERETE CHE CON UN SOLO PASSAGGIO, OSSIA IL COMANDO DATO AL TERMINALE, FACCIAMO IN UNA SINGOLA OPERAZIONE TUTTI I VARI STEP DESCRITTI SULL’ ALTRO METODO.
      DETTO QUESTO, MOLTO IMPORTANTE E’ SOTTOLINEARE CHE COSI’ FACENDO EVITEREMO ERRORI  DI DISTRAZIONE RIGUARDO AI PASSAGGI O FRAINTENDIMENTI.
      Immagine 
      Potete adesso passare ad installare il bootloader Clover sulla vostra usb.
      *NOTA*:
      Avendo usato questo metodo l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      =========================
      METODO "MANUALE"....  (lascio per futura memoria-Compatibile fino a 10.12)
      ==========================
      Bootloader
      **Nota:** Installazione in UEFI  dipenderà dalla scheda madre in vostro possesso, quindi se non supporta tale opzione , il bootloader dovrà essere installato in  modalità Legacy.
       Vi invito, qualora non sapeste questa informazione, a recarvi nel sito ufficiale del produttore e controllare le informazioni a riguardo
      Fatto questo dobbiamo installare  Clover sulla usb.
      A seconda del tipo di Bios o al tipo di installazione che vogliamo fare UEFI o Legacy avremo ovviamente configurazioni diverse in questa fase.
      Lanciate il pkg.
      Immagine 

       
      Cambiate la destinazione di installazione ad USB oppure Install Mac_OS_X (a secondo del tipo di creazione eseguita)
      Successivamente clicchiamo su "Ad Hoc"
      Per Installazione UEFI
      Mettete i flag   : Installazione solo per avvio UEFI
                               : installare Clover nella ESP
                               : Driver64UEFI  AptioMemory --> (consigliato) 
                               : Driver64UEFI  ApfsDriverLoader --> (consigliato) --> sostituisce l'uso del driver apfs.efi
                               : Selezionate l'altri driver come da successiva immagine,
       
      *Nota: Altri driver che si possono usare  al suo posto  sono:
       informazioni 
       
      Proseguite con l’installazione.
      Immagine 
      ** Ricordate che avrete accesso a questa cartella dopo aver montato la partizione EFI**
      ===========================
      Per installazione Legacy
      Immagine 
      ===========================
      Impostazione per config.plist:
      Con clover configurator “montate” la partizione EFI della usb.
      1) Per fare questo nel menù di sinistra, cliccate su “Mount EFI”
      2) individuate la partizione relativa alla vostra usb, a questo punto montiamo la relativa partizione EFI  selezionando l’apposito pulsante “Mount Partition”
      Immagine 
      3) Successivamente cliccate su “Open Partition”.. recatevi in EFI/Clover ed aprite il config.plist
      4) Sezione ACPI: Disabilitate tutti i fix sia del menù 1 che del menù 2
      Immagine 
      5) Sezione BOOT: Sole se si sta installando Yosemite mettete il flag su kext-dev-mode=1
      Immagine 
      6) Sezione RT Variables: Se si sta installando El Capitan oppure Sierra, aggiungere i valori: BooterConfig= 0x28, CsrActiveConfig= 0x67
      Immagine 
      7) Sezione System Parameters: Su inject kext mettete YES
      Immagine 
      ===========================
      Nota: Su El Capitan, è stato introdotto SIP (System Integrity Protection)
      Info:
      ===========================
      Recatevi in EFI/Clover/kext/10.x 
      X= alla versione di osx che state installando. Per esempio se installerete Yosemite dovrete recarvi nella cartella 10.10, con El Capitan in 10.11….ecc
      Se non ci fosse tale cartella, createla e nominatela voi a “modo”.
      Copiatevi all’interno FakeSmc.kext
      *Nota se venite già da altre vostre configurazioni, oltre kext sopra citato ,potete mettere gli altri necessari per il vostro hardware
      Stessa cosa se avete DSDT e/o SSDT potete copiarli in EFI/Clover/Acpi/Patched
      Immagine 
      
      Per High Sierra:
      Scaricare il driver apfs.efi a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
       
      Per chi volesse continuare ad usare HFS vi rimando a questo post:
        Come installare High Sierra in HFS direttamente dalla usb  
      Utenti Laptop:  Nel 99% è obbligatorio disattivare la grafica discreta Nvidia/Amd per installare questo nuovo osx
                                     Quindi aggiungete --> SSDT-Disable_DGPU.aml.zip
                                     in EFI/Clover/acpi/Patched della usb
      --------------------------------------------------------------------
      Per Mojave:
      Scaricare il driver apfs.efi per 10.14 a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
      Versione di clover non antecedente a V_4015
      Volete usare HFS?
      E' possibile fare un installazione diretta su altro disco o partizione, nel caso può essere usato anche per effettuare aggiornamenti...
      nel caso guardate...
       Mojave in HFS 
       Oppure direttamente da usb  
       
      Fatto questo avrete la vostra USB bootable per installare OSX.
      ………Non scordatevi Fakesmc.kext da mettere nella relativa cartella…. senza il quale non farete mai il Boot......
      *NOTA: se usato il terminale per la creazione della usb, l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      **NOTA** Se avete processori Broadwell,Skylake o Kabylake...usate FakeSmc.kext e relativi sensors che trovate all'interno del secondo pacchetto.. (potete usarlo anche sui precedenti senza problemi, essendo una versione più aggiornata ha ulteriore supporto per le cpu più recenti)
      Update: Fakesmc e sensors versione 6.26
      Post installazione... post #2           
       Buon Hack….. 
      Aggiornamento:Install_Mac_OS_X.command.zip (compatibile da 10.10 a 10.12)
      le info le trovate a questo post
      Ringrazio @Ciro82 che mi ha aiutato nel preparare questa guida.
      Pacchetto.zip
      Pacchetto-2.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      C_I_M.zip
       
      apfs.efi-10.14-beta1_No_Log.zip





       

×