Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Sounds reasonable. Lack of acceleration would make the GUI super slow. But instead of excluding them (who knows why people want to run Sierra? Maybe as a server where graphics don't matter?), why not put a warning in the patcher instead, saying something like "Warning: This machine is too slow to properly run macOS. Try at your own risk.".

I may like this solution, as a MacBook 4,1 owner. ;)
 
Jun 19 11:00:36 MacBook-Pro OSInstaller[531]: PackageKit: Executing script "preinstall" in /Volumes/SierraMBP/.OSInstallSandboxPath/Scripts/com.apple.pkg.OSInstall.NxLRXh
Jun 19 11:00:36 MacBook-Pro OSInstaller[531]: PackageKit: Unable to apply system content manifest from installation sandbox: untrusted manifest.
Jun 19 11:00:36 MacBook-Pro OSInstaller[531]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=119 "An error occurred while setting file attributes." UserInfo={NSURL=BaseSystemResources.pkg -- file:///System/Installation/Packages/OSInstall.mpkg#Distribution, PKInstallPackageIdentifier=com.apple.pkg.BaseSystemResources, NSLocalizedDescription=An error occurred while setting file attributes.} {
NSLocalizedDescription = "An error occurred while setting file attributes.";
NSURL = "BaseSystemResources.pkg -- file:///System/Installation/Packages/OSInstall.mpkg#Distribution";
PKInstallPackageIdentifier = "com.apple.pkg.BaseSystemResources";
}
Jun 19 11:00:36 MacBook-Pro OSInstaller[531]: OSIInstallElement <OSIInstallElement: 0x7ff98ef6f590> errored out:Error Domain=PKInstallErrorDomain Code=119 "An error occurred while setting file attributes." UserInfo={NSURL=BaseSystemResources.pkg -- file:///System/Installation/Packages/OSInstall.mpkg#Distribution, PKInstallPackageIdentifier=com.apple.pkg.BaseSystemResources, NSLocalizedDescription=An error occurred while setting file attributes.}

I had reported an install problem a couple of days ago (shown in quote is installer log error message after install failed); tried a few variations but with no success.

However, I noticed this morning that there was a newer version of patch app (v2.0) and when I tried install with it, it worked! Machine is macbook pro, late 2008; model 5,1. Sierra seems to run pretty well. A few notes:

  • in post-install patch phase I just used the suggested patches for my 5,1 model (this is a really neat feature of the newer patch tool)
  • I disabled the automatic reporting feature (for obvious reasons) - wondered if there's a way to do this by default in the patch tool?
  • as others have noted, wifi could not be configured
  • some USB operations seem very slow (eg copying a 1mb file from desktop to empty flash usb drive took a couple of minutes
thanks for this program!!
 
  • Like
Reactions: SteveJobzniak
dOJ0GvvvPiY.jpg
 
  • Like
Reactions: SteveJobzniak
i made a usb to boot from but it doesnt show up on the boot menu when i hold alt on my 5,1 Macbook Pro
 
@parrotgeek1 and @SteveJobzniak I tried the "LegacyHDMIAudio.kext" out of the "macOS Sierra Patcher 2" by @dosdude1 , but it seems to break the audio ("no audio device found" under: system information>audio). After deleting the "LegacyHDMIAudio.kext" all is fine again but, as expected, without HDMI Audio. So it seems for the ATI HD4850 in the iMac9,1 (early 2009) there is no need for for the "LegacyHDMIAudio.kext", or to be precise the kext will deactivate all audio devices.
 
i made a usb to boot from but it doesnt show up on the boot menu when i hold alt on my 5,1 Macbook Pro

make sure you are using the v2.0 version of the patch tool; I had problems with 5,1 Macbook Pro using the earlier version of the tool

(also make sure your usb partition has journalling enabled; sometimes it isn't by default); if it's not, then just use diskutils to enable journalling.)

Does it show up in System Preferences when you look at Startup Disk prefs?
 
@parrotgeek1 and @SteveJobzniak I tried the "LegacyHDMIAudio.kext" out of the "macOS Sierra Patcher 2" by @dosdude1 , but it seems to break the audio ("no audio device found" under: system information>audio). After deleting the "LegacyHDMIAudio.kext" all is fine again but, as expected, without HDMI Audio. So it seems for the ATI HD4850 in the iMac9,1 (early 2009) there is no need for for the "LegacyHDMIAudio.kext", or to be precise the kext will deactivate all audio devices.
Yeah, I noticed this. As such, I have disabled the HDMI audio patch by default for all models in the post-install tool.
 
Mac App Store seems to works for me on my MacBookPro4,1. What I checked:
- former purchased app download
- new free app purchase and download
Hmm, been running in El Capitan at the moment. Will boot back into Sierra and see if I can get it working. Maybe I'm just being stupid haha..

Update:
@Czo @jon8214 Just signed out of the App Store, signed back in, and now it's working. It asked me for my 2 step authentication, and now it seems to be downloading apps fine.
Could be a bug in this build of Sierra, rather than an 'unsupported Mac' problem.
 
Last edited:
  • Like
Reactions: jon8214
Hmm, been running in El Capitan at the moment. Will boot back into Sierra and see if I can get it working. Maybe I'm just being stupid haha..

Update:
@Czo @jon8214 Just signed out of the App Store, signed back in, and now it's working. It asked me for my 2 step authentication, and now it seems to be downloading apps fine.
Could be a bug in this build of Sierra, rather than an 'unsupported Mac' problem.
Yep, I concur. After signing out and then logging back in, the Mac App Store works. This, using the Sierra SSD in my MacBook Pro 5,1.
 
I'm going to exclude all GMAX3100-based systems. It's not worth running anything newer than 10.8 on those machines due to the lack of GPU acceleration.
Sounds reasonable. Lack of acceleration would make the GUI super slow. But instead of excluding them (who knows why people want to run Sierra? Maybe as a server where graphics don't matter?), why not put a warning in the patcher instead, saying something like "Warning: This machine is too slow to properly run macOS. Try at your own risk.".
I may like this solution, as a MacBook 4,1 owner. ;)
You might not like that solution right now either. I was working with MacBook 4,1 on Sierra already and the performance is so bad right now. None of the scripts I wrote for OSXE and MCPF work well like they did with Mavericks and Yosemite. I had to disable Photos and Maps as well as replace Quicktime. The processor heats up more often now too. Unless you're doing light work like web browsing or music and don't mind waiting 5+ seconds running certain apps, the only suitable options at this point to actually getting this model running efficiently is working on acceleration with Beta OpenGL frameworks or staying with Yosemite. I'll keep working on this model if you anyone wants to join me but I'm done with OpenGL after months of kernel and WindowServer failures.
[doublepost=1466559411][/doublepost]
i made a usb to boot from but it doesnt show up on the boot menu when i hold alt on my 5,1 Macbook Pro
Which patch did you use?
 
Last edited:
Wifi is the only issue at this point. And yes, it should work on both of those machines.

Very nice work! I think you're the first to make a patch so far. Sadly, the 1,1/2,1 Mac Pros have a ways to go, since they need to meet some CPU requirement that I have seen referenced on MacRumors lately. BTW, what's the deal with 2007 iMacs and MacBook Pros? Are they physically not able to use the patch? Our 2007 MaBook Pro 17" has a better GPU and CPU than my 2009 MacBook Pro, so it can run Sierra better, if it can do so under the patch.
 
Very nice work! I think you're the first to make a patch so far. Sadly, the 1,1/2,1 Mac Pros have a ways to go, since they need to meet some CPU requirement that I have seen referenced on MacRumors lately. BTW, what's the deal with 2007 iMacs and MacBook Pros? Are they physically not able to use the patch? Our 2007 MaBook Pro 17" has a better GPU and CPU than my 2009 MacBook Pro, so it can run Sierra better, if it can do so under the patch.
The 2007 MacBook Pro and iMac models which were previously supported in El Capitan have the same CPU limitation present in the 2006/2007 Mac Pros.
 
Yeah, I noticed this. As such, I have disabled the HDMI audio patch by default for all models in the post-install tool.

Wow that's dangerous. I know why it happens.

The HDMI Audio Support Injector was made by the Hackintosh community, to enable OS X to see the HDMI Audio Out on their modern PC graphics cards.

Therefore the extension is very generic, specifying that a "device class == Nvidia or ATI" supports HDMI Audio. It's only meant to be used if you are very sure that your card supports HDMI audio.

If you install that extension, your graphics card will always try to load an audio passthrough driver even if it's a very old graphics card that has no audio chip.

And if the card doesn't actually support HDMI audio... well, then OS X gives up initializing the audio device, and apparently gives up all other audio outputs too... :/
[doublepost=1466567883][/doublepost]@TMRJIJ: Maybe the Sierra GUI will run well when NVIDIA's Web Driver supports Sierra. They've got Metal support in that driver, which may help you out.
 
Wow that's dangerous. I know why it happens.

The HDMI Audio Support Injector was made by the Hackintosh community, to enable OS X to see the HDMI Audio Out on their modern PC graphics cards.

Therefore the extension is very generic, specifying that a "device class == Nvidia or ATI" supports HDMI Audio. It's only meant to be used if you are very sure that your card supports HDMI audio.

If you install that extension, your graphics card will always try to load an audio passthrough driver even if it's a very old graphics card that has no audio chip.

And if the card doesn't actually support HDMI audio... well, then OS X gives up initializing the audio device, and apparently gives up all other audio outputs too... :/
[doublepost=1466567883][/doublepost]@TMRJIJ: Maybe the Sierra GUI will run well when NVIDIA's Web Driver supports Sierra. They've got Metal support in that driver, which may help you out.
Good catch, we should edit the kext to only include certain PCI devices
[doublepost=1466570101][/doublepost]
The 2007 MacBook Pro and iMac models which were previously supported in El Capitan have the same CPU limitation present in the 2006/2007 Mac Pros.
I don't think this CPU limitation will ever be overcome. SSE4 is VERY different semantically from SS(S)E3. Emulating those instructions would incur a huge performance penalty, akin to floating point emulation. Given that even launchd uses SSE4, this would cripple the whole system. (Emulating SSE3 using SSE2, while slow, was much easier due to similar data sizes and other tidbits)
 
Last edited:
You might not like that solution right now either. I was working with MacBook 4,1 on Sierra already and the performance is so bad right now. None of the scripts I wrote for OSXE and MCPF work well like they did with Mavericks and Yosemite. I had to disable Photos and Maps as well as replace Quicktime. The processor heats up more often now too. Unless you're doing light work like web browsing or music and don't mind waiting 5+ seconds running certain apps, the only suitable options at this point to actually getting this model running efficiently is working on acceleration with Beta OpenGL frameworks or staying with Yosemite. I'll keep working on this model if you anyone wants to join me but I'm done with OpenGL after months of kernel and WindowServer failures.
[doublepost=1466559411][/doublepost]
Which patch did you use?

.......How did you get Sierra on a MacBook 4,1? And surely if we can work out the bugs in Sierra quickly, we can make a suitable X3100 kext. I remember Mavericks on my MacBook 4,1. God if I hadn't needed to upgrade I wouldn't have. But no seriously how'd you get past SIP?
 
  • Like
Reactions: pulker
On MacBookPro4,1 the following things required to make everithyng working:
- "-no_compat_check" to com.apple.Boot.plist
- "LegacyUSBInjector.kext" to Extensions
- Replace WiFi with a supported one

This machine running pretty fine Sierra without any more modification. (Trackpad, multitouch gestures, ambient light sensor, digital audio output, keyboard backlight seems to working fine).
 
I have followed both the written instructions and video. On restarting to boot from USB, the grey load bar gets about half way then i get a prohibitory sign.

My setup:
- macOS Sierra Patcher runs successfully
- Ran on two separate copies of 10.12 incase of corrupt files.
- Using OS X El Capitan‎ on a Late 2008 unibody mac.
- USB3 drive with 16gb.

Any ideas? Thank you.
 
Last edited:
The 2007 MacBook Pro and iMac models which were previously supported in El Capitan have the same CPU limitation present in the 2006/2007 Mac Pros.

Dang... I hope that can somehow be bypassed, however difficult it might be to do. Scary that this could be the end of all of these machines.
 
The table on the 1st post says:
iMac mid-2007 (iMac7,1) - Very hard, unsupported Merom CPU, Can upgrade to Penryn. Also BCM4321

If anyone has managed to get this machine working with Sierra, please let me know! I'd like to get at least 10 years out of this machine, even if it means hardware upgrades.
 
The table on the 1st post says:
iMac mid-2007 (iMac7,1) - Very hard, unsupported Merom CPU, Can upgrade to Penryn. Also BCM4321

If anyone has managed to get this machine working with Sierra, please let me know! I'd like to get at least 10 years out of this machine, even if it means hardware upgrades.

You can simply install it with the available tools after the CPU and WiFi card replacement.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.