Got a tip for us?
Let us know
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
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I don't agree, having a 3TB WD Black.
Otherwise: I'm not able to bring a HFS Backup image from TM on a APFS formatted partition without loosing the APFS format. It turns to HFS again. I think "This is the End, my only friend, the End".
But don't cry for me Argentina, my SL is still alive and kickin'...
Last edited:
Just use Mavericks and you'll be fine. It will run better even on external HDD connected via USB2.0.
It is useful for creating a patched system "from scratch". You have to get a prelinked kernel for your particular machine (in this case the MB4,1) from someone running the same -or very close- kernel version (build) for initial boot. That makes further replacements of KEXTs and plugins possible and eventually pre-linking your own kernel with the modifications.
Managed the same for my MacBookPro 5,2 ... however note that you might have to apply patches from the installer after the installation, as I was getting kernel panics.
Will now try to enable FileVault and pray it works !
Edit: it did work
Last edited:
Re-curring question, here's the link to the framework.OH my!
so, have anyone got the original frameworks?
or how can I solve this?
Dear friends! Yesterday I did the last security update on my MBP8,3, running 10.14.6. All was running perfectly. But after boot, my Mac was freezing near end of boot screen. I try to repatch with 1.3.3 and now it's in boot loop... Any ideas? Thanks a lot!
I'm trying to migrate from the unsupported GeForce 8800GT on my Mac Pro to a GTX780 with UEFI firmware. Another user here made the suggestion that I reinstall Mojave to build a system without the legacy GPU driver. Unfortunately, that is not working. When I run Mojave patcher and select 'install' it goes away for about five minutes and tells me there are no packages 'eligible for installation'. :-(. Is this expected? Do I really need to reformat and start over from scratch?
Saw some advice on the net about setting date, but it's already correct.
Saw some advice on the net about setting date, but it's already correct.
Last edited:
This is one of those rare moments when wrong is actually right. I mean you need to set a wrong date(to align with the installer date). I recently had a similar issues when trying to install a supported El Capitan.
Last edited:
You win the prize!
. The current date was causing a problem. I reset it back to the date I first used Mojave patcher and it worked fine. There was a recent warning about an expired Apple certificate, but I thought that was relative to new installation rather than re-installation. Apparently not.I'm happily running a re-flashed GTX780 now. I do notice that text display during UEFI preboot is very, very slow now. Not really a problem, but wondering if there's a workaround or fix available.
Last edited:
I had the same issue with Mojave... had to set a “wrong” date of 1st Jan 2019 in order to get the installer to work.
Wondering if the patched installer should set always a fixed date, then restore the date before restart so this stupid issue with the cert won’t happen. Perhaps even remove the cert date check.
If a potential dosdude’s patcher 1.3.4 to automatically sort this issue. Would solve a lot of problems and questions here.
Unfortunately, seems Catalina is quite clunky and definitely slower than Mojave. I’ll be staying with 10.14.x and wouldn’t recommend going higher with very old machines.
Last edited:
I installed the latest Legacy Video patch, and it works great 👍👍👍 , except when you right click icons in the dock as the pic attached. This only happens when an app is open and showed on screen. As you may notice some short of shadowing is being presented.
👍👍👍 , except when you right click icons in the dock as the pic attached. This only happens when an app is open and showed on screen. As you may notice some short of shadowing is being presented.Here too...
By the way, if anyone using the light mode wants just the Dock, Finder and menu bar into Dark mode:
Launch Terminal (located in /Applications/Utilities) and enter the following command:
sudo defaults write -g NSRequiresAquaSystemAppearance -bool Yes
Then logout or restart. Switch to Light mode. Only the "weird darkish mode" will be changed by black mode.
-> This is an excerpt from :
https://www.tekrevue.com/tip/only-dark-menu-bar-dock-mojave/
Mainly, whoever wants a Light Mode can have it working 99%, only the dock and top bar will be blank, but not “weird darkish grey”.
I currently prefer this mode to fully white or black and is better than the weird one.
By the way, if anyone using the light mode wants just the Dock, Finder and menu bar into Dark mode:
Launch Terminal (located in /Applications/Utilities) and enter the following command:
sudo defaults write -g NSRequiresAquaSystemAppearance -bool Yes
Then logout or restart. Switch to Light mode. Only the "weird darkish mode" will be changed by black mode.
-> This is an excerpt from :
https://www.tekrevue.com/tip/only-dark-menu-bar-dock-mojave/
Mainly, whoever wants a Light Mode can have it working 99%, only the dock and top bar will be blank, but not “weird darkish grey”.
I currently prefer this mode
to fully white or black and is better than the weird one.
Just installed the latest legacy video patch on a MBP 8.2 late 2009 (with faulty dGPU). Unfortunately I can only run in safe mode now. Won't boot in normal mode.
Try to find out now how to revert back to the former version.
Any help would be appreciated.
Try to find out now how to revert back to the former version.
Any help would be appreciated.
Did the repatch again from the install-USB. I assume it installs earlier versions again. Hoewever, this does not help. MBP boots, when the UI is partly loaded it hangs and reboots/shuts down.
If you've been using Time Machine on an APFS system volume, it seems possible to roll back to an earlier snapshot by booting the patcher USB stick. I did this successfully yesterday.
You just need to re-run the NVRAM command to disable the dGPU, shown on my dGPU disable instructions webpage.
WARNING! The latest legacy video patch has a major problem for users running Office 2011. While it fixes the grey menu which is great it breaks office 2011 (Word, Excel and Powerpoint from running.). You get these errors upon launch. Reinstalling the USB patcher legacy video patch doesn't fix the issue.
"Microsoft Word cannot be opened because of a problem.
Check with the developer to make sure Microsoft Word works with this version of macOS. You may need to reinstall the application. Be sure to install any available updates for the application and macOS."
Click Report to see more detailed information and send a report to Apple.
Anyone have a fix? Bunch of Mac Minis that I applied the video patcher to now all messed up and won't launch Office 2011 and can't roll back.
Process: Microsoft Word [1104]
Path: /Applications/Microsoft Office 2011/Microsoft Word.app/Contents/MacOS/Microsoft Word
Identifier: com.microsoft.Word
Version: 14.7.7 (14.7.7)
Build Info: Unknown-170905~0
Code Type: X86 (Native)
Parent Process: ??? [1]
Responsible: Microsoft Word [1104]
User ID: 505
Date/Time: 2019-11-03 11:53:38.034 -0500
OS Version: Mac OS X 10.14.6 (18G103)
Report Version: 12
Anonymous UUID: 40720028-08CF-9565-779F-D47037CCF7EF
Time Awake Since Boot: 1200 seconds
System Integrity Protection: disabled
Crashed Thread: 0
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
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/CoreGraphics.framework/Versions/A/CoreGraphics
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: mach-o, but wrong architecture
"Microsoft Word cannot be opened because of a problem.
Check with the developer to make sure Microsoft Word works with this version of macOS. You may need to reinstall the application. Be sure to install any available updates for the application and macOS."
Click Report to see more detailed information and send a report to Apple.
Anyone have a fix? Bunch of Mac Minis that I applied the video patcher to now all messed up and won't launch Office 2011 and can't roll back.
Process: Microsoft Word [1104]
Path: /Applications/Microsoft Office 2011/Microsoft Word.app/Contents/MacOS/Microsoft Word
Identifier: com.microsoft.Word
Version: 14.7.7 (14.7.7)
Build Info: Unknown-170905~0
Code Type: X86 (Native)
Parent Process: ??? [1]
Responsible: Microsoft Word [1104]
User ID: 505
Date/Time: 2019-11-03 11:53:38.034 -0500
OS Version: Mac OS X 10.14.6 (18G103)
Report Version: 12
Anonymous UUID: 40720028-08CF-9565-779F-D47037CCF7EF
Time Awake Since Boot: 1200 seconds
System Integrity Protection: disabled
Crashed Thread: 0
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
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/CoreGraphics.framework/Versions/A/CoreGraphics
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: mach-o, but wrong architecture
I'm seeing the same DYLD "Wrong architecture" error after installing the latest Legacy Video patch (8) this morning, when trying to run an old game, Snood. Haven't tried Office apps yet.
@tzmmtz
@dosdude1
The patched SkyLight binary is missing the 32-bit code (since it was taken from Catalina). It does work great for 64-bit programs I agree.
Patched version:
gfxshared$ file SkyLight
SkyLight: Mach-O 64-bit dynamically linked shared library x86_64
Original version:
A$ file SkyLight
SkyLight: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit dynamically linked shared library x86_64] [i386]
SkyLight (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64
SkyLight (for architecture i386): Mach-O dynamically linked shared library i386
A method that worked for me is to restore the old version of /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight from backup, and copy it to /Applications/Utilities/macOS Post Install.app/Contents/Resources/gfxshared on your USB install drive. Boot from that drive, reinstall "Legacy Video" and rebuild the cache.
@dosdude1
The patched SkyLight binary is missing the 32-bit code (since it was taken from Catalina). It does work great for 64-bit programs I agree.
Patched version:
gfxshared$ file SkyLight
SkyLight: Mach-O 64-bit dynamically linked shared library x86_64
Original version:
A$ file SkyLight
SkyLight: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit dynamically linked shared library x86_64] [i386]
SkyLight (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64
SkyLight (for architecture i386): Mach-O dynamically linked shared library i386
A method that worked for me is to restore the old version of /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight from backup, and copy it to /Applications/Utilities/macOS Post Install.app/Contents/Resources/gfxshared on your USB install drive. Boot from that drive, reinstall "Legacy Video" and rebuild the cache.
Did this. But also needed to remove AMDRadeonX3000.kext again from /System/Library/Extenions, followed by the touch-command. Mojave now runs again, however the Patch Updater again comes with the message there is a new version of the Legacy Video Card Patch. It looks like another version, because the description mentions more changes, but I think I will skip this one for now.