Jump to content
rockinron_1

[Guide] The all-in-one guide to Vanilla OS X (including Chameleon + DSDT) for beginners (updated for Yosemite!)

911 posts in this topic

Recommended Posts

Advertisement

Agreed, this is an excellent write up. I am still having problems after the install but that is likely due to my 6970. I still have no idea if there is a way to get that going.

Share this post


Link to post
Share on other sites

thanx a lot. Works perfect on my Sandy Bridge i5 System with Nvidia GTX 560 and ALC 662 Audio. I just needed to install additional Kexts for ALC662 from osx86.net. The graphics is now much much faster with the out of the box driver from apple.

 

But i can't access the app store and can't execute apps downloaded from the app store with 10.7.4. It says my computer isn't recognized.

Is there a soluten to use the app store?

Share this post


Link to post
Share on other sites

App store issue is a generic one regarding your network hardware.

 

You MUST have either a working airport or ethernet card. Then ensure ethernet buit in is checked in your org.chameleon.boot.plist. Now go to system preferences and delete all the devices in the network section. Now navigate to /Library/Preferences/SystemConfiguration and delete com.apple.airport.preferences.plist and networkinterfaces.plist and com.apple.boot.plist. Reboot then add your network interfaces in system preferences and try to connect to app store again

Share this post


Link to post
Share on other sites

rockinron,

Thank you for the updated ML install guide v2.2.pdf

What are the changes compare with ML install guide v1.0.pdf?

TQ

Share this post


Link to post
Share on other sites

Fundamentally there's little change; structures been played about with and some post-install stuffs been added, i just like to keep note of the guides i've posted and if I spot a mistake / something that might be unclear I update it. 1.0 will be removed in a bit, its only still there for people who have been using it and might not have finished installing.

Share this post


Link to post
Share on other sites

Part 5 – DSDT

Although not strictly required it is useful to have a DSDT for your system. On its own it can fix shutdown / sleep problems

It can't, this is a myth.

 

OS X already "loads" your DSDT, as well as your other ACPI tables, otherwise you would not be able to extract them on OS X in the first place.

Extracting your DSDT to a file, fixing compiling errors and having Chameleon load it for you by placing it in /Extra does not fix or change anything.

(native CPU power management) You MUST have a DSDT for this to work.

Not true. With GeneratePStates/CStates set in org.chameleon.Boot.plist, native CPU power management works for me with no ACPI table overrides.

(...) give it the paths to your DSDT and SMBios (/Extra)

/Extra is the default path for those files, it is not necessary to do anything if smbios.plist and DSDT.aml are placed in /Extra.

4. App-store "your device or computer could not be recognised..." error.

App-store requires a MAC address to verify your computer (any address, it doesn't have to be an apple one) hence you MUST have a working Ethernet or airport card for App Store to work.

This will only work with a wired Ethernet device with the built-in property set. This is what EthernetBuiltIn=y in /Extra/org.chameleon.Boot.plist is for.

You must have a driver loaded for your wired ethernet for the App store to work. It will not work with wireless ethernet.

Share this post


Link to post
Share on other sites

It can't, this is a myth.

 

OS X already "loads" your DSDT, as well as your other ACPI tables, otherwise you would not be able to extract them on OS X in the first place.

Extracting your DSDT to a file, fixing compiling errors and having Chameleon load it for you by placing it in /Extra does not fix or change anything.

 

 

I was about to call total BS on this, however I read and re-read the original post and I agree. HOWEVER, without DSDT edits some systems need separate kexts to have working sleep and shutdown/restart. This is most prevalent on legacy and AMD systems. Chameleon is magic, but it only goes so far.

 

I will say this though, your reply makes it sound like a DSDT is not needed at all. It DOES fix a lot of issues (HPET, USB, HDEF etc) without the need of kexts, and for power users such as myself, I use only FakeSMC and Realtek ethernet, the rest is made possible by the fully edited DSDT. For beginners, enabling the options/fixes through Chameleon (Wizard) is the easiest way to go about getting a working Hackintosh. It teaches them absolutely nothing, but I suppose some people just want to "Git'r done!" :P

Share this post


Link to post
Share on other sites

I quoted the sentence that I'm objecting to: "on its own it can fix shutdown and sleep problems." That is simply not true.

 

Placing an unmodified DSDT in /Extra does nothing. Compiling errors fixed or not.

 

That's basically what I said, my reply was very clear and to the point. I don't see how you can possibly read anything else into it.

Share this post


Link to post
Share on other sites

I don't claim to be perfect so I'll take your word for that lot but this:

You must have a driver loaded for your wired ethernet for the App store to work. It will not work with wireless ethernet.

Is wrong. Without an ethernet kext loaded my laptop will connect to the app-store fine with an ar9285 airport card

Share this post


Link to post
Share on other sites

This worked great for me, here are some specs:

 

Gigabyte GA-X58A-UD3R Rev 2 (No DSDT!)

Intel i7 950

10GB DDR3 @ 1079MHz

2 7200rpm sata hard drives and 1 Corsair M4 SSD with TRIM support through [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url]

ATI Radeon HD 6770 flashed as 5770 to work OOB (dual monitors working)

ALC889 audio installed with ######## (select drivers & bootloaders -> kexts & enablers -> audio -> realtek alc8xx -> unified device injector -> alc8xxHDA, then applehda rollback one level up, and finally non dsdt hda enabler -> alc889)

 

RealtekRTL81xx pkg enabled ethernet

 

Some notes:

I used the latest version of the Chameleon pkg which I found at http://www.osx86.net...ootloaders.html

Sleep does not work, but display sleep does, so turn off the system going to sleep in power options if you don't want the computer to require a reboot

Share this post


Link to post
Share on other sites

Thanks for the guide, well written and explained. Though, as always, when i go Vanilla, i have the same issue. When installing, i get to Starting Darwin, then reboot. Try all combos of flags. Just can't get to the installer. I'm running an i7 2600k on a Asrock P67 Extreme4 Gen3 with 16 gigs memory and a GTX 560. If anyone has any ideas, please share. Thanks.

Share this post


Link to post
Share on other sites

Without an ethernet kext loaded my laptop will connect to the app-store fine with an ar9285 airport card

 

That makes sense, it's an airport card. It will not work with wireless cards that aren't recognized as "Airport".

 

Sorry, I was a little too fast on the trigger there.

Share this post


Link to post
Share on other sites

My Linksys (Ralink RT73) USB dongle is of course not recognized as an "Airport," yet I have no problem logging on to the App Store. Simply rerouted the feed through one of my ethernet ports, so it appears to be a hard line, though it's entirely wi-fi.

Share this post


Link to post
Share on other sites

Hi,

 

Thanks for the excellent guide. I followed your instructions carefully step-by-step but when booting from USB all i get is a white screen with cursor. I tried booting in verbose, but no errors. Could it be the smbios?

Share this post


Link to post
Share on other sites

I'm getting the same problem, would be nice to know whats causing it and how to solve it

 

Ive tried different chameleon(1820 and 2030) same result

Extensions, DSDT, smbios and boot.plist from my running system but still that white screen with the cursor :(

Currently running ML DP2 with no problems

 

My system is running on Gigabyte GA-H67MA-UD2H-B3, Intel i5 2400S and Sapphire Radeon HD 6850

Share this post


Link to post
Share on other sites

HD6xxx series has known permissions problems with ML. Thankfully this is very fixable:

 

Fix:

Make sure you've got hidden files shown. Then open your install usb, navigate to system -> library -> extensions and copy ATI6000Controller.kext to a safe location (e.g. copy it to the folder of essential files). Now delete the ATI6000Controller.kext. Boot the installer with the boot flags -v -x -f and hopefully it will boot (all be it at basic resolution with no QI / CE). Now install OS X as usual. Once OS X is installed use kext utility to re-install the ATI6000Controller.kext,

I've just done that off the top of my head so check I've got the method right and get back to me.

Share this post


Link to post
Share on other sites

HD6xxx series has known permissions problems with ML. Thankfully this is very fixable:

 

Fix:

Make sure you've got hidden files shown. Then open your install usb, navigate to system -> library -> extensions and copy ATI6000Controller.kext to a safe location (e.g. copy it to the folder of essential files). Now delete the ATI6000Controller.kext. Boot the installer with the boot flags -v -x -f and hopefully it will boot (all be it at basic resolution with no QI / CE). Now install OS X as usual. Once OS X is installed use kext utility to re-install the ATI6000Controller.kext,

I've just done that off the top of my head so check I've got the method right and get back to me.

 

How does one USE the kext utility? Or is it the kext wizard? Where do I reinstall the file once installed?

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 KristFlex
      Hello community!
      I searched everywhere, but couldn't find tables from one or both of these two macbooks, if someone here has these models, please, could you share the acpi tables with me? I really need them.
      Thanks
    • 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
      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 Drovosek
      Hello.
      I extracted .aml files via F2 to Clover, then moved iasl and patchmatic to .../bin and DSDT converted.aml to DSDT.dsl
      Then I patched the DSDT.dsl patch battery_HP-G6-2221ss.txt and clicked "Compile".

      11750, 6126, syntax error, unexpected PARSEOP_ARG1
      19689, 6126, syntax error, unexpected PARSEOP_METHOD
      19735, 6126, syntax error, unexpected PARSEOP_CLOSE_PAREN
      19738, 6126, syntax error, unexpected '}', expecting $end and premature End-Of-File

      The first error disappears if you remove all the "args", the third if you remove the closing parenthesis (but I do not know how this is the correct solution to the errors)
       

      debug_9278.zip
      battery_HP-G6-2221ss.txt
      DSDT after bat patching.dsl
      DSDT primary.dsl
    • By valueimagery
      Hello Everybody,

      First Hack here, and I have a fresh vanilla install with Mojave 10.14.2 closely following this vanilla installation:
      https://hackintosh.gitbook.io/-r-ha...p-guide/config.plist-per-hardware/coffee-lake

      I was surprised how well it worked initially with the above suggested settings. Only a few minor things (USB SSDT, signing the Bluetooth Kext, and switching from VritualSMC to FakeSMC) needed to be adjusted to get were I am currently.

      I built this machine to be a video editing/photography workstation. And so far pretty happy but would really appreciate if anyone has any knowledge or solutions with the few problems I'm still experiencing:

      1) FIXED (SEE COMMENT BELOW)
      Sleep issues waking up from sleep (maybe due to the ASMEDIA USB controller)
      -FIX WAS UNRELATED TO ASMEDIA CONTROLLER BUT DUE TO PREFERENCE OF "ALLOW BLUETOOTH DEVICE TO WAKE THIS COMPUTER"/ AN EXTERNAL USB 3 to SATA Cable for Hot plugging SSD's/2.5" HDD's.  With USB to SATA adapter unplugged/ Bluetooth preference changed, Mac now sleeps uninterrupted.

      2)
      The ASMEDIA USB 3.1 Gen 2 ports ejecting after sleep

      3)
      Am I currently using the correct setup for graphic acceleration with a connector-less ID for the UHD 630 and Radeon RX580? Specifically for optimized performance with FCPX. 

      4)
      Normal Power Consumption?


      I've attached my config.plist, ioreg.zip from RUNME app, SSDT-UIAC.aml (created using Rehabman Method), and my DSDT.aml (from this post for the Maximus x code courtesy of @MaLd0n ) If anyone has the time to take a look and maybe shed some light if I've done something wrong that be awesome.

      And for anyone looking to build a similar machine, I would highly recommend it, and feel free to use these settings. If these minor last things are addressed, this is a really solid hack.

      Cheers,
      Shark

      Detailed below is What is Not Working, The Build/BIOS Setup/Install Process, and What is Working.


      NOT WORKING:
      1) Sleep:

      If I put the computer to sleep, or it falls asleep on it's own, it wakes up immediately after sleep.
       
      I’m getting these errors in terminal trying to figure this out using the following two commands:

      Command: pmset -g
      sleep 10 (sleep prevented by powerd, sharingd)

      Command: log show --style syslog | fgrep "Wake reason"
      localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: XHC


      Here are my current settings:
      Clover:
      Boot -> Darkwake=0 (tried 1 and 2 as well)
      Energy Saver Settings: 
      Nothing Checked EXCEPT Put Hard disk to sleep when possible

      Would like Power Nap Enabled for the purpose of Time Machine, but doesn’t seem to be an option with Hackintosh?

      Using Terminal I have disabled the following:
      sudo pmset -a ttyskeepawake 0
      sudo pmset -a proximitywake 0
      sudo pmset -a standby 0
      sudo pmset -a autopoweroff 0

      2) USB 3.1 Gen 2

      For the 2.0/3.0 Intel Chipset, I’ve tried both the @headkaze Intel FB-Patcher v 1.6.8 and @RehabMan instructions on creating a SSDT. The FB-Patcher did not work completely. So I continued with @RehabMan method, created a SSDT, and sacrificed 2 x usb 2.0 ports and 1 internal RGB LED header to reach my 15 port max with 3.0 speeds on all SS ports.

      The ASMEDIA Ports work OOB with full 3.1 speeds. However the Eject issue can only be resolved by using an App like Jettison. And using that app doesn’t solve the sleep issue, computer still wakes. I’d rather figure out why the disks keep ejecting on sleep and if fixing issue #1 would resolve issue #2 or vice versa?

      Do I possibly need a power management ssdt? And how would I create one for the ASMEDIA chip?
       
      I've now tried using the attached DSDT.aml in my Patched folder.  I can now see it's working as my PCI devices in System Profiler are now populating (before it was stating no PCI devices).  However still experiencing sleep and eject issues.

      Ioreg Reads for the ASMEDIA 3.1 controller as:

      The 3.1 controllers for the back USB gen 2 ports are controlled by:
      RP05@1C,4/IOPP/PXSX@0/PXSX@01000000
      PRT1@01100000 (type C) (3.1 speeds)
      PRT2@01200000 (type A) (3.1 speeds)
      PRT3@01300000 (type C) (2.0 speeds)
      PRT4@01400000 (type A) (2.0 speeds)

      The 1 x 3.1 type C port on the front panel is controlled by:
      RP07@1C,6/IOPP/PXSX@0/PXSX@01000000
      HS01@00300000 (2.0 speed)
      SS01@00100000 (3.1 Speed) 

      There is also a SS02@0010000 under this controller, and as far as I can tell it does not have a function. Is there a way to disable, such as when creating an Intel Chipset SSDT?

      3) FINAL CUT ISSUES/ GRAPHIC ACCELERATION:
      Currently it doesn’t appear that the IGPU UHD 630 is doing much in iStats. In Apple System Profile/ Activity Monitor GPU window I only see RX580, no UHD 630. Is this how it should be? Or is that what connector-less ID should look like?

      With FCPX there is no crashing, glitchy exports, or rendering issues, however not sure if Graphic acceleration is being used to its fullest potential.
      The IGPU uses 5-8% Memory/ Processor when playing/scrubbing in timeline.
      And only 5-10% of the IGPU Memory (no processor) is used during any render or export of footage. The RX580 is still doing most of the hard work. My Bruce X times are quick 14-18 seconds, but I’m curious as to why the IGPU isn’t doing any of the lifiting. Is this expected? I'm pretty happy with how Lightroom and Final Cut are performing, I just want to make sure I've set the hardware up correctly.


      4) Power Consumption
      I have a general understanding of building computers, but not an expert especially with first time building a Hackintosh, overclocking, timings, voltages, etc…

      In HWMonitor the CPU Package Core reads blank, CPU Package Total is anywhere from 3.52w to 4.8w, the CPU Package DRAM is anywhere from 1.12 – 5.08. 

      Is this normal, or high? My temperatures seem fine and idle between 45-57 C, And Max shortly at 85 during stress tests.

      So just not sure if the CPU Power Consumption HWmonitor reporting is normal or abnormal. I've attached two HWmonitor screenshots 1 normal idle cpu, one while FCP rendering.
       
      THE INSTALL…
      Kexts Used:
      AirportBrcmFixup.kext
      AppleALC.kext
      BRCMFirmwareData.kext
      BrcmNonPatchRAM2.kext
      BrcmPatchRAM2.kext
      FakeSMC_ACPISensors.kext
      FakeSMC_CPUSensors.kext
      FakeSMC_GPUSensors.kext
      FakeSMC_LPCSensors.kext
      FakeSMC_SMMSensors.kext
      FakeSMC.kext
      IntelMausiEthernet.kext
      Lilu.kext
      USBInjectAll.kext 
      WhateverGreen.kext
      XHCI-unsupported.kext

      BUILD:
      ASUS ROG Maximus X CODE
      i7 8700k OC’d to 4800
      2 x 16gb Corsair Vegeance LPX DDR4 2400mhz C16 OC’d to 2666mhz
      Sapphire RX 580 NITRO+ 8Gb Graphics Card
      BCM94352Z Dell DW1560 (Wifi and Bluetooth Both Natively Working with Rehabman Kexts)
      BeQuiet! Darkrock Pro 4 
      EVGA 650w g1+
      Phanteks Enthoo Evolv X
      Samsung 28” E590DS (DP), Samsung 24” D300 (HDMI), Samsung 22” Syncmaster (DVI), Sony Bravia 48” (HDMI)

      Pre Install BIOS Settings:
      Updated Bios to Version 1704
      Loaded Optimized Defaults 
      AI Overclocker Tuner > Manual
      Extreme Tweeking > Enable
      Advanced \ System Agent(SA) Configuration →IGPU Multi-Monitor : Enabled
      Advanced \ System Agent (SA) Configuration →Vt-d: Disabled
      System Agent (SA) Configuration > Graphics Configuration > Primary Display > PEG
      USB Configuration > Legacy USB Support > AUTO
      USB Configuration > Keyboard and Mouse Simulation > Disabled
      APM Configuration > Power on by PCI - E/PCI > Disabled
      CSM: Disabled 
      Fast Boot > Disabled
      Boot Logo Display > Disabled
      Secure Boot > OS Type > Other OS
      DVMT Pre-Allocated > 128M

      WORKING:
      ICLOUD, iMessages, Handoff, etc

      Nitro+ 8GB GPU:
      4 Displays (DVI, DP, HDMI 1&2) from RX580 with Audio
      Currently set to 1920 resolution, but have option to use up to 4k resolution (3840x2160)
      Audio over DP and HDMI
      *Not sure if Airplay works as I don’t have an Apple TV, but registers in System Bar and say's looking...

      IGPU:
      Set in Connectorless State (AAPL,ig-platform-id: 0300923E)
      *If in a Connected State, slows down Bruce 5k Exports to well over a minute, with glitches, and does not send display signal to DP or HDMI (just green screen), even with connector type patch to correct type. So keeping it connectorless.
      *Not sure if Graphic acceleration is really working as FCPX is struggling with Multicam original media. This could just be the GH5 4k file encoding that FCPX struggles with. Was just hoping to remove creating proxy media from my workflow.

      Audio Front/ Back
      All working:
      Digital Optical Out 
      Back Green - Internal Speakers
      Front Headphones - Internal Speakers automatically changes to Headphones when plugged in
      Back Mic (Internal Microphone, not Line In)
      Front Mic (Internal Microphone, changes to a 2nd Line In)

      Bluetooth
      After initial install Bluetooth was seen by Mac System but not recognising any devices
      Thanks to @RehabMan Entered following code in terminal and bluetooth now works:
      sudo nvram boot-args="kext-dev-mode=1"

      I've now enabled this in my config.plist as well.
      https://github.com/RehabMan/OS-X-BrcmPatchRAM/blob/master/README-Mac.md
      (unsigned kernel extensions need to be enabled. Take the following steps in the Terminal)

      FANS/ TEMPS
      Temps or Fans were not registering with TG Pro using VirtualSMC.kext
      Fixed by switching from VIRTUALSMC.kext with older FAKESMC.kext with sensor gauges kexts. All working now.
      Computer Idles between 46 and 52 Celcius. Hits 81-87 when stress testing.

      USB 2.0/3.0 
      It appears that are physically too many USB ports on the Asus Maximus Code X to ever work with the 15 port limit safely. I created a custom SSDT that disabled USB 2.0 hs07(L),HS08(ML),12(aura led controller) to get usb 3.0 speeds on ss04,ss05, and ss06
      Be curious if anyone ever found a workaround for this...
       
       
      Overclocking:
      RAM:
      2400mhz to 2666mhz with Manual DRAM frequency change in BIOS. Did not change Latency or Timing and no crashing or panics so far. The 2666mhz speed is recognised in About this Mac and the Novabench RAM score increased.
      *Please advise if this method of overclocking the RAM is unadvisable.
       
      CPU:
      4.8ghz @ 75F @ 50% (Prime 95 test)
      Followed these BIOS steps:
       


       
      config_ValuesImac.plist
      DSDT.aml
      Send me Values-iMac.zip
      SSDT-UIAC.aml


    • By BugsB
      After the 309 Update, what should be the login screen (after the verbose mode screen with all the lines flashing by and the brief intermediate black screen with the progress bar), is now a black screen, with just the mouse pointer movable (doesn't change when pressing keys).
       
      On my X510UAR in High Sierra 10.13.6 booting to Desktop with BIOS 308/ 303/ 301 has always worked fine regardless if with static or hot patch, and even w/o any DSTD patches.
       
      Latest hotpatch v.8 from saintno1997, but same thing with original/ stock ReHabMan config_HD615_620_630_640_650.plist instead of hotpatch config.plist, or any previous EFI folder from backup.
       
      Latest Clover versions (by RehabMan on Volumes/EFI, by Slice on Volumes/Clover) and latest versions of all kexts, installed to L/E.
       
      When I wait a few seconds for the black screen, type my PW, press enter, plug in my external monitor, it usually kicks in after some seconds displaying the Desktop, then the Laptop screen comes alive, too (or I need to unplug the external for that to happen)!
       
      But at first everything was painstakingly slowed down, like running on 1% CPU power. Activity Monitor did not reveal anything unusual.
      I managed to solve at least that one malfunctioning aspect by setting the UHD 620 ig-platform-id 0x59160000 in Clover config/ Graphics, but still many things graphics-related are "sticky":
      - apps with transparency effects etc. misbehave
      - Dock magnification tends to stick
      - no preview when I type something into Spotlight
      etc.
      - dragging files and folders

      I've done file-by-file diff compares of corresponding *.dsl pairs with Beyond Compare 308 --> 309. Final findings:
       
      DSDT: only two differences:
      309, line 70 (added line):
      External (_SB_.PCI0.GFX0.GLID, MethodObj) // 1 Arguments (from opcode) then in both BIOSes, under Scope (_SB.PCI0.LPCB.EC0):
      308, Line 40301:
      Device (LID) { Name (_HID, EisaId ("PNP0C0D")) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Store (One, Local0) Store (RPIN (0x11), Local0) If (LEqual (Local0, Ones)) { Store (One, Local0) } Return (Local0) } } was changed into
      309, line 40263:
      Device (LID) { Name (_HID, EisaId ("PNP0C0D")) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Store (One, Local0) Store (RPIN (0x11), Local0) If (LEqual (Local0, Ones)) { Store (One, Local0) } If (IGDS) { ^^^^GFX0.GLID (Local0) } Return (Local0) } } So all I see accdg. to Beyond Compare is a If (IGDS) condition inserted into Device (LID).
       
      Removed the 4 lines with the If (IGDS) condition, compiled, applied to Clover/ACPI/patched, rebooted --> black screen.
       
      Applying the misc_LidPoll.txt work-around via MaciASL [misc] Poll for LID changes + ACPIPoller install --> reboot did NOT solve this, either.
       
      SSDTs: the 6 SSDTs SSDT-x.dsl and SSDT-x3_x.dsl are all exactly the same = did NOT change from 308 --> 309.
       
      Unless there is a graphics related change in one of the other SSDTs, ^^^^GFX0.GLID (Local0) would be the culprit causing a black screen where the login screen should be, and simply commenting it out does not help any.
       
      Does that produce an incorrect lid state leading to a black screen? Or is this a framebuffer issue introduced by the 309 upadte?
       
      I next also tried the other ig-platform-ids I know of for the UHD 620 (0x59180002 and 0x59180009), but these don't work.
       
      From what I know studying the boards, there is no other ig-platform-id which would make sense trying, right? this being a ACPI related issue. As usual ASUS did not provide a change log.
       
      Here's what else I've already tried, with same result:
      - boot with -f
      - boot into safe mode -x
      - static patch config.plist w/o any DSDT
      - empty EFI/CLOVER/ACPI/patched folder w/o any SSDTs
      - put to sleep and wake back up
      - SMBIOS sys def 15,2 (hotpatch v.8 from saintno1997), or 14,1 (the one I have always been running)
      - in Clover, re-activated kext patch AppleBacklightInjector.kext (credit RehabMan)
       
      What to do next - how to proceed from here?
       
      What's new with this Notebook after this 309 BIOS update is that it does NOT even boot w. static patch config.plist and no patched DSDT. Therefore I don't think that creating a static patch DSDT would help here.
       
      Black.dragon74's gen_debug script gets stuck at "dumping Clover files" in this limited mode, even after 30 minutes or so, and neither does it work in single user mode mode in general, so I generated problem reporting files booted in 309 BIOS manually (below). I attached the full debug_BIOS_308_GOOD.zip, + the manual_debug_BIOS_309_Black-Screen.zip with only the changed files, all other files already being present in debug_BIOS_308. That way you can have a look at what changed from 308 to 309 in the graphics related sections, and can hopefully give me hints how to proceed.
       
      Back on 308 for now, but concrete pointers are very welcome! Thanks, everybody.
       
      PS: for those with DSDT knowledge, here is a Google search on If (IGDS) ^^^^GFX0.GLID (Local0).
      manual_debug_BIOS_309_Black-Screen.zip
      debug_BIOS_308_GOOD.zip
×