macOS 10.14 Mojave on Unsupported Macs Thread

[avz]

Not using time machine: Maybe a case of my still limited understanding of APFS, but I thought that when using CCC (or perhaps not even CCC, but no time machine, that APFS inherently creates local snapshots.) But could be that CCC isn't creating snapshots -- if CCC is necessary for snapshot creation -- because it can see that this is a rotational disk, not an SSD. In any case still a bit puzzled that running "tmutil listlocalsnapshots /" produces command not found, as well as the recovery partition center panel missing any functional items. Wonder if the Patcher version of the recovery partition is limited in this regard.

>>"CCC and Time Machine are both capable of creating snapshots on a given APFS volume."

https://bombich.com/kb/ccc5/leveraging-snapshots-on-apfs-volumes

Sorry mate, I know nothing about CCC, so you are on your own. All I know is that APFS recovery and APFS snapshots(Time Machine) are fully functional on my late 2008 MacBook and my mid-2010 MBP. You are better off asking that Bombich guy as I am sure your issue has nothing to do with the "Unsupported Macs".

 

[joevt]

I'm using latest (as of today) Mojave on a Mac Pro 3,1 with a GTX680 under APFS, and generally things work very well. I'm super grateful for the patcher and all the great work here.

I'm looking for clues about poor performance of Parallels 14 (14.1.3) virtual machines, both Linux and Windows, under this regime. My VMs are insanely compute bound and glacially slow, like a key operation is taking 10 or a 100 times as long as it should. I say compute bound, because the VM CPU indicator goes on full for minutes at a time when the system is just doing housekeeping, but I suspect the hangup is connected with I/O. E.g., after a boot, the VM crawls as the guest does its chores. After being allowed to rest, it becomes usable, barely. Simple GUI stuff has poor response, like how it feels when you use screen sharing over a slow connection.. Yet purely compute activities like a GIMP filter seem to run about normal.

I've scoured the Parallels forums, and the web in general for clues and coming up empty-handed. Seen some complaining about very poor Parallels performance on Mojave back around 10.14.3 or so, but no resolutions, as if maybe it go fixed by a MacOS point release?

Anyone else using Parallels on legacy Macs seeing bad performance?

Suggestions for how to investigate what's holding things up?

I don't know about Parallels 14, but Parallels 15 has bad performance on MacPro3,1 since 10.14.4. You need to go back to 10.14.3.

Parallels support will not help us with the problem because Mojave and Catalina is not supported on the MacPro3,1. We need someone to reproduce the problem on a Mac that supports Mojave. I was not able to reproduce the problem on a Mac Mini 2018.

Apple hasn't released the source code for the kernel of 10.14.4 so we can't see what has changed there.

Maybe some kernel tracing can help find a problem? I haven't tried that yet. I would compare 10.14.4 with 10.14.3 to see if it shows a difference.

 

[Tyke666]

I must admit, it does "feel" more like a hardware fault than a software fault. I'll start looking at whats involved in replacing C7771. Interestingly, the post number you put on your reply doesn't show to me, but pasting your quote here has revealed it as #11995
Thanks again.

Well I had a look at C7771 and it was working at the correct voltage so that's not the issue.
Any problems remaining all still revolve around sleeping/waking.
The machine does not sleep or wake up properly. Putting it to sleep will result in a message similar to:
Stackshot Reason: Sleep transition timed out after 180 seconds while entering darkwake on way to sleep. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x74.

There are still the occassional random shutdowns while in use, but I have found that, if I keep the mains power on these are very infrequent (so long as I do not attempt to sleep the machine). Even with the mains lead in, I get a shutdown on booting the machine occassionaly, usually just as the apple logo appears. Then I reboot again and its fine.

Maybe it's just got old.

One other thing: If anyone has the 3 in one network/bluetooth/isight cable for this machine (Macbook Pro 17" mid 2009) I would be interested. I managed to slightly damage the connector while putting it back together and my network is present but intermittent and will only connect to 2.4GHz (not 5GHz like it used to). I can't seem to source one in the UK. I can always add a USB network adaptor cheaply but it would be nice to get the inbuilt one working again.

 

[0134168]

Hi there!

Anyone having this problem where QuickTime Player 7 Pro does not open?

Log reads:

Termination Reason: DYLD, [0x2] Wrong architecture

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
Library not loaded: /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight
Referenced from: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
Reason: no suitable image found. Did find:
/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight: mach-o, but wrong architecture
/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight: stat() failed with errno=1
/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight: mach-o, but wrong architecture


Ran a DDG search and found out that SkyLight is the new CoreGraphicsServices framework. Does that ring a bell? I'm not sure where the issue lies, though.

The computer is a MacBook Pro 17" Late 2011 running 10.14.6 with the AMD Radeon deactivated since it crapped out years ago.

Thanks in advance!

Exactly the same problem here. Could you solvii?

 

[dosdude1]

Exactly the same problem here. Could you solvii?

Re-install the Legacy Video Card Patch using Patch Updater, that should fix it.

 

[0134168]

Ok. I´m gonna try, Console logs grow up like bad plants. Also it seems I have some violations of Sandbox. Priviledge problems in some files. No big deal.

Must I use a boot usb? Or may I use the Patch Updater?

Thnx

 

[frilli]

Hi everyone, sorry for my ugly English
I have a Macbook Pro 15 end 2011 (version 8.2), with 1TB SSD (half Windows and half OSX), 16 GB Ram, I downloaded the latest version of DosDude Mojave Patche 1.3.7 and I have the following problem: The tool mi causes the boot USB to be created correctly, however, after loading the system and partitioned the disk, when I go to install Mojave, after 20/30 seconds it stops giving me the following error: "No package suitable for installation. Contact the supplier". ...... etc ...
I tried to redo the key by now 100 times, always the same problem ..... but if I use Catalina Patcher ..... no problem, it installs regularly .... how can I turn it?

P.S. I use Mojave 10.14.6 and I have changed several USB sticks.

Espandi
Comprimi

 

[Dayo]

No package suitable for installation etc

You used a Mojave installer you had on disk from before or around 24 October 2019 but the certificate in those have expired hence the message.

Get rid of that installer, use the Dosdude patcher to download a new one (Apple has since updated the certificates), create a new USB with this and it will install OK.

You can use your current installer by temporarily changing your computer system date before trying to install (trick the installer) but better to get a new installer with a valid certificate.

To trick the installer, open terminal after booting into the usb and enter "date -u 1010101019" without quotes.

This will change your system date to 10 Oct 2019.

As this is before the certificate expiry date, the installer will work and the date will be automatically fixed after installation is completed if you are connected to the web.

 

[hvds]

Not using time machine: Maybe a case of my still limited understanding of APFS, but I thought that when using CCC (or perhaps not even CCC, but no time machine, that APFS inherently creates local snapshots.) But could be that CCC isn't creating snapshots -- if CCC is necessary for snapshot creation -- because it can see that this is a rotational disk, not an SSD. In any case still a bit puzzled that running "tmutil listlocalsnapshots /" produces command not found, as well as the recovery partition center panel missing any functional items. Wonder if the Patcher version of the recovery partition is limited in this regard, and this is to be expected.

And, even if there were no local snapshots present, would think that command would at least be recognized. But maybe that's not the case when no snapshots are present.

>>"CCC and Time Machine are both capable of creating snapshots on a given APFS volume."

https://bombich.com/kb/ccc5/leveraging-snapshots-on-apfs-volumes

I am using time machine and CCC. In CCC, in the lower part of the sidebar to the left, it shows the connected volumes. When selecting an APFS volume, in the main part of the window it shows the available snapshots, together with an icon whether it was generated by time machine or CCC.
At the bottom of this main window, you can select whether CCC should produce snapshots or not. I kept it unselected.
I don't have or use a recovery partition - dosdude1's patcher on an USB volume/stick seems more capable to me. I always take it with me when traveling...

 

[RK78]

I am using time machine and CCC. In CCC, in the lower part of the sidebar to the left, it shows the connected volumes. When selecting an APFS volume, in the main part of the window it shows the available snapshots, together with an icon whether it was generated by time machine or CCC.
At the bottom of this main window, you can select whether CCC should produce snapshots or not. I kept it unselected.
I don't have or use a recovery partition - dosdude1's patcher on an USB volume/stick seems more capable to me. I always take it with me when traveling...

Thanks for pointing me to that. I think these screenshots explain why I'm not seeing any snapshots with CCC:

 

[hvds]

Thanks for pointing me to that. I think these screenshots explain why I'm not seeing any snapshots with CCC:
View attachment 879712 View attachment 879713 View attachment 879712

Right - I use the same CCC settings, snapshots disabled globally and per-volume.
My snapshots are all from time machine. I use TM both on external disks and for local snapshots. The latter I think is a good thing to do in any case.

 

[Dayo]

Recently updated to Mojave from HiSierra on a 3,1 and note there is a pending security update.
Is the process to do this on Mojave the same as outlined in Post 1 of the HiSierra thread?

https://forums.macrumors.com/thread...s-thread.2048478/?post=24638801#post-24638801

I.E., download, expand, edit, flatten, install and patch?

 

[hvds]

Recently updated to Mojave from HiSierra on a 3,1 and note there is a pending security update.
Is the process to do this on Mojave the same as outlined in Post 1 of the HiSierra thread?

https://forums.macrumors.com/thread...s-thread.2048478/?post=24638801#post-24638801

I.E., download, expand, edit, flatten, install and patch?

You can just do the upgrade via system settings->software updates, then run the latest Mojave patcher (1.3.7) on it. 1.3.7 includes important improvements, backported from Catalina.
Be sure to have a bootable USB installer on a stick/disk at hand for this. Use 1.3.7 to download the latest full installer of 10.14.6 (supplement 3 I think) and prepare the USB installer with it. Boot into this installer to apply the post install patches to your system.

 

[carlcaulkett]

@dosdude1 Hello, I am in danger of having messed up my Apple Mac Pro (early 2009). I have patched it a few times and it has been running 10.14.6 quite happily.

A couple of days ago, I tried to fit a new GTX680 GPU, and the machine froze on reboot after 60% of the Apple logo and progress bar.

I checked on another forum here and someone recommended I do the DosDude update again but this time without applying any post-install video patches.

I set that in motion earlier today and came back to find that the update had failed with a message about not finding a module, and prompting me to reboot. When I rebooted I was offered the choice of installing macOS again but this now fails because it doesn’t recognise my machine as a hardware compatible machine.

If I fit the new GTX680, I still get the 60% partial boot, and if I fit the old GPU my problems are as described just now.

i cannot figure what to do next. Can you or any other bright spark offer any advice?

 

[Dayo]

You can just do the upgrade via system settings->software updates

Thanks. I decided to follow the download, expand, edit, flatten, install and patch process from Post 1 of the HiSierra thread and up and running.

 

[carlcaulkett]

@dosdude1
If I fit the new GTX680, I still get the 60% partial boot, and if I fit the old GPU my problems are as described just now.

i cannot figure what to do next. Can you or any other bright spark offer any advice?

The situation has shifted a little in that I discovered that the power cables of the new GPU were not attached properly meaning that I needn't have tried the DosDude update again.

What seems clear is that for some reason the update did not complete properly, meaning that I can only run Safari from the recovery menu (the one with Time Machine, Install macOS, Disk Utility etc).

Disk Utility seems to show that my drives are still intact, but if I select Install New macOS, it will not let me, saying that either my GPU is not Metal compatible (it is!) or that I have File Vault installed (I don't!).

How can I get my machine to boot from my main drive again?

Before the power cable issue came to light, the startup keyboard shortcuts were not working. I'm going to try again and see if Save Mode or Command Line mode works. Wish me luck

 

[carlcaulkett]

I’ve managed to boot onto the USB drive again and to instigate another Mojave install. When I tried that just now I got the infamous ”No packages were eligible for install” message. After a quick DuckDuckGo I found a possible solution which involved resetting the date. I’m not entirely confident it will work, though, because in my case the date *was* correct so I ended up backdating.

Once again, any thoughts or suggestions are more than welcome.

 

[carlcaulkett]

Last time I tried the install it stopped after about two minutes. This time it’s been going for about half an hour, even thought the message says 25 minutes remaining, having started at 34 minutes ?

Maybe this time it will work??!!

 

[carlcaulkett]

The beast lives! The "No packages were eligible for install" problem that halted the macOS install were solved, it seems, by this fix https://techsparx.com/computer-hardware/apple/macosx/install-osx-when-you-cant.html.

As I said, the date appeared to be correct before, but I'm guessing the hardware change upset something or other.

Anyhow, the GTX680 is installed and is running perfectly happily!

 

[wire_]

No problem on my cMP3.1. However, you will have to be prepared to patch afterwards so have the latest USB Patcher to hand.

No prob with apply and use, but had to re-patch.

I keep a patcher partition on the same drive as the OS to easily Opt-choose at startup, so setup is self-contained and easy to update with new Apple installers. Much, much faster to update and boot than a flash drive.

 

[aflito]

does anyone has the link to dosdude`s imac 9.1 brightness patch? I lost my copy of it

I think it should be added to the OP for easier spot

 

[dosdude1]

does anyone has the link to dosdude`s imac 9.1 brightness patch? I lost my copy of it

I think it should be added to the OP for easier spot

If it's working for everyone, I may just release it via Patch Updater.

 

[aflito]

If it's working for everyone, I may just release it via Patch Updater.

TY for the reply! It worked fine for a long time on my machine, is there any logs/info I can share with you to be added on a `working machines list`?

The only thing that dint work was the sleep/awake, it always required to re-set the brightness value. other than that, it works fine

 

[frilli]

You used a Mojave installer you had on disk from before or around 24 October 2019 but the certificate in those have expired hence the message.

Get rid of that installer, use the Dosdude patcher to download a new one (Apple has since updated the certificates), create a new USB with this and it will install OK.

You can use your current installer by temporarily changing your computer system date before trying to install (trick the installer) but better to get a new installer with a valid certificate.

To trick the installer, open terminal after booting into the usb and enter "date -u 1010101019" without quotes.

This will change your system date to 10 Oct 2019.

As this is before the certificate expiry date, the installer will work and the date will be automatically fixed after installation is completed if you are connected to the web.

Thanks .... that was the problem !!!

 

[Flacko]

No prob with apply and use, but had to re-patch.

I keep a patcher partition on the same drive as the OS to easily Opt-choose at startup, so setup is self-contained and easy to update with new Apple installers. Much, much faster to update and boot than a flash drive.

It is useful to have the latest USB just in case you have a drive problem for example. Unless you have a working recovery partition the USB is a good failsafe. However, you suggestion is good for the times you just need to repatch.