macOS 10.14 Mojave on Unsupported Macs Thread

[StellarVixen]

Sorry for maybe sounding dumb, but I would like to know what makes the certain graphics Metal-compatible, and others not?

Why is HD3000 not compatible with Metal, while HD4000 is?

Is it just that the Apple has purely decided to draw the line somewhere, or are there real, technical reason for why some cards are not supported?

 

[jackluke]

I tried your method on my 2011 (still on HS), works great and it seems like the screen flickering it did before has stopped !

I've been looking into increasing the vram on my mbp 15 2010. On a fresh install of snow leopard from the original discs the MacBook came with, I get 288 mb vram for the intel hd no matter what ram combination I put in. I get the same on Mojave and high Sierra.
Apples specs is 256mb. So I conclude that its set in the efi, and I will leave it at that.

Well I'm glad it worked and fixed flickering, maybe that is the side effect of the side effect VRAM patching.

I don't have any Mac with an "AppleIntelHDGraphics" 1st gen, so can't really test, but based on vista980622 's thread I think that 288 MB is not so simple to be represented finding a possible value in hex editor inside the AppleIntelHDGraphicsFB, considering that inside AppleIntelSNBGraphicsFB the hex byte "18" is 384 MB , "20" is 512 MB, so 256 MB is represented by hex byte "10" then remains spare 32 MB that is 10/8 but I am not sure in a hex value translation.

So 288 MB VRAM is not simple to locate in the ending part of an offset but it seems a fixed size so I guess you're totally right it was been set in the EFI, and I don't like to play much with EFI in general.

Anyway I see you have 16 GB RAM and you're on HighSierra 10.13.3, so if you are brave give a try increasing VRAM up to 2048 MB, but this time without using the Terminal commands use these already patched: IntelHD3000 VRAM Mojave patch

They are from 10.13.6 but should work both on HighSierra and Mojave, since dosdude1 has fixed IntelHD3000 QE/CI using HS kexts in Mojave.

For safety take a backup of your stock IntelHD3000 High Sierra 10.13.3 kexts.

edit:
Or if you still prefer Terminal way, from your High Sierra 10.13.3 Terminal repeat all the previous steps with these little modifications:

from stock 1536 MB to 2048 MB VRAM:

sudo perl -pi -e 's|\xC7\x45\xD0\x00\x00\x00\x60|\xC7\x45\xD0\x00\x00\x00\x80|g' AppleIntelSNBGraphicsFB

while inside the:
/System/Library/Extensions/AppleIntelHD3000Graphics.kext/Contents/Info.plist

Adding after these strings, this part:

<key>VRAMMethod</key>
<integer>0</integer>
<key>VRAMOverride</key>
<integer>0</integer>
<key>VRAMSize</key>
<integer>2048</integer>

 

[Badruzeus]

I have a feeling someone at insanelymac or one of these other Hackintosh forums might be able to figure it out...if they have an incentive...

No idea with Radeon 6xxx series under Mojave, pretty old HD4830 is woking fine though. Because lack of dMux or Metal or else, IDK (Apple dropped it's support since 10.14, is true). But, MBP8,x I think has Intel HD3000 with Graphics acceleration enabled, doesn't it? So.., way better than nothing work at all #LoL..

Spoiler

I ever imagined that @rodsmith would add more features inside his #rEFInd bootloader on this case (for loading 3rd party injector kexts w/o touching our vanilla system, FakeID, Kext & Kernel to Patch, etc.), I mean for unsupported macs with newer system, but later on.. I see no reason why he should to (with potentially damaging our mac firmware?). Which device-id need to be Faked on real macs, or do they need missing ACPI Tables patching? I don't think so.

Hackintosh+Clover >< Real Macs uhmb, yeah.. I just read prev. posts above. Similar problem on similar devices, but on different cases with also different methods; not sure why make these two become comparable, #IMHO.

[doublepost=1534179938][/doublepost]

I don't have any Mac with an "AppleIntelHDGraphics" 1st gen, so can't really test, but based on vista980622 's thread I think that 288 MB is not so simple to be represented finding a possible value in hex editor inside the AppleIntelHDGraphicsFB, considering that inside AppleIntelSNBGraphicsFB the hex byte "18" is 384 MB , "20" is 512 MB, so 256 MB is represented by hex byte "10" then remains spare 32 MB that is 10/8 but I am not sure in a hex value translation.

So 288 MB VRAM is not simple to locate in the ending part of an offset but it seems a fixed size so I guess you're totally right it was been set in the EFI, and I don't like to play much with EFI in general.

Dynamic VRam allocation is not implemented on 1st Gen. IntelHDGraphics (Arrandale / GMA 4500MHD), #afaik.. compared to IntelHD3000 or later.. which will be increased, once upgrading RAM module. So, it' s graphics hardware limitation (on mac).

 

[TimothyR734]

DP7 has just been released showtime

 

[Badruzeus]

Aw, but this one just released. Good luck!
macOS Mojave 10.14 beta 7 (18A365a)

 

[tsialex]

DP7 has just been released showtime

Build 18A365a

 

[Badruzeus]

DP7 has just been released showtime

You're one step faster #LoL Beating me..

 

[TimothyR734]

downloading on my iMac 9,1

 

[Appleak]

b7 3.27 gb downloading ... now

 

[Badruzeus]

 

[arqueox]

Still no update again...
[doublepost=1534182582][/doublepost]

DP7 has just been released showtime

Do I need to be on apple developer program and need to pay to have access to the updates? Or there is another way to do it?

 

[pkouame]

Still no update again...
[doublepost=1534182582][/doublepost]
Do I need to be on apple developer program and need to pay to have access to the updates? Or there is another way to do it?

If you are not enrolled, try downloading the proper beta utility within Mojave again. It should kick off a system update -> download of (probably) full installer. Sometimes takes a few tries running the beta utility app. There are ways of enrolling manually (search thread) also. Or use the patcher.
[doublepost=1534183475][/doublepost]

downloading on my iMac 9,1

And the race is on!
[doublepost=1534183735][/doublepost]

Sorry for maybe sounding dumb, but I would like to know what makes the certain graphics Metal-compatible, and others not?

Why is HD3000 not compatible with Metal, while HD4000 is?

Is it just that the Apple has purely decided to draw the line somewhere, or are there real, technical reason for why some cards are not supported?

No dumb questions here...Metal graphics cards support special instructions that allow the metal framework to "speak" directly to the GPU using special command buffers and queues. By being so low-level and "bare metal" it bypasses some overhead to super charge the graphics pipeline. Great for graphics and compute (think ML AI) intensive tasks. Also makes it a little rough to program. Its competing with directX and Vulkan. Actually makes quite a difference...

 

[Larsvonhier]

With a similar MacBook to me the new dosdude1 NS patch has worked, I consider a patched Night Shift a right for everyone, so please try mine already patched for your machine following these steps:

- Open Finder then GO "go to folder" or use keyboard shortcut CMD+Shift+G and copy-paste:

/System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/A/

- Replace the one inside this subfolder with the already patched CoreBrightness I have attached
- After done restart your MacBook and check if Night Shift is there

This is a pre-patched file using the dosdude1 Night Shift cbpatcher valid for Mojave DP4/PB3 and DP5/PB4 and maybe next version

edit:
This Patched Night Shift file has been deeply tested and results still perfectly working even with Mojave beta 6 build 18A353d

But when Mojave beta 7 will come out, please wait before using it again.

I just found out that you can get your system up & running again whenever something turns sour with CoreBrightness and you don't have access to the backup framework files: Just boot into single user mode and mount the filesystem (r/w) then delete CoreBrightness in folder .../Versions/A/
After reboot, some functions (trackpad, brightness etc.) will be missing, but you can then fire up Safari and get a correctly patched or original CoreBrightness again!
(I stumbled around for a while after encryption deadlocked system before I found this out, so may be helpful in some extreme cases)

 

[TimothyR734]

update successful for those who use night shift don't forget to apply the night shift patch from the patch updater in your utilities folder

 

[StellarVixen]

update successful for those who use night shift don't forget to apply the night shift patch from the patch updater in your utilities folder

That is beautiful, I am so glad it works for you.

What is that clock app called, btw?

 

[pkouame]

update successful for those who use night shift don't forget to apply the night shift patch from the patch updater in your utilities folder

Fastest gun in the west...congrats

 

[arqueox]

update successful for those who use night shift don't forget to apply the night shift patch from the patch updater in your utilities folder

Friend, still problems on light mode?

 

[TimothyR734]

Friend, still problems on light mode?

Light mode
[doublepost=1534186181][/doublepost]

Fastest gun in the west...congrats

Thank you

 

[arqueox]

Light mode
[doublepost=1534186181][/doublepost]
Thank you

Yep still the same... I don't think apple will do anything to change that.

 

[TimothyR734]

Yep still the same... I don't think apple will do anything to change that.

I prefer dark mode anyways but hope they will fix light mode

 

[arqueox]

I prefer dark mode anyways but hope they will fix light mode

Me too. But probably somebody already said something about but on Macs with fully support by apple, they have problems with light mode too?

 

[thegurgz]

Light mode
[doublepost=1534186181][/doublepost]
Thank you

That’s one hell of a dock bar you got there!

 

[pkouame]

Yep still the same... I don't think apple will do anything to change that.

Yup. They've just dropped FaceTime Group Chat in Mojave and iOS (Cupertino has some real issues) so our Light mode glitches are the least of their concerns.

 

[visberry]

Hit me up if anyone needs a core backup for 13" mid 2010 MacBook Pro.
[doublepost=1534187710][/doublepost]

Yup. They've just dropped FaceTime Group Chat in Mojave and iOS (Cupertino has some real issues) so our Light mode glitches are the least of their concerns.

Shi*, let's hope it's not another messages in iCloud

 

[Olivia88]

Well I'm glad it worked and fixed flickering, maybe that is the side effect of the side effect VRAM patching.

I don't have any Mac with an "AppleIntelHDGraphics" 1st gen, so can't really test, but based on vista980622 's thread I think that 288 MB is not so simple to be represented finding a possible value in hex editor inside the AppleIntelHDGraphicsFB, considering that inside AppleIntelSNBGraphicsFB the hex byte "18" is 384 MB , "20" is 512 MB, so 256 MB is represented by hex byte "10" then remains spare 32 MB that is 10/8 but I am not sure in a hex value translation.

So 288 MB VRAM is not simple to locate in the ending part of an offset but it seems a fixed size so I guess you're totally right it was been set in the EFI, and I don't like to play much with EFI in general.

Anyway I see you have 16 GB RAM and you're on HighSierra 10.13.3, so if you are brave give a try increasing VRAM up to 2048 MB, but this time without using the Terminal commands use these already patched: IntelHD3000 VRAM Mojave patch

They are from 10.13.6 but should work both on HighSierra and Mojave, since dosdude1 has fixed IntelHD3000 QE/CI using HS kexts in Mojave.

For safety take a backup of your stock IntelHD3000 High Sierra 10.13.3 kexts.

edit:
Or if you still prefer Terminal way, from your High Sierra 10.13.3 Terminal repeat all the previous steps with these little modifications:

from stock 1536 MB to 2048 MB VRAM:

sudo perl -pi -e 's|\xC7\x45\xD0\x00\x00\x00\x60|\xC7\x45\xD0\x00\x00\x00\x80|g' AppleIntelSNBGraphicsFB

while inside the:
/System/Library/Extensions/AppleIntelHD3000Graphics.kext/Contents/Info.plist

Adding after these strings, this part:

<key>VRAMMethod</key>
<integer>0</integer>
<key>VRAMOverride</key>
<integer>0</integer>
<key>VRAMSize</key>
<integer>2048</integer>

Thanks ! I tested the 2gb patch you made, works great too except SIP need to stay disabled. I assume that's because the kexts are from 13.6 and I have 13.3 installed. Does not matter anyway.