How many instances of boot.efi are there in the Recovery partition? If there are two, have you replaced both of them with Pike's boot.efi? Are there any hardware limitations in one or more plists in the Recovery partition?
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.
Resolved 2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite
- Thread starter Mr. Zarniwoop
- Start date
- Sort by reaction score
How many instances of boot.efi are there in the Recovery partition? If there are two, have you replaced both of them with Pike's boot.efi? Are there any hardware limitations in one or more plists in the Recovery partition?
only one boot.efi on the recovery partition. but there's also the BaseSystem.dmg which has a boot.efi in /usr/standalone/i386/
https://forums.macrumors.com/posts/20075579/
Are the permissions of boot.efi in the Recovery partition correct? Does it belong to root (with read, write & execute rights) of group wheel (with read rights) and read rights for everyone else? Does it require any flags, such as uchg?
That's only necessary when creating the patched installer. Does not have any impact on installed OS. Never had to do that on any MP I upgraded.
Oh, right.
That is true!
----------
NICE JOB. Just whoa!
YouTube video with my Mac Pro 1,1 booting into Yosemite, like a champ.
Here we go:
http://youtu.be/_XaAMe2bDPg
hammid, have a look at the most recent comment posted by piker:
https://pikeralpha.wordpress.com/2014/10/09/lzvn-packed-apple-logos/#comments
Is there a fix to the "WIFI: No Hardware" issue?
Did the IO80211Family.kext atheros via kext installer but no progress. I had to swap some files from "Preference>SystemConfig in order to show the missing Wifi option in the "SystemPreference>Network".
SL
Did the IO80211Family.kext atheros via kext installer but no progress. I had to swap some files from "Preference>SystemConfig in order to show the missing Wifi option in the "SystemPreference>Network".
SL
What is the best when I want to upgrade my actual Mavericks partition to Yosemite ?
1) I install Yosemite directly on my Mavericks partition
2) Since I have a clone of the Mavericks partition, I install Yosemite from scratch and I use the Migration assistant to recover all my data and applications.
My Mavericks partition is a 120 Gb SSD drive and contains mainly the system. My documents are on another drive. I have a Mac Pro rev 1,1
Thank you
1) I install Yosemite directly on my Mavericks partition
2) Since I have a clone of the Mavericks partition, I install Yosemite from scratch and I use the Migration assistant to recover all my data and applications.
My Mavericks partition is a 120 Gb SSD drive and contains mainly the system. My documents are on another drive. I have a Mac Pro rev 1,1
Thank you
I'd recommend to go with the second solution you mentioned. do a fresh install and then restore the data and settings.
This individual reported this glaring inconsistency the other day and so far from what I can tell, it seems to have been overlooked however the latest Build 6c697848ef and the new version of Little Snitch 3.4.1 do not work together at all. With Build 6c697848ef and Little Snitch 3.4.1 installed, my OS X 10.9.5 Mavericks drive booted and rebooted in a continuos loop non stop. Reinstalling Tiamo's boot.efi solved the problem immediately.
I purposely used my OS X 10.9.5 Mavericks system so that I would be able to gauge whether or not it is a Little Snitch glitch or an issue with Build 6c697848ef boot.efi and the fact that Tiamo's build does not exhibit the same behavior is the clincher.
2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite
Well he said that he was having an issue with LS 3.4.1 on Mavericks with Tiamo's boot.efi. The issue is the 3.4.1 update.
Well he said that he was having an issue with LS 3.4.1 on Mavericks with Tiamo's boot.efi. The issue is the 3.4.1 update.
Maybe I am over looking something in his statement however I have tested this thoroughly and I can state with all certainty that OS X 10.9.5 + Tiamo's boot.efi + Little Snitch 3.4.1 boot with no issue whatsoever at all. Conversely, OS X 10.9.5 + Build 6c697848ef boot.efi + Little Snitch 3.4.1 will not boot. It will only cycle through a continuous loop.
By the way, are Hennesie's "Boot Black.zip" and "Boot Grey.zip" incarnations of build 6c697848ef, or are they different builds that don't exhibit this problem?
Not exactly Hennesie
With Mavericks and Tiamo's boot it was the same problem when i wanted to update LS at this time it was 3.2
The issue is any update of LS when using any modified boot.efi under Maverick or Yosemite.
2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite
My builds are just what I have compiled using the source code. They are 6C6978 builds.
----------
OK well you only mentioned 3.4 and 3.4.1 so I assumed you were using 3.4 then updating to 3.4.1 caused the problem. I understand the problem now.
Did you ever try resetting the PRAM when it wouldn't boot?
My builds are just what I have compiled using the source code. They are 6C6978 builds.
----------
Not exactly Hennesie
With Mavericks and Tiamo's boot it was the same problem when i wanted to update LS at this time it was 3.2
The issue is any update of LS when using any modified boot.efi under Maverick or Yosemite.
OK well you only mentioned 3.4 and 3.4.1 so I assumed you were using 3.4 then updating to 3.4.1 caused the problem. I understand the problem now.
Did you ever try resetting the PRAM when it wouldn't boot?
Yeap i did it but no changes, the sole solution is to reinstall modified boot.efi and to go back to backup ...
If i don't do any LS update LS is working well, under Chameleon there was not any problem when updating LS in Yosemite.
Last edited:
Do either of them exhibit any incompatibility between Mavericks/Yosemite and LS 3.4.1 on an early Mac Pro? Oddly enough, if 6C6978 is the same build as 6c697848ef, there's something I don't understand: "Your" boot.efi ("Boot Black") and "my" boot.efi exhibit differences in nearly 400 bytes. I mean their value; the file size is the same.
Well I'll dig on Permissions but I mount the Base System with a shadow file, patch it the way I did before (did not change the script only the target)
I replace the boot.efi, patch the Platform support copy the Kernel.
then I create a new DMG from the shadow file which the one I clone the USB stick with and which I then copyon the stick. I also do the Packages folder copy once asr is done and patch the mpkg.
As of writing, I'm thinking that there is a BaseSystem SHA1 MD5 in this mpkg, and I did changed it but with the too large UDZO 568 Mo file. I did not change the SHA1 with the BaseSystem.dmg I finally used...
Concerning Permissions I assume they're correct as it is something I think I do correctly from the script - But I'll double check.
I'll work on it tonight, and hopefully I'll succeed.
I'll keep the forum posted of course.
I haven't tried them with LS, I don't use it. What are your settings when compiling?
Release/Win32. Untouched source code. I DO use LS, but I still have to update to 3.4.1, but I wouldn't like to brick my Mac Pro when installing Yosemite. That would be a show stopper.
The only explanation for that I can think of would be that, somehow, we compiled from slightly different source code believing it to be build 6c697848ef, but the GitHub server provided the wrong ZIP file to one of us. Would that be possible?
Here's my build of 6c697848ef, in case someone wants to check compatibility with LS 3.4.1.