Resolved 2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite

[Hennesie2000]

But surely the card still works with OS X as long as there is a driver for the card? And the drivers are regularly updated as well, right?

It does work but some people are having issues with certain ports on the card not working but it varies and often the hackintosh systems with problems are poorly configured. The drivers are updated often but you have to wait for the drivers to update before you can update the OS or you will end up with a non-booting machine since there is no native support to fallback on. The drivers have checks for the build number of OS X so if that changes they stop loading. This happened a lot with the security updates from 10.10.2.

 

[SuperKerem]

It does work but some people are having issues with certain ports on the card not working but it varies and often the hackintosh systems with problems are poorly configured. The drivers are updated often but you have to wait for the drivers to update before you can update the OS or you will end up with a non-booting machine since there is no native support to fallback on. The drivers have checks for the build number of OS X so if that changes they stop loading. This happened a lot with the security updates from 10.10.2.

If this happened, it would be especially bad because the stock MP card doesn't support Yosemite! :O

 

[Hennesie2000]

If this happened, it would be especially bad because the stock MP card doesn't support Yosemite! :O

This is one reason I suggested using Clover. You can usually still boot using the flag nv_disable=1 and then update the driver when it is released, generally a day after the OS update is released.

 

[DirtynNerdy]

Hung parts help.

Disk Utility, system pref seems to all hang randomly. Sometime I check them both and they are hung. If I reboot everything is fine. This also keeps me from ejecting my DVD rom. Disc or not disc.

 

[NOTNlCE]

And then, out of nowhere, my RAID 1 array just boots up with Yosemite. So strange. Anyone know what the heck goes on with these?

 

[Onward42]

lost on the path

Trying to follow the advice/guidance of how to get Yosemite on my mac pro 2,1 (late 2007).

Bought geforce 120 video card for pre-Yosemite preparation.

Have installed--but no display/just blank/black.

Any idea how to fix/get back on the path?

Thanks!

 

[tbarhorst]

10.10.3 Update

I upgraded my MacPro 1,1 with ATI Radeon HD 5770, running Yosemite 10.10 using the SFOTT script (Tiamo's boot.efi) . Everything works well.

How do I get to 10.10.3 (and higher in the future) without overwriting boot.efi?

Will PikeYoseFix work in this case? Or are there other scripts or solutions that will suffice? I am tired of worrying about Apple updates making my nice old MacPro not boot.

 

[Hennesie2000]

I upgraded my MacPro 1,1 with ATI Radeon HD 5770, running Yosemite 10.10 using the SFOTT script (Tiamo's boot.efi) . Everything works well.



How do I get to 10.10.3 (and higher in the future) without overwriting boot.efi?



Will PikeYoseFix work in this case? Or are there other scripts or solutions that will suffice? I am tired of worrying about Apple updates making my nice old MacPro not boot.

Use the PikeYoseFix script for Yosemite.

 

[Antoni Nygaard]

I just reinstalled Yosemite 10.10.3 from scratch using another Mac onto the hard drive using target mode on the mac pro then copying the boot.efi file over to the two places it schould be, but when the machines reboots and the apple logo comes and the loading bar it is crawling slowly up to 50% then stops.. I have tried installing a few times made a USB and downloaded yosemite again from the app store. I tried booting in verbose mode and it stops at every time at this:

Warning: couldn't block sleep during cache update
Warning: proceeding w/o DiskArb
/dev/disk0s2 on / (hfs, local, Journaled)
BootCacheControl: Unable to open /var/db/BootCache.playlist: 2 No such file or directory
bash: /etc/rc.server: No such file or directory
bash /etc/rc.installer_Cleanup: No such file or directory.


anybody that has a solution? It has always worked for me.


EDIT: Fixed it by downloading the pre patchet image on the front page

 

[Rocketman83]

Kernel Extraction Error

I'm trying to create a bootable installation USB drive using MacRumors member Hennessie2000's Yosemite Install Guide - boot.efi method, but I keep getting the following error message when trying to extract the kernel from the Essential.pkg file, using Pacifist.

The file “file:///Volumes/Installer/Pacifist%20Temp.9893/D7DE7052-5A45-47CE-B6CE-B06A08219052%20Contents/./System/Library/Kernels/kernel” does not exist.

Any ideas? Thanks.

 

[Hennesie2000]

2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite

I'm trying to create a bootable installation USB drive using MacRumors member Hennessie2000's Yosemite Install Guide - boot.efi method, but I keep getting the following error message when trying to extract the kernel from the Essential.pkg file, using Pacifist.



The file “file:///Volumes/Installer/Pacifist%20Temp.9893/D7DE7052-5A45-47CE-B6CE-B06A08219052%20Contents/./System/Library/Kernels/kernel” does not exist.



Any ideas? Thanks.

Try extracting the whole folder. Or, a few pages back or so I posted the kernel file.

 

[Rocketman83]

Kernel Extraction Error

Thanks for your help, Hennessie2000. If I extract the entire Essentials.pkg file, where should I extract it to? And once I extract it, can I then just copy the kernel to the required location on the USB drive?

I did see the February post where you said you would later post the kernel file, but I couldn't find that post on this forum. Do you happen to have that post number?

 

[Hennesie2000]

2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite

Thanks for your help, Hennessie2000. If I extract the entire Essentials.pkg file, where should I extract it to? And once I extract it, can I then just copy the kernel to the required location on the USB drive?



I did see the February post where you said you would later post the kernel file, but I couldn't find that post on this forum. Do you happen to have that post number?

Not all that, just the Kernels folder

https://copy.com/UhlWrUCDGZilVttN

 

[Rocketman83]

Thanks, Hennessie2000. I saved the revised kernel from the link you provided and was able to copy it to the properly designated folder. Later today, I will try to install Yosemite from the completed USB installation drive.

One other note: Under Step 17 of your Yosemite Install Guide, I made two additional edits to the PlatformSupport.plist (in the System/Library/CoreServices folder). I typed in MacPro1,1 and MacPro2,1 (on separate lines) at the end of the supported machines list, using the given syntax format. Not sure if this is necessary, but it made sense to me to include these machines in the list.

 

[Rocketman83]

Btw, my machine is a MacPro 2,1, upgraded from a 1,1.

 

[Rocketman83]

2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite

Not all that, just the Kernels folder

https://copy.com/UhlWrUCDGZilVttN

I tried installing Yosemite from the newly created installation USB drive. The black boot screen appeared and showed some movement along the progress meter. But after a short while, a light gray screen appeared, and then a message in various languages saying to restart. I rebooted, but the same cycle of events occurred again.

In OS X Lion, the mounted USB drive is labeled (by me) as "Installer". The drive icon is colored white. Attached is a screenshot showing the contents of this USB drive. At the boot up screen, the USB drive is labeled as "BaseSystem.dmg", and the drive icon color is yellow and orange.

My goal is to install Yosemite on my Mac Pro's empty SSD drive, and retain my existing Lion installation on a separate 3.5" SATA disk drive. TRIM is already enabled on the empty SSD drive.

Any other suggestions for a successful Yosemite installation would be most appreciated.

 

[Uncle Terry]

.

 

[Uncle Terry]

Just wanted to say a huge thank you. I successfully upgraded my 2006 Mac 1,1 to run Yosemite 10.10.3 without a hitch. Even iMessage is working. I used the pre-patched Piker-Alpha installer and added the PikeYose Fix. The process went smoother than an eel in a bath full of KY jelly. Thanks again.

 

[Lee Joramo]

I have a Mac Pro 1,1 (4GB RAM, NVIDIA GeForce GT 120 from MacVidCard) that I am trying to upgrade from Lion 10.7.5 to Yosemite 10.10.3.

I have attempted 3 upgrade methods:

• Clean Install of a Yosemite to an external drive from a MacMini and swapped in Pike's boot.efi. This initially crashed on the white Apple on black background screen. Reboots resulted in a flashing question mark folder.
• The SFOTT method run from the MacPro. This gave me a white Apple on black with a verbose mode startup ending in a kernel panic. I saw that the last loaded kext was related to RAID. I pulled the two mirrored RAID drives leaving a SSD for the system. Repeated restarts resulted in a kernel panic with com.apple.driver.AppleUSBHIDMouse being the last loaded kext.
• Finally I tried the pre-built Yosemite installer from Hennesie2000, and ended up with the same repeated crash on loading the AppleUSBHIDMouse.

Any suggestions? I know that kernel crashes can be very difficult to diagnose

 

[MaCXyLo]

Heyyo Dudes,
i automized a script to repair the recovery partition
- done it several times on a mac pro 1,1
- so i had no lust to do it over and over again after every update per hand.
can someone try the script out to confirm that it works well?
the only thing what made me concerns are the permissions.
maybe somone can proof them before and after execution.

Warning:
Please proof with 'diskutil list' if the script is executed on the right partition.

#!/bin/bash
sudo su
diskutil mount /dev/disk0s3
cd /Volumes/Recovery\ HD/com.apple.recovery.boot/
/usr/libexec/PlistBuddy -c "Add :SupportedBoardIds: string 'Mac-F4208DC8'" PlatformSupport.plist
/usr/libexec/PlistBuddy -c "Add :SupportedBoardIds: string 'Mac-F4208DA9'" PlatformSupport.plist
/usr/libexec/PlistBuddy -c "Add :SupportedModelProperties: string 'MacPro1,1'" PlatformSupport.plist
/usr/libexec/PlistBuddy -c "Add :SupportedModelProperties: string 'MacPro2,1'" PlatformSupport.plist
hdiutil convert BaseSystem.dmg -format UDRW -o ~/Downloads/BaseSystemUDRW.dmg
cd ~/Downloads
chmod 777 BaseSystemUDRW.dmg
hdiutil attach -readwrite BaseSystemUDRW.dmg
# Piker-Alpha_bootloader_-_black_-_build_3b402a9
curl -o piker.zip 'https://forums.macrumors.com/attachments/boot-black-zip.511172/'
unzip piker.zip
chmod 644 boot.efi
cd /Volumes/OS\ X\ Base\ System/
rm -rf /System/Library/CoreServices/boot.efi
rm -rf /usr/standalone/i386/boot.efi
cp ~/Downloads/boot.efi /System/Library/CoreServices/
cp ~/Downloads/boot.efi /usr/standalone/i386/
cd /Volumes/OS\ X\ Base\ System/System/Library/CoreServices/
/usr/libexec/PlistBuddy -c "Add :SupportedBoardIds: string 'Mac-F4208DC8'" PlatformSupport.plist
/usr/libexec/PlistBuddy -c "Add :SupportedBoardIds: string 'Mac-F4208DA9'" PlatformSupport.plist
/usr/libexec/PlistBuddy -c "Add :SupportedModelProperties: string 'MacPro1,1'" PlatformSupport.plist
/usr/libexec/PlistBuddy -c "Add :SupportedModelProperties: string 'MacPro2,1'" PlatformSupport.plist
cd /Volumes/OS\ X\ Base\ System/System/Library/CoreServices/com.apple.recovery.boot/
/usr/libexec/PlistBuddy -c "Add :SupportedBoardIds: string 'Mac-F4208DC8'" PlatformSupport.plist
/usr/libexec/PlistBuddy -c "Add :SupportedBoardIds: string 'Mac-F4208DA9'" PlatformSupport.plist
/usr/libexec/PlistBuddy -c "Add :SupportedModelProperties: string 'MacPro1,1'" PlatformSupport.plist
/usr/libexec/PlistBuddy -c "Add :SupportedModelProperties: string 'MacPro2,1'" PlatformSupport.plist
hdiutil convert ~/Downloads/BaseSystemUDZW.dmg -format UDZO -imagekey zlib-level=9 -o BaseSystem.dmg
cd /Volumes/Recovery\ HD/com.apple.recovery.boot/
rm -rf boot.efi
rm -rf BaseSystem.dmg
cp ~/Downloads/boot.efi /
cp ~/Downloads/BaseSystem.dmg /
chflags uchg boot.efi

add execution permission in terminal to the script:
chmod +x repairrecovery.command
Execute it with doubleclick.

Thanks.

 

[sumer]

Heyyo Dudes,
i automized a script to repair the recovery partition
- done it several times on a mac pro 1,1
- so i had no lust to do it over and over again after every update per hand.
can someone try the script out to confirm that it works well?
the only thing what made me concerns are the permissions.
maybe somone can proof them before and after execution.

Warning:
Please proof with 'diskutil list' if the script is executed on the right partition.

#!/bin/bash
sudo su
diskutil mount /dev/disk0s3
cd /Volumes/Recovery\ HD/com.apple.recovery.boot/
/usr/libexec/PlistBuddy -c "Add :SupportedBoardIds: string 'Mac-F4208DC8'" PlatformSupport.plist
/usr/libexec/PlistBuddy -c "Add :SupportedBoardIds: string 'Mac-F4208DA9'" PlatformSupport.plist
/usr/libexec/PlistBuddy -c "Add :SupportedModelProperties: string 'MacPro1,1'" PlatformSupport.plist
/usr/libexec/PlistBuddy -c "Add :SupportedModelProperties: string 'MacPro2,1'" PlatformSupport.plist
hdiutil convert BaseSystem.dmg -format UDRW -o ~/Downloads/BaseSystemUDRW.dmg
cd ~/Downloads
chmod 777 BaseSystemUDRW.dmg
hdiutil attach -readwrite BaseSystemUDRW.dmg
# Piker-Alpha_bootloader_-_black_-_build_3b402a9
curl -o piker.zip 'https://forums.macrumors.com/attachments/boot-black-zip.511172/'
unzip piker.zip
chmod 644 boot.efi
cd /Volumes/OS\ X\ Base\ System/
rm -rf /System/Library/CoreServices/boot.efi
rm -rf /usr/standalone/i386/boot.efi
cp ~/Downloads/boot.efi /System/Library/CoreServices/
cp ~/Downloads/boot.efi /usr/standalone/i386/
cd /Volumes/OS\ X\ Base\ System/System/Library/CoreServices/
/usr/libexec/PlistBuddy -c "Add :SupportedBoardIds: string 'Mac-F4208DC8'" PlatformSupport.plist
/usr/libexec/PlistBuddy -c "Add :SupportedBoardIds: string 'Mac-F4208DA9'" PlatformSupport.plist
/usr/libexec/PlistBuddy -c "Add :SupportedModelProperties: string 'MacPro1,1'" PlatformSupport.plist
/usr/libexec/PlistBuddy -c "Add :SupportedModelProperties: string 'MacPro2,1'" PlatformSupport.plist
cd /Volumes/OS\ X\ Base\ System/System/Library/CoreServices/com.apple.recovery.boot/
/usr/libexec/PlistBuddy -c "Add :SupportedBoardIds: string 'Mac-F4208DC8'" PlatformSupport.plist
/usr/libexec/PlistBuddy -c "Add :SupportedBoardIds: string 'Mac-F4208DA9'" PlatformSupport.plist
/usr/libexec/PlistBuddy -c "Add :SupportedModelProperties: string 'MacPro1,1'" PlatformSupport.plist
/usr/libexec/PlistBuddy -c "Add :SupportedModelProperties: string 'MacPro2,1'" PlatformSupport.plist
hdiutil convert ~/Downloads/BaseSystemUDZW.dmg -format UDZO -imagekey zlib-level=9 -o BaseSystem.dmg
cd /Volumes/Recovery\ HD/com.apple.recovery.boot/
rm -rf boot.efi
rm -rf BaseSystem.dmg
cp ~/Downloads/boot.efi /
cp ~/Downloads/BaseSystem.dmg /
chflags uchg boot.efi

add execution permission in terminal to the script:
chmod +x repairrecovery.command
Execute it with doubleclick.

Thanks.

Does this only work for Yosemite? I don;t get the last part if I double click on the script and let it run after that do I then run chmod +x repairrecovery after that?

Cheers

 

[Hennesie2000]

Does this only work for Yosemite? I don;t get the last part if I double click on the script and let it run after that do I then run chmod +x repairrecovery after that?

Cheers

The chmod +x command turns the script into an executable file. You must do that before double clicking on it to run it.

 

[MaCXyLo]

Does this only work for Yosemite? I don;t get the last part if I double click on the script and let it run after that do I then run chmod +x repairrecovery after that?

Cheers

i test this only with yosemite - other osx versions: no guarantee

 

[irulz]

Hi,

I'm getting the system uptime in nanoseconds error. Can someone please help me fix this issue?

I've attached a screenshot of the error I'm getting. I've tried using the Chamelon method and the sfott method and get the same issue.

 

[Mjsais]

Use the PikeYoseFix script for Yosemite.

Is the PikeYose script the same as the Tiamo script but with the new boot.efi file? if not, what are the differences? I am clonning my Maverick disk, which has the tiamo script before attempting the upgrade to Yosemite. Thank you.