Clover General discussion

dmazar · November 5, 2012

Right now, I want to boot clover from hdd (ML) only. Please help me how to do that

DarwinDumper shows that you have installed Clover on all possible places. :wacko:

That's a bad idea.

You should use USB stick, install it there and test it and configure it on that USB stick. Only when you have all working from the USB stick, then it's a good time to move it to HD. In that way you would not mess with your current bootloaders.

Regarding Chameleon ... you can fix it in on your Lion disk:

- remove /boot, /boot3, /boot6, /EFI folder from there (those are Clover files)

- and rename /boot1 to /boot (current boot1 is your Chimera)

- then try to reboot by choosing Lion disk as boot disk - should start your Chimera from that disk

- additionally, you can replace current Clover's "boot1h2" partition boot loader with standard Chameleon's, to get rid of 2 seconds pause during boot:

--- you may use ChameleonWizard and install "boot0hfs" to Lion partition

Regarding ML disk: you can safely delete Clover's files from ML partition, since you have installed Clover to EFI partition on that disk also. Meaning: if you choose ML disk, then that will start Clover from EFI partition and not from ML. So:

- remove /boot, /boot3, /boot6, /EFI folder from ML partition

And use USB stick for Clover tests first. Hope this helps.

kyndder · November 5, 2012

Could you show me your config.plist?

Do you use the plist for speedstep? What SMBios do you use?

With 0XBCB7, it's able to wake sometime, but sometime not ,and sometime reboot after it wakes...

I found out that it will restart when I open DSDTSE after it wakes...

I'm using your MacPro5_1.plist, custom SSDT made with Revogirl's script and of course, MacPro5,1 SMBIOS, but I only

set on my config.plist the machine model and any other one information, this way, Clover can fill the rest...

I don´t had any restart after wake on 10.7 and 10.8 (at least until now)...

I will send my config.plist later when I came home...

magnifico · November 5, 2012

@dmazar

but you could create a script to open the hidden EFI partition, without going through the Terminal?

Slice · November 5, 2012

- additionally, you can replace current Clover's "boot1h2" partition boot loader with standard Chameleon's, to get rid of 2 seconds pause during boot:

--- you may use

ChameleonWizard

and install "boot0hfs" to Lion partition

Caution! Chameleon's boot1h will not load Clover-64 because of limited size of boot file. 440kb for Chameleon's boot1h and 472kb for Clover.

kyndder · November 5, 2012

@dmazar

but you could create a script to open the hidden EFI partition, without going through the Terminal?

Why you don't add to fstab for automount???

UUID=PartitionUUID /Volumes/EFI msdos rw,auto

Taruga · November 5, 2012

My guess that it is because of kext injection. You may try to install kexts to /S/L/E and not keep them in Clover's /efi/kexts/...

Although, I do not get this error even when using Clover's kext injection.

And here is the version of the driver that will silently fix that error without pausing. You may use that.

OsxAptioFixDrv-64.efi.zip

Works well,

http://www.youtube.com/watch?v=HOVV4eOFNr0

ps. Video was recorded with the Marvel controller disabled, else I get a 3 minute delay until I can see Clover GUI

And the system is being booted from an external USB 3 dual dock with one 240GB SSD + 250GB HDD setup as a CoreStorage Volume

Clover it's almost perfect for me to use it from now on, I just wish the developers skipped hard disk searches connected to the marvel controller to avoid the 3 minute delay that I have.

Edited November 5, 2012 by Taruga

magnifico · November 5, 2012

Works well,

http://www.youtube.com/watch?v=HOVV4eOFNr0

ps. Video was recorded with the Marvel controller disabled, else I get a 3 minute delay until I can see Clover GUI

And the system is being booted from an external USB 3 dual dock with one 240GB SSD + 250GB HDD setup as a CoreStorage Volume

Clover it's almost perfect for me to use it from now on, I just wish the developers skipped hard disk searches connected to the marvel controller to avoid the 3 minute delay that I have.

Taruga ..you have error hda ???

It is impossible :hammer:

You are a guru for hda ...

I'm playing not to offend you, sorry

Taruga · November 5, 2012

It's just a test installation and usually I don't use AppleHDA, I have an USB device connected to my Sound Mixer.

magnifico · November 5, 2012

It's just a test installation and usually I don't use AppleHDA, I have an USB device connected to my Sound Mixer.

Me too friend ..have a usb device Dac ...it is fantastic

Sorry for OT

n10jbX1.6 · November 6, 2012

dmazar you are superfast

For me you'll be a future forum moderator... :wink2:

:thumbsup_anim:

DarwinDumper shows that you have installed Clover on all possible places.

That's a bad idea.

You should use USB stick, install it there and test it and configure it on that USB stick. Only when you have all working from the USB stick, then it's a good time to move it to HD. In that way you would not mess with your current bootloaders.

Regarding Chameleon ... you can fix it in on your Lion disk:

- remove /boot, /boot3, /boot6, /EFI folder from there (those are Clover files)

- and rename /boot1 to /boot (current boot1 is your Chimera)

- then try to reboot by choosing Lion disk as boot disk - should start your Chimera from that disk

- additionally, you can replace current Clover's "boot1h2" partition boot loader with standard Chameleon's, to get rid of 2 seconds pause during boot:

--- you may use ChameleonWizard and install "boot0hfs" to Lion partition

Regarding ML disk: you can safely delete Clover's files from ML partition, since you have installed Clover to EFI partition on that disk also. Meaning: if you choose ML disk, then that will start Clover from EFI partition and not from ML. So:

- remove /boot, /boot3, /boot6, /EFI folder from ML partition

And use USB stick for Clover tests first. Hope this helps.

Thanks, I'll try it

kyndder · November 6, 2012

I will send my config.plist later when I came home...

@shiecldk

Here´s my config.plist ....

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com...yList-1.0.dtd">

<dict>

<key>Pointer</key>

<dict>

<key>Speed</key>

<key>DoubleClickTime</key>

</dict>

<key>KernelAndKextPatches</key>

<dict>

<key>Debug</key>

<key>ATIConnectorInfo</key>

<key>KernelCpu</key>

<key>AsusAICPUPM</key>

<key>AppleRTC</key>

</dict>

<!--

<key>Volumes</key>

<dict>

<key>HideVolumes</key>

<dict>

<dict>

<key>VolumeString</key>

</dict>

<dict>

<key>VolumeString</key>

</dict>

<dict>

<key>VolumeString</key>

</dict>

<key>HideAllLegacy</key>

</dict>

-->

<key>SystemParameters</key>

<dict>

<key>iCloudFix</key>

<string>npci=0x2000 darkwake=0 slide=0</string>

<key>DefaultBootVolume</key>

<key>CustomUUID</key>

<key>InjectSystemID</key>

<key>LegacyBoot</key>

<key>BacklightLevel</key>

</dict>

<key>SMBIOS</key>

<dict>

<key>ProductName</key>

<string>MacPro5,1</string>

</dict>

<dict>

<key>Turbo</key>

</dict>

<key>Graphics</key>

<dict>

<key>CustomEDID</key>

<key>InjectEDID</key>

<key>GraphicsInjector</key>

<key>LoadVBios</key>

<key>PatchVBios</key>

<key>VideoPorts</key>

<key>FBName</key>

<string>Makaka</string>

<key>NVCAP</key>

<key>display-cfg</key>

</dict>

<dict>

<key>StringInjector</key>

<key>DeviceProperties</key>

<key>PCIRootUID</key>

<key>HDAInjection</key>

<key>USBInjection</key>

<key>LpcTune</key>

</dict>

<dict>

<key>DsdtName</key>

<key>DropOemSSDT</key>

<key>DropAPIC</key>

<key>DropMCFG</key>

<key>DropHPET</key>

<key>DropECDT</key>

<key>GenerateCStates</key>

<key>GeneratePStates</key>

<key>PLimitDict</key>

<key>UnderVoltStep</key>

<key>EnableC6</key>

<key>EnableC4</key>

<key>EnableC2</key>

<key>EnableISS</key>

<key>ResetAddress</key>

<key>ResetValue</key>

<key>smartUPS</key>

<key>PatchNMI</key>

<key>FixDsdtMask</key>

</dict>

</plist>

I commented ou the Volumes section for obvious reasons...

shiecldk · November 6, 2012

@shiecldk

Here´s my config.plist ....

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com...yList-1.0.dtd">

<plist version="1.0">

<dict>

<key>Pointer</key>

<dict>

<key>Speed</key>

<string>20</string>

<key>DoubleClickTime</key>

<string>500</string>

</dict>

<key>KernelAndKextPatches</key>

<dict>

<key>Debug</key>

<string>No</string>

<key>ATIConnectorInfo</key>

<string>No</string>

<key>KernelCpu</key>

<string>No</string>

<key>AsusAICPUPM</key>

<string>No</string>

<key>AppleRTC</key>

<string>Yes</string>

</dict>



<key>SystemParameters</key>

<dict>

<key>iCloudFix</key>

<string>Yes</string>

<key>boot-args</key>

<string>npci=0x2000 darkwake=0 slide=0</string>

<key>prev-lang:kbd</key>

<string>en:0</string>

<key>DefaultBootVolume</key>

<string></string>

<key>CustomUUID</key>

<string>511CE200-1000-4000-9999-010203040506</string>

<key>InjectSystemID</key>

<string>Yes</string>

<key>LegacyBoot</key>

<string>PBR</string>

<key>BacklightLevel</key>

<string>0x0</string>

</dict>

<key>SMBIOS</key>

<dict>

<key>ProductName</key>

<string>MacPro5,1</string>

</dict>

<key>CPU</key>

<dict>

<key>Turbo</key>

<string>Yes</string>

</dict>

<key>Graphics</key>

<dict>

<key>CustomEDID</key>

<string></string>

<key>InjectEDID</key>

<string>No</string>

<key>GraphicsInjector</key>

<string>Yes</string>

<key>VRAM</key>

<string>1024</string>

<key>LoadVBios</key>

<string>No</string>

<key>PatchVBios</key>

<string>No</string>

<key>VideoPorts</key>

<string>2</string>

<key>FBName</key>

<string>Makaka</string>

<key>NVCAP</key>

<string>04000000000003000C0000000000000A00000000</string>

<key>display-cfg</key>

<string>03010300FFFF0001</string>

</dict>

<key>PCI</key>

<dict>

<key>StringInjector</key>

<string>No</string>

<key>DeviceProperties</key>

<string></string>

<key>PCIRootUID</key>

<string>0</string>

<key>HDAInjection</key>

<string>No</string>

<key>USBInjection</key>

<string>Yes</string>

<key>LpcTune</key>

<string>Yes</string>

</dict>

<key>ACPI</key>

<dict>

<key>DsdtName</key>

<string></string>

<key>DropOemSSDT</key>

<string>Yes</string>

<key>DropAPIC</key>

<string>No</string>

<key>DropMCFG</key>

<string>No</string>

<key>DropHPET</key>

<string>No</string>

<key>DropECDT</key>

<string>No</string>

<key>GenerateCStates</key>

<string>No</string>

<key>GeneratePStates</key>

<string>No</string>

<key>PLimitDict</key>

<string>0</string>

<key>UnderVoltStep</key>

<string>0</string>

<key>EnableC6</key>

<string>Yes</string>

<key>EnableC4</key>

<string>Yes</string>

<key>EnableC2</key>

<string>Yes</string>

<key>EnableISS</key>

<string>No</string>

<key>ResetAddress</key>

<string>0x64</string>

<key>ResetValue</key>

<string>0xFE</string>

<key>smartUPS</key>

<string>No</string>

<key>PatchNMI</key>

<string>No</string>

<key>FixDsdtMask</key>

<string>0xBCB7</string>

</dict>

</dict>

</plist>

I commented ou the Volumes section for obvious reasons...

Thanks, kyndder!

But it still can't wake every time. (Only 5% of chance to wake it up successfully.)

I think I should give up "sleeping" at this moment... I had to prepare for my college entrance exam in Taiwan now. :hammer: (Which is eighty days to go.... :shock: )

I'm appreciative of your help. :thumbsup_anim:

Please keep in touch with me.

kyndder · November 6, 2012

Thanks, kyndder!

But it still can't wake every time. (Only 5% of chance to wake it up successfully.)

Sorry buddy... I don't know what could be this issue...

As I told to you before, I don't have the habit to use sleep function, but on the tests that I

done, every single one was sucessful to sleep and wake up, so 100% sucessfully...

Maybe the GA-P67A-UD3-B3 UEFI BIOS fits better on my machine than on yours...

I think I should give up "sleeping" at this moment... I had to prepare for my college entrance exam in Taiwan now. (Which is eighty days to go.... )

Yes, take care of your future and good luck!

I'm appreciative of your help.
Please keep in touch with me.

You're welcome, but we both helped one to another!!!

Mrengles · November 6, 2012

Proper config:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
... other sections ...
<key>KernelAndKextPatches</key>
<dict>
<key>Debug</key>
<string>Yes</string>
... other options ...
<key>KextsToPatch</key>
<dict>
<key>0</key>
<dict>
<key>Name</key>
<string>IOAHCIBlockStorage</string>
<key>Find</key>
<data>QVBQTEUgU1NE</data>
<key>Replace</key>
<data>AAAAAAAAAAAA</data>
</dict>
</dict>
</dict>
</dict>
</plist>
Note Debug=Yes above - it's just for testing (although this testing is not complete yet). You can set it to No when you are done.

Data inside <data> is binary and is base64 encoded in plist. Plist editor decodes it and shows real binary data.

Thanks! I've got the TRIM patch working, The problem was that I had the KextsToPatch as its own Dictionary and not under the KernelAndKextPatches Dictionary.

Every thing is working with my build except wake from sleep with USB keyboard/mouse, Bluetooth, or PCI Airport card, Realtek NIC. I also have a weird issue with USB 3.0 when its turned on, that only usb 3.0 devices work in those ports. It's not backwards comatiable with USB 2.0/1.0 devices.

Thanks again dmazar for help with TRIM, any ideas for getting wake/ and USB 3.0 working? Injecting USB did not work.

-Mrengles

PS. power button wake the system, but I have to unplug/replug the keyboard to get it working with either USB 1.0/2.0/3.0

Attached my /EFI/config.plist below...

Thanks again!

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>SMBIOS</key>
<dict>
 <key>Family</key>
 <string>Mac Pro</string>
 <key>ProductName</key>
 <string>MacPro3,1</string>
 <key>Board-ID</key>
 <string>Mac-F42C88C8</string>
 <key>SerialNumber</key>
 <string>G8948123XYL</string>
 <key>BiosVersion</key>
 <string>MP31.88Z.006C.B05.0802291410</string>
 <key>SMUUID</key>
 <string>XXXE5967-XXXX-XXXX-XXXX-XXX12A20DDC7</string>
 <key>ChassisAssetTag</key>
 <string>P8Z77-M-Pro</string>
</dict>
<key>SystemParameters</key>
<dict>
 <key>DefaultBootVolume</key>
 <string>Macintosh SSD</string>
 <key>boot-args</key>
 <string>arch=x86_64 slide=0</string>
 <key>CustomUUID</key>
 <string>XXX22B2C-XXXX-XXXX-XXXX-XXX000EE5F09</string>
 <key>prev-lang:kbd</key>
 <string>en:0</string>
 <key>InjectSystemID</key>
 <string>YES</string>
</dict>
<key>ACPI</key>
<dict>
 <key>DsdtName</key>
 <string>DSDT.aml</string>
 <key>FixDsdtMask</key>
 <string>0x3031</string>
 <key>EnableISS</key>
 <string>YES</string>
 <key>GenerateCStates</key>
 <string>YES</string>
 <key>GeneratePStates</key>
 <string>YES</string>
 <key>EnableC2</key>
 <string>YES</string>
 <key>EnableC4</key>
 <string>NO</string>
 <key>EnableC6</key>
 <string>YES</string>
</dict>
<key>PCI</key>
<dict>
 <key>StringInjector</key>
 <string>NO</string>
 <key>PCIRootUID</key>
 <string>0</string>
 <key>HDAInjection</key>
 <string>1</string>
</dict>
<key>CPU</key>
<dict>
 <key>Turbo</key>
 <string>YES</string>
</dict>
<key>Graphics</key>
<dict>
 <key>GraphicsInjector</key>
 <string>NO</string>
 <key>LoadVBios</key>
 <string>NO</string>
 <key>VideoPorts</key>
 <string>4</string>
</dict>
<key>KernelAndKextPatches</key>
<dict>
 <key>AppleRTC</key>
 <string>YES</string>
 <key>AsusAICPUPM</key>
 <string>NO</string>
 <key>KernelCpu</key>
 <string>NO</string>
 <key>KextsToPatch</key>
 <dict>
  <key>0</key>
  <dict>
   <key>Name</key>
   <string>IOAHCIBlockStorage</string>
   <key>Find</key>
   <data>QVBQTEUgU1NE</data>
   <key>Replace</key>
   <data>AAAAAAAAAAAA</data>
  </dict>
 </dict>
</dict>
<key>Volumes</key>
<dict/>
<key>Pointer</key>
<dict>
 <key>Speed</key>
 <string>8</string>
 <key>DoubleClickTime</key>
 <string>500</string>
</dict>
</dict>
</plist>

dmazar · November 6, 2012

I guess you need to clean ACPI section

If you have GenerateCStates and GeneratePStates, then you probably also need DropOemSSDT=Yes. If you also have your own SSDT for P states for example, then you do not need GeneratePStates.

If you already have patched DSDT in ACPI/patched (DsdtName=DSDT.aml - you do not need to specify it), then you probably do not need FixDsdtMask=0x3031 but FixDsdtMask=0. Your DSDT mask injects USB stuff into DSDT - maybe this is causing problems for you.

Something like:

<key>ACPI</key>
<dict>
<key>FixDsdtMask</key>
<string>0</string>
<key>DropOemSSDT</key>
<string>Yes</string>
<key>GenerateCStates</key>
<string>Yes</string>
<key>GeneratePStates</key>
<string>Yes</string>
plus your EnableCx - if needed.
</dict>

(if you have your own SSDT with p states, then remove GeneratePStates)

And then I would also try with disabled USB device tree injection:

<key>PCI</key>
<dict>
<key>HDAInjection</key>
<string>1</string>
<key>USBInjection</key>
<string>No</string>
</dict>

Mrengles · November 6, 2012

I guess you need to clean ACPI section

If you have GenerateCStates and GeneratePStates, then you probably also need DropOemSSDT=Yes. If you also have your own SSDT for P states for example, then you do not need GeneratePStates.

If you already have patched DSDT in ACPI/patched (DsdtName=DSDT.aml - you do not need to specify it), then you probably do not need FixDsdtMask=0x3031 but FixDsdtMask=0. Your DSDT mask injects USB stuff into DSDT - maybe this is causing problems for you.

Something like:
<key>ACPI</key>
<dict>
<key>FixDsdtMask</key>
<string>0</string>
<key>DropOemSSDT</key>
<string>Yes</string>
<key>GenerateCStates</key>
<string>Yes</string>
<key>GeneratePStates</key>
<string>Yes</string>
plus your EnableCx - if needed.
</dict>
(if you have your own SSDT with p states, then remove GeneratePStates)

And then I would also try with disabled USB device tree injection:
<key>PCI</key>
<dict>
<key>HDAInjection</key>
<string>1</string>
<key>USBInjection</key>
<string>No</string>
</dict>

Thanks, for the advise. I'll make some changes, and edit this post, with how it goes...

Mrengles · November 7, 2012

Dmazar,

I made the changes you suggested, dropssdt, gen c&p states yes, and I'm not using Fixdsdtmadk. When I use USB keyboard, I need to unplug and replug to get system to fully wake, with a second keyboard/mouse click. But I also get a KP that forces the computer to restart. It looks like it tries to load the hibernate image and fails.

Still not luck with usb3.

Working wake is getting closer, but still not quite right.

tonydickinson · November 7, 2012

Dmazar,

I made the changes you suggested, dropssdt, gen c&p states yes, and I'm not using Fixdsdtmadk. When I use USB keyboard, I need to unplug and replug to get system to fully wake, with a second keyboard/mouse click. But I also get a KP that forces the computer to restart. It looks like it tries to load the hibernate image and fails.

Still not luck with usb3.

Working wake is getting closer, but still not quite right.

@mrengles - Not sure that your config.plist is correct as xCode shows it as "Corrupt" My entry for trim is:

<dict>

<key>AppleRTC</key>

<key>AsusAICPUPM</key>

<key>KernelCpu</key>

<key>KextsToPatch</key>

<string>IOAHCIBlockStorage</string>

<string>QVBQTEUgU1NE</string>

<key>Replace</key>

<string>AAAAAAAAAAAA</string>

</dict>

And it works..! It is always a good idea (I think) to use xCode to check the validity of the file, as otherwise you can make make many changes that might not work in OSX if the syntax is not correct.

Regarding the USB3 - I am an eSata man myself and USB is not of great interest or concern, however I believe that the USB kext apple uses PXHCD.kext, is not fully compatible with the Z77 chipset. (Dmazar et all - correct me if I am wrong) however the Intel USB3 should partially work, but NOT the ASMEDIA USB 3 ports.

My Z77 wakes from sleep fine although one has to use the power button to wake, then the mouse to wake the monitor, but USB works fine on waking. I am using the default USB settings in the Asus 1616 BIOS.

Mrengles · November 7, 2012

@mrengles - Not sure that your config.plist is correct as xCode shows it as "Corrupt" My entry for trim is:

<dict>

<key>AppleRTC</key>

<string>Yes</string>

<key>AsusAICPUPM</key>

<string>No</string>

<key>KernelCpu</key>

<string>No</string>

<key>KextsToPatch</key>

<integer>0</integer>

<key>Name</key>

<string>IOAHCIBlockStorage</string>

<key>Find</key>

<string>QVBQTEUgU1NE</string>

<key>Replace</key>

<string>AAAAAAAAAAAA</string>

</dict>

And it works..! It is always a good idea (I think) to use xCode to check the validity of the file, as otherwise you can make make many changes that might not work in OSX if the syntax is not correct.

Regarding the USB3 - I am an eSata man myself and USB is not of great interest or concern, however I believe that the USB kext apple uses PXHCD.kext, is not fully compatible with the Z77 chipset. (Dmazar et all - correct me if I am wrong) however the Intel USB3 should partially work, but NOT the ASMEDIA USB 3 ports.

My Z77 wakes from sleep fine although one has to use the power button to wake, then the mouse to wake the monitor, but USB works fine on waking. I am using the default USB settings in the Asus 1616 BIOS.

Hey, I'm not sure about the file being corrupt with Xcode, because I used Xcode to create the config.plist file. I think your problem is copy and pasting from this site. I'll post a zipped copy at the end of this post.

I fixed my KP by adding darkwake=0 to the Kernel Flags (happens only once and a while now), No longer need to use the power button to wake the machine. But still need to provide two taps/clicks, one before I unplug the keyboard, and one after. The keyboard (all USB) is dead on wake, but works after I unplug one of my devices.

I'm not using the asmedia 3.0 ports, they are disabled in the UEFI BIOS, These problems are happening with the Intel Z77 ports. They work fine when 3.0 is disabled in the BIOS.

Here is a zipped copy of my config.plist

http://organicdata.n...onfig.plist.zip

Thanks for the advise.

magnifico · November 7, 2012

:hammer:

Hi all..for user boot UEFI

did you find these updates?

http://www.mediafire...ybdwxqnt4y1fvww

this is a imac original

dmazar · November 7, 2012

@mrengles - sorry, but do not know how to help. It looks like it's some issue with DSDT patches. Does it work with Chameleon? If yes, did you compare ACPI tables from Clover and Chameleon (DarwinDumper is a great tool). I'm not able to tell anything more.

tonydickinson · November 8, 2012

@mrengles - Robert - you are likely correct regarding the copy/paste...

I am not sure about your ACPI section of your config plist and I see no KPs.

Your ACPI.

<dict>

<key>DropOemSSDT</key>

<key>EnableISS</key>

<key>GenerateCStates</key>

<key>GeneratePStates</key>

<key>EnableC2</key>

</dict>

MY ACPI options.

<dict>

<key>DsdtName</key>

<key>FixDsdtMask</key>

<key>DropOemSSDT</key>

<key>DropAPIC</key>

<key>DropMCFG</key>

<key>DropHPET</key>

<key>DropECDT</key>

<key>GenerateCStates</key>

<key>GeneratePStates</key>

<key>PLimitDict</key>

<key>UnderVoltStep</key>

<key>EnableC6</key>

<key>EnableC4</key>

<key>EnableC2</key>

</dict>

I am not sure - as I recall reading somewhere else that you are using a DSDT.aml with your Z77 motherboard, from day one I have found that with the modded Asus BIOS a DSDT is not necessary, and for me everything just works with the exception of an iffy USB3 service.

Me I do not use a DSDT at all, and in my config.plist the BIOS.aml is what Clover picks up from the BIOS - Great fun - the only ongoing issue I have with Clover is Windows8 as despite all I cannot get it to load via Clover as long as I use the ATI discrete graphics card which I would prefer to use as I bought it... If I use the F8 option and select Windows Boot Manager it works fine.

Dmazar and the team over at Project OS X have been very helpful and we did some tests and if I remove the 6870 and use the on board HD4000 it works fine so it has to be the way I am configuring the graphics.

Win8 is growing on me, it is useful to have as a tool, but there are great advantages in not using virtual versions

Keep on. If you are interested a copy of my config.plist is attached.

Brgds/Tony.

Hi all..for user boot UEFI

did you find these updates?

http://www.mediafire...ybdwxqnt4y1fvww

this is a imac original

Bonjorno - Thanks I will investigate further as this looks like a new refit??? - I will research further as it looks more like Refind to me particularly with the rEFItBlesser. I am sure Slice/Dmazar will enlighten us...

Thank for posting - interesting.

config.plist.zip

Slice · November 8, 2012

refit? rEFInd? rEFItBlesser? - what do you want to ask?

Mrengles · November 8, 2012

New & Updated mrenglesTheme by mrengles for Clover v2 Bootloader!

mrenglesTheme v1.1 Fixed a few visual bugs. (Nov 8th, 2012)

mrenglesTheme v1.2 Added some alternate png artwork such as about, help, shutdown, and restart. (Nov 10th, 2012)

mrenglesTheme v1.3 Added a couple of icons to help identify the type of operating system (OS) on the selected disk. (Nov 11th, 2012)

mrenglesTheme v1.5 Added some extra artwork, New Anti-Aliased Fonts, and detailed the refit.conf settings. (Nov 14th, 2012)

This download includes all of the necessary files for an easy installation. They just need to be moved into the correct locations.

/EFI/BOOT/font/ - Fonts go here>
/EFI/BOOT/refit.conf - Don't forget to backup original use something like: $ cp refit.conf refit.conf-original-backup
/EFI/BOOT/themes/mrenglesTheme

...

mrenglesTheme v1.5 Download

mrenglesTheme Extra Fonts Download

Think twice about using this theme if you have allot of operating system drives visible in Clover. My theme shows limited OS badges because I wanted to create a simple theme that was easy on the eyes without allot of advertising going on. :wink2:

Thanks again to everyone who provided help & support!

-Mrengles

Edited November 15, 2012 by mrengles

xmen107 · November 8, 2012

I like your theme :thumbsup_anim:

Clover General discussion

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites