Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

h9826790

macrumors P6
Original poster
Apr 3, 2014
16,656
8,587
Hong Kong
This might help.
Apple released a special edition OS, Mojave 10.14.4 18E2034. It aims to support non-iGPU and non-VEGA iMac19,x with hardware acceleration. As a hackintosher, I managed to install it on my NUC8i7BEH (i7-8559U) with an RX580 eGPU hooked. I used a headless ig-platform-id which iGPU mental was disabled. FYI, you must change the SMBIOS to iMac19,2 in your EFI. Rendering a Brucex 5K took me round 22 seconds btw.

This should give us some hints. At least now we know that we can compare 18E2034 and 18E226 to check what's the different.

AFAIK, Dosdude will have a look of this matter, hopefully he can give us some good news later.

Anyway, if you follow the exact procedure to run BruceX. You will output the rendered video as ProRes, not H264 / HEVC. Therefore, it won't touch the GPU's video engine.

A cMP can finish BruceX in 15s with RX580. The problem is if we export H264 / HEVC, the process will become very slow due to unable to utilise the GPU video engine.

Anyway, why 19,2 has no iGPU? I think they use normal Intel Core series CPU, which has iGPU, aren't they?
 
Last edited:

LightBulbFun

macrumors 68030
Nov 17, 2013
2,900
3,195
London UK
aye AFAIK they do

they use a headless configuration

which is to say, the iGPU is still enabled and used its just not exposed as a graphics device to the user

however the iGPU gets used for quick-sync etc
 

Earl Urley

macrumors 6502a
Nov 10, 2014
793
438
So the third beta 10.14.5 build. 18F118d is available. Any status change on HEVC acceleration?
 

Earl Urley

macrumors 6502a
Nov 10, 2014
793
438
Think you might need the script to download it. I believe tsialex already has downloaded it.
 

sarkrui

macrumors newbie
Jan 22, 2018
14
11
Anyway, why 19,2 has no iGPU? I think they use normal Intel Core series CPU, which has iGPU, aren't they?
The 27' inch iMac 2019 uses i9-9900KF/i5-9600KF CPU, which does not have iGPU. It's believed the 18E2034 Mojave 10.14.4 is designed for this series iMacs, and thus SMBIOS iMac19,1 and iMac192 are worth trying. With iMac19,1 SMBIOS, I did not find HEVC encoding/decoding property in IOREG though, I did see AMD's working when I was playing/exporting H265 footages.
lRWhv0b.jpg

Source: https://www.macobserver.com/analysis/intel-cpus-in-apples-2019-imacs-chart/

Script to download Crazybirdy Mojave by Crazybirdy
https://www.dropbox.com/s/i27tkt7o0t4sb2l/installScript_1014fullapp.zip
 
  • Like
Reactions: Synchro3

LightBulbFun

macrumors 68030
Nov 17, 2013
2,900
3,195
London UK
The 27' inch iMac 2019 uses i9-9900KF/i5-9600KF CPU, which does not have iGPU. It's believed the 18E2034 Mojave 10.14.4 is designed for this series iMacs, and thus SMBIOS iMac19,1 and iMac192 are worth trying. With iMac19,1 SMBIOS, I did not find HEVC encoding/decoding property in IOREG though, I did see AMD's working when I was playing/exporting H265 footages.
lRWhv0b.jpg

Source: https://www.macobserver.com/analysis/intel-cpus-in-apples-2019-imacs-chart/

Script to download Crazybirdy Mojave by Crazybirdy
https://www.dropbox.com/s/i27tkt7o0t4sb2l/installScript_1014fullapp.zip

I dont think that source for CPU info is very acurate

looking at actual benchmarks which report back the CPU type, none of the iMac use the "F" suffix iGPUless CPUs

they all use normal intel CPUs which have iGPUs
 
  • Like
Reactions: h9826790

sarkrui

macrumors newbie
Jan 22, 2018
14
11
I dont think that source for CPU info is very acurate

looking at actual benchmarks which report back the CPU type, none of the iMac use the "F" suffix iGPUless CPUs

they all use normal intel CPUs which have iGPUs
Yeah, you are correct. I did not see any real benchmark with iGPUless iMac from geekbench. I am also doubting the reliability of that information. It makes no sense to not keep the CPUs consistent on iMacs. But it's also nonsense to have two different versions of 10.14.4.

UPDATE
Linus just released a new reviewing video about the new iMac. It is confirmed that i9-9900KF was configured on the ultimate iMac2019 (aimed to avoid the thermal issue)!
cr60j1T.png

Source:
 
Last edited:

LightBulbFun

macrumors 68030
Nov 17, 2013
2,900
3,195
London UK
*sigh*

if it was a KF CPU it would say so right in the CPUID string which would show up in geekbench

as you can see here in this CPU Z validation of a 9900KF CPU http://valid.x86.fr/nzymci it says 9900KF right in the CPUID string, which the iMacs CPU does not say

linus is not someone id go to for accurate information

(PS for what its worth, retail anyway F and non F SKUs are priced the same)
 

sarkrui

macrumors newbie
Jan 22, 2018
14
11
I found a guy managed to install 10.14.4 18E2034 on his i5-9400F build with full HW acceleration using iMac 19,2 SMBIOS (H.264, HEVC). See http://bbs.pcbeta.com/viewthread-1813658-1-10.html
I also found there is no entry for iMac19,1 and iMac19,2's board-ids in the AppleVGA.framework (under /System/Library/PrivateFrameworks/AppleGVA.framework) in 10.14.4 18E226 installer, but did find in the 18E2034 one. It might be interesting to inject the same property from iMac191/192 for Mac5,1 (board-id: Mac-F221BEC8).

Code:
<key>18E226</key>
<key>iMac18,3</key>
<key>Mac-BE088AF8C5EB4FA2</key>
    <dict>
        <key>facetimeDecode</key>
        <true/>
        <key>forceOfflineRenderer</key>
        <true/>
        <key>hwe</key>
        <true/>
        <key>hweBGRA</key>
        <true/>
        <key>ke1</key>
        <true/>
        <key>pp</key>
        <integer>1</integer>
    </dict>



iMac19,1 iMac19,2 N/A

<key>18E2034</key>
<key>iMac18,3</key>
<key>Mac-BE088AF8C5EB4FA2</key>
    <dict>
        <key>facetimeDecode</key>
        <true/>
        <key>forceOfflineRenderer</key>
        <true/>
        <key>hwe</key>
        <true/>
        <key>hweBGRA</key>
        <true/>
        <key>ke1</key>
        <true/>
        <key>pp</key>
        <integer>1</integer>
    </dict>

<key>iMac19,1</key>
<key>Mac-AA95B1DDAB278B95</key>
        <dict>
            <key>facetimeDecode</key>
            <true/>
            <key>forceOfflineRenderer</key>
            <true/>
            <key>hwe</key>
            <true/>
            <key>hweBGRA</key>
            <true/>
            <key>ke1</key>
            <true/>
            <key>pp</key>
            <integer>1</integer>
        </dict>

<key>iMac19,2</key>
<key>Mac-63001698E7A34814</key>
    <dict>
        <key>facetimeDecode</key>
        <true/>
        <key>forceOfflineRenderer</key>
        <true/>
        <key>hwe</key>
        <true/>
        <key>hweBGRA</key>
        <true/>
        <key>ke1</key>
        <true/>
        <key>pp</key>
        <integer>1</integer>
    </dict>

iMacPro1,1
    <key>Mac-7BA5B2D9E42DDD94</key>
    <dict>
        <key>allowFrameReordering</key>
        <false/>
        <key>hwe</key>
        <true/>
        <key>hwe420</key>
        <true/>
        <key>interlacedOff</key>
        <true/>
        <key>ke1</key>
        <true/>
    </dict>
 
  • Like
Reactions: octoviaa

h9826790

macrumors P6
Original poster
Apr 3, 2014
16,656
8,587
Hong Kong
I found a guy managed to install 10.14.4 18E2034 on his i5-9400F build with full HW acceleration using iMac 19,2 SMBIOS (H.264, HEVC). See http://bbs.pcbeta.com/viewthread-1813658-1-10.html
I also found there is no entry for iMac19,1 and iMac19,2's board-ids in the AppleVGA.framework (under /System/Library/PrivateFrameworks/AppleGVA.framework) in 10.14.4 18E226 installer, but did find in the 18E2034 one. It might be interesting to inject the same property from iMac191/192 for Mac5,1 (board-id: Mac-F221BEC8).

Code:
<key>18E226</key>
<key>iMac18,3</key>
<key>Mac-BE088AF8C5EB4FA2</key>
    <dict>
        <key>facetimeDecode</key>
        <true/>
        <key>forceOfflineRenderer</key>
        <true/>
        <key>hwe</key>
        <true/>
        <key>hweBGRA</key>
        <true/>
        <key>ke1</key>
        <true/>
        <key>pp</key>
        <integer>1</integer>
    </dict>



iMac19,1 iMac19,2 N/A

<key>18E2034</key>
<key>iMac18,3</key>
<key>Mac-BE088AF8C5EB4FA2</key>
    <dict>
        <key>facetimeDecode</key>
        <true/>
        <key>forceOfflineRenderer</key>
        <true/>
        <key>hwe</key>
        <true/>
        <key>hweBGRA</key>
        <true/>
        <key>ke1</key>
        <true/>
        <key>pp</key>
        <integer>1</integer>
    </dict>

<key>iMac19,1</key>
<key>Mac-AA95B1DDAB278B95</key>
        <dict>
            <key>facetimeDecode</key>
            <true/>
            <key>forceOfflineRenderer</key>
            <true/>
            <key>hwe</key>
            <true/>
            <key>hweBGRA</key>
            <true/>
            <key>ke1</key>
            <true/>
            <key>pp</key>
            <integer>1</integer>
        </dict>

<key>iMac19,2</key>
<key>Mac-63001698E7A34814</key>
    <dict>
        <key>facetimeDecode</key>
        <true/>
        <key>forceOfflineRenderer</key>
        <true/>
        <key>hwe</key>
        <true/>
        <key>hweBGRA</key>
        <true/>
        <key>ke1</key>
        <true/>
        <key>pp</key>
        <integer>1</integer>
    </dict>

iMacPro1,1
    <key>Mac-7BA5B2D9E42DDD94</key>
    <dict>
        <key>allowFrameReordering</key>
        <false/>
        <key>hwe</key>
        <true/>
        <key>hwe420</key>
        <true/>
        <key>interlacedOff</key>
        <true/>
        <key>ke1</key>
        <true/>
    </dict>

I read your link (I can understand Chinese natively, so, no google translation etc involved).

The OP of that post said he has no idea what HW acceleration is, and he is just a normal user, he doesn't need that.

So, there is still no prove that HW acceleration is working flawlessly with that special build 10.14.4 (or with iMac 19,2 ident).

In fact, another member there replied that config will have "colour block issue" when exporting video. Not sure if that's due to the buggy HW acceleration support, or other Hackintosh issue.

However, your finding about the board-id in AppleGVA framework may really means something.
 
  • Like
Reactions: octoviaa

startergo

macrumors 603
Sep 20, 2018
5,020
2,282
I read your link (I can understand Chinese natively, so, no google translation etc involved).

The OP of that post said he has no idea what HW acceleration is, and he is just a normal user, he doesn't need that.

So, there is still no prove that HW acceleration is working flawlessly with that special build 10.14.4 (or with iMac 19,2 ident).

In fact, another member there replied that config will have "colour block issue" when exporting video. Not sure if that's due to the buggy HW acceleration support, or other Hackintosh issue.

However, your finding about the board-id in AppleGVA framework may really means something.
This only sets HWE I don't see HWD. but it is a good finding.
 

startergo

macrumors 603
Sep 20, 2018
5,020
2,282
This is still good news. Did you confirm encoding by exporting with QuickTime?
No I did not test it I just saw the key in the framework. I believe that kext needs to be edited by adding MacPro5,1 properties then installed back with something like this
 

sarkrui

macrumors newbie
Jan 22, 2018
14
11
Since I found the guy from pcbeta.com managed to have full HW acceleration on his i5-9400F build with 18E2034 Mojave using iMac19,2 SMBIOS (source). I wanted to find out if it was also applicable for my Xeon build.
Fths4PI.jpg

(As you can see from the snapshot, he has full HW acceleration, even though he is not aware of it. As he said, "I have no idea what HW acceleration is." in his post.)

My specs,
CPU: Xeon E3-1231 v3
GPU: RX580 Nitro+ 8G

Case 1:10.14.4 18E2034 + MacPro5,1/iMac19,1/iMac19,2
--> neither supports H264 nor HEVC
B6LonrD.png

Case 2:18E2034 + iMacPro1,1 + AppleGVA.framework/AppleGVACore.framework (10.14.5 beta 5)+ AMDxxxxxx.kexts from 10.14.5 beta4
--> Both H264 and HEVC HW acceleration are fully supported. FYI, I was able to export render BruceX 5K in FCPX in the format of HEVC 8bit, while in 10bits, FCPX didn't utilize GPU (I assume a real Mac can also ONLY support SW HEVC 10bit encoding).
bT3knFT.png


Case 3: the same as Case 2, (frameworks and KEXTs) but using MacPro5,1
Case 3_1: the same as above, but inserting MacPro5,1 key with the same property on iMacPro1,1 in AppleGVA.framework and AppleGVACore.framework
Code:
        <key>MacPro5,1</key>
        <dict>
            <key>allowFrameReordering</key>
            <false/>
            <key>hwe</key>
            <true/>
            <key>hwe420</key>
            <true/>
            <key>interlacedOff</key>
            <true/>
            <key>ke1</key>
            <true/>
        </dict>

--> In both cases, only HEVC HW acceleration is fully supported.
5L1IopY.png


Case 4: Using MacPro5,1 (cMP) SMBIOS with iMacPro1,1 board-id: Mac-7BA5B2D9E42DDD94
--> Both H264 and HEVC HW acceleration are fully supported. Although this is easily doable on Hackintosh with a Clover flag, unfortunately, it might be not feasible on cMPs.
6oSa4hy.png

FYI, I have no issue in exporting HEVC from Compressor.
mvFhJvZ.png
 
Last edited:

h9826790

macrumors P6
Original poster
Apr 3, 2014
16,656
8,587
Hong Kong
Since I found the guy from pcbeta.com managed to have full HW acceleration on his i5-9400F build with 18E2034 Mojave using iMac19,2 SMBIOS (source). I wanted to find out if it was also applicable for my Xeon build.
Fths4PI.jpg

(As you can see from the snapshot, he has full HW acceleration, even though he is not aware of it. As he said, "I have no idea what HW acceleration is." in his post.)

My specs,
CPU: Xeon E3-1231 v3
GPU: RX580 Nitro+ 8G

Case 1:10.14.4 18E2034 + MacPro5,1/iMac19,1/iMac19,2
--> neither supports H264 nor HEVC
B6LonrD.png

Case 2:18E2034 + iMacPro1,1 + AppleGVA.framework/AppleGVACore.framework (10.14.5 beta 5)+ AMDxxxxxx.kexts from 10.14.5 beta4
--> Both H264 and HEVC HW acceleration are fully supported. FYI, I was able to export render BruceX 5K in FCPX in the format of HEVC 8bit, while in 10bits, FCPX didn't utilize GPU (I assume a real Mac can also ONLY support SW HEVC 10bit encoding).
bT3knFT.png


Case 3: the same as Case 2, (frameworks and KEXTs) but using MacPro5,1
Case 3_1: the same as above, but inserting MacPro5,1 key with the same property on iMacPro1,1 in AppleGVA.framework and AppleGVACore.framework
Code:
        <key>MacPro5,1</key>
        <dict>
            <key>allowFrameReordering</key>
            <false/>
            <key>hwe</key>
            <true/>
            <key>hwe420</key>
            <true/>
            <key>interlacedOff</key>
            <true/>
            <key>ke1</key>
            <true/>
        </dict>

--> In both cases, only HEVC HW acceleration is fully supported.
5L1IopY.png


Case 4: Using MacPro5,1 (cMP) SMBIOS, replacing iMacPro1,1 board-id: Mac-7BA5B2D9E42DDD94
--> Both H264 and HEVC HW acceleration are fully supported. Although this is easily doable on Hackintosh with a Clover flag, unfortunately, it might be not feasible on cMPs.
6oSa4hy.png

FYI, I have no issue in exporting HEVC from Compressor.
mvFhJvZ.png

Thanks for all the tests. May I know where you get that screen capture from? I read through your source link (just 2 pages), can't find that screen capture about hardware accel is working. (UPDATE: I just found that I have no permission to see the attachment because I am not a registered member, most likely that's why I can't see it).

And that RX580 on the screen capture may have nothing to do about the hardware accel. Of course, I hope that I am wrong. However, that screen capture means little at this moment.

e.g. On my Hackintosh, the hardware accel actually from the UHD630, but on that page, it shows 1080Ti as the graphic card. And there is no SMBIOS / board-id in the screen capture.
Hardware Acc Engine.png


Of course, in your case, must come from the RX580, but you are using the iMac Pro info to achieve that, not iMac.

Anyway, it's good to know more about how the ident affect hardware accel. If I understand correctly, your case 4 proved that only board-id matters. As long as the board-id is Mac-7BA5B2D9E42DDD94, no other modification is required to get full hardware accel from the RX580. This is a very useful finding. But also sad you proved that all functions are already there inside the macOS, but just Apple artificially block cMP users to use it.

Also, may be we can start with your case 3_1. If we can make HEVC hardware accel work, still better than nothing. No H264 encoding still a very big deal on cMP, but lack of HEVC decode can be more trouble. H264 encoding eventually will be done, just a matter of time. But cannot play HEVC in real time means the video is not playable, and no alternative solution.

Not sure if OpenCore will do less (hopefully no) damage to the cMP's firmware. If that works, then we may still have a chance to ident our cMP at iMac Pro 1,1 to utilise hardware accel (without risking to brick the logic board).
 
Last edited:
  • Like
Reactions: crjackson2134

sarkrui

macrumors newbie
Jan 22, 2018
14
11
As long as the board-id is Mac-7BA5B2D9E42DDD94, no other modification is required to get full hardware accel from the RX580.
Sorry, maybe I didn't explain the lase case explicitly. In case 4, I also was also using the AMDxxxx.KEXTs drivers extracted from 10.14.5 beta4. In short, with replaced kexts and iMacPro1,1's board-id, I got full HW acceleration; with kexts and no board-id, I only had HEVC HW acceleration. I've also attached the kexts I used. Please feel free to try them out. https://drive.google.com/file/d/1VD5LgBTHIlfGObPwDUF15_qZxpO93B30
Ye8clTB.jpg

(Remember to back up your original kexts and do not forget to rebuild the cache. Good luck!)
 

startergo

macrumors 603
Sep 20, 2018
5,020
2,282
This is excellent discovery! Now if Apple adds EFI bootscreen as hinted in the new firmware, the old grandpa will be ready to fight again :).
 
  • Like
Reactions: TheStork

h9826790

macrumors P6
Original poster
Apr 3, 2014
16,656
8,587
Hong Kong
Sorry, maybe I didn't explain the lase case explicitly. In case 4, I also was also using the AMDxxxx.KEXTs drivers extracted from 10.14.5 beta4. In short, with replaced kexts and iMacPro1,1's board-id, I got full HW acceleration; with kexts and no board-id, I only had HEVC HW acceleration. I've also attached the kexts I used. Please feel free to try them out. https://drive.google.com/file/d/1VD5LgBTHIlfGObPwDUF15_qZxpO93B30
Ye8clTB.jpg

(Remember to back up your original kexts and do not forget to rebuild the cache. Good luck!)

I am wondering what will happen if we install Lilu and WhatEverGreen, then set
Code:
sudo nvram boot-args="shikigva=60 shiki-id=Mac-7BA5B2D9E42DDD94"
On Hackintosh, this boot argument will allow GVA to use iMacPro 1,1 SMBIOS. I wonder if it can do the same on cMP. Since we set this via terminal, so, if anything goes wrong, we should able to clear it simply via NVRAM reset.
[doublepost=1556748809][/doublepost]Anyway, I just installed the latest 10.14.5 DP. No hardware accel as expected (apart from that Airplay option which is not really working).

Then replace the iMac Pro section by cMP 5,1 in AppleGVA.framework also has no effect.
 
Last edited:

sarkrui

macrumors newbie
Jan 22, 2018
14
11
sudo nvram boot-args="shikigva=60 shiki-id=Mac-7BA5B2D9E42DDD94"
I think it's a brilliant idea to try Lilu and WhateverGreen, but I don't think you will need the shikigva=60 (not really sure what '60' means here, it's for nVidia GFX, right?). Besides the board-id, I guess you might need 10.14.5 beta 2 (or up) kexts. I suggest you run the beta Mojave on a separate volume.
 

h9826790

macrumors P6
Original poster
Apr 3, 2014
16,656
8,587
Hong Kong
I think it's a brilliant idea to try Lilu and WhateverGreen, but I don't think you will need the shikigva=60 (not really sure what '60' means here, it's for nVidia GFX, right?). Besides the board-id, I guess you might need 10.14.5 beta 2 (or up) kexts. I suggest you run the beta Mojave on a separate volume.

I can't find the documents that explain those shikigva options. But it seems this parameter can affect hardware accel and iTunes play back ability (DRM content). At this moment, I only know some guys need shikigva=1, some need shikigva=60, some need shikigva=61 to get everything working properly.

Thanks for the reminder. I do all the test on my spare HDD. I have no spare SSD now. The test drive is very slow as boot drive, but it's completely separated from my primary and backup boot drive.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.