Personally I cannot get any of this to work unless I use the "sled" hard drive slots with my SSD. Even the motherboard SATA port would not boot.
Legacy mode only supports those hdd slots.
Personally I cannot get any of this to work unless I use the "sled" hard drive slots with my SSD. Even the motherboard SATA port would not boot.
Could my USB 3 or SATA card be the culprits? Any other suggestions?
I am using one of the sleds. But I am wondering, whether the PCIe cards being present creates issues.
All I can say is I sure hope that Tiamo comes up with a fix ;-)
Personally I cannot get any of this to work unless I use the "sled" hard drive slots with my SSD. Even the motherboard SATA port would not boot
I have fully functioning mac pro with clover r2774 now, audio and sata ports.
For audio, you have to write in the config.plist: Devices → Audio → Inject 12 and activate FixHDA_8000.
For SATA copied my SSDT-1.aml in / EFI / CLOVER / ACPI / patched folder and dropped your original "SataPri" in the config.plist. The necessary entries look in my config.plist.
The SSDT 1.aml is mine patched "SataPri" with DTGP and _DSM Method.
No custom DSDT.aml in EFI/CLOVER/ACPI/patched folder.
I hope it will work for you, for me it does
my config.plist is an example.
I understand that, I was grasping for straws for the interference.PCI slots are not loaded with Chameleon and neither are USB devices or the on board sata ports (the ones used for a blu-ray drive, etc). You have to understand that you are booting in legacy mode which behaves different.
I have a USB 3.0 card and have no issues with Chameleon.
Does the BOOT partition reside on the same disk as Yosemite?I have fully functioning mac pro with clover r2774 now, audio and sata ports.
For audio, you have to write in the config.plist: Devices → Audio → Inject 12 and activate FixHDA_8000.
For SATA copied my SSDT-1.aml in / EFI / CLOVER / ACPI / patched folder and dropped your original "SataPri" in the config.plist. The necessary entries look in my config.plist.
The SSDT 1.aml is mine patched "SataPri" with DTGP and _DSM Method.
No custom DSDT.aml in EFI/CLOVER/ACPI/patched folder.
I hope it will work for you, for me it does
my config.plist is an example.
Everything works perfectly. First time I have ever personally witnessed Clover recognizing my ODD ports/Blu ray optical drive. Native AppleHDA audio and loads my Apple ATI Radeon HD 5770 graphics card without issue. The great thing is while knowing Clover fairly well, is that the tweaks involved are certain to stick. I believe I can state with a fair amount of certainty that in my case, Chameleon has been permanently replaced.
Booting Yosemite with full functionality just became so much easier...Thanks much !
I have a disc extra just for Clover. Could be hybrid mbr / gpt works exactly, I do not know.Does the BOOT partition reside on the same disk as Yosemite?
Is it FAT or HFS-Plus?
I have a disc extra just for Clover. Could be hybrid mbr / gpt works exactly, I do not know.
I formatted the disk to MBR and FAT32, but hfs + should also work.
All my sleds are full with 4TB drives. Two additional internal ports are used for Blue Ray RW and a 960GB SSD with Mavericks/Tiamo boot.I have a disc extra just for Clover. Could be hybrid mbr / gpt works exactly, I do not know.
I formatted the disk to MBR and FAT32, but hfs + should also work.
b1f: init
b1f: error
I am having the same issue...I have been messing with getting clover to boot on a Hybrid MBR so that I can use Clover on one disk like I did with chameleon. I have created a disk with 3 partitions BOOT/Installer/Yosemite as FAT32/HFS+/HFS+ respectively. Setup the Installer partition and installed Clover. I then created the Hybrid MBR writing a 0c type to the MBR for the BOOT partition. Now here is where I am stuck. Normally when I would try to boot Clover on a pure GPT I would get the "No bootable device..." error. Since I setup the hybrid MBR I now get the following:
Code:b1f: init b1f: error
Now this would suggest that the partition where Clover is installed is the wrong file system but I know it is FAT32 which is correct.
Anyone with more Clover experience have any suggestions on how to get past this error? Can Clover be booted from any other file system, HFS, NTFS, etc?
I am having the same issue...
I have been messing with getting clover to boot on a Hybrid MBR so that I can use Clover on one disk like I did with chameleon. I have created a disk with 3 partitions BOOT/Installer/Yosemite as FAT32/HFS+/HFS+ respectively. Setup the Installer partition and installed Clover. I then created the Hybrid MBR writing a 0c type to the MBR for the BOOT partition. Now here is where I am stuck. Normally when I would try to boot Clover on a pure GPT I would get the "No bootable device..." error. Since I setup the hybrid MBR I now get the following:
Code:b1f: init b1f: error
Now this would suggest that the partition where Clover is installed is the wrong file system but I know it is FAT32 which is correct.
Anyone with more Clover experience have any suggestions on how to get past this error? Can Clover be booted from any other file system, HFS, NTFS, etc?
I can only add that back with Mountain Lion, I was able to use Clover in a sudo "install in the ESP" legacy type fashion where it would boot from a small adjacent formatted, "blessed" HFS+/FAT32 partition to the 10.8 OS system. I have tried this same set-up with Yosemite and while Clover loads/boots without issue, OS X 10.10 just will not. Note in fact earlier in this very same thread where I remark that I simply assumed that this type of set-up would work and I could not understand why my initial install was not working while everyone else was booting Yosemite with Clover without issue. Once it was revealed that the way folks were booting it was from a separate MBR formatted BOOT drive, I was able to get the first release to boot also.
On a side note, I have been booting Yosemite with Clover on my Dell E6400 Laptop exactly in this manner i.e. installed in the ESP while formatting the Apple EFI partition to FAT32. The only difference being is that it is not necessary to "bless" the partition in order to legacy boot on a PC.
What tool did you use to set these up? Do you mean to write, you end up with four partitions, or did you convert one HFS+ to fat32? I am not sure, what you mean with "EE in Slot one" and "AF in slot 2"?I was able to figure it out. The trick was not to use FAT32. Instead setup the HDD with the 3 partitions all HFS+ Journaled and GPT. Then Create the installer partition. Then create the Hybrid MBR for the Boot partition and set it up with an EE in slot one and an AF in slot two flagged as active. Install Clover and the necessary files. Then bless the Boot partition and install.
After the install you will have to redo the Hybrid MBR since the installer will overwrite it. For safe measure I reinstalled Clover too. From here you should be able to boot the newly installed Yosemite. I am typing this from a single HDD in Yosemite with a Hybrid MBR/GPT setup.
Now to try all the updates...
What tool did you use to set these up? Do you mean to write, you end up with four partitions, or did you convert one HFS+ to fat32? I am not sure, what you mean with "EE in Slot one" and "AF in slot 2"?
Thanks. Did all that - pretty straight forward. But it ended up booting one of the Windows partitions on another disk.Clover is installed on the HFS+ partition and you only have 3 partitions. There are no FAT partitions used at all. To create the Hybrid MBR I use a command line tool called gdisk. Follow the instructions here: http://www.rodsbooks.com/gdisk/hybrid.html. You will understand what I mean by slot one and two after reading this. An amendment to those instructions, I do not create any more entries to protect partitions as this usually causes errors for me.
Thanks. Did all that - pretty straight forward. But it ended up booting one of the Windows partitions on another disk.
What are your install options for the boot sector in this scenario?Clover is installed on the HFS+ partition and you only have 3 partitions. There are no FAT partitions used at all. To create the Hybrid MBR I use a command line tool called gdisk. Follow the instructions here: http://www.rodsbooks.com/gdisk/hybrid.html. You will understand what I mean by slot one and two after reading this. An amendment to those instructions, I do not create any more entries to protect partitions as this usually causes errors for me.