E6530: Problem with keyboard and trackpad after wake up with powerbutton

[Millerdry]

Hi guys,

 

first sorry that my english is not the best and thank you for this forum.

 

I did my first hackintosh on a Dell Latitude E6530 with following Jakes  guide an all is working fine.

Thanks for your guide Jake its very easy to get mavericks 10.9.5 runnig fine on my Dell.

 

The only problem what i get is to wake up the system withe the power button, after waking i can not use keyboard and trackpad is there any idea to fix it ?

 

System is:

 

E6530

 

Bios A13

 

I7 3520m with HD4000

 

Nvidia NVS 5200m

 

16GB DDR

 

Thanks for your help

 

 

Greetings Miller

[Bronxteck]

you might have to patch HPET in your DSDT. open your dsdt in an dsdt editor and check to see if your HPET section looks like this

Device (HPET)
{
Name (_HID, EisaId ("PNP0103"))
Name (BUF0, ResourceTemplate ()
{
IRQNoFlags ()
{0}
IRQNoFlags ()
{8}
IRQNoFlags ()
{11}
IRQNoFlags ()
{15}
Memory32Fixed (ReadOnly,
0xFED00000, // Address Base
0x00000400, // Address Length
_Y10)
})

if you only see

IRQNoFlags ()
{0}
IRQNoFlags ()
{8}

add this behind it

IRQNoFlags ()
{11}
IRQNoFlags ()
{15}

recompile the DSDT save it as .aml and test it hopefully that resolves your issue.

another test would be to backup then remove System/Library/Extensions/AppleHPET.kext then rebuild your catches. you can try that before the DSDT edits to see if it really is HPET conflicting and stealing your IRQ values. if it works fine after that then replace the kext and test the DSDT edits for a permanent solution.

the problem with HPET can manifests itself as non working devices after sleep, can be USB ports, DVDROM, Wlan, Trackpad basically anything the gets designated an IRQ value.

[Millerdry]

Hi Bronx,

 

first thank you for your answer.

 

If had tried to delete the AppleHPET.kext and rebuild my chaches with myhack myfix.

 

After that i got the Problem, that the system go to freez after a few seconds.

 

So without this.kext i have more Problems like bevor.

 

Should i try it still with the dsdt method or does it make no sense after the problem without the kext.

 

Any other ideas?

 

Thanks and greetings

Miller

[Bronxteck]

well it just means your hardware depends on the kext. so the dsdt edits allow it to function but tell it what IRQ values to use instead of hogging all free or not free IRQ's.

[Millerdry]

Hi Bronx,

 

Okay now i have opened my dsdt with dsdt editor.

 

And the next problem, i have no HPET device in my dsdt.

 

Can i add this device manual with your entrys or does my Motherboard not Support it.

 

Thanks Miller

[Bronxteck]

hmm i wonder if it has it as a separate SSDT.aml instead; try searching for "PNP0103" in dsdt incase it is named something different.

if your willing to try you can try injecting the whole device into dsdt

[Jake Lo]

@Millerdry,

 

Which guide and bootpack did you use? 

The one with Optimus enabled or disabled?

[Bronxteck]

jake can you take a look to see if HPET is in a separate SSDT.aml or see if you can inject the snippet above. i know clover has an option to do it for you.

[Jake Lo]

This is in both DSDT.aml for Optimus enabled and disabled. I don't recall losing trackpad or keyboard after sleep for Optimus enabled (HD4000) though. Sleep doesn't work for Optimus disabled (Nvs5200m).

 

I'm not sure where he gotten his DSDT if it doesn't have HPET.

                Device (HPET)
                {
                    Name (_HID, EisaId ("PNP0103"))  // _HID: Hardware ID
                    Name (_UID, Zero)  // _UID: Unique ID
                    Name (BUF0, ResourceTemplate ()
                    {
                        IRQNoFlags ()
                            {0}
                        IRQNoFlags (_Y10)
                            {8}
                        Memory32Fixed (ReadWrite,
                            0xFED00000,         // Address Base
                            0x00000400,         // Address Length
                            )
                    })

[Millerdry]

Good morning,

 

i have found the device it was my fault i looked on the left side of the editor for this.

 

Now i had add this other irqs but it is the same.

 

When i go to normal sleep i can wake up the system with the spacebar an all is okay.

 

Only i dont know whats the right name for it this sleep when i must wake up the system with the powerbutton, then i loose mouse and trackpad.

 

@jake i start with the guide without optimus, then i did the update up to 10.9.5 over the appstore.

 

After that i install the new bootpack for optimus an enable optimus in the bios.

 

Greetings Miller