macOS 10.14 Mojave on Unsupported Macs Thread

[TheSkywalker77]

It's installing on my Mac Mini (mid 2010) and it seems frozen on "16 minutes remaining". I've tried moving the mouse cursor and it's frozen. The machine was converted to APFS a few months ago. Should I just let it run through and hope it goes through it and finishes installing? Or something else?

EDIT: It was just taking longer than I thought (it sat there for about 15 mins). Booting into the operating system right now!

 

[AnonMac50]

Here's a grim prediction about macOS 10.15, macOS updates, macOS installers, and macOS patchers. Next year, when Apple introduces macOS 10.15, the following things relating to macOS updates, macOS installers, and macOS patchers will have changed:

• There will no longer be downloadable macOS installers
• There will no longer be macOS installer partitions
• There will no longer be downloadable macOS updates
• All updates will be done from System Preferences
• All reinstalls will be done from macOS Recovery or macOS Internet Recovery

The removal of access to the macOS installation and update files will make macOS patching much more complicated if not impossible. If someone has any thoughts on this, reply to this post. Remember, this is just my prediction but with updates in macOS 10.14 being in System Preferences and downloadable installers no longer being available on the 10.14 App Store, this looks like it's an unavoidable future. (Mention me in replies.)

I was telling my friend something similar the other day.

this sounds about right

i’d add that by 10.16 or 10.17

macos wont run without a t2 chip

Probably a later version considering that not even all current models have a T2 chip. Maybe 10.18 or 10.19. I do believe that T2 chips will eventually come with all Macs and will prevent any System modifications whatsoever by using hardware instead of software to inforce intense security which will most likely include a macOS version iBoot and System file and boot file checking and hardware encryption.

I reckon if the T2 is required, then it would be about 5-7 years after the last non-T2 is sold (if Apple still decides when to not support a Mac based on its obsolete/vintage status.

 

[0403979]

I was telling my friend something similar the other day.





I reckon if the T2 is required, then it would be about 5-7 years after the last non-T2 is sold (if Apple still decides when to not support a Mac based on its obsolete/vintage status.

I think all Macs without a T2 chip will be updated to include one or be removed from Apple’s lineup within the next two years, but we’ll see.

 

[MoHaya]

I dont know if any one has come across this or not, but I'll ask anyways

I have 2 2008 Mac Pros both running Mojave on my secondary drives, everything works fine except I'm getting GUI artifacting and glitches with one of my GPUs, GTX 660 2gb. The other Mac Pro's GPU which is a GTX 760 4gb works perfectly, Prior to the 760 4gb I had a different 660 2gb in that machine with the same issue. So now I know that theres nothing wrong with both of my 660s and the problem is with Mojave.

According to dosdude GUI artifacting and glitches should only happen with NonMetal Fermi based or prior GPUs, so I dont know why I'm getting this with Kepler Cards on Mojave
[doublepost=1535048690][/doublepost]

I dont know if any one has come across this or not, but I'll ask anyways

I have 2 2008 Mac Pros both running Mojave on my secondary drives, everything works fine except I'm getting GUI artifacting and glitches with one of my GPUs, GTX 660 2gb. The other Mac Pro's GPU which is a GTX 760 4gb works perfectly, Prior to the 760 4gb I had a different 660 2gb in that machine with the same issue. So now I know that theres nothing wrong with both of my 660s and the problem is with Mojave.

According to dosdude GUI artifacting and glitches should only happen with NonMetal Fermi based or prior GPUs, so I dont know why I'm getting this with Kepler Cards on Mojave

Im still on Developer Preview 4, dose any one know if latter versions of Mojave Beta fixed this? The glitches are not present all the time, they start on their own but when I restart the machine they are fixed temporarily but start up again at a later time

 

[pkouame]

I think all Macs without a T2 chip will be updated to include one or be removed from Apple’s lineup within the next two years, but we’ll see.

Yes - part of the roadmap - accounts for all those BridgeOS (the OS running on the T2) messages in our logs...

 

[visberry]

@visberry can send that though. He has a supported Mac that will get no suspicion.

I have sent many pics and a screen recoding- response saying "we are working on the new information that you have provided, thanks for your assistance. We will be in touch."
[doublepost=1535052697][/doublepost]By the way, here is the response, timely fashion.

 

[jackluke]

I have sent many pics and a screen recoding- response saying "we are working on the new information that you have provided, thanks for your assistance. We will be in touch."
[doublepost=1535052697][/doublepost]By the way, here is the response, timely fashion.

Thank you, if this conversation with them will continue I'd suggest you to tell that you noticed a less brighter transparent Finder menu bar than High Sierra, ask them if could add only in Mojave "light mode" less grey translucent color tone and make opacity close to a white transparency, pointing out that menu bar transparency is faded in comparison to High Sierra light mode.

I recall you also that "dark mode - Finder menu bar" was already present in High Sierra with the function in System Preferences/ General (pane): "Use Dark Menu Bar and Dock."

So again point out that dark mode menu bar in Mojave is already fine as High Sierra one.

 

[visberry]

Thank you, if this conversation with them will continue I'd suggest you to tell that you noticed a less brighter transparent Finder menu bar than High Sierra, ask them if could add only in Mojave "light mode" less grey translucent color tone and make opacity close to a white transparency, pointing out that menu bar transparency is faded in comparison to High Sierra light mode.

I recall you also that "dark mode - Finder menu bar" was already present in High Sierra with the function in System Preferences/ General (pane): "Use Dark Menu Bar and Dock."

Yep, I will do. You submitted one, right? One of ours will be duped. Could be mine or yours once they identify it is the same issue.

 

[jackluke]

Yep, I will do. You submitted one, right? One of ours will be duped. Could be mine or yours once they identify it is the same issue.

No I didn't bug reported to them the grey finder menu bar in light mode. I meant I never encountered that on supported Mac or if noticed just for less than one sec, no material time to take a snapshot.

If I'm not wrong your menu bar issue occurred on MacBook Pro mid 2012 with IntelHD4000 and that was your friend's laptop, anyway we could have much support if someone will report the menu bar grey bug from a Mac Pro 2010 or 2012 with an unsupported Metal Video Card Nvidia or IntelHD3000 or AMD/ATI with QE/CI at least.

I think if they make the Light Finder menu bar much closer to white, it could work for anyone, with enough luck. Or in worst case we'd have a whiter non-transparent Finder menu bar, but at least we have translucent dock and other transparencies somewhere.

 

[Tuli]

I dont know if any one has come across this or not, but I'll ask anyways

I have 2 2008 Mac Pros both running Mojave on my secondary drives, everything works fine except I'm getting GUI artifacting and glitches with one of my GPUs, GTX 660 2gb. The other Mac Pro's GPU which is a GTX 760 4gb works perfectly, Prior to the 760 4gb I had a different 660 2gb in that machine with the same issue. So now I know that theres nothing wrong with both of my 660s and the problem is with Mojave.

According to dosdude GUI artifacting and glitches should only happen with NonMetal Fermi based or prior GPUs, so I dont know why I'm getting this with Kepler Cards on Mojave
[doublepost=1535048690][/doublepost]

Im still on Developer Preview 4, dose any one know if latter versions of Mojave Beta fixed this? The glitches are not present all the time, they start on their own but when I restart the machine they are fixed temporarily but start up again at a later time

I'm running a 2008 Mac Pro with a GTX 680 2GB. I have run all the developer previews but haven't noticed any artefacts.

 

[pkouame]

I'm running a 2008 Mac Pro with a GTX 680 2GB. I have run all the developer previews but haven't noticed any artefacts.

Same here.

 

[the.burn]

Yeah I know about that app...it just doesn't "stick" to Intel HD...

It does
You just need to install the correct release
E.g. I'm using 2.4.4i, which is build to force integrated always.

 

[TimothyR734]

Tenth seed of iOS 12 /PB8 is out I wonder if another developers beta of Mojave will follow

 

[the.burn]

Dear all,
I maneuvered myself into some inconvenience
I've read some post ago that sb talked about a Nightshift patch, which he applied successfully.
So, I searched for that patch and installed it to my Mojave OS on my MBP 2010 15".

Nightshift was working after that, but Home.app did not, as CoreBrightness.framework was modified by the patch and now Home is angry about that:

Dyld Error Message:
Library not loaded: /System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/A/CoreBrightness
Referenced from: /System/iOSSupport/System/Library/PrivateFrameworks/AccessibilityUtilities.framework/AccessibilityUtilities
Reason: no suitable image found. Did find:
/System/Library/PrivateFrameworks/CoreBrightness.framework/CoreBrightness: mach-o, but not built for iOSMac
/System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/A/CoreBrightness: mach-o, but not built for iOSMac
/System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/A/CoreBrightness: mach-o, but not built for iOSMac

Now I wanted to revert the framework back to its unmodified original, the patch made a backup of the CoreBrightness.framework file(!).
Unfortunately, the _CodeSignature was not backed up, as I already issued here: https://github.com/aonez/NightShiftPatcher/issues/3
Without a correct signing, Finder crashes repeatedly...

So, I copied the framework file and the _CodeSignature from my High Sierra drive.
This makes Finder and macOS itself "stable" again, but since it is the old framework file, it has not the features Home.app needs:
"iOSMac" compatibility

Long story short:
Can sb provide my the CoreBrightness framework from the Mojave installation?
It is stored here:
/System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/A/
I assume that it would be best to get all the files in this directory...

I have a MacBook Pro 2010 15", which is MBP 6,2.
Do I need the files from an exact same versioned machine or can anybody running Mojave provide the files to me?

Thank you sooo much

 

[pkouame]

I dont know if any one has come across this or not, but I'll ask anyways

I have 2 2008 Mac Pros both running Mojave on my secondary drives, everything works fine except I'm getting GUI artifacting and glitches with one of my GPUs, GTX 660 2gb. The other Mac Pro's GPU which is a GTX 760 4gb works perfectly, Prior to the 760 4gb I had a different 660 2gb in that machine with the same issue. So now I know that theres nothing wrong with both of my 660s and the problem is with Mojave.

According to dosdude GUI artifacting and glitches should only happen with NonMetal Fermi based or prior GPUs, so I dont know why I'm getting this with Kepler Cards on Mojave
[doublepost=1535048690][/doublepost]

Im still on Developer Preview 4, dose any one know if latter versions of Mojave Beta fixed this? The glitches are not present all the time, they start on their own but when I restart the machine they are fixed temporarily but start up again at a later time

My GTX 680 has been rock solid on all Mojave betas (same pro 3.1) And the 660 vs 680 are SO similar (almost the card I bought) Pretty weird. The fact that it glitches over time may indicate some sort of hardware issue. What exactly are the UI glitches you are experiencing? This forum is getting confusing with all the various types of glitches being discussed ...

 

[TimothyR734]

Dear all,
I maneuvered myself into some inconvenience
I've read some post ago that sb talked about a Nightshift patch, which he applied successfully.
So, I searched for that patch and installed it to my Mojave OS on my MBP 2010 15".

Nightshift was working after that, but Home.app did not, as CoreBrightness.framework was modified by the patch and now Home is angry about that:

Dyld Error Message:
Library not loaded: /System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/A/CoreBrightness
Referenced from: /System/iOSSupport/System/Library/PrivateFrameworks/AccessibilityUtilities.framework/AccessibilityUtilities
Reason: no suitable image found. Did find:
/System/Library/PrivateFrameworks/CoreBrightness.framework/CoreBrightness: mach-o, but not built for iOSMac
/System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/A/CoreBrightness: mach-o, but not built for iOSMac
/System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/A/CoreBrightness: mach-o, but not built for iOSMac

Now I wanted to revert the framework back to its unmodified original, the patch made a backup of the CoreBrightness.framework file(!).
Unfortunately, the _CodeSignature was not backed up, as I already issued here: https://github.com/aonez/NightShiftPatcher/issues/3
Without a correct signing, Finder crashes repeatedly...

So, I copied the framework file and the _CodeSignature from my High Sierra drive.
This makes Finder and macOS itself "stable" again, but since it is the old framework file, it has not the features Home.app needs:
"iOSMac" compatibility

Long story short:
Can sb provide my the CoreBrightness framework from the Mojave installation?
It is stored here:
/System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/A/
I assume that it would be best to get all the files in this directory...

I have a MacBook Pro 2010 15", which is MBP 6,2.
Do I need the files from an exact same versioned machine or can anybody running Mojave provide the files to me?

Thank you sooo much

/System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/A/ this is not the original but it should work or at least bring back night shift

 

[the.burn]

/System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/A/ this is not the original but it should work or at least bring back night shift

Thanks!
Will try
Honestly, a working Home.app is more important to me than Nightshift, as I'm a longterm Flux user

 

[TimothyR734]

Thanks!
Will try
Honestly, a working Home.app is more important to me than Nightshift, as I'm a longterm Flux user

Well I hope someone does have the original core brightness for you as mine is the one I copied for you> another nice little app I use instead of flux is shifty when you turn on night shift it will switch to dark mode at night

 

[the.burn]

Wuhuuu
Thank you, Home is running fine

Ahh shifty is a nice tipp! One of the reasons why I was not comfortable with Night Shift instead of flux was the inability of automatic dark mode activation...

 

[flygbuss]

I have been using Dark Reader on Mojave for both Chrome and Firefox for about 2 months now, its not perfect but close enough.

https://darkreader.org/

For chrome you still need a separate home page dark theme which chrome offers on their theme extensions page

I have 'Native Dark' as a firefox add-on and it matches perfectly with mojaves dark mode.

 

[TimothyR734]

Wuhuuu
Thank you, Home is running fine

Ahh shifty is a nice tipp! One of the reasons why I was not comfortable with Night Shift instead of flux was the inability of automatic dark mode activation...

Your welcome If you decide to try shifty check out the preferences to set dark mode

 

[the.burn]

Your welcome If you decide to try shifty check out the preferences to set dark mode

Nice, Shifty and the Nightshift patch together are a real alternative to flux I think when I update my High Sierra in October I will switch to this combination
Until today I had no idea that Nightshift can be enabled on my MBP... Github and its users are gods

 

[TimothyR734]

Nice, Shifty and the Nightshift patch together are a real alternative to flux I think when I update my High Sierra in October I will switch to this combination
Until today I had no idea that Nightshift can be enabled on my MBP... Github and its users are gods

Shifty is in beta phase to just like Mojave so you might experience a few hiccups but for the most part it works well
[doublepost=1535062100][/doublepost]

Nice, Shifty and the Nightshift patch together are a real alternative to flux I think when I update my High Sierra in October I will switch to this combination
Until today I had no idea that Nightshift can be enabled on my MBP... Github and its users are gods

Here is the CoreBrightnes for High Sierra just follow the same steps as Mojave and Thanks to jackluke

 

[Macschrauber]

made another find regarding HD5xxx and HD6xxx and legacy video:

Mac Pro 3.1 and a HD5770

when legacy video patch is installed then I have seen that

AMDRadeonX3000.kext is loaded

wtf !?

so disabling AMDRadeonX3000.kext just by renaming it to AMDRadeonX3000.kex

and

sudo kextcache -I /

and rebooting

cured the trail glitches without re-installing

doesn't bring OpenGL and such, but better disabling x3000 than a re-install

 

[Badruzeus]

I have 2 2008 Mac Pros both running Mojave on my secondary drives, everything works fine except I'm getting GUI artifacting and glitches with one of my GPUs, GTX 660 2gb.

Strange! :O This Kepler graphics should to be natively supported under Mojave.

1st, plz make sure that nvAccelerator is properly loaded //Terminal: $

kextstat | egrep "GeForce|NVD|IOAccel"

2nd, rebuild prelinkedkernel, kernelcache && dyld.. //with SIP: Disabled.
(no graphics acceleration enabled w/o these, sometimes they are not rebuilt correctly for unknown reason)

- Boot to Recovery, Terminal: csrutil disable
- Boot to Desktop, Terminal: 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
- Re enable SIP within Recovery environment: csrutil enable

3rd, the last.. is Apple bugs. No idea with this one; FYi I got no fully graphics acceleration with my Fermi Graphics (GF) since 10.14 Beta 5: but only CI (Core Imaging) without Quatz Extreme (QE), native "GeForce - NVDAGF100Hal - NVDAResman - IOAccelerator" all are properly loaded though.

#EDIT: Also try using more recents or even latest Mojave Beta release.