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

Hennesie2000 · Aug 6, 2014

atvusr said:
I did run the 'bless' command (as given in the Guide and with 'sudo') right after point 6 of the Chameleon installation. I've tried the 'bless' command again with double dashes for the options (as seen in the man pages) - same result, it still boots Windows automatically on the Bootcamp partition.

How can I change / swap the Boot priority between disk0 (internal SSD of the MBP) and disk1 (external SSD for Yosemite)?

You can't change what the disk identifier is and it will sometimes change by itself. The only way to get around it is to put Clover/Chameleon on the same HDD as Windows in the first partition. For example, my current setup is a single HDD with partitions in this order Mavericks/Clover/Win7 and Yosemite on another HDD. Before I had Clover on a second drive with Yosemite but if I wanted to boot Clover I had to pull my Mavericks/Win7 drive. To boot Mavericks with clover you have to remove the Tiamo boot.efi files and put back the originals.

If Clover and Windows are on the same drive you will also have to set the Clover/Chameleon partition as the active partition. This can be done using diskpart in Windows or fdisk in OS X.

----------

haralds said:
Clover is no go - no bootable disk found.

Restored Clover and it is working with all disks installed. But no iMessage...

The no bootable disk found with Clover on a GPT normally means that there isn't a hybrid MBR present.

haralds · Aug 6, 2014

Hennesie2000 said:
The no bootable disk found with Clover on a GPT normally means that there isn't a hybrid MBR present.

It should still have the hybrid MBR, but I will try one more time tonight setting it up explicitly.

Man, not sure why this has been so hard this time. When I did this with Mavericks prior to tiamo's boot.efi, it worked first try on the same system.

Hennesie2000 · Aug 6, 2014

haralds said:
It should still have the hybrid MBR, but I will try one more time tonight setting it up explicitly.

Man, not sure why this has been so hard this time. When I did this with Mavericks prior to tiamo's boot.efi, it worked first try on the same system.

If you re-installed clover or updated Yosemite while the clover partition was mounted then it might have written over the hybrid MBR. That happened to me a few times. Be sure to do the steps in my guide for the final setup which will keep the Clover/Chameleon partition from mounting on boot. It is just safer that way and I had no problems updating Yosemite after that.

haralds · Aug 6, 2014

Hennesie2000 said:
If you re-installed clover or updated Yosemite while the clover partition was mounted then it might have written over the hybrid MBR. That happened to me a few times. Be sure to do the steps in my guide for the final setup which will keep the Clover/Chameleon partition from mounting on boot. It is just safer that way and I had no problems updating Yosemite after that.

I was able to boot into Clover by pulling all other drives. I also rewrote the MBR prior to installing, which again writes the MBR.

But iMessage and FaceTime are still DOA.

Hennesie2000 · Aug 6, 2014

haralds said:
I was able to boot into Clover by pulling all other drives. I also rewrote the MBR prior to installing, which again writes the MBR.

But iMessage and FaceTime are still DOA.

Hmm, I have not had any issues with iMessage or FaceTime when using Clover. Neither would work with Chameleon unless I booted using Clover once.

haralds · Aug 6, 2014

Hennesie2000 said:
Hmm, I have not had any issues with iMessage or FaceTime when using Clover. Neither would work with Chameleon unless I booted using Clover once.

I even deleted my account and recreated it!

I am about done with this...

Hennesie2000 · Aug 6, 2014

haralds said:
I even deleted my account and recreated it!

I am about done with this...

have you tried just starting from scratch? Setup the hdd with the partitions; create the installer partition, install clover, setup the hybrid MBR and go from there and install Yosemite by booting the installer with clover. Just something to consider only takes me about 30mins to have an up and running Yosemite using one hdd and either Chameleon or Clover.

eddiescott · Aug 7, 2014

Install problem

I've followed the instructions in Msg 108 of this thread (twice) and although apparently successful in creating the usb stick, I get an "Error Loading Operating System" when I try to boot from the Windows volume.

Any ideas, anyone?

Hennesie2000 · Aug 7, 2014

eddiescott said:
I've followed the instructions in Msg 108 of this thread (twice) and although apparently successful in creating the usb stick, I get an "Error Loading Operating System" when I try to boot from the Windows volume.

Any ideas, anyone?

Here is a more manual and less terminal heavy method.

Right click on the downloaded Yosemite Installer app and click show package contents.
In terminal you will need to show hidden file using the following commands
Code:
```
$ defaults write com.apple.Finder AppleShowAllFiles YES
$ killall Finder
```
Browse to the folder /Contents/SharedSupport
Double-click to mount “InstallESD.dmg”
Open up Disk Utility and drag BaseSystem.dmg to the side bar in Disk Utility.
Click on BaseSystem.dmg in Disk Utility and select the Restore tab
Set the BaseSystem.dmg as the source and choose the 8GB Installer partition as the destination.
Rename the Installer partition back to "Installer" after restoring the disk image.
Once that is done use Finder to browse the newly restored Installer partition.
Browse to the folder /System/Installation on the Installer partition and delete the "Packages" alias file.
Go back to the mounted InstallESD.dmg and drag the "Packages" folder to the Installer partition into the /System/Installation folder where the alias file used to be.
Copy the "BaseSystem.dmg" and "BaseSystem.chunklist" files to the root of the Installer partition.
To hide the hidden files again run the previous 2 commands and change YES to NO

eddiescott · Aug 7, 2014

Progress....

After yesterday's failure, today I created the BOOT and Installer partitions on an internal hard drive. I can now boot into Clover and select the Installer to boot from.
I get the Apple logo with a progress bar, followed by the start of a verbose boot which gets to about a screenful before the system re-boots :-(

Progress, I guess.

haralds · Aug 11, 2014

Hennesie2000 said:
have you tried just starting from scratch? Setup the hdd with the partitions; create the installer partition, install clover, setup the hybrid MBR and go from there and install Yosemite by booting the installer with clover. Just something to consider only takes me about 30mins to have an up and running Yosemite using one hdd and either Chameleon or Clover.

Do you have any Boot Camp partitions? Is Clover able to retain precedence in booting. I have moved the clover disk to bay 1, but it still does not boot with the other drivers present, if they have Boot Camp.

Hennesie2000 · Aug 11, 2014

haralds said:
Do you have any Boot Camp partitions? Is Clover able to retain precedence in booting. I have moved the clover disk to bay 1, but it still does not boot with the other drivers present, if they have Boot Camp.

Just because a drive is in bay one doesn't mean that it will have a lower disk identifier.

I had Mavericks and Windows 7 on one HDD. What I ended up doing was splitting the Mavericks partition so I could add a 1gb partition between it and the windows partition using disk utility. There was already a hybrid MBR setup and when I added the partition it added the correct entry to the MBR so I didn't need to mess with that. I then installed clover on the new 1gb partition so that it would always be in front of the boot camp partition. Then using fdisk I set the new Clover partition to be the active partition. I still have Yosemite on a separate HDD but now using clover I can triple boot Mavericks, Yosemite and Windows 7.

Here is my diskutil list:

Code:

/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS BOOT                    942.7 MB   disk0s2
   3:                  Apple_HFS Installer               8.0 GB     disk0s3
   4:                  Apple_HFS Yosemite                490.0 GB   disk0s4
   5:                 Apple_Boot Recovery HD             650.0 MB   disk0s5
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                  Apple_HFS Mavericks               700.1 GB   disk1s2
   3:                  Apple_HFS Clover                  939.5 MB   disk1s3
   4:       Microsoft Basic Data Windows 7               298.7 GB   disk1s4

Clover is the partition I am using to boot Yosemite. The BOOT partition is what I was using but it is currently empty. NOTE: disk1 is actually in slot one but the machine identifies the disk in slot two as disk0.

This is the hybrid MBR on disk1:

Code:

Disk size is 1953525168 sectors (931.5 GiB)
MBR disk identifier: 0x54F1969F
MBR partitions:

Number  Boot  Start Sector   End Sector   Status      Code
   1                     1       409639   primary     0xEE
   2                409640   1367863295   primary     0xAF
   3      *     1368125440   1369960447   primary     0xAF
   4            1370222592   1953523711   primary     0x07

The asterisk on entry 3 signifies the active partition which makes it bootable and so that it boots before the 4th entry which is for the Windows partition.

haralds · Aug 11, 2014

Hennesie2000 said:
Just because a drive is in bay one doesn't mean that it will have a lower disk identifier.

I had Mavericks and Windows 7 on one HDD. What I ended up doing was splitting the Mavericks partition so I could add a 1gb partition between it and the windows partition using disk utility. There was already a hybrid MBR setup and when I added the partition it added the correct entry to the MBR so I didn't need to mess with that. I then installed clover on the new 1gb partition so that it would always be in front of the boot camp partition. Then using fdisk I set the new Clover partition to be the active partition. I still have Yosemite on a separate HDD but now using clover I can triple boot Mavericks, Yosemite and Windows 7.

Here is my diskutil list:

Code:

/dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_HFS BOOT 942.7 MB disk0s2 3: Apple_HFS Installer 8.0 GB disk0s3 4: Apple_HFS Yosemite 490.0 GB disk0s4 5: Apple_Boot Recovery HD 650.0 MB disk0s5 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk1 1: EFI EFI 209.7 MB disk1s1 2: Apple_HFS Mavericks 700.1 GB disk1s2 3: Apple_HFS Clover 939.5 MB disk1s3 4: Microsoft Basic Data Windows 7 298.7 GB disk1s4

Clover is the partition I am using to boot Yosemite. The BOOT partition is what I was using but it is currently empty. NOTE: disk1 is actually in slot one but the machine identifies the disk in slot two as disk0.

Yes, I noticed that.
I will try adding the partition to one of the other Windows bootcamp disks.

----------

Hennesie2000 said:
Just because a drive is in bay one doesn't mean that it will have a lower disk identifier.

I had Mavericks and Windows 7 on one HDD. What I ended up doing was splitting the Mavericks partition so I could add a 1gb partition between it and the windows partition using disk utility. There was already a hybrid MBR setup and when I added the partition it added the correct entry to the MBR so I didn't need to mess with that. I then installed clover on the new 1gb partition so that it would always be in front of the boot camp partition. Then using fdisk I set the new Clover partition to be the active partition. I still have Yosemite on a separate HDD but now using clover I can triple boot Mavericks, Yosemite and Windows 7.

Here is my diskutil list:

Code:

/dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_HFS BOOT 942.7 MB disk0s2 3: Apple_HFS Installer 8.0 GB disk0s3 4: Apple_HFS Yosemite 490.0 GB disk0s4 5: Apple_Boot Recovery HD 650.0 MB disk0s5 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk1 1: EFI EFI 209.7 MB disk1s1 2: Apple_HFS Mavericks 700.1 GB disk1s2 3: Apple_HFS Clover 939.5 MB disk1s3 4: Microsoft Basic Data Windows 7 298.7 GB disk1s4

Clover is the partition I am using to boot Yosemite. The BOOT partition is what I was using but it is currently empty. NOTE: disk1 is actually in slot one but the machine identifies the disk in slot two as disk0.

This is the hybrid MBR on disk1:

Code:

Disk size is 1953525168 sectors (931.5 GiB) MBR disk identifier: 0x54F1969F MBR partitions: Number Boot Start Sector End Sector Status Code 1 1 409639 primary 0xEE 2 409640 1367863295 primary 0xAF 3 * 1368125440 1369960447 primary 0xAF 4 1370222592 1953523711 primary 0x07

First of all, thanks for your help. It is much appreciated.

A few other questions to save time.
1. What version of Disk Utility are you using for partitioning? Or are you using diskutil from command line. Does CoreVolume interfere with this? I noticed that Lion and up tend to convert to CoreVolume and have been using Snow Leopard. But that has other issues.
2. Which version of Clover are you on? r2795 is what I found to be the highest rev.
3. I have been using winch's config.plist and SSDT-1.aml. Is that, what you are using now? Where is the *.aml file placed? I have been using /EFI/Clover/ACPI/patched.

Thanks.
-- Harald

Hennesie2000 · Aug 11, 2014

haralds said:
Yes, I noticed that.
I will try adding the partition to one of the other Windows bootcamp disks.

----------

First of all, thanks for your help. It is much appreciated.

A few other questions to save time.
1. What version of Disk Utility are you using for partitioning? Or are you using diskutil from command line. Does CoreVolume interfere with this? I noticed that Lion and up tend to convert to CoreVolume and have been using Snow Leopard. But that has other issues.
2. Which version of Clover are you on? r2795 is what I found to be the highest rev.
3. I have been using winch's config.plist and SSDT-1.aml. Is that, what you are using now? Where is the *.aml file placed? I have been using /EFI/Clover/ACPI/patched.

Thanks.
-- Harald

1. I have been using the version of disk utility that is part of Mavericks. Disk utility can non destructively resize HFS+ partitions on a GPT.

2. I think I am using Clover r2774, I will double check that on my next reboot.

3. Yes that is where the SSDT-1.aml file goes.

haralds · Aug 11, 2014

Hennesie2000 said:
1. I have been using the version of disk utility that is part of Mavericks. Disk utility can non destructively resize HFS+ partitions on a GPT.

That one definitely adds CoreVolume, even if you just format one of the partitions. So that does not seem to bother Clover?

----------

haralds said:
That one definitely adds CoreVolume, even if you just format one of the partitions. So that does not seem to bother Clover?

Darn, just realized, my Boot Camp disks already have 4 partitions (they are all 4TB) - which is the max for legacy MBR boot to work.

Hennesie2000 · Aug 11, 2014

haralds said:
That one definitely adds CoreVolume, even if you just format one of the partitions. So that does not seem to bother Clover?

Honestly, I have never encountered core storage. I do not use the bootcamp assistant utility provided by Apple. I partition my disk using disk utility and then add the hybrid MBR myself. Now this might only be because I am not using any disk larger then 2.2TB (the MBR limit).

Code:

/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                  Apple_HFS Mavericks               700.1 GB   disk1s2
   3:                  Apple_HFS Clover                  939.5 MB   disk1s3
   4:       Microsoft Basic Data Windows 7               298.7 GB   disk1s4

I added that Clover partition last week and it did not add any CoreStorage. Here is a screen shot of the partition in disk utility:

haralds · Aug 11, 2014

Hennesie2000 said:
Honestly, I have never encountered core storage. I do not use the bootcamp assistant utility provided by Apple. I partition my disk using disk utility and then add the hybrid MBR myself. Now this might only be because I am not using any disk larger then 2.2TB (the MBR limit).

Code:

/dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk1 1: EFI EFI 209.7 MB disk1s1 2: Apple_HFS Mavericks 700.1 GB disk1s2 3: Apple_HFS Clover 939.5 MB disk1s3 4: Microsoft Basic Data Windows 7 298.7 GB disk1s4

I added that Clover partition last week and it did not add any CoreStorage. Here is a screen shot of the partition in disk utility:

Image

You can use larger disks as long as the Boot Camp partition is below the 2TB boundary and you do not have more than 4 primary partitions.
Guess, I will do more experimentation, when I get some time.

Tiamo's solution sure is easier, but I do not expect it until Apple publishes the new boot.efi code on opensource.com.

Hennesie2000 · Aug 11, 2014

haralds said:
You can use larger disks as long as the Boot Camp partition is below the 2TB boundary and you do not have more than 4 primary partitions.
Guess, I will do more experimentation, when I get some time.

Tiamo's solution sure is easier, but I do not expect it until Apple publishes the new boot.efi code on opensource.com.

I look forward to a Tiamo like solution but right now Clover has everything working for me. HDMI audio wasn't working for me in 10.9.3+ but using Clover it is so I might stick with it anyways.

ilegal31 · Aug 12, 2014

Mavericks USB Install issue.

Hello, I just created a Mavericks 10.9.3 USB Install with the 64 to 32 script but I can not boot from the USB drive, when I try to install Mavericks I get the following error: Could not find installation information for this machine. Any advise please?. I am on a Mac Pro 2,1 OS X 10.7.5

Hennesie2000 · Aug 13, 2014

ilegal31 said:
Hello, I just created a Mavericks 10.9.3 USB Install with the 64 to 32 script but I can not boot from the USB drive, when I try to install Mavericks I get the following error: Could not find installation information for this machine. Any advise please?. I am on a Mac Pro 2,1 OS X 10.7.5

This thread is for Yosemite, please post here in there original Tiamo/Mavericks thread: https://forums.macrumors.com/threads/1598176/

LaurentR2D2 · Aug 14, 2014

Hello,

I have Mavericks installed on my Mac Pro rev 1,1. Is it safe to upgrade it to Yosemite, or should I wait for later ?

Thank you

Hennesie2000 · Aug 14, 2014

LaurentR2D2 said:
Hello,

I have Mavericks installed on my Mac Pro rev 1,1. Is it safe to upgrade it to Yosemite, or should I wait for later ?

Thank you

The beta is pretty stable but you would need to be using clover or chameleon to boot Mavericks as the Tiamo boot.efi method does not currently work with Yosemite. If it is to be your primary OS then I would wait till the GM release.

Hennesie2000 · Aug 16, 2014

Finally picked up a pair of x5365's. Hopefully I'll have them installed in the next week or two and running Yosmite.

splifingate · Aug 17, 2014

Hennesie2000 said:
Finally picked up a pair of x5365's. Hopefully I'll have them installed in the next week or two and running Yosmite.

x5365's installed, and up to 32GB ram . . . temps are a little high compared to x5150's and 16GB ram . . . dunno what to think, but I'm not freakin', unnervingly.

Keyboard USB forgets itself, on occasion, so I un-plug, then re-plug, to gain activity...

I'm sticking to Mav for the time being....

Hennesie2000 · Aug 17, 2014

splifingate said:
x5365's installed, and up to 32GB ram . . . temps are a little high compared to x5150's and 16GB ram . . . dunno what to think, but I'm not freakin', unnervingly.

Keyboard USB forgets itself, on occasion, so I un-plug, then re-plug, to gain activity...

I'm sticking to Mav for the time being....

I had issues with my 3rd party mouse not working on boot until I unplugged and replugged it. My fix was plugging the mouse into my USB 3.0 PCI-e card. As for temps I plan on using SMC fan control to raise the minimum fan speeds a bit.

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

macrumors 68000

macrumors 68030

macrumors 68000

macrumors 68030

macrumors 68000

macrumors 68030

macrumors 68000

macrumors newbie

macrumors 68000

macrumors newbie

macrumors 68030

macrumors 68000

macrumors 68030

macrumors 68000

macrumors 68030

macrumors 68000

macrumors 68030

macrumors 68000

macrumors member

macrumors 68000

macrumors member

macrumors 68000

macrumors 68000

macrumors 68000

macrumors 68000

Our Staff