Jump to content
daniel_iversen

How do I get ATI/AMD Radeon HD 5570 graphic card working on High Sierra (10.13.6)?

1 post in this topic

Recommended Posts

Hi there,

TL;DR; Any idea on how I can get an ATI Radeon HD5570 graphics card working on High Sierra?

I just installed High Sierra, and I read it was supposed to be “Out of the Box” to get these AMD/ATI cards working, but it’s been very hard and I’ve read like 100 articles and done a million experiments to no avail.

The card is built in to a HP TouchSmart 610-1030a touch screen PC, and the symptom/problem is:

- I can at best get a decent resolution at best, but no acceleration (I'm testing with the Chess app but can visually see it everywhere) and the OS only detects 7MB memory whereas it has 1GB.

I’ve tried a combination of:

- OOTB (then there’s no detection really)

- Clover setup in “Graphics” tab - combination of these settings:

- Inject ATI

- Load VBIOS/patch VBIOS

- Entered my card details (what I thought) - vendor ID 0x1002, product ID 0x68d9, FBName “Eulemur” or “Baboon”

Also;

- I have Lilu.kext and WhateverGreen.kext

- I've got the "EmuVariableUefi-64.efi" file deployed in my drivers64UEFI folder 

- Tried using “downgraded” (from Sierra) versions of kexts AMDRadeonX3000.kext, AMDRadeonX3000GL.Driver.bundle, IOAccelerator2D.plugin, IOAcceleratorFamily2.kext (I think my wifi disappeared with the IO ones which makes sense I suppose)


At worst in the "About this Mac" it just says "Display 3MB" (and often with poor resolution), and at best it says "ATI Mobility Radeon HD 5570 7 MB" but with no acceleration (and no recognition of the 1GB VRAM).

Any ideas of what I’m supposed to do? I don’t really get all the stuff I read about patching and rolling my own kexts etc but my impression was that after Sierra I wasn’t supposed to do that for the AMD/ATI cards.

Thanks a lot in advance!!

Share this post


Link to post
Share on other sites
Advertisement

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 corbrink
      Hi,
      I have the following system:
      - Gigabyte Z370M-D3H M-ATX
      - Core i7-8700K Coffee Lake
      - Gigabyte Radeon RX 560 4GB
      - Crucial Ballistix 16GB DDR4
      - 960 EVO 1TB NVMe SSD
      - 850 EVO 500GB SSD
      - Crucial 500GB SSD
      - The 2 500GB SSD's run in Raid for data storage.
      - Western Digital 3TB HDD - Time machine
      - EFI here (too large to attach): EFI.zip

      Questions:
      1. I have a dual screen running from Radeon card, 1 on DP and 1 on HDMI. The one screen on DP goes randomly blank from time to time. Any ideas?
      2. I've read that the kexts should preferably be installed in /library/extensions. I would like to know what kexts should remain in the EFI. I read that you should install FakeSMC in both locations (EFI and L/E). If I follow this route must I change something in the config.plist?
      3. USB info in System Information (attached does not seem correct. I've followed the changes suggested but I'm not sure if this is the best it can be.
      4. Are there something in the EFI and config.plist I don't need or doing wrong?

      Feedback will be appreciated.


    • By 1Ale1
      Ciao a tutti, ultimamente ho deciso di mettermi al lavoro e fare un investimento a lungo termine comprando un fisso che ho assemblato pezzo dopo pezzo leggendo numerosi forum per essere bene informato sul miglior hardware che potessi ottenere per un Hackintosh ottimizzando al meglio i costi: ho finito così per comprare:
       
      Hardware:
       
       
      -Motherboard: Gigabyte Z390 Aorus Pro (Rev 1.0)
      -CPU: Intel i7 9700k raffreddato a liquido (CoffeLake)
      -GPU: AMD Radeon RX580 (avendo letto le eccellenti prestazioni a ottimo prezzo per MacOS)
      -RAM: 32GB DDR4 Crucial Ballistix Sport LT (4x8GB 3000MHz)
      -NVMe SSD Samsung 970 Evo 250GB M.2 dedicato solo a MacOS, nel secondo slot della Mobo M.2 avrei poi messo un Western Digital Blue da 250GB con Windows 10 su metà disco e per l'altra metà il Debian che sto utilizzando adesso
       
       
      Poi mi sono messo subito al lavoro per cercare di far partire questo benedetto MacOs su una macchina non ufficiale, ho tovato quindi questa guida su GitHub che era molto simile alla mia configurazione:
       
      https://github.com/cmer/gigabyte-z390-aorus-master-hackintosh/blob/master/STEP_BY_STEP.md
       
      Dopo aver fatto partire una macchina virtuale per configurare la USB come comunemente viene fatto, scaricando l'applicazione e facendo il "burn/copia dei file" di macOS su pennetta esterna rendendola bootabile solamente da un pc ufficiale mac, sono passato alla configurazione di Clover (l'EFI installer, cartella che allegherò qui sotto, ma prima leggete il problema): Ho messo i driver necessari, mettendo quelli che lui menzionava sotto la sezione "building the usb installer"
       
      https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/building-the-usb-installer
       
       
      Install Clover for UEFI booting only
      Install Clover to the ESP
      Under Drivers64UEFI:
      AptioMemoryFix (the new hotness that includes NVRAM fixes, as well as better memory management) (che poi ho dovuto rimuovere, leggi sezione https://github.com/cmer/gigabyte-z390-aorus-master-hackintosh/blob/master/STEP_BY_STEP.md#fixing-kernel-panics-at-rebootshutdown)
      VBoxHfs-64.efi (or HFSPlus.efi if available) - one of these is required for Clover to see and boot HFS+ volumes. If you see the option to enable it in the installer, make sure it's selected - if you don't see it in the installer, verify that one of them exists in the EFI -> CLOVER -> drivers64UEFI folder
      ApfsDriverLoader - (Available in Dids' Clover builds - or here) this allows Clover to see and boot from APFS volumes by loading apfs.efi from ApfsContainer located on block device (if using AptioMemoryFix as well, requires R21 or newer)
       
      applicando piccole modifiche a causa di un errore già riportato da questa persona che ha scritto la guida di GitHub di sostituire AptioMemoryFix-64 (dalla cartella EFI/EFI/CLOVER/driver64UEFI) con OsxAptioFix2Drv-free2000, questa infatti riportava  quanto segue dopo aver detto di aver sostituito AptioMemoryFix-64.efi con OsxaptioFix2Drv-free2000:
       
      "I am told that there are downsides (that I don't fully understand yet) to using OsxAptioFix2Drv-free2000, so do this at your own risk."
       
      Ho configurato poi il config.plist
       
      Come diceva lui, partendo da questo file: https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/config.plist-per-hardware/coffee-lake e applicando le modifiche che sotto ha descritto, del tipo:
       
      Open coffeelake_sample_config.plist with Clover Configurator (right click → Open With → Clover Configurator)   In SMBIOS: - Click the button with an up/down arrow (middle right). Chose iMac18,3. This is important since we'll be connecting our monitor to the RX580. The HDMI port on our motherboard is NOT yet working for Hackintoshes. - Make sure the serial number generated is an iMac (mid-2017) by clicking Model Lookup. - Ensure that Check Coverage reports that the serial is NOT valid. You don't want to use somebody else's serial number. - While you're here, copy your Board Serial Number to your clipboard. You'll need it soon.
      In Rt Variables: Paste your Board Serial Number in the MLB field. Set CsrActiveConfig to 0x0 which enables SIP for extra security. This should work just fine for a Vanilla Hackintosh install and is how genuine Macs ship. In Boot: Change the Custom Flags to: shikigva=40 uia_exclude=HS14 (this disables onboard Bluetooth since we'll be using an external Broadcom Wi-Fi/Bluetooth adapter) In ACPI: Click List of Patches and enable the following: Change GFX0 to IGPU In Devices: Set Inject to 16. Now to enable our headless iGPU, we need to fake the device id. To do so, Click Properties, select PciRoot(0x0)/Pci(0x2,0x0). Then, click the + button to add a property. Add the following: Property Key: device-id Property Value: 923E0000 Value Type: DATA Click the Export Configuration button (bottom left), then Save As config.plist. Copy your newly generated config.plist to /EFI/CLOVER/ on your bootable USB key.  
      Impostazioni BIOS
       
      E avendo settato nel BIOS le impostazioni che questa perona configliava all'inizio della guida,                       (N.B. la mia versione di Bios è l'ultima, F7 https://www.gigabyte.com/Motherboard/Z390-AORUS-PRO-rev-10#support-dl-bios) (a quanto risulta il giorno 7.01.2019)
       
      Load Optimized Default Settings Peripherals → USB Configuration → XHCI Hand-off : Enabled Chipset → Internal Graphics : Enabled (important for Quicklook/Preview) Please note that we will be using our internal GPU in headless mode only and this guide assumes that. This is how an iMac18,3 (what we're basing our build on) behaves. That's it! I literally didn't change anything else and it just worked.
       
      Anche per me ha funzionato. Comunque lui riportava ulteriori settaggi, aggiungendo:
       
      However, these are settings that are generally recommended. Your mileage may vary:
       
      BIOS → Fast Boot : Disabled BIOS → LAN PXE Boot Option ROM : Disabled BIOS → Storage Boot Option Control : UEFI Peripherals → Trusted Computing → Security Device Support : Disable Peripherals → Network Stack Configuration → Network Stack : Disabled Peripherals → USB Configuration → Legacy USB Support : Auto Peripherals → USB Configuration → XHCI Hand-off : Enabled (Extremely important) () Chipset → Vt-d : Disabled (non l'ho messo e parte a volte, quindi penso che se parte non ha una importanza così rilevante) Chipset → Wake on LAN Enable : Disabled (era già così) Chipset → IOAPIC 24-119 Entries : Enabled  
       
      Il sistema è partito e soltanto alcune volte dava il seguente errore:
       
      Error allocating 0x11996pages at 0x000000001d453000 alloc type 2
      Couldn't allocate runtime area.
       
      Credo che sia questo piccolo problema: la NVRAM.
      Non riesco bene a capire dove cercare per sapere con esattezza se è supportato nativamente o meno. Ho cercato di informarmi, voi potreste dirmi se è vero?
      Premendo poi Ctrl+Alt+Canc riavviavo e selezionando da Clover l'NVMe interno partiva senza dare questo errore, per cui il kernel non trova spazio perché la memoria Non Volatile ad accesso Randomico è troppo frammentata, come
       
      Questa guida riportava:
       
      Primo post:
      https://nickwoodhams.com/x99-hackintosh-solving-osxaptiofixdrv-allocaterelocblock-can-not-allocate-relocation-block/
       
      Post aggiornato nel 2016:
      https://nickwoodhams.com/x99-hackintosh-osxaptiofixdrv-allocaterelocblock-error-update/
       
      Mi sono letto tutto e ho capito che lui applicava anche delle modifiche al file: "Changes to OsxLowMemFixDrv-64.efi were simply editing 0x10000000 to 0x20000000."
       
      Ho quindi seguito il suo consiglio di mettere OsxAptiofix Emuvariable 64 e Test2-2016.efi (che lui aveva creato) ma il problema sembrava persistere, più raramente
       
      La mia cartella driver64UEFI di ora
       
      Dopo aver trovato una strada senza soluzoni anche lì mi sono rivolto a degli amici, e di questo errore ne ho parlato anche con utenti del gruppo Telegram "Hackintosh Italia" che sono stati e ancora sono molto gentili ad aiutarmi spiegandomi che si tratta di un problema di NVRAM, che nel mio caso, avendo installato questi .efi file nella cartella EFI/EFI/CLOVER/driver64UEFI (che ancora è cosi attualmente, oscillando tra couldnt allocate runtime area (anche dopo aver definitivamente staccato la corrente dopo aver spento il PC per capire se poteva aiutare) e a volta anche nessun errore)
       
       
      -ApfsDriverLoader-64.efi
      -DataHubDxe-64.efi
      -EmuVariableUefi-64.efi
      -FSInject-64.efi
      -HFSPlus-64.efi
      -NTFS-64.efi
      -NvmExpressDxe-64.efi
      -OsxAptioFix2Drv-free2000.efi
      -PartitionDxe-64.efi
      -UsbKbDxe-64.efi
       
      In più ho aggiunto gli RC Scripts (come mi è stato consigliato dai membri del gruppo telegram) sul disco interno in cui mac è installato.
       
      Togliendo quindi qualsiasi test.efi o test2- 2016.efi ed ascoltando chi ne sapeva di più. Ora mi trovo a dover affrontare diverse volte questo errore dovendo riavviare per risolverlo, cosa che mi fa dedurre che Osxaptiofix2 2000 sia un po' instabile nel pulire la NVRAM prima di avviare la macchina/ allo spegnimento di questa.
      Questo problema di couldnt allocate runtime area persiste sebbene prema F12 dalla schermata di Boot di Clover.
       
      Vi chiedo gentilmente una mano, inoltre mi è stato detto che siccome il sistema da:
       
      -"3.6 GHz unknown nella sezione "Processor"
      -non riconosce la RAM con un Vendor ID? (del tipo Ballistix dovrebbe essere?)
       
       
      Serve di rivedere il config.plist che ho creato, rivedere i DSDT e gli efi? sono a posto?, (mi hanno detto che gengik84 fare, ma accolgo volentieri l'aiuto di tutti) ,  vi mando una foto della schermata di "About this Mac" e della EFI in allegato. Quello che farò sicuramente mentre attendo vostre risposte è il downgrade da 10.14.3 Beta a 10.14.2, l'upgrade l'ho fatto pensando che magari avrei aggiustato qualcosa, ma l'errore come lo dava prima lo dà ora, non credo che questo cambi molto le cose in gioco. Comunque è meglio non essere in Beta per aggiustare gli errori.
       
       
      Grazie mille per essere arrivato a leggere fino a questo punto, lo apprezzo molto.
       
       
      Per la cartella EFI: sono 22MB zippati, in allegato non entrano...
       
      https://drive.google.com/open?id=106jXkDB0Id045lzIIzAn9F5MwnzWFv3X
       

       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       

       
       
       
       



    • 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 macinsane
      Mojave (and maybe High Sierra 10.13.6) on Asrock H370M-ITX/ac and getting RX560 or RX580 to work with Intel graphics for full hardware acceleration
       
      Components used:
       
      Core i7 8700, UHD 630
      Gigabyte Radeon RX560
      Wifi/BT BCM943602BAED (DW1830) M.2
      Sapphire Nitro RX 580
      Samsung PM961 NVMe SSD
       
      *This guide requires you to know the basics, meaning how to create a macOS install drive, installing and using Clover. There are great beginners guides out there! As always you need at least FakeSMC to boot, every other kext I’ve used is mentioned in the guide. For Mojave beta you need to be enlisted with your Apple-ID in Apple’s beta programme. What is described here may work for High Sierra 10.13.6, but I doubt it to be reliable. Even in early beta status (PB3) Mojave runs much more stable and smoother than High Sierra ever did for me.* 
       
      *UPDATE Mojave final*
      For the final release of Mojave you can use my attached Clover folder as a reference. If you don't have a Radeon RX 580 installed or you prefer WhatEverGreen just use the DSDT_no_graphics.aml and rename it to DSDT.aml. You need to have updated to BIOS V3.00 to use it.  
       
      *UPDATE*
      I've updated to BIOS Revision 3.00 which seems to work fine in contrast to 1.50. Already compiled a new DSDT and uploaded it alongside a new config.plist. You can use both if you like. If you don't use a RX 580 you need to edit the PEG0-PEGP section in the DSDT to adjust it to your graphics hardware. With this DSDT and config in place you'll only need FakeSMC, IntelMausiEthernet, USBinjectall plus XHCI-300-Injector, Lilu plus AppleALC for Sound. You can add Shiki for iTunes DRM playback if you like, I've uploaded the latest version as well. Avoid Whatevergreen at this time.
       
      UEFI-BIOS settings:
       
      The board comes with BIOS version 1.20, there is an update 1.50 on the Asrock website. Usually it is good to stay updated but in this case I’ll recommend to stay on 1.20, because the 1.50 version seems to be unstable and I had restarts upon wake and things like that I couldn’t get fixed even with dsdt patches. So I just downgraded to 1.20 which runs fine.
      Settings needed: Just the usual. Disable fast boot and security boot (everything Windows-related), disable vt-d and enable XHCI hand-off. Activate multi monitor support and set VRAM to 64MB to activate the Intel IGPU. From what I’ve read most people recommend 128MB but I find the 64MB setting to be more reliable, getting artifacts with settings below or above 64MB. 128MB may be needed for 4k support, though. *Update* BIOS V 3.00 with Mojave final release works fine with 128MB. As for nVidia users: You may have to disable the Intel graphics. I’m using an AMD card and that is the brand to go these days since Apple decided to work with AMD
       
      Clover and power management:
       
      I recommend upgrading to 4586. It seems that Aptiomemoryfix is now working with H370 chipsets. I stayed on OsxAptiomemoryfix2 together with Emuvariable and it works. Feel free to experiment. *Update* Now using OsxAptioV3.  
      For power management with your CoffeeLake cpu you can just tick plugin type within Clover or compile a ssdt with Pikeralphas script. Mojave reports my cpu correctly as Core i7 since PB3, before that it is just “Unknown” but that is just cosmetic. 
       
      Graphics:
       
      *UPDATE*
      Whatevergreen 1.2.3 now supports Displayport on Nitro RX580. Still recommend DSDT or SSDT port activation instead as it runs more reliable and faster than WhatEverGreen.
       
      *UPDATE*
      I updated to PB4/DP5 and switched to a Sapphire Nitro RX 580. You don't need to spoof Kabylake anymore, SMBIOS 18,x now works and can use my attached DSDT_RX580 for your convenience! You'll need it for displayport to work as primary display or else you get black screen on boot and can use only HDMI. Problems are the same as written below in the graphics section. If you need iTunes you absolutely need to keep a copy of the latest Shiki that is available, because it is discontinued. The newest WhatEverGreen-Fix (1.2.0/1.2.1) does not work! If you want to use Final Cut and don't need iTunes just stay away from Shiki or Whatevergreen. 
       
       
      This is the worst part. Getting the Radeon to run correctly alongside the Intel graphics took me weeks to figure out. 
       
      While RX570 and 580 run out of the box in most cases, the RX560 models often do not or at least not correctly. Apple even banned them from eGPU use. For my approach you cannot use “Whatevergreen.kext”, it simply didn’t work for me the way I needed it. Instead I added some fixes to my DSDT to set the correct number of ports used (DP, HDMI, DVI) and tell macOS to use the correct frambuffer. For those who are not into dsdt editing I added my DSDT, look at the “PEGP” section how it is done. This works for the RX560 using the “Acre” framebuffer, you can replace it with “Radeon”, that works too. Other cards need a different framebuffer and a different number of ports. You can do it!   BTW: Do not buy this Gigabytecard!!! It has some weird VBIOS on it, which caused me nightmares before I got the card to work! Buy a Sapphire card instead, they are used by Apple too.   
       
      To get full hardware acceleration for encoding videos you have to have the Intel graphics enabled alongside your AMD card. Problem is, you cannot have it running simply as a second graphics card but you’ll need to “hide” it, means telling macOS that it doesn’t have any display connectors. Otherwise you’ll have screen artifacts or in the worst case just constant crashes. This can be done by adding a certain ig-platform-id in Clover. If you use 59120003 the Intel graphics will not show up in system profiler but it is there. You can check it with iStats or HWMonitor or look if the Kaby Lake graphics kexts are loaded.  This ID makes the CoffeeLake UHD 630 to be recognized as a Kaby Lake gpu that has no display ports, is just used as a helper card.
       
      You’ll need it as a helper card for video encoding. That is what Intel graphics are used for in Macs, to support video encoding on the hardware side. You can check if hardware encoding is supposedly enabled by using MacX Video Converter Pro and VDADecoderChecker. If both say “yes” and “fully supported” this is a good start. But despite the widespread belief this doesn’t mean everything is set correctly! You now have to find out, how to get both cards working together. This is the moment where you have to choose between work and fun: Are you using FinalCut Pro for video editing or are you planning to use iTunes for entertainment? Up until this day (Mojave PB3 PB4/DP5, High Sierra 10.13.6) you cannot have both working correctly! I’ll show you how it is done both ways. 
       
      The best settings for Final Cut:
       
      Use the DSDT I’ve added with the respective AMD settings for the RX560 or modify them for your graphics card.
       
      Use SMBIOS for iMac17,1 (14,2 does work but picture over DP port is ugly, iMac 18,1/2/3 do not work *Since Mojave PB4 they do work at least for RX580*) in Clover.
       
      Have AppleIntelKBLGraphicsFramebufferInjector_3e9x.kextin your Clover/kexts/Other folder.
       
      Until Mojave PB2 (may work on High Sierra 10.13.6):
       
      Fake-ID 3E928086 plus ig-platform-id 59120003
       
      These are the correct setting when installing Mojave (usually you will start with PB1 as the full installer).
       
      For Mojave PB3 and higher:
       
      Fake-ID 59128086 plus ig-platform-id 59120003
       
      After upgrading to PB3 you will get a black screen with 3E92 fake id because PB3 introduces Coffee Lake kexts and macOS will use these kexts instead but that doesn’t work with our ig-platform-id. So you can download the update to PB3 but before installing it you’ll need to change the fake-id to a usual Kaby Lake id. While this didn’t work in High Sierra and the first two Mojave betas (meaning you didn’t get full hardware encoding) it is now magically working with PB3. It is safe to remove AppleIntelKBLGraphicsFramebufferInjector_3e9x.kext after upgrading to PB3.
       
      For Mojave PB4 and higher (including final release):
      Only add ig-platform-id 3E920003 and inject Intel = Yes in Clover, no need for spoofing a fake id anymore. Now iMac18,3 works best with AMD. Intel only users should use iMac18,1 instead.
       
      The best setting for iTunes and why it is the worst for Final Cut:
      Just do the same thing as for FinalCut, put Shiki.kext into your Clover/kexts/other folder and add -shikigva boot argument. You can use -shikigva=1 or 2 or 12 it will work either way. Now you can watch movies with iTunes, yay! But it has some sideeffects. You cannot use this setting when seriously editing with Final Cut.
       
      While this works by tricking macOS to use the IntelGraphics to play protected video content, it doesn’t seem to be the way real Macs are doing this. As soon as you open FinalCut you will notice (check this with iStats or HWMonitor) that the Intel graphics is not or only barely utilized under certain circumstances depending on your material. Instead cpu usage skyrockets, indicating that slow software rendering is used instead of hardware encoding through Intel graphics. To make it worse the Radeon still “thinks” there is an Intel graphics helping so it does not run at highest potential. 
       
      Wifi and Bluetooth
       
      *UPDATE*
      With Mojave PB4/DP5 Bluetooth stopped working with Rehabman's kext, my MagicMouse simply isn't connecting anymore. I decided to finally remove the card because handoff isn't working anyway these days with M.2 or NGFF bluetooth on High Sierra or Mojave (tried several ones "the internet" claims they would work oob but they do not ;)). That is what I wanted Bluetooth for. If you need Wifi I recommend you go with a cheap Wifi-only card, you don't need to pay 30 or 40 $ for dual cards that won't work the way they were intended to work. If you are on a micro ATX board and can have a graphics card plus PCIe Wifi/BT-card that actually connects to a physical USB port on you're board then you may be lucky enough to have handoff working as expected. I'm having a wifi repeater laying around with an ethernet port in case I may need wifi someday on my hack. 
       
      I swapped the Intel Wifi card that was coming with the mainboard plugged into the onboard M.2 port with a compatible Dell card. The DW1830 or BCM943602BAED. The wifi part runs half way out of the box, but if you want the card to appear as Apple AirportExtreme and set the country code according to your country you need to put FakePCIID_Broadcom_WiFi.kext into Clover/kexts/other and add some Clover kext-to-patches by PMHeart. 
       
      Name: com.apple.driver.AirPort.BrcmNIC
      Find: 75166644 3BA3581A 0000750C 4183FE04 7406
      Replace: 66906644 3BA3581A 00006690 4183FE04 6690
      Comment: AirPortBrcmNIC - PCIe in 10.13.x
       
      Name: com.apple.driver.AirPort.BrcmNIC
      Find: 4183FCFF 7435488D 55D0
      Replace: 66C70644 45EB348D 55D0    (*this is for DE country code, change for your need)
      Comment: BCM4352-Country Code 
       
      Bluetooth will work thanks to Rehabman’s kexts. You’ll need BrcmPatchRAM2.kext and BrcmFirmwareData.kext OR BrcmFirmwareRepo.kext. The Data.kext can be injected through Clover, just throw it into the kexts/other folder, the Repo.kext has to be installed in /Library/Extensions on your mac drive, it won’t work with Clover. I had issues with the Data.kext, Bluetooth was gone on every second or third reboot. The Repo.kext is more reliable, haven’t had any issues yet. I really don’t like the kexts to be installed in my system but I guess I have to live with it for the time being.
       
      Oh, handoff and continuity don’t work, doesn’t matter that system profiler shows them as enabled. At least it works in one way: the mac can handoff Safari pages to my iPhone, but not the other way around. Documents opened on my phone show up in the dock, but they are not loaded. 
      This issue is around since at least High Sierra and from what I’ve read Rehabman is not going to fix this, because he founds this features not worth it. I have to disagree, these are very convenient and valuable features if you work with desktop, laptop and tablet in different situations, I miss this capability very much!    
       
      Audio
       
      Audio works with Lilu.kext plus AppleALC.kext and you need to inject Layout ID=1 in Clover if you don't use a patched DSDT. For Mojave use the boot setting -lilubetaall to force the kexts to load. If you like to have DP or HDMI audio add a HDAU device to your dsdt (see mine for reference). There's an audio patch already added in my DSDT, so you don't need to use the Clover patch.
       
      Credits:
      Credits go to this great community! I hope I mentioned everyone in this guide whose insights made this hack possible. If I have forgotten someone please let me know!
       
       
       
       
      CLOVER_Mojave_Final.zip
×