macOS 10.14 Mojave on Unsupported Macs Thread

[jackluke]

@pkouame

I had News+ on .5 beta 1, however News.app appears to work correctly now.
Yes the workflow is correct, except that in manual patching I don't replace or add any AMD/ATI kext since I don't have that GPU, and neither a couple of IntelHD kext as FramebufferAzul and Capri in my case are not needed.

Only note is this time on .5 beta 3 , I needed to replace the AppleMCCSControl.kext from .4 , because it resolves me a missing symbol. But even without replacing it, graphics acceleration is working anyway.

 

[pkouame]

@pkouame

I had News+ on .5 beta 1, however News.app appears to work correctly now.
Yes the workflow is correct, except that in manual patching I don't replace or add any AMD/ATI kext since I don't have that GPU, and neither a couple of IntelHD kext as FramebufferAzul and Capri in my case are not needed.

Only note is this time on .5 beta 3 , I needed to replace the AppleMCCSControl.kext from .4 , because it resolves me a missing symbol. But even without replacing it, graphics acceleration is working anyway.

Cool. I'll try the exact same video post-install script I just posted. I may comment out the AMD/ATI stuff too. If this works it means the end of retro-patching hell and very good news (no pun intended) for 10.15...
[doublepost=1555979871][/doublepost]

If you meant that, yes, since .5 beta2 I don't have more News+ pane, but if I do search inside News.app it lets me open every newspaper, even those without a favicon.

Stock IOGraphics * kext don't work, I mean they don't bring acceleration even replacing the "three frameworks". They worked only in framebuffer mode. So minimum of them to use are .4 to bring legacy Acceleration.

.5 beta 3 OpenGL worked in framebuffer mode, but not in acceleration mode. So .3 OpenGL is still required.

Ok, I re-read your .5b3 steps again and it seems like non-accelerated/framebuffer .5b3 is still the only thing achievable using your technique. Sorry but your thread confuses me a little .... I'm not sure a mix of .4 IO kexts with .3 OpenGL suite gets us any further than we already are. May even complicate things.

I think I'll stick to simple. Still great work giving us all an early taste of .5b3.... Thanks.

 

[webg3]

@pkouame

Try:

- Update OTA to 10.14.5b3 and reboot
- CMD-S copy CoreDisplay.framework (0.3 or 0.4) to /System/Library/Frameworks
- Reboot USB Installer from Patch Dosdude1 1.30 (10.14.3 or 10.14.4); Pos-Install patch Legacy Video;
- Reboot, working

Re-apply Patch Update Mojave (Legacy Video and others);
Reboot;

This OK.
[doublepost=1555982743][/doublepost]

[doublepost=1555982852][/doublepost]Core Display

 

[pkouame]

@pkouame
Try:

- Update OTA to 10.14.5b3 and reboot
- CMD-S copy CoreDisplay.framework (0.3 or 0.4) to /System/Library/Frameworks
- Reboot USB Installer from Patch Dosdude1 1.30 (10.14.3 or 10.14.4); Pos-Install patch Legacy Video;
- Reboot, working

Re-apply Patch Update Mojave (Legacy Video and others);
Reboot;

This OK.
[doublepost=1555982743][/doublepost]View attachment 833397
[doublepost=1555982852][/doublepost]Core Display

Yes, I know that works Found anything new in .5b3?
[doublepost=1555987933][/doublepost]All -

MBP 5,3 (Dual GPU Nvidia 9600M GT + 9400M) APFS runs .5b3 just fine.

Upgrade path : OTA software update from .5b2 -> post-install + CoreDisplay.

The experience is similar to .5b2.

EDIT: OpenGL screensavers and Chess all work well. News is crashing as it did before.

 

[Syncretic]

I’m adding you to a group with a link. Try the google drive one below. Anyone else who wants a link, message me here or dm me and I’ll add you.

I would also appreciate a link to the full 10.14.3 installer. Thanks in advance.

 

[pkouame]

System: MBP5,2 17", SSD with APFS, APFS ROM patch applied.

System running well with 10.14.5b2.

Thanks to RogueB for the instructions, and worth repeating what he said: All credit, and thanks, to @dosdude1, @jackluke, @ASentientBot, @pkouame and many others (in no particular order) for their amazing work and perseverance!

To start, cloned stable 10.14.3 to an external SSD (with CCC). 9600M GT GPU selected all the time.
- installed 10.14.4 over this with dosdude's patcher 1.3.0, applied post-install patches, no extra patch updater patches proposed
- updated to 10.14.5b2 OTA, applied 1.3.0 post-install patches again (and rebuilt caches)
- in single-user mode moved .4 CoreDisplay.framework to /System/Library/Frameworks (before, /sbin/mount -uw /). Used the framework attached to post #14339
- booted fine. Rebuilt caches with sudo kextcache -system-caches; sudo kextcache -system-prelinked-kernel (wasn't sure if needed)

The SSD with 10.14.5b2 is now on SATA and being used as my standard system. Fingers still crossed...

Experience so far:
- stable running for a day using the 9600M GT GPU.
- then switched to 9400M, went well for several hours then a KP in Mail. Was difficult to switch back to 9600M GT because of frequent KPs, but eventually succeeded and running fine again with 9600M GT.
- started to use Safari at this point which had caused KPs in 10.14.4. Fine so far for a few hours, so this is better in 10.14.5b2.

After some running I'll retry everything with the .3 CoreDisplay.framework, to see how 9400M behaves then. Apart from having a stable-enough beta system the thrill of experimenting is also valuable.

Thanks again!View attachment 833340

Just to follow up on this. I've been running stable with .5b3 on both 9600M GT and 9400M gpus.

 

[avz]

I am wondering if I am the only one who is getting the "up to date" treatment? My Mac is enrolled in a beta program but still no sign of .5b3. Is there a way to reset/clear a software update?

Edit: Public Beta 3 has not been released yet.

 

[jackluke]

I am wondering if I am the only one who is getting the "up to date" treatment? My Mac is enrolled in a beta program but still no sign of .5b3. Is there a way to reset/clear a software update?

View attachment 833409

I guess if you are already on APFS, you should try Czo's suvmmfaker in the OP.
That patch allow to force retrieve updates on unsupported machines.

 

[avz]

I guess if you are already on APFS, you should try Czo's suvmmfaker in the OP.
That patch allow to force retrieve updates on unsupported machines.

Yep, APFS since day one, Czo's patch already installed(SUVMMFaker.dylib and com.apple.softwareupdated.plist in their places). I re-enrolled again but no luck.

 

[webg3]

Yesp I know that works Found anything new in .5b3?

We need a new patch to CoreDisplay.framework
[doublepost=1556009746][/doublepost]

I am wondering if I am the only one who is getting the "up to date" treatment? My Mac is enrolled in a beta program but still no sign of .5b3. Is there a way to reset/clear a software update?

View attachment 833409

Public Beta?

Update comes first to Developers Program Beta

 

[avz]

Public Beta?

Update comes first to Developers Program Beta

Yes, Public Beta. Cheers, I am new to the Beta program.
[doublepost=1556013476][/doublepost]

.5 beta 3 available, but cannot test now, I guess in three hours I can

edit:

.5 beta 3 IOUSB* worked OOB again.

I still have LegacyUSBInjector installed. Does that mean that .5 beta 2 IOUSB* not working for my Mac OOB? I am just trying to understand a connection. I did not applied LegacyUSBInjector patch after the .5 beta 2 update but it seems that the update did not break it.

 

[MrZupp]

System: MBP5,2 17", SSD with APFS, APFS ROM patch applied.

System running well with 10.14.5b2.

Thanks to RogueB for the instructions, and worth repeating what he said: All credit, and thanks, to @dosdude1, @jackluke, @ASentientBot, @pkouame and many others (in no particular order) for their amazing work and perseverance!

To start, cloned stable 10.14.3 to an external SSD (with CCC). 9600M GT GPU selected all the time.
- installed 10.14.4 over this with dosdude's patcher 1.3.0, applied post-install patches, no extra patch updater patches proposed
- updated to 10.14.5b2 OTA, applied 1.3.0 post-install patches again (and rebuilt caches)
- in single-user mode moved .4 CoreDisplay.framework to /System/Library/Frameworks (before, /sbin/mount -uw /). Used the framework attached to post #14339
- booted fine. Rebuilt caches with sudo kextcache -system-caches; sudo kextcache -system-prelinked-kernel (wasn't sure if needed)

The SSD with 10.14.5b2 is now on SATA and being used as my standard system. Fingers still crossed...

Experience so far:
- stable running for a day using the 9600M GT GPU.
- then switched to 9400M, went well for several hours then a KP in Mail. Was difficult to switch back to 9600M GT because of frequent KPs, but eventually succeeded and running fine again with 9600M GT.
- started to use Safari at this point which had caused KPs in 10.14.4. Fine so far for a few hours, so this is better in 10.14.5b2.

After some running I'll retry everything with the .3 CoreDisplay.framework, to see how 9400M behaves then. Apart from having a stable-enough beta system the thrill of experimenting is also valuable.

Thanks again!View attachment 833340

Did this on the exact same machine, but I moved the AppleMCCSControl.kext from @jackluke had some KPs that occur several minutes from boot, and I can't seem to switch between graphic cards, it always says that I need to log out, I logged out 10 times, but nothing, in the About My Mac section it still shows the 9400M and in system report it doesn't even show the 9600M.

Edit: Aaaand still no brigtness control...

 

[jackluke]

Did this on the exact same machine, but I moved the AppleMCCSControl.kext from @jackluke had some KPs that occur several minutes from boot, and I can't seem to switch between graphic cards, it always says that I need to log out, I logged out 10 times, but nothing, in the About My Mac section it still shows the 9400M and in system report it doesn't even show the 9600M.

Edit: Aaaand still no brigtness control...

For dualGPUs machine Nvidia 330 and IntelHD Arrandale, I use also AppleGraphicsControl.kext from .4 , anyway for a dualGPUs Nvidia Tesla the behavior is different I guess.

But this "MUX switching" needs more investigation from dosdude1 I guess, this is beyond my knowledge.

edit:
Anyway I find agree, when an accelerated system doesn't have the brightness control (and sleep function) fans are ramped with higher cpu temperatures, and also the dual switching doesn't respond correctly.

I my case I fixed using a .4 kext set IOGraphics * and AGC plugins, but I can't verify it on a dual Nvidia Tesla and moreover on an non-native APFS machine, I admit with a native APFS machine patching is a slight easier job.

 

[Yojx21]

Yes i am. I did it a lot of time with HS Patcher and never had this issue. :/

Today i have tryed with another image of Mojave and it made the same error. Anybody can help ?

What is strange is that it doesn't ask for root password before trying to mount the image...

 

[MrZupp]

For dualGPUs machine Nvidia 330 and IntelHD Arrandale, I use also AppleGraphicsControl.kext from .4 , anyway for a dualGPUs Nvidia Tesla the behavior is different I guess.

But this need more investigation from dosdude1 I guess, this is beyond my knowledge.

edit:
Anyway I find agree, when an accelerated system doesn't have the brightness control (and sleep function) fans are ramped with higher cpu temperatures, and also the dual switching doesn't respond correctly.

Yep, I tought that was a problem with my macbook, even changed the thermal paste a few hours ago, it's not as hot as it was before, but it is getting very close very fast. I even tried the gfxCardStatus, but where it should show the card I'm using it says currentcard and when I switch to discrete, it just does nothing, usually a KP after 20-30 seconds.

Edit: inside the macbook there were a few missing screws, but nothing was out of the ordinary, the flex cables were ok, there was no sign of liquid damage or scratches on the motherboard, but someone has opened it before (paid 130$ for this thing, so I wasn't expecting much...)

 

[jackluke]

Yep, I tought that was a problem with my macbook, even changed the thermal paste a few hours ago, it's not as hot as it was before, but it is getting very close very fast. I even tried the gfxCardStatus, but where it should show the card I'm using it says currentcard and when I switch to discrete, it just does nothing, usually a KP after 20-30 seconds.

These issues you described I am almost sure depend mostly from AppleGraphicsControl.kext (and its internal Plugins folder).
In my case dualGPUs I also had random KP but I know for my machine model they belong mainly to the Nvidia 330 , so with software patching I can use both the GPUs.

Probably to make "MUX switching" working again for gfxCardStatus could be needed also a replacement of AppleGraphicsPowerManagement.kext from .4
I'll do other tests.

 

[p8712]

So I upgraded my Macbook5,1 running 10.14.4 from 4gb to 8gb ram. It had been running perfectly, but now won't boot past the progress bar (HFS+ drive). Any ideas? I zapped the PRAM, to no effect. Even the mojave patcher USB stick will no longer boot. It boots to Snow Leopard just fine via USB and sees the new ram. Any ideas? Strange that just a ram upgrade would do this...

 

[flygbuss]

So I upgraded my Macbook5,1 running 10.14.4 from 4gb to 8gb ram. It had been running perfectly, but now won't boot past the progress bar (HFS+ drive). Any ideas? I zapped the PRAM, to no effect. Even the mojave patcher USB stick will no longer boot. It boots to Snow Leopard just fine via USB and sees the new ram. Any ideas? Strange that just a ram upgrade would do this...

Did you try to reseat the ram modules?

 

[p8712]

Did you try to reseat the ram modules?

Not yet. They are both recognized. Good quality ram, too.

 

[MrZupp]

These issues you described I am almost sure depend mostly from AppleGraphicsControl.kext (and its internal Plugins folder).
In my case dualGPUs I also had random KP but I know for my machine model they belong mainly to the Nvidia 330 , so with software patching I can use both the GPUs.

Probably to make "MUX switching" working again for gfxCardStatus could be needed also a replacement of AppleGraphicsPowerManagement.kext from .4
I'll do other tests.

Can you provide me the AppleGraphicsPowerManagement.kext from .4?

 

[Kevbasscat]

For anyone interested, I succeeded. iMac 9,1 flashed with APFS support. Here is how I did it.

1) Boot normally. No holding the power button.

* possible extra step here - see note if you are not successful otherwise.

2) The APFS patcher can launch on Lion or later. However, it contains a kext ... which apparently requires Sierra (10.12) or later. If you try earlier, the app opens. But flashing *Always* fails. I was trying on Yosemite and El Capitan. This is what tripped me up repeatedly. Console revealed the error: the kext developer ID was not being accepted. Examining the kext showed it was built using Sierra. So boot into Sierra, High Sierra, or Mojave. I did this from Mojave on HFS+.

3) Launch the APFS patcher. Ignore the steps for booting into programming mode, tell it to proceed with the flash. It checks your EEPROM model. This takes a few minutes. No multiple-definitions error in my case, so it proceeded to the flashing.

4) Flashing took a long time, 5 minutes or more. Let it complete without interruption, or you may hose your Mac.

5) After it announces success, reboot into the boot selector. It does indeed see an APFS volume. Flash complete.

* note: before trying the above, I tried to activate firmware programming mode by blessing the CoreServices folder using the undocumented -firmware command. I don't think this was needed, and it threw an error message. Next boot afterwards seemed normal, and Sys Info claimed it was a normal boot. But in case it was needed: "sudo bless -folder -firmware /System/Library/CoreServices", then reboot into Sierra or later to replicate my steps.

-----------
Now I'm off to convert my Mojave install to APFS. Then see if Software Update finally offers OS updates.

To those who still use HFS+ you will not get automatic Software Updates as Mojave and Apple only updates APFS. No exceptions.

 

[K two]

Not yet. They are both recognized. Good quality ram, too.

SMC reset?

 

[p8712]

SMC reset?

Not yet, but will try tonight. I had to remove the battery to upgrade ram, obviously. Maybe that corrupted something.

 

[pkouame]

We need a new patch to CoreDisplay.framework

Of all the frameworks in play here, CoreDisplay has some really significant changes to support Apple's new "VirtualDisplay" technology. Lots of new code. I posted some analysis a while ago. It is really central to some key 10.15 changes in their roadmap. So well worth taking apart and trying to find a simple workaround that lets the latest and greatest CoreDisplay play nice with our acceleration retro-patches.

 

[jackluke]

Can you provide me the AppleGraphicsPowerManagement.kext from .4?

Here is, weirdly this was compiled by apple on April 1st, while almost all the .4 core binaries were compiled on March 28th. The file attached is untouched retrieved from a Core.pkg .4 official Installer app.