Use mine, no KP.
https://dl.dropbox.c...dooHDA.kext.zip
EDIT: Can you also change the thread name to include your Laptop model?
This way other people can find it easily and use the files.
33 replies to this topic
#21
Posted 01 September 2012 - 07:48 PM
#22
Posted 01 September 2012 - 10:05 PM
#23
Posted 03 September 2012 - 11:06 AM
Now I am using the dsdt but need to put in a patch for the nvidia so how would go about doing that ?
#24
Posted 03 September 2012 - 11:36 AM
The dsdt i gave you has included a graphic patch, it does not work with your lappy?
If it doesn´t just add to org.chameleon.boot.plist the flag: GraphicsEnabler=Yes
If it doesn´t just add to org.chameleon.boot.plist the flag: GraphicsEnabler=Yes
#25
Posted 03 September 2012 - 11:41 AM
pere, on 03 September 2012 - 11:36 AM, said:
The dsdt i gave you has included a graphic patch, it does not work with your lappy?
The gt525m works perfectly with your dsdt , but on the osx86 .es the patch talks about changing brightness control , now in windows and linux it works with "Fn + f6 or f7" plus in your DSDT in the it is "0x3A" and on the os86.es patch it is 0x38. And if i make changes in your DSDT and try to compile using DSDTSE it gives an error.
Also have a problem with sleep / stndby mode, I need to power off remove and reconnect the battery and start.
#26
Posted 03 September 2012 - 01:08 PM
On Osx, the keys controlling the brightness are FN+INS and FN+PGDOWN, you need a keymapper to setup them on their original place.
Cause the one on the page doesn´t have this:
"hda-gfx",
Buffer (0x0A)
{
"onboard-1"
}
This is why this value is different, if you want to change something, just erase the value down in red and compile. Anyway, use the patch included in my DSDT, is more complete.
Method (_DSM, 4, NotSerialized)
{
Store (Package (0x38)
You should go to preferences>Displays and find there a brightness slider.
eurofightertyhpoon, on 03 September 2012 - 11:41 AM, said:
....plus in your DSDT in the it is "0x3A" and on the os86.es patch it is 0x38. And if i make changes in your DSDT and try to compile using DSDTSE it gives an error.
Cause the one on the page doesn´t have this:
"hda-gfx",
Buffer (0x0A)
{
"onboard-1"
}
This is why this value is different, if you want to change something, just erase the value down in red and compile. Anyway, use the patch included in my DSDT, is more complete.
Method (_DSM, 4, NotSerialized)
{
Store (Package (0x38)
You should go to preferences>Displays and find there a brightness slider.
#27
Posted 03 September 2012 - 02:14 PM
#28
Posted 03 September 2012 - 06:22 PM
Thnx Pere , I reinstalled ML and used your DSDT and SSDT and it picked up the wifi
#29
Posted 03 September 2012 - 06:34 PM
Open your own SSDT files, locate this:
Replace this code inside my SSDT with your data, compile the SSDT and place it into extra folder (Be sure is named SSDT.aml).
Name (SPSS, Package (0x11)
{
Package (0x06)
{
0x08FD,
0x88B8,
0x0A,
0x0A,
0x1D00,
0x1D00
},
Package (0x06)
{
0x08FC,
0x88B8,
0x0A,
0x0A,
0x1700,
0x1700
},
Package (0x06)
{
0x0898,
0x8068,
0x0A,
0x0A,
0x1600,
0x1600
},
Package (0x06)
{
0x0834,
0x7997,
0x0A,
0x0A,
0x1500,
0x1500
},
Package (0x06)
{
0x07D0,
0x7197,
0x0A,
0x0A,
0x1400,
0x1400
},
Package (0x06)
{
0x076C,
0x6B0E,
0x0A,
0x0A,
0x1300,
0x1300
},
Package (0x06)
{
0x0708,
0x64A6,
0x0A,
0x0A,
0x1200,
0x1200
},
Package (0x06)
{
0x06A4,
0x5D1D,
0x0A,
0x0A,
0x1100,
0x1100
},
Package (0x06)
{
0x0640,
0x56F9,
0x0A,
0x0A,
0x1000,
0x1000
},
Package (0x06)
{
0x05DC,
0x50F6,
0x0A,
0x0A,
0x0F00,
0x0F00
},
Package (0x06)
{
0x0578,
0x49D8,
0x0A,
0x0A,
0x0E00,
0x0E00
},
Package (0x06)
{
0x0514,
0x4418,
0x0A,
0x0A,
0x0D00,
0x0D00
},
Package (0x06)
{
0x04B0,
0x3E7C,
0x0A,
0x0A,
0x0C00,
0x0C00
},
Package (0x06)
{
0x044C,
0x37CA,
0x0A,
0x0A,
0x0B00,
0x0B00
},
Package (0x06)
{
0x03E8,
0x326B,
0x0A,
0x0A,
0x0A00,
0x0A00
},
Package (0x06)
{
0x0384,
0x2D2B,
0x0A,
0x0A,
0x0900,
0x0900
},
Package (0x06)
{
0x0320,
0x26E4,
0x0A,
0x0A,
0x0800,
0x0800
}
})
Name (_PSS, Package (0x16)
{
Package (0x06)
{
0x0B54,
0x88B8,
0x0A,
0x0A,
0x1D00,
0x1D00
},
Package (0x06)
{
0x0AF0,
0x88B8,
0x0A,
0x0A,
0x1C00,
0x1C00
},
Package (0x06)
{
0x0A8C,
0x88B8,
0x0A,
0x0A,
0x1B00,
0x1B00
},
Package (0x06)
{
0x0A28,
0x88B8,
0x0A,
0x0A,
0x1A00,
0x1A00
},
Package (0x06)
{
0x09C4,
0x88B8,
0x0A,
0x0A,
0x1900,
0x1900
},
Package (0x06)
{
0x0960,
0x88B8,
0x0A,
0x0A,
0x1800,
0x1800
},
Package (0x06)
{
0x08FC,
0x88B8,
0x0A,
0x0A,
0x1700,
0x1700
},
Package (0x06)
{
0x0898,
0x8068,
0x0A,
0x0A,
0x1600,
0x1600
},
Package (0x06)
{
0x0834,
0x7997,
0x0A,
0x0A,
0x1500,
0x1500
},
Package (0x06)
{
0x07D0,
0x7197,
0x0A,
0x0A,
0x1400,
0x1400
},
Package (0x06)
{
0x076C,
0x6B0E,
0x0A,
0x0A,
0x1300,
0x1300
},
Package (0x06)
{
0x0708,
0x64A6,
0x0A,
0x0A,
0x1200,
0x1200
},
Package (0x06)
{
0x06A4,
0x5D1D,
0x0A,
0x0A,
0x1100,
0x1100
},
Package (0x06)
{
0x0640,
0x56F9,
0x0A,
0x0A,
0x1000,
0x1000
},
Package (0x06)
{
0x05DC,
0x50F6,
0x0A,
0x0A,
0x0F00,
0x0F00
},
Package (0x06)
{
0x0578,
0x49D8,
0x0A,
0x0A,
0x0E00,
0x0E00
},
Package (0x06)
{
0x0514,
0x4418,
0x0A,
0x0A,
0x0D00,
0x0D00
},
Package (0x06)
{
0x04B0,
0x3E7C,
0x0A,
0x0A,
0x0C00,
0x0C00
},
Package (0x06)
{
0x044C,
0x37CA,
0x0A,
0x0A,
0x0B00,
0x0B00
},
Package (0x06)
{
0x03E8,
0x326B,
0x0A,
0x0A,
0x0A00,
0x0A00
},
Package (0x06)
{
0x0384,
0x2D2B,
0x0A,
0x0A,
0x0900,
0x0900
},
Package (0x06)
{
0x0320,
0x26E4,
0x0A,
0x0A,
0x0800,
0x0800
}
})
Replace this code inside my SSDT with your data, compile the SSDT and place it into extra folder (Be sure is named SSDT.aml).
#30
Posted 03 September 2012 - 06:45 PM
pere, on 03 September 2012 - 06:34 PM, said:
Open your own SSDT files, locate this:
Replace this code inside my SSDT with your data, compile the SSDT and place it into extra folder (Be sure is named SSDT.aml).
Replace this code inside my SSDT with your data, compile the SSDT and place it into extra folder (Be sure is named SSDT.aml).
What is it for exactly ? and "your data" due you mean the one from osx86.es ? your voodoohda gave a kp after a reinstall.
Can you help with what I can do about the sleep / stnd by problem ?
#31
Posted 03 September 2012 - 07:18 PM
SSDT is the processor´s speed (and other stuff) control.
Using mine you are slowering your processor as mine is one step under yours.
That´s why i recommend you:
Get and open your own SSDT files (There are hundreds of tutorias here and there about "how to").
Lotate the piece of code i have `paste before, copy it.
Open my SSDT file, replace that code with yours.
Compile.
Use it.
Using mine you are slowering your processor as mine is one step under yours.
That´s why i recommend you:
Get and open your own SSDT files (There are hundreds of tutorias here and there about "how to").
Lotate the piece of code i have `paste before, copy it.
Open my SSDT file, replace that code with yours.
Compile.
Use it.
#32
Posted 03 September 2012 - 07:27 PM
Pere,
I remove the code pasted by you from the SSDT (which gave me) and paste the one from my own SSDT am I right. But I don't my SSDT as I don't know how to extract one.
I remove the code pasted by you from the SSDT (which gave me) and paste the one from my own SSDT am I right. But I don't my SSDT as I don't know how to extract one.
#33
Posted 03 September 2012 - 07:47 PM
Please, you have a lot of tutorials here explaining hot to extract your acpi files, just take a look on this DSDT subforum or go to osx86.es, there is a post also on how to do it.
#34
Posted 04 September 2012 - 04:35 AM
Pere,
I will look into the tutorials for DSDT & SSDT, thnx.
I will look into the tutorials for DSDT & SSDT, thnx.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users



Sign In
Create Account









