- Joined
- Jan 12, 2010
- Messages
- 671
- Motherboard
- GA-X58A-UD5
- CPU
- 980x
- Graphics
- r9 290x + 6850
- Mac
- Mobile Phone
I'm a long time user of Chameleon and recently started trying to Use Clover.
My big trouble with Clover.
I have several dives in my system and a Legacy BiOS on a 5 series board:
I have 2 SSD Boot drives, one with 10.10 and one with 10.11 both have Chameleon as Bootloader.
If I try to install Clover via Multibeast or from the standalone installer on a tertiary drive the Clover installer does something to the drive it installs on which causes me to not be able to boot from my other drives even though I have my SSD Chameleon drives set in the BiOS as primary.
Somehow the Clover installer is doing something to force bypass my BiOS settings. This is incredibly frustrating and I would love for someone to tell me how to disable this function of Clover.
As I am in the experiments stages of using Clover sometimes in the experimentation process the new Clover install won't boot which is totally fine and expected. But because it bypasses my BiOS settings I am unable to boot from my other drives.
In order to correct this issue I have to open my box and remove all my other drives and boot from one of the Chameleon drives then remount all my drives individually from an external doc and use:
(a really inelegant large hammer to fix it)
Sorry for the wordy post:
My Question:
The Clover installer is doing something to force bypass my BiOS settings primary boot drive. I would love for someone to tell me how to disable this function of Clover.
Or how others are dealing with this issue.
Thank you.
My big trouble with Clover.
I have several dives in my system and a Legacy BiOS on a 5 series board:
I have 2 SSD Boot drives, one with 10.10 and one with 10.11 both have Chameleon as Bootloader.
If I try to install Clover via Multibeast or from the standalone installer on a tertiary drive the Clover installer does something to the drive it installs on which causes me to not be able to boot from my other drives even though I have my SSD Chameleon drives set in the BiOS as primary.
Somehow the Clover installer is doing something to force bypass my BiOS settings. This is incredibly frustrating and I would love for someone to tell me how to disable this function of Clover.
As I am in the experiments stages of using Clover sometimes in the experimentation process the new Clover install won't boot which is totally fine and expected. But because it bypasses my BiOS settings I am unable to boot from my other drives.
In order to correct this issue I have to open my box and remove all my other drives and boot from one of the Chameleon drives then remount all my drives individually from an external doc and use:
(a really inelegant large hammer to fix it)
Code:
newfs_hfs -v EFI /dev/disk1s1
fdisk -e /dev/rdisk0
p
f 1
w
Sorry for the wordy post:
My Question:
The Clover installer is doing something to force bypass my BiOS settings primary boot drive. I would love for someone to tell me how to disable this function of Clover.
Or how others are dealing with this issue.
Thank you.