Hennesie2000: It should power on without the front fan. All's you are trying to do if see if it will at least power up.
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
Hi,
How is this different than the one posted by mike boss on post #1502?
What is LZVN?
Thanks
2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite
This one has the debug output removed. LZVN is the compression used.
https://github.com/Piker-Alpha/macosxbootloader/commits/master
The mikeboss one was commit 2c199833. I will be updating my guide with new black and grey versions later today.
This one has the debug output removed. LZVN is the compression used.
https://github.com/Piker-Alpha/macosxbootloader/commits/master
The mikeboss one was commit 2c199833. I will be updating my guide with new black and grey versions later today.
I'm pretty sure mine's f519966. my binary has a timestamp from october the 26th and 2c199833 was published yesterday.
I've tested your build and have also tested one of my own that, oddly enough, is not entirely identical, but both behave similarly. Neither of them will boot the Yosemite Recovery HD if you press Option after the initial chime and then select Recovery 10.10. If you do that, they simply boot the regular Yosemite partition. However, if you press Cmd-R immediately after the chime, both boot the Yosemite Recovery HD without any trouble. They are both non-verbose, naturally, and show the black background with the white Apple logo and the progress bar.
Weird. I tested yesterday commit (title: Cleanup) and it worked with option in BootX without problems. Did you chmod -R 775 boot.efi on recovery partition or just chown root:wheel? I did both.
I can't test today commit because I had to move the SSD to another machine and erase it. Will try to install on another drive in a spare time.
I know, I'm nitpicking... actually it should be chmod 644
this whole thing with COMMAND-R and/or OPTION is very odd. I never use CMD-R, I always tested the OPTION method only.Hey,
I checked my ram with the systeminformations-app and I looked at the vendor ids according to the memtest-app (which btw crashes after a minute - I think something is wrong with the implementation).
With system informations output I can see that every RAM is installed as pair.
I have tested the machine with Lion and so far no crash yet.
But it is a strange kind of issue, sometimes the Mac works for two days and sometimes it crashes after every standby.
It is possible to figure out if the crash is related to Mavericks or Yosemite?
Thanks a lot
I know, I'm nitpicking... actually it should be chmod 644
I made boot.efi to owned by root, and group wheel, with access to everybody. I tried two sets of permissions:
1. read, write and execute for root, read and execute for wheel, read and execute for everybody.
2. read and execute for root, read for wheel, read for everybody.
In both cases, the result was the same: both work with Cmd-R. Neither works with Option + Recovery 10.10, as the regular Yosemite partition is booted. I haven't changed the kernel cache of the Recovery HD, neither have I altered any other files or disk images therein.
Edit: The second set of permissions was read and WRITE for root, read for wheel, read for everybody.
Last edited:
I know, I'm nitpicking... actually it should be chmod 644
Good point, this is how original permissions are set. However I use 775, like for kexts. Don't ask why
Same here and option worked for me like I said before (yesterday). I did a clean install, activated TRIM, replaced boot.efi on main and recovery partitions and set permissions. That's all. Confusing...
New boot.efi files for black and grey. Commit 2ed42fe. My guide on the first page has been updated with the new links.
Last edited:
I am 95% sure it is the power supply. I think I am going to try and find a working complete machine, hopefully under $200, that I can strip for parts. When pressing the diagnostic button behind the memory cage the trickle LED should light up if the power supply is working and it doesn't. With out the trickle of power provided to the board then it won't start at all like it is doing.
If it isn't the power supply then I can just swap my stuff (x5365's, GPU, hdds, etc) over to the new machine and I'll be good to go.
I'm still debating going the full hackintosh route though. I have gotten pretty good at setting them up quickly and I am currently using a computer that I got for free (core 2 duo @ 3.0GHz, 4GB 800MHz ram) as a Yosemite hackintosh and I just booted up the HDD that I was using in my Mac Pro. It is working great, a little slow, but it will do until I either build something or fix the Mac Pro.
I do hope you fix the Mac Pro. We want to have you on board for whatever comes after Yosemite!
Fully Working Recovery HD 10.10
Greetings, all.
Multiple personal tries to get a successful boot into Recover HD 10.10 met with no success with the latest release from Pike compiled in VisualStudio2013, until it was sussed that the "Release" channel (thx mikeboss) was requisite for successful boot into the Recovery environment.
Replacement of the boot.efi in the Recovery HD 10.10/com.apple.recovery.boot/ partition with the latest Piker release achieved a successful boot via Cmd+R, but an un-successful boot via re-boot -> Option -> Recovery HD 10.10
The incorporation of the latest release of Piker's source-compiled boot.efi into /Volumes/Recovery\ HD/com.apple.recovery.boot/BaseSystem.dmg leads to the successful boot into the Recovery environment via both Cmd+R /and/ re-boot -> Option -> Recovery HD 10.10
For those of you interested, abbreviated terminal commands are as follows:
sudo -i
hdiutil attach /Volumes/some/folder/InstallESD.dmg
(mount the stock InstallESD.dmg (extracted from Install OSX Yosemite.app, etc., &c.))
hdiutil convert /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg -format UDRW -o /Volumes/temp/folder/BaseSystem.dmg
cp /Volumes/temp/folder/BaseSystem.dmg /Volumes/temp/folder/BaseSystem_copy.dmg
(this enables r/w status)
delete /Volumes/temp/folder/BaseSystem.dmg
rename /Volumes/temp/folder/BaseSystem_copy.dmg > BaseSystem.dmg
hdiutil attach /Volumes/temp/folder/BaseSystem.dmg
(mount BaseSystem.dmg)
cp new_boot.efi over old_boot.efi in /System/CoreServices/ and /usr/Standalone/
edit PlatformSupport.plist in /System/CoreServices/ and /System/CoreServices/com.apple.recovery.boot/
(to support your system (may not be necessary, but WTF))
modify permissions, as needed
(expansion is better than reduction (adherence to original privileges seem not necessary)
hdiutil detach /Volumes/temp/folder/BaseSystem.dmg
hdiutil convert /Volumes/temp/folder/BaseSystem.dmg -format UDZO -imagekey zlib-level=9 -o /Volumes/temp/folder/BaseSystemNew.dmg
(critical to CRC32 validation and size-reduction (Recovery HD is _tiny_))
rm /Volumes/temp/folder/BaseSystem.dmg
cp /Volumes/temp/folder/BaseSystemNew.dmg /Volumes/temp/folder/BaseSystem.dmg
rm /Volumes/Recovery\ HD/com.apple.recovery.boot/BaseSystem.dmg
empty the Recycle Bin
(necessary to allow space on /Recovery\HD)
cp /Volumes/temp/folder/BaseSystem.dmg /Volumes/Recovery\ HD/com.apple.recovery.boot/BaseSystem.dmg
Now, one can re-boot into the Recovery HD 10.10 with both Cmd+R /and/ re-boot -> Option -> Recovery HD 10.10
It may be that I have transcribed these details with errors, so I beg forgiveness if something does not work as expected...You know what works, and where I may have made a mis-take <s>
Enjoy.
Regards, splifingate
Greetings, all.
Multiple personal tries to get a successful boot into Recover HD 10.10 met with no success with the latest release from Pike compiled in VisualStudio2013, until it was sussed that the "Release" channel (thx mikeboss) was requisite for successful boot into the Recovery environment.
Replacement of the boot.efi in the Recovery HD 10.10/com.apple.recovery.boot/ partition with the latest Piker release achieved a successful boot via Cmd+R, but an un-successful boot via re-boot -> Option -> Recovery HD 10.10
The incorporation of the latest release of Piker's source-compiled boot.efi into /Volumes/Recovery\ HD/com.apple.recovery.boot/BaseSystem.dmg leads to the successful boot into the Recovery environment via both Cmd+R /and/ re-boot -> Option -> Recovery HD 10.10
For those of you interested, abbreviated terminal commands are as follows:
sudo -i
hdiutil attach /Volumes/some/folder/InstallESD.dmg
(mount the stock InstallESD.dmg (extracted from Install OSX Yosemite.app, etc., &c.))
hdiutil convert /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg -format UDRW -o /Volumes/temp/folder/BaseSystem.dmg
cp /Volumes/temp/folder/BaseSystem.dmg /Volumes/temp/folder/BaseSystem_copy.dmg
(this enables r/w status)
delete /Volumes/temp/folder/BaseSystem.dmg
rename /Volumes/temp/folder/BaseSystem_copy.dmg > BaseSystem.dmg
hdiutil attach /Volumes/temp/folder/BaseSystem.dmg
(mount BaseSystem.dmg)
cp new_boot.efi over old_boot.efi in /System/CoreServices/ and /usr/Standalone/
edit PlatformSupport.plist in /System/CoreServices/ and /System/CoreServices/com.apple.recovery.boot/
(to support your system (may not be necessary, but WTF))
modify permissions, as needed
(expansion is better than reduction (adherence to original privileges seem not necessary)
hdiutil detach /Volumes/temp/folder/BaseSystem.dmg
hdiutil convert /Volumes/temp/folder/BaseSystem.dmg -format UDZO -imagekey zlib-level=9 -o /Volumes/temp/folder/BaseSystemNew.dmg
(critical to CRC32 validation and size-reduction (Recovery HD is _tiny_))
rm /Volumes/temp/folder/BaseSystem.dmg
cp /Volumes/temp/folder/BaseSystemNew.dmg /Volumes/temp/folder/BaseSystem.dmg
rm /Volumes/Recovery\ HD/com.apple.recovery.boot/BaseSystem.dmg
empty the Recycle Bin
(necessary to allow space on /Recovery\HD)
cp /Volumes/temp/folder/BaseSystem.dmg /Volumes/Recovery\ HD/com.apple.recovery.boot/BaseSystem.dmg
Now, one can re-boot into the Recovery HD 10.10 with both Cmd+R /and/ re-boot -> Option -> Recovery HD 10.10
It may be that I have transcribed these details with errors, so I beg forgiveness if something does not work as expected...You know what works, and where I may have made a mis-take <s>
Enjoy.
Regards, splifingate
No more USB errata since then, with no known cause, or reason.
SMC-FC has been a God-Send.
Mac Pro is noisier, but, well, cooler, because of such.
I've probably performed less than half the reboots you've done, and (to this date) only one memory stick out of eight has thrown a fail.
Re-moval and re-insertion of said proved success (no subsequent red-leds on the Riser), but I lie waiting for The failure point . . . .
I hope you get your system fully functional; sooner, rather than later.
Props, H.
Regards, splifingate
In case you want a replacement PSU, I found 2 for you near your area.
http://www.ebay.com/itm/Apple-Mac-P...-/321563461792?pt=PCA_UPS&hash=item4adead08a0
http://www.ebay.com/itm/Apple-Mac-P...131003132420&rk=3&rkt=6&sd=321563461792&rt=nc
Good luck Hennesie and thanks for all the effort about the Guide and all who is involved.
PS: We could create a website/blog to put all info and files up there, all in one place with Donation buttons to whom deserves some cash for his time and knowledge or just for a beer
iStat Menu report
hey guys,
I didn't quite know where to put this so as I'm running Yosemite on my 1,1 this thread felt like an ideal place
Here's a report from iStat Menu (I'm not doing anything intensive right now, just reading mail and safari). As I read in another thread about amps and voltage stats, looking at mine got me wondering. I know all our machines run differently and that a 1,1 will mostly consume more power than a more recent model etc. Having said that, what do you guys make of these numbers? Should I be worried? (I should mention that my mac runs flawlessly and perfectly, I'm just a little obsessed with iStat in general)
hey guys,
I didn't quite know where to put this so as I'm running Yosemite on my 1,1 this thread felt like an ideal place
Here's a report from iStat Menu (I'm not doing anything intensive right now, just reading mail and safari). As I read in another thread about amps and voltage stats, looking at mine got me wondering. I know all our machines run differently and that a 1,1 will mostly consume more power than a more recent model etc. Having said that, what do you guys make of these numbers? Should I be worried? (I should mention that my mac runs flawlessly and perfectly, I'm just a little obsessed with iStat in general
)Attachments
Might you still possess the none edited verbose output of this build and if so could you please post a link ? While this particular build did indeed boot my Recovery HD, oddly I have not been able to boot my Yosemite operating system HD with anything other then your very first (literally) Pike Alpha Verbose build compiled weeks ago. I am uncertain if it has anything to do with my system now booting from a SSD HD or not though quite frankly, in that I have found a way that just simply works consistently and as the additional visual aesthetics are unimportant trouble shooting the issue is of no interest to me. I am just hoping to eliminate as much confusion on my on behalf as possible in using the same compiled boot.efi version on both my OS HD as well as my Recovery HD.
2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite
https://forums.macrumors.com/showpost.php?p=20227330
These are forced verbose. Commit 2c199833. If you want me to build you a specific commit just let me know the number.
https://forums.macrumors.com/showpost.php?p=20227330
These are forced verbose. Commit 2c199833. If you want me to build you a specific commit just let me know the number.