DSDT patch requests

[chewymix]

Hi - i added this DSDT but in doing so my sound went away. I stopped looking at the sleep/HDMI issue due to this so could you help me in the sound problem before i can move on? I removed the DSDT and the sound came back again.

many thanks

[artur-pt]

hello

what u are using for have sound ?

the dsdt have hdef section

layout id 12 for applehda

without hdef section

 

DSDT.aml.zip

 

good hack

[chewymix]

Hi

For this test i was using the onboard ALC269 and this is the one that disappeared. Is there any chance that its possible to have both output devices available ?

thankyou!

[artur-pt]

hello

man read about ....

is not that i ask u...

http://Olarila.com/forum/viewtopic.php?f=9&t=1933

or

http://Olarila.com/forum/viewtopic.php?f=18&t=454

good hack

[piyushseem]

hi mod,

I need a patch for my mobo: Asus P5SD2-VM

Thanks with best regards,

Piyushseem.

[wellstone]

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

[xsmile]

Does the console say anything useful related to Sleep?

Regarding USB, you could adding current settings to EHC1, EHC2, XHC1 as in:

http://tdev.me/2010/12/apple-hardware-dumps/#iMac13,1 's original DSDT.

They are in the _DSM methods.

[SRSR333]

Hey guys...

I have a Samsung RF411, and I have patched the DSDT using the motherboard-specific patch in the database here. However, I have no sound without HDAEnabler or VoodooHDA. Could I have a patch.txt file that patches my DSDT for my audio codec, ALC 269? I would also like the HDMI audio patch. Thanks...

NOTE: Attached are my unedited DSDT and codec dump from Linux, if necessary. They are all in the Send me.zip file.

Send me.zip

[artur-pt]

hello

see here

http://Olarila.com/forum/viewtopic.php?f=9&t=1933

good hack

[chewymix]

hello

man read about ....

is not that i ask u...

http://Olarila.com/forum/viewtopic.php?f=9&t=1933

or

http://Olarila.com/forum/viewtopic.php?f=18&t=454

good hack

 

thanks - i will read

If i go down the route to get both sound working which DSDT from you should i use, the first or the second you posted?

thanks

[SRSR333]

Thanks for info! Really appreciate it!

[wellstone]

Does the console say anything useful related to Sleep?

Regarding USB, you could adding current settings to EHC1, EHC2, XHC1 as in:

http://tdev.me/2010/12/apple-hardware-dumps/#iMac13,1 's original DSDT.

They are in the _DSM methods.

 

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.

[xsmile]

Oops, I thought you patched your DSDT already.

There are patch sets available at http://Olarila.com/forum/packs.php. Your board is listed there. Use DSDT Editor to apply the patch file: http://Olarila.com/forum/viewtopic.php?f=19&t=62. Most erros should be resolved with the new DSDT.

Take a look at the bottom of it, these are the current settings I was talking about.

Good hack, as the guys here use to say.

[wellstone]

Oops, I thought you patched your DSDT already.

There are patch sets available at http://Olarila.com/forum/packs.php. Your board is listed there. Use DSDT Editor to apply the patch file: http://Olarila.com/forum/viewtopic.php?f=19&t=62. Most erros should be resolved with the new DSDT.

Take a look at the bottom of it, these are the current settings I was talking about.

Good hack, as the guys here use to say.

 

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

[wellstone]

Oops, I thought you patched your DSDT already.

There are patch sets available at http://Olarila.com/forum/packs.php. Your board is listed there. Use DSDT Editor to apply the patch file: http://Olarila.com/forum/viewtopic.php?f=19&t=62. Most erros should be resolved with the new DSDT.

Take a look at the bottom of it, these are the current settings I was talking about.

Good hack, as the guys here use to say.

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

[xsmile]

The log looks normal I would say, I got the same sequence.

It seems you have tried quite a few things already, I saw your posts on another forum.

Please test this DSDT. I changed:

- Added current settings to device XHC

- IRQNoFlags moved from RTC, TIMR to HPET; HPET new _CID

- Disabled OS recognition, set OSYS to 07D2 (Windows 2001 SP2)

- Cleaned up OSYS checks

According to this thread the DSDT contains a buggy "SIOW" method.

If it still doesn't work with this DSDT, try replacing the SIOW method with one from my board's DSDT, an Asus P8Z77-V LK:

                Method (SIOW, 1, NotSerialized)
               {
                   Store ("SIOW", Debug)
                   ^SIO1.ENFG (0x0A)
                   Store (^SIO1.OPT3, PMFG)
                   Store (0xFF, ^SIO1.OPT3)
                   And (^SIO1.OPT6, 0xCF, ^SIO1.OPT6)
                   And (0xFE, ^SIO1.OPT2, ^SIO1.OPT2)
                   ^SIO1.EXFG ()
               }

 

Also, you should avoid the use of any Sleep enabler and power management kexts as you seem to have a patched BIOS already.

Do you have any messages like this in console?:

"Unsynchronized TSC"

Are the C- and P-States reported correctly in IOReg? Example:

PS:

The iMac 13,1 USB devices are external in one of the SSDT files; look for EHC1, EHC2, XHCI.

DSDT.aml.zip

[wellstone]

Also, you should avoid the use of any Sleep enabler and power management kexts as you seem to have a patched BIOS already.

Do you have any messages like this in console?:

"Unsynchronized TSC"

Are the C- and P-States reported correctly in IOReg? Example:

PS:

The iMac 13,1 USB devices are external in one of the SSDT files; look for EHC1, EHC2, XHCI.

 

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

[xsmile]

Right, forgot to modify the XHC device.

It seems the PStates are handled differently with Sandy Bridge (I got Ivy). I found them under PerformanceStateArray in ACPI_SMC_PlatformPlugin.

Do you generate them with Chameleon?

Can you share all of your SSDT tables? You can get them with AIDA64's ACPI tool for example.

Try these two versions.

I merged some things from Pro3 Gen3 BIOS v2.30 DSDT that might help.

One more thing, did you set up your BIOS to manual settings and disabled things like PLL overvoltage? Just want to be sure.

DSDTs.zip

[wellstone]

Right, forgot to modify the XHC device.

It seems the PStates are handled differently with Sandy Bridge (I got Ivy). I found them under PerformanceStateArray in ACPI_SMC_PlatformPlugin.

Do you generate them with Chameleon?

Can you share all of your SSDT tables? You can get them with AIDA64's ACPI tool for example.

Try these two versions.

I merged some things from Pro3 Gen3 BIOS v2.30 DSDT that might help.

One more thing, did you set up your BIOS to manual settings and disabled things like PLL overvoltage? Just want to be sure.

 

here are the ssdts, i will try what you have gave me now and see a result.

BIOS is on manual.

ssdts.zip

[wellstone]

here are the ssdts, i will try what you have gave me now and see a result.

BIOS is on manual.

 

Nothing changed, same sleep cycle, wakes only once.