I just wouldn’t recommend it because it is a beta software and it perhaps would transfer incompatible files or something and create a problem. It should work fine but still.
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 just wouldn’t recommend it because it is a beta software and it perhaps would transfer incompatible files or something and create a problem. It should work fine but still.
Good point Julian, so far most of the apps from HS work pretty well, I've not really had any issues with any PrimeTime apps aside from Google Chrome, Onyx has an update scheduled with Fall release & Photo's not finding Photo Library.
Last edited:
yes same here with th AppStore, however i think it’s only the first tab that is crashing. If you manage to quickly change the tab while it is still loading it doesn’t crash.
I haven’t tried the procedure myself but as soon as the UI glitches are sorted out (hopefully they will be soon) I will upgrade since it’s the only problem with patched Mojave on a MacBook7,1 (that’s a mid 2010, the last of the polycarbonate MacBooks btw. I have upgraded it with an SSD and 16GB of ram though. I rather stupidly damaged some screws and stuff when I installled a dual drive bracket but the exterior is mostly in good condition. I ordered some replacement screws just in case I have to replace a couple of them one day.).
[doublepost=1532291683][/doublepost]
That sounds like it’s a beta bug to me and not a patched system bug. Sounds incredibly weird to be the result of a patch or of unsupported hardware.
Re a fix for the 'DoubleBoot'
1) did you mean - S / L / UserEventPlugins/com.apple.telemetry - from High Sierra?
2) Can anyone else who has tried this confirm that it works?
Thanks
I took your advice but went one step further and redownloaded Mojave again before making a second attempt. That did the trick, so there must have been something corrupted with the first download of Mojave somewhere.
Anyway, I'm really happy that I can run Mojave on my Mid-2010 MPB. Performance is similar enough in what I use it for that I don't notice much of a difference, and having dark mode is a huge plus that I like. All of my apps except one work and I'm confident it will later down the line.
Thank you for all of the hard work put into patching this so it runs on older machines. Really appreciate it!
I must say that Migration assistant works really well in Mojave, I usually just use a cloned drive to selectively restore files, however I thought I'd give Migration a shot at it, so far pretty impressed with results of it. If you're using a lot of "4th" party apps check for updates.
Sorry this should have been a private message. Please ignore it.
Last edited:
None of my officially supported Macs running Mojave exhibit the App Store issue, but the patched one does. The temporary fix is indeed to quickly navigate away from the Discover tab as that is the one causing the crash once the content is loaded.
I really hope these minor annoyances and UI glitches will be sorted out. I just randomly bump into these issues (specific to unsupported Macs) here and there - none of them are real deal breakers in themselves, but taken together...
On Mojave beta 4 I don't have any App Store crashes neither on different unsupported Macs, and the front page with "video demo app" running in background doesn't give any issues, so could be the patching or the Video Card typology better/less supported in OpenGL rendering vs Metal adaptive contents.
It seems that Legacy IntelHD and Nvidia Video Cards react better than legacy AMD/ATI , just a supposition.
Last edited:
!!!!!!ANYONE NEEDING TO PATCH THEIR BACKLIGHT DO NOT PATCH IT
IT CAUSES MY iMAC 8,1 TO KERNEL PANIC
KEXTCACHE -I / DIDNT HELP
so dosdude1 PLEASE fix this the patch from 10.13 isn’t working and causing kernel panic
I can post verbose log if anyone want it
Otherwise everything works perfectly. Thanks bruh
EDIT: Now the backlight kext patch will not show up in the Patch Updater. Don’t use the High sierra patch but use the brightness slider instead: http://bergdesign.com/brightness/
IT CAUSES MY iMAC 8,1 TO KERNEL PANIC
KEXTCACHE -I / DIDNT HELP
so dosdude1 PLEASE fix this the patch from 10.13 isn’t working and causing kernel panic
I can post verbose log if anyone want it
Otherwise everything works perfectly. Thanks bruh
EDIT: Now the backlight kext patch will not show up in the Patch Updater. Don’t use the High sierra patch but use the brightness slider instead: http://bergdesign.com/brightness/
Last edited:
lol Same thing happened to me on my iMac8,1 it took me a few reinstalls to figure it out..
A final thought on whether or not you want to migrate, If you're considering Mojave as a Primary OS with Fall release, you can either migrate all you apps or selectively bring over your most important apps and test them, instead of waiting for Fall release & finding out some of your most important apps don't work on an unsupported Mac running Mojave. Option 2 is on a clean install of Mojave, reinstall primary app & test them independently. As @0403979 had stated earlier some incompatibly associated with beta of Mojave could pose some issues Migrating all your apps with these early beta's.
Edit:
For me personally running Mojave on an iMac 2010 with no graphic acceleration it's almost unusable as a Primary/Daily OS but interesting to test in preparation for my other Mac's.
Edit:
For me personally running Mojave on an iMac 2010 with no graphic acceleration it's almost unusable as a Primary/Daily OS but interesting to test in preparation for my other Mac's.
Last edited:
Hej, first: thanks a lot for all the work. I already used it from time to time and it helped me many times.
I have a MP 1,1 to 2,1 with capitan,a MP 6,1 with high sierra, a MBP 15 8,2 high sierra as well and a 13 MBP 8,1 (late 2011) which I was trying to use for mojave since it's the only mac I have with at least kinda the ability to make it work.
(I don't dare to touch the MP 6,1 because it's my working machine)
I connected a SATA SSD via thunderbolt to the MBP and followed the instructions coming with the patcher. After I realized I should better do a fresh install everything worked like a charme.
So far so good, after some testing I disconnected the drive, put it into the internal slot, closed the hatch and got a huge gpu bug. I can see it booting but as soon as it comes to the log in screen its looks like a broken gpu.
Everything is in purple or yellow or green and then the MBP starts beeping.
As soon as I take out the drive it works as it should and putting an other drive inside with a different OS works as well. What I tried so far: Re-running the patch (force re-building caches as well)
Installing everything again with the drive inside.
Nothing helps.. SIP is disabled.
Any ideas?
Thanks again!
I have a MP 1,1 to 2,1 with capitan,a MP 6,1 with high sierra, a MBP 15 8,2 high sierra as well and a 13 MBP 8,1 (late 2011) which I was trying to use for mojave since it's the only mac I have with at least kinda the ability to make it work.
(I don't dare to touch the MP 6,1 because it's my working machine)
I connected a SATA SSD via thunderbolt to the MBP and followed the instructions coming with the patcher. After I realized I should better do a fresh install everything worked like a charme.
So far so good, after some testing I disconnected the drive, put it into the internal slot, closed the hatch and got a huge gpu bug. I can see it booting but as soon as it comes to the log in screen its looks like a broken gpu.
Everything is in purple or yellow or green and then the MBP starts beeping.
As soon as I take out the drive it works as it should and putting an other drive inside with a different OS works as well. What I tried so far: Re-running the patch (force re-building caches as well)
Installing everything again with the drive inside.
Nothing helps.. SIP is disabled.
Any ideas?
Thanks again!
Attachments
Have you tried booting in recovery and running Terminal
fsck _fy
/sbin/fsck _fy
I had problems with one install, tried everything in last ditch effort, I booted in Recovery Mode & ran those commands, problem fixed, Disk Utility said Drive was ok prior to running Terminal.
Thanks you!
No haven’t tried it yet, but will certainly do.
Though I formatted the disc between my attempts two times and tried HFS+ and APFS..
No haven’t tried it yet, but will certainly do.
Though I formatted the disc between my attempts two times and tried HFS+ and APFS..
Open the system and reseat RAM. Common issue on these is the lower RAM slot failing, which causes these kinds of issues.
YES! It's been the RAM..
Awesome! Made my day! (Or night actually)
The beeping made me curious but I would have never thought about that since it worked with a different OS or with mojave from an external drive!
Thank you so much!
Awesome! Made my day! (Or night actually)
The beeping made me curious but I would have never thought about that since it worked with a different OS or with mojave from an external drive!
Thank you so much!
Last edited:
So as a short distraction, but still on topic, I decided to benchmark Mojave devb4 on macPro 3,1 + Nvidia GTX680.
Versus same machine running (low) Sierra.
I was particularly interested in the impact of the new metal frameworks (if any)
I used the latest Cinebench R15 (openGL and cpu) and GeekBench 4 (cpu and metal compute) on both.
Controlling conditions on both as best I could, running multiple times.
In short:
Mojave devB4 Cinebench R15
Sierra Cinebench R15
Mojave devB4 Geekbench 4 (metal compute perforamnce)
Sierra Geekbench 4 (metal compute performance)
Versus same machine running (low) Sierra.
I was particularly interested in the impact of the new metal frameworks (if any)
I used the latest Cinebench R15 (openGL and cpu) and GeekBench 4 (cpu and metal compute) on both.
Controlling conditions on both as best I could, running multiple times.
In short:
- My system runs as well if not slightly better than on Sierra (Cinebench R15 openGL and cpu scores are roughly the same)
- I noticed a consistent 2% to 3% boost in Geekbench 4 metal compute performance. Must be the new "full" metal frameworks.
- Given that this is all beta and that Nvidia drivers are not out yet - the straight out of the box performance bodes well for the (near) future. Not bad for a 10 year old desktop - scores are pretty decent
Mojave devB4 Cinebench R15
Sierra Cinebench R15
Mojave devB4 Geekbench 4 (metal compute perforamnce)
Sierra Geekbench 4 (metal compute performance)
This is not a fix for the double boot. This is a fix that @jackluke and I found to fix a grey screen + kernel panic on Penryn architecture systems. Totally unrelated problem.
I believe the double boot is a result of a corrupt/modified EFI partition. I had some troubles of my own (corrupted SSD, had to wipe and am reinstalling now) so I can't do any testing immediately but I should be running DP4 by midnight and can continue testing.
[doublepost=1532310850][/doublepost]
Same here. @jackluke, are you certain that this IOAccelerator replacement actually does anything? I tested it awhile back on my MB7,1 and nothing changed at all. I have full acceleration either way, and graphical glitches either way.
[doublepost=1532311163][/doublepost]Also, @jackluke, just a question I've been meaning to ask you for a while -- how long did it take you to find which file in UserEventPlugins was the culprit? Did you do something clever like a binary search or just a one-by-one replacement? Because that would suck.
EDIT: Just realized I mentioned you 3 times. I'm sorry, jackluke.
Last edited:
If AMD acceleration is not supported, I may just move to Liniux as this offers more support.
Oh you could not upgrade to Mojave. Sierra and High Sierra work just fine.
Well, I have more important things to worry about.. I found out sometime last week medical results that I have been diagnosed with cancer of the stomach.. so, really by the time Mojave comes out I may not even be here.