Jump to content

macinsane

Donators
  • Content count

    168
  • Joined

  • Last visited

About macinsane

  • Rank
    InsanelyMac Geek

Recent Profile Visitors

5,309 profile views
  1. Hi! First of all: You should never use a DSDT from a different board (even the bios version is important). That your board boots with it is pure luck and maybe it is in fact the root of your problems. Second: Why do you have VoodooPS2 installed? Third: There seems to be problems with your config.plist as well. <key>CsrActiveConfig</key> should be <string>0x67</string>. So as a first step, get rid of the dsdt and get the config.plist in order. Can you boot without dsdt? The problem with my board was that a dsdt was mandatory because else mac OS wouldn't recognize the SATA drives. Don't you need the webdrivers for your GTX 750 or do you have one of these rare Kepler-based cards?
  2. Dear fellow hackintosh people, does anybody know a solution for the memory "cannot allocate" error on Z390 chipsets? Aptiomemoryfix, osxaptiofix 1,2 and 3 do not work, I simply cannot boot with them. The only aptio fix that is working for me somehow is OsxAptioFix2Drv-free2000.efi. But even with that clover hangs at every second boot, which is really annoying. If anyone please can help me out?!
  3. I guess you are right. From what I understand the hope was that this renaming alone would help. After weeks of testing the best results I get in terms of graphics performance is just using pikeralpha's graphics device policy patch to activate my display port and leave everything else untouched. Whatevergreen always gives the worst performance and doesn't even enable DRM playback. I'm looking forward to check out Mac Mini 2018 smbios and see if it makes a difference. It bothers me that the RX580 was just a waste of money for the purpose intended, could have stuck with cheap 560 instead. At least it has improved my gaming performance in Windows... What really annoys me is that people everywhere claim that their 580's would run oob just fine and that they still recommend it (by what they only mean that they get a working screen...). With prices falling anyone who intends to do video editing should definetely go for Vega instead or just take the cheapest AMD card around.
  4. macinsane

    Multiboot from External drive

    Mojave runs 32-bit apps just fine, it just warns you that future versions of mac OS may not.
  5. Unfortunately not, there is a thread on Hackintosh-Forum.de (kext is in post #37) where people claim to get the RX cards running as native Radeon Pro's what should give you better results but it seems to be very fragile at the moment. I tried it and noticed no difference at all performance wise.
  6. You might have a picture on another port (DisplayPort or HDMI). If you don't you need to patch DSDT or insert RadeonDeinit / ATI inject in config.plist. The provided kext alone does not enable correct display type!
  7. No, this is code for the DSDT.aml file that "represents" your computer's main Acpi table. You could say this is what the UEFI or BIOS tells any operating systems (be it Windows or Mac OS) what kind of PC it is, which and where devices are present and many other things. If you have no idea what I'm talking about you should start reading guides about "How-to-patch-DSDT" to get yourself familiar with the topic. This is generally a good thing to know if you are hackintoshing. But if you don't care at the moment you could try to just tick "Inject ATI" and "RadeonDeinit" in CloverConfiguartor and see if that gives you a picture on the Displayport for a start. Remove Whatevergreen before that.
  8. What I mean is this: Device (PEGP) { Name (_ADR, Zero) // _ADR: Address Name (_SUN, One) // _SUN: Slot User Number Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x10) { "AAPL,slot-name", Buffer (0x07) { "Slot-0" }, "@0,name", Buffer (0x0C) { "ATY,Orinoco" }, "@0,AAPL,boot-display", Buffer (One) { 0x00 }, "model", Buffer (0x12) { "AMD Radeon RX 580" }, "hda-gfx", Buffer (0x0A) { "onboard-2" }, "ATY,Copyright", Buffer (0x33) { "(C) 1988-2017, AMD Technologies Inc." }, "ATY,VendorID", Buffer (0x02) { 0x02, 0x10 }, "ATY,DeviceID", Buffer (0x02) { 0xDF, 0x67 } }) } } With this you can tell Mac OS which display to initialise and which framebuffer to use.
  9. This topic is about what do if have no Vega The aim is to enable AMD rendering on Polaris GPU's (RX 4xx/5xx) the way it works for Vega cards.
  10. This is bothering me for a long time now: Why does Apple deliberately disables the the RX4xx, RX5xx capabilities to hardware encode HEVC and is using Intel Quicksync instead? Is it to make the iMacPro look better than it is? I stumbled over a thread at tony-mac where people are going a totally different road for Radeon graphics. Instead of hassling around with getting Quicksync to work, they proposed to activate the AMD hardware renderer for Polaris GPU's. I tried it out and it works...somewhat I used a dummy kext from that tomato thread and edited it, so that it enables the AMDU7V4 IOGVACodec like on Vega cards, switched to iMacPro1,1 SMBIOS from iMac18,3, disabled the IGPU and the results were astonishing: My 3:34min 4k50p film was rendered by FCP with HEVC in 2:34 minutes. Nearly half the time than with Quicksync! With the iMac18 SMBIOS and the "help" of Intel Quicksync it took FCP 4:41 minutes to get it done! The problem is: As soon as the "wrong" IOGVACodec is enabled H.264 encoding leads to Mojave crashing at once (be it FCP, QuickTime or Videoproc). Watching H264 material is fine, though. If anyone has any idea how to handle this, I would be very grateful. I would even accept Mojave using software encoding for H264 if I could keep this amazing speeds on HEVC! BTW: Without IGPU on iMacPro1,1 SMBIOS no problem with DRM or iTunes, no need for Whatevergreen or Shiki. That is a bonus Ellesmere.kext.zip
  11. No, I don't use WhateverGreen, as I've written in the guide I've patched my DSDT for graphics. Sometimes I use Shiki to enable iTunes if I wish to. WEG in its new form does not enable DRM playback and should be avoided, maybe it gets fixed in the future. If you are planning to use FinalCut you should avoid using WEG anyway, it is not so complicated to add corresponding patches to your DSDT.
  12. 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
  13. Of course you're right! I've done all this fine tuning dozens of times for years now, but this time was a bit different, because I literally changed nothing and a software update just did the job. Usually it gets worse when Apple releases new stuff
  14. I meant without any active dsdt patching, the usual GFX0-IGPU hot patches are of course in place. But it is just awesome, that whole thing drove me crazy but it seems Apple added some Coffee Lake "compatibilities" to 10.13.6. So great! On the other hand: I wasted hours for nothing...
×