T-Bone90 Posted April 21, 2010 Share Posted April 21, 2010 Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/ Share on other sites More sharing options...
Avelarius Posted April 21, 2010 Share Posted April 21, 2010 Hello, i currently have the problem, when i try to compile my dsdt with DSDTSE (by Team Ev0sx86) i always get an error but i dont know how to solve it, without making my dsdt unusable. I'll attach my patched dsdt and the original. I get this messages Intel ACPI Component Architecture ASL Optimizing Compiler version 20100331 [Mar 31 2010] Copyright (c) 2000 - 2010 Intel Corporation Supports ACPI Specification Revision 4.0 dsdt.dsl 417: Name (_HID, "*pnp0c14") Error 4001 - ^ String must be entirely alphanumeric (*pnp0c14) dsdt.dsl 430: Name (_WDG, Buffer (0x64) Warning 1099 - ^ Unknown reserved name (_WDG) dsdt.dsl 446: Method (_WED, 1, NotSerialized) Warning 1099 - Unknown reserved name ^ (_WED) dsdt.dsl 446: Method (_WED, 1, NotSerialized) Warning 1088 - ^ Not all control paths return a value (_WED) dsdt.dsl 446: Method (_WED, 1, NotSerialized) Warning 1099 - Unknown reserved name ^ (_WED) dsdt.dsl 685: Name (_T_0, 0x00) Remark 5111 - Use of compiler reserved name ^ (_T_0) dsdt.dsl 799: Name (_T_1, 0x00) Remark 5111 - Use of compiler reserved name ^ (_T_1) dsdt.dsl 843: Name (_T_2, 0x00) Remark 5111 - Use of compiler reserved name ^ (_T_2) dsdt.dsl 894: Name (_T_3, 0x00) Remark 5111 - Use of compiler reserved name ^ (_T_3) dsdt.dsl 931: Name (_T_4, 0x00) Remark 5111 - Use of compiler reserved name ^ (_T_4) dsdt.dsl 973: Name (_T_5, 0x00) Remark 5111 - Use of compiler reserved name ^ (_T_5) dsdt.dsl 6513: Method (HKDS, 1, NotSerialized) Warning 1088 - ^ Not all control paths return a value (HKDS) ASL Input: dsdt.dsl - 8020 lines, 283822 bytes, 3153 keywords Compilation complete. 1 Errors, 5 Warnings, 6 Remarks, 908 Optimizations [Completed] Thanks in advance original_dsdt.zip patched_dsdt.zip Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1453109 Share on other sites More sharing options...
Beerkex'd Posted April 21, 2010 Share Posted April 21, 2010 Do a search and replace of "_T_" with "T_" to fix all your "Remark 5111". That's the easy one.. For the two "warning 1088" you need to add a return 0 at the end. Some clues here (from post #9 an onwards): http://www.projectosx.com/forum/index.php?showtopic=454 As for the rest I have no idea. Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1453112 Share on other sites More sharing options...
Avelarius Posted April 21, 2010 Share Posted April 21, 2010 What is this "HKDS thing" and where do i have to ad a return 0? At the end of the file, or under the section with the "_T_"'s? Could you show me a example? (Sorry for not so good englisch - i'm german) Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1453122 Share on other sites More sharing options...
T-Bone90 Posted April 21, 2010 Author Share Posted April 21, 2010 Hi, oh my Post are blank ^^ Here is my DSDT: http://pastebin.com/p9TbeQuW And here are the Tutorial: http://www.insanelymac.com/forum/index.php...t&p=1280888 OK how can I post the PSS and CST for me, where can I found the Adresses ? And are the Adresses in the DSDT, I mean 0x0.... are from Board to Board different ? I have a P5Q-E, can I copy the DSDT from a P5Q-E and chance the CPU Info ? Or more different. The Problem at the Moment is, I came not forward Many Adresses are different and I don't know were I can found this for my System Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1453136 Share on other sites More sharing options...
Beerkex'd Posted April 21, 2010 Share Posted April 21, 2010 Everything you need to know about speed stepping is in this thread: http://www.insanelymac.com/forum/index.php?showtopic=181631 What is this "HKDS thing" and where do i have to ad a return 0? Follow the link I posted for more information. That's all the help I can give. "HKDS" is secondary, what's important is the error message and the error/warning/remark code. If you see " Warning 1088: Not all control paths return a value" you can fix this in the same way as anyone else who gets this error. To fix this warning 1088 you need to add a return 0 at the end of the method in question, which in your case is method HKDS. It even tells you which line number it's on. So you can find it by line number or just search the DSDT for instances of HKDS. By comparing the information you have with the information you find by following the link I posted, you should be able to fix this yourself. I can't be more specific simply because I don't remember exactly how to do it. As for the all the _T_ remarks just use the replace function in DSDTSE as I said. It has nothing to do with HKDS or any of the other errors. It's a common issue in ASUS motherboard DSDTs. Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1453146 Share on other sites More sharing options...
T-Bone90 Posted April 22, 2010 Author Share Posted April 22, 2010 Thanks a lot, very cool. Another PRoblem from your DSDT. OperationRegion (BIOS, SystemMemory, 0xCFF7E064, 0xFF) Field (BIOS, ByteAcc, NoLock, Preserve) { SLPS, 8, Offset (0x0B), MG1B, 32, MG1L, 32, MG2B, 32, MG2L, 32, Offset (0x2C), ASSB, 8, Offset (0x38), MG3B, 32, MG3L, 32 } Can I copy this 1 to 1 for my System or where can I found Numbers for me ? And by: Name (CST, Package (0x04) { 0x03, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, One, One, 0x03E8 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000000814, // Address ,) }, 0x02, One, 0x01F4 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000000816, // Address ,) }, 0x03, 0x39, 0x64 } }) Are the Adresses for me too ? OR where can I found this for example 0x03, 0x39, 0x64 And the last question, is it good to use MACPro 3.1 with my System or is it better to use 4.1 or IMAC ? Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1453727 Share on other sites More sharing options...
Beerkex'd Posted April 24, 2010 Share Posted April 24, 2010 You must change at least "0xCFF7E064, 0xFF" so that it matches the value in your DSDT. If you compare the rest of that section with your unmodified DSDT you'll see a lot of stuff has been deleted from mine. You should only copy that whole section if you've made the same modifications as I have. If you want to learn more, look here: http://www.insanelymac.com/forum/index.php...t&p=1280888 Almost all my modifications are based on the DSDTs posted by Master Chief in that thread. The other bit you quote is specific for my CPU (C-states), don't use it unless you're sure it matches yours. You need to extract your SSDT tables and see what the code looks like for your CPU. Again (for the third time, first time was via PM) you need to read this, it is all explained here: http://www.insanelymac.com/forum/index.php?showtopic=181631 I would only recommend using a MacPro4,1 model identifier to someone who has a Nehalem CPU. I use iMac9,1 which works very well for me. I think most people with P45/P35 chipset motherboards use MacPro3,1 though. Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1454559 Share on other sites More sharing options...
T-Bone90 Posted April 24, 2010 Author Share Posted April 24, 2010 You must change at least "0xCFF7E064, 0xFF" so that it matches the value in your DSDT. Where can I found this for me ? Where is it ? If you compare the rest of that section with your unmodified DSDT you'll see a lot of stuff has been deleted from mine. You should only copy that whole section if you've made the same modifications as I have. If you want to learn more, look here:http://www.insanelymac.com/forum/index.php...t&p=1280888 Almost all my modifications are based on the DSDTs posted by Master Chief in that thread. All Right The other bit you quote is specific for my CPU (C-states), don't use it unless you're sure it matches yours.You need to extract your SSDT tables and see what the code looks like for your CPU. Again (for the third time, first time was via PM) you need to read this, it is all explained here: http://www.insanelymac.com/forum/index.php?showtopic=181631 I have extract my DSDT but what Codes I need ? Can you look in my SSDT in the Archiv ? I don't find any Info about CST in this Thread. I would only recommend using a MacPro4,1 model identifier to someone who has a Nehalem CPU. I use iMac9,1 which works very well for me. I think most people with P45/P35 chipset motherboards use MacPro3,1 though. OK I use actualy MacPro 3.1 but I test it with IMac. Only Test SSDT.dsl.zip Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1455026 Share on other sites More sharing options...
Beerkex'd Posted April 24, 2010 Share Posted April 24, 2010 Where can I found this for me ? Where is it ? It's in the same place as it is in my DSDT. You have the same motherboard as I do! Open your DSDT and mine side by side and compare the code, or just use the search function in DSDTSE. Type for example "OperationRegion" in the search field. I have extract my DSDT but what Codes I need ? Can you look in my SSDT in the Archiv ? There are no C-states in the table you've extracted. Try using Everest in Windows and extract all the SSDT tables. Again, read the Speedstepping thread, all the information you need is there. I don't find any Info about CST in this Thread. It's right there in the first post. Scroll the 2nd codebox. C-States are covered in greater detail towards the end of the thread, just keep looking and you'll find it eventually. Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1455034 Share on other sites More sharing options...
T-Bone90 Posted April 24, 2010 Author Share Posted April 24, 2010 It's in the same place as it is in my DSDT. You have the same motherboard as I do! Open your DSDT and mine side by side and compare the code, or just use the search function in DSDTSE. Type for example "OperationRegion" in the search field. Thanks I found it There are no C-states in the table you've extracted. Try using Everest in Windows and extract all the SSDT tables. Again, read the Speedstepping thread, all the information you need it there. Thanks I test it with Everest. It's right there in the first post. Scroll the codebox. C-States are covered in greater detail towards the end of the thread, just keep looking and you'll find it eventually. Yes I found this in the 2 Codebox Method (_CST, 0, NotSerialized) { Return (Package (0x02) { One, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, One, 0x9D, 0x03E8 } }) } } 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size 0x9D, 0x03E8 This six Codes, I don't found any Infos too this in the Thread. Please Can you help me ? Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1455047 Share on other sites More sharing options...
Beerkex'd Posted April 24, 2010 Share Posted April 24, 2010 Trust me the info is there, don't give up, keep looking. You need to get all your SSDT tables extracted first so you have something to compare with. Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1455069 Share on other sites More sharing options...
T-Bone90 Posted April 24, 2010 Author Share Posted April 24, 2010 HEy, now I have 3 SSDT Tables, extracted from Everest Windows. But this three are in .bin, where can I chance it to read ? Archiv.zip Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1455148 Share on other sites More sharing options...
Beerkex'd Posted April 25, 2010 Share Posted April 25, 2010 Just rename them to .aml and decompile them. Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1455328 Share on other sites More sharing options...
T-Bone90 Posted April 25, 2010 Author Share Posted April 25, 2010 OK I have. Is this right. I must use Method (_PCT to write the 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ? But One, 0x9D, 0x03E8 I don't found. Archiv.zip Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1455347 Share on other sites More sharing options...
Beerkex'd Posted April 25, 2010 Share Posted April 25, 2010 I get five SSDT tables when dumping with Everest. Do you have C-states disabled in the BIOS? In the BIOS, Look in the CPU settings menu. You may have to scroll down, the last C-state setting is off-screen in my BIOS. Do you know the version (stepping) of your CPU? mine for example is stepping E0, ie the last E8500: http://processorfinder.intel.com/details.aspx?sSpec=SLB9K Different versions of the same CPU can have different capabilities. if you know the details you can look up your CPU on Intel's website and see exactly which features it supports. Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1455595 Share on other sites More sharing options...
T-Bone90 Posted April 25, 2010 Author Share Posted April 25, 2010 I have B2 ^^ I have look in the BIOS by C1E and so on but I don't found C-states off screen. With witch KEy can I scroll down ? Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1455623 Share on other sites More sharing options...
Beerkex'd Posted April 26, 2010 Share Posted April 26, 2010 As you can see, your CPU can only do C1E: http://processorfinder.intel.com/details.aspx?sSpec=SL9ZL Compare with mine: http://processorfinder.intel.com/details.aspx?sSpec=SLB9K That means you can use the CST code the way it is in FormerlyKnownAs' example. With witch KEy can I scroll down ? uhh let's see.. the up arrow? No, that can't be it... Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1455828 Share on other sites More sharing options...
T-Bone90 Posted April 26, 2010 Author Share Posted April 26, 2010 ah OK also I can use the CST code from http://www.insanelymac.com/forum/index.php?showtopic=181631 in the 2 Codebox ? Or can I use your code because the features from both CPUs are the same ? In my BIOS, i dont find the hide Option in the CPU Menü Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1456189 Share on other sites More sharing options...
Beerkex'd Posted April 26, 2010 Share Posted April 26, 2010 Please pay attention to what I'm writing and follow the links that I post so that you can educate yourself. Having to repeat what I say when speaking is one thing, but when it's in writing and pictures clear as day, then it's just a waste of time. I am not here to hold your hand. As you can clearly see in the specs page for your CPU (refer to screenshot below), it only supports C1E. This means you can use the generic CST code in FormerlyKnownAs' example: Method (_CST, 0, NotSerialized) { Return (Package (0x02) { One, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, One, 0x9D, 0x03E8 } }) } Our CPU features are not the same. Yours: Mine: What "hide" option? Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1456198 Share on other sites More sharing options...
T-Bone90 Posted April 26, 2010 Author Share Posted April 26, 2010 I mean the option in the bios, that I can see when I scroll.# Also you mean the CST COde from my SSDT right ? Also I copy the CST Code from the Codebox 2 and rename the Code with my Code from the SSDT ? Sorry fro my bad english ^^ Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1456201 Share on other sites More sharing options...
Beerkex'd Posted April 26, 2010 Share Posted April 26, 2010 I mean the option in the bios, that I can see when I scroll.# Ah you meant to say "hidden" not "hide". That's because it isn't there, the BIOS "CPU features" page only shows features that are actually supported by your CPU! Read my previous post again. Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1456209 Share on other sites More sharing options...
T-Bone90 Posted April 26, 2010 Author Share Posted April 26, 2010 OK thanks and sorry. Iam not 100% understand you ^^ OK then I use FormerlyKnownAs' example: 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size One, 0x9D, 0x03E8 Can I use this addresses or need I other values from my SSDT or other ? Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1456322 Share on other sites More sharing options...
Beerkex'd Posted April 26, 2010 Share Posted April 26, 2010 LOL, this is the third and last time I'm going to say this: You can use the _CST method as it is in the example posted by FormerlyKnownAs. As for the rest, just follow the guide. I recommend that you continue in the German sub-forum: http://www.insanelymac.com/forum/index.php?showforum=93 Link to comment https://www.insanelymac.com/forum/topic/216128-dsdt-problem-with-hex/#findComment-1456331 Share on other sites More sharing options...
Recommended Posts