macOS 10.14 Mojave on Unsupported Macs Thread

[Pinarek]

Yeah, it seems the legacy graphics hardware has weird issues with external displays/clamshell mode under Mojave... Unfortunately there's really nothing that can be done about that.

On a different note, as a MacBook5,1 owner, I think you'll find my latest endeavor quite interesting... I upgraded the CPU on a MacBook5,1 to a 3.06 GHz Core 2 Duo T9900, the absolute fastest CPU that board can support! You can see the process in my video here:

@dosdude1 I have a question: how about the fan of the CPU? you have now built a T9900 processors, the fan runs more often because of the stronger heating of the CPU? and how high is the CPU temperature during normal operation?

 

[dosdude1]

@dosdude1 I have a question: how about the fan of the CPU? you have now built a T9900 processors, the fan runs more often because of the stronger heating of the CPU? and how high is the CPU temperature during normal operation?

Surprisingly, it seems to run no warmer than it did with the original CPU installed. The fan doesn't even get up to full speed when running Geekbench, so I'd say it runs quite well.

 

[jhowarth]

Surprisingly, it seems to run no warmer than it did with the original CPU installed. The fan doesn't even get up to full speed when running Geekbench, so I'd say it runs quite well.

That is only a 35W TDP part which is nothing compared to the 45W TDP toaster that they used in the 2006 MacBook Pros.

 

[Mr-Stabby]

Does anyone think there will ever be graphics acceleration for the 2011 iMac? I have 28 of these at a media college that i'd love to keep going with updates if possible. I've already used the patcher on our remaining 2008 and 2009 iMacs, and they are like new, so really appreciate the work done so far! We're too poor to buy new machines at this point so things like this are a godsend!

 

[varad]

So,
Firstly, Happy New year everybody!

I was hoping if somebody could help with an issue.

I am running Mojave 10.14.2 (SSD) on MacBook Pro 2011(Late) i7 756GB

I just replaced the Bluetooth/Airport card to BCM94331PCIEBT4CAX and lost Bluetooth on Mojave completely.
However, If I boot into the High Sierra Partition (As a failsafe on HD), Bluetooth is recognized.

Can somebody help with this, please?


Would i have to rerun the dosdude patcher using a install disk ?

 

[Kent W]

Does anyone think there will ever be graphics acceleration for the 2011 iMac? I have 28 of these at a media college that i'd love to keep going with updates if possible. I've already used the patcher on our remaining 2008 and 2009 iMacs, and they are like new, so really appreciate the work done so far! We're too poor to buy new machines at this point so things like this are a godsend!

It seems as Schwab on previous page 456 reported a succesful upgrade of a 2011 iMac using ResXtreme to correct graphics problems with colors. However not clear status on the possible missing graphics acceleration.

 

[Flacko]

So,
Firstly, Happy New year everybody!

I was hoping if somebody could help with an issue.

I am running Mojave 10.14.2 (SSD) on MacBook Pro 2011(Late) i7 756GB

I just replaced the Bluetooth/Airport card to BCM94331PCIEBT4CAX and lost Bluetooth on Mojave completely.
However, If I boot into the High Sierra Partition (As a failsafe on HD), Bluetooth is recognized.

Can somebody help with this, please?


Would i have to rerun the dosdude patcher using a install disk ?

Hi Varad and happy new year to you. There have been quite few members who have had troubles with Mojave and bluetooth. The problem appears quite random and there has been no definite identification of the exact problem. However, it does seem more prevalent in those who have updated their BT/Airport card. As you know the card works well in HS then there is a chance replacing some kexts in Mojave's S/L/E with those from your HS partition. This is what worked for me. First try IOBluetoothFamily.kext and IOBluetoothHIDDriver.kext. Remember to fix permissions after and clear the kext cache. This has worked for quite a few members and got me working on 14.0. However, to get BT working on 14.1 and 14.2 I had also to replace IOACPIFamily.kext. Take it in stages and you may get lucky!

 

[Larsvonhier]

It seems as Schwab on previous page 456 reported a succesful upgrade of a 2011 iMac using ResXtreme to correct graphics problems with colors. However not clear status on the possible missing graphics acceleration.

SwitchResX does the same trick, reduce color depth and the partly-inverse colors are correct on all ATI cards (even eGPUs). Acceleration is still missing, though.

 

[varad]

Hi Varad and happy new year to you. There have been quite few members who have had troubles with Mojave and bluetooth. The problem appears quite random and there has been no definite identification of the exact problem. However, it does seem more prevalent in those who have updated their BT/Airport card. As you know the card works well in HS then there is a chance replacing some kexts in Mojave's S/L/E with those from your HS partition. This is what worked for me. First try IOBluetoothFamily.kext and IOBluetoothHIDDriver.kext. Remember to fix permissions after and clear the kext cache. This has worked for quite a few members and got me working on 14.0. However, to get BT working on 14.1 and 14.2 I had also to replace IOACPIFamily.kext. Take it in stages and you may get lucky!

I have located the kexts, how Ian i fix permissions and clear the kext cache?

Thank you so much for your help !

 

[Flacko]

I have located the kexts, how Ian i fix permissions and clear the kext cache?

Thank you so much for your help !

After replacing the kext with those from HS (try both the bluetooth ones first) open Terminal and run the following commands. You can copy and paste them into terminal:

sudo chmod -R 755 /System/Library/Extensions/IOBluetoothFamily.kext

sudo chmod -R 755 /System/Library/Extensions/IOBluetoothHIDDriver.kext

sudo chown -R 0:0 /System/Library/Extensions/IOBluetoothFamily.kext

sudo chown -R 0:0 /System/Library/Extensions/IOBluetoothHIDDriver.kext

then clear the kext cache using this:

sudo kextcache -system-prelinked-kernel

Let the final command take its time. You will get a lot a text referring to the cache. Make sure it is finished before you reboot your system. With a bit of luck you may have your BT up and running. If not you can try replacing the IOACPIFamily.kext as well:

sudo chmod -R 755 /System/Library/Extensions/IOACPIFamily.kext
sudo chown -R 0:0 /System/Library/Extensions/IOACPIFamily.kext

sudo kextcache -system-prelinked-kernel

 

[antony34]

If you have a late 2009 iMac, you should be able to install High Sierra as a supported machine and let the stock Apple installer do the APFS conversion which will produce the fully populated container.

so, i may use High Sierra installer to convent to APFS rather than patched installer?

 

[roronl]

@antony34 with a supported machine yes, and you should

 

[antony34]

@antony34 with a supported machine yes, and you should

thank you very much!!

 

[varad]

After replacing the kext with those from HS (try both the bluetooth ones first) open Terminal and run the following commands. You can copy and paste them into terminal:

sudo chmod -R 755 /System/Library/Extensions/IOBluetoothFamily.kext

sudo chmod -R 755 /System/Library/Extensions/IOBluetoothHIDDriver.kext

sudo chown -R 0:0 /System/Library/Extensions/IOBluetoothFamily.kext

sudo chown -R 0:0 /System/Library/Extensions/IOBluetoothHIDDriver.kext

then clear the kext cache using this:

sudo kextcache -system-prelinked-kernel

Let the final command take its time. You will get a lot a text referring to the cache. Make sure it is finished before you reboot your system. With a bit of luck you may have your BT up and running. If not you can try replacing the IOACPIFamily.kext as well:

sudo chmod -R 755 /System/Library/Extensions/IOACPIFamily.kext
sudo chown -R 0:0 /System/Library/Extensions/IOACPIFamily.kext

sudo kextcache -system-prelinked-kernel

You should use these two kext IOBluetoothFamily.kext and IOBluetoothHIDDriver.kext taking from a Mojave clean installation or late HighSierra, using those inside the USB Installer I guess won't work cause they are smaller in size so presumably can't cover all the BT devices.

In case you don't have, I attach both the Bluetooth kexts from a clean Mojave GoldenMaster, replace the ones inside your Mojave /System/Library/Extensions/ after you have to launch Terminal and type:

sudo chmod -R 755 /S*/L*/E*
sudo chown -R 0:0 /S*/L*/E*
sudo kextcache -i /
sudo reboot

So I tried the what @Flacko said, and that didnot work for me because I used old HS Kexts ,
Later I tried the kexts from the installer USB and they didn't work either.

What worked was using the 2 Kexts from @jackluke 's post and using the exact commands.

Hurray !

Thanks @jackluke & @Flacko !!

 

[jhowarth]

so, i may use High Sierra installer to convent to APFS rather than patched installer?

Assuming that you are still on Sierra or earlier, when you install High Sierra as a supported machine, the process will convert the system HFS volume to APFS with the normally populated container.

 

[Yojx21]

All hints duly noted about how slow this machine is without (or even with) accelerated graphics output. Still an interesting experiment - and still way better than some virtualisation attempts that some folks run.

I have now repaired the flex keyboard cable, so up to El Cap everything runs fine on the Macbook 4,1. ("Fine" meaning frame buffers for video memory and basic acceleration work, but of course not OpenGL. Makes it still a machine you could work on: I have prepared such a setup a while ago for a friend who works with M$ Office 2016 on it and wants to use modern browsers. No complaints from that side! Also: Nice to be able to sync the latest iOS gadgets vie iTunes on it. So I´d be glad to be spared about further warnings about how unfeasible Mojave would be on it. I want to experience it myself - is that not the spirit in especially this thread? ;-) )

As (High) Sierra USB does not work either, am I right that it would take the El Cap or Yosemite kexts to get it running under Mojave? Any chance that such old kexts would be usable? Any info on the dependencies of IOUSBFamily / IOPCIFamily / IONDRVSupport - or perhaps some more of the AppleUSB_ sorts?

Pretty intersting experimentation ! Let ius know where you get with it !

 

[DaniloGeekDude]

Mojave 10.14.3 Beta 3 Upgrade

Successfully upgraded to the latest beta using OTA and macOS Patch Updater 1.2.3



Also using HyBrid v1.4 for UI fixes/enhancements.
Will continue to test this beta. So far so good.

Many Thanks to @dosdude1 and @pkouame for your tools/apps and to other contributors mentioned on the OP as well.

EDIT: Correction on the Hybrid version --- used 1.4.1.

 

[Pinarek]

Mojave 10.14.3 Beta 3 Upgrade

Successfully upgraded to the latest beta using OTA and macOS Patch Updater 1.2.3

View attachment 814704

Also using HyBrid v1.4 for UI fixes/enhancements.
Will continue to test this beta. So far so good.

Many Thanks to @dosdude1 and @pkouame for your tools/apps and to other contributors mentioned on the OP as well.

How about the transparency, again the 2 Frameworks files have to be
replaced or are those of the Beta2 still? I mean these 2 dates:
CoreUI Hybrid-18C54-v1.4.1 and HIToolboxHybrid-18C54

 

[DaniloGeekDude]

How about the transparency, again the 2 Frameworks files have to be
replaced or are those of the Beta2 still? I mean these 2 dates:
CoreUI Hybrid-18C54-v1.4.1 and HIToolboxHybrid-18C54

Yes, I replaced those with the ones from 1.4.1 version. Verified the checksums:

52eede43e030fd75a37e61fc7205cddc0884d344 CoreUIHybrid-18C54-v1.4.1
8f0a8129950cc0acf14821e96a54d917ad1f3947 HIToolboxHybrid-18C54

Regards.

 

[Larsvonhier]

Pretty intersting experimentation ! Let ius know where you get with it !

So far, no luck with the El Cap kexts. I think I´ll have to dive deeper and replace single kext contents. I found that actually, the MB 4,1 runs El Cap only without USB functionality also - but fine with Yosemite. (At least when I run El Cap on it from a MB Pro 3,1 over firewire target mode). Have not tried original vanilla installation from another machine so far., might behave different, though.
Screenshot shows the kexts on Mojave and Yosemite that we have to deal with (I assume). Note that IOUSB... are not all present (5x) on 10.10.5 ?!

 

[rmendez011]

Don't know if there's a solution for this, but I followed the steps here and installed Mac OS Mojave on my 2011 Macbook Pro, but now whenever I sleep it the fans stay on and if I try turning it on, I can't, I have to hold the power button till it shuts off then I can power it on, any solution? Thanks.

 

[Larsvonhier]

Short note to @dosdude1 : The backlight brightness patch for old MB Pro 4,1 (CCFL backlight) still works with the latest 10.14.3 beta 3. Perhaps it could be integrated into a (hopefully!) coming v1.2.4 of your post-patch list?

 

[Flacko]

So I tried the what @Flacko said, and that didnot work for me because I used old HS Kexts ,
Later I tried the kexts from the installer USB and they didn't work either.

What worked was using the 2 Kexts from @jackluke 's post and using the exact commands.

Hurray !

Thanks @jackluke & @Flacko !!

Well done, I was just about to send you the kexts. You will have to go through this again if you update to 14.3 when it is available as the replaced kexts will be overridden. Keep a back up copy of the kexts that work.

 

[antony34]

Assuming that you are still on Sierra or earlier, when you install High Sierra as a supported machine, the process will convert the system HFS volume to APFS with the normally populated container.

my imac 2009 installed 10.14.2 now....can't convert? or need clean install?

 

[christougher]

Hi, are there any known issues reverting back to High Sierra? I've gone back to High Sierra (format and fresh install from USB stick as well as restoring a backup. Since then I've noticed there is a 30 second black screen delay right before the system log in screen should show. After this 30 second delay everything works fine. Any idea if this could be related? I'm no 100% positive when it started happening.

EDIT: Never mind, the issue was something else.