Jump to content
fantomas1

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

1,060 posts in this topic

Recommended Posts

So you didn't manually add this argument and nvidia web driver automatically added that when you installed correct ? It was a case with El Capitan, however same behaviour cannot be seen for Sierra. It's strange, argument also appears in my nvram right now but it's because of clover i think.

 

No I did not manually add this argument, and yes I am using macOS Sierra 10.12 DP4, all I did was install the web drivers but you also have to remember I do not use a hack, using a real Mac Pro 5,1. Since thats the case and seems like a lot of people are having issues maybe Clover is having issues adding arguments to nvram.

Share this post


Link to post
Share on other sites
Advertisement

No I did not manually add this argument, and yes I am using macOS Sierra 10.12 DP4, all I did was install the web drivers but you also have to remember I do not use a hack, using a real Mac Pro 5,1. Since thats the case and seems like a lot of people are having issues maybe Clover is having issues adding arguments to nvram.

Ah i see now, thank you for that, I wasn't know that you are using real 5.1. As you guessed, it's probably related to clover i think. Let's see how it will end up, I'm using hack as 6.1.

 

Thanks again.

Share this post


Link to post
Share on other sites

Nvidia Web Driver 367.10.10.05b01 has been updated to support the last macOS Sierra beta 5 (16A286a)

 

Check the first page, #1.

 

Regards

 

Little bit confused here, is there any change when comparing with current driver, it's just recently released ? Nvidia panel indicate that there are no update yet, so is that modified same blob for DP5 ? Thanks

Share this post


Link to post
Share on other sites

Little bit confused here, is there any change when comparing with current driver, it's just recently released ? Nvidia panel indicate that there are no update yet, so is that modified same blob for DP5 ? Thanks

If you are still not updated to PB4 or DP5 than you will not see any update, once you update the OS you will see the update.

I suggest to download first the update of web drivers than update OS and update web drivers.

I am going to try this now...

 

UPDATE

update to BP4 breaks my GPU...I have installed the latest drivers but i have many glitches on top of windows and top bar

 

P.s

the app will not show new drivers, I am downloading the latest build for the OS and check again...

Share this post


Link to post
Share on other sites

Question to those brave guys of you who are using it in a daily basis:
How many bug there are to be fixed and how does it affects you in your dally tasks? I'm asking that coz this hack im using is my daily driver and I don't wanna screw it all up although still wanna update.

 

My spects are on sign but im now running this 750TI I bought this week, works well.

Share this post


Link to post
Share on other sites

There might be hardware problems for you, I'm not quite sure that because of webdriver, I'm on DP5, still using same webdriver. There was problem with Airmail but it's also seems fixed with DP5, I can say pretty stable.

Share this post


Link to post
Share on other sites

Odd, I just installed the Sierra PB and this is my build number; 16A284a. I'm getting a black screen on my 970, I had to swap in my 680 in the mean time. WebDriver Updater finds no drivers for my OS build.

 

EDIT: EVGA 970, black screen. With 680, perfect. Same results with HDMI, DVI-D or wiping kernel caches. Considering WebDriver Updater doesn't find a driver for my OS build I think the latest drivers might be for the DP5 only.

 

EDIT 2: Well, considering the NVIDIA Web Drivers are activated while using the 680 I'm guessing there's a bug with it working with my 970

Share this post


Link to post
Share on other sites

There might be hardware problems for you, I'm not quite sure that because of webdriver, I'm on DP5, still using same webdriver. There was problem with Airmail but it's also seems fixed with DP5, I can say pretty stable.

 

PB3 was working just fine,  i think its compatibility issue with my GPU 

Share this post


Link to post
Share on other sites

Question to those brave guys of you who are using it in a daily basis:

How many bug there are to be fixed and how does it affects you in your dally tasks? I'm asking that coz this hack im using is my daily driver and I don't wanna screw it all up although still wanna update.

 

My spects are on sign but im now running this 750TI I bought this week, works well.

 

Then beta software is not for you. You should wait for the official version.

Share this post


Link to post
Share on other sites

Then beta software is not for you. You should wait for the official version.

Not such universal rule. I've seen and even tried pretty stable betas like Windows 10 previews, those were pretty stable. Usually, betas tend to come quite stable as release date comes around (not trying to be captain obvious here)

besides Apple historically not religiously release their final product in September "This fall" and that is around the corner already. But I understand where you came with this idea from and this is true most of the time.

Share this post


Link to post
Share on other sites

Not such universal rule. I've seen and even tried pretty stable betas like Windows 10 previews, those were pretty stable. Usually, betas tend to come quite stable as release date comes around (not trying to be captain obvious here)

besides Apple historically not religiously release their final product in September "This fall" and that is around the corner already. But I understand where you came with this idea from and this is true most of the time.

 

You seeked advice and I gave you mine, what you with it is your business. Surely, you will die if you don't upgrade now...just do it.

At least, be smart and install it on a different drive or partition to test it if you cannot afford your 'daily driver' to fail

Share this post


Link to post
Share on other sites

PB4 booted with PB3 drivers for me and my 970... no driver update and no issues as far as I can tell...

 

attachicon.gifpb4970proof.jpeg

That's the kind of answer I'm looking for. You didn't tell not to do it, you didn't say it's unsafe nor that should do this or that. Thanks mate, I asked for testimonials based on your experience and that's just about what you gave me ;)

Hats off.

Share this post


Link to post
Share on other sites

PB4 booted with PB3 drivers for me and my 970... no driver update and no issues as far as I can tell...

 

attachicon.gifpb4970proof.jpeg

THIS WORKED! The later, "PB4" drivers gave me the consistent black screen, I installed the PB3 drivers and I'm happily typing this with my 970 back in the comp!

Share this post


Link to post
Share on other sites

That's weird... I am using driver 367.10.10.05b01 (the latest, and the same driver released for PB3) on PB4 (16A286a) with no issue... I wonder why you guys are having issues and are seeing new drivers...

 

 

That's the kind of answer I'm looking for. You didn't tell not to do it, you didn't say it's unsafe nor that should do this or that. Thanks mate, I asked for testimonials based on your experience and that's just about what you gave me ;)
Hats off.

 

Sorry - I was responding to the rest of the conversation about driver problems... I would actually strongly discourage you from installing the beta on your main machine. There are issues (it is a beta, running on unsupported hardware with a community sponsored bootloader...), as evidenced by all of the users having issues with their GTX 970s in the past page, and the problems users have been having in general with unsupported GPUs...

 

Moreover, aside from being the wrong thread, you're not really going to have much luck answering this question unless a user has the exact same hardware that you do and a similar workflow. This isn't Windows, it's OS X, running in beta with known issues on real macintoshes, on hackintoshes... you're definitely going to run into some hiccups and may even have to do some reconfiguration, and, even then, it's still a beta. Heck, skylake support, that was added in 10.11.4, hasn't even made it into 10.12 (last I checked at least)...

 

But, you know - go for it if you want to! YMMV, there are always risks, et cetera - thus is the nature of both betas and hackintoshes.

Share this post


Link to post
Share on other sites

I have a Gigabyte GTX970 WindForce OC running DP5 with latest webdrivers and....... no luck :no: 

I've tried booting with and without nvda_drv=1 and my card still isn't detected..........

Share this post


Link to post
Share on other sites

Have you tried this?

Thank you - I think I have found a solution! Hopefully it works for others!

 

First, I changed my the Rt Variable "CsrActiveConfig" from 0x03 to 0x67 in Clover, as per these instructions (useful resource as SIP management is more nuanced now than it was). This allowed me to add boot arguments to the nvram:

 

sudo nvram boot-args="nvda_drv=1"
Checked with nvram -p and the change had been committed! So, I reboot, but still no Nvidia kexts!

 

Then, I used this command, as per a forum post that can not be named:

sudo nvram nvda_drv
Which produced these results with nvram -p:

boot-args	dart=0 nvda_drv=1
bootercfg	(%00
Clover.KeepBackupLimit	0
nvda_drv	1
prev-lang:kbd	en:0
SystemAudioVolumeDB	%02
security-mode	none
Clover.NVRamDisk	Yes
fmm-computer-name	claes
csr-active-config	g%00%00%00
SystemAudioVolume	%01
LocationServicesEnabled	%01
Rebooted and the kext has loaded! Thanks for all of the help!

Share this post


Link to post
Share on other sites

Have you tried this?

 

It doesn't work for me and my 750Ti :

 

$ sudo nvram boot-args

nvram: Error getting variable - 'boot-args': (iokit/common) data was not found

 

$ sudo nvram nvda_drv

nvram: Error getting variable - 'nvda_drv': (iokit/common) data was not found

Share this post


Link to post
Share on other sites

It doesn't work for me and my 750Ti :

 

$ sudo nvram boot-args

nvram: Error getting variable - 'boot-args': (iokit/common) data was not found

 

$ sudo nvram nvda_drv

nvram: Error getting variable - 'nvda_drv': (iokit/common) data was not found

 

you need to disable SIP , you can use clover config set variable to 0x67

by the way for 750ti on PB 4 you will have some glitches on screen, it totally related to the web drivers 

Share this post


Link to post
Share on other sites

you need to disable SIP , you can use clover config set variable to 0x67

by the way for 750ti on PB 4 you will have some glitches on screen, it totally related to the web drivers 

 

 

I already have 0x67 in my config.plist :

<key>BooterConfig</key><string>0x28</string>
<key>CsrActiveConfig</key>
<string>0x67</string>

But doesn't work :

nvram: Error getting variable - 'nvda_drv': (iokit/common) data was not found

Share this post


Link to post
Share on other sites

What's the "nvram -p" output?

$ nvram -p
bootercfg (%00
prev-lang:kbd it:0
efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>721EA2C3-D885-4B9D-96CB-ACF8B3B93760</string></dict></dict></dict></array>
security-mode none
EmuVariableUefiPresent Yes
fmm-computer-name iMac
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%04%00%00%00%f0;Q%09%00%00%00%00x%b0%94%04%00%00%00%00%c3%a2%1er%85%d8%9dK%96%cb%ac%f8%b3%b97`%02%02%7f%ff%04%00
csr-active-config g%00%00%00

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
      Première bêta... macOS Catalina 10.15 beta (19A471t)
       
       
      anciennes carte graphiques Nvidia + Intel HD 3000
    • 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





       

×