macOS 10.14 Mojave on Unsupported Macs Thread

[hvds]

Updated to PB8 (=DP9) from PB7 with System Settings -> Software Update, then Post Install with Mojave patcher (version 1.1.2). No issues, only had to select Force Cache Rebuild in Post Install.
(MacBookPro5,2 17", APFS ROM patch applied, external SSD with APFS)

 

[SDAVE]

Unfortunately Dosdude's disable GPU has broke 2 things for me:

1) Sleep doesn't work (ie close shell doesn't go to sleep) or even via apple > sleep
2) Brightness control is gone from keyboard and in settings

@dosdude1 I restored via resetting PRAM & SMC, and moved back the AMD kexts into S/L/E and force build the cache...

But brightness slider is gone and system can't sleep

 

[Olivia88]

Unfortunately Dosdude's disable GPU has broke 2 things for me:

1) Sleep doesn't work (ie close shell doesn't go to sleep) or even via apple > sleep
2) Brightness control is gone from keyboard and in settings

I have both brightness control and sleep working in Mojave on my 15" mbp with a broken gpu that won't even boot unless disabled, this is how I did it :

(If you want to try this method, just apply the post install patches again and start from #3.)

1 boot into single user mode and set nvram variable:

sudo nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00

2 install Mojave, then apply patches.

3 boot into single user mode again, type:

/sbin/mount -uw /

mkdir AMD

mv /System/library/Extensions/AMDRadeonX3000.kext AMD/

reboot

4 open terminal, type:

sudo mkdir -p /Library/LoginHook

sudo nano /Library/LoginHook/LX3000.sh

contents:

#!/bin/bash
kextload /AMD/AMDRadeonX3000.kext
exit 0

press ctrl + x to exit and y to save.

sudo chmod a+x /Library/LoginHook/LX3000.sh

sudo defaults write com.apple.loginwindow LoginHook /Library/LoginHook/LX3000.sh

5 set gpu for sleep to integrated:

sudo pmset -a gpuswitch 0

reboot

6 check that x3000 is loaded and gpu is set to integrated

sudo kextstat | grep AMD

pmset -g

compare to the screenshot to make sure its correct.

7 optional, increase vram for hd3000 using Jacklukes method here

You have to do #1 again each time the nvram is reset.

 

[SDAVE]

I have both brightness control and sleep working in Mojave on my 15" mbp with a broken gpu that won't even boot unless disabled, this is how I did it :

(If you want to try this method, just apply the post install patches again and start from #3.)

1 boot into single user mode and set nvram variable:

sudo nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00

2 install Mojave, then apply patches.

3 boot into single user mode again, type:

/sbin/mount -uw /

mkdir AMD

mv /System/library/Extensions/AMDRadeonX3000.kext AMD/

reboot

4 open terminal, type:

sudo mkdir -p /Library/LoginHook

sudo nano /Library/LoginHook/LX3000.sh

contents:

#!/bin/bash
kextload /AMD/AMDRadeonX3000.kext
exit 0

press ctrl + x to exit and y to save.

sudo chmod a+x /Library/LoginHook/LX3000.sh

sudo defaults write com.apple.loginwindow LoginHook /Library/LoginHook/LX3000.sh

5 set gpu for sleep to integrated:

sudo pmset -a gpuswitch 0

reboot

6 check that x3000 is loaded and gpu is set to integrated

sudo kextstat | grep AMD

pmset -g

7 optional, increase vram for hd3000 using Jacklukes method here

You have to do #1 again each time the nvram is reset.

Thanks for that.

Unfortunately display slider is still not working (it did before the Dosdude patch).

 

[Olivia88]

Thanks for that.

Unfortunately display slider is still not working (it did before the Dosdude patch).

Then I don't know of any other solution than to install Mojave again, sorry.

 

[SDAVE]

Then I don't know of any other solution than to install Mojave again, sorry.

Thank you.

I will probably do that when final is out.

For now I will try reinstalling these kexts from High Sierra:
AppleBacklight.kext
AppleBacklightExpert.kext
AppleUSBDisplays.kext

 

[olrik77]

Fantastic !

Tonight, i did a clean install of Mojave (latest Beta) on my MP3,1 (GeForce GTX 680), according @dosdude1 method : all is running very very fine.
Mojave is installed on a SSD formated in HFS+ (journaled).
I spend a large part of the night testing : no problem detected so far !

Many thanks,

 

[Olivia88]

Thank you.

I will probably do that when final is out.

For now I will try reinstalling these kexts from High Sierra:
AppleBacklight.kext
AppleBacklightExpert.kext
AppleUSBDisplays.kext

Try #6 and compare it to the screenshot, if you don't have those 4 amd kexts loaded, brightness might not work.

 

[jackluke]

Thank you.

I will probably do that when final is out.

For now I will try reinstalling these kexts from High Sierra:
AppleBacklight.kext
AppleBacklightExpert.kext
AppleUSBDisplays.kext

Not only by these kext, the Display brightness control and sleep function depend also from the GPU Framebuffer kext loaded on Mojave boot, I don't know if the AMD/ATI is the primary GPU on that MacBookPro, but you could try if want to experiment the VRAM increase here: InteHD3000 VRAM Patched kext

but apart replacing not mandatory of these files, the most important part is the chmod/chown and kextcache rebuild, try that you should fix.

Also try the AMD kext suggested by @Olivia88 , simply booting from USB Mojave Installer, Post-Install select only "Legacy Video Patch" and "force cache rebuild".

 

[SDAVE]

Try #6 and compare it to the screenshot, if you don't have those 4 amd kexts loaded, brightness might not work.

Hey you're awesome.

It only had one kext loaded.

Used Kext Utility and dropped all backed up AMD kexts and now it's all back to normal.

 

[Larsvonhier]

Then I don't know of any other solution than to install Mojave again, sorry.

I had this effect on my MacBook 5,2 after I applied the latest beta Mojave and re-applied the dosdude patches for that machine. Could move the slider, but it did not effect the brightness. Keyboard function keys for brightness did nothing, too. Then I re-installed all patches in the patch updater app, rebooted and voila: Brightness ctrl works once again!

 

[SDAVE]

Not only by these kext, the Display brightness control and sleep function depend also from the GPU Framebuffer kext loaded on Mojave boot, I don't know if the AMD/ATI is the primary GPU on that MacBookPro, but you could try if want to experiment the VRAM increase here: InteHD3000 VRAM Patched kext

but apart replacing not mandatory of these files, the most important part is the chmod/chown and kextcache rebuild, try that you should fix.

Also try the AMD kext suggested by @Olivia88 , simply booting from USB Mojave Installer, Post-Install select only "Legacy Video Patch" and "force cache rebuild".

Just did this and it killed the brightness slider/sleep again

Going to restore original kexts.

 

[16v]

Mine yes. Magic Mouse 1

and before?
With beta 8 mine is not working...
touch don´t work.

 

[jackluke]

Just did this and it killed the brightness slider/sleep again

Going to restore original kexts.

Oh that's why, you have a MBP 15" dual GPUs IntelHD3000 and AMD/ATI 6xxx series, you need to use the original AMD/ATI kexts in order to have the brightness/sleep functions.

While I can assure if you install correctly mine patched IntelHD3000 VRAM (through KextUtility in your case), they will work and will not affect in any way the brightness/sleep, you just need the stock backup AMD6xxx kext for enabling that, I meant you need the patched AMD6xxx kext based on AMDRadeonX3000 Framebuffer.

However I guess your issues depend mainly from not correctly installing the patched kext and generating the kextcache, instead of KextUtility, better using these commands from Mojave Terminal:

sudo -s

chown -R 0:0 /S*/L*/E* && chmod -R 755 /S*/L*/E*

kextcache -i /

reboot

edit:
Probably to use QE/CI and VRAM patch with your IntelHD3000 you need to disable totally the AMD/ATI GPU.

Are you sure you used the dosdude1's vram command booting from your Mojave Volume in single user mode (holding CMD+S) after power-on ?
Typing correctly any single character (since obviously you can't copy/paste in single user mode) ?
After done have you used the dGPU Disabler app suggested by dosdude1?

 

[Yipee2016]

I have a question because I'm a little lost. I have a MP 3.1 with High Sierra (thks again @dosdude1) installed on a SSD formatted in APFS. When it will be available I would like to install Mojave. What will be the better way ?
- Do I have to perform a fresh new install on my SSD ?
- Is it preferable to modify the ROM of my Mac before ?

 

[0403979]

Not sure if you guys have seen this but I thought you might find it cool. Off-topic, I know, but neat! Already used it on a couple apps.

Forcing third party apps to use dark mode.

That looks amazing.

 

[jackluke]

A very interesting link about Mojave Dark Mode implementation (high level but still some low level juicy bits) here.

This article is really very interesting, I guess this guy can seriously break the OpenGL Finder menu grey bar transparency code into Mojave "light mode". Should be invited to participate in this thread.

edit:
Of course also his other articles are interesting, especially this one: https://mackuba.eu/2018/07/10/dark-side-mac-2/

 

[saudor]

It's AE retail from Creative Cloud (I'm on a monthly plan) with the latest updates.

I didn't know AE uses OpenGL besides for hardware accelerated UI panels (which I disabled)...and some plugins do use OpenGL (which I disabled). This happens on launch and it freezes after I import any clip.

Curious to see if CC2019 will fix this? I think it will be announced in November.



2011 15" MBP, 16GB RAM, 500GB SSD, Intel HD 3000/Radeon HD6750M...

Forced iGPU via gfxCardStatus 2.4.4i

It shows that iGPU is selected when apps are open and system doesn't slow down to a crawl which is typical to AMD drivers being not fully loaded.

Since something like Sierra, even with gfxCardstat (2.4+ Aka the forked version), some apps will momentarily trigger the dGPU and then gfxcard would switch it back to the iGPU. In older versions, it actually activated both the iGPU and dGPU quietly so that seemed to be the patch/fix.

 

[LuisN]

and before?
With beta 8 mine is not working...
touch don´t work.

Since at least, beta 6

 

[16v]

Since at least, beta 6

hm,...
what model do you have?
cause there is another user, and his mm1 is also not working correctly.

Edit:
Just updated to PB8 touch functionality of MM1 still not working.

 

[DaniloGeekDude]

For those interested, I re-added the original APFS booting implementation back to the post-install tool (from High Sierra Patcher). Of course, be sure to deselect this if you have a machine that has been patched with APFS ROM Patcher. It will NOT be selected by default on systems that supported High Sierra natively, and have an official APFS-compatible BootROM from Apple.

Thank You @dosdude1.

Question please on the highlighted text on the quote. I have a MacBookPro5,3 with the latest Mojave Public beta installed on an external HFS formatted drive. Everything works fine. I tried earlier to run your APFS ROM patcher, but failed. Held off on trying it again. Then I saw this post on your latest Mojave Post Install (version 2.4.0).

So I wanted to see if I could re-ran the Post Install to "implement APFS". It's greyed out when I select my model. So I'm assuming then that based on your quote above, that my MBP5,3 has an "official APFS-compatible BootROM from Apple".

Thank You.

 

[dosdude1]

Thank You @dosdude1.

Question please on the highlighted text on the quote. I have a MacBookPro5,3 with the latest Mojave Public beta installed on an external HFS formatted drive. Everything works fine. I tried earlier to run your APFS ROM patcher, but failed. Held off on trying it again. Then I saw this post on your latest Mojave Post Install (version 2.4.0).

So I wanted to see if I could re-ran the Post Install to "implement APFS". It's greyed out when I select my model. So I'm assuming then that based on your quote above, that my MBP5,3 has an "official APFS-compatible BootROM from Apple".

Thank You.

You need to select the volume as well. If an APFS volume is selected, along with a model that needs the APFS patch, the option will be available.

 

[TimothyR734]

Thank You @dosdude1.

Question please on the highlighted text on the quote. I have a MacBookPro5,3 with the latest Mojave Public beta installed on an external HFS formatted drive. Everything works fine. I tried earlier to run your APFS ROM patcher, but failed. Held off on trying it again. Then I saw this post on your latest Mojave Post Install (version 2.4.0).

So I wanted to see if I could re-ran the Post Install to "implement APFS". It's greyed out when I select my model. So I'm assuming then that based on your quote above, that my MBP5,3 has an "official APFS-compatible BootROM from Apple".

Thank You.

I created a new usb Mojave patcher with the added APFS patch and just like you it was gray out, so formatted my internal hdd to APFS then rebooted into the patcher and the APFS patch was not greyed out installed the latest beta applied the post install patches hit option on reboot and was presented with a EFI and recovery option the only HDD that appeared normal was my external hdd macOSUSB,EFI,recovery. Then name of my formatted internal hdd MacintoshHD is not appearing

 

[LuisN]

hm,...
what model do you have?
cause there is another user, and his mm1 is also not working correctly.

Edit:
Just updated to PB8 touch functionality of MM1 still not working.

mm1
MacBookPro 6,2

 

[OGNerd]

@dosdude1 I restored via resetting PRAM & SMC, and moved back the AMD kexts into S/L/E and force build the cache...

But brightness slider is gone and system can't sleep

Try using the Brightness Slider app that is available from the store.
[doublepost=1535567629][/doublepost]It appears that an APFS formatted boot volume will only be required to receive system software updates, as the Safari Technology Preview update was presented to my HPFS+ and APFS formatted volumes via Software Update.