UPDATE: Guys it looks like final 10.5.6 AppleRTC.kext doesnt panic without DSDT patch, so you probably wont need it. It paniced on new macbook and some beta 10.5.6 update though.



Also look up this thread: Chameleon with DSDT override function

@All complaining about hotter CPU's with AppleIntelCPUPowerManagement: Guys there is no need to have this kext loaded all the time, if you get hotter CPU, just remove that kext and everything is ok. Why I added this to patcher is just for security reasons on update, since i still see many people without an Disabler.kext and they just blindly update and then complain about a kernel panic during the update process. So this is just to be more secure on updating.

Update:

Version 1.0.1e
-added OSI emulation by mackerintel
-added Mute fix by mackerintel
thx for this
Click to view attachment

Most things needed to be fixed for Darwin the patcher fixes now. There may be still issues in your DSDT but since one DSDT looks very different than another this is needed to be done manually. So i think its time to release the source (yeah i know the code looks ugly but it does its job)
Click to view attachment

---------------
VAIO Users: pls try this patcher, i saw some Variable issues in LCD Device of VAIO DSDT, the patcher fixes this issues, maybe that will solve Internal LCD Diplay issue with QE/CI enabled. Maybe also more work is needed but actually i think we can solve your Problems in DSDT. Somebody correct me if i'm wrong. So please come here and test, thank you. I also invite more people to mess around with DSDT and come here with their findings

Update: I made some different DSDT's but haven't yet found how to get QE/CI working on the internal display, seems more things needs to be done... Look up this thread by vaag, he got it working on his DELL, maybe you can find solution. http://forum.insanelymac.com/index.php?sho...=135184&hl=
---------------


Also, if the compiling goes wrong, it doesnt always mean the patching went wrong, some manufactorers just ship crappy DSDT's in the BIOS. You can force to compile it even if there are errors: /PATH/TO/DSDT\ Pachter -f

-------Original Post-----------

Hey there, i thought it might be better to start a new Thread for this. As you may already heard you will have Problems with the upcoming (10.5.6) Apple Update if your DSDT is messed up, and it is for sure .

Good thing is, mackerintel added DSDT override function to Chameleon: http://forum.insanelymac.com/index.php?showtopic=132757

What does that mean? Well you can put a modified compiled DSDT in the Root of your Booting partition, and it will try to attach this, very good for people who are afraid of flashing their BIOS.

I made a little Tool that will patch your DSDT and will (well should) let you allow to use the upcoming (10.5.6) AppleRTC.kext and AppleIntelCPUPowerManagement.kext (no disabler needed anymore) which will otherwise panic.


Pls report back if it works or not, and what is working and what not, so this tool can grow.
Readme is included in the Zip file.

greetz

P.S. I will release the source when its done
And i like to thank all Chameleon/OSX Developers, especially zef, kabyl, modbin for helping all the time, keep up the good work!



---------Old Versions-----------
Version 1.0.1d
-fixed another search Routine issue
-added -newHPET arg, for people still suffering "Package 0 didn't get a HPET" after patching. so you guys drag the Patcher in the Terminal and write -newHPET
-Patcher uses now a bash script for obtaining the DSDT since GetDSDT didn't worked for some people.
-contains _T_ Variable issues fix which caused non-compiling by mackerintel
-contains "Method local variable is not initialized (Local0)" fix
-contains CPU Aliases fix
-contains RTC fix for upcoming AppleRTC.kext
-contains HPET fix for AppleIntelCPUPowerManagement.kext
Click to view attachment

Version 1.0.1c2
-Patcher uses now a bash script for obtaining the DSDT since GetDSDT didn't worked for some people.
-fixed CPU Aliases patching (all what pointed to the removed Alias has to be patched as well)
-added _T_ Variable issues fix which caused non-compiling by mackerintel
-contains "Method local variable is not initialized (Local0)" fix
-contains CPU Aliases fix
-contains RTC fix for upcoming AppleRTC.kext
-contains HPET fix for AppleIntelCPUPowerManagement.kext
Click to view attachment Fixed DSDT.X issue
Click to view attachment

Version 1.0.1b
-fixed a patching routine issue which caused non-compiling dsdt
-added "Method local variable is not initialized (Local0)" fix
-contains CPU Aliases fix
-contains RTC fix for upcoming AppleRTC.kext
-contains HPET fix for AppleIntelCPUPowerManagement.kext
Click to view attachment

Version 1.0.1a
-fixed CPU Aliases fix
-contains RTC fix for upcoming AppleRTC.kext
-contains HPET fix for AppleIntelCPUPowerManagement.kext
Click to view attachment

Version 1.0.1
-added CPU Aliases fix
-added some device name fix
-contains RTC fix for upcoming AppleRTC.kext
-conatins HPET fix for AppleIntelCPUPowerManagement.kext
Click to view attachment

can u explain why i should try it?
i have no problems so far
but i can't stop trying new stuff

can't understand this thing with DSDT

Yeah so far... but in 10.5.6 there will be a new AppleRTC.kext which will panic if you haven't your RTC Device patched in your DSDT. Other than the AppleIntelCPUPowerManagement.kext you cant just delete it. So better to fix your DSDT now, than having Problems later

greetz

ok i got it
i'll try and post results

You can use AppleRTC.kext from 10.5.5 but DSDT is the right way. Even my AZAL sound device I´ve managed to change it to HDEF with it.
So, I´m glad for the work of the Chameleon, DSDT guys as well as DSDT Patcher

thanks

I'm trying to understand a bit more on DSDT , reading around on this very forum but..

What will change in future on ours osx86 with dsdt patcher possibility ?

I mean , we can update 10.5.6 , and will be improvements in other areas , like ACPI for example ?

DSDT is a part of ACPI. Actually DSDT tells OS how to interract with the hardware (simplified way of telling it). OSX has an incomplete ACPI implementation which supports only a subset of DSDT. By replacing DSDT we can declare essentially the same interface but in the way that OSX understands. This potentially can solve nearly any ACPI-related problem (except if OSX bypasses ACPI). Other usage case is emulating by the means of DSDT features or hardware components not present on your system. But this is limited to devices that use ACPI.

@all: does anybody know if binary protection uses ACPI? If so implementing binary protection emulator in DSDT would be a way to have a completely untouched OSX.

Thanks Indeed for ur awesome job mackerintel,
In the meantime I understood how this "small" change , will make big improvement on osx86 , especially on a big unified bootloader
So I stay tuned and ready to test.

Tomorrow I try it on a DS4 Mboard

@mackerintel: thanks for the explanation. As FavleX was wondering and searching about DSDT to understand more. Thanks again.

Well, emulating devices, i added for instance an SMC device to my DSDT, doesnt really do anything, but i have now SMC device in the IOReg:



greetz

..mmhh, probably I say an "idiot one" but I'm trying to enlight myself sorry in advance ..
If one day the last update release from apple , requests a SMC Sensor, I can go ahead with updating just emulating it?
Is this the meaning ?

Very nice fassl. Way to go.
@all: emulating SMC could enable the full-feature usage of unpatched PowerManagementBundle and sleep with vanilla kernels

Sleep, well fixing the _WAK Device in DSDT could enable sleep, some _WAK Devices need this at the end:
thx to realityiswhere for pointing that out.

doesnt get to compile dsdt.aml even with '-f' flag...



Is there a way to patch it manually (and compile it)?

Sure, patch Debug/dsdt_fixed.txt

then run

I ended up with a dsdt.hex file. Can I make the .aml file out of the hex?

@BlackCH

Can you post your dsdt.dsl. I am interesting to see how you manage both core to work. I have hp 530 and for now is no chance to run both core. Thare is no aliaces problem and processors in dsdt table are described in diferent way then in other comps

thanks

Nevermind, the file was actually empty. my dsdt.dsl wont compile (not even unmodified!). I tryed ./iasl -sa which gave me a .asm file but empty as well...
so I will try to do it on linux to see if I get to it.



Dual core was working out of the box. Im just trying to get RTC/HPET fixed.... But here is my (untouched) dsdt file if you want to have a look. Maybe you could help me

Your dump seems to be uncomplete and/or incorrectly disassembled. Try using latest iasl and look if you have SSDT

ASUS P5B-Deluxe..
Done mine, copied it over to the root with the new "boot", removed IntelCPUPMDisabler.kext and everything seems fine!

What is the function of the "dsdt_acpi12.diff" that comes with the "boot" file and where should it go!?
How can one see, test to see if it works or is the fact that I could remove IntelCPUPMDisabler.kext enough proof!?

SticMAN

As soon as your AppleIntelCPUPowerManagement.kext gets initialised without panic, the HPET patch worked.

greetz

I have iATKOS v4.1i updated to 10.5.5 via Software Update. Do I need this/how do I check if I need this?

Run the patcher, when it says: "Found IRQ in RTC Device -> removed", yeah then you need this to be able to update to 10.5.6 when its there.

greetz

The readme says:
How do I check if I'm using the Chameleon bootloader? I don't think I selected when I installed iATKOS, but I'm not 100% on that... I may be using the Darwin bootloader.

Chameleon is a modified Darwin bootloader, pretty all new distros come with Chameleon bootloader as default. Look up your Root on your OSX Partition, if there is a file called boot you should have chameleon installed.

greetz

I'm going to assume I don't then. How would I go about installing Chameleon sos I can install the DSDT patcher and eventually 10.5.6?

Google "chameleon osx" and use the installer to install it.


greetz

Hi,so nice job!!!
I try to use the patcher and i get this output:

Getting the DSDT...
ACPI contains 11 values
Failed to get DSDT


Decompiling the DSDT...

Intel ACPI Component Architecture
AML Disassembler version 20080926 [Oct 4 2008]
Copyright © 2000 - 2008 Intel Corporation
Supports ACPI Specification Revision 3.0a

Could not open input file ./dsdt.dat

What can be the problem?
Do you need any output from my system?
Thanks.

Failed to get the DSDT seems to be an Error from the GetDSDT Tool, thats not mine so i cant help you with that, what you could do to obtain your DSDT is:



This will write the ACPI Tables to ioregdump.txt, remove all other tables except the DSDT, then copy the hex values to a HEX Editor like 0xED and save it as dsdt.dat

then do this to decompile your DSDT:


To patch it do


greetz

Thanks! I will do it.

Have you launched the patcher as root? (eg using sudo)

Can somebody look in to my dsdt.dsl??? HPET and RTC seems to be fine but i can not run both cores. Thare are no aliasis. I have hp530, CD t2400 @ 1.83, gma950, mobile945 chipset.

thanks

Yes i do it as root using "su root".
Using your commands i have this output:

DSDT Patcher 1.0.1b -- report Bugs to superfassl@gmail.com
enclose "DSDT Patcher/Debug/USER.tar"
Press any key to continue...
Done, now start the Patching!

Could not open file dsdt.dat

There were errors pacthing the RTC

sh-3.2# ./DSDT\ Patcher dsdt.dsl
sh: ./DSDT Patcher: No such file or directory
sh-3.2#

Thanks

Scratch this, i have use your script placing the dsdt.dat besides it and has done his job!

Thanks again!

tyvm.

Said "Chameleon 1.0.11" when I booted, so I'll assume it worked.

Ran DSDT Patcher, copied dsdt.aml to /... That all I'm supposed to do?

Try this and pls report back: Click to view attachment



Yeah copy dsdt.aml to / and replace the /boot with the chameleon bootloader with dsdt override function. Thats all

No luck, but thanks

These one is from hp6720 and is very similar to my original in the beginning and he have both cores out of the box. http://forum.insanelymac.com/index.php?act...st&id=37317 .

Maybe need to combine those two???

When its very similar, just try to compile that one and boot with it, if you have all cores enabled then, run the Patcher to patch the other things.

greetz

I try that many times before i ask for help, but i am not coder , i work with networks. But in any case thanks for your fast answer and generous effort.

Ill take a look at it when i have time, or maybe another guy can do this

greetz

Whats wrong? 

Be sure to use latest version of patcher. Any help request should be accompanied by tar (explicitely said by patcher) or at least DSDT

Great !!!!!
Really great....

How can I figure out if I have SSDT?; Anyway some people at Ubuntu's forum claim to have edited the dsdt to fix thermal zones (here: http://ubuntuforums.org/showthread.php?t=659027&page=2 ). So apparently would be possible at least to make the dump from ubuntu... I will try that. Also I googled for the iasl; I only found some linux links ( http://packages.ubuntu.com/intrepid/i386/iasl/download ); Which version is on the dsdt patcher?


Thanks for the answers!

Great work!

What exactly are you patching?

I'm having problems waking from USB-devices and sometimes USB-devices are unavailable after wake from sleep.

From reading the ACPI specification it seems that these problems may be due to bad DSDT info. Do you optimize for this?

Maybe this could help.

How about boot-132 method with DSDT patching ?

Get the dsdt override diff (first link in this topic) and apply it to boot132 source, should work.

greetz

hehe, 'fass' is burning wheels in here ;)

go ahead, wish ya all well...

Post your DSDT. We'll have a look but promise nothing

BTW you can also search on the internet if some fixes are available for similar issues. DSDT-patching formely was used a lot in linux

Thank you very much