2 good questions and 2 dumb ones for replacing Chameleon with Clover

I have a fully working (except iMessage) Chameleon install of 10.4. It boots to a GPT formatted EFI partition.
I've made a Clover legacy install on a USB and when I boot to it, it also runs perfectly.

QUESTIONS:

1. I had to use EFI with chameleon because of my R9-270x GPU. Will I have to do the same using Clover?

2. I want to use this procedure: http://www.tonymacx86.com/alternate-bootloaders/127134-test-drive-how-create-clover-usb-5.html, Will I need to remake a USB Clover boot stick with UEFI install instead of legacy?

3. I was hoping I could simply format the SSD EFI partition to fat32 and copy all the legacy files from the usb into it. Possible?

4. If I decide to install Clover directly to the SSD for UEFI booting, do I first need to do anything to the current EFI partition?

Thanks for listening

michaelcly said:

I have a fully working (except iMessage) Chameleon install of 10.4. It boots to a GPT formatted EFI partition.
I've made a Clover legacy install on a USB and when I boot to it, it also runs perfectly.

QUESTIONS:

1. I had to use EFI with chameleon because of my R9-270x GPU. Will I have to do the same using Clover?

2. I want to use this procedure: http://www.tonymacx86.com/alternate-bootloaders/127134-test-drive-how-create-clover-usb-5.html, Will I need to remake a USB Clover boot stick with UEFI install instead of legacy?

3. I was hoping I could simply format the SSD EFI partition to fat32 and copy all the legacy files from the usb into it. Possible?

4. If I decide to install Clover directly to the SSD for UEFI booting, do I first need to do anything to the current EFI partition?

Thanks for listening

Click to expand...

1. Yes, the Clover EFI folder goes in the EFI partition.
2. No, you can use the EFI folder on your existing USB drive
3. Yes. Copy your /Extra folder from the EFI partition to desktop for backup. Install Clover to the SSD. Copy the EFI folder from the USB to the EFI partition on the SSD, replacing the one from the Clover install you just did. Since it boots OK from the USB, then it should boot OK from the SSD.
4. No, see 3.

Going Bald said:

1. Yes, the Clover EFI folder goes in the EFI partition.
2. No, you can use the EFI folder on your existing USB drive
3. Yes. Copy your /Extra folder from the EFI partition to desktop for backup. Install Clover to the SSD. Copy the EFI folder from the USB to the EFI partition on the SSD, replacing the one from the Clover install you just did. Since it boots OK from the USB, then it should boot OK from the SSD.
4. No, see 3.

Click to expand...

Thanks GB
I think I can do this. I want to make sure I understand. When you say install Clover to the SSD you mean run the Clover pkg and configurator same as I did for USB, rather than copy Clover files from the USB?

EDIT: Found this from a previous post of yours. I get it now.

"run show all files.
open Finder
delete the file called boot
install Clover to your HDD/SSD same as you did for the USB installer. Do the exact same thing to the Clover files on the HDD/SSD that you did on the USB when you created it."


One more question please:
When I boot from the USB, I'm guessing some of the extensions in S/L/E that were placed or changed by MultiBeast are used by Clover. I guess what I mean is, will I have to deal with things like moving AppleHDA when I do the next OS X upgrade?

Mike

michaelcly said:

Thanks GB
I think I can do this. I want to make sure I understand. When you say install Clover to the SSD you mean run the Clover pkg and configurator same as I did for USB, rather than copy Clover files from the USB?

EDIT: Found this from a previous post of yours. I get it now.

"run show all files.
open Finder
delete the file called boot
install Clover to your HDD/SSD same as you did for the USB installer. Do the exact same thing to the Clover files on the HDD/SSD that you did on the USB when you created it."

Click to expand...

You got it

michaelcly said:

One more question please:
When I boot from the USB, I'm guessing some of the extensions in S/L/E that were placed or changed by MultiBeast are used by Clover. I guess what I mean is, will I have to deal with things like moving AppleHDA when I do the next OS X upgrade?

Mike

Click to expand...

MultiBeast is a post install tool to install kexts in S/L/E and create the /Extra folder and install a boot loader, depending on your selections. I have used it to install kexts for networking and drivers for other board chipsets and for audio and still installed Clover as my boot loader.

The only reason you put kexts in the kext folder of Clover USB is because they are not in the native OS X boot package - really, you need only fakesmc kext when booting/installing with Clover. Adding your audio and networking kexts is handy to have, but not required if you don't need the internet to go download what you need to finish the installation.
When I install Clover as boot loader I always install the kexts in S/L/E because that is where they belong and I do not care if my install is not 100% "vanilla".
Once you have fakesmc kext and the others in OS X S/L/E, it is no longer needed to have them in Clover/kexts/10.xx.xx folder when you install Clover on your hard drive.

One caveat here is, if you want to have audio using only the native unpatched AppleHDA.kext so you do not have to worry about reloading a new patched kext every time you update, you can use toleda's method of injecting the patch with Clover "on-the-fly" when you boot. See http://www.tonymacx86.com/audio/143757-audio-realtek-alc-applehda-guide.html

Thank you, very helpful

That's exactly how I would like to do it... use the patched kext you suggested and another from insanelyMac forum for my GPU. That's the whole reason I'm doing this.

Success!

Failed to install first time because I booted from the USB. Rebooted from the SSD w/Chameleon then installed and replaced the EFI folder from the new install with the EFI from the USB. Unplugged the USB and restarted without a hitch. I left all the kexts in S/L/E from Multibeast so it works exactly how it did before. I'll deal with the AppleHDA patch on the next upgrade.

From another post, I used Clover configurator to change the system def to iMac 12.1. That is the only one I could find that let me run my CPU at 4.1GHZ (until I learn about ssdt's)

Still having some USB3 issues with USB2 devices. That's next.

Happy, happy, happy

michaelcly said:

Success!

Failed to install first time because I booted from the USB. Rebooted from the SSD w/Chameleon then installed and replaced the EFI folder from the new install with the EFI from the USB. Unplugged the USB and restarted without a hitch. I left all the kexts in S/L/E from Multibeast so it works exactly how it did before. I'll deal with the AppleHDA patch on the next upgrade.

From another post, I used Clover configurator to change the system def to iMac 12.1. That is the only one I could find that let me run my CPU at 4.1GHZ (until I learn about ssdt's)

Still having some USB3 issues with USB2 devices. That's next.

Happy, happy, happy

Click to expand...

So you managed to get iMessage working? From your original post I would think this was the reason you wanted Clover in the first place.

Going Bald said:

So you managed to get iMessage working? From your original post I would think this was the reason you wanted Clover in the first place.

Click to expand...

I don't really use it, but I will try to get it going. My priority is to inject with the correct frame buffer. My r9 270X is running about 1/5 the speed it did with Mavericks. The best way to do that is with clover. There's a great thread on that over at InsanelyMac. There used to be a command you could add to chameleon plist for the older Radeon cards, but it no longer works (you clued me in on that a long time ago). So, as I understand, I need to extract the info from the GPU bios in Windows and use the info patch the DSDT or something like that. It's a little over my head but I'll get there.

Your help is appreciated. I've been wanting to boot with Clover for some time, but kept chickening out. It was easier than I thought thanks to all the help.