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

macOS 10.14 Mojave on Unsupported Macs Thread

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
16v said:
250€... and disabling amd gpu makes it slower? (They are expensive in germany)

2012 logicboard means a new mainboard? So then i have a 2012 mbp?
Click to expand...
I suggest you save your money. It will be a constant battle with Apple and an increasingly frustrating experience of a clunky, slow and inferior interface. In macOS 10.15 you will be forbidden from running 32bit apps, and it is not even certain if we will make it so far. The way I see it, we might not go beyond 10.14.4, or 10.14.5. That was the reason for my complaint in an earlier post.
So, put instead Windows 10 Pro on that machine. The old drivers provided by apple are all supported. Everything works as supposed to. Dark Mode in Windows 10 looks better than the unsupported gimmick we have now on Mojave. Updates on Windows are FOR LIFE and not for the tiny 5 to 7 years apple gives you. You get monthly security updates and 2 major yearly updates, from which one is a feature update. So every year your Windows 10 will run better and will have more and more features. Compare that to the hurdles we get from Apple. Plus you can run from 32bit programs created for Windows 95 to the latest native Microsoft Store Apps in 64bit (same for the phone version) and all in-between. And the saying "There is an app for that" is actually 100% true on Windows. You can get MacFanControl (free) and set it to regulate fans by measuring the chip sensor, for example. That last one you need, because apple intentionally gives inferior drivers for bootcamp, forcing their equipment to run hotter on Windows compared to macOS. And you can get modified and updated drivers for the AMD video card in your computer free of charge at https://www.bootcampdrivers.com, which work better on Windows, than the native drivers on macOS.
 
Last edited:
Not wanting to back through 12,000+ responses, I will ask what is probably a redundant question...

Mac App Store on my Late 2008 Aluminum Macbook keeps popping up "ads" from Apple suggesting I really should update to Mojave.

But I know it's not supported, and, anyway, pretty sure I've already followed one of those ads and cannot download because it is not supported.

If Apple changed something and it is in fact supported, I would love to update. But I don't want to use some workaround that I will have to re-do with every updated.

Edit: Nope.

"We could not complete your purchase.

This version of macOS 10.14.3 cannot be installed on this computer."

So, why are they pushing it on Macs that can't install (or even download) it?
 
ASentientBot said:
I got this MacBook7,1 in 2011. No, it wasn't cheap. $1000 new for the base model. But it had 7 years of completely free software updates. It's been rock solid; every repair was because I broke something. Find me a cheaper PC that beats that.

And people love to bash macOS for being "locked down" and "dumbed down" but you're just repeating a worn-out myth. Yes, it's minimalist and intuitive to use. But if you're really a power user, there's a lot of tinkering and automation you can do. Ease of use and power aren't mutually exclusive.

And -- it's silly to think they're breaking this stuff on purpose. They just don't care.
Click to expand...
Consider this: in 2011 you could have ordered a custom built gaming laptop for those same $1000. Hardware-wise it would have run circles around that weak apple hardware. Your Windows version at that moment would have been updated free of charge to Windows 10, which, as I just wrote, promises now updates FOR LIFE (monthly security + 2 major yearly updates, one of which a feature update). If you would have insisted on MacOS, well there are plenty of Hackintosh tutorials on the web. Granted the gaming laptop would have been uglier, than the pretty toy called MacBook. Also although a gaming laptop gets a plastic housing and the MacBook is in an aluminum, if you would have applied a bit of caution, both would have aged pretty well.
We are all suckers for having carried on that same attitude of yours. That's why Apple's pockets are now full with our cash, they couldn't care less for the suckers that we are and you and many others are spending hundreds and hundreds of valuable hours (how much does that cost?) trying to temporarily overcome the locks apple implements against us the faithful suckers.
[doublepost=1550105299][/doublepost]
jtara said:
Not wanting to back through 12,000+ responses, I will ask what is probably a redundant question...

Mac App Store on my Late 2008 Aluminum Macbook keeps popping up "ads" from Apple suggesting I really should update to Mojave.

But I know it's not supported, and, anyway, pretty sure I've already followed one of those ads and cannot download because it is not supported.

If Apple changed something and it is in fact supported, I would love to update. But I don't want to use some workaround that I will have to re-do with every updated.

Edit: Nope.

"We could not complete your purchase.

This version of macOS 10.14.3 cannot be installed on this computer."

So, why are they pushing it on Macs that can't install (or even download) it?
Click to expand...
Keep on dreaming! Just read my post above and you will have your answer as to why apple would be pushing you to update. But to give you a quick relief, well Apple wants your cash! If you are a faithful sucker, you will buy the latest model and get Mojave with it for FREE. Just buy the hardware, the operating system is free of charge (but only for the next 7 years). What a joke. I can't believe I was so blind, and some continue to be blind. Sad, sad, sad.
 
Hey guys, I just got a MacBook 7,1 that I'm using for school and I noticed something strange when I go into "About This Mac." For some odd reason it thinks my display is 12 inches instead of 13.3. I'm wondering if anyone else with a MacBook Mid 2010 has the same issue? Graphics acceleration is working perfect, so it must just be cosmetic. Still weird though, as my mother's MacBook 5,1 recognizes it as 13.3 inches on Mojave.
 

Attachments

  • Screen Shot 2019-02-13 at 8.12.25 PM.png
    Screen Shot 2019-02-13 at 8.12.25 PM.png
    56.4 KB · Views: 219
Sveto said:
I suggest you save your money. It will be a constant battle with Apple and an increasingly frustrating experience of a clunky, slow and inferior interface. In macOS 10.15 you will be forbidden from running 32bit apps, and it is not even certain if we will make it so far. The way I see it, we might not go beyond 10.14.4, or 10.14.5. That was the reason for my complaint in an earlier post.
So, put instead Windows 10 Pro on that machine. The old drivers provided by apple are all supported. Everything works as supposed to. Dark Mode in Windows 10 looks better than the unsupported gimmick we have now on Mojave. Updates on Windows are FOR LIFE and not for the tiny 5 to 7 years apple gives you. You get monthly security updates and 2 major yearly updates, from which one is a feature update. So every year your Windows 10 will run better and will have more and more features. Compare that to the hurdles we get from Apple. Plus you can run from 32bit programs created for Windows 95 to the latest native Microsoft Store Apps in 64bit (same for the phone version) and all in-between. And the saying "There is an app for that" is actually 100% true on Windows. You can get MacFanControl (free) and set it to regulate fans by measuring the chip sensor, for example. That last one you need, because apple intentionally gives inferior drivers for bootcamp, forcing their equipment to run hotter on Windows compared to macOS. And you can get modified and updated drivers for the AMD video card in your computer free of charge at https://www.bootcampdrivers.com, which work better on Windows, than the native drivers on macOS.
Click to expand...
??? There is no plan to change logicboard.

And maybe the pro's here get the amd cards to work... sometimes. I believe in that.

But maybe i will try to use win on this machine. I also need a new win laptop...
What to do to use win? Only win? Or do i have to install macos too?
 
Hi all,

Again, thanks to dosdude and all of the other individuals who contribute to this goal of keeping older machines alive. I am still on an early 2009 iMac with 10.4.2. No previous issues after following the instructions exactly. I always do each new upgrade on a supplemental usb drive with a standard install and then add some additional maintenance programs. When I ever have an issue with the internal drive I use the supplemental as the start-up.

Yesterday I installed 10.4.3 on the usb drive. Installation went smoothly with the usual amount of time. Post install completed without issue, also.

Now the issue. After the install, the iMac/drive is as slow as molasses in January, maybe even February. Reaction time is almost frozen. Beyond description.

Any ideas why this may have happened with this install? Never had any issue like this, previously. Obviously, I did not attempt the upgrade on the internal drive.

Thanks!
 
I have an iMac 7,1 which I've just ordered a Penryn processor for. I see that the Penryn information about the 7,1 has been stripped from the OP--should this be a cause for concern? Mojave is still a go with a processor upgrade? Anything to do with the GFX card(s)?

Additionally, today I was gifted a 27" 2009 iMac 11,1 that "had a bad HDD", which after inspection actually "had a borked video card." I see that the 5xxx and 6xxx series are a non-starter for Mojave anyway. Kind of hilarious I might get Mojave running on a 7,1 but not an 11,1.

I guess I could run Mojave on the 11,1 if I had an nVidia card. I see reference to people putting 880m in 2011 27" iMacs, but nothing for 2009 (A1312). Can anyone comment? Is there an nVidia option for this model? It certainly doesn't seem to crop up on many forums...thx!
 
  • Like
Reactions: olad
psu7276 said:
Yesterday I installed 10.4.3 on the usb drive. Installation went smoothly with the usual amount of time. Post install completed without issue, also.

Now the issue. After the install, the iMac/drive is as slow as molasses in January, maybe even February. Reaction time is almost frozen. Beyond description.

Any ideas why this may have happened with this install? Never had any issue like this, previously. Obviously, I did not attempt the upgrade on the internal drive.
Click to expand...

You probably need to re-apply Mojave Patcher.app (Post-Install) related to USB?
 

Attachments

  • Screenshot 18.png
    Screenshot 18.png
    37.7 KB · Views: 231
psu7276 said:
Hi all,

Again, thanks to dosdude and all of the other individuals who contribute to this goal of keeping older machines alive. I am still on an early 2009 iMac with 10.4.2. No previous issues after following the instructions exactly. I always do each new upgrade on a supplemental usb drive with a standard install and then add some additional maintenance programs. When I ever have an issue with the internal drive I use the supplemental as the start-up.

Yesterday I installed 10.4.3 on the usb drive. Installation went smoothly with the usual amount of time. Post install completed without issue, also.

Now the issue. After the install, the iMac/drive is as slow as molasses in January, maybe even February. Reaction time is almost frozen. Beyond description.

Any ideas why this may have happened with this install? Never had any issue like this, previously. Obviously, I did not attempt the upgrade on the internal drive.

Thanks!
Click to expand...

Noticed a similar behavior, I'd say it is the indicted 18D109 update that added something new to our unsupported macs, during verbose boot I see many "EXC_RESOURCE" not serious but in activity monitor I have almost full RAM saturation in idle mode and I was used to have half RAM use of my total amount, so I "fixed" in this way, re-installed the 10.14.2 main system overwriting the 10.14.3 and everything went fine.
Probably the 10.14.3 without the 18D109 embedded is more stable on unsupported macs but it's becoming not so easy to find.

@ASentientBot could you confirm this? I mean do you use the very stable 10.14.2 or 10.14.3 without issues on Macbook7,1 ?
 
  • Like
Reactions: olad and Badruzeus
dosdude1 said:
​
Current Hardware Support Status:
  • Machine Support
    • Early-2008 or newer Mac Pro, iMac, or MacBook Pro:
      • MacPro3,1
      • MacPro4,1
      • iMac8,1
      • iMac9,1
      • iMac10,x
      • iMac11,x (systems with AMD Radeon HD 5xxx and 6xxx series GPUs will be almost unusable when running Mojave. More details are located in the Current Issues section below.)
      • iMac12,x (systems with AMD Radeon HD 5xxx and 6xxx series GPUs will be almost unusable when running Mojave. More details are located in the Current Issues section below.)
      • MacBookPro4,1
      • MacBookPro5,x
      • MacBookPro6,x
      • MacBookPro7,1
      • MacBookPro8,x
    • Late-2008 or newer MacBook Air or Aluminum Unibody MacBook:
      • MacBookAir2,1
      • MacBookAir3,x
      • MacBookAir4,x
      • MacBook5,1
    • Early-2009 or newer Mac Mini or white MacBook:
      • Macmini3,1
      • Macmini4,1
      • Macmini5,x
      • MacBook5,2
      • MacBook6,1
      • MacBook7,1
    • Early-2008 or newer Xserve:
      • Xserve2,1
      • Xserve3,1
  • Video Card Support
    • Pre-Metal AMD video cards (Radeon HD 6xxx series and older without acceleration, Radeon HD 4xxx series and older with acceleration.)
    • Pre-Metal Nvidia video cards (GeForce 5xx series and older, i.e. 8600M(GT), 8800M(GT), 9400M, 9600M(GT), 320M)
    • Pre-Metal Intel video cards (Intel HD Graphics 3000 and Intel HD Graphics Arrandale)
Current Issues
  • Minor Issues
    • Graphics anomalies: Currently, pre-metal video cards used in Mojave will produce a weird darkish grey Menu Bar and Finder sidebar when using the light theme. In the dark theme, these anomalies are not present, while other, less obvious anomalies are present (window corners may not render properly, bottom part of dock menus may have artifacts). A workaround for graphics anomalies in light mode is to enable Reduce Transparency in System Preferences > Accessibility > Display (this might create additional side effects beside the obvious loss of transparency as some systems with pre-metal AMD graphics render the dock in dark gray).
    • Built-in iSight cameras: Currently, built-in iSight cameras do not work correctly on some machines. It seems to be hit or miss, but when installing, expect your iSight camera to be non-functional.
    • Trackpad (MacBook5,2 affected only). Trackpad multi-finger gestures on the MacBook5,2 not supported in Mojave. While the trackpad works and is fully usable, Mojave detects it as just a standard mouse, preventing you from changing some trackpad-oriented settings.
  • Major Issues
    • AMD Radeon HD 5xxx/6xxx series GPU acceleration: Currently, it is not possible to get full graphics acceleration when running Mojave on a system with a Radeon HD 5xxx or 6xxx series GPU. Mojave will be almost UNUSABLE without graphics acceleration. This includes the 15" and 17" MacBook Pro systems (MacBookPro8,2 and 8,3). If you want to enable GPU acceleration on these machines, you'll need to disable the AMD GPU (This will work on MacBook Pro 8,2 and 8,3 systems ONLY. You CANNOT disable the AMD GPU in an iMac.) Weird colors will also be produced when running Mojave with one of these video cards installed/enabled. To disable the AMD GPU on a 2011 MacBook Pro 8,2 or 8,3, follow the guide found here.
    • App Store Crashing: Some users have reported crashing upon opening the App Store. This is caused by App Store videos and can be worked around by disabling video autoplay and not viewing App Store videos. This is not a fix, this is a workaround. Safari may also experience crashes with certain kinds of embedded videos.
    • Early-2008 Mac Pro (MacPro3,1) GPU support: When running Mojave, you CANNOT use a newer AMD video card EVEN IF it is a Metal-compatible card and is supported in Mojave. The newer AMD drivers used in Mojave require the SSE4.2 instruction set, which the MacPro3,1 does not support. There is no way around this at this time. Your only GPU upgrade options for MacPro3,1 systems are Nvidia cards, which work perfectly fine.
    • Unsupported WiFi modules in some systems. Macs that use the Broadcom BCM4321 WiFi module will not have functional WiFi when running Mojave. A fix for this is to open up your machine and install a compatible WiFi card. Machines affected include some MacPro3,1, MacBook5,2, MacBookPro4,1, iMac8,1, Macmini3,1, and MacBookAir2,1 systems. Please note that not all these machines will have an unsupported card, this is just a list of machines known to have shipped with that card in some configurations.
Current Issues by Hardware
  • Minor Issues
    • Graphics anomalies:
      • All machines
    • Built-in iSight camera:
      • All machines, hit or miss
    • Trackpad:
      • MacBook5,2
  • Major Issues
    • AMD GPU acceleration:
      • All machines with a Radeon HD 5xxx or 6xxx series GPUs (these systems will be almost unusable when running Mojave. More details are located in the Current Issues section above.)
    • App Store Crashing:
      • All machines with Radeon HD 4xxx series GPUs
    • AMD GPU support:
      • MacPro3,1
    • Unsupported WiFi modules:
      • All machines with Broadcom BCM4321 WiFi modules
Installation:
To install on your machine, you can download and run the macOS Mojave Patcher application, which will let you download a copy of the latest installer app from Apple and create a bootable installer drive for use on unsupported Macs. It contains all the patches necessary to achieve the hardware support listed above. The installation guide can be found here and an installation guide video here.

APFS ROM Patcher:
Warning: This tool could irreversibly brick your EFI chip. Please exercise caution with machines that have multiple EEPROM definitions. Relevant information can be found here and here. The APFS ROM patcher can be found here. Use the password apfs to decrypt the ZIP.

Mojave Builds and Installer Versions (Developer Preview, Public Beta):
2018/06/04 - 2018/09/12 10.14.0 DP1 - DP11, PB1 - PB10
2018/06/04 DP1, build 18A293u, installer 14.0.08
2018/06/19 DP2, build 18A314h, installer 14.0.11
2018/06/26 PB1, build 18A314k, installer 14.0.11
2018/07/03 DP3, build 18A326g, installer 14.0.12
2018/07/06 PB2, build 18A326h, installer 14.0.12
2018/07/16 DP4, 2018/07/17 PB3, build 18A336e, installer 14.0.14
2018/07/30 DP5, 2018/07/31 PB4, build 18A347e, installer 14.0.15
2018/08/06 DP6, 2018/08/06 PB5, build 18A353d, installer 14.0.16
2018/08/13 DP7, 2018/08/13 PB6, build 18A365a, installer 14.0.17
2018/08/20 DP8, 2018/08/20 PB7, build 18A371a, installer 14.0.18
2018/08/27 DP9, 2018/08/27 PB8, build 18A377a, installer 14.0.20
2018/09/04 DP10, 2018/09/04 PB9, build 18A384a, installer 14.0.21
2018/09/12 DP11, 2018/09/12 PB10, build 18A389, installer 14.0.21​
2018/09/24 10.14.0 Final, build 18A391, installer 14.0.22
2018/09/25 - 2018/10/23 10.14.1 DP1 - DP5, PB1 - PB5 - do not install
2018/09/25 10.14.1 DP1, 2018/09/27 PB1, build 18B45d - do not install
2018/10/02 10.14.1 DP2, 2018/10/02 PB2, build 18B50c - do not install
2018/10/08 10.14.1 DP3, 2018/10/08 PB3, build 18B57c - do not install
2018/10/17 10.14.1 DP4, 2018/10/17 PB4, build 18B67a - do not install
2018/10/23 10.14.1 DP5, 2018/10/23 PB5, build 18B73a - do not install​
2018/10/30 10.14.1 Final, build 18B75, installer 14.1.0 - install from drive
2018/10/31 - 2018/11/28 10.14.2 DP1 - DP4, PB1 - PB4
2018/10/31 10.14.2 DP1, 2018/11/02 PB1, build 18C31g
2018/11/07 10.14.2 DP2, 2018/11/07 PB2, build 18C38b
2018/11/16 10.14.2 DP3, 2018/11/16 PB3, build 18C48a
2018/11/28 10.14.2 DP4, 2018/11/28 PB4, build 18C52a​
2018/12/05 10.14.2 Final, build 18C54, installer 14.2.2
2018/12/10 - 2019/01/11 10.14.3 DP1 - DP4, PB1 - PB4
2018/12/10 10.14.3 DP1, 2018/12/11 PB1, build 18D21c
2018/12/19 10.14.3 DP2, 2018/12/19 PB2, build 18D32a
2019/01/07 10.14.3 DP3, 2019/01/07 PB3, build 18D38a
2019/01/11 10.14.3 DP4, 2019/01/11 PB4, build 18D39a​
2019/01/21 10.14.3 Final, build 18D42, installer 14.3.2
2019/02/07 10.14.3 Supplemental, build 18D109
2019/01/24 - 2019/02/04 10.14.4 DP1 - DP2, PB1
2019/01/24 10.14.4 DP1, 2019/01/28 PB1, build 18E174f - do not install
2019/02/04 10.14.4 DP2, 2019/02/05 PB2, build 18E184e - do not install​
Credits:
@dosdude1 - Developed macOS Mojave Patcher.
@parrotgeek1 - Developed LegacyUSBInjector, SIPManager, and NDRVShim. (Source Code)
@Czo - Developed SUVMMFaker. (Source Code)
@Badruzeus - Discovered that Sierra OpenGL drivers work in Mojave.
@ASentientBot - Fixed Nvidia kernel panic, Core 2 Duo kernel panic, and iSight.
@jackluke - Narrowed down cause of Core 2 Duo kernel panic.

Moderator Note:
Please do not ask for, or provide help getting developers profile information to access unauthorised beta software on MacRumors. If you are not a developer, sign up to the Apple Beta Software Program to get the official public beta releases.
Click to expand...
[doublepost=1550137039][/doublepost]Hello,
i want to create a fusiondrive on a macbook pro 17, early 08.
Everytime I get the error 69888. I can't create the fusiondrive. Every help is awesome.
Thank you.
[doublepost=1550139212][/doublepost]Hello dear Mrler,
I am having trouble creating a Fusion Drive with Macos Mojave on a MacBook Pro 17 early 08. There is always an error code - 69888. All instructions I found on the Internet returned the same error code. I tried diskutil cs list, but he wrote me that he does not find anything there. I had also tried kernel CoreStorage create FusionDrive / dev / disk0 / dev / disk1, where he started doing something and aborted error code 69888.

What can I do ? Thank you !
 
Did anybody successfully dual booted(two APFS installs) on their APFS ROM patched systems? I don't seem to have any luck dual booting Mojave and High Sierra(both APFS partitions).
There is definitely something going on since 18D109 update.
First of all I was unable to create a High Sierra patched USB installer(tried 3 USB sticks which worked fine previously).
I had to boot into Snow Leopard(the only recent OS I had apart from Mojave) on my externally connected original HDD and created High Sierra patched USB installer without any issues.
First I tried to install High Sierra on a APFS volume which I created under the existing container, it did not go through.
Then I re-partitioned my SSD and created a dedicated APFS partition with it's own container for High Sierra. The install went fine, post install patches with force cache rebuild went fine but upon restart I was greeted with a prohibited sign.

Am I missing something? I would not be surprised if somewhere along the line I missed the writing on the wall that we cannot dual boot APFS installs on our unsupported machines.
 
jackluke said:
...Probably the 10.14.3 without the 18D109 embedded is more stable on unsupported macs....
Click to expand...
I found out the hard way. 10.14.3 with the 18D109 used up all the RAM on my MBP4,1 (6Gb memory) despite all efforts. Reinstalled 10.14.3 without the 18D109 (18D42) from the USB Mojave Patcher and everything quieted down. I think I will wait for the 10.14.4 final.
 
  • Like
Reactions: jackluke
olad said:
I found out the hard way. 10.14.3 with the 18D109 used up all the RAM on my MBP4,1 (6Gb memory) despite all efforts. Reinstalled 10.14.3 without the 18D109 (18D42) from the USB Mojave Patcher and everything quieted down. I think I will wait for the 10.14.4 final.
Click to expand...

Thanks for your feedback, I'm absolutely agree, during "activity monitor" full RAM saturation in idle mode is never a good sign for hardware's health, I noticed it earlier when at loginUI got full ramped fan, while on an supported mac with 18D109 there is no ram saturation so it's definitely an incompatibility issue with older macs, after-all the 18D109 was released during the 10.14.4 beta phase it still preserves the OpenGL init function but personally I don't like an OS with full RAM in idle mode, so for now I avoid further updates.

edit:
After deep analysis I confirm that using 10.14.3 build 18D42 (without the 18D109 update) makes Mojave more stable on unsupported macs with normal RAM usage in idle mode.

For clarity, with "idle mode" I don't mean "sleep/stand-by" but a "wake" system with the main core processes actives only.
 
Last edited:
  • Like
Reactions: webg3, olad and Badruzeus
avz said:
Did anybody successfully dual booted(two APFS installs) on their APFS ROM patched systems? I don't seem to have any luck dual booting Mojave and High Sierra(both APFS partitions).
There is definitely something going on since 18D109 update.
First of all I was unable to create a High Sierra patched USB installer(tried 3 USB sticks which worked fine previously).
I had to boot into Snow Leopard(the only recent OS I had apart from Mojave) on my externally connected original HDD and created High Sierra patched USB installer without any issues.
First I tried to install High Sierra on a APFS volume which I created under the existing container, it did not go through.
Then I re-partitioned my SSD and created a dedicated APFS partition with it's own container for High Sierra. The install went fine, post install patches with force cache rebuild went fine but upon restart I was greeted with a prohibited sign.

Am I missing something? I would not be surprised if somewhere along the line I missed the writing on the wall that we cannot dual boot APFS installs on our unsupported machines.
Click to expand...

Are you using the Mojave Patcher to apply, the APFS patch as opposed to the APFS ROM patches applied to the boot roms? I believe that mechanism tethers the EFI boot partition to a specific APFS boot device on a given drive.
 
  • Like
Reactions: avz
jhowarth said:
Are you using the Mojave Patcher to apply, the APFS patch as opposed to the APFS ROM patches applied to the boot roms? I believe that mechanism tethers the EFI boot partition to a specific APFS boot device on a given drive.
Click to expand...

I applied APFS ROM patch, and there is no need to use Mojave patcher as I already had Mojave installed. My goal was to dual boot Mojave with High Sierra(both APFS).
I am happy to report that dual boot seems to be working but there is a catch: the only way to boot into High Sierra is by holding Option at the startup and selecting the correct EFI Boot(since two of them are present). It is not really a stretch by any means. Mighty patchers seems to work from every angle!
 
avz said:
I applied APFS ROM patch, and there is no need to use Mojave patcher as I already had Mojave installed. My goal was to dual boot Mojave with High Sierra(both APFS).
I am happy to report that dual boot seems to be working but there is a catch: the only way to boot into High Sierra is by holding Option at the startup and selecting the correct EFI Boot(since two of them are present). It is not really a stretch by any means. Mighty patchers seems to work from every angle!
Click to expand...

Are you saying that you can't use the Startup Disk system preference panel to toggle between the two APFS volumes on the same physical drive?
 
jhowarth said:
Are you saying that you can't use the Startup Disk system preference panel to toggle between the two APFS volumes on the same physical drive?
Click to expand...

Correct. I actually just run maintenance tasks in Onyx(my goal was actually to fix the App Store as it refuses to show me the latest Safari and iTunes updates) and now I can use the Startup Disk system preference panel to toggle between the two APFS volumes(partitions might be more accurate) on the same physical drive.
It was very strange seeing prohibitory sign after applying post install patches but the end result is still a success. I can't believe how solid the patchers are.
P.S. APFS is definitely very picky and quite tricky to work with. I guess it is still a new standard and requires some work.
 
  • Like
Reactions: olad
jackluke said:
After deep analysis I confirm that using 10.14.3 build 18D42 (without the 18D109 update) makes Mojave more stable on unsupported macs with normal RAM usage in idle mode.
Click to expand...

On my case it only happenned on 1st boot (post-update). Yes, about RAM usage is above normal when idle; with only 2 x 2GB RAM I realized that having "swap0, swap1, swap2, swap3" files on "/private/var/vm", they're more than 6GB in size #LoL. On Activity Monitor I see high RAM usage for WindowServer and Spotlight tasks.

I then manually rebuild dyld etc.. using Onyx maintenance tool (at least when was lazy with Terminal commands); reboot.. now everything is fine, even smoother than 18D43. Oh ya, I use HFS+.. not sure with APFS.
 
  • Like
Reactions: webg3, olad and jackluke
Badruzeus said:
On my case it only happenned on 1st boot (post-update). Yes, about RAM usage is above normal when idle; with only 2 x 2GB RAM I realized that having "swap0, swap1, swap2, swap3" files on "/private/var/vm", they're more than 6GB in size #LoL. On Activity Monitor I see high RAM usage for WindowServer and Spotlight tasks.

I then manually rebuild dyld etc.. using Onyx maintenance tool (at least when was lazy with Terminal commands); reboot.. now everything is fine, even smoother than 18D43. Oh ya, I use HFS+.. not sure with APFS.
Click to expand...

It could be, but for me it's a bit different and weird, the full RAM usage occurs but it's not effectively reported on "activity monitor" in both memory/cpu tabs things seem normal, I only noticed that by three factors: "EXC_RESOURCE" instances during verbose, fans a bit louder, and "Memory used" in idle (with all apps closed) 7 gb used / 8 gb physical available.

While on 10.14.3 18D42 even with safari, maps, notes and some other app opened I don't exceed the 3.5 gb used / 8 gb available, far better.
 
  • Like
Reactions: webg3, olad and Badruzeus
jackluke said:
It could be, but for me it's a bit different and weird, the full RAM usage occurs but it's not effectively reported on "activity monitor" in both memory/cpu tabs things seem normal, I only noticed that by three factors: "EXC_RESOURCE" instances during verbose, fans a bit louder, and "Memory used" in idle (with all apps closed) 7 gb used / 8 gb physical available.

While on 10.14.3 18D42 even with safari, maps, notes and some other app opened I don't exceed the 3.5 gb used / 8 gb available, far better.
Click to expand...

I remember killed lot of Mojave's LaunchAgents && LaunchDaemons since 10.14.0, so far.. having no issue:
Code: 
#!/bin/bash

# Disabling GateKeeper (10.14):
sudo spctl --master-disable

# Unload useless LaunchDaemons services on 10.14:

cd /System/Library/LaunchDaemons
sudo launchctl unload -wF com.apple.backupd-helper.plist
sudo launchctl unload -wF com.apple.dynamic_pager.plist
sudo launchctl unload -wF com.apple.CrashReporterSupportHelper.plist
sudo launchctl unload -wF com.apple.ReportCrash.Root.plist
sudo launchctl unload -wF com.apple.ReportCrash.Root.Self.plist
sudo launchctl unload -wF com.apple.spindump.plist
sudo launchctl unload -wF com.apple.tailspind.plist
sudo launchctl unload -wF com.apple.touchbarserver.plist

# Moving useless LaunchDaemons services on 10.14:

sudo mv com.apple.backupd-helper.plist com.apple.backupd-helper.bak
sudo mv com.apple.dynamic_pager.plist com.apple.dynamic_pager.bak
sudo mv com.apple.CrashReporterSupportHelper.plist com.apple.CrashReporterSupportHelper.bak
sudo mv com.apple.ReportCrash.Root.plist com.apple.ReportCrash.Root.bak
sudo mv com.apple.ReportCrash.Root.Self.plist com.apple.ReportCrash.Root.Self.bak
sudo mv com.apple.spindump.plist com.apple.spindump.plist.bak
sudo mv com.apple.tailspind.plist com.apple.tailspind.plist.bak
sudo mv com.apple.touchbarserver.plist com.apple.touchbarserver.bak

# Moving useless LaunchAgents services on 10.14:

cd /System/Library/LaunchAgents
sudo mv com.apple.applespell.plist com.apple.applespell.bak
sudo mv com.apple.cloudphotosd.plist com.apple.cloudphotosd.bak
sudo mv com.apple.Maps.pushdaemon.plist com.apple.Maps.pushdaemon.bak
sudo mv com.apple.NowPlayingTouchUI.plist com.apple.NowPlayingTouchUI.bak
sudo mv com.apple.photoanalysisd.plist com.apple.photoanalysisd.bak
sudo mv com.apple.ReportCrash.plist com.apple.ReportCrash.bak
sudo mv com.apple.ReportCrash.Self.plist com.apple.ReportCrash.Self.bak
sudo mv com.apple.spindump_agent.plist com.apple.spindump_agent.bak
sudo mv com.apple.touristd.plist com.apple.touristd.bak

# Disable Sleep & Hibernate to save free space:

cd /
sudo pmset -a hibernatemode 0
sudo rm /private/var/vm/sleepimage
sudo touch /private/var/vm/sleepimage
sudo chflags uchg /private/var/vm/sleepimage

# Rebuild prelikedkernel, kernelcache & dyld on macOS:

sudo rm -f /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache && sudo touch /System/Library/Extensions && sudo kextcache -u / && sudo update_dyld_shared_cache -force

# Done!
echo -e "Succeeded! Enjoy optimized macOS."
exit

Oh ya; 18D43 is from UpdateCombo (offline).
#EDIT: I don't use TimeMachine backup, rarely (almost never) using iPhoto, no need AppleSpell, and with SpinDump & CrashReport disabled is not good for troubleshooting purpose.
 
Last edited:
  • Like
Reactions: bogdanf and jackluke
AHOY! New version of macOS installer down from the 1.2.3 patcher. Previous was 14.3.2. w/2018 date, latest is 14.3.3 with Feb.14, 2019 date. Payload is a bit bigger, too. Making a new USB stick, next.
 
Last edited:
  • Like
Reactions: ASentientBot
may have missed this since I haven't visited the thread in awhile, gonna try to perform a search now. but I've been running the most up to date Mojave 10.14.3 on my unsupported mid 2010 MBP without a problem. however I did recently notice when I went into the photos app and selected a photo to view, computer kernel panics every time. this is the only time it does this. here is a report of the kernel panic. any known fixes? computer updated today to a newer version and it still occurs.

Thu Feb 14 22:47:43 2019



*** Panic Report ***

panic(cpu 2 caller 0xffffff7f92fa583d): "GPU Panic: mux-regs 5 3 7f 0 0 0 severity 3 WS-ready 1 switch-state 0 IG FBs 0 EG FBs 1:3 power-state 0 3D idle HDA idle system-state 1 power-level 20:20 connect-change 0 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff8cf767b000 0x0a5480a2, D0, P2/4\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleGraphicsControl/AppleGraphicsControl-3.28.4/src/AppleMuxControl/kext/GPUPanic.cpp:170

Backtrace (CPU 2), Frame : Return Address

0xffffff80bc8daa80 : 0xffffff8011baeb0d

0xffffff80bc8daad0 : 0xffffff8011ce8653

0xffffff80bc8dab10 : 0xffffff8011cda07a

0xffffff80bc8dab80 : 0xffffff8011b5bca0

0xffffff80bc8daba0 : 0xffffff8011bae527

0xffffff80bc8dacc0 : 0xffffff8011bae373

0xffffff80bc8dad30 : 0xffffff7f92fa583d

0xffffff80bc8dad90 : 0xffffff7f93c8b441

0xffffff80bc8dae50 : 0xffffff7f93d571ca

0xffffff80bc8dae90 : 0xffffff7f93d57235

0xffffff80bc8daf10 : 0xffffff7f94d107f0

0xffffff80bc8db030 : 0xffffff7f93d78d35

0xffffff80bc8db050 : 0xffffff7f93c92048

0xffffff80bc8db100 : 0xffffff7f93c8fa84

0xffffff80bc8db2f0 : 0xffffff7f93c914c1

0xffffff80bc8db3c0 : 0xffffff7f93edc58e

0xffffff80bc8db4a0 : 0xffffff7f93ed9b2e

0xffffff80bc8db510 : 0xffffff7f93eda799

0xffffff80bc8db580 : 0xffffff7f93edadce

0xffffff80bc8db6b0 : 0xffffff7f93edb799

0xffffff80bc8db7e0 : 0xffffff7f93f0b9cb

0xffffff80bc8db820 : 0xffffff7f93f0c6bd

0xffffff80bc8db860 : 0xffffff7f93f062e2

0xffffff80bc8db9d0 : 0xffffff7f93f06b71

0xffffff80bc8dba10 : 0xffffff7f93f0283d

0xffffff80bc8dba40 : 0xffffff7f93ee6a85

0xffffff80bc8dba80 : 0xffffff801228779c

0xffffff80bc8dbae0 : 0xffffff80122859c0

0xffffff80bc8dbb30 : 0xffffff801228ecdf

0xffffff80bc8dbc70 : 0xffffff8011c94c64

0xffffff80bc8dbd80 : 0xffffff8011bb43ed

0xffffff80bc8dbdd0 : 0xffffff8011b8ebe5

0xffffff80bc8dbe50 : 0xffffff8011ba35ae

0xffffff80bc8dbef0 : 0xffffff8011cc17bb

0xffffff80bc8dbfa0 : 0xffffff8011b5c486

Kernel Extensions in backtrace:

com.apple.driver.AppleMuxControl(3.28.4)[EFC6EE53-4EB1-34F5-B6E4-43429F691B51]@0xffffff7f92f97000->0xffffff7f92fa9fff

dependency: com.apple.driver.AppleGraphicsControl(3.28.4)[B940D328-A2B1-3906-972C-289E86DFDE48]@0xffffff7f92f56000

dependency: com.apple.iokit.IOACPIFamily(1.4)[67079254-1B34-31D2-8C7B-B138E26BFDD8]@0xffffff7f92a81000

dependency: com.apple.iokit.IOPCIFamily(2.9)[5C9A453F-559B-3683-9E81-D288D13A33CE]@0xffffff7f92495000

dependency: com.apple.iokit.IOGraphicsFamily(530.14)[D44517BE-2B53-3BD5-826E-4E78B55E3B73]@0xffffff7f92c2e000

dependency: com.apple.AppleGraphicsDeviceControl(3.28.4)[E80DEB91-2401-31C2-901F-CA63B4342337]@0xffffff7f92f47000

com.apple.nvidia.classic.NVDAResmanTesla(10.0.4)[F8258F0F-61AD-30F4-BDD5-B18CCAAE535A]@0xffffff7f93c3a000->0xffffff7f93ea2fff

dependency: com.apple.iokit.IOPCIFamily(2.9)[5C9A453F-559B-3683-9E81-D288D13A33CE]@0xffffff7f92495000

dependency: com.apple.iokit.IONDRVSupport(530)[693B770C-4748-33DC-B497-CF8C103DDD0E]@0xffffff7f92f6d000

dependency: com.parrotgeek.NDRVShim(1)[408EA24C-230F-3FA4-8F74-1EA79ABDD3BD]@0xffffff7f93c37000

dependency: com.apple.iokit.IOGraphicsFamily(530.14)[D44517BE-2B53-3BD5-826E-4E78B55E3B73]@0xffffff7f92c2e000

com.apple.GeForceTesla(10.0.4)[426B2568-8B0A-372B-BB33-B421D942837A]@0xffffff7f93eae000->0xffffff7f93f6cfff

dependency: com.apple.iokit.IOPCIFamily(2.9)[5C9A453F-559B-3683-9E81-D288D13A33CE]@0xffffff7f92495000

dependency: com.apple.iokit.IONDRVSupport(530)[693B770C-4748-33DC-B497-CF8C103DDD0E]@0xffffff7f92f6d000

dependency: com.apple.iokit.IOGraphicsFamily(530.14)[D44517BE-2B53-3BD5-826E-4E78B55E3B73]@0xffffff7f92c2e000

dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.4)[F8258F0F-61AD-30F4-BDD5-B18CCAAE535A]@0xffffff7f93c3a000

com.apple.nvidia.classic.NVDANV50HalTesla(10.0.4)[5DCF031B-F81F-32A3-ADCD-18E16EAC7CF0]@0xffffff7f94bec000->0xffffff7f94e94fff

dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.4)[F8258F0F-61AD-30F4-BDD5-B18CCAAE535A]@0xffffff7f93c3a000

dependency: com.apple.iokit.IOPCIFamily(2.9)[5C9A453F-559B-3683-9E81-D288D13A33CE]@0xffffff7f92495000



BSD process name corresponding to current thread: Photos

Boot args: -no_compat_check
 
  • Like
Reactions: ASentientBot
dictoresno said:
may have missed this since I haven't visited the thread in awhile, gonna try to perform a search now. but I've been running the most up to date Mojave 10.14.3 on my unsupported mid 2010 MBP without a problem. however I did recently notice when I went into the photos app and selected a photo to view, computer kernel panics every time. this is the only time it does this. here is a report of the kernel panic. any known fixes? computer updated today to a newer version and it still occurs.

Thu Feb 14 22:47:43 2019



*** Panic Report ***

panic(cpu 2 caller 0xffffff7f92fa583d): "GPU Panic: mux-regs 5 3 7f 0 0 0 severity 3 WS-ready 1 switch-state 0 IG FBs 0 EG FBs 1:3 power-state 0 3D idle HDA idle system-state 1 power-level 20:20 connect-change 0 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff8cf767b000 0x0a5480a2, D0, P2/4\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleGraphicsControl/AppleGraphicsControl-3.28.4/src/AppleMuxControl/kext/GPUPanic.cpp:170

Backtrace (CPU 2), Frame : Return Address

0xffffff80bc8daa80 : 0xffffff8011baeb0d

0xffffff80bc8daad0 : 0xffffff8011ce8653

0xffffff80bc8dab10 : 0xffffff8011cda07a

0xffffff80bc8dab80 : 0xffffff8011b5bca0

0xffffff80bc8daba0 : 0xffffff8011bae527

0xffffff80bc8dacc0 : 0xffffff8011bae373

0xffffff80bc8dad30 : 0xffffff7f92fa583d

0xffffff80bc8dad90 : 0xffffff7f93c8b441

0xffffff80bc8dae50 : 0xffffff7f93d571ca

0xffffff80bc8dae90 : 0xffffff7f93d57235

0xffffff80bc8daf10 : 0xffffff7f94d107f0

0xffffff80bc8db030 : 0xffffff7f93d78d35

0xffffff80bc8db050 : 0xffffff7f93c92048

0xffffff80bc8db100 : 0xffffff7f93c8fa84

0xffffff80bc8db2f0 : 0xffffff7f93c914c1

0xffffff80bc8db3c0 : 0xffffff7f93edc58e

0xffffff80bc8db4a0 : 0xffffff7f93ed9b2e

0xffffff80bc8db510 : 0xffffff7f93eda799

0xffffff80bc8db580 : 0xffffff7f93edadce

0xffffff80bc8db6b0 : 0xffffff7f93edb799

0xffffff80bc8db7e0 : 0xffffff7f93f0b9cb

0xffffff80bc8db820 : 0xffffff7f93f0c6bd

0xffffff80bc8db860 : 0xffffff7f93f062e2

0xffffff80bc8db9d0 : 0xffffff7f93f06b71

0xffffff80bc8dba10 : 0xffffff7f93f0283d

0xffffff80bc8dba40 : 0xffffff7f93ee6a85

0xffffff80bc8dba80 : 0xffffff801228779c

0xffffff80bc8dbae0 : 0xffffff80122859c0

0xffffff80bc8dbb30 : 0xffffff801228ecdf

0xffffff80bc8dbc70 : 0xffffff8011c94c64

0xffffff80bc8dbd80 : 0xffffff8011bb43ed

0xffffff80bc8dbdd0 : 0xffffff8011b8ebe5

0xffffff80bc8dbe50 : 0xffffff8011ba35ae

0xffffff80bc8dbef0 : 0xffffff8011cc17bb

0xffffff80bc8dbfa0 : 0xffffff8011b5c486

Kernel Extensions in backtrace:

com.apple.driver.AppleMuxControl(3.28.4)[EFC6EE53-4EB1-34F5-B6E4-43429F691B51]@0xffffff7f92f97000->0xffffff7f92fa9fff

dependency: com.apple.driver.AppleGraphicsControl(3.28.4)[B940D328-A2B1-3906-972C-289E86DFDE48]@0xffffff7f92f56000

dependency: com.apple.iokit.IOACPIFamily(1.4)[67079254-1B34-31D2-8C7B-B138E26BFDD8]@0xffffff7f92a81000

dependency: com.apple.iokit.IOPCIFamily(2.9)[5C9A453F-559B-3683-9E81-D288D13A33CE]@0xffffff7f92495000

dependency: com.apple.iokit.IOGraphicsFamily(530.14)[D44517BE-2B53-3BD5-826E-4E78B55E3B73]@0xffffff7f92c2e000

dependency: com.apple.AppleGraphicsDeviceControl(3.28.4)[E80DEB91-2401-31C2-901F-CA63B4342337]@0xffffff7f92f47000

com.apple.nvidia.classic.NVDAResmanTesla(10.0.4)[F8258F0F-61AD-30F4-BDD5-B18CCAAE535A]@0xffffff7f93c3a000->0xffffff7f93ea2fff

dependency: com.apple.iokit.IOPCIFamily(2.9)[5C9A453F-559B-3683-9E81-D288D13A33CE]@0xffffff7f92495000

dependency: com.apple.iokit.IONDRVSupport(530)[693B770C-4748-33DC-B497-CF8C103DDD0E]@0xffffff7f92f6d000

dependency: com.parrotgeek.NDRVShim(1)[408EA24C-230F-3FA4-8F74-1EA79ABDD3BD]@0xffffff7f93c37000

dependency: com.apple.iokit.IOGraphicsFamily(530.14)[D44517BE-2B53-3BD5-826E-4E78B55E3B73]@0xffffff7f92c2e000

com.apple.GeForceTesla(10.0.4)[426B2568-8B0A-372B-BB33-B421D942837A]@0xffffff7f93eae000->0xffffff7f93f6cfff

dependency: com.apple.iokit.IOPCIFamily(2.9)[5C9A453F-559B-3683-9E81-D288D13A33CE]@0xffffff7f92495000

dependency: com.apple.iokit.IONDRVSupport(530)[693B770C-4748-33DC-B497-CF8C103DDD0E]@0xffffff7f92f6d000

dependency: com.apple.iokit.IOGraphicsFamily(530.14)[D44517BE-2B53-3BD5-826E-4E78B55E3B73]@0xffffff7f92c2e000

dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.4)[F8258F0F-61AD-30F4-BDD5-B18CCAAE535A]@0xffffff7f93c3a000

com.apple.nvidia.classic.NVDANV50HalTesla(10.0.4)[5DCF031B-F81F-32A3-ADCD-18E16EAC7CF0]@0xffffff7f94bec000->0xffffff7f94e94fff

dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.4)[F8258F0F-61AD-30F4-BDD5-B18CCAAE535A]@0xffffff7f93c3a000

dependency: com.apple.iokit.IOPCIFamily(2.9)[5C9A453F-559B-3683-9E81-D288D13A33CE]@0xffffff7f92495000



BSD process name corresponding to current thread: Photos

Boot args: -no_compat_check
Click to expand...
Yep, that's actually a known hardware issue with that system. To repair it, you'll need to replace a capacitor on the GPU framebuffer power rail (C6950), and that will get the machine running without issue. The reason this happens when using the Photos app is because the Photos app makes the machine switch to its dedicated GPU. I've made a video of that repair on my YouTube channel:

 
  • Like
Reactions: webg3, ASentientBot, olad and 2 others
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back