wellstone
Members-
Posts
8 -
Joined
-
Last visited
Reputation
0 NeutralHackintosh Specs
-
CPU
i7 6700k
-
MOTHERBOARD
Gigabyte z170XP SLI
-
GPU
HD7700
-
Yes sleep is now working but, no audio. did you happen to remove some HDA info? USB still shows an error.
- 19,329 replies
-
- acpi
- acpispecification
-
(and 4 more)
Tagged with:
-
Nothing changed, same sleep cycle, wakes only once.
- 19,329 replies
-
- acpi
- acpispecification
-
(and 4 more)
Tagged with:
-
here are the ssdts, i will try what you have gave me now and see a result. BIOS is on manual. ssdts.zip
- 19,329 replies
-
- acpi
- acpispecification
-
(and 4 more)
Tagged with:
-
Changed everything you mentioned inside the DSDT with no success i still get the error (even with the EHC1 EHC3 and XHCI from the iMac). From what i see it's the USB2 hub causing the problem. I dont have any reports about the C & P states in the IOReg. I dont use any sleep enablers nor power managers. I dont have "Unsynchronized TSC" anywhere in the console, that's why i'm so curious to what is causing all of this. This is how the DSDT looks like now: DSDT.aml.zip
- 19,329 replies
-
- acpi
- acpispecification
-
(and 4 more)
Tagged with:
-
Also regarding sleep in the console this is what i have: 1/21/13 5:51:50.000 PM kernel[0]: Wake reason: GLAN XHC EHC1 1/21/13 5:51:50.000 PM kernel[0]: The USB device HubDevice (Port 1 of Hub at 0x1d000000) may have caused a wake by issuing a remote wakeup (2) 1/21/13 5:51:50.000 PM kernel[0]: The USB device Keyboard Hub (Port 1 of Hub at 0x1d100000) may have caused a wake by issuing a remote wakeup (3) 1/21/13 5:51:50.000 PM kernel[0]: The USB device Apple Keyboard (Port 2 of Hub at 0x1d110000) may have caused a wake by issuing a remote wakeup (3) 1/21/13 5:52:45.000 PM kernel[0]: Wake reason: PWRB (User) 1/22/13 6:06:46.000 PM kernel[0]: Wake reason: GLAN XHC EHC1 1/22/13 6:06:46.000 PM kernel[0]: The USB device HubDevice (Port 1 of Hub at 0x1d000000) may have caused a wake by issuing a remote wakeup (2) 1/22/13 6:06:46.000 PM kernel[0]: The USB device Keyboard Hub (Port 1 of Hub at 0x1d100000) may have caused a wake by issuing a remote wakeup (3) 1/22/13 6:06:47.000 PM kernel[0]: The USB device Apple Keyboard (Port 2 of Hub at 0x1d110000) may have caused a wake by issuing a remote wakeup (3) 1/22/13 6:12:08.000 PM kernel[0]: Wake reason: GLAN XHC EHC1 1/22/13 6:12:46.000 PM kernel[0]: The USB device HubDevice (Port 1 of Hub at 0x1d000000) may have caused a wake by issuing a remote wakeup (2) 1/22/13 6:12:46.000 PM kernel[0]: The USB device Keyboard Hub (Port 1 of Hub at 0x1d100000) may have caused a wake by issuing a remote wakeup (3) 1/22/13 6:12:46.000 PM kernel[0]: The USB device Apple Keyboard (Port 2 of Hub at 0x1d110000) may have caused a wake by issuing a remote wakeup (3) 1/22/13 6:22:38.000 PM kernel[0]: Wake reason: GLAN XHC EHC1 1/22/13 9:54:34.000 PM kernel[0]: The USB device HubDevice (Port 1 of Hub at 0x1d000000) may have caused a wake by issuing a remote wakeup (2) 1/22/13 9:54:34.000 PM kernel[0]: The USB device Keyboard Hub (Port 1 of Hub at 0x1d100000) may have caused a wake by issuing a remote wakeup (3) 1/22/13 9:54:34.000 PM kernel[0]: The USB device Apple Keyboard (Port 2 of Hub at 0x1d110000) may have caused a wake by issuing a remote wakeup (3) 1/23/13 9:18:15.320 AM com.apple.security.pboxd[225]: __block_global_2: connection failed unexpectedly; terminating process; delegate was ( 0 RemoteViewServices 0x00007fff8ea4c0a9 -[NSRemoteServiceConnection setDelegate:] + 253 1 com.apple.security.pboxd 0x00000001085b471b com.apple.security.pboxd + 22299 2 com.apple.security.pboxd 0x00000001085b4c07 com.apple.security.pboxd + 23559 3 com.apple.security.pboxd 0x00000001085b3a72 com.apple.security.pboxd + 19058 4 libxpc.dylib 0x00007fff851564a2 _xpc_connection_recv_message + 699 5 libxpc.dylib 0x00007fff8515616d _xpc_connection_wakeup_recv + 165 6 libxpc.dylib 0x00007fff851548b4 _xpc_connection_wakeup2 + 1799 7 libxpc.dylib 0x00007fff8515417c _xpc_connection_wakeup + 145 8 libdispatch.dylib 0x00007fff84f730b6 _dispatch_client_callout + 8 9 libdispatch.dylib 0x00007fff84f7529b _dispatch_source_invoke + 691 10 libdispatch.dylib 0x00007fff84f74305 _dispatch_queue_invoke + 72 11 libdispatch.dylib 0x00007fff84f74448 _dispatch_queue_drain + 180 12 libdispatch.dylib 0x00007fff84f742f1 _dispatch_queue_invoke + 52 13 libdispatch.dylib 0x00007fff84f741c3 _dispatch_worker_thread2 + 249 14 libsystem_c.dylib 0x00007fff8b255cab _pthread_wqthread + 404 15 libsystem_c.dylib 0x00007fff8b240171 start_wqthread + 13 ) 1/21/13 5:51:50.000 PM kernel[0]: Previous Sleep Cause: 5 1/21/13 5:51:50.585 PM WindowServer[104]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/21/13 5:51:50.662 PM WindowServer[104]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/21/13 5:52:45.310 PM WindowServer[104]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/21/13 5:52:45.000 PM kernel[0]: Previous Sleep Cause: 5 1/21/13 5:52:45.510 PM WindowServer[104]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/21/13 5:52:45.552 PM WindowServer[104]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/21/13 5:52:46.646 PM WindowServer[104]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/21/13 5:52:50.971 PM WindowServer[104]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/21/13 5:52:51.259 PM WindowServer[104]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/21/13 5:52:51.345 PM WindowServer[104]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/21/13 6:05:12.884 PM WindowServer[77]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/21/13 6:05:12.899 PM WindowServer[77]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/21/13 6:05:30.022 PM VLC[262]: kIOPMAssertionTypePreventUserIdleSystemSleep 1/21/13 6:05:31.262 PM VLC[262]: kIOPMAssertionTypePreventUserIdleDisplaySleep 1/21/13 7:07:01.026 PM WindowServer[75]: handle_will_sleep_auth_and_shield_windows: no lock state data 1/21/13 7:07:01.145 PM WindowServer[75]: handle_will_sleep_auth_and_shield_windows: no lock state data 1/21/13 7:07:01.189 PM WindowServer[75]: handle_will_sleep_auth_and_shield_windows: no lock state data 1/21/13 7:23:26.383 PM WindowServer[75]: handle_will_sleep_auth_and_shield_windows: no lock state data 1/22/13 6:06:46.000 PM kernel[0]: Previous Sleep Cause: 5 1/22/13 6:06:46.685 PM WindowServer[79]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/22/13 6:06:46.762 PM WindowServer[79]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/22/13 6:12:46.693 PM WindowServer[79]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/22/13 6:12:46.899 PM WindowServer[79]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/22/13 6:12:46.000 PM kernel[0]: Previous Sleep Cause: 5 1/22/13 6:12:46.933 PM WindowServer[79]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/22/13 9:54:34.000 PM kernel[0]: Previous Sleep Cause: 5 1/22/13 9:54:34.688 PM WindowServer[79]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/22/13 9:54:39.908 PM WindowServer[79]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/22/13 9:54:39.936 PM WindowServer[79]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/22/13 9:54:55.530 PM WindowServer[79]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/22/13 9:54:55.573 PM WindowServer[79]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 1/22/13 9:59:55.756 PM WindowServer[79]: handle_will_sleep_auth_and_shield_windows: no lock state data 1/23/13 9:17:46.498 AM WindowServer[101]: handle_will_sleep_auth_and_shield_windows: NULL auth_window 1/23/13 9:17:46.543 AM WindowServer[101]: handle_will_sleep_auth_and_shield_windows: NULL auth_window
- 19,329 replies
-
- acpi
- acpispecification
-
(and 4 more)
Tagged with:
-
I have a DSDT even tho i didn't need one. I need DSDTs is just for AppleHDA, HDMI audio(which it doesn't work), Orange icon fix, and that's about it. I looked over the iMac dsdt but couldn't find anything that even resembles what i had to look for. I had the XHCI EHC1 and EHC2 but on the iMac DSDT that information was absent or i couldn't see it. I attached a copy of what i had. DSDT.aml.zip
- 19,329 replies
-
- acpi
- acpispecification
-
(and 4 more)
Tagged with:
-
Hi nothing useful in the console regarding sleep or wake. About the USB how exactly do i do that? can you explain the process a bit? USB is not really imported because it works, it's just the error that's popping up, other than that it's OK. On the other hand sleep is really getting on my nerves. I honestly will remove the motherboard if it's not sleep capable, but from what i read on the net, it IS capable of sleep.
- 19,329 replies
-
- acpi
- acpispecification
-
(and 4 more)
Tagged with:
-
Hello everyone, I'm writing because I'm out of ideas. I own an ASRock Z68 Pro3 Motherboard with a Nvidia GTX 560 non-Ti. Ever since i started to install mac on my PC i alway had the problem of not achieving the perfect sleep cycle. It works only on iMac 11.3 till iMac 12.2 only once. It goes to sleep fine it wakes up, but if i put it to sleep again it sleeps but on wake only fans are working. I tried using other SMBios definitions but it didnt sleep at all. After 10.7.3 A USB Error started to appear saying the hub was drawing too much power and has been disabled. Could it be the USB3? The Install is almost vanilla, gfx are standard nvidia drivers and cuda, lnx2mac lan kext, latest fakeSMC and audio from toleda. What do you think the problem might be? I added the Send me.zip below, should i add the DSDT i use? Send me .zip
- 19,329 replies
-
- acpi
- acpispecification
-
(and 4 more)
Tagged with:
