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 have a late model Mac mini 2009. It is on list to upgrade but been having some major issues.
I created a thumb drive of macOS el capitan and a thumb drive of Mojave patch version. I removed the apple drive and put in a Samsung ssd. I was able to install the el capitan but I can not do the Mojave. Won’t go in as upgrade or clean install. Tried extended journal and the AFS. Comes back and says it can’t be installed. Tried a repair, tried it again.
Spend hours and hours on this today.
Tomorrow I’m going to try and remove one of the ram sticks. If it fails, try this all on the stock drive. Correct me if I’m wrong, some SSDs just don’t work?
Ram is OWC and was in the machine.
I created a thumb drive of macOS el capitan and a thumb drive of Mojave patch version. I removed the apple drive and put in a Samsung ssd. I was able to install the el capitan but I can not do the Mojave. Won’t go in as upgrade or clean install. Tried extended journal and the AFS. Comes back and says it can’t be installed. Tried a repair, tried it again.
Spend hours and hours on this today.
Tomorrow I’m going to try and remove one of the ram sticks. If it fails, try this all on the stock drive. Correct me if I’m wrong, some SSDs just don’t work?
Ram is OWC and was in the machine.
see post 12229 from dosdude1. it may clear up the issue for you.
Last edited:
A bit of a random question for somebody who have an in-depth understanding of a startup chime. I don't remember my MacBook5,1 ever had a chime, it just squeaks. Everything is working great, so I am guessing the absence of a chime is not a fault in itself. So the question is: what makes the chime possible? A code in the firmware? Some excitation voltage applied to a particular pin on some chip?
P.S. Of course I tried NVRAM and SMC reset and some terminal commands, made sure that the system volume is at max before turning the machine on but nothing seems to help.
P.S. Of course I tried NVRAM and SMC reset and some terminal commands, made sure that the system volume is at max before turning the machine on but nothing seems to help.
Every mac does have a chime at power-on to check hardware components, and I can confirm that chime sound is embedded into EFI firmware as a simple binary sound file, and it can be heard only if the speaker is in working order with volume set to no-mute.
Here is a nice sample video:
My MacBook5,1 is definitely an odd beast. Speakers are working perfectly fine, I even run an original DVD Apple Hardware extensive test recently without any issues(there was 4HDD/11/40000000: SATA(0,0) alert - not sure what it means - SSD is working great at 3GB). Apple seems to say it is ok: https://support.apple.com/en-us/HT203648.
Anyway it seems that my MacBook5,1 proves that you don't need a chime for a perfectly functioning machine. Unless it is a part of an Apple humor to make a different sound(squeak) on some machines.
Last week I used Time machine to transfer all data from Macbook (early 2009, running patched Mojave) to Macbook Air (2015). I've had some problems, but you guys helped me and it works OK now.
I got one little problem though. SSD format in Macbook Air is HFS+ now. I think it would be better to convert it to apfs, but this option (convert to apfs) is grayed out in disk utilities (even if I boot from bootable USB Mojave drive) Does anyone know why this option is grayed out?
I got one little problem though. SSD format in Macbook Air is HFS+ now. I think it would be better to convert it to apfs, but this option (convert to apfs) is grayed out in disk utilities (even if I boot from bootable USB Mojave drive) Does anyone know why this option is grayed out?
If you mean running the latest beta on an unsupported Mac, yes I was able to install and run it.
However, graphics acceleration with OpenGL is still not working. Hoping it will be fixed on future betas or on the final GM release.
See my post --> https://forums.macrumors.com/thread...ed-macs-thread.2121473/page-487#post-27106357
Good luck if you want to try it on your device.
That's weird the only times I didn't heard a boot chime were when I had broken speakers, then replaced and heard again, and when had faulty GPU or faulty RAM, in that case I heard only tones/beeps . Anyway it seems with new streamline mac apple dropped the power-on chime sound: https://support.apple.com/HT202768
https://www.macrumors.com/2016/10/30/classic-startup-chime-new-macbook-pros/
Ok, it looks like I've heard the chime finally, it was not as pronounced(even at the max volume), but it definitely was there. Holding CMD+OPTION+P+R until computer restarts 4-5 times seems to do the trick. Looks like the machine is just getting tired of my silly face and refuses to greet me. "Here is a chime for you, just stop pushing my buttons you little baby."
No, I didn't know I should umount SSD...
I've just did it and SSD was smoothly converted to APFS.
Thanks!
Apart compatibility issues with some SSD controllers, Samsung should be fine, could be a RAM module, it's advisable on that machine to use 1066Mhz RAM frequency, higher could cause instability.
Last edited:
PRAM reset actually set the general Volume to their default values. Try to set Volume mute into Mojave then shutdown, at next power-on you will get no chime again, because it's stored in nvram.
Yes it is true. The machine is still very selective when it decides to chime(obviously it never chimes when the Volume is Mute). Even when unmuted the chime does not seem to be guaranteed. For example, I started machine by pressing the power button - no chime, shut down the machine, pressed the Option to get into boot menu, pressed power button - got chime. Truly has a mind of it's own unless I am still missing something.
Back at this for the past few hours.
So I did a fresh install of el capitan. Then confirmed the eprom chip and ran the update from page 1. Was a success, rebooted, all was good.Then setup a new usb of high Sierra and ran that as an upgrade. Went a quarter of the way and was there for a n bour, mouse was still moving. So I was thinking, maybe it has an issue converting it to apfs. So restarted, wiped the ssd, formatted it to apfs, installing high Sierra and same results. The ram is 1667. I'm going to try the one ram chip next and then I'm off to using the stock hdd.
Considering that 10.14.4 has firmware updates that should be spoiling the installation, I don't understand how anyone can be certain that OpenGL is really broken as opposed to the installation simply being prematurely truncated. Short of downloading the update as a stand-alone pkg file which could then be modified to skip the failing firmware update, I wouldn't put too much stock in a badly behaved failing update.
Lets see what the next Developer Preview brings. Hopefully it'll install without issue.
Technically your mini doesn't support APFS natively. All pre-2010 mac doesn't support until Sierra/HighSierra. APFS was introduced in beta stage with 10.12.6.
i took out 1 ram chip and was able to install high sierra..... Still an issue with mojave. Disc utility says I am on APFS now. That was fixed when I did the flash.
You should leave I guess at least a chip with 4 gb ram ddr3-1066 PC3-8500, higher frequency won't run stable, cause during installing Mojave its pkgs are all expanded temporary in RAM, then swapped to the SSD.
