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
macOS Mojave runs fine on my 2009 Late iMac 27", the only thing i need to replace is the GPU but i'm going to wait until the GM is released.
If you replace the GPU, you lost brightness control and boot screen (until MacVidCards release some cards with the proper EFI firmware).
Those use the 1st gen MXM interface. No new cards have been produced for that since 2010, so you have no chance of installing a Metal compatible card.
Since Apple said they will Support the 2010 and 2012 Mac Pros with a Metal video card, I am convinced the beta 2 and all GM will be more compatible under the hood. Not giving up just yet.
If Apple makes it impossible, and a you really need to have Mojave for things like having the latest and greatest version of Xcode running or supporting the latest iOS, 2012 and 2014 Mac minis will be something to look for. I am hoping it does not come down that that. I do have one nice 2012 Mac mini left at home, but my 2008 Mac Pro handles 4k at 60 Hz with scaling. It's way better than the 2012 on Mojave.
Also, if Apple decides to come out with a Mac mini Pro or one that handles 4k super well, I will definitely buy one. Still want to keep running my 2008's but a beefed up Mac mini in 2018/2019/2020 would be awesome (as long as they don't neuter it like the 2014).
If Apple makes it impossible, and a you really need to have Mojave for things like having the latest and greatest version of Xcode running or supporting the latest iOS, 2012 and 2014 Mac minis will be something to look for. I am hoping it does not come down that that. I do have one nice 2012 Mac mini left at home, but my 2008 Mac Pro handles 4k at 60 Hz with scaling. It's way better than the 2012 on Mojave.
Also, if Apple decides to come out with a Mac mini Pro or one that handles 4k super well, I will definitely buy one. Still want to keep running my 2008's but a beefed up Mac mini in 2018/2019/2020 would be awesome (as long as they don't neuter it like the 2014).
Sound is working, but graphics loading in black screen. I reinstall Mojave again and copy this kexts - AppleHDA.kext, AppleIntelHD3000Graphics.kext, AppleIntelHD3000GraphicsGA.plugin, AppleIntelHD3000GraphicsGLDriver.bundle, AppleIntelHD3000GraphicsVADriver.bundle, AppleIntelSNBGraphicsFB.kext. Bat i copy the AppleIntelHD3000Graphics.kext and AppleIntelSNBGraphicsFB.kext - it loading with vesa mode. What I doing wrong?
You didn't do anything wrong, it just doesn't work. It's not as simple as simply adding the kexts/bundles.
And I add the Nvidia 9400m MCP79 controller (also for iMacs 2009) is very similar to my Nvidia Geforce 320m codename MCP89. They should use the same GPU kext.
Without Clover and any other modification I managed to boot the Mojave Beta Recovery partition from an unsupported unibody Macbook 2010.
Surprising from verbose I read “ NVDAStartup: Official” kext loaded (while on normal boot it reboots immediately after all verbose lines), finally I can reach the macOS GUI it looks like also graphically fast (I mean I can see the fade-in effect and this is a kind of acceleration I guess no), but I cannot detect my laptop's keyboard and trackpad, neither other usb external peripherals like usb mouse (but the red led powers on) so it's like a stall but I see also from the verbose mode that AppleHDA sound assertions are loaded too, and even the wifi card upper right on the GUI.
This is the main issue I read in verbose on usb external mouse (or usb keyboard) before reach the GUI:
"AppleUSBHostPort :: disconnect : persistent enumeration failures"
It's weird because I'm booting it exactly from another same side USB port where the Mojave Recovery partition stores.
I need some tips on which kexts could be involved on usb external mouse or internal laptop trackpad and keyboard. I've already tried VoodooPS2Controller but seems not detected.
I’ve also compared inside the basesystem.dmg of the Mojave recovery’s extensions folder with Mojave stock S/L/E and tried to use only those emergency kexts but I get ever a quick reboot after all verbose checks on standard boot, while tried everything to cheat the PrelinkedKernel folder with just the recovery prelinkedkernel but nothing, assuming that can boot Mojave recovery with Nvidia GUI, the worst is that can't get any usb input peripherals detected, totally incompatible.
Also noticed that inside the apfs container the Mojave recovery partition is HFS+ so maybe quick reboot could depend also from a missing patched apfs efi?
I’m almost sure that these waterwall errors depend moreover from a missing 10.14 EFI eeprom mac firmware update or a patched kernel for unsupported macs, in my specific case the only way to boot would be Clover but the risk to brick the mac is too high.
Ok reading better early and lastly posts I have understood macbook 2010 cpu lacks the SSE4.2 instruction, and I confirm the major issue are the new streamline USB kexts, so I give up.
Last edited:
Working on iMacs is not fun either. First you have to remove the glass, unscrew the LCD and either lean the display towards you or disconnecf the cables then work on it. Then see all the dust bunnies it stores. Be horrified that it is such an ugly design inside, out it back together and deal with magnets next to where most of the screws go. Such a pain.
If I remember right the MacOs update won't appear in the App Store in Mojave someplace in settings or you could try a update patch and set it to Develpers beta
Software Update is in Settings and it says my Mac is up to date. Just tried on my 2015 rMBP and got the same message. I suppose it will take some time to roll out.
I have verified right now, to me it requires additional 14,61 gb to upgrade from Mojave beta 1 to beta 2, even removing the sleepimage, I cannot achieve, I should remove and merge the apfs recovery partition but that volume container appears totally locked and I cannot do others tests so I drop for now, good luck.
Edit:
I fixed, finally downloading 2,59 gb the reason I average use a hybrid disk with 4 partition types with different file system I find out that there was an additional APFS VM partition, I rid following this terminal command:
diskutil apfs deleteContainer diskXsY
Edit2:
Upgraded, right now the only addition I found is the circle Mojave desert picture on "About this Mac".
Edit:
I fixed, finally downloading 2,59 gb the reason I average use a hybrid disk with 4 partition types with different file system I find out that there was an additional APFS VM partition, I rid following this terminal command:
diskutil apfs deleteContainer diskXsY
Edit2:
Upgraded, right now the only addition I found is the circle Mojave desert picture on "About this Mac".
Last edited:
intel HD 3000 dont work? And how works radeon 5xxx with replace kexts? This is also without metall
My 5,1 MacPRO has 56GB RAM, two 3.06GHz x5675 processors, and a Radeon HD 7950 w/ 3GB and I still can't download MacOS 10.14 Beta2. I'm wondering if and when Apple will allow Mojave to download onto MP 5,1s?
I was able to Dissect an installer disk after it got put in an internal SSD that cannot be seen by my Mac’s EFI. It’s a limitation of this type of card. What I did notice, the installer records the initial hardware UUID and wha was weird in my case it “recorded” it in two places and what wrong unless it has some type of encryption on the UUID. I found initial UUID in two places on the installer in the same plist two different directories. Has Apple always recorded the UUID in the installer and are they using it for bug reports or something else.
It also has a pretty lengthy EFI folder on it with images, sound, and all are in some type of efi extension.
Because of this. I might redownload the installer and will double check this UUIDs before proceeding again.
Gonna also check it’s installer disk images are see if I find anything else out of the ordinary.
It also has a pretty lengthy EFI folder on it with images, sound, and all are in some type of efi extension.
Because of this. I might redownload the installer and will double check this UUIDs before proceeding again.
Gonna also check it’s installer disk images are see if I find anything else out of the ordinary.
Last edited: