Search results

So I found a (weird) (and annoying) work around: Rename HFSPlus.efi to just HFSPlus (without the .efi extension), so that the driver does NOT load. This way, Clover loads fine, but of course doesn't show any of my Mac boot volumes. Run UEFI Shell, find your EFI boot volume (mine was FS1:), and...

A year later... did you ever fix this? I have the same issue. Been trying to update my 6 year old clover, and only way I can get it to start with updated clover is with NO efi drivers. But then it can’t see any of my mac volumes to try and boot. If I use hfsplus.efi, it hangs on an unblinking...

As long as I'm using the kext developer = 1 boot argument, I shouldn't have to worry about the kext signing boot error if I use Trim Enabler, right?? I might just do that. I can't get patching the hex values in the kext right, on-the-fly through Clover... :-/

Just wanted to add to this that this weekend I finished migrating to Clover, and can confirm that iMessage works out of the box (at least, setting MLB and ROM, etc., values in SMBIOS using iMessage Debug) with RAID0 boot when using Clover. You can log in and out at will while booted from the...

Trying to get trim working, using the on-the-fly kext patching. Have the requisite entry in config file (replacing hex values for ahciblockstorage kext), but trim always shows "no" in system profiler...

Aaand, all done. Used migration assistant, cloned to my RAID0 boot array, copied EFI to the RAID drives, setup the boot options in my boot manager, and it's all good to go. It was a steep learning curve, coming from Chameleon/Chimera, BUT Clover is clearly the way to go. With one boot loader on...

I realize this is now an exercise in mental masturbation (not to be crude...) but in case anyone runs into the same problem as I. I got Yosemite installed and booted, and yes, all my SATA drives mount just fine now. My issues were, in order of repair: • achieve true UEFI clover boot (had to...

BOOYAH!! Installer booted. Going on a fresh drive right now. Cross your fingers... Gotta love when the progress bar says "about a second remaining" for like, five minutes...

I'm a bit of a rube. So I assumed kexts were being injected from 10.10, etc. However, no. I had to add <key>InjectKexts<key/><true/> to the config. Now at least I get past the kernel panic when booting the installer... however eventually it hangs in an endless loop of what appears to be waiting...

Okay I have made some progress here. I was able to get UEFI boot working properly by replacing the config file with the more simple pared down version. I believe this fixed the problem with accessing SATA drives. I think there was a problem with using my DSDT file in conjunction with clovers...

Okay, just checked my BIOS, and there is NO option for CSM, and NO option for Secure Boot, at all. ??? Just tried loading clover via legacy, with all hard drives unplugged, and booting the Yosemite installer from the USB stick, and still no go. Just sits at the apple sign forever.

Thanks for weighing in. I think we may be getting closer. When I install Clover to the usb stick for UEFI to the ESP, I choose UEFI:USB volume in my boot manager which results in a very brief black screen before getting kicked back out to the boot manager. So I installed for legacy support, and...

what I find strange is that clover sees all my boot drives just fine, can boot Mavericks from any drive (with internal sata drives accessible), and can boot Yosemite from usb. And it's strange that when booting that same Yosemite usb volume using Chimera, sata drives are accessible.

BTW, should also mention that Clover boots my Mavericks RAID0 array, no problem whatsoever, all drives recognized and accessed just fine. What's more, it even allows logging in and out of iCloud, iMessage, etc., which was NEVER possible with Chimera/Chameleon when booting from a RAID0. So it's...

Quick story: installed Yosemite to an external USB drive to get it right before trying to get it in place of Mavericks on my RAID0 boot array. Got it going fine, but then discovered that fileNVRAM.dylib seems to be deprecated and doesn't work for iMessage any more in Yosemite. So started...

I am looking for this, too. Bump!!

So.... any luck?!

Of course, the size of your single drive will depend totally on the size of your cloned volume. To future proof the solution, best choice would be to get a 256 GB drive, in case the size of your cloned system grows over time. The clone does not need to be a SSD, though. Any cheap USB solution...

Success. Booted to the single-drive, and FaceTime connected just fine. Cloned back to the RAID and rebooted. FaceTime works. :-) Only caveat is that if I log out or get disconnected, I have to go through the same rigamarole. :-\ However, the login sticks forever, through all reboots, unless...

I just hooked up an old firewire camera and FaceTime recognized it just fine. It let me sign in, however it then sits waiting at "Verifying" forever, similar to what iMessage did (spins forever when I clicked "Enable account"). I am just cloning to my USB drive now, and will try my method again...