Clover General discussion

[JustFortehFun]

Hopefully, im not going to sound like a complete idiot, but i would like to ask for advice as to how to initially boot Clover.

 

Setup:

Z87/Haswell/GUID HDD/USB Instlall

 

Goal:

I would like to make a USB boot-drive and install Yosemite to my HDD.

 

Problem:

How to actually install Clover:

 

1) How to install Clover on my USB pen-drive without formatting and/or deleting the Yosemite installation files?

2) Which mode should i use to boot: UEFI (i have z87 UEFI motherboard), ESP, FAT ?

[arsradu]

Hopefully, im not going to sound like a complete idiot, but i would like to ask for advice as to how to initially boot Clover.

 

Setup:

Z87/Haswell/GUID HDD/USB Instlall

 

Goal:

I would like to make a USB boot-drive and install Yosemite to my HDD.

 

Problem:

How to actually install Clover:

 

1) How to install Clover on my USB pen-drive without formatting and/or deleting the Yosemite installation files?

2) Which mode should i use to boot: UEFI (i have z87 UEFI motherboard), ESP, FAT ?

 

Have a look here.

 

Also, if you haven't already done that, you might want to have a look here, as well.

 

You won't be using the stock 10.9.1 mach_kernel. So don't take that.

 

Images usually speak better than words. So have a look there.

 

Before clicking Install, make sure you select Customize and select the things you want to install. Also, make sure you select the drive you want Clover installed on (in this case, I suppose it's gonna be your Yosemite USB pen drive). So make sure you select that. Otherwise you might be installing it on your current OS.

 

You can use whichever mode you want. You've got everything described for both cases there. If you've got a UEFI motherboard, you can go for UEFI. Both methods should work either way. Just make sure you select the right things for that specific case before clicking Install.

[JustFortehFun]

Thanks, somehow i missed those articles.

 

Another question that i missed was:

 

Which plugins should i install.

 

The thing is: i made a Hackinotsh a while ago for a 775 platform and everything was fixed by a magic DSDT for my board, however im not sure what is not/is not going to work with Z87/Haswell and thus i can't possibly configure Clover flags and plugins.

[Slice]

Thanks, somehow i missed those articles.

 

Another question that i missed was:

 

Which plugins should i install.

 

The thing is: i made a Hackinotsh a while ago for a 775 platform and everything was fixed by a magic DSDT for my board, however im not sure what is not/is not going to work with Z87/Haswell and thus i can't possibly configure Clover flags and plugins.

Probably all plugins.

The best config is empty config. All flags Clover will set by own calculations if you didn't set them.

Clover Configurator is wrong helping you to fill config. You must NOT FILL it.

All values have three states: a value, zero, and not set. Third one is the best value.

[arsradu]

Thanks, somehow i missed those articles.

 

Another question that i missed was:

 

Which plugins should i install.

 

The thing is: i made a Hackinotsh a while ago for a 775 platform and everything was fixed by a magic DSDT for my board, however im not sure what is not/is not going to work with Z87/Haswell and thus i can't possibly configure Clover flags and plugins.

You might not need any DSDT anymore.

If i were you, i would go with the defaults (first) for UEFI case (just select what you see in the screenshot for UEFI case). I don't have an ASUS motherboard so i don't know exactly. But this is what i would do. Start with the defaults.

And make sure you got your Yosemite on a separate partition (just in case).

[Simonej]

There is working AppleUSBXHCI 677.4.0 (OS X 10.9.3) patch for Clover (USB3ports)? Or patched kext...

 

 

Maniac10 patch for Clover doesn't' work well for me; http://www.insanelymac.com/forum/topic/285157-patched-appleusbxhci-from-os-1082/?p=2004536 (TI chipset AsRock X79)

[Maniac10]

Hey Simonej, perhaps you have a different version of the kext in which case it may need to be adjusted. For instance, on 10.9.4 (13E16) I had to change the patch a bit again.

[ADHDMedia]

There is working AppleUSBXHCI 677.4.0 (OS X 10.9.3) patch for Clover (USB3ports)? Or patched kext...

 

 

Maniac10 patch for Clover doesn't' work well for me; http://www.insanelymac.com/forum/topic/285157-patched-appleusbxhci-from-os-1082/?p=2004536 (TI chipset AsRock X79)

 

I found one that worked the other day (actually slice linked me to it) but GenericUSBXHCI works just as well.  If you have a problem with it not working after waking up from sleep (I did) just boot with flag -gux_nosleep and it should take care of that problem. 

So quick question about Clover:  do you have to be using UEFI in order to reboot from the Startup Disk menu in Preferences?  

[AsusFreak]

Reboot from the Startup Disk menu doesn't work on a hack, even with Clover UEFI. It will reboot boot but only to the default boot drive...

[ADHDMedia]

I'm almost positive I read that as a Clover benefit/feature lol hmm

 

EDIT:  Yea, right here: 

- boot into 10.4 - 10.8 OSX, Windows EFI and Linux EFI
- boot into LegacyOS (WindowsXP, Linux, DOS) by their bootsectors
- this is EFI bootloader so it provides RuntimeServices for OS that impossible for Legacy Bootloaders
- mostly Clover do automatic detection of hardware and set all properties by default. But user can change them by config.plist
- With Clover you may restart into other OS from Startup Disk prefPane
- With Clover you boot your OS X's Recovery HD, impossible for others bootloaders
- config autodetect by OEM product name
- UUID written into config.plist will be the same as in OS
- autopatch OemDSDT for working OSX
- SMBIOS will be corrected to standard 2.6
- ACPI will be corrected to standard 4.0. Custom DSDT will be loaded from booted partition or from EFI folder
- MADT table may be corrected to resolve problem with NMI on some hardware
- ACPI tables loading (SSDT-xx, APIC, BOOT, SLIC, SLIT, SRAT, UEFI...)
- correctly set PowerProfile for laptops (notebooks), desktops, workstations
- customizable RestartFix
- sleep/wake fixes
- PCIRootUID value (0,1) for device-injection for those who can't edit DSDT
- Graphics Properties Injector for ATI, NVidia and Intel for wide range of supported cards. Also customizable.
- Custom EDID for non-DDC monitors
- USB fix (LegacyOff, Ownership, Builtin, clock-id) up to USB 3.0
- HDA injector, HDMI fix.
- Ethernet builtin injector
- CPU turbo
- P- and C-states generator
- PLimitDict and UnderVoltage for CPU Speedstep
- patch kernel on the fly for unsupported CPU like Atom and Ivy Bridge
- Patch AppleIntelCPUPowerManagement for native Speedstep (Intel Processor) of ASUS ownwers
- patch kexts inside kernelcache for unsupported hardware
- extra kexts loading
- security mode for FireWire
- default boot after timeout
- customizable GUI: themes support, own icons, fonts, animations.
- there is a possibility to implement national languages and fonts. F1 - multilingual help
- saving boot.log in OS and preboot.log from GUI by typing F2
- save original (OEM) ACPI tables by pressing F4
- test DSDT patching with F5
- save videoBIOS into EFI/misc by pressing F6
- saving screenshots from GUI typing F10
- CD/DVD eject by F12 and refresh menu after CD insertion

This looks like an old change log, but it should still apply right? 

"With Clover you may restart into other OS from Startup Disk prefPane"

[AsusFreak]

Never worked for me, but whatever... I don't see how it could work, it's not like OS X "Startup Disk" can write to Clover config or to nvram.  Maybe others have found a way make it work...

[ADHDMedia]

Never worked for me, but whatever... I don't see how it could work, it's not like OS X "Startup Disk" can write to Clover config or to nvram. Maybe others have found a way make it work...

It doesn't work for me either... That's why I figured it must be a UEFI only thing. When I choose reboot to another OS in my prefPane it's just like a regular reboot lol oh well

[blackosx]

Changing boot device from the Startup Disk pref pane works fine using Clover in UEFI mode, though I'm not sure when using legacy boot mode (I will need to test)

 

It works due to the nvram efi-boot-device variable. You can test it by issuing nvram -p from terminal. Here's mine before making a loading the Startup Disk pref pane and making a change

efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>A9A532E5-2625-4E75-A807-B6642847CBF1</string></dict></dict></dict></array>

and after

efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>47E2A5DE-B075-4993-AFC1-B7867A644A5D</string></dict></dict><key>BLLastBSDName</key><string>disk1s3</string></dict></array>

And looking at my Clovers boot-log from next boot I see

6:538  0:019  GetEfiBootDeviceFromNvram:
6:539  0:000   efi-boot-device-data: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(3,GPT,47E2A5DE-B075-4993-AFC1-B7867A644A5D,0x224028,0x6C72FC0)

 

EDIT: Yep, works fine using legacy boot too but make sure you have the following rc.script installed:

/etc/rc.shutdown.d/80.save_nvram_plist.local

 

Looking at boot-log from next boot.

4:727  0:000  Loading nvram.plist from Vol 'BackupMAV' - loaded, size=4015
4:742  0:015  PutNvramPlistToRtVars ...
….
4:742  0:000   Adding Key: efi-boot-device: String: Size = 264, Val = '<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>47E2A5DE-B075-4993-AFC1-B7867A644A5D</string></dict></dict><key>BLLastBSDName</key><string>disk2s3</string></dict></array>': Success
4:742  0:000   Adding Key: efi-boot-device-data: Data: Size = 74: Success
…

These test were from 10.9. If using 10.10 then you will need the latest workaround for initiating the rc.scripts as the current method no longer works with 10.10.

[franmglp]

Yosemite DP1 Removes SystemStarter

 

NVRAM script isn't working in Yosemite because of this?

 

A very simple question... How can I load kexts correctly using Clover during OS X installation. For example, I want to load FakeSMC.kext/Contents/PlugIns/ALXEthernet.kext to set iCloud during the installation. I put my kexts in /EFI/CLOVER/kexts/Other but Ethernet kext isn't loading.

[xpamamadeus]

Yosemite DP1 Removes SystemStarter

 

NVRAM script isn't working in Yosemite because of this?

 

A very simple question... How can I load kexts correctly using Clover during OS X installation. For example, I want to load FakeSMC.kext/Contents/PlugIns/ALXEthernet.kext to set iCloud during the installation. I put my kexts in /EFI/CLOVER/kexts/Other but Ethernet kext isn't loading.

u need to inject IONetworkingFamily.kext for ALXEthernet.kext to work.

[AsusFreak]

@BlackOSX
 
Booting Yosemite with Clover UEFI on Disk0. I have done the patch for rc.scripts. nvram is being created and RT Variables working.

nvram -p

%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00@%93%b5%1d%00%00%00%00%99n%99%7f%cb%94~E%97~%9a@%91%ca%a5e%02%02%7f%ff%04%00

Restart and the box boots back to Yosemite instead of Mavericks.

nvram-p no change.

%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00@%93%b5%1d%00%00%00%00%99n%99%7f%cb%94~E%97~%9a@%91%ca%a5e%02%02%7f%ff%04%00

Not a big deal as I've never seen much value in this feature but interested on why it's not working...

 

Regards

[ADHDMedia]

Changing boot device from the Startup Disk pref pane works fine using Clover in UEFI mode, though I'm not sure when using legacy boot mode (I will need to test)

 

It works due to the nvram efi-boot-device variable. You can test it by issuing nvram -p from terminal. Here's mine before making a loading the Startup Disk pref pane and making a change

 

efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>A9A532E5-2625-4E75-A807-B6642847CBF1</string></dict></dict></dict></array>

and after

efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>47E2A5DE-B075-4993-AFC1-B7867A644A5D</string></dict></dict><key>BLLastBSDName</key><string>disk1s3</string></dict></array>

And looking at my Clovers boot-log from next boot I see

6:538  0:019  GetEfiBootDeviceFromNvram:
6:539  0:000   efi-boot-device-data: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(3,GPT,47E2A5DE-B075-4993-AFC1-B7867A644A5D,0x224028,0x6C72FC0)

EDIT: Yep, works fine using legacy boot too but make sure you have the following rc.script installed:

/etc/rc.shutdown.d/80.save_nvram_plist.local

 

Looking at boot-log from next boot.

4:727  0:000  Loading nvram.plist from Vol 'BackupMAV' - loaded, size=4015
4:742  0:015  PutNvramPlistToRtVars ...
….
4:742  0:000   Adding Key: efi-boot-device: String: Size = 264, Val = '<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>47E2A5DE-B075-4993-AFC1-B7867A644A5D</string></dict></dict><key>BLLastBSDName</key><string>disk2s3</string></dict></array>': Success
4:742  0:000   Adding Key: efi-boot-device-data: Data: Size = 74: Success
…

These test were from 10.9. If using 10.10 then you will need the latest workaround for initiating the rc.scripts as the current method no longer works with 10.10.

Where do I find that rc.script?

Never mind, I have it installed... Trying to reboot to different OS now.

Ya mine just restarts to Clover GUI.

[Slice]

This feature was the first goal in creating the Clover. It works for me since the first version.

blackosx already explained how it works.

I have to say about NVRAM used in the technology.

Legacy Clover (CloverEFI). rc script will create a file nvram.plist after the Restart button pressed and keep information about next drive started.

UEFI Clover with hardware not supporting NVRAM. You should have /EFI/CLOVER/drivers64UEFI/EmuVariableUefi-64.efi

UEFI Clover with hardware NVRAM. This is my computer #1 in signature. Additional bonus I have is Panic.log. For example

Anonymous UUID:       43065937-BBF0-8F2F-C339-5635BC71CE03

Wed May 28 07:56:29 2014
panic(cpu 0 caller 0xffffff80002dbf5e): Kernel trap at 0xffffff7f8253ca25, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x0000000103b83fc8, CR3: 0x000000000fd3405b, CR4: 0x00000000000606e0
RAX: 0x6a5993c096a5009c, RBX: 0x0000000000000001, RCX: 0x000000000000064c, RDX: 0xffffff8000686fd0
RSP: 0xffffff80e7c77ea0, RBP: 0xffffff80e7c77ed0, RSI: 0x0000000000000000, RDI: 0x0000000000000000
R8:  0x0000000000000000, R9:  0x0000000000000010, R10: 0x0000000000000000, R11: 0xffffff8000686fd0
R12: 0xffffff80184015e8, R13: 0xffffff80279e6284, R14: 0xffffff8110cdbb40, R15: 0x0000000000000000
RFL: 0x0000000000010002, RIP: 0xffffff7f8253ca25, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000103b83fc8, Error code: 0x0000000000000000, Fault CPU: 0x0

Backtrace (CPU 0), Frame : Return Address
0xffffff80e7c83c50 : 0xffffff8000222fa9 
0xffffff80e7c83cd0 : 0xffffff80002dbf5e 
0xffffff80e7c83ea0 : 0xffffff80002f3456 
0xffffff80e7c83ec0 : 0xffffff7f8253ca25 
0xffffff80e7c77ed0 : 0xffffff80002e336e 
0xffffff80e7c77f10 : 0xffffff80002e2c8e 
0xffffff80e7c77f50 : 0xffffff80002e1fd6 
0xffffff80e7c77f80 : 0xffffff80002db51f 
0xffffff80e7c77fd0 : 0xffffff80002f3619 
0xffffff810fa1bde0 : 0xffffff800021a3e7 
0xffffff810fa1be20 : 0xffffff800021baba 
0xffffff810fa1be70 : 0xffffff8000217b9b 
0xffffff810fa1bf10 : 0xffffff8000229627 
0xffffff810fa1bf40 : 0xffffff800021d604 
0xffffff810fa1bf70 : 0xffffff80002c989d 
0xffffff810fa1bfb0 : 0xffffff80002f3c76 
      Kernel Extensions in backtrace:
         com.coresystems.driver.DirectHW(1.3)[46ED721E-1B50-31CA-B1A2-D6F7140E7906]@0xffffff7f8253b000->0xffffff7f8253efff

BSD process name corresponding to current thread: Terminal
Boot args: -v slide=0 

Mac OS version:
13D65

Kernel version:
Darwin Kernel Version 13.2.0: Thu Apr 17 23:03:13 PDT 2014; root:xnu-2422.100.13~1/RELEASE_X86_64
Kernel UUID: ADD73AE6-88B0-32FB-A8BB-4F7C8BE4092E
System model name: iMac12,2 (Mac-942B5BF58194151B)

System uptime in nanoseconds: 13885620970427
last loaded kext at 855277706575: com.apple.filesystems.cd9660	1.4.4 (addr 0xffffff7f8253f000, size 36864)
loaded kexts:
com.coresystems.driver.DirectHW	1.3
org.voodoo.driver.VoodooHDA	2.8.4
org.slice.RadeonMonitor	1.0.0d1

[ADHDMedia]

So what is the end result when you use this feature with legacy boot (not UEFI)? Does your system go through a full reboot and go through bios and then just boot through Clover into the selected OS? Or how does it work...?

I'd like to be able to jump back and forth between 10.10 and 10.9.3 with the prefpane, but I'm not ready to make the jump to upgrading my board to UEFI boot... Haha

[Slice]

So what is the end result when you use this feature with legacy boot (not UEFI)? Does your system go through a full reboot and go through bios and then just boot through Clover into the selected OS? Or how does it work...?

I'd like to be able to jump back and forth between 10.10 and 10.9.3 with the prefpane, but I'm not ready to make the jump to upgrading my board to UEFI boot... Haha

Yes, exactly as you said.

I have two systems 10.7.5 and 10.9.3. I can choose one in Startup Disk and reboot. I can go out and wait what is happen.

The computer goes through full restart, bios, then CloverGUI, timeout set to 5 seconds, then start the OS chosen in Startup DIsk.

I am lazy to show you the Video, trust me, it occurs.

It works for both legacy Clover and UEFI Clover. Tested and always works with all Clover versions on all 4 my computers.

[ADHDMedia]

I just got mine working, and it works exactly as advertised  Thanks bro.  

 

Is there any way to speed up the CloverGUI process?  I set the timeout to 0, but it still takes a good 15-20 seconds, maybe longer, for Clover to finish loading and start booting the OS.  What can I do to speed up Clover?

 

You guys were right, this is getting better and better lol

[Slice]

Some users have 1 seconds from computer powerup through clover to kernel start.

Show your boot.log to see what is the delay.

[ADHDMedia]

Where do I find the log?

 

**Nevermind**

[blackosx]

if you have /usr/local/bin/bdmesg installed then in Terminal type

sudo bdmesg

The package istaller would have installed it for you.

Or simply run DarwinDumper and select the Firmware (Boot) Log option

 

Boot speed for me using Legacy boot:

7:653  0:000  Closing log

or UEFI boot:

3:352  0:000  Closing log

That’s with PatchVBios set to true which adds time to the process.

[alexanderq]

Some users have 1 seconds from computer powerup through clover to kernel start.

Show your boot.log to see what is the delay.

Sorry Slice but i have 3 pc and i have tried in other ten diferent configurations but that is the only thing (the only thing) i hate about clover it is slow 10 15 20 seconds.Maybe some users are booting fast but all new users that are trying clover for the first time are coplaining for booting times.