Jump to content
fantomas1

Nvidia Web Driver updates for macOS Sierra (UPDATE May 15, 2019)

1,060 posts in this topic

Recommended Posts

Made some progress ...

 

Proper graphics acceleration happens when I boot into the Recovery HD, but not my main OSX partition...

 

Should I try to remove the graphics drivers and reinstall them? 

 

-Duncan 

i just enable gtx 970 successfully on sierra for my friends.. so no problems with  your graphics cards....yes ,you can do that and try 

Share this post


Link to post
Share on other sites
Advertisement

 

remove id 0x13C2  and DSDT.aml</string>

<key>Patches</key>
<array>
<dict>
<key>Comment</key>
<string>GFX0 [to] GFX2</string>
only use ADGPFIX1.3 

 

 

 

So I tried changing the config file as you had mentioned, but still no luck. I even tried the iMac 17,1 smbios, but no recognition of card or loading of nvidia driver booting into Sierra. 

 

So it does appear that the nvda_drv=1 boot arg is not making it through reboot in the nvram for sierra. I have tried manually setting the nvram in terminal using 'sudo nvram boot-args="nvda_drv=1"'. It will show up when I then print the nvram using nvram -xp. However on reboot there is no nvda_drv boot arg in nvram in sierra. I assume that this has something to do with how clover is handling the nvram??

 

I can also confirm that when i do not have nvda_drv=1 set for El Capitan i get the same result as I do in Sierra. 

 

Thoughts?

Share this post


Link to post
Share on other sites

So I tried changing the config file as you had mentioned, but still no luck. I even tried the iMac 17,1 smbios, but no recognition of card or loading of nvidia driver booting into Sierra. 

 

So it does appear that the nvda_drv=1 boot arg is not making it through reboot in the nvram for sierra. I have tried manually setting the nvram in terminal using 'sudo nvram boot-args="nvda_drv=1"'. It will show up when I then print the nvram using nvram -xp. However on reboot there is no nvda_drv boot arg in nvram in sierra. I assume that this has something to do with how clover is handling the nvram??

 

I can also confirm that when i do not have nvda_drv=1 set for El Capitan i get the same result as I do in Sierra. 

 

Thoughts?

enabling EmuVariableUefi-64.efi in driver64uefi..

Share this post


Link to post
Share on other sites

enabling EmuVariableUefi-64.efi in driver64uefi..

exactly just like xxdd said

you need to have emuvariable installed

i also will like to add or ask brocklanders this , do you have your boot loader installed in your bootable hard drive or are you booting from a usb flash drive?

make sure you have clover installed in your bootable hard drive and you have the latest version of clover install

use ShowHiddenFiles.app click on show special files and make sure you have nvram.plist in root of your bootable sierra drive

to revert the settings simply click on hide special files

do not use a usb to boot the hard drive

install the boot loader in the hard drive and boot from there

so clover can read nvram.plist from the hard drive

 

also you are only running one command and not the complete set of commands

make sure the run the complete command list

 

like a said before there are may things to take under consideration like are you using fast boot

do yo have csmvideodxe installed on clover

ShowHiddenFiles.zip

Share this post


Link to post
Share on other sites

So I tried changing the config file as you had mentioned, but still no luck. I even tried the iMac 17,1 smbios, but no recognition of card or loading of nvidia driver booting into Sierra. 

 

So it does appear that the nvda_drv=1 boot arg is not making it through reboot in the nvram for sierra. I have tried manually setting the nvram in terminal using 'sudo nvram boot-args="nvda_drv=1"'. It will show up when I then print the nvram using nvram -xp. However on reboot there is no nvda_drv boot arg in nvram in sierra. I assume that this has something to do with how clover is handling the nvram??

 

I can also confirm that when i do not have nvda_drv=1 set for El Capitan i get the same result as I do in Sierra. 

 

Thoughts?

 

I am using macpro 6.1 definition. You don't need to use any kext or modify kext. Just fully apply patch in clover which I shared on my original post. Still working SIerra GM as well.

http://www.insanelymac.com/forum/topic/312525-nvidia-web-driver-updates-for-macos-sierra-update-08292016/?p=2274555

Share this post


Link to post
Share on other sites

 

I am using macpro 6.1 definition. You don't need to use any kext or modify kext. Just fully apply patch in clover which I shared on my original post. Still working SIerra GM as well.

http://www.insanelymac.com/forum/topic/312525-nvidia-web-driver-updates-for-macos-sierra-update-08292016/?p=2274555

is it useful for imac17.1 system definition?

Share this post


Link to post
Share on other sites

is it useful for imac17.1 system definition?

If you have discrete gpu can work I think, didn't test it yet on that. Reason that i'm using 6.1, ui somehow seems to appearing more smooth to me (could be placebo). I'm also attaching whole config file (SMBIOS nuked) here without SMBIOS section. Can be easily populated with clover configurator.

config.plist.zip

Share this post


Link to post
Share on other sites

Maybe my experience is just entirely unrelated,

 

when I trialled the first beta version of Sierra I did it in a new partition created on my existing El Capitan install SSD, booted the system from clover installed in el capitan EFI. All my relevant kexts have always been in the clover extra folder, so no need to create a folder for 10.12.

I have a skylake processor so I am using iMac 17.1 system def. After reaching desktop on first beta install I changed the appropriate board ID status to none, installed the Nvidia web driver for my GTX970 and rebooted with NVDA_drv=1 boot flag still set, this was always set, and never changed this at any time. On subsequent Sierra beta updates, I found it was first necessary to uninstall the Nvidia web drivers before rebooting and installing new beta version or I got a black screen on second stage boot, even with NV_disable flag set.

I am currently running Sierra GM using same procedure for install with full GPU acceleration (or what passes for full acceleration on my hack, lol).

Hope this helps

Share this post


Link to post
Share on other sites

This topic has become absolutely painful to read..

 

:yes:

 

+2

 

It's for a while that I'm keeping an eye on the way that things took in this topic but afraid of being in the censorship, I just let these things go.  :(

 

@ ALL

 

Guys, It will be more helpful if we stay focused on the main theme which is testing the last nvidia web driver on our hackintosh, especially in macOS Sierra (as this is its dedicated topic   :P  ).

 

You don't have to write a novel to make us understand that you have a problem, especially when this problem is not necessarily related to the web driver.

 

All posts must be clearly written and easy to read.

 

Thank you all for your understanding.   ;)

 

Best regards

Share this post


Link to post
Share on other sites

 

It's for a while that I'm keeping an eye on the way that things took in this topic but afraid of being in the censorship, I just let these things go.  :(

 

 

My proposal is to open a topic specific to discuss 

the graphical problems found in the Sierra and so try to 

solves them in the best possible way.

and we can begin to do this, migrating some of the post 

from here to this new topic, well, it's only my thought.

Share this post


Link to post
Share on other sites

exactly just like xxdd said

you need to have emuvariable installed

i also will like to add or ask brocklanders this , do you have your boot loader installed in your bootable hard drive or are you booting from a usb flash drive?

make sure you have clover installed in your bootable hard drive and you have the latest version of clover install

use ShowHiddenFiles.app click on show special files and make sure you have nvram.plist in root of your bootable sierra drive

to revert the settings simply click on hide special files

do not use a usb to boot the hard drive

install the boot loader in the hard drive and boot from there

so clover can read nvram.plist from the hard drive

 

also you are only running one command and not the complete set of commands

make sure the run the complete command list

 

like a said before there are may things to take under consideration like are you using fast boot

do yo have csmvideodxe installed on clover

 

 

So thank you for the response. I was unable to post last night as the discussion boards were down, but I did a bit of research after looking at some other entries from other forums. Imtheonlyone4ever you were ultimately correct. My install of Sierra is on a drive separate from my El Capitan install which has the Clover EFI. I found that there was no nvram.plist in the Sierra root. After adding nvram.plist to the root of the Sierra drive with the appropriate boot args, my GTX 970 is recognized and drivers are loaded appropriately!! Now i just got to fix my broadcom BT/WIFI...

 

So I wonder for all of those who are having trouble with these drivers on Sierra, have you checked to see if there is a nvram.plist in the root of your Sierra install HD?? This helps explain why no nvram boot args carry over etc. I also had to delete the piker graphics fix in my kernel patches in clover config.plist. Then all you need is v 1.3 of AGPDfix to enable graphics output on imac 15,1 or 17,1 or the mac pro 6,1.

 

I hope that makes sense

Share this post


Link to post
Share on other sites

thank you you are very nice and cool i'm happy that you got it working.

 

as for the other person comment joe75 about that the topic has become painfully to read, so you want me to apologies because my english is not perfect, "sorry for my bad english" even my english is painful to read, blocklanders understood me and got his card working, and don't say you didn't said that because of me, be a man and backup your words and if you actually didn't say it because of me, you know those kind of comment make people feel people bad, specially people who can't write english 100% but you know what is all good anyway because blocklanders comment made me feel good with his positive comment. im also happy that he got his card working.

 

even with my broken down english which i already know is not perfect but thanks for the complement anyway joe, maybe you will not understand this because is painful to read, so i see your comment as a rude comment but if i said rude things to you then i get ban from the forum. that's why i'm not going to say anything but if you have something to say be direct and specific and don't make those comments that make people feel bad. thank you i hope this don't be to painful to read but i'm sure anybody with an average brain can understand. there are more countries around the world and the world is not just the streets around your house. i will like to see you try to talk or write in another language. professor

Share this post


Link to post
Share on other sites

this my last post

you have to use nvram that is stored in sierra boot drive because that nvram contains the nvda=drv value that the nvda_drv from El Capitan don’t have

because El Capitan don't use that new value

if you use another hard drive boot loader , yes it will boot the system , yes that hard drive also has nvram.plist

but that file do not have the value that is require for the graphic card to work in sierra

so most likely the problem that most people are having is because they are booting sierra from clover boot loader that is installed in El Capitan Hard drive or partition

just make sure that sierra got his own boot loader installed on its own bootable sierra drive

i’m done here , i wish everybody good luck and success

all i wanted to do was help

but it seems that it bothers some people

Share this post


Link to post
Share on other sites

this my last post

you have to use nvram that is stored in sierra boot drive because that nvram contains the nvda=drv value that the nvda_drv from El Capitan don’t have

because El Capitan don't use that new value

if you use another hard drive boot loader , yes it will boot the system , yes that hard drive also has nvram.plist

but that file do not have the value that is require for the graphic card to work in sierra

so most likely the problem that most people are having is because they are booting sierra from clover boot loader that is installed in El Capitan Hard drive or partition

just make sure that sierra got his own boot loader installed on its own bootable sierra drive

i’m done here , i wish everybody good luck and success

all i wanted to do was help

but it seems that it bothers some people

Eww giz Why so salty honey? Anyways boys calm your {censored} down and don't do dumb stuff. 

Sierra should get its own Hard driver packed with its own Bootloader. Why? Because it has its own particularities!

put Emuvariable under clover folder then run commands and you're done. 

Share this post


Link to post
Share on other sites

as for the other person comment joe75 about that the topic has become painfully to read, so you want me to apologies because my english is not perfect, "sorry for my bad english" even my english is painful to read, blocklanders understood me and got his card working, and don't say you didn't said that because of me, be a man and backup your words and if you actually didn't say it because of me, you know those kind of comment make people feel people bad, specially people who can't write english 100% but you know what is all good anyway because blocklanders comment made me feel good with his positive comment. im also happy that he got his card working.

 

even with my broken down english which i already know is not perfect but thanks for the complement anyway joe, maybe you will not understand this because is painful to read, so i see your comment as a rude comment but if i said rude things to you then i get ban from the forum. that's why i'm not going to say anything but if you have something to say be direct and specific and don't make those comments that make people feel bad. thank you i hope this don't be to painful to read but i'm sure anybody with an average brain can understand. there are more countries around the world and the world is not just the streets around your house. i will like to see you try to talk or write in another language. professor

 

My comment has nothing to do with your "bad english". Many people here speak bad english :P

 

It is in regards to the content.. This is a topic about the web drivers, not about how you can't get them to work.  This topic is not to educate you about your boot manager or any other fix needed outside of the web drivers. There is a bunch of nonsense going back and forth with the posts about the nvram command. As fantomas pointed out, your problems are not from the drivers at all, but instead are with clover and your inability to properly use your boards nvram space..

Share this post


Link to post
Share on other sites

this my last post

you have to use nvram that is stored in sierra boot drive because that nvram contains the nvda=drv value that the nvda_drv from El Capitan don’t have

because El Capitan don't use that new value

if you use another hard drive boot loader , yes it will boot the system , yes that hard drive also has nvram.plist

but that file do not have the value that is require for the graphic card to work in sierra

so most likely the problem that most people are having is because they are booting sierra from clover boot loader that is installed in El Capitan Hard drive or partition

just make sure that sierra got his own boot loader installed on its own bootable sierra drive

i’m done here , i wish everybody good luck and success

all i wanted to do was help

but it seems that it bothers some people

everyone has different kinds of ideas about the same problem..so ignore those nonsense things..but i think you slove graphics cards balck screen problem for me..i learn much more from you..you have done a great work. thank you 

Share this post


Link to post
Share on other sites

i just enable gtx 970 successfully on sierra for my friends.. so no problems with  your graphics cards....yes ,you can do that and try 

 

I've updated my Web Drivers to the latest GM one, and still black screen!?

I'm starting to lose my head at this point ...

 

NVRAM is consistent and has nvda_drv=1 every boot, all patches are restored (so no patches), running iMac14,2...

I wouldn't know what the cause would be at this point ...

 

Any ideas?  :rolleyes:

 

-Duncan 

Share this post


Link to post
Share on other sites

I've got fingers crossed here that THIS patch (GM) will at last support HDMI audio.... no problem with Graphics on my GTX 750 Ti SC (EVGA) on 3 monitors but not even a hint of audio!!!

Has the driver actually been updated even? I simply updated from PB7 and the same driver worked,,,


I've got fingers crossed here that THIS patch (GM) will at last support HDMI audio.... no problem with Graphics on my GTX 750 Ti SC (EVGA) on 3 monitors but not even a hint of audio!!!

Has the driver actually been updated even? I simply updated from PB7 and the same driver worked,,,

To answer my own question... ABSOLUTELY NOT...

driver updated for???

It's the same driver that has been in use since PB 3 or thereabouts! When will the HDMI audio fix come????

Share this post


Link to post
Share on other sites

I've been trying to get this working for hours, but I cannot get my PC to keep the Nvidia driver selection. I installed with nv_Disable=1, rebooted and then set the Nvidia driver as the driver to use, rebooted with nvda_drv=1, still no luck. Telling me I have 5mb of VRAM lol. Is this happening to anyone else? I've tried a fresh install 3 times now. Tried forcing nvda_drv=1 with terminal. Gigabyte Gaming 7 mobo, w/ intel 6700k and GTX960.. 

Share this post


Link to post
Share on other sites

Back to the main discussion, though.  :)

 

Nvidia Web Driver - 367.10.10.05b01 has been updated to support the last macOS 10.12 GM build 16A320.

 

Please, check the first page post #1.

 

Regards

 

Using this driver originally, I had issues until i edited the graphics device policy kext. 

Edited by fantomas1
"off topic" removed!!!

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 fantomas1
      First beta... macOS Catalina 10.15 beta (19A471t)  Release Notes!!!
       
      Useful information:
       
      macOSDeveloperBetaAccessUtility.dmg.zip (thanks to gengik84)
      Clover r4945 (thanks to Cyberdevs)
      Lilu_plugins (thanks to gengik84)
      Port Limit Patch (thanks to daliansky)
      older non metal nVidia and Intel cards (thanks to fusion71au))
    • By fusion71au
      Patch Catalina or Mojave macOS Installer App for Unsupported Machines
       
      Often for economic reasons, Apple prevents the Installer.app for its latest macOS from installing on older machines perfectly capable of running it eg macOS 10.14 Mojave on Unsupported Macs Thread.
       

       
      In Mojave 10.14, @ASentientBot posted a method to patch the distribution file in OSInstall.mpkg to enable the Mojave installer to install on unsupported machines (with or without graphics card metal support). 
       
      In Catalina 10.15beta, the above method no longer works since Apple is checking OSInstall.mpkg for its file signature and the mandatory requirement in Catalina to install to 2 separate apfs volumes necessitates using the original Catalina macOS Base System Installer.  Fortunately, it is still possible to substitute High Sierra’s Apple Signed OSInstall.mpkg inside the Catalina or Mojave InstallESD.dmg by making it R/W.
       
      The procedure below will allow Macs or Hacks able to install High Sierra to also install Catalina or Mojave (eg SMBIOS MacPro5,1, iMac11,3, MacBook Pro7,1 which have been unsupported in macOS 10.14.x and 10.15beta) -credit to @ASentientBot's post.
       
      Prerequisites
      1. Mac or Hack capable of and running High Sierra 10.13.x
      2. An original, untouched copy of OSInstall.mpkg from High Serra InstallESD.dmg - attached OSInstall_10.13.6.mpkg.zip save to your ~/Downloads folder
      3. macOS Installer App eg for Catalina beta or Mojave downloaded to /Applications
      4. Add NVRAM boot arg (or Clover config.plist boot arg on a hack) -no_compat_check to enable system to boot to final completed Mojave or Catalina install.
       
      Procedure
      1. Open Terminal and type the following
       
      open /Applications/Install*/Contents/SharedSupport/InstallESD.dmg (assuming the Catalina or Mojave Installer App is in /Applications)  
      2. Open Disk Utility, click File|New Image|Image from ‘InstallESD”
      3. Save as read/write image, no encryption in /Applications
      4. Unmount InstallESD in DU by clicking the "eject" icon next to it
       
       
      5. Open the R/W InstallSD.dmg in /Applications and replace Catalina’s/Mojave's OSInstall.mpkg with High Sierra’s version by typing in terminal
       
      open /Applications/InstallESD.dmg cp ~/Downloads/OSInstall_10.13.6.mpkg /Volumes/InstallESD/Packages/OSInstall.mpkg  
      6. Unmount InstallESD in DU by clicking the "eject" icon next to it
      7. Replace original Catalina/Mojave InstallESD.dmg with our patched one, making a backup of the original.  In terminal, type
       
      sudo mv /Applications/Install*/Contents/SharedSupport/InstallESD.dmg /Applications/InstallESD_orig.dmg sudo mv /Applications/InstallESD.dmg /Applications/Install*/Contents/SharedSupport/  
      8.  Test the newly patched installer!…

    • 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





       

    • By MaLd0n
      Now have a Olarila app, just download app and clover folder for your Chipset! https://olarila.com/forum/viewtopic.php?f=81&amp;t=6771   Nehalem, SandyBridge, IvyBridge, Haswell, Broadwell     Skylake, Kabylake and Coffeelake is here http://www.insanelymac.com/forum/topic/321872-guide-sierra-on-gigabyte-mobos-serie-200-kabylake-dsdt/   Install MacOS with Olarila Image, Step by Step, Install and Post Install
       
      https://olarila.com/forum/viewtopic.php?f=50&t=8685
        Mojave Full DSDT patch   http://olarila.com/forum/viewtopic.php?f=59&amp;t=6428   First...   ***Update bios to last available version!***   If you need a full patched DSDT...  -Extract tables with F4 key in Clover boot screen! -Run it and send me files! RunMe.app   Installation   --Create a bootable copy of macOS Sierra / High Sierra / Mojave   https://github.com/chris1111/Create-Install-Media/releases   --Install Clover in USB stick   https://sourceforge.net/projects/cloverefiboot/files/Installer/   --Replace with my Clover folder https://olarila.com/files/Clover.Folder/CLOVER.SERIES.CHIPSET.zip   --Install Sierra/High Sierra and boot into system!   Post Installation --Install Clover and replace with my folder   https://olarila.com/files/Clover.Folder/CLOVER.SERIES.CHIPSET.zip   --Reboot and activate video!   Bingo!   Now you need a fine tune! DSDT time!   --DSDT   Patches -FIX ERRORS AND WARNINGS -HPET -SATA -DMAC -SLPB -DARWIN -LPC -XHCI -PLUGIN TYPE -XXXX to HDEF -HDEF -RTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -USBX -PMCR -EC -PNLF -HDMI
       
      --Power Management
      - 1 Generation Intel Processors, use Generate P and C States in config.plist
      - 2 and 3 Generations Intel Processors, Generate SSDT with Piker script and drop CpuPm and Cpu0Ist SSDTs
      ssdtPRGen.command.zip
      Credits-https://github.com/Piker-Alpha/ssdtPRGen.sh
      - 4 Generation+ Intel Processors, use PluginType=1 in DSDT, SSDT or Clover config.plist
       
      for check Power, Frequency, Temperature and Utilization, use it
       
      Install Intel Power Gadget.pkg.zip
       
      --Brightness
      Install .app, select the required permission and reboot. Work in F1 / F2 keys!
      NativeDisplayBrightness.app.zip


      https://github.com/Bensge/NativeDisplayBrightness/releases
      *in some cases .app don't work, check patches in config.plist inside Clover folder Post Install
       
      --Clover
       
      https://sourceforge.net/projects/cloverefiboot/files/Installer/
       
      --AUDIO
       
      Use DSDT + AppleAlc
       
      --install Lan driver by Mieze
        -Atheros   http://www.insanelymac.com/forum/files/file/313-atherose2200ethernet/   -Intel   http://www.insanelymac.com/forum/files/file/396-intelmausiethernet/   -Realtek   http://www.insanelymac.com/forum/files/file/88-realtekrtl8111-binary/   --Links   -FakeSMC   https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek   -Audio   https://github.com/vit9696/AppleALC http://www.insanelymac.com/forum/topic/314406-voodoohda-289/   -USB   https://bitbucket.org/RehabMan/os-x-usb-inject-all/downloads   It's time to Rock   -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!   Apple, Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad and many, many, many others!   We're all here to have fun and learn from each other!  
×