Search results

I've the same hardware. Until yesterday 10.10.1 with Clover was running on my machine, installed by using this guide (#1). Now I got a new HD and I want to install 10.10.3 the same way. But it won't work. After installing clover, I got this error: Does anyone know what this error means?

With Windows sleep doesn't work, too. If I wake up the laptop after setting it to sleep it also restarts under Windows (8.1). Can the problem have something to do with the Bios Mod? Or do I have to make changes in Bios? If yes, in which direction do I have to search?

Could the sleep problem have something to do with my wifi-card (AR9285)? In system.log I see this: kernel[0]: PXSX cannot assert wake from D3cold

btw. Since I use the other SSDT (SSDT3) my P-States are not working. I've 12 and 24 only. I removed this SSDT an got my P-States back.

And what could be the reason for this?

I click on "Sleep" in apple menu. Then I've to wait 20-25 sec. After that the cpu fan stops and I see the power led blinking. Is this sleep or am I wrong? If I compare it with my "real" MacBook, it takes a little bit longer til the led is blinking (about 12 sec). But sometimes the "real"...

That's what I've done: clean system.log - sleep laptop - reactivate - examine new system.log Find attached my fresh extracted DSDT and SSDT. I use Kext Wizard and I always repair permissions / rebuild cache - install kext - and again repair permissions / rebuild cache. Should I try...

I did it. I did exactly how you wrote in readme (first, second, thrid ...) but I get this message in system.log only: ACPIDebug: Version 0.1.0 starting Unfortunately nothing like "_WAK enter". Why are these methods never executed? I also made the test with ioio. This is the output in...

Another try...

P-States working now: I added the patches but still no wake up from sleep. Next I patched DSDT with debug.txt from your OS-X-ACPI-Debug, also patched with instrument_WAK_PTS.txt and installed the ACPIDebug.kext ('make' and 'make install'). Attached you'll find my ioreg and my system.log.

Ok, I think you'll need my system.log? Attached... Once again.

Yes, I use Geekbench 3. I think you mean, I should patch my DSDT with "Instrument _WAK/_PTS"? If I do this I get errors: IOReg is attached. Done. Nothing changed. How can I check if changes were executed?

Sorry, I don't understand. What do you mean with "if you push it"? If I "push" my CPU then I get 2.4Ghz max. Yes, LED is blinking. I used all of them (together). No change. Still no wake up. Just a restart. Maybe I should use only ONE of the patches?

Ok, so everything's fine with my output of AICPUPMI? Unfortunately the same result: sleep - try to wake up - but reboot Is this a USB problem? Do I've to make changes in BIOS?

Brightness works now. Thanks! I did this and Mavericks: Native CPU/IGPU Power Management Result: If I do not use SSDT (as you said in your last post) then I just have one State (800 Mhz). This is the result of cat /var/log/system.log | grep "AICPUPMI:" Aug 2 14:04:08 localhost kernel[0]...

Ok, I got it. I reseted bios, made a new stick with Unibeast4 and replaced VoodooPS2Controller by the latest one (1.8.12 I think; with the one in Unibeast I got KP). Installation of OS X finished and system is running. I installed some kexts and extracted my DSDT. There where one Error (TNOT)...

I made a new usb stick with Unibeast4. After booting 1. without dart and IGPlatform —> kernel panic 2. with dart=0 IGPlatformID=01660004 —> kernel panic 3. with dart=0 IGPlatformID=01660009 —> kernel panic I switched to an older VoodooPS2Controller (from Jessers' ZIP-File) and used the 3...

Ok, thanks! I got it...

This is what I see in my profile/signature: Lenovo Z710: i7-4700MQ, Intel HD 4600 @ 1920x1080, Samsung 840 EVO 250GB, Edimax EW-7811Un, OSX 10.9.1, No Sleep! But working!: - i7 Other - HD 4600 ACER Aspire E1-570-33214G50Mnrr: i3-3217U, Intel HD 4000, Toshiba Q-Series 128GB, AR9285, OSX...

At the moment I'm hackintoshing exactly the same laptop: Y580 with i7 and FullHD. What I did: - unlocking BIOS as discribed in the link in the main post of this thread - building USB-stick with UniBeast 4 - I could never boot the system - building USB-stick with UniBeast 3 - worked, but... -...