1876 replies to this topic

[Slice]

After 10.8.2 update, rc.shutdown.local and rc.local stop working. Any solution for that?

False.
I have 10.8.2 and my scripts work as before.

[STLVNUB]

The key word here being "After" 10.8.2 update.
Use latest Clover package and Re-Install it, will just upgrade your Clover, just use same selections you used originally.

[Taruga]

I found out that wake only works when I boot with -v with an earlier version of OsxAptioFixDrv-64.efi.

Where can I get that version of OsxAptioFixDrv-64.efi.
I would like to have sleep working again, but it´s not being easy.

[shiecldk]

Where can I get that version of OsxAptioFixDrv-64.efi.
I would like to have sleep working again, but it´s not being easy.

These two work when boot with -v for me:
 OsxAptioFixDrv-64.efi.zip   11.77KB   40 downloads

 OsxAptioFixDrv-64.efi.zip   11.3KB   27 downloads

[antoniodapc]

I copied the folder "EFI" using this command from the Finder in the partition "EFI (Volumes/EFI , disk0s1) " disk formatted in GUID

sudo mkdir /Volumes/EFI
sudo mount_msdos /dev/disk0s1 /Volumes/EFI/

with Unpackges I recovered from Clover.pkg the file boot and copied to the Volume/Efi

But I still can not boot ...
What's wrong?

Please I Need Help

[STLVNUB]

This one is easy, and the way I've done it.
Install package to ML partition with default settings
run those commands again.^^^
and this one
sudo cp -R /EFI/* /Volumes/EFI
delete /EFI or rename /EFI1
restart and wallah
done

[antoniodapc]

This one is easy, and the way I've done it.
Install package to ML partition with default settings
run those commands again.^^^
and this one
sudo cp -R /EFI/* /Volumes/EFI
delete /EFI or rename /EFI1
restart and wallah
done

Which is of the default option for EFI boot

• BIOS MBR boot0 (HFS+Fat32)
• BIOS MBR Boot0hfs (HFS+Fat32)
• BIOS GPT EFI (HFS + FAT32)
• UEFI boot

My disc Is partitioned in GUID with Sectors to 4096

[STLVNUB]

Clover currently does NOT support 4K sectors ( may be coming shortly though )
Use a USB flash drive and install to that.
You will need to boot off USB to boot the HD

OR try smaller HD and do as I said.

[Taruga]

These two work when boot with -v for me:
 OsxAptioFixDrv-64.efi.zip   11.77KB   40 downloads

 OsxAptioFixDrv-64.efi.zip   11.3KB   27 downloads

Only had time to test with the first version and surprise.... sleep worked, wake worked! After wake I tried to sleep a second time and it just did nothing.
But after wake I had no ethernet, only wifi. Since my board has 2 network connectors, I will activated the other and test with it also.
Later today, I will test the other version.

[antoniodapc]

Clover currently does NOT support 4K sectors ( may be coming shortly though )
Use a USB flash drive and install to that.
You will need to boot off USB to boot the HD

OR try smaller HD and do as I said.

that bad news

<?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>ACPI</key>
  <dict>
   <key>DropOemSSDT</key>
   <string>Yes</string>
   <key>GenerateCStates</key>
   <string>Yes</string>
   <key>GeneratePStates</key>
   <string>Yes</string>
   <key>PLimitDict</key>
   <string>1</string>
  </dict>
 
<key>SystemParameters</key>
<dict>
  <key>boot-args</key>
  <string>-v npci=0x2000 slide=0</string>
  <key>prev-lang:kbd</key>
  <string>en:0</string>
  <key>InjectSystemID</key>
  <string>Yes</string>
  <key>LegacyBoot</key>
  <string>PBR</string>
  <key>iCloudFix</key>
  <string>Yes</string>
</dict>
<dict>
  <key>AppleRTC</key>
  <string>Yes</string>
  <key>StringInjector</key>
  <string>No</string>
<dict>
<key>Pointer</key>
<dict>
  <key>Speed</key>
  <string>8</string>
</dict>
<key>Graphics</key>
<dict>
  <key>GraphicsInjector</key>
  <string>Yes</string>
  <key>PatchVBiosBytes</key>
  <dict>
   <key>Find</key>
   <data>gAeoAqAF</data>
   <key>Replace</key>
   <data>gAeoAjgE</data>
  </dict>
</dict>
</dict>
</plist>

my config file is correct

[dmazar]

These two work when boot with -v for me:
 OsxAptioFixDrv-64.efi.zip   11.77KB   40 downloads

 OsxAptioFixDrv-64.efi.zip   11.3KB   27 downloads

If this makes you a difference in sleep, can you identify me which versions are those? Where did you get it?

[Taruga]

If this makes you a difference in sleep, can you identify me which versions are those? Where did you get it?

Well, it makes a difference with him, as it did with me. We should investigate this better.
I only had time to test the 1st of the 2 files he posted.
And it was the first time I got my pc to sleep and wake while booting in UEFI mode.

[dmazar]

My disc Is partitioned in GUID with Sectors to 4096

What does that mean? Which disk do you have?

Clover currently does NOT support 4K sectors ( may be coming shortly though )

Support for real 4K disk will probably not come, at least, I believe, not shortly. I think this will require rewriting/modifying all boot sector loaders.


But, as far as I understood, real 4K disks (in the sense that system communicates with disks with 4K sectors) are very rare. Almost all 4K disks are emulating 512 bytes sectors and should work like 512 disks. Check this.
Meaning, no issues with Clover or Chameleon with 4K 512e disks. Except known issue with some of them when dd utility can not write boot1h - see here.

[antoniodapc]

What does that mean? Which disk do you have?


Support for real 4K disk will probably not come, at least, I believe, not shortly. I think this will require rewriting/modifying all boot sector loaders.


But, as far as I understood, real 4K disks (in the sense that system communicates with disks with 4K sectors) are very rare. Almost all 4K disks are emulating 512 bytes sectors and should work like 512 disks. Check this.
Meaning, no issues with Clover or Chameleon with 4K 512e disks. Except known issue with some of them when dd utility can not write boot1h - see here.

unfortunately yes, even chameleon I install it manually bs=4096

[shiecldk]

If this makes you a difference in sleep, can you identify me which versions are those? Where did you get it?

I got it from anther person... I'll ask him if he remember.
But the other one I don't remember where it came from... I only know these two are different by checking their md5.

Well, it makes a difference with him, as it did with me. We should investigate this better.
I only had time to test the 1st of the 2 files he posted.
And it was the first time I got my pc to sleep and wake while booting in UEFI mode.

Did you get wake from sleep work with or without -v?
And are you able to wake it with darkwake=0?

Mine can't wake with darkwake=0 even add -v in boot-args.

[Taruga]

Did you get wake work with or without -v in boot?
And are you able to wake it with darkwake=0 in

I always use -v and I tested it with darkwake=no, I had no more time left to make proper testing.

[STLVNUB]

What does that mean? Which disk do you have?


Support for real 4K disk will probably not come, at least, I believe, not shortly. I think this will require rewriting/modifying all boot sector loaders.

On it now

[Slice]

Don't know what is the problem with sleep/wake.

Nov 30 22:44:08 localhost WindowServer[97]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
Nov 30 22:44:08 localhost kernel[0]: Wake reason: PWRB (User)

 screenshot9.png   304.12KB   22 downloads
 Clover-911-test.zip   288.05KB   22 downloads
Test, please, this combination for UEFI boot.
My config is almost empty.

<key>ACPI</key>
<dict>
  <key>DsdtName</key>
  <string>DSDT-n.aml</string>
  <key>DropOemSSDT</key>
  <string>Yes</string>
  <key>GenerateCStates</key>
  <string>Yes</string>
  <key>GeneratePStates</key>
  <string>Yes</string>
  <key>PLimitDict</key>
  <string>0</string>
  <key>UnderVoltStep</key>
  <string>0</string>
  <key>EnableC6</key>
  <string>No</string>
  <key>EnableC4</key>
  <string>No</string>
  <key>EnableC2</key>
  <string>Yes</string>
  <key>EnableISS</key>
  <string>Yes</string>
  <key>ResetAddress</key>
  <string>0xCF9</string>
  <key>ResetValue</key>
  <string>0x06</string>
  <key>smartUPS</key>
  <string>No</string>
  <key>PatchNMI</key>
  <string>No</string>
  <key>FixDsdtMask</key>
  <string>0xB1BF</string>
</dict>
<key>Graphics</key>
<dict>
  <key>GraphicsInjector</key>
  <string>Yes</string>
  <key>FBName</key>
  <string>Ipomoea</string>
  <key>LoadVBios</key>
  <string>No</string>
  <key>VideoPorts</key>
  <string>3</string>
  <key>PatchVBios</key>
  <string>Yes</string>
</dict>
<key>CPU</key>
<dict>
  <key>Turbo</key>
  <string>No</string>
  <key>ProcessorType</key>
  <string>0x0903</string>
  <key>BusSpeedkHz</key>
  <string>99790</string>
  <key>QPI</key>
  <string>6400</string>
</dict>
<key>KernelAndKextPatches</key>
<dict>
  <key>KernelCpu</key>
  <string>No</string>
  <key>ATIConnectorsController</key>
  <string>6000</string>
  <key>ATIConnectorsData</key>
  <string>000400000403000000010000120401050008000004020000000100001102040310000000100000000001000000000002</string>
  <key>ATIConnectorsPatch</key>
  <string>040000000403000000010000100001061000000010000000000100000000000100080000040200000001000012040403</string>
  <key>AsusAICPUPM</key>
  <string>No</string>
  <key>AppleRTC</key>
  <string>Yes</string>
  <key>KextsToPatch</key>
  <dict>
   <key>0</key>
   <dict>
    <key>Name</key>
    <string>VoodooHDA</string>
    <key>Find</key>
    <data>SGVhZHBob25lcwA=</data>
    <key>Replace</key>
    <data>VGVsZXBob25lcwA=</data>
   </dict>
   <key>1</key>
   <dict>
    <key>Name</key>
    <string>AppleAHCIPort</string>
    <key>Find</key>
    <data>RXh0ZXJuYWw=</data>
    <key>Replace</key>
    <data>SW50ZXJuYWw=</data>
   </dict>
  </dict>
</dict>

and serials/uuid/volumes

[dmazar]

ML install does not need FakeSMC. First time heard it from Trauma here (23/03/2011, some time ago). My response was:

But if Apple one day releases OSX that does (not) need some SMC fix, I would not be surprised if it gets unnoticed for a while, since we are all automatically adding FakeSMC to every install.

Well, installed OSX needs it, but not installer.

Correction or amendment to above ...

STLVNUB claimed that he needed FakeSMC for installer. D-an-W also needed it. So, I have downloaded latest ML install from App Store, restored Install OS X Mountain Lion/Contents/SharedSupport/InstallESD.dmg to USB stick, checked booting of it and - yes, FakeSMC is needed. Was not needed for 10.8.0 (and some DP releases), but is needed again.

Thanks to FrodoKenny, it's enough here to put FakeSMC.kext to Clover's /EFI/kexts/Other installer's kernelcache boots fine (did not checked full install).

Note: this kext injection into kernelcache works with 10.8.2 fine, but that injection requires patching of the kernel on the fly, in memory. There are no guarantees that this patching will work with future kernel versions, without some intervention to the Clover code.

My config is almost empty.

Almost ... yes.

[antipop2323]

Hey all, I just skimmed through this entire thread and wanted to relate some of my experiences UEFI booting Clover on a P8Z77-V Pro, particularly regarding wake from sleep.

Using a DSDT I created w/ only simple HDEF fix I wake to black screen (works fine in Cham)

NO DSDT, wakes fine but only w/ power button (no usb peripherals/bluetooth)

With:

<key>PCI</key>
<dict>
...
<key>USBInjection</key>
<string>No</string>
</dict>

Can wake from peripherals/bluetooth BUT restarts after 30 seconds

(tried shiecldk's OsxAptioFixDrv-64.efi files but still restarts after 30 seconds)

So that's where I'm at, can wake fine but only w/ power button, OR w/ peripherals and restart after 30 seconds or so. For the record, my usb devices do work fine after waking.

Also, my mouse doesn't work properly within the bootloader when UEFI booting, I think somewhere back towards the beginning of the thread dmazar said it's due to OsxAptioFixDrv-64.efi... Basically it actually works, it just doesn't refresh its position when I move the mouse. However, if I right click the mouse it jumps to the place that I moved it to, so I can quasi use it by guessing and right clicking to refresh its position lol.

Anyways, everything else seems to be working in an orderly fashion, speedstepping, restart, shutdown etc.