Jump to content

ACPI (DSDT) Patcher for BIOS and AML


koalala
 Share

845 posts in this topic

Recommended Posts

I have trying to compile previously decompiled DSDT.dsl, but the patcher throws an exception "File *** not found!", and deleted my DSDT.dsl. I was trying to include roisoft's solution for HDA on P35-DS3L.

Yes , that error (not found) is a bit stupid.

I had also such an ???

SOLUTION:

Open the .dsl file (that one you edited and want to recomplie to .aml) with textedit.

Look at at first lines (header).

You will find some information, i think the IASL uses - its the name and the path to it for the your.dsl file.

If path and/or name in the header doesnt fit to your extisting .dsl file (name + path to it)- you get that error.

So you have to be sure name of your mydsdt.dsdt is named EQUAL to that found in the mydsdt.dsl header !

Also you can remove maybe an not fitting path or not existing path to it, simple change it to "./now name of dsdtfile" and

put dsl file in same folder as iASL.

That error may happen special to people made handmade changes/addes and after that rename that file to for example mydsdt_NEW.dsl. Also if someone try to recompile an other users .dsl file , with path that mostly isnt on your mac. (/users/peter/desktop/peters.dsl for example).

Will give that error ... !

Link to comment
Share on other sites

Pardon for my english, is an machine translation.

 

In first place thank you for your magnificent work Koalala.

I only mean that I also have this sound so much unpleasant (POP) after a brief period of inactivity of the loudspeakers, I use a modified AppleHDA.

All the rest works perfectly.

Link to comment
Share on other sites

Question on the cpu aliases fix- I've got an ECS mb (g31t-m) and I've used your patcher to patch the AMI bios for the board. I don't seem to be able to see both cores of my core 2 duo after the patch, is that the only way I can verify whether the aliases patch worked? Any logs I can check? Thanks!

If you can boot without cpus=1 it works, else your problem can be different.

I tested with your BIOS, aliases are removed so it should work.

 

homepav, this problem sould only happen when putting dsdt file in the same folder than the patcher and your dsdt is named :

"dsdt.aml","dsdt.dsl" or "dsdt.xtr"

Since the patcher use it to store temp file, all that files are deleted before lauching functions.

Link to comment
Share on other sites

Can you tell me what is the exact option which cause this bug (Import DSDT, D/C, ...) ?

Thanks

 

In "D/C DSDT" page I selected .aml file, destination folder (different from aml file), not checked "patch before...", selected "Compile (to AML)" and pressed "D/C" and got "File not found!" error. Also patcher have deleted selected .dsl file.

Link to comment
Share on other sites

I answered in my previous message.

 

But It's not working. I exported DADT.dsl to C:\ and trying to compile DSDT.aml to D:\ and patcher deletes DSDT.dsl and said what It cant found "C:\DSDT.dsl".

 

Yeh, I found! After renaming DSDT.dsl patcher compile it! But if the file have name "DSDT" patcher always deletes it.

Link to comment
Share on other sites

But It's not working. I exported DADT.dsl to C:\ and trying to compile DSDT.aml to D:\ and patcher deletes DSDT.dsl and said what It cant found "C:\DSDT.dsl".

 

Yeh, I found! After renaming DSDT.dsl patcher compile it! But if the file have name "DSDT" patcher always deletes it.

 

?????? yes , work

Link to comment
Share on other sites

If you can boot without cpus=1 it works, else your problem can be different.

I tested with your BIOS, aliases are removed so it should work.

 

homepav, this problem sould only happen when putting dsdt file in the same folder than the patcher and your dsdt is named :

"dsdt.aml","dsdt.dsl" or "dsdt.xtr"

Since the patcher use it to store temp file, all that files are deleted before lauching functions.

 

You're right- it does indeed boot without cpus=1. Is it not just the bios aliases that prevent the kernel from recognizing both cores of a multi core cpu?

Link to comment
Share on other sites

I flashed my BIOS on Gigabyte Dual BIOS mobo P35-DS3L. It works just fine like with dsdt.aml but now im having two long beeps on restart before POST. I know that people have same experience here. Let's solve it guys! Or I will simply remove the beeper out of the mobo =)

Seriously, why do you think it happens?

Link to comment
Share on other sites

You're right- it does indeed boot without cpus=1. Is it not just the bios aliases that prevent the kernel from recognizing both cores of a multi core cpu?

Aliases are mis-interperted by OSX so it crash. CPU Aliases are useless, in real mac, there is no CPU aliases.

Link to comment
Share on other sites

I was unable to flash the bios

 

Here is copy of my bios for p5qc

sound realtec alc1200, 8 channel High definition Audio CODEC

 

The bios is version 1613

 

Here is the message from the patcher

 

0 Warning, 0 Error occurred.

Done.

 

Intel ACPI Component Architecture

AML Disassembler version 20081204 [Dec 4 2008]

Copyright © 2000 - 2008 Intel Corporation

Supports ACPI Specification Revision 3.0a

 

 

Intel ACPI Component Architecture

ASL Optimizing Compiler version 20081204 [Dec 4 2008]

Copyright © 2000 - 2008 Intel Corporation

Supports ACPI Specification Revision 3.0a

 

dsdt.dsl 2775: Name (_T_0, Zero)

Remark 5110 - Use of compiler reserved name ^ (_T_0)

 

dsdt.dsl 2860: Name (_T_0, Zero)

Remark 5110 - Use of compiler reserved name ^ (_T_0)

 

dsdt.dsl 2908: Name (_T_0, Zero)

Remark 5110 - Use of compiler reserved name ^ (_T_0)

 

dsdt.dsl 2974: Name (_T_0, Zero)

Remark 5110 - Use of compiler reserved name ^ (_T_0)

 

dsdt.dsl 3044: Name (_T_0, Zero)

Remark 5110 - Use of compiler reserved name ^ (_T_0)

 

dsdt.dsl 5768: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 5784: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 5876: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 5975: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 6470: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 6513: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 6597: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 6611: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 6730: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 6800: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 6891: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 6905: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 7032: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 7102: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 7106: Name (_T_1, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_1)

 

dsdt.dsl 7344: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 7407: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 7575: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 7608: Name (_T_1, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_1)

 

dsdt.dsl 7649: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 7705: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 7875: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 7903: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 7956: Name (_T_1, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_1)

 

dsdt.dsl 9622: Method (VGET, 1, NotSerialized)

Warning 1087 - ^ Not all control paths return a value (VGET)

 

dsdt.dsl 9667: Method (TGET, 1, NotSerialized)

Warning 1087 - ^ Not all control paths return a value (TGET)

 

dsdt.dsl 9720: Method (FGET, 1, NotSerialized)

Warning 1087 - ^ Not all control paths return a value (FGET)

 

dsdt.dsl 9751: Store (VGET (Local0), Local1)

Warning 1092 - ^ Called method may not always return a value

 

dsdt.dsl 9793: Store (TGET (Local0), Local1)

Warning 1092 - ^ Called method may not always return a value

 

dsdt.dsl 9826: Store (FGET (Local0), Local1)

Warning 1092 - ^ Called method may not always return a value

 

dsdt.dsl 10075: Name (_T_0, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_0)

 

dsdt.dsl 10143: ShiftRight (BUF2, 0x04)

Warning 1105 - Result is not used, operator has no effect ^

 

dsdt.dsl 10211: Name (_T_1, Zero)

Remark 5110 - ^ Use of compiler reserved name (_T_1)

 

ASL Input: dsdt.dsl - 10315 lines, 332792 bytes, 4839 keywords

AML Output: dsdt.aml - 38527 bytes, 996 named objects, 3843 executable opcodes

 

Compilation complete. 0 Errors, 7 Warnings, 31 Remarks, 69 Optimizations

 

0 Warning, 0 Error occurred.

Done.

P5QC_ASUS_1613m.zip

Link to comment
Share on other sites

Yes, you're right, but the "patched" ROM, is the original one when FATAL ERROR appeared. It would be better if no file were generated.

If the generated ROM isn't not working, tell me and use the attachement (manually patched).

 

Koalala;

 

Generated ROMs aren't working, neither is the manually patched one you posted.

 

EZ-Flash (Asus built-in BIOS flash tool) throws a 'boot block in file is not valid' error and refuses to flash.

 

I've successfully used this patched BIOS before:

http://www.osxcores.site50.net/page1/files...US-1406.ROM.zip

 

EZ-Flash won't let me downgrade by BIOS, so I can't go back to it now.

Maybe you can tell what's wrong by comparing the code.

Link to comment
Share on other sites

koalala

 

could it by any chance solve the two beeps problem on gigabytes?

 

For all those who have problem with real Dual BIOS Gigabyte, it's due to a corruption bug of cbrom. Try replacing cbrom with the attached file (rename it cbrom) and try patching. It will solve some problems but I don't know if it will solve Virtual Dual BIOS bug.

CBROM115.zip

Link to comment
Share on other sites

 Share

×
×
  • Create New...