macOS 10.14 Mojave on Unsupported Macs Thread

[TianjinMBP]

Thanks avz,
Seems like I just live with the scrolling. Not sure that I want to chance bricking the system just yet. It is a mid 2009 MacBook Pro with 8Gb and a 256Gb SSD so it runs Mojave reasonably well for a 10-year-old system, but the graphics is NVIDIA GeForce 9400M so not worth the risk of wrecking it given the repeated warnings in the video.

It's not the NVIDIA Graphics that he's talking about, it's the SATA/SATA Express chipset. See Pic. Mine shows the version he's talking about and shouldn't try the patch.

 

[sadboi]

Hello, I have a Macbook Pro 2009 Mid. I had Mojave 10.14.3 on it but I decided to swap drives. I installed a brand new SSD and installed 10.14.4 on it. The installation went fine , I launched the Post Install and did everything as said but when I booted there was a prohibiton sign. I reinstalled it, first-aided the disk a couple of times, made a new Installation USB. Now after 15-20 reboots it launches the OS but when I restart the problem is still present and I don’t know what is causing it. Can I get some help

 

[avz]

Hello, I have a Macbook Pro 2009 Mid. I had Mojave 10.14.3 on it but I decided to swap drives. I installed a brand new SSD and installed 10.14.4 on it. The installation went fine , I launched the Post Install and did everything as said but when I booted there was a prohibiton sign. I reinstalled it, first-aided the disk a couple of times, made a new Installation USB. Now after 15-20 reboots it launches the OS but when I restart the problem is still present and I don’t know what is causing it. Can I get some help

I am not an expert but from what I understand not all SSD's are working with Mac's. It has something to do with the controller that SSD has. Samsung SSD's seems to be OK but other brands can be hit and miss.

 

[olad]

Or perhaps, do a clone of the old drive to the new SSD (SuperDuper, Carbon Copy Cloner), then update that and check whether it is working correctly. If it boots Ok, update it (or do a clean install from dosdude1's patcher). If not, then something wrong with the new SSD drive.

 

[timidpimpin]

Anyone else getting lesser Bluetooth performance on Mojave? Under El Capitan with a Bluetooth 4.0 USB dongle it would remember my two different headphones, and I simply had to turn them on to use them. Now with Mojave I have to properly pair them every time.

This is on a Mac Mini 3,1 running 10.14.3 BTW. Not a big deal at all, but I just wanted to see if others had still working but degraded Bluetooth functionality. There are also occasional audio blips on YouTube videos that are not there on my phone.

Anyone?

 

[sadboi]

Hello, I have a Macbook Pro 2009 Mid. I had Mojave 10.14.3 on it but I decided to swap drives. I installed a brand new SSD and installed 10.14.4 on it. The installation went fine , I launched the Post Install and did everything as said but when I booted there was a prohibiton sign. I reinstalled it, first-aided the disk a couple of times, made a new Installation USB. Now after 15-20 reboots it launches the OS but when I restart the problem is still present and I don’t know what is causing it. Can I get some help

Also I can't open Recovery mode...

 

[webg3]

I guess that tool is for hack***osh and expressly for Intel Graphics, consider that the other forum has "fixed" Nvidia Tesla following the @ASentientBot guide.

Anyway even if IntelHD Graphics in OpenGL mode worked without any binary patch in Mojave, from .5 beta2 they have the exact same behavior of binary patched Nvidia Tesla.

I've tested IntelHD Arrandale and IntelHD3000, same noOpenGLaccel behavior of Nvidia 320M .

I understand, I'm on 10.14.3, I already tried 10.14.4 (I managed to get it working, but several bugs in Safari and Siri made me go back to 10.14.3).

The system is solid on 10.14.3, so for now I'll keep it up and follow up until when all problems are remedied in 10.14.5 (from what I've been reading, it's friendlier than 10.14.4), I can update quietly.

These artifacts in Intel Graphics / GeForce 320m do not bother me so much because I use the dark mode.

The @pkouame solution only uses AppKit removed from the Flat package, so I keep the menus transparent and something solid, with a bit of transparency in some parts of the system, much better than using no solution.

 

[TimothyR734]

Also I can't open Recovery mode...

open your terminal then open the zip file drop the install.sh in terminal follow the commands and it should there is also another one some pages back that is called boot recovery fix that works also if you are using APFS

 

[webg3]

Those who are in 10.14.3 and do not want to update more recommend removing Mojave from the update catalog, so in the terminal give the command:

sudo softwareupdate --set-catalog https: //swscan.apple.com/content/catalogs/others/index-10.13seed-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog.gz

If you want to go back do this:

sudo softwareupdate --set-catalog https: //swscan.apple.com/content/catalogs/others/index-10.14seed-10.14-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog.gz

'-)

"remove the spaces".

 

[jackluke]

I understand, I'm on 10.14.3, I already tried 10.14.4 (I managed to get it working, but several bugs in Safari and Siri made me go back to 10.14.3).

The system is solid on 10.14.3, so for now I'll keep it up and follow up until when all problems are remedied in 10.14.5 (from what I've been reading, it's friendlier than 10.14.4), I can update quietly.

These artifacts in Intel Graphics / GeForce 320m do not bother me so much because I use the dark mode.

The @pkouame solution only uses AppKit removed from the Flat package, so I keep the menus transparent and something solid, with a bit of transparency in some parts of the system, much better than using no solution.

View attachment 831920 View attachment 831921 View attachment 831922

If you use mainly the dark mode, just use the stock Appkit, CoreUI and HIToolbox and you will have an almost perfect dark mode. pkouame's HybridMode patch is very useful in light mode.

 

[sadboi]

open your terminal then open the zip file drop the install.sh in terminal follow the commands and it should there is also another one some pages back that is called boot recovery fix that works also if you are using APFS

I'm not using APFS

 

[pkouame]

If you use mainly the dark mode, just use the stock Appkit, CoreUI and HIToolbox and you will have an almost perfect dark mode. pkouame's HybridMode patch is very useful in light mode.

Yes - no need for any patches if you like in Dark Mode.

 

[jackluke]

Yes - no need for any patches if you like in Dark Mode.

I've tried for fun to compile and build the "flurry" but you know, it does work on any OSX except on 10.14.4 accelerated, I get instead of grey-screen of original flurry, a black screen. Don't know maybe my Xcode libraries are mismatched, infact I used Xcode 9 and apparently got very few warning messages and build succeeded, but I guess your porting of flurry will be better.

 

[pkouame]

Yes, Flurry works in non-GL-accelerated mode on .5b2 and beyond, just software render mode or CoreImage (I guess).

I've already tried as invited by Xcode to convert the .nib to UTF16 and to update the headermaps to the current coding, but same result one error only.

I do have in Xcode preferences the "Continue building after errors" checked of course.

I still get this one only error resulting in Build failed.

Spoiler: Flurry build failed with one error

ld: warning: ignoring file /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks//ScreenSaver.framework/ScreenSaver, missing required architecture x86_64 in file /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks//ScreenSaver.framework/ScreenSaver (2 slices)
Undefined symbols for architecture x86_64:
  "_OBJC_CLASS_$_ScreenSaverDefaults", referenced from:
      objc-class-ref in FlurryView.o
      objc-class-ref in PresetManager.o
  "_OBJC_CLASS_$_ScreenSaverView", referenced from:
      _OBJC_CLASS_$_FlurryView in FlurryView.o
  "_OBJC_METACLASS_$_ScreenSaverView", referenced from:
      _OBJC_METACLASS_$_FlurryView in FlurryView.o
  "_objc_msgSendSuper2", referenced from:
      -[FlurryView initWithFrame:isPreview:] in FlurryView.o
      -[FlurryView dealloc] in FlurryView.o
      -[FlurryView setFrameSize:] in FlurryView.o
      -[FlurryView startAnimation] in FlurryView.o
      -[FlurryView stopAnimation] in FlurryView.o
      -[MonitorCell dealloc] in FlurryView.o
      -[MonitorCell initWithIndex:] in FlurryView.o
      ...
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Tried to add from "Build Settings" the "Other Linker Flags" -v but still get almost the same build error.

I've thought that maybe Appkit and Foundation could be required to make the preference pane to work.
I got also the same error if I keep the pre-header Flurry_Prefix.

I have to say that I am using Xcode 10.1 from HighSierra 10.13.6 , so deployment target is 10.13 but noticed the source code is good to use until 10.8 or even 10.7 .

edit:
I was using the wrong SDKROOT ? Apparently not. Can't figure it out.

edit2:
Used Xcode 9.x and it worked.

I have a fully functioning "modern" build of Flurry. As I said before, it's best to start with a "clean" screen saver project template and add the bits of code and resources you need.

I just finished re-enabling a better Flurry "Screen Saver Options" panel. It works and one can tweak speed, threads and thickness as before. All I need to add are the color options.

While cleaning up some of this ancient GL, I was hoping to stumble on what breaks on our .4 + retro-patch configuration: nothing yet, except that I don't get a blank or grey screen - but totally black. So the custom build is changing something - but not there yet.

I also ran GL Profiler attached to the screensaver and the GL animation seems to be running with no errors. Like the functioning ones (Arabesque etc..)
[doublepost=1555176375][/doublepost]

I've tried for fun to compile and build the "flurry" but you know, it does work on any OSX except on 10.14.4 accelerated, I get instead of grey-screen of original flurry, a black screen. Don't know maybe my Xcode libraries are mismatched, infact I used Xcode 9 and apparently got very few warning messages and build succeeded, but I guess your porting of flurry will be better.

I use the latest Xcode (10.2) and play with targeting older platforms to see what falls out. Then I install the .saver on my patched .4 mbp 5,3 Preferences.

 

[K two]

THIS #14142
worked for me
[doublepost=1555078796][/doublepost]

Yes for me. …On three different Mac mini 3.1's Late 2009's

THIS #14142
worked for me

In the end, I believe Onyx cleared prior application states.
If I knew Terminal Commands, I may have been able to do the same

But in my three cases, all three mini's are running reliably

• Installed .4 over solid .3, then installed patch set from v.1.3.0 on USB installer. Reboot w/cache rebuild ran for 2 mins. KP'd while observing which screensavers went kaput in the Control Panel. Rebooted OK, so re-installed ALL of the recommended patches via the Patch Updater. Rebooted, ran Maintenance v.2.5.1 (Onyx w/o the esoterica). Mini3,1 8GB, HFS+SSD has been running w/ no random KP's for over 24 hrs. Sleep is good. News crashes every time. Flurry, Plasma and Flux savers are gone (OK in .3) but Watch OSX still lives. Safari and Numbers seem solid. 32 bit apps still kicking.

Thanks for your enthusiasm and help.

Initial observations - .4 has limits compared to .3, stability issues where iOS-ish apps are involved and obsolescence are obvious. Now looking for any real advantage for .4 over .3?

 

[TimothyR734]

I'm not using APFS

sudo nvram boot-args="-x" use this in the terminal to enable safe mode during boot up to return to normal boot up use this in terminal; sudo nvram boot-args=""

 

[pkouame]

• Installed .4 over solid .3, then installed patch set from v.1.3.0 on USB installer. Reboot w/cache rebuild ran for 2 mins. KP'd while observing which screensavers went kaput in the Control Panel. Rebooted OK, so re-installed ALL of the recommended patches via the Patch Updater. Rebooted, ran Maintenance v.2.5.1 (Onyx w/o the esoterica). Mini3,1 8GB, HFS+SSD has been running w/ no random KP's for over 24 hrs. Sleep is good. News crashes every time. Flurry, Plasma and Flux savers are gone (OK in .3) but Watch OSX still lives. Safari and Numbers seem solid. 32 bit apps still kicking.

Thanks for your enthusiasm and help.

Initial observations - .4 has limits compared to .3, stability issues where iOS-ish apps are involved and obsolescence are obvious. Now looking for any real advantage for .4 over .3?

View attachment 831931

My .4 KPs randomly too. I also noticed that it's while or after I play in Preferences with OpenGL based screen savers. I'm thinking there may be an issue with the retro-patched .4 ( ie. .4 with post-install .3 OpenGL and GPUSupport) It does get us up and running in accelerated mode on .4 though. So no big complaints, but .3 is the most stable and reliable patched configuration for now IMHO. Depends on what you do.

 

[avz]

Those who are in 10.14.3 and do not want to update more recommend removing Mojave from the update catalog, so in the terminal give the command:

sudo softwareupdate --set-catalog https: //swscan.apple.com/content/catalogs/others/index-10.13seed-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog.gz

If you want to go back do this:

sudo softwareupdate --set-catalog https: //swscan.apple.com/content/catalogs/others/index-10.14seed-10.14-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog.gz

'-)

"remove the spaces".

Would it be possible to get a Safari12.1 update while staying with 10.14.3?

P.S. I guess Safari12.1 is only available as part of the 10.14.4 update.

[doublepost=1555179668][/doublepost]

Yes - no need for any patches if you like in Dark Mode.

I am only using the dark mode but I like the translucency of the right-click menu's that I am getting with Hybrid patches.

 

[TimothyR734]

Would it be possible to get a Safari12.1 update while staying with 10.14.3?

P.S. I guess Safari12.1 is only available as part of the 10.14.4 update.

[doublepost=1555179668][/doublepost]

I am only using the dark mode but I like the translucency of the right-click menu's that I am getting with Hybrid patches.

https://mac.softpedia.com/get/Internet-Utilities/Safari.shtml don't really know if safari 12,1 for HS ill work but you can download the tech preview 12.2 which works better

 

[jackluke]

I've been playing with 10.14.5 DP2, and while I haven't made any significant progress, I noticed one really weird thing: My MacBook7,1's keyboard and touchpad now work without any USB patches, which hasn't been the case since High Sierra. Anybody else find this?

Edit: Same with iSight. Weird...

That's absolutely TRUE!

I had a backup of .5 beta2 IOUSB*.kext, checked their internal binaries compiled by apple on April 6th.
Replaced and kextcached, they work OOB with all external/internal USB devices (isight, bluetooth and so on).

 

[avz]

https://mac.softpedia.com/get/Internet-Utilities/Safari.shtml don't really know if safari 12,1 for HS ill work but you can download the tech preview 12.2 which works better

I actually downloaded Tech Preview 12.2 from the links posted by webg3 above, but it refuses to open it on 10.14.3. Plist file might need adjustment, I am not sure where though.
[doublepost=1555182986][/doublepost]

That's absolutely TRUE!

I had a backup of .5 beta2 IOUSB*.kext, checked their internal binaries compiled by apple on April 6th.
Replaced and kextcached, they work OOB with all external/internal USB devices (isight, bluetooth and so on).

Does it mean that we can use it on 10.14.3 to avoid using LegacyUSB kext? Would it be possible to upload it if the file is not too big?

 

[jackluke]

I actually downloaded Tech Preview 12.2 from the links posted by webg3 above, but it refuses to open it on 10.14.3. Plist file might need adjustment, I am not sure where though.
[doublepost=1555182986][/doublepost]

Does it mean that we can use it on 10.14.3 to avoid using LegacyUSB kext? Would it be possible to upload it if the file is not too big?

I cannot guarantee they will work on any legacy penryn cpu machine, I have only tested on machines natively APFS, but even if this is a future version, I guess if you chown/chmod and kextcache them correctly they could work even on 10.14.3 .
I can upload, they are relatively small.

 

[TimothyR734]

I actually downloaded Tech Preview 12.2 from the links posted by webg3 above, but it refuses to open it on 10.14.3. Plist file might need adjustment, I am not sure where though.
[doublepost=1555182986][/doublepost]

Does it mean that we can use it on 10.14.3 to avoid using LegacyUSB kext? Would it be possible to upload it if the file is not too big?

I have it on 10.14.2 seems to work fine
[doublepost=1555184396][/doublepost]I am really enjoy 10.14.4 on my MacBook I thought it was the 5,1 model but used this neat little app and found out it is the 5,2 model have full acceleration and the newest hybrid patches work great

 

[parrotgeek1]

That's absolutely TRUE!

I had a backup of .5 beta2 IOUSB*.kext, checked their internal binaries compiled by apple on April 6th.
Replaced and kextcached, they work OOB with all external/internal USB devices (isight, bluetooth and so on).

@dosdude1 weird!

 

[avz]

I have it on 10.14.2 seems to work fine
[doublepost=1555184396][/doublepost]I am really enjoy 10.14.4 on my MacBook I thought it was the 5,1 model but used this neat little app and found out it is the 5,2 model have full acceleration and the newest hybrid patches work great

Yeah, I did a mistake by downloading a High Sierra one.