LocusOfControl Posted January 16, 2010 Share Posted January 16, 2010 d00d,thanks for the tips, i managed to solve the `turbo enabled but no turbo P-state found' warning message. now i have a lot of 'FakeSMC: key not found' message in kernel.log is this something i should worried? Jan 15 18:45:26 GigaMacPro kernel[0]: FakeSMC: key not found BEMB, length - 1 Jan 15 18:50:01 GigaMacPro kernel[0]: FakeSMC: key info not found TB2T, length - 6 Jan 15 18:50:01 GigaMacPro kernel[0]: FakeSMC: key info not found TB3T, length - 6 Jan 15 18:50:01 GigaMacPro kernel[0]: FakeSMC: key info not found TN0P, length - 6 Jan 15 18:50:01 GigaMacPro kernel[0]: FakeSMC: key info not found TN1P, length - 6 ... i haven't tried this, but from http://www.insanelymac.com/forum/index.php?showtopic=186490 , apparently we could turn off the debug to get rid these messages. fyi, i have to use vi to paste the processor part of dsdt, no more error when compiling. for strange reason pasting that part using DSDTSE creates strange error and the line pointed by the error message doesn't make sense at all. about Temperature Monitor, the CPU Temp Diodes show incredibly high more than 10000 degree, SMC CPU Diodes too, in the range of 9000 degree. however the CPU Cores seem reasonable, about 39 degree. is this normal or there is something that i missed? thanks again d00d ciao For those curious about what those SMC keys mean, more info here inc how to create a realistic serial number etc http://prasys.co.cc/2009/12/understanding-...about-smc-keys/ Link to comment Share on other sites More sharing options...
d00d Posted January 16, 2010 Author Share Posted January 16, 2010 For step #16, is there a benefit to using that DSDT patch if you don't plan on using the modified bootloader, since you'll need a kext for restart functionality anyway? Also, for #5 your posted code and the attached dsdt file (for a 920) don't seem to match up. Is one of them incorrect? Ryan! Yes, you wouldn't need 16 if you're using EvOreboot.kext or similar.I use 16 because I need shutdown, but don't use restart. When a restart fix or option is added to C2RC5 I'll have both. Different in what way? The instructions are the same as the dsdt.dsl, and the compiler makes some changes (removes some comments, shortens hex, etc.) from that to the DSDT.aml. For those curious about what those SMC keys mean, more info here inc how to create a realistic serial number etc http://prasys.co.cc/2009/12/understanding-...about-smc-keys/ Here's another good one;http://www.mail-archive.com/mactel-linux-u...t/msg00860.html Hehe, is this is rather funny, look at this KP: But, it's not that funny, because KP's really frustrate me. Especially since they seem to happen more often now. I got the KP while in Logitech Control centre, setting the scroll acceleration to "none" gave a KP. This time, it's not of the type "13 general protection" but "14 page fault" which often has to do with memory (if I'm right). I have no overclock at all though! d00d, I'm not sure if you've seen my last post, but I'm really lost in the woods now. I'm thinking of completely rebuilding my DSDT. In order to do that I have to get a fresh DSDT first, because I'm not sure if your attached (920) DSDT is OK, is it? I don't know what to recommend at this point, but I don't think it's your DSDT.I've been using the v2 DSDT attached to post 1 for two weeks without KP, and used v1 for another two weeks before that without KP. I also did a diff of your DSDT against mine, and there's no difference. Link to comment Share on other sites More sharing options...
kdawg Posted January 16, 2010 Share Posted January 16, 2010 Yes, you wouldn't need 16 if you're using EvOreboot.kext or similar.I use 16 because I need shutdown, but don't use restart. When a restart fix or option is added to C2RC5 I'll have both. Different in what way? The instructions are the same as the dsdt.dsl, and the compiler makes some changes (removes some comments, shortens hex, etc.) from that to the DSDT.aml. Here's another good one; http://www.mail-archive.com/mactel-linux-u...t/msg00860.html I don't know what to recommend at this point, but I don't think it's your DSDT. I've been using the v2 DSDT attached to post 1 for two weeks without KP, and used v1 for another two weeks before that without KP. I also did a diff of your DSDT against mine, and there's no difference. I think you really should check all the voltages in your BIOS. Especially your RAM's timings and voltage. If you overclocked your processor at all I would check the vcore too. If you're using BIOS from identical systems then most likely a hardware issue. I'm not saying it couldn't be something else like a bad install, a random mkext, whatever. I say it's most likely something in your settings. You can't just set the motherboard on auto and trust it'll set everything right, especially Gigabyte mobos. Lasty Logitech makes crappy software for the Mac. It'll causes all sorts of problems, check your logs. I'm sure it's riddled with all sorts of Logitech related stuff. Link to comment Share on other sites More sharing options...
d00d Posted January 16, 2010 Author Share Posted January 16, 2010 I think you really should check all the voltages in your BIOS. Especially your RAM's timings and voltage. If you overclocked your processor at all I would check the vcore too. If you're using BIOS from identical systems then most likely a hardware issue. I'm not saying it couldn't be something else like a bad install, a random mkext, whatever. I say it's most likely something in your settings. You can't just set the motherboard on auto and trust it'll set everything right, especially Gigabyte mobos. Lasty Logitech makes crappy software for the Mac. It'll causes all sorts of problems, check your logs. I'm sure it's riddled with all sorts of Logitech related stuff.My trackball works fine without any Logitech software;Trackball: Product ID: 0xc404 Vendor ID: 0x046d (Logitech Inc.) Version: 2.20 Speed: Up to 1.5 Mb/sec Manufacturer: Logitech Location ID: 0x5a100000 Current Available (mA): 500 Current Required (mA): 100 Link to comment Share on other sites More sharing options...
Josvdp Posted January 16, 2010 Share Posted January 16, 2010 I think you really should check all the voltages in your BIOS. Especially your RAM's timings and voltage. If you overclocked your processor at all I would check the vcore too. If you're using BIOS from identical systems then most likely a hardware issue. I'm not saying it couldn't be something else like a bad install, a random mkext, whatever. I say it's most likely something in your settings. You can't just set the motherboard on auto and trust it'll set everything right, especially Gigabyte mobos. Lasty Logitech makes crappy software for the Mac. It'll causes all sorts of problems, check your logs. I'm sure it's riddled with all sorts of Logitech related stuff. As I posted earlier, I took off my OC and everything is running stock now. So that's not the problem. Is it possible that my i7 got damaged from running too hot? I guess it would have just been either dead or working, not anything in the middle Link to comment Share on other sites More sharing options...
d00d Posted January 16, 2010 Author Share Posted January 16, 2010 As I posted earlier, I took off my OC and everything is running stock now. So that's not the problem. Is it possible that my i7 got damaged from running too hot? I guess it would have just been either dead or working, not anything in the middle What are you running your 1333 MHz memory at?My memory that's rated for 1333 MHz starts to get flaky around 1520 MHz. Link to comment Share on other sites More sharing options...
kdawg Posted January 16, 2010 Share Posted January 16, 2010 What are you running your 1333 MHz memory at?My memory that's rated for 1333 MHz starts to get flaky around 1520 MHz. I would check the stock voltage for your RAM then compare it to what the mobo is actually giving it and make sure the two match up. Check the section where you can see the fan speeds it'll show it there. Link to comment Share on other sites More sharing options...
aikidoka25 Posted January 16, 2010 Share Posted January 16, 2010 ...Different in what way? The instructions are the same as the dsdt.dsl, and the compiler makes some changes (removes some comments, shortens hex, etc.) from that to the DSDT.aml. ... i noticed that too, the attached dsl for 920 has a repeated processor section, i mean the vanilla section still there. common sense, i only follow the one from the section quoted in post #1 instead. Link to comment Share on other sites More sharing options...
d00d Posted January 16, 2010 Author Share Posted January 16, 2010 i noticed that too,the attached dsl for 920 has a repeated processor section, i mean the vanilla section still there. common sense, i only follow the one from the section quoted in post #1 instead. I just looked at it again and don't see any repetition, there's CPU0, and aliases to that with the other seven.Would you explain what you mean in greater detail? Link to comment Share on other sites More sharing options...
ryansimms Posted January 16, 2010 Share Posted January 16, 2010 I could be mistaken, but here's the section embedded in post #1: Processor (\_PR.CPU0, 0x00, 0x00000410, 0x06) { Name (_CST, Package (0x07) { 0x06, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, 0x01, 0x0001, 0x000003E8 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000010, // Address 0x01, // Access Size ) }, 0x02, 0x0040, 0x000001F4 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000020, // Address 0x01, // Access Size ) }, 0x03, 0x0060, 0x0000015E }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x00, // Bit Width 0x00, // Bit Offset 0x0000000000000000, // Address ,) }, 0x01, 0x0001, 0x000003E8 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000000414, // Address ,) }, 0x02, 0x0040, 0x000001F4 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000000415, // Address ,) }, 0x03, 0x0060, 0x0000015E } }) Name (_PCT, Package (0x02) { ResourceTemplate () { Register (FFixedHW, 0x40, // Bit Width 0x00, // Bit Offset 0x0000000000000199, // Address ,) }, ResourceTemplate () { Register (FFixedHW, 0x10, // Bit Width 0x00, // Bit Offset 0x0000000000000198, // Address ,) } }) Name (_PSS, Package (0x0A) { Package (0x06) { 0x00000A65, 0x0001FBD0, 0x0000000A, 0x0000000A, 0x00000015, 0x00000015 }, Package (0x06) { 0x00000A64, 0x0001FBD0, 0x0000000A, 0x0000000A, 0x00000014, 0x00000014 }, Package (0x06) { 0x000009DF, 0x0001A9C8, 0x0000000A, 0x0000000A, 0x00000013, 0x00000013 }, Package (0x06) { 0x0000095A, 0x000186A0, 0x0000000A, 0x0000000A, 0x00000012, 0x00000012 }, Package (0x06) { 0x000008D5, 0x00014438, 0x0000000A, 0x0000000A, 0x00000011, 0x00000011 }, Package (0x06) { 0x00000850, 0x000128E0, 0x0000000A, 0x0000000A, 0x00000010, 0x00000010 }, Package (0x06) { 0x000007CB, 0x0000F618, 0x0000000A, 0x0000000A, 0x0000000F, 0x0000000F }, Package (0x06) { 0x00000746, 0x0000DEA8, 0x0000000A, 0x0000000A, 0x0000000E, 0x0000000E }, Package (0x06) { 0x000006C1, 0x0000B798, 0x0000000A, 0x0000000A, 0x0000000D, 0x0000000D }, Package (0x06) { 0x0000063C, 0x0000A7F8, 0x0000000A, 0x0000000A, 0x0000000C, 0x0000000C } }) Method (_PPC, 0, NotSerialized) { Return (Zero) } } Processor (\_PR.CPU1, 0x01, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU2, 0x02, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU3, 0x03, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU4, 0x04, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU5, 0x05, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU6, 0x06, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU7, 0x07, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } and here's that same section from the DSDt file attached to post #1: Processor (\_PR.CPU0, 0x00, 0x00000410, 0x06) { Name (_CST, Package (0x07) { 0x06, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, 0x01, 0x0001, 0x000003E8 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000010, // Address 0x01, // Access Size ) }, 0x02, 0x0040, 0x000001F4 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000020, // Address 0x01, // Access Size ) }, 0x03, 0x0060, 0x0000015E }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x00, // Bit Width 0x00, // Bit Offset 0x0000000000000000, // Address ,) }, 0x01, 0x0001, 0x000003E8 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000000414, // Address ,) }, 0x02, 0x0040, 0x000001F4 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000000415, // Address ,) }, 0x03, 0x0060, 0x0000015E } }) Name (_PCT, Package (0x02) { ResourceTemplate () { Register (FFixedHW, 0x40, // Bit Width 0x00, // Bit Offset 0x0000000000000199, // Address ,) }, ResourceTemplate () { Register (FFixedHW, 0x10, // Bit Width 0x00, // Bit Offset 0x0000000000000198, // Address ,) } }) Name (_PSS, Package (0x0A) { Package (0x06) { 0x00000A65, 0x0001FBD0, 0x0000000A, 0x0000000A, 0x00000015, 0x00000015 }, Package (0x06) { 0x00000A64, 0x0001FBD0, 0x0000000A, 0x0000000A, 0x00000014, 0x00000014 }, Package (0x06) { 0x000009DF, 0x0001A9C8, 0x0000000A, 0x0000000A, 0x00000013, 0x00000013 }, Package (0x06) { 0x0000095A, 0x000186A0, 0x0000000A, 0x0000000A, 0x00000012, 0x00000012 }, Package (0x06) { 0x000008D5, 0x00014438, 0x0000000A, 0x0000000A, 0x00000011, 0x00000011 }, Package (0x06) { 0x00000850, 0x000128E0, 0x0000000A, 0x0000000A, 0x00000010, 0x00000010 }, Package (0x06) { 0x000007CB, 0x0000F618, 0x0000000A, 0x0000000A, 0x0000000F, 0x0000000F }, Package (0x06) { 0x00000746, 0x0000DEA8, 0x0000000A, 0x0000000A, 0x0000000E, 0x0000000E }, Package (0x06) { 0x000006C1, 0x0000B798, 0x0000000A, 0x0000000A, 0x0000000D, 0x0000000D }, Package (0x06) { 0x0000063C, 0x0000A7F8, 0x0000000A, 0x0000000A, 0x0000000C, 0x0000000C } }) Method (_PPC, 0, NotSerialized) { Return (Zero) } } Processor (\_PR.CPU1, 0x01, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU2, 0x02, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU3, 0x03, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU4, 0x04, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU5, 0x05, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU6, 0x06, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU7, 0x07, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU8, 0x08, 0x00000410, 0x06) {} Processor (\_PR.CPU9, 0x09, 0x00000410, 0x06) {} Processor (\_PR.CPUA, 0x0A, 0x00000410, 0x06) {} Processor (\_PR.CPUB, 0x0B, 0x00000410, 0x06) {} Processor (\_PR.CPUC, 0x0C, 0x00000410, 0x06) {} Processor (\_PR.CPUD, 0x0D, 0x00000410, 0x06) {} Processor (\_PR.CPUE, 0x0E, 0x00000410, 0x06) {} Processor (\_PR.CPUF, 0x0F, 0x00000410, 0x06) {} } The extra bit is at the end of the second box. It's not quite the same as the original code, it's for CPU8-CPUF. Ryan! Link to comment Share on other sites More sharing options...
aikidoka25 Posted January 16, 2010 Share Posted January 16, 2010 The extra bit is at the end of the second box. It's not quite the same as the original code, it's for CPU8-CPUF. Ryan! since i followed the posted version, i don't have those extras. are the required/important? side question: why there are another 8 CPUs more (16 in total)? provision for next generation (8 cores) processor? Link to comment Share on other sites More sharing options...
d00d Posted January 16, 2010 Author Share Posted January 16, 2010 I could be mistaken, but here's the section embedded in post #1: Processor (\_PR.CPU0, 0x00, 0x00000410, 0x06) { Name (_CST, Package (0x07) { 0x06, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, 0x01, 0x0001, 0x000003E8 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000010, // Address 0x01, // Access Size ) }, 0x02, 0x0040, 0x000001F4 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000020, // Address 0x01, // Access Size ) }, 0x03, 0x0060, 0x0000015E }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x00, // Bit Width 0x00, // Bit Offset 0x0000000000000000, // Address ,) }, 0x01, 0x0001, 0x000003E8 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000000414, // Address ,) }, 0x02, 0x0040, 0x000001F4 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000000415, // Address ,) }, 0x03, 0x0060, 0x0000015E } }) Name (_PCT, Package (0x02) { ResourceTemplate () { Register (FFixedHW, 0x40, // Bit Width 0x00, // Bit Offset 0x0000000000000199, // Address ,) }, ResourceTemplate () { Register (FFixedHW, 0x10, // Bit Width 0x00, // Bit Offset 0x0000000000000198, // Address ,) } }) Name (_PSS, Package (0x0A) { Package (0x06) { 0x00000A65, 0x0001FBD0, 0x0000000A, 0x0000000A, 0x00000015, 0x00000015 }, Package (0x06) { 0x00000A64, 0x0001FBD0, 0x0000000A, 0x0000000A, 0x00000014, 0x00000014 }, Package (0x06) { 0x000009DF, 0x0001A9C8, 0x0000000A, 0x0000000A, 0x00000013, 0x00000013 }, Package (0x06) { 0x0000095A, 0x000186A0, 0x0000000A, 0x0000000A, 0x00000012, 0x00000012 }, Package (0x06) { 0x000008D5, 0x00014438, 0x0000000A, 0x0000000A, 0x00000011, 0x00000011 }, Package (0x06) { 0x00000850, 0x000128E0, 0x0000000A, 0x0000000A, 0x00000010, 0x00000010 }, Package (0x06) { 0x000007CB, 0x0000F618, 0x0000000A, 0x0000000A, 0x0000000F, 0x0000000F }, Package (0x06) { 0x00000746, 0x0000DEA8, 0x0000000A, 0x0000000A, 0x0000000E, 0x0000000E }, Package (0x06) { 0x000006C1, 0x0000B798, 0x0000000A, 0x0000000A, 0x0000000D, 0x0000000D }, Package (0x06) { 0x0000063C, 0x0000A7F8, 0x0000000A, 0x0000000A, 0x0000000C, 0x0000000C } }) Method (_PPC, 0, NotSerialized) { Return (Zero) } } Processor (\_PR.CPU1, 0x01, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU2, 0x02, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU3, 0x03, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU4, 0x04, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU5, 0x05, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU6, 0x06, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU7, 0x07, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } and here's that same section from the DSDt file attached to post #1: Processor (\_PR.CPU0, 0x00, 0x00000410, 0x06) { Name (_CST, Package (0x07) { 0x06, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, 0x01, 0x0001, 0x000003E8 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000010, // Address 0x01, // Access Size ) }, 0x02, 0x0040, 0x000001F4 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000020, // Address 0x01, // Access Size ) }, 0x03, 0x0060, 0x0000015E }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x00, // Bit Width 0x00, // Bit Offset 0x0000000000000000, // Address ,) }, 0x01, 0x0001, 0x000003E8 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000000414, // Address ,) }, 0x02, 0x0040, 0x000001F4 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000000415, // Address ,) }, 0x03, 0x0060, 0x0000015E } }) Name (_PCT, Package (0x02) { ResourceTemplate () { Register (FFixedHW, 0x40, // Bit Width 0x00, // Bit Offset 0x0000000000000199, // Address ,) }, ResourceTemplate () { Register (FFixedHW, 0x10, // Bit Width 0x00, // Bit Offset 0x0000000000000198, // Address ,) } }) Name (_PSS, Package (0x0A) { Package (0x06) { 0x00000A65, 0x0001FBD0, 0x0000000A, 0x0000000A, 0x00000015, 0x00000015 }, Package (0x06) { 0x00000A64, 0x0001FBD0, 0x0000000A, 0x0000000A, 0x00000014, 0x00000014 }, Package (0x06) { 0x000009DF, 0x0001A9C8, 0x0000000A, 0x0000000A, 0x00000013, 0x00000013 }, Package (0x06) { 0x0000095A, 0x000186A0, 0x0000000A, 0x0000000A, 0x00000012, 0x00000012 }, Package (0x06) { 0x000008D5, 0x00014438, 0x0000000A, 0x0000000A, 0x00000011, 0x00000011 }, Package (0x06) { 0x00000850, 0x000128E0, 0x0000000A, 0x0000000A, 0x00000010, 0x00000010 }, Package (0x06) { 0x000007CB, 0x0000F618, 0x0000000A, 0x0000000A, 0x0000000F, 0x0000000F }, Package (0x06) { 0x00000746, 0x0000DEA8, 0x0000000A, 0x0000000A, 0x0000000E, 0x0000000E }, Package (0x06) { 0x000006C1, 0x0000B798, 0x0000000A, 0x0000000A, 0x0000000D, 0x0000000D }, Package (0x06) { 0x0000063C, 0x0000A7F8, 0x0000000A, 0x0000000A, 0x0000000C, 0x0000000C } }) Method (_PPC, 0, NotSerialized) { Return (Zero) } } Processor (\_PR.CPU1, 0x01, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU2, 0x02, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU3, 0x03, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU4, 0x04, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU5, 0x05, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU6, 0x06, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU7, 0x07, 0x00000410, 0x06) { Alias (\_PR.CPU0._CST, _CST) Alias (\_PR.CPU0._PCT, _PCT) Alias (\_PR.CPU0._PSS, _PSS) Alias (\_PR.CPU0._PPC, _PPC) } Processor (\_PR.CPU8, 0x08, 0x00000410, 0x06) {} Processor (\_PR.CPU9, 0x09, 0x00000410, 0x06) {} Processor (\_PR.CPUA, 0x0A, 0x00000410, 0x06) {} Processor (\_PR.CPUB, 0x0B, 0x00000410, 0x06) {} Processor (\_PR.CPUC, 0x0C, 0x00000410, 0x06) {} Processor (\_PR.CPUD, 0x0D, 0x00000410, 0x06) {} Processor (\_PR.CPUE, 0x0E, 0x00000410, 0x06) {} Processor (\_PR.CPUF, 0x0F, 0x00000410, 0x06) {} } The extra bit is at the end of the second box. It's not quite the same as the original code, it's for CPU8-CPUF. Ryan! That extra bit (CPU8 through CPUF) is not in my instructions to add because it's already there in your dsdt.dsl derived from UD5 BIOS F9e and newer (or similar versions for Extreme, UD4 and 3).The currently available CPUs only have 4 cores (8 logical with multi threading), so that's why you see the CPU8 through CPUF (8 through 15) disabled in kernel.log; Jan 16 13:45:39 localhost kernel[0]: AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled Jan 16 13:45:39 localhost kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=2 Enabled Jan 16 13:45:39 localhost kernel[0]: AppleACPICPU: ProcessorId=2 LocalApicId=4 Enabled Jan 16 13:45:39 localhost kernel[0]: AppleACPICPU: ProcessorId=3 LocalApicId=6 Enabled Jan 16 13:45:39 localhost kernel[0]: AppleACPICPU: ProcessorId=4 LocalApicId=1 Enabled Jan 16 13:45:39 localhost kernel[0]: AppleACPICPU: ProcessorId=5 LocalApicId=3 Enabled Jan 16 13:45:39 localhost kernel[0]: AppleACPICPU: ProcessorId=6 LocalApicId=5 Enabled Jan 16 13:45:39 localhost kernel[0]: AppleACPICPU: ProcessorId=7 LocalApicId=7 Enabled Jan 16 13:45:39 localhost kernel[0]: AppleACPICPU: ProcessorId=8 LocalApicId=8 Disabled Jan 16 13:45:39 localhost kernel[0]: AppleACPICPU: ProcessorId=9 LocalApicId=9 Disabled Jan 16 13:45:39 localhost kernel[0]: AppleACPICPU: ProcessorId=10 LocalApicId=10 Disabled Jan 16 13:45:39 localhost kernel[0]: AppleACPICPU: ProcessorId=11 LocalApicId=11 Disabled Jan 16 13:45:39 localhost kernel[0]: AppleACPICPU: ProcessorId=12 LocalApicId=12 Disabled Jan 16 13:45:39 localhost kernel[0]: AppleACPICPU: ProcessorId=13 LocalApicId=13 Disabled Jan 16 13:45:39 localhost kernel[0]: AppleACPICPU: ProcessorId=14 LocalApicId=14 Disabled Jan 16 13:45:39 localhost kernel[0]: AppleACPICPU: ProcessorId=15 LocalApicId=15 Disabled Link to comment Share on other sites More sharing options...
ryansimms Posted January 16, 2010 Share Posted January 16, 2010 That extra bit (CPU8 through CPUF) is not in my instructions to add because it's already there in your dsdt.dsl derived from UD5 BIOS F9e and newer (or similar versions for Extreme, UD4 and 3).The currently available CPUs only have 4 cores (8 logical with multi threading), so that's why you see the CPU8 through CPUF (8 through 15) disabled in kernel.log; I have a UD3R with BIOS F8D. Perhaps that's why I didn't have that bit in my original DSDT, although I think my pre-patched DSDT was derived from an earlier bios firmware. Is it important to re-derive my DSDT every time I update my BIOS firmware? Ryan! Link to comment Share on other sites More sharing options...
d00d Posted January 16, 2010 Author Share Posted January 16, 2010 I have a UD3R with BIOS F8D. Perhaps that's why I didn't have that bit in my original DSDT, although I think my pre-patched DSDT was derived from an earlier bios firmware. Is it important to re-derive my DSDT every time I update my BIOS firmware? Ryan! It may be important to start with a clean dsdt.dsl derived from a new BIOS.For example, UD5 F9m added DVID, which results in additional code in the dsdt.dsl derived from it. Using a DSDT derived from an earlier BIOS conditionally caused a KP on resume from S3 sleep (Update 1 and 2 in post 1). Save the clean dsdt.dsl derived from each new BIOS that you use. If the clean dsdt.dsl derived from the next new BIOS is the same, then no modification to the DSDT is needed. Also keep in mind that a BIOS setting could change the derived dsdt.dsl. However, I've only seen the sleep setting do this so far. When you dump a BIOS set to S1(POS) sleep you get; Name (\_S1, Package (0x04) and Name (\SS3, Package (0x04) When you dump a BIOS set to S3(STR) sleep you get; Name (\SS1, Package (0x04) and Name (\_S3, Package (0x04) Link to comment Share on other sites More sharing options...
ryansimms Posted January 17, 2010 Share Posted January 17, 2010 It may be important to start with a clean dsdt.dsl derived from a new BIOS.For example, UD5 F9m added DVID, which results in additional code in the dsdt.dsl derived from it. Using a DSDT derived from an earlier BIOS conditionally caused a KP on resume from S3 sleep (Update 1 and 2 in post 1). Save the clean dsdt.dsl derived from each new BIOS that you use. If the clean dsdt.dsl derived from the next new BIOS is the same, then no modification to the DSDT is needed. Also keep in mind that a BIOS setting could change the derived dsdt.dsl. However, I've only seen the sleep setting do this so far. When you dump a BIOS set to S1(POS) sleep you get; Name (\_S1, Package (0x04) and Name (\SS3, Package (0x04) When you dump a BIOS set to S3(STR) sleep you get; Name (\SS1, Package (0x04) and Name (\_S3, Package (0x04) Thanks for the info. What is the best way to get a DSDT dump? I've read about using a Ubuntu Live CD, but is there a way to do it from OSX? I don't have access to Windows. I get a kernel panic after sleep in 32 bit mode, so maybe I need a new DSDT dump and the latest UD3R BIOS update. Thanks, Ryan! Link to comment Share on other sites More sharing options...
d00d Posted January 17, 2010 Author Share Posted January 17, 2010 Thanks for the info. What is the best way to get a DSDT dump? I've read about using a Ubuntu Live CD, but is there a way to do it from OSX? I don't have access to Windows. I get a kernel panic after sleep in 32 bit mode, so maybe I need a new DSDT dump and the latest UD3R BIOS update. Thanks, Ryan! Near the top of post 1 I explain how to extract a clean dsdt.dsl from BIOS within OS X. Link to comment Share on other sites More sharing options...
ryansimms Posted January 17, 2010 Share Posted January 17, 2010 Near the top of post 1 I explain how to extract a clean dsdt.dsl from BIOS within OS X. So I upgraded to F8i and got myself a new DSDT file. DSDTSE was giving me compile errors, so I just used Digital Dreamer's script to get a new one, which worked fine. My DSDT was significantly different from the one I'd been using since I got the motherboard. It now looks pretty much like the "original" code you have in post #1. I've applied all patched except for 14 & 15 (I have ALC888 sound and idle sleep has been working for me) I still get the same KP's after wake from sleep when in 32 bit though. It's not a big deal, because everything seems to work fine in 64 bit mode, but it would be nice if I knew it was working. Also, It seems that my apple bluetooth mighty mouse (with belkin dongle) is a little less responsive now and the cursor lags a bit. My spare usb mouse works fine. Any ideas? Ryan! Link to comment Share on other sites More sharing options...
ryansimms Posted January 17, 2010 Share Posted January 17, 2010 One more issue. At startup, I'm now getting this error which I wasn't getting before: 1/17/10 Jan 17, 1:36:13 AM kernel akeSMC: key info not found VS6C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VS8C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found Vp1C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VG1C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VS1C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VSAC, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VM0S, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found Vp3C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VSCC, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VS3C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VP0R, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VMBS, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VSEC, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VCAC, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VS5C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VS7C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found Vp0C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VG0C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VS0C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VS9C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found Vp2C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VSBC, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VS2C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VN0C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VMAS, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VSDC, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VS4C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found VC0C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found PG0C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found PG1C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found PN2R, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found PM2S, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found PP0R, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found PC0C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found PM1S, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found PN0C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found PN1R, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found PN0R, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found PCBC, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found PCAC, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found PMBS, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found Pp0C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found Pp1C, length - 6 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found PMAS, length - 6 I'm not sure what this means or if it's something to worry about or how to fix it. Thanks, Ryan! Link to comment Share on other sites More sharing options...
d00d Posted January 17, 2010 Author Share Posted January 17, 2010 One more issue. At startup, I'm now getting this error which I wasn't getting before:... 1/17/10 Jan 17, 1:36:13 AM kernel FakeSMC: key info not found PMAS, length - 6 I'm not sure what this means or if it's something to worry about or how to fix it. Thanks, Ryan! This was discussed a few posts back. Link to comment Share on other sites More sharing options...
LocusOfControl Posted January 17, 2010 Share Posted January 17, 2010 So I upgraded to F8i and got myself a new DSDT file. DSDTSE was giving me compile errors, so I just used Digital Dreamer's script to get a new one, which worked fine. My DSDT was significantly different from the one I'd been using since I got the motherboard. It now looks pretty much like the "original" code you have in post #1. I've applied all patched except for 14 & 15 (I have ALC888 sound and idle sleep has been working for me) I still get the same KP's after wake from sleep when in 32 bit though. It's not a big deal, because everything seems to work fine in 64 bit mode, but it would be nice if I knew it was working. Also, It seems that my apple bluetooth mighty mouse (with belkin dongle) is a little less responsive now and the cursor lags a bit. My spare usb mouse works fine. Any ideas? Ryan! Magic mouse works perfectly on f9m for me with ATI 4870. I previously had an Nvidia card with leopard and I had lags with a USB mouse all the time. Since switching to ATI no problem. Only problem I have is that if I activate wake using Bluetooth it prevents idle sleep. Does this happen with mighty mouse? I find if I switch to a usb mouse that it zooms around really fast and jerky, have you tried resetting your mouse tracking settings etc? I haven't found anything in DSDT that deals with Bluetooth. Out of curiosity what do you get if you type nvram -p in terminal? I get EFIBluetoothDelay %b8%0b , just curious as to where this comes from? Link to comment Share on other sites More sharing options...
aikidoka25 Posted January 17, 2010 Share Posted January 17, 2010 ...Also keep in mind that a BIOS setting could change the derived dsdt.dsl. ,,, should i regenerate the dsdt if the base clock changed? i tried to do an OC by increasing the Base Clock from 130 to 140. but it seems it breaks the resume, the screen just stays black. in the end i restored the original clock 130 and resume works again. Link to comment Share on other sites More sharing options...
d00d Posted January 17, 2010 Author Share Posted January 17, 2010 should i regenerate the dsdt if the base clock changed? i tried to do an OC by increasing the Base Clock from 130 to 140. but it seems it breaks the resume, the screen just stays black. in the end i restored the original clock 130 and resume works again. Changing BCLK doesn't change the derived dsdt.dsl, you can see this yourself.The complete quote is; Also keep in mind that a BIOS setting could change the derived dsdt.dsl. However, I've only seen the sleep setting do this so far. Link to comment Share on other sites More sharing options...
ryansimms Posted January 17, 2010 Share Posted January 17, 2010 Magic mouse works perfectly on f9m for me with ATI 4870. I previously had an Nvidia card with leopard and Ihad lags with a USB mouse all the time. Since switching to ATI no problem. Only problem I have is that if I activate wake using Bluetooth it prevents idle sleep. Does this happen with mighty mouse? I find if I switch to a usb mouse that it zooms around really fast and jerky, have you tried resetting your mouse tracking settings etc? I haven't found anything in DSDT that deals with Bluetooth. Out of curiosity what do you get if you type nvram -p in terminal? I get EFIBluetoothDelay %b8%0b , just curious as to where this comes from? I get: platform-uuid %00%00%00%00%00%00%10%00%80%00%00$%1d%15%f7%94 EFIBluetoothDelay %b8%0b It's only laggy sometimes, so maybe I'm just being overly critical. But it definitely seems like it's worse now than before. I'm going to try to revert back to F8D BIOS (UD3R) and see if that helps. This was discussed a few posts back. oof, sorry 'bout that. I've been following this thread, but I missed that. I try not to clutter the thread if I can. Ryan! Link to comment Share on other sites More sharing options...
LocusOfControl Posted January 17, 2010 Share Posted January 17, 2010 I get:platform-uuid %00%00%00%00%00%00%10%00%80%00%00$%1d%15%f7%94 EFIBluetoothDelay %b8%0b Ryan! A curiosity, I've occasionally wondered about this, I don't get platform-uuid. Wonder if this is used for anything or just an anomaly on hacks? Link to comment Share on other sites More sharing options...
ryansimms Posted January 17, 2010 Share Posted January 17, 2010 I get:platform-uuid %00%00%00%00%00%00%10%00%80%00%00$%1d%15%f7%94 EFIBluetoothDelay %b8%0b It's only laggy sometimes, so maybe I'm just being overly critical. But it definitely seems like it's worse now than before. I'm going to try to revert back to F8D BIOS (UD3R) and see if that helps. Ryan! I figured out the bluetooth problem. I had moved the dongle from my keyboard to the back of the computer around the same time I did the BIOS/DSDT upgrades and that's when it started being laggy. All I had to do to fix it was to move it back. I guess there's a whole lotta mojo in the air over there that makes bluetooth queazy. Also, for anyone who's annoyed by FakeSMC's "key info not found" cosmetic errors, the simple fix is to open up info.plist inside of FakeSMC.kext and change the "true" to a "false" under the debug key to keep the kext from reporting those errors. Netkas added this functionality in v2.5. I may be jinxing myself by saying this, but I think my system is 100% functional. EDIT: except sleep in 32-bit mode, but 64-bit is great. Ryan! Link to comment Share on other sites More sharing options...
Recommended Posts