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
What are you saying? Do you have gfx acceleration functioning on an Amd 6xxx card? What video card patch are you alluding to? Thanks!
but the thing is the dropdown isn't dropping down
i clicked on it and no models for me to choose
Hi there! I've managed to use the dosdude1 firmware patcher to enable NVMe booting. Wow--what a difference! It's breathed new life into my cMP 3,1.
I ended up getting a Samsung 970, which with my adapter reverts all the way back to PCIe 1.0, even in a 2.0 slot (Slot 1 or 2).
I'm able to manually enter a string of commands in terminal after each boot to force the slot to 2.0, but this caught my attention.
@dosdude1, please excuse what is probably a really dumb question, but is there a way to utilize your patcher to accomplish this? Older Gen 2 adapters are getting harder to come by--I'd imagine there are other users who might benefit from this...
I ended up getting a Samsung 970, which with my adapter reverts all the way back to PCIe 1.0, even in a 2.0 slot (Slot 1 or 2).
I'm able to manually enter a string of commands in terminal after each boot to force the slot to 2.0, but this caught my attention.
Code:
# Set Target Link Speed of MacPro3,1 slot 2 root port to 5GT/s
sudo setpci -s 00:1 CAP_EXP+30.w=2:F@dosdude1, please excuse what is probably a really dumb question, but is there a way to utilize your patcher to accomplish this? Older Gen 2 adapters are getting harder to come by--I'd imagine there are other users who might benefit from this...
In complete agreement, High Sierra works well on 2010-2011 iMac's, especially if you have an internal SSD in terms of performance. I went to HS on 2 iMac's, a 2010 & 2011, both of which are pretty stable. 2010 now has Mojave and will probably revert back to HS, as no GPU acceleration in either (2010 was test bed) it makes no sense to run a system without acceleration. Perhaps in the future someone will figure out a patch, doesn't seem likely though. It was an interesting journey with all the Mojave betas, the 1st thru the last, the good and not so good.
I don't have acceleration, I said that I don't have the sound or graphics issues that another iMac owner reported, my iMac is fully functional I can play videos in a normal way, no stuttering, or weird colours.
I converted my Macbook5,1 running High Sierra from HFS to APFS today (with the APFS ROM patch installed) using Disk Utility, in preparation for a Mojave install next week. At first it wouldn't boot; some research showed that although Disk Utility converted the file system, it didn't create a Preboot volume in the APFS container, which is required for booting. Doh! Not knowing how to fix this, I simply did a fresh High Sierra install and restored my Time Machine backup; all working now, booting natively with APFS.
A minor issue I've noticed is that I can't boot from the Recovery volume. It's present in the APFS container along with the main High Sierra volume, but it's not listed among the boot options when I hold down Option, and if I use Command-R it just goes to the circle with a bar through it. I do see another boot option called "EFI Boot", which doesn't work either (circle with bar). I don't know where this is coming from because I don't have a BOOT folder or any boot files in my EFI partition. Does anyone know how to fix these issues?
Thanks,
cinergi
A minor issue I've noticed is that I can't boot from the Recovery volume. It's present in the APFS container along with the main High Sierra volume, but it's not listed among the boot options when I hold down Option, and if I use Command-R it just goes to the circle with a bar through it. I do see another boot option called "EFI Boot", which doesn't work either (circle with bar). I don't know where this is coming from because I don't have a BOOT folder or any boot files in my EFI partition. Does anyone know how to fix these issues?
Thanks,
cinergi
Not an issue at the time, but I currently have a Mac Pro 3,1 with a Nvidia GTX 970 installed. I know the bootloader/boot menu is gone because it's a non-flashed GPU, but when the time comes to upgrade from High Sierra to Mojave, I can get into the USB Installer via Startup Disk. The problem arrives when macOS throws the File Logo with an X on it (Which I've experienced with BETA testing in the past with Mojave), where I can't install the patches because I can't get to the boot menu and back onto the Installer USB. What do I do at that point? Will I have to throw down the cap and put my old GPU back in and do it the good old fashion way? Or is there a trick to boot the system into the USB without having to waste time and possibly minimize the risk of breaking something.
The "Preboot" volume only gets put in the container after an install, and after you convert to APFS it shouldn't affect booting. I installed Mojave onto a HFS+ disk, then converted to APFS and booted back in without issues, as I have done may times. Right now the only disks in my APFS container is my main boot partition and the VM disk, and nothing is affected. When converting to APFS, I assume it creates an invisible Preboot partition which isn't visible until you run a reinstall on the disk or an update. I have done a lot of testing on this.
With the APFS patcher, you will not be able to have a bootable recovery partition. That's just the nature of working with things on unsupported devices. This shouldn't be an issue, since a bootable installer has all the same elements as a recovery partition. Your USB stick with High Sierra should be more than enough if you ever need to use a "recovery" feature.
The EFI Boot option is just an error in the code of the APFS Patcher according to @dosdude1, as said here. This is an arbitrary option and does not affect booting into APFS. Just select your main boot partition and everything will be smooth sailing, for the most part. Hope this helps!
Please read the guide, a 16GB or larger USB drive is required.but the thing is the dropdown isn't dropping down
Feature Request...... On MacBook Pro 8,2 (and other applicable machines) is it possible to add Continuity Activation Toolkit function to the Post Installer?
It seems to be working on MacBook Pro 8,2, if CAT is ran after install.
I use a 16gb drive with a 6.6gb partition for an El Capitan installer and an 8.29gb partition for Mojave, both installations work. Its just that 8gb drives only give you 7.75-ish gb actually to work with, which isn't big enough for the Mojave installer. The next size of flash drive is normally 16gb, so that is why its suggested to use a bigger than 8gb flash drive.
Well said, @Wooser. I couldn't agree more. It's been a delight using his patcher these last few years.
Hi, I have a Mac Pro 3.1 with a ATI Radeon HD 5870 GPU in, it runs High Sierra with Dosdudes Patcher, (many thanks) I know it won't run Mojave because it doesn't support Metal, but I am thinking of getting a new GPU, I am thinking a Nvidia Geforce GTX 680 for a Mac, will run Mojave with Dosdudes Patcher ?
Thanks Guys
Thanks Guys
The GTX 680 works great on the 3,1 running macOS Mojave which was installed using dosdudes amazing patcher.
Was anybody with a 17" MacBookPro5,2 2009 able to install Mojave onto an external USB drive?
I've successfully applied the APFS ROM patch to my machine, successfully created an APFS installer stick and booted from it. I've then installed Mojave onto a second USB stick for the purpose of testing and applied the post install patches. Result: Mojave will start to boot from that second USB stick, but gets stuck at waiting on <dict ID="0"><key>IOProviderClass<... (obviously its root device), no matter what filesystem I've chosen (I've tried both HFS+ and APFS).
I've successfully applied the APFS ROM patch to my machine, successfully created an APFS installer stick and booted from it. I've then installed Mojave onto a second USB stick for the purpose of testing and applied the post install patches. Result: Mojave will start to boot from that second USB stick, but gets stuck at waiting on <dict ID="0"><key>IOProviderClass<... (obviously its root device), no matter what filesystem I've chosen (I've tried both HFS+ and APFS).
First off, you should not be using APFS for your installer drive. Second, OS X is not designed to run off a USB flash drive. Use an external hard disk if you want to run it externally, and you'll have no issues.
Thanks! In my case, when I tried to "bless" the boot volume (Macintosh HD), the command gave an error that there's no Preboot volume present in the APFS container. Oddly, when I booted while holding down Option and manually selected the same boot volume, it booted fine. I don't know why. After my fresh install (with Preboot volume present), it still wouldn't boot initially but running "bless" worked this time and now it's fine.
Thanks for the info regarding the Recovery partition. You're right, the same functionality can be accomplished with an external USB drive; I just wanted to get it working if possible, just because.
-cinergi
Well, this has been "rehab the Mac 3,1" weekend in preparation for Mojave Monday. And sometimes you encounter a problem due to aging hardware. In this case, my problem appears to be a failing part of my fusion boot drive, specifically the 3 TB Seagate hard drive part of it. I replaced the SSD last year when SoftRAID (which managing a 4 drive RAID 5 of 6 TB drives) reported that the SSD was toward the end of its life. So I replaced it and rebuilt the fusion drive.
But yesterday I began the task of backing up the fusion boot to an external drive so that I could have a second backup (other than Time Machine). And just before doing the Carbon Copy Cloner task, I saw that a large (but not critical file) on my boot drive was suffering a -36 error when trying to copy it to the external volume. Carbon Copy confirmed that the section of the hard drive is bad and likely needs to be replaced. This 3 TB drive is the last of a group of four 3 TB drives that originally sat in an older Drobo before I replaced them with 4 Tb drives (which are still in operation). Over time, the 3 Tb drives began failing one by one and this one was the last one of that set. It's disappointing that this particular hard drive family didn't seem to last as long as some other drives I've bought in the past.
I'll have SoftRAID attempt to re-certify the drive today but it's pretty clear that I probably need to spend coin to replace it. Just another issue of trying to keep old hardware alive for one more season.
But yesterday I began the task of backing up the fusion boot to an external drive so that I could have a second backup (other than Time Machine). And just before doing the Carbon Copy Cloner task, I saw that a large (but not critical file) on my boot drive was suffering a -36 error when trying to copy it to the external volume. Carbon Copy confirmed that the section of the hard drive is bad and likely needs to be replaced. This 3 TB drive is the last of a group of four 3 TB drives that originally sat in an older Drobo before I replaced them with 4 Tb drives (which are still in operation). Over time, the 3 Tb drives began failing one by one and this one was the last one of that set. It's disappointing that this particular hard drive family didn't seem to last as long as some other drives I've bought in the past.
I'll have SoftRAID attempt to re-certify the drive today but it's pretty clear that I probably need to spend coin to replace it. Just another issue of trying to keep old hardware alive for one more season.
Strange, both my Mac mini's are able to see/connect to bluetooth devices after swapping cards. Do you have bluetooth available at all in system preferences? It could be one of your antennae connectors (most likely the one by itself) popped off during reassembly
Attachments
Thanks for your answer. I'm aware that HFS+ is the recommended FS for the installation sticks created by Mojave Patcher, but have intentionally used APFS on this single occasion to have confirmation my machine has become capable of booting APFS after its ROM upgrade.
Is that a "I positively know Mojave won't boot from external USB flash storage" or rather an "it's not recommended to …"? - I ask because earlier macOS versions were able to create a bootable OS installation on USB sticks, which were a nice way to perform a few tests with a new major macOS release before deciding whether or not you'd want to early adopt it as the main OS for your machine's internal storage.
I installed Mojave on my Mid 2010 21.5" iMac. Everything went fine, this Mac natively supports APFS. What's different about this iMac is the CPU, I wanted this iMac to be quad core. I found out the hard way the 21.5" iMac does not support CPU's higher than the 73w TDP. Doing research of different Lynnfield processors I came across the Xeon L3426. It's a 45w 1.86GHz quad core cpu with hyper threading. This is the CPU in the iMac now and it has been working flawlessly.
