Jump to content
27,505 posts in this topic

Recommended Posts

Is your system able to wake after sleep?

 

Mine always restart after wake. I've tried both your and my DSDT, but got same result.

 

Same here...

 

I didn't tried till see your question... As I don't use sleep, I didn't tried yet...

 

I did a few tests here and I can't wake...

 

Did you tried using Clover's DSDT Fix Mask instead of custom DSDT???

About anime and other PNG graphics. I found that some programs export non-reliable png file (empty chunk headers). It's why it doesn't work.

Just resave every file with Photoshop and then it works.

Look example. It was 000, after photoshop it becomes 020

Screen shot 2012-10-22 at 10.48.51.png Screen shot 2012-10-22 at 10.49.07.png

 

I begin to write more detailed instruction now.

My latest screenshot

screenshot23.png

Same here...

 

I didn't tried till see your question... As I don't use sleep, I didn't tried yet...

 

I did a few tests here and I can't wake...

 

Did you tried using Clover's DSDT Fix Mask instead of custom DSDT???

I've tried SHUTDOWN+HPEF+LPC=0X0034, but it still doesn't work. Maybe try them separately later.

With this SleepEnabler.kext can make system wake after sleep, but it will shutdown itself after 1 minute form wake.

SleepEnabler.kext.zip

 

I've also extracted DSDT from DSDTSE when SleepEnabler.kext was loading. But with that DSDT, it still shutdown itself after 1 minute form wake.

I've tried SHUTDOWN+HPEF+LPC=0X0034, but it still doesn't work. Maybe try them separately later.

With this SleepEnabler.kext can make system wake after sleep, but it will shutdown itself after 1 minute form wake.

SleepEnabler.kext.zip

 

I've also extracted DSDT from DSDTSE when SleepEnabler.kext was loading. But with that DSDT, it still shutdown itself after 1 minute form wake.

 

You take a look at system.log to see what happened before shutdown???

You take a look at system.log to see what happened before shutdown???

This is what I got from system.log:

(I made it sleep at 9:24 and waked it up via usb keyboard at 9:25, but it rebooted instantly.)

 

9:24:30.419 WindowServer[132]: Created shield window 0x46 for display 0x0b41b7d8
9:24:30.419 WindowServer[132]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x0(0)
9:24:30.427 WindowServer[132]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x0(0)
9:24:32.342 mDNSResponder[62]: ActivateLocalProxy: No service for interface vnic0
9:24:32.342 mDNSResponder[62]: ActivateLocalProxy: No service for interface vnic1
9:27:48.000 bootlog[0]: BOOT_TIME 1350998868 0 //<--------another boot

 

I think it didn't have time to print any log out after it got a wake order (which cause it reboot)....

This is what I got from system.log:

(I made it sleep at 9:24 and waked it up via usb keyboard at 9:25, but it rebooted instantly.)

 

9:24:30.419 WindowServer[132]: Created shield window 0x46 for display 0x0b41b7d8
9:24:30.419 WindowServer[132]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x0(0)
9:24:30.427 WindowServer[132]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x0(0)
9:24:32.342 mDNSResponder[62]: ActivateLocalProxy: No service for interface vnic0
9:24:32.342 mDNSResponder[62]: ActivateLocalProxy: No service for interface vnic1
9:27:48.000 bootlog[0]: BOOT_TIME 1350998868 0 //<--------another boot

 

I think it didn't have time to print any log out after it got a wake order (which cause it reboot)....

 

I see...

 

 

Well, you told that you make a try with DSDT Fix mask using SHUTDOWN+HPET+LPC, make a try using

DTPG+HPET+LPC+SBUS+RTC...

 

You may try also, manually patching your AppleRTC.kext instead of use Clover´s RTC patch...

 

Also, you can check your hibernation mode...

 

sudo pmset -g | grep hibernatemode

 

Check if it´s set to 0, if no...

 

sudo pmset -a hibernatemode 0

 

This last days I´m very busy, because of this I can´t make some tests but I will when I get some time....

I see...

 

Well, you told that you make a try with DSDT Fix mask using SHUTDOWN+HPET+LPC, make a try using

DTPG+HPET+LPC+SBUS+RTC...

 

This last days I´m very busy, because of this I can´t make some tests but I will when I get some time....

Gigabyte has released new UEFI. Do you want to give it a try?

http://www.mediafire...7km5oa4l5gvye7a

Gigabyte has released new UEFI. Do you want to give it a try?

http://www.mediafire...7km5oa4l5gvye7a

 

Hmmm...

 

I think that update to a Beta BIOS of a different MOBO that we have is more

dangerous than update to a Final BIOS of a different MOBO that we have...

 

For now, I'll stay with U1a that is very stable and give me no issues till here...

 

I'm afraid that my coins end up... :2cents:

 

:whistle:

Hi guys,my laptop is Thinkpad W520.

 

Clover EFI take a very very long time from it start to welcome screen of mountain lion installtion.

Especially the last step, stay here up to three,,or four minutes long:

photo pic here: post-690005-0-77036000-1351253415_thumb.jpg

 

And when I remove the -v args, I see the circle rotation speed is slower than normal.

 

Then enter the welcome screen of ML installtion, the keyboard and mouse can not use.

However,the same driver can work fine when I use chameleon boot.

 

here is my clover setting:

<key>ACPI</key>
<dict>
<key>DropOemSSDT</key>
<string>Yes</string>
<key>DsdtName</key>
<string>dsdt.aml</string>
<key>EnableC2</key>
<string>Yes</string>
<key>EnableC4</key>
<string>No</string>
<key>EnableC6</key>
<string>Yes</string>
<key>EnableISS</key>
<string>Yes</string>
<key>FixDsdtMask</key>
<string>0x0000</string>
<key>GenerateCStates</key>
<string>Yes</string>
<key>GeneratePStates</key>
<string>Yes</string>
<key>PLimitDict</key>
<string>1</string>
<key>ResetAddress</key>
<string>0x64</string>
<key>ResetValue</key>
<string>0xFE</string>
<key>UnderVoltStep</key>
<string>1</string>
<key>smartUPS</key>
<string>No</string>
</dict>
<key>CPU</key>
<dict>
<key>BusSpeedkHz</key>
<string>100000</string>
<key>CpuFrequencyMHz</key>
<string>2200</string>
<key>ProcessorType</key>
<string>0x0201</string>
<key>QPI</key>
<string>4800</string>
<key>Turbo</key>
<string>Yes</string>
</dict>
<key>Graphics</key>
<dict>
<key>GraphicsInjector</key>
<string>Yes</string>
<key>VRAM</key>
<string>2048</string>
</dict>
<key>PCI</key>
<dict>
<key>StringInjector</key>
<string>No</string>
<key>USBInjection</key>
<string>Yes</string>
</dict>
<key>SMBIOS</key>
<dict>
<key>BiosReleaseDate</key>
<string>01/01/12</string>
<key>BiosVendor</key>
<string>Apple Inc.</string>
<key>BiosVersion</key>
<string>MBP81.88Z.0047.B0E.1104221557</string>
<key>Board-ID</key>
<string>Mac-942459F5819B171B</string>
<key>BoardManufacturer</key>
<string>Apple Inc.</string>
<key>BoardSerialNumber</key>
<string>C02GJ818DF92</string>
<key>BoardVersion</key>
<string>Proto1</string>
<key>ChassisAssetTag</key>
<string>LatitudeD420</string>
<key>ChassisManufacturer</key>
<string>Apple Inc.</string>
<key>Family</key>
<string>MacBook Pro</string>
<key>LocationInChassis</key>
<string>Part Component</string>
<key>Manufacturer</key>
<string>Apple Inc.</string>
<key>Mobile</key>
<string>Yes</string>
<key>ProductName</key>
<string>MacBookPro8,3</string>
<key>SerialNumber</key>
<string>C02GJ818DF92</string>
<key>Version</key>
<string>1.0</string>
</dict>
<key>SystemParameters</key>
<dict>
<key>CustomUUID</key>
<string>D239E796-E237-5253-9EF5-BB06F0B4F74B</string>
<key>boot-args</key>
<string>-v arch=x86_64 slide=0 npci=0x2000 Kernel=mach_kernel darkwake=0</string>
<key>iCloudFix</key>
<string>Yes</string>
<key>prev-lang:kbd</key>
<string>en:0</string>
</dict>

 

 

somebody help me,thanks

 

DarwinDumper_2.4.5_Chameleon_2.1_Lion_lynx.zip

UEFI boot or standard CloverEFI boot (boot0 -> boot1-> boot)?

 

I would remove OEM folder to avoid config.plist confusion. And then would try to "relax" config.plist:

- remove CPU section and let the Clover detect all what is needed

- would try to remove all from ACPI section and use only FixDsdtMask=0 for start - I guess you can always add other keys later to fix what needs to be fixed

I have a chameleon dual boot ML + Windows working perfectly, now I want to try Clover UEFI on my laptop HP Elitebook 8460p. I copied EFI folder to EFI partition, copied HFS and NTFS driver to EFI\driversUEFI64\, reboot and turn on UEFI in BIOS. It boots right to Clover! It shows 3 partitions: EFI, Legacy on Legacy HD2, Windows on Legacy HD3. I can't boot to Mac or Windows. How can I fix it?

I have a chameleon dual boot ML + Windows working perfectly, now I want to try Clover UEFI on my laptop HP Elitebook 8460p. I copied EFI folder to EFI partition, copied HFS and NTFS driver to EFI\driversUEFI64\, reboot and turn on UEFI in BIOS. It boots right to Clover! It shows 3 partitions: EFI, Legacy on Legacy HD2, Windows on Legacy HD3. I can't boot to Mac or Windows. How can I fix it?

 

Take a look...

 

Here > #150

 

And here > #193

I don't think I've seen any reports of anyone using Clover on a RAID setup.

I think I saw one report somewhere, maybe AppleLife.ru about RAID and Clover working. This is all about booting from Boot helper partition, right? If Clover can see that partition, then there should be no problems: Clover installed to that Boot helper partition or to EFI partition should work. Clover is just starting OSX's original boot loader (boot.efi) anyway, and this one should handle all OSX cases.

 

My guess.

@ Slice

 

what is the use for PartitionDxe and VboxExt ?

Just curious and may have overseen some explanation...

 

thank you

MY PartitionDxe differs from UEFI one by support of Apple Partitoning of DVD and hybrid MBR/GPT if you need it.

VBoxExt2 supports EXT2/3 file system of Linux if you want to start Linux EFI.

×
×
  • Create New...