@Ultracyclist ... thank you for your outstanding article for the installation of the new WLAN BT card 1342 in the Macmini3,1.
My ordered card at Ebay (also the 1342 from a Mac Book Black) from China would also arrive here in D soon. I will install the same, whether I pierce a hole, for fastening, I still do not know. First time so easy to fix and test.
When I finish the operation, I write a report here.
I've got an iMac 14.2 and installed the beta 3 of Sierra 10,12,1 and wanted to install the latest nVidia web driver WebDriver-367.15.10.05f01.pkg, the error message comes that this driver is not compatible Is. He has a Strix GTX950 nVidia graphics card in it. At El Capitan everything was ok. But is a hackintosh. Do you know which nVidia Webtreiber must use?
Running so far so good on MacPro 3,1 (Early 2008).
After install completed, but before reboot I launched terminal and replaced the PlatformSupport.plist file with the one used by the installer partition so that I could boot into macOS without issue.
EDIT:
iMessage having issues ... crashed several times.
Graphical elements missing in iMessage on the display I'm running off of the 8800GT card (non issue on GTX650 card). iMessage crashes when moving between displays running on different cards.
Using Nvidia web drivers vs OEM Apple drivers make no difference in this.
this is a bug with metal and cards with extremely different opengl versions, it's apple's problem
[doublepost=1476062340][/doublepost]oh @dosdude1 can you make your program refuse to run if sip is enabled? and explain how to disable it in the info
also I think you could detect that sip is enabled, using a launch daemon, and then reboot to recovery if it is enabled, with setting boot-args sipfixer=1
then, in a launch daemon in the recovery,check if sipfixer=1 in boot-args, if so, run automatically csrutil disable, clear boot-args and reboot
this is a bug with metal and cards with extremely different opengl versions, it's apple's problem
[doublepost=1476062340][/doublepost]oh @dosdude1 can you make your program refuse to run if sip is enabled? and explain how to disable it in the info
also I think you could detect that sip is enabled, using a launch daemon, and then reboot to recovery if it is enabled, with setting boot-args sipfixer=1
then, in a launch daemon in the recovery,check if sipfixer=1 in boot-args, if so, run automatically csrutil disable, clear boot-args and reboot
For the first time since OS X Mountain Lion (10.8) in 2012, macOS Sierra (10.12) has changed the official minimum requirements needed for installation, leaving many older (but still perfectly capable) Macs behind.
MacBook (late 2009 or later)
iMac (late 2009 or later)
MacBook Air (2010 or later)
MacBook Pro (2010 or later)
Mac mini (2010 or later)
Mac Pro (2010 or later)
This is a thread for people to discuss and offer solutions for newly unsupported Macs in macOS Sierra. This post will be updated with solutions as they become available.
Apple History
OS X Snow Leopard (10.6) was the first version of OS X with support for 64-bit kernels, allowing booting with either a 32-bit or 64-bit kernel. However, Apple did not support booting the 64-bit kernel in Macs that shipped with EFI32 firmware, even if they had 64-bit processors capable of running the 64-bit kernel. When Apple dropped the 32-bit kernel entirely in OS X Mountain Lion (10.8), EFI32 Macs no longer had an Apple-supported mechanism to boot newer versions of OS X.
OS X El Capitan (10.11) includes SIP (System Integrity Protection/Rootless). It makes sure that system files and their permissions are automatically protected, and also updated during Software Updates. The Repair Permissions function is no longer available and access to system files that need to be changed may require disabling it.
Known Issues:
macOS Sierra dropped support for Wi-Fi cards (BCM4321) used in most 2008 and some 2009 Macs. A hardware upgrade is required to get Wi-Fi functionality on those models.
iMac8,1 - Volume control for the Built-In Audio device may work improperly or not at all.
Macbook5,2 - The trackpad is not configurable, it is detected as a regular mouse instead.
Models Tested:
Older Legacy Macs not in this table (including the MacBook2,1, MacBook3,1 and iMac5,1) can install Mountain Lion (10.8), Mavericks (10.9), and Yosemite (10.10) with MacPostFactor or OS X Extractor (noted in the spoiler below), but are not supported by OS X El Capitan (10.11) or later.
MacPro1,1 and 2,1 can run OS X El Capitan with the methods noted in the spoiler below, but are currently not supported by macOS Sierra due to a lack of SSE 4 support (the CPU can be upgraded but its firmware does not support newer SSE 4-compatible CPUs).
Current Development Files:
Kexts: Legacy USB Injector Kext OS X Extractor - Beta USB Kexts.zip (depreciated)
PlatformSupport.plist / InstallableMachines.plist: Download Zip
Known Patching Methods (the important bit):
Automatic tools that can be used to install macOS Sierra onto an unsupported Mac.
[doublepost=1476087644][/doublepost]I have a 2012 macbook pro that is (I think) running Mountain Lion 10.8.5. I upgraded to Mavericks when that came out and immediately lost the WiFi and then loads of other thing went wrong and I had to pay a shop to resurrect my machine. Since then I have been reluctant to take advantage of the 'Free Upgrades' but now I keep on getting messages that my version of Safari is out of date etc etc! Is there a way to work round the faults that are caused by upgrading to a new operating system, obviously all the hardware that I have dates from 2012 with the exception of the RAM that I've recently upgraded from 4 to 16 Gig.
Since I am writing, my bluetooth connection has stopped working. Does anybody have any suggestions?
I have lost confidence in Apple since Steve Jobs left us, the machine is indispensable for photographs and music when compared with a PC but the 'must have' culture of a new operating system every year that makes older machines obsolete is not the correct way to keep the faithful buying Apple.
When I have to replace my machine in a few years I will be researching what is out there and it is unlikely that I will be paying premium price for a new Macbook or whatever name they will have dreamed up by then!
[doublepost=1476087644][/doublepost]I have a 2012 macbook pro that is (I think) running Mountain Lion 10.8.5. I upgraded to Mavericks when that came out and immediately lost the WiFi and then loads of other thing went wrong and I had to pay a shop to resurrect my machine. Since then I have been reluctant to take advantage of the 'Free Upgrades' but now I keep on getting messages that my version of Safari is out of date etc etc! Is there a way to work round the faults that are caused by upgrading to a new operating system, obviously all the hardware that I have dates from 2012 with the exception of the RAM that I've recently upgraded from 4 to 16 Gig.
Since I am writing, my bluetooth connection has stopped working. Does anybody have any suggestions?
I have lost confidence in Apple since Steve Jobs left us, the machine is indispensable for photographs and music when compared with a PC but the 'must have' culture of a new operating system every year that makes older machines obsolete is not the correct way to keep the faithful buying Apple.
When I have to replace my machine in a few years I will be researching what is out there and it is unlikely that I will be paying premium price for a new Macbook or whatever name they will have dreamed up by then!
Surprised you had any issues at all - you certainly shouldn't have (that's kinda the point of Apple having these closed systems).
To completely preserve your configuration, you could use something like Carbon Copy Cloner to clone your internal hard drive to an external USB hard drive - making it bootable (then test it, booting your MacBook off of the external USB).
Once verified, download the Sierra installer, but don't install (apple menu, quit). Then use dosdude1's utility to make yourself a USB installer (with a USB flash drive). Then use that to do an upgrade on your install on the external USB drive, then boot from that and see if there's any issues.
If there aren't any issues, you can feel comfortable upgrading your internal hard drive to Sierra.
Now, as your 2012 MacBook is actually a SUPPORTED Mac, you don't need to run the post-install utility.
I have lost confidence in Apple since Steve Jobs left us, the machine is indispensable for photographs and music when compared with a PC but the 'must have' culture of a new operating system every year that makes older machines obsolete is not the correct way to keep the faithful buying Apple.
When I have to replace my machine in a few years I will be researching what is out there and it is unlikely that I will be paying premium price for a new Macbook or whatever name they will have dreamed up by then!
From my experience if you think apple sucks today go try windows (winblows), I am the IT guy at work (small company) and every single time win10 comes out with updates I cringe, at least 4 times this year alone the updates took out printer drivers and ect.. A few times the only way to fix, was system restore's NOTHING else fixed it. I even upgraded the memory in 3 of them to a well known brand, adding double also to find out that had no effect on performance issues that I have with them. Winblows still can not handle multiple things running, 2 workers reboot at least 2 times a week (one of them shuts down every night even) all have no viruses and spyware. Also the same upgrade issues happen with window machines, after so many years (usually a lot fewer) they need upgrading if not sooner or just discarded.
As for apple well I don't like or will not buy the new mac pro (non upgradable like my early 2008 that is still running great as I type this), but the rest of the line seems great, maybe the mac mini next I will see what at the time. My MacBook pro (mid 2010. 6,2) is still getting updates and I never reloaded any of my macs form a fresh format, my macs still have all the stuff from day one on (unless I uninstalled, trashed the program).
Best of luck!
Cheers!!
EDIT:
I always have a carbon copy cloner disk ready, sometimes it may be a few months old but I have a restore point (instant swap) when needed if at all, of course time machine should work great also (I have not used it).
I have an iMac 8,1: a 2008 24" iMac with a 3.06 GHz Core 2 Duo CPU. As stated in dosdude1's excellent instructions for the Sierra Patcher Tool, all but WiFi and audio volume control are working. WiFi is not an issue for me, since this iMac has been connected via wired Ethernet for all its' life. And if needed, I can replace the AirPort card. The audio volume control is the last hurdle to take for me.
Did anyone with an iMac 8,1 already have success with getting the audio volume control fixed? I went through this thread, and saw a few suggestions but haven't seen a definite explanation on how to do this.
What I've done so far is copy AppleHDA.kext and IOAudioFamily.kext in /System/Library/Extensions from El Capitan to Sierra and rebuild the kernel caches using:
I have an iMac 8,1: a 2008 24" iMac with a 3.06 GHz Core 2 Duo CPU. As stated in dosdude1's excellent instructions for the Sierra Patcher Tool, all but WiFi and audio volume control are working. WiFi is not an issue for me, since this iMac has been connected via wired Ethernet for all its' life. And if needed, I can replace the AirPort card. The audio volume control is the last hurdle to take for me.
Did anyone with an iMac 8,1 already have success with getting the audio volume control fixed? I went through this thread, and saw a few suggestions but haven't seen a definite explanation on how to do this.
What I've done so far is copy AppleHDA.kext and IOAudioFamily.kext in /System/Library/Extensions from El Capitan to Sierra and rebuild the kernel caches using:
I found this developer whose program might help disable SIP from within your patcher. The issue being that his exploit was already patched in OS X 10.11.4.
I found this developer whose program might help disable SIP from within your patcher. The issue being that his exploit was already patched in OS X 10.11.4.
I have an iMac 8,1: a 2008 24" iMac with a 3.06 GHz Core 2 Duo CPU. As stated in dosdude1's excellent instructions for the Sierra Patcher Tool, all but WiFi and audio volume control are working. WiFi is not an issue for me, since this iMac has been connected via wired Ethernet for all its' life. And if needed, I can replace the AirPort card. The audio volume control is the last hurdle to take for me.
Did anyone with an iMac 8,1 already have success with getting the audio volume control fixed? I went through this thread, and saw a few suggestions but haven't seen a definite explanation on how to do this.
What I've done so far is copy AppleHDA.kext and IOAudioFamily.kext in /System/Library/Extensions from El Capitan to Sierra and rebuild the kernel caches using:
I have 16A323 installed on an external Firewire disk, connected to an iMac8,1, and as long as I use a pair of USB speakers (Soundsticks), the volume control works just fine. But when I switch to the built-in speakers, I cannot change the volume.
By the way: thanks to ”swamprock” who linked to http://www.ebay.com/itm/111988677835, a cheap wifi card that turned out to work perfectly on this machine.
For the first time since OS X Mountain Lion (10.8) in 2012, macOS Sierra (10.12) has changed the official minimum requirements needed for installation, leaving many older (but still perfectly capable) Macs behind.
MacBook (late 2009 or later)
iMac (late 2009 or later)
MacBook Air (2010 or later)
MacBook Pro (2010 or later)
Mac mini (2010 or later)
Mac Pro (2010 or later)
This is a thread for people to discuss and offer solutions for newly unsupported Macs in macOS Sierra. This post will be updated with solutions as they become available.
Apple History
OS X Snow Leopard (10.6) was the first version of OS X with support for 64-bit kernels, allowing booting with either a 32-bit or 64-bit kernel. However, Apple did not support booting the 64-bit kernel in Macs that shipped with EFI32 firmware, even if they had 64-bit processors capable of running the 64-bit kernel. When Apple dropped the 32-bit kernel entirely in OS X Mountain Lion (10.8), EFI32 Macs no longer had an Apple-supported mechanism to boot newer versions of OS X.
OS X El Capitan (10.11) includes SIP (System Integrity Protection/Rootless). It makes sure that system files and their permissions are automatically protected, and also updated during Software Updates. The Repair Permissions function is no longer available and access to system files that need to be changed may require disabling it.
Known Issues:
macOS Sierra dropped support for Wi-Fi cards (BCM4321) used in most 2008 and some 2009 Macs. A hardware upgrade is required to get Wi-Fi functionality on those models.
iMac8,1 - Volume control for the Built-In Audio device may work improperly or not at all.
Macbook5,2 - The trackpad is not configurable, it is detected as a regular mouse instead.
Models Tested:
Older Legacy Macs not in this table (including the MacBook2,1, MacBook3,1 and iMac5,1) can install Mountain Lion (10.8), Mavericks (10.9), and Yosemite (10.10) with MacPostFactor or OS X Extractor (noted in the spoiler below), but are not supported by OS X El Capitan (10.11) or later.
MacPro1,1 and 2,1 can run OS X El Capitan with the methods noted in the spoiler below, but are currently not supported by macOS Sierra due to a lack of SSE 4 support (the CPU can be upgraded but its firmware does not support newer SSE 4-compatible CPUs).
Current Development Files:
Kexts: Legacy USB Injector Kext OS X Extractor - Beta USB Kexts.zip (depreciated)
PlatformSupport.plist / InstallableMachines.plist: Download Zip
Known Patching Methods (the important bit):
Automatic tools that can be used to install macOS Sierra onto an unsupported Mac.
I ran the dosdude's patch and the installer on my MBP 5,2 via a FW-connected SSD (with a clone of my boot drive) last night. Although the process was slow (writing from FW to USB2 and back!), at the end it all seemed to work *touch wood* perfectly. I wasn't sure what to expect with the trackpad issues, but my tap to click and two-finger tap to right click were working as before, and the settings in Sys Pref were all good. I didn't dare fiddle with them, though!
I wasn't fussed that my 7 year old machine wasn't supported, it runs really well on ElCap with an SSD, but I was interested in the improvements to the Photos app. Many thanks @dosdude1 and @foxlet!
Used the patcher to upgrade my Mac Pro 3,1 to Sierra. Mine is a little different in that I have an Nvidia GT120 card I got on Craigslist to replace the ATI 2400 card the machine came with once that card failed. So far everything seems to work except volume control for the internal speaker seems to be wonky. I don't remember this being a specific bug. If I use the (awful) external speakers in my Viewsonic monitor, then everything is fine. I'll play around with it a little more.
I have two other Macs that can be upgraded as well. A Macbook unibody 5,1 is probably next on the list since I don't think there are any known issues. But I have an iMac 8,1 I'd like to upgrade as well. Wifi is a problem but this machine is on wired Ethernet (all non-portable machine in my house are wired). I am trying to figure out what I do about the volume control problem....maybe external speakers again is the answer.
Used the patcher to upgrade my Mac Pro 3,1 to Sierra. Mine is a little different in that I have an Nvidia GT120 card I got on Craigslist to replace the ATI 2400 card the machine came with once that card failed. So far everything seems to work except volume control for the internal speaker seems to be wonky. I don't remember this being a specific bug. If I use the (awful) external speakers in my Viewsonic monitor, then everything is fine. I'll play around with it a little more.
I have two other Macs that can be upgraded as well. A Macbook unibody 5,1 is probably next on the list since I don't think there are any known issues. But I have an iMac 8,1 I'd like to upgrade as well. Wifi is a problem but this machine is on wired Ethernet (all non-portable machine in my house are wired). I am trying to figure out what I do about the volume control problem....maybe external speakers again is the answer.
I found audio on my pro 3,1 to be a little quirky also. For another reason: the audio output device seems to change after sleep. Happens less after my upgrade to 10.12.1 beta 3 though, so it may have been a temporary bug.
As for wifi - I recently upgraded to this card : http://www.osxwifi.com/pre-order-ap...ac-bluetooth-4-0-with-adapter-for-macpro-2008 with great success. A little pricy though. Make sure and wire the antennae correctly (there is a link in one of the reviews with a great hands-on tutorial and the proper terminals to use) Wifi performance is great + Continuity (handoff, universal cut&paste etc...) are fully functional. Continuity kinda grows on you...
[doublepost=1476165890][/doublepost]
@Ultracyclist ... thank you for your outstanding article for the installation of the new WLAN BT card 1342 in the Macmini3,1.
My ordered card at Ebay (also the 1342 from a Mac Book Black) from China would also arrive here in D soon. I will install the same, whether I pierce a hole, for fastening, I still do not know. First time so easy to fix and test.
When I finish the operation, I write a report here.
I've got an iMac 14.2 and installed the beta 3 of Sierra 10,12,1 and wanted to install the latest nVidia web driver WebDriver-367.15.10.05f01.pkg, the error message comes that this driver is not compatible Is. He has a Strix GTX950 nVidia graphics card in it. At El Capitan everything was ok. But is a hackintosh. Do you know which nVidia Webtreiber must use?
As is often the case, NVidia has trouble catching up with Apple. And you have installed a beta version so, unfortunately, WebDriver-367.15.10.05f01.pkg will not install. You have two options:
@pkouame great thanks for your reference, I've tried everything as in the thread with Insanelymac see and also the thread of "Wastez" I have read and tried, just does not.
I even then macOS 10.12. GM3 reinstalled and then tried to install the nVidia web driver for the 16A323, successfully installed, booting up to half with Clover 3716 then, if the Garfik must switch to nVidia, comes only blue screen, then "no signal" and black screen .
At Yosemite and El Capitan no such problems, everything ok.
I guess it is at the Strix GTX950 map with Sierra.
I wait, as you say, until the macOS 10.12.1 and the nVidia drivers come then, let's see if it will be something.
[doublepost=1476009380][/doublepost]I have 2 x 2009 early minis and want to update to sierra. Of course it appears to be a no go except for now. However I have also read that wireless can be regained by using an external wife dongle rather than going through the route clearly explained above.
Has anyone done this? and with which one?
Cheers
Hi, I have buy somedays ago a Macbook4,1 (Early 2008) 13-inch Black.
MB arrive only friday. in waiting.. i can know if Sierra works fine on this model?
Hi, I have buy somedays ago a Macbook4,1 (Early 2008) 13-inch Black.
MB arrive only friday. in waiting.. i can know if Sierra works fine on this model?
@pkouame great thanks for your reference, I've tried everything as in the thread with Insanelymac see and also the thread of "Wastez" I have read and tried, just does not.
I even then macOS 10.12. GM3 reinstalled and then tried to install the nVidia web driver for the 16A323, successfully installed, booting up to half with Clover 3716 then, if the Garfik must switch to nVidia, comes only blue screen, then "no signal" and black screen .
At Yosemite and El Capitan no such problems, everything ok.
I guess it is at the Strix GTX950 map with Sierra.
I wait, as you say, until the macOS 10.12.1 and the nVidia drivers come then, let's see if it will be something.
In my case it works because I had the driver loaded BEFORE updating to Sierra 10.12.1 betas. So Nvidia Preferences would just complain about an incompatible driver and revert back automagically to the default Sierra ones. I then had to fix the plist and rebuild caches and kernels (you did remember to do that right?).
If you try and run the latest installer on a beta, the installer's system check will block it. The only way around that is open heart surgery in the .pkg files. There is a distribution file in the .pkg with this code :
Code:
function validateSoftware()
{
var supportedOSVer = "10.12";
var supportedOSBuildVer = "16A323";
var targetBuild = system.version.ProductBuildVersion;
var result = compareBuildVersions(targetBuild, supportedOSBuildVer);
if (result != 0)
...
...
Unless you have a really pressing need for the new web driver, just wait for the official one...
