I followed the Clover instructions from post #108 of this thread. Then used Winch's config.plist and SSDT-1.aml files.
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
I followed the Clover instructions from post #108 of this thread. Then used Winch's config.plist and SSDT-1.aml files.
Interestingly, after going through the update process to get to DP4 my mouse driver and HDMI audio are no longer working. It is saying invalid signature like it was with chameleon. I guess one big benefit is that iMessage is still working.
EDIT: adding kext-dev-mode=1 fixed my kext not loading issue. Hopefully it can be removed in the future as those kext have never been a problem before DP4.
Update:
So after doing some reading I learned that DP4 is more strict against unsigned or improperly signed kexts. This is why adding kext-dev-mode=1 works and why my two kext stopped working even though they are in the exceptions list. I didn't realize at first that Winch's config.plist for clover already had this boot flag entered.
Last edited:
After applying your hybrid MBR fix, I first tried Clover 2774 on a small HFX+ partition. I was able to boot into the Clover Boot screen and from there, boot Lion.
However, the Yosemite Installer would not boot. Same is true for a bootable Yosemite image.
I then tried Clover 2689 from note 108, which would not let me install over the old Clover. Since it is older, probably not a good choice.
I see, the boot arguments do the right thing for KEXT-DEV mode.
More experiments.
What graphics card are you using? If it is a GTX 5xx or earlier then you will need to enable the NVIDIA injector.
Can you tell where it is stopping in verbose mode? Also, maybe Gpatpandp can help since he is using a 5770, although with clover on a second hdd.
I just tried to boot a preconfigured version of Yosemite. It did show a bunch of stars in a row but then stopped.
Sorry to be dumb, but how do I enable verbose? Is this the verbose boot flag -v, or is there another setting for Clover debug itself?
I just noticed, the verbose flag is set in /EFI/CLOVER/config.plist
Last edited:
Yes the -v is verbose mode. If you used Winch's config.plist then it was already enabled.
If you have another hdd separate from the Yosemite install, try installing clover there to see if you can get that to boot. That would eliminate or confirm a config issue. If it boots then it might be an issue with it all being on one drive.
Yes it is working fine for me. Since you were able to get Clover to boot on a Hybrid MBR/GPT drive I don't think it should be an issue but I am not sure. Our hardware specs are slightly different and sometimes that can be all the difference.
Is there any way to get Clover to be verbose during the first stage of the boot?
Do you mean like a text mode for Clover? If you have -v in the config file then everything is verbose after you choose which partition to boot.
Yea, that's what I'm trying to figure out where it stops. Has it finished running through all the text on the verbose screen or is it stopping somewhere you can take a picture of the screen?
DP5 out this time
I had a few beers tonight so I won't be touching it til tomorrow, someone else can check if it updates this time
System Software Overview:
System Version: OS X 10.10 (14A298i)
Kernel Version: Darwin 14.0.0
Boot Volume: Macintosh SSD
Boot Mode: Normal
Computer Name: Graeme Marshall's Mac Pro
User Name: Graeme Marshall (StatusQuoRules)
Secure Virtual Memory: Enabled
Time since boot: 7 days 5:26
I had a few beers tonight so I won't be touching it til tomorrow, someone else can check if it updates this time
System Software Overview:
System Version: OS X 10.10 (14A298i)
Kernel Version: Darwin 14.0.0
Boot Volume: Macintosh SSD
Boot Mode: Normal
Computer Name: Graeme Marshall's Mac Pro
User Name: Graeme Marshall (StatusQuoRules)
Secure Virtual Memory: Enabled
Time since boot: 7 days 5:26
No problems with DP5 using my new Clover 2774 setup. Installed via the AppStore and everything still works fine.
I have clover 2774 on a 20gb hd from an xbox but I have 2380 chameleon on a 1gb partition from a 2TB green WD and updated fine from 3 to 4 last time but ill wait this time as few beers hehe can't ruin my night yet lol
Hello, just wondering if you have released the script yet seeing as how we are on DP5 now. Thank you
There is no need for a script as it has been fairly well documented using both Chameleon and Clover.
Yosemite PB1 via Chameleon on a MacBook Pro 2,2
Slightly Off-Topic:
Since Tiamo's Boot.efi is not compatible with Yosemite yet, I've tried to install Yosemite PB1 on a MacBook Pro 2,2 with the Chameleon Bootloader as described in the Guide above.
Everything went fine until point 1. of 'Installing Yosemite'. Since the Chameleon Bootloader has apparently problems with USB-Drives, I've used a SSD connected via a SATA-ExpressCard34 (works fine with Mountain Lion as well as Mavericks). For the SMBios.plist I've used this one from here, tried also the Serial-# from the System Profiler. When I reboot the MPB, Chameleon doesn't come up. In the Mac-Bootscreen I can see the two additional HDD's 'EFI Boot' as well as 'Installer', but when I select them, it boots the Windows from the Bootcamp partition.
Any ideas what's wrong with the Chameleon boot?
Slightly Off-Topic:
Since Tiamo's Boot.efi is not compatible with Yosemite yet, I've tried to install Yosemite PB1 on a MacBook Pro 2,2 with the Chameleon Bootloader as described in the Guide above.
Everything went fine until point 1. of 'Installing Yosemite'. Since the Chameleon Bootloader has apparently problems with USB-Drives, I've used a SSD connected via a SATA-ExpressCard34 (works fine with Mountain Lion as well as Mavericks). For the SMBios.plist I've used this one from here, tried also the Serial-# from the System Profiler. When I reboot the MPB, Chameleon doesn't come up. In the Mac-Bootscreen I can see the two additional HDD's 'EFI Boot' as well as 'Installer', but when I select them, it boots the Windows from the Bootcamp partition.
Any ideas what's wrong with the Chameleon boot?
Last edited:
You shouldn't hold option at boot to select chameleon, it will automatically be done when you set legacy mode using terminal. However if the disk identifier for your boot camp partition is lower than that of the chameleon partition it will boot Windows instead, ie disk0 vs disk1.
It sounds like you didn't run the bless command.
Last edited:
I went back to Chameleon r2380. I restricted search to a single drive and pulled all drives with Windows.
I was able to boot and update to DP5. iMessage is not working - as expected.
Will try Clover r2795 one more time after getting everything else working with Chameleon.
Last edited:
Clover is no go - no bootable disk found.
Restored Chameleon and it is working with all disks installed. But no iMessage...
(edited earlier posting that mixed up Clover in the last line.)
Last edited:
Yosemite PB1 via Chameleon on a MacBook Pro 2,2
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)?
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)?
Last edited: