DSDT Compiling...

hmm... For some reason iASL, or the iASLme.app (which generally is the same) will not compile without producing errors.

Yes, but then I need to edit the DSDT, which involves decompiling the DSDT, editing it then recompiling it and I cannot recompile it without errors.

Strange eh?

Cheers,
~ Cleo

Thank you very much, staticanime.

It compiled without errors once that fix were applied.

Greatly appreciated

Thanks again!
~ Cleo

NOTE: Make sure you are using the latest version of iasl

i can compille and decompile fine with iASLme.app

@SaCleoCheaterI'm having a bit of a problem.. Compiling DSL files just gives me a Bus error using Terminal, since every DSDT app is mainly based on iasl, I'm pretty much stuffed. Has anyone been able to compile DSDTs properly after upgrading to 10.5.8? Does anyone have a solution to this? Both my 10.5.7 and 10.5.8 hackintoshes seem to do this…

just get pcefi ver 9 installer. it has GUI dsdt patcher, make sure you select new hpet and make sure you force compile. good luck

@SaCleoCheaterI'm having a bit of a problem.. Compiling DSL files just gives me a Bus error using Terminal, since every DSDT app is mainly based on iasl, I'm pretty much stuffed. Has anyone been able to compile DSDTs properly after upgrading to 10.5.8? Does anyone have a solution to this? Both my 10.5.7 and 10.5.8 hackintoshes seem to do this…

just get pcefi ver 9 installer. it has GUI dsdt patcher, make sure you select new hpet and make sure you force compile. good luck

@SaCleoCheaterYes, but then I need to edit the DSDT, which involves decompiling the DSDT, editing it then recompiling it and I cannot recompile it without errors. Strange eh? Cheers, ~ Cleo

What errors are you getting, can you post them?

@SaCleoCheaterpaste bin.ca/1540346 Hmm.. Quite a few errors…

Can you dump a DSDT stright from the BIOS (IE, without any changes, and send me whatever chages you want/links to the code snippets), usually problems like that are from different character encoding sets (like combining UFT-8 and ISO-8859), that caused me headaches a few times. Not really a solution, but I found iasl.exe for Windows ignores the encoding, and still compiles the DSDT correctly (yes, it will still work on OSX)

I'm in Windows atm, so if you want me to try that for you, just send me the DSDt and the code you need fixed

EDIT: Scratch all that, here's quote from the Ubuntu forums of someone with similar errors:

Line 24 had the wrong syntax. That was causing the whole file to show errors. The Microsoft compiler loves to do this. The original line was (^CPU0._PPC). The "^" symbol doesn't belong here. I changed it to the ACPI compliant (\_PR_.CPU0._PPC) method, and you have zero errors/warnings. It was actually a good dsdt with some monkey…

So, make that change, the file shold compile perfectly

@SaCleoCheaterThank you very much, staticanime. It compiled without errors once that fix were applied. Greatly appreciated Thanks again! ~ Cleo

Ha ha, no prb. been messing with DSDT for the last while, got native speedstep, sleep on lid close, vga string injection, audio/lan/wifi info injection to System Profiler & HPET fix on my Msi Wind U100 DSDT, that coupled with patched GMA950kexts, voodoohda/battery/ps2controller, r1000.kext, fakesmc.kext and UUID.kext, all in EFI, means perfect Leopard on my Wind

Working with other on trying to do away with R1000/UUID.kext, would be awesome if we can (would mean I'll be down to 6 kexts in EFI)