Sierra on the iMac is running with your "Sierra4You_v0.1" so no additional things done (like HMI Audio or something).Even with this kext?
I'm having the same issue on my MacBookPro5,3Any one had problems installing apps from the App Store? I can't install any on my MacBook 5,2
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.".
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'm having the same issue on my MacBookPro5,3
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
Yeah, I noticed this. As such, I have disabled the HDMI audio patch by default for all models in the post-install tool.@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.
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..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
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.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.
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.".
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.I may like this solution, as a MacBook 4,1 owner.![]()
Which patch did you use?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
Wifi is the only issue at this point. And yes, it should work on both of those machines.
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.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 CPU in the iMac can be upgraded to a compatible one.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.
Good catch, we should edit the kext to only include certain PCI devicesWow 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.
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)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.
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?
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.
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.