Jump to content

Asus P5E DSDT fixes

oldnapalm

By oldnapalm,
in Patches

 Share
300 posts in this topic

Recommended Posts

oldnapalm
oldnapalm
Posted
  • Author
Posted
Only other minor issue is not being able to do timed sleep (in Energy Saver) but I know this is a common issue with different hardware. Could this be fixed by DSDT?

If it can be fixed by DSDT I don't know how.

 

You can use one of these programs

 

http://www.insanelymac.com/forum/index.php?showtopic=182535

 

or

 

http://www.dragonone.com/products/macosx/pleasesleep/

Link to comment
Share on other sites
atomiX_X
atomiX_X
Posted
Posted

Thanks for the tip, works great!

 

On a related note, turns out the issue with USB mouse/keyboard not being powered up after sleep is caused by the 10.6.3 IOUSBHIDDriver.kext. A modified 10.6.2 kext is available here.

 

edit: Wasn't able to test this for myself until last night. I wasn't able to make this fix work on the P5E, I also tried replacing with vanilla 10.6.2 IOUSBHIDDriver.kext with no success :(. I'm back at 10.6.2 for now.

Link to comment
Share on other sites
  • 3 weeks later...
KeFfBoY
KeFfBoY
Posted
Posted

I did patch my DSDT with all the fixes now, I think. Here is the file I've ended up with:

 

( I didn't do the audio nor network part because I already found a kext which did fix network, and I use another audiocard )

 

Seems like the computer wants to boot ok, and sleep works.

dsdt.aml.zip

Link to comment
Share on other sites
oldnapalm
oldnapalm
Posted
  • Author
Posted
Thanks for the tip, works great!

 

On a related note, turns out the issue with USB mouse/keyboard not being powered up after sleep is caused by the 10.6.3 IOUSBHIDDriver.kext. A modified 10.6.2 kext is available here.

 

edit: Wasn't able to test this for myself until last night. I wasn't able to make this fix work on the P5E, I also tried replacing with vanilla 10.6.2 IOUSBHIDDriver.kext with no success ;). I'm back at 10.6.2 for now.

Looks like the problem is fixed in latest 10.6.4 beta

http://www.projectosx.com/forum/index.php?...post&p=7095

 

I did patch my DSDT with all the fixes now, I think. Here is the file I've ended up with:

 

( I didn't do the audio nor network part because I already found a kext which did fix network, and I use another audiocard )

 

Seems like the computer wants to boot ok, and sleep works.

Please try with the attached file

dsdt.aml.zip

Link to comment
Share on other sites
KeFfBoY
KeFfBoY
Posted
Posted
Looks like the problem is fixed in latest 10.6.4 beta

http://www.projectosx.com/forum/index.php?...post&p=7095

 

 

Please try with the attached file

dsdt.aml.zip

 

Can I assume that Speedstep works ok when running VoodooMonitor and noticing that if I look in the tab "status" I can see that all 4 cores seem to jump between 1600 MHz and 2400 MHz (2400 MHz is the default)?? It stays at 1600 when I don't do much, and when I boot up a movie or something it jumps to 2400.

 

Also, I think that I managed to get my DSDT to work finally. The icon on my harddrive is fine now, and I don't use the AHCI kext anymore.

 

Both sleep and restarts works!

 

(Although the mouse stops working after sleep.. I have to reconnect it to get it working again)

Link to comment
Share on other sites
oldnapalm
oldnapalm
Posted
  • Author
Posted
Can I assume that Speedstep works ok when running VoodooMonitor and noticing that if I look in the tab "status" I can see that all 4 cores seem to jump between 1600 MHz and 2400 MHz (2400 MHz is the default)?? It stays at 1600 when I don't do much, and when I boot up a movie or something it jumps to 2400.

Yes, that's right.

 

(Although the mouse stops working after sleep.. I have to reconnect it to get it working again)

That's because of the issue atomiX_X was talking about in previous posts.

Link to comment
Share on other sites
KeFfBoY
KeFfBoY
Posted
Posted
You are welcome. Please try the dsdt.aml I modified for you, maybe it fixes the performance issues (PIC and TMR IRQs removed).

 

Tried it but didn't really resolve the issue. I will do some more testing tomorrow probably, and I start to think maybe it's not a performance issue, but an issue with the physicsengine that is used in the app I run.. I will get back with more info when I've tested this out more.

 

Time for bed now. Thanks for all the help!

 

Ciao!

Link to comment
Share on other sites
atomiX_X
atomiX_X
Posted
Posted
Fixing sleep and usb after wake up

 

 

http://osx86.net/f84/various-dsdt-mods-t1960/page3.html

 

Thanks for the post. This does solve the issue but introduces another, i can no longer wake from sleep using my USB keyboard/mouse. This might not be critical for everyone but it is for me.

 

For those interested, search for Method (GPRW, 2, NotSerialized) and replace Return (PRWP) a few lines below with:

Return (Package (0x02)
         {
             Zero, 
             Zero
         })

 

I would appreciate it if someone had an edit that could fix my wake-from-usb though. I might just wait until 10.6.4 comes out.

Link to comment
Share on other sites
tChibo
tChibo
Posted
Posted
Thanks for the post. This does solve the issue but introduces another, i can no longer wake from sleep using my USB keyboard/mouse. This might not be critical for everyone but it is for me.

 

For those interested, search for Method (GPRW, 2, NotSerialized) and replace Return (PRWP) a few lines below with:

Return (Package (0x02)
         {
             Zero, 
             Zero
         })

 

I would appreciate it if someone had an edit that could fix my wake-from-usb though. I might just wait until 10.6.4 comes out.

 

 

Do you add new SLEEP button to the dsdt in _gpe scope?

 

Device (SLPB)

{

Name (_HID, EisaId ("PNP0C0E"))

Method (_PRW, 0, NotSerialized)

{

Return (Package (0x02)

{

0x0B,

0x04

})

}

}

Link to comment
Share on other sites
atomiX_X
atomiX_X
Posted
Posted
Do you add new SLEEP button to the dsdt in _gpe scope?

 

I'm pretty sure I did at one point or another. As well as changing the \_SB.PWRB, 0x02 strings under the _L0X methods to \_SB.SLPB, 0x02. I've tried a few different variations of fixes but I'll try again anyway...worth a shot.

 

EDIT: Nope, no go. Adding the SLPB device by itself did nothing (normal since it isn't referenced anywhere else in the DSDT) and also while changing the "\_SB.PWRB, 0x02" strings to "\_SB.SLPB, 0x02" as I did previously but that didn't work either.

Link to comment
Share on other sites
  • 2 weeks later...
Guest segundojazz
Guest segundojazz
Posted
Posted

Hello everyone.

Please, all I have P5E ok with 4GB ram, but with 6GB ram hangs after a while.

Help please, my English is very bad. Thanks

Link to comment
Share on other sites
Guest segundojazz
Guest segundojazz
Posted
Posted
Are you using a modified dsdt.aml? If so, maybe you need to update the file when adding or removing memory.

 

What's your main language?

 

 

Thanks for answers

I speak Spanish.

Yes, I am using you DSDT.aml with BootThink_2.3.18 but not edit it.

Also use this:

AD1988b.Fix

fakesmc

LegacyAppleYukon2

64 NVEnabler

OpenHaltRestart

OSXRestart

PlatformUUID

 

Everything is perfect with 4Gb Ram, 6 Gb ram when I freeze the passage of time

 

I do not understand is this:

((If You Have Different RAM size you OperationRegion May Have to edit values for RAMW, BIOS and STBL, check your original DSDT. Thanks to Stuntman for the info.))

Link to comment
Share on other sites
oldnapalm
oldnapalm
Posted
  • Author
Posted

You can add the RAM and boot without the dsdt.aml file, then you extract the original DSDT using DSDT_Patcher and search for OperationRegion. Probably it will have different values than mine, then you edit my file and replace those values.

 

If you prefer writing in spanish, there's this topic in the portuguese forum

http://www.insanelymac.com/forum/index.php?showtopic=209636

Link to comment
Share on other sites
Guest segundojazz
Guest segundojazz
Posted
Posted
I attached diff file.

 

I changed information about RAM in your file to have 4 GB of ram. It's located in the OperationRegion (RAMW, SystemMemory, *How much memory you have*)

Also i need to change OperationRegion for BIOS, CPU(1,2,3,4).

You will see this in diff file :D

 

 

Hi Stuntman, I change this?, Please explain.

I have 4gb of ram but when I 6GB ram a while until it freezes and damages the OS.

I do not edit the DSDT with my 6 gb ram.

I have to do with the diff?

Thank you very much for your time :rolleyes:

Link to comment
Share on other sites
oldnapalm
oldnapalm
Posted
  • Author
Posted

segundojazz,

 

1) remove my dsdt.aml

2) add RAM and boot without the dsdt.aml, it should boot (without fixes)

3) extract your dsdt.aml using DSDT_Patcher

4) attach your dsdt.aml and I will patch it, or patch it yourself

Link to comment
Share on other sites
Guest segundojazz
Guest segundojazz
Posted
Posted
segundojazz,

 

1) remove my dsdt.aml

2) add RAM and boot without the dsdt.aml, it should boot (without fixes)

3) extract your dsdt.aml using DSDT_Patcher

4) attach your dsdt.aml and I will patch it, or patch it yourself

 

 

 

This is myDSDT.zip with 6 GB Ram.

Thanks in advance

Link to comment
Share on other sites
Guest segundojazz
Guest segundojazz
Posted
Posted

I already did, now I'm trying, I'll tell you that this is going.

Many many many thanks

 

 

Edit:

All ok ¡¡¡¡¡¡ muchas Gracias !!!!!!

Link to comment
Share on other sites
  • 3 weeks later...
oldnapalm
oldnapalm
Posted
  • Author
Posted

Applied patches look ok.

 

About SpeedStep, you don't need to add the _PSS. Just adding _CST as in the first post you will have 2 working P-states (0 and 3).

 

If you want to add the 4 states, do as explained in this topic

http://www.insanelymac.com/forum/index.php?showtopic=181631

 

Your _PSS according to the screenshot would be

        Method (_PSS, 0, NotSerialized)
       {
           Return (Package (0x04)
           {
               Package (0x06)
               {
                   Zero, 
                   Zero, 
                   0x10, 
                   0x10, 
                   0x0920, 
                   Zero
               }, 

               Package (0x06)
               {
                   Zero, 
                   Zero, 
                   0x10, 
                   0x10, 
                   0x081D, 
                   One
               }, 

               Package (0x06)
               {
                   Zero, 
                   Zero, 
                   0x10, 
                   0x10, 
                   0x0719, 
                   0x02
               }, 

               Package (0x06)
               {
                   Zero, 
                   Zero, 
                   0x10, 
                   0x10, 
                   0x0615, 
                   0x03
               }
           })
       }

 

You can patch method _PTS to fix shutdown.

 

For device SATA, I use ID 2681, but I guess 3A22 will work also.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...