Jump to content
Micky1979

Build_Clover.command, another Script to build standard Clover (or customized)

1,956 posts in this topic

Recommended Posts

Advertisement
9 hours ago, vector sigma said:

Do you mean that below cmd does'nt work?


cp -R "${DIR_MAIN}"/edk2/Clover/Patches_for_EDK2/* "${DIR_MAIN}"/edk2/

here works good, but this is right from @SavageUS?


The current local EDK2 revision is the suggested one (26300).

should not be r26767 like mentioned by this guy?

Working with Slice's HWMonitor on sf is a pain as well  maybe is just sourceforge.. I also see that Aptiofix is already synced with a git reposytory, maybe you guys can you just do the same with edk2.

Well I just tested it by reverting my local copy of the EDK2 to it's original state and I got those errors that were being posted. I copied Patches_for_EDK2 to EDK2 dir, they disappeared because it built (besides one error that I fixed, unsure how anyone was building but ok). Then I reverted again then updated to the newest EDK2 commit, got build errors again. Recopied the patches, and it built. So yes if you are getting those errors it's because the patches were not copied. Maybe you might want to add the -f flag to copy so that it forcibly overwrites the files, just in case? Or maybe see if the result of the return from cp is an error because it failed? I don't know what you mean about AptioFix being synced, it is not. That is an external dependency just like EDK2, and is basically AptioFix3 with some added stuff that were basically what I had been saying should happen, no one listened and argued with me a bunch. Then decided that it should behave that way and wrote it separately from clover because that was easier to maintain.... I constantly have to remove it to properly build because either the repo can't update because its down (I have way more trouble with most stuff on github than I've ever had at SF, which is why I don't think the problem is truly SF, but then again I live like right by one of the main servers so it may be a proximity/routing thing) or because the code is broken and won't build. Which is why I didn't want it as an external dependency but I was overruled by Slice because I'm assuming he didn't want to have to constantly maintain packporting the fix into clover. Since even though I give anyone who asks and has demonstrated any ability to code the chance to at least have an opportunity to submit commits, I apparently wouldn't allow AptioFix to be updated (with my own ideas, mind you) by anyone else. Which is complete {censored} because no one ever asked to submit code ever, not once. Seems more like an opportunity to steal other people's work and pass it off as there own.... Which whatever, I don't really care. Recognition is like being constantly shot in the face with a fire hose, it's fun for about one millisecond, and then your head is being blasted with a fire hose....

Share this post


Link to post
Share on other sites
Posted (edited)

Hi Sir apianti, I'm sorry but I cannot understand what you mean or referring to AptioFix stories, but me at least, I was only referring on how the script (as per title of the topic) checkout/update AptioFix from github into a svn one and I was wondering if this can be done with edk2 ...and get rid of sourceforge. No some thing else. About the copy of the patches.. how this cannot work? cp in -R mode continue copying even on errors, so that I agree with -f, but errors are printed to the stdout and this is not the case. Those errors only happened to me when patches for edk2 inside Clover aren't good for the local revision of edk2 itself why I showned you this:

The current local EDK2 revision is the suggested one (26300).

Sir Zenith432 committed new patches compatible with newer r26764 but the guy who showned a fail on the log was using 26300.

So, if you revert edk2, don't forget to revert Clover as well, otherwise errors for sure. You know, simply that. 

EDIT
unless you are talking about reverting edk2 to the same revision but untouched:D. Anyway mentioned cp command is inside clover() func, so to apply patches you have to ensure to update clover with an option of that script. So yes if you cannot update Clover because sf is down, patches cannot be applied but anyway are the old one. Speaking by using this script ^_^

EDIT II

maybe you have to move the cp command outside this function, or eventually have this code in ebuild.sh.

Edited by vector sigma
spelling

Share this post


Link to post
Share on other sites
5 hours ago, vector sigma said:

Hi Sir apianti, I'm sorry but I cannot understand what you mean or referring to AptioFix stories, but me at least, I was only referring on how the script (as per title of the topic) checkout/update AptioFix from github into a svn one and I was wondering if this can be done with edk2 ...and get rid of sourceforge. No some thing else. About the copy of the patches.. how this cannot work? cp in -R mode continue copying even on errors, so that I agree with -f, but errors are printed to the stdout and this is not the case. Those errors only happened to me when patches for edk2 inside Clover aren't good for the local revision of edk2 itself why I showned you this:


The current local EDK2 revision is the suggested one (26300).

Sir Zenith432 committed new patches compatible with newer r26764 but the guy who showned a fail on the log was using 26300.

So, if you revert edk2, don't forget to revert Clover as well, otherwise errors for sure. You know, simply that. 

EDIT
unless you are talking about reverting edk2 to the same revision but untouched:D. Anyway mentioned cp command is inside clover() func, so to apply patches you have to ensure to update clover with an option of that script. So yes if you cannot update Clover because sf is down, patches cannot be applied but anyway are the old one. Speaking by using this script ^_^

EDIT II

maybe you have to move the cp command outside this function, or eventually have this code in ebuild.sh.

No, I had the patches copied over and had to revert the EDK2 repo to its original state. The revision actually matters very little, not as much as made out to be, sometimes when there are large changes to one of the headers or something there is an issue but most of the time it's fine because it overwrites the entire file, not just patch it. You only need the patches if you are building the firmware, the GUI alone shouldn't need the patches but then you have to specifically build each module. Which I doubt the script does. The script can definitely be changed to use the git repo, it's not my script, and was my initial point, switch to the github repo of EDK2 and you will probably have less issues.

Share this post


Link to post
Share on other sites

can't the edk repo just be changed in the BuildCloverConfig.txt on line 16

EDK2_REP=svn://svn.code.sf.net/p/edk2/code/trunk/edk2

or is there more to it then just that?

Share this post


Link to post
Share on other sites
27 minutes ago, bronxteck said:

can't the edk repo just be changed in the BuildCloverConfig.txt on line 16

EDK2_REP=svn://svn.code.sf.net/p/edk2/code/trunk/edk2

or is there more to it then just that?

No it's more than that as the commands would need to be switched to use git instead of subversion. It would also require removing any working copy.

Share this post


Link to post
Share on other sites
Posted (edited)
8 hours ago, bronxteck said:

can't the edk repo just be changed in the BuildCloverConfig.txt on line 16

EDK2_REP=svn://svn.code.sf.net/p/edk2/code/trunk/edk2

or is there more to it then just that?

 

7 hours ago, apianti said:

No it's more than that as the commands would need to be switched to use git instead of subversion. It would also require removing any working copy.

I'm confident that this:

EDK2_REP=https://github.com/tianocore/edk2/trunk

in BuildCloverConfig.txt will work as expected :D. Just need a clean src the first time. Bye bye sourceforge... now we need Clover on github..

Edited by vector sigma

Share this post


Link to post
Share on other sites
Posted (edited)

I suspected such sync issues may occur.

Migrating all the repos to git would require a major change in the source code versioning and I think that's up to @Slice to decide.

Edited by Philip Petev

Share this post


Link to post
Share on other sites

Hi Sir Philip Petev, of course yes. About the revision,by calling:

Build_Clover.command --edk2rev 36852

everything went fine, but can we assume that differences is always the same?? 

Share this post


Link to post
Share on other sites
Posted (edited)
4 minutes ago, vector sigma said:

Hi Sir Philip Petev, of course yes. About the revision,by calling:


Build_Clover.command --edk2rev 36852

everything went fine, but can we assume that differences is always the same?? 

The only way to be sure is to svn-checkout both the git and the SF repos in different folders and compare them with visual diff tool like Kaleidoscope. If they are identical, you won't see any occurrences when you load them in the app.

Edited by Philip Petev

Share this post


Link to post
Share on other sites
Posted (edited)
10 minutes ago, Philip Petev said:

The only way to be sure is to checkout both the git and the SF repos in different folders and compare them with visual diff tool like Kalleidoscope.

IMHO, is just the revision that comes with sf that is missleading, main repo is on github. I mean that if Slice will decide to use:

https://github.com/tianocore/edk2/trunk

instead of 

svn://svn.code.sf.net/p/edk2/code/trunk/edk2

then the rivision will be just the latest he wants to be ha ha. He just need to checkout new modules with new url. Is always a svn repo and have to do this only once and syntax He's using will be always the same (i.e. He can continue to use ~/src/edk2/Clover/update.sh)

Edited by vector sigma
spelling

Share this post


Link to post
Share on other sites
Posted (edited)

There is no reason to need to continue with any revision for EDK2, it is only used to update the patches, which is why at some point there is a "suggested" revision. However, the git and svn repos are identical, except that the svn repo constantly syncs with the git repo. Clover v2 repo won't be changing git, just the script using git for EDK2, it still would need to use subversion for Clover. And if you do switch to git for the EDK2 repo you'll have to make sure the entire working copy is erased to pull from the git repo or you'll run into issues.

EDIT: Also I switched to the git EDK2 repo a long time ago when the svn repo switched to syncing instead of direct commits. Never had an issue.

Edited by apianti

Share this post


Link to post
Share on other sites
25 minutes ago, apianti said:

make sure the entire working copy is erased to pull from the git repo or you'll run into issues

yeah, just compare each packages by doing the following (in this case BaseTools):

cd ~/src/edk2/BaseTools
svn info . | grep '^URL'

then if the output is not "URL: ${EDK2_REP}/BaseTools" you'll have delete it and checkout it again.

 

Share this post


Link to post
Share on other sites
Posted (edited)

SF is out for lunch... again.

Edit: guys, take a look at this:

Spoiler

================================================================================
boot6
                             <--------------------------------------------------
TOOLCHAIN_DIR: /Users/philip/src/opt/local
MTOC_PREFIX: /Users/philip/src/opt/local/bin/
NASM_PREFIX: /Users/philip/src/opt/local/bin/
NASM_VER: 2.13.03
Building from: /Users/philip/src/edk2

Running edk2 build for CloverX64 using the command:
build  -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/philip/src/edk2/Conf -D USE_LOW_EBDA -p Clover/Clover.dsc  -a X64 -b RELEASE -t XCODE8 -n 9

Build environment: Darwin-16.7.0-x86_64-i386-64bit
Build start time: 22:24:40, Apr.02 2018

WORKSPACE        = /Users/philip/src/edk2
ECP_SOURCE       = /Users/philip/src/edk2/EdkCompatibilityPkg
EDK_SOURCE       = /Users/philip/src/edk2/EdkCompatibilityPkg
EFI_SOURCE       = /Users/philip/src/edk2/EdkCompatibilityPkg
EDK_TOOLS_PATH   = /Users/philip/src/edk2/BaseTools
CONF_PATH        = /Users/philip/src/edk2/Conf


Architecture(s)  = X64
Build target     = RELEASE
Toolchain        = XCODE8

Active Platform          = /Users/philip/src/edk2/Clover/Clover.dsc
Flash Image Definition   = /Users/philip/src/edk2/Clover/Clover.fdf

Processing meta-data ..

build.py...
/Users/philip/src/edk2/MdePkg/Library/BaseLib/BaseLib.inf(452): error 000E: File/directory not found in workspace
    /Users/philip/src/edk2/MdePkg/Library/BaseLib/X64/WriteTr.nasm


- Failed -
Build end time: 22:24:44, Apr.02 2018
Build total time: 00:00:04


o_Ops, ./ebuild.sh exited with error(s), aborting..

That's clean source download (no ~/src/edk2) from the GH repo.

Edited by Philip Petev

Share this post


Link to post
Share on other sites
11 hours ago, vector sigma said:

yeah, just compare each packages by doing the following (in this case BaseTools):


cd ~/src/edk2/BaseTools
svn info . | grep '^URL'

then if the output is not "URL: ${EDK2_REP}/BaseTools" you'll have delete it and checkout it again.

 

No, if you switch to a git repo from using subversion repo, you need to erase the entire working copy. They are completely different tools and hold the commits in different ways, they cannot be checked out into the same directory. In fact git usually refuses to checkout into a non empty directory without flags and also if I recall correctly also complains that its already being tracked by subversion. You can however convert it to git but that won't help you because you want to have the remote git repo's commits/history, not create a new one.

7 hours ago, Philip Petev said:

SF is out for lunch... again.

Edit: guys, take a look at this:

  Hide contents

================================================================================
boot6
                             <--------------------------------------------------
TOOLCHAIN_DIR: /Users/philip/src/opt/local
MTOC_PREFIX: /Users/philip/src/opt/local/bin/
NASM_PREFIX: /Users/philip/src/opt/local/bin/
NASM_VER: 2.13.03
Building from: /Users/philip/src/edk2

Running edk2 build for CloverX64 using the command:
build  -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/philip/src/edk2/Conf -D USE_LOW_EBDA -p Clover/Clover.dsc  -a X64 -b RELEASE -t XCODE8 -n 9

Build environment: Darwin-16.7.0-x86_64-i386-64bit
Build start time: 22:24:40, Apr.02 2018

WORKSPACE        = /Users/philip/src/edk2
ECP_SOURCE       = /Users/philip/src/edk2/EdkCompatibilityPkg
EDK_SOURCE       = /Users/philip/src/edk2/EdkCompatibilityPkg
EFI_SOURCE       = /Users/philip/src/edk2/EdkCompatibilityPkg
EDK_TOOLS_PATH   = /Users/philip/src/edk2/BaseTools
CONF_PATH        = /Users/philip/src/edk2/Conf


Architecture(s)  = X64
Build target     = RELEASE
Toolchain        = XCODE8

Active Platform          = /Users/philip/src/edk2/Clover/Clover.dsc
Flash Image Definition   = /Users/philip/src/edk2/Clover/Clover.fdf

Processing meta-data ..

build.py...
/Users/philip/src/edk2/MdePkg/Library/BaseLib/BaseLib.inf(452): error 000E: File/directory not found in workspace
    /Users/philip/src/edk2/MdePkg/Library/BaseLib/X64/WriteTr.nasm


- Failed -
Build end time: 22:24:44, Apr.02 2018
Build total time: 00:00:04


o_Ops, ./ebuild.sh exited with error(s), aborting..

 

I have been using SF all day and haven't had one problem, lol.

7 hours ago, Philip Petev said:

That's clean source download (no ~/src/edk2) from the GH repo.

What do you mean? I use the GH git repo for EDK2, and the SF svn repo for Clover, in multiple OSes and it works perfectly fine. Just built with newest commits from each repo, works great...?

Share this post


Link to post
Share on other sites
Posted (edited)
8 hours ago, apianti said:

No, if you switch to a git repo from using subversion repo, you need to erase the entire working copy. They are completely different tools and hold the commits in different ways, they cannot be checked out into the same directory. In fact git usually refuses to checkout into a non empty directory without flags and also if I recall correctly also complains that its already being tracked by subversion. You can however convert it to git but that won't help you because you want to have the remote git repo's commits/history, not create a new one.

We are saying a similar thing of Just checking if the repo is not the same, then you can erase it or not. But me I'm talking by using "svn co" on github not git, otherwise you can ignore me :)

16 hours ago, Philip Petev said:

That's clean source download (no ~/src/edk2) from the GH repo.

Wrong revision of edk2 (probably is old), take latest or use r36852 as I already tried. EDIT: just for testing purpose, assuming you're using github.

Edited by vector sigma

Share this post


Link to post
Share on other sites
Posted (edited)

My point was subversion counts the revisions in the git repo the wrong way. Trying to pull out the latest preferred revision (r26764), subversion downloaded unusable copy (probably another revision), so changing the edk2 url with the GH repo doesn't work, at least no as it should be.

And the latest revision works only because nothing has been changed much (or at all) in the files from the Patches_for_edk2 folder.

Edited by Philip Petev

Share this post


Link to post
Share on other sites
Posted (edited)
58 minutes ago, Philip Petev said:

subversion downloaded unusable copy (probably another revision)

there's probably a diferences of 10086:

svn info https://github.com/tianocore/edk2/trunk
Path: trunk
URL: https://github.com/tianocore/edk2/trunk
Relative URL: ^/trunk
Repository Root: https://github.com/tianocore/edk2
Repository UUID: 72af8a33-8d04-ae46-851a-ce57b7db7bff
Revision: 36858
Node Kind: directory
Last Changed Author: carsey..jaben
Last Changed Rev: 36858
Last Changed Date: 2018-04-03 11:39:34 +0200 (Mar, 03 Apr 2018)

vs sourceforge:

svn info svn://svn.code.sf.net/p/edk2/code/trunk/edk2
Path: edk2
URL: svn://svn.code.sf.net/p/edk2/code/trunk/edk2
Relative URL: ^/trunk/edk2
Repository Root: svn://svn.code.sf.net/p/edk2/code
Repository UUID: 6f19259b-4bc3-4df7-8a09-765794883524
Revision: 26772
Node Kind: directory
Last Changed Author: edk2buildsystem
Last Changed Rev: 26768
Last Changed Date: 2018-04-02 11:05:26 +0200 (Lun, 02 Apr 2018)

so by checking out r26764 from github (svn) is like having downloading r16678 from sf :D

EDIT

..but sf is actually one day older. Maybe We can checkout a single BaseTools from both url (r36858 and r26772) and see if the commit message is the same with:

cd .../BaseTools
svn log --revision xxxxx

EDIT II

Anyway git is best, but the big problem is if Slice wants that??

Edited by vector sigma
typo

Share this post


Link to post
Share on other sites
On 1/4/2018 at 8:28 PM, apianti said:

So yes if you are getting those errors it's because the patches were not copied

Got it. I'm playing with Clover to make a customized iso with nvme+apfs drivers for virtualbox. I've entered the called "Developer mode", and this really doesn't copy patches. Don't know if this is a bug or is wanted, unsure.

Good night

Share this post


Link to post
Share on other sites

You need to check out the github URL with git. You did that right? If you only changed the URL and still used svn then it probably did something weird.

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   0 members

    No registered users viewing this page.

  • Similar Content

    • 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  selezionate OsxAptioFixDrv-64
                             *  :Se nel vostro sistema è presente una scheda grafica (discreta) della serie 9xx nVidia selezionate OsxAptioFix2Drv-64 al posto di  OsxAptioFixDrv-64 *
      ** OsxAptioFix2Drv :E' necessario per poter impostare CsrActiveConfig= 0x3 **
      ***OsxAptioFix3Drv oppure AptioMemory --> (consigliato) devono essere usati su hardware Skylake o successivi perché permettono alla nvram di lavorare correttamente
           (mi raccomando o uno o l'altro)
      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 
       
       
       
      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
      apfs.efi-10.13-NoLog.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      apfs.efi-10.13.1-No_LOG.zip
      apfs.efi-10.13.2_No_Log.zip
      apfs.efi-10.13.3-No_Log.zip
      apfs.efi-10.13.4-No_Log.zip
      apfs.efi-10.13.5_No_Log.zip
      C_I_M.zip
       
      apfs.efi-10.14-beta1_No_Log.zip






    • By warty
      On 8/20/2018 at 5:22PM, TessereKt said:
       
      On 8/21/2018 at 7:34AM, insanelyDeepak said:
       
      @insanelyDeepak, I would like to try cloverHDA, but I need help understanding how to use it.
       
      I have an Asus laptop that uses Realtek ALC295.
       
      My questions with regard to using cloverHDA:
      1.  I am running High Sierra (10.13.6). Is cloverHDA directly compatible? If not, can it easily be made compatible with adjustments I can apply?
       
      2.  What needs to be done with the original AppleHDA.kext that is already present in /S/L/E? Should it be left alone? Should it be removed? If it is removed, does the AppleHDA.kext that comes with cloverHDA, for example /Vanilla AppleHDA/Mac OS Sierra 10.12.6/AppleHDA.kext, need to be installed in its place?
       
      3.  In the 21 aug 18 reply to TessereKt, you mentioned "there is ALCPluxfix must install this." I noticed that there is a directory for alc_fix in one ALC295 directory (the ALC295_v2 Asus UX430UA directory) but not in the other ALC 295 directory that is provided (the ALC295/3254 directory). In which situation(s) is ALCPlugFix required?
       
      4.  My pathmaps are somewhat different from those in the cloverHDA.kext. Is there an easy way for me to customize the kext? For example, if I just switch the values in the xml files, will that be enough? Or does the whole thing then need to be recompiled?
       
      needed pathmaps:
      33-2
      23-3
      7-36-18
      9-34-19
       
      (My highest priority for the moment is getting headphone working, which is 33-2, and I might even be able to use the 33-3 that is already included. But I would like to eventually get all of them working.)
       
       
    • By C0nvert
      EFI Clover zip: https://aster-cloud.de/nextcloud/index.php/s/TjXg3qs2ydRTmS9
    • By kylon
      ACPI and Clover config for Acer Aspire v5-571PG intel i5-U IvyBridge
       
       
      Not Working:
      - sd card reader
       
       
      Tested on High Sierra 10.13.6 and Clover EFI 4678
       
       
      Notes:
      Somehow boot Clover EFI.
      You may need to disable UEFI and boot Clover as Legacy with EmuVariable.
      After that, you should install and boot macOS to install clover as legacy in your EFI partition.
      Now disable Secure Boot and enable UEFI Mode. (remove EmuVariable)
      You may need more steps if you are dual-booting with Windows.
       
       
      **To reset your BIOS, power on the pc and hold the power button for about 30-40 seconds or you can short G2101 (RAM SLOT 1)**
       
       
      Feel free to ask for help.
       
      You will need:
      Clover install options: Install in EFI Partition, Install boot0af, Enable OsxAptioFixDrv-64 and script RC Latest Clover config (acerAspirev5-571PG - CCE Bank) from here ATH9KFixup (here) WhateverGreen (here) Rehabman AppleIntelBacklightInjector (here) in L\E + rebuild cache Rehabman Voodoo PS2 Controller (here) Rehabman ACPI Battery Driver (here) vit9696 AppleALC (here) + Lilu (here) Mieze Realtek RTL8111 (here)
×