juanerson Posted June 15, 2011 Share Posted June 15, 2011 Hi, I find some information from a RU site about battery, look this screenshot:It seems the battery dependency have changed since Lion, I see he edits the DSDT, IOPCIFamily.kext, change the Mac Model, also use VoodooBattery to meter. But no more details. jp1.tiff Definitely that's right... Dependencies... and I am almost sure we need the proper DSDT fix for our buggy battery code, because should works, from I know even using AppleACPIBatteryManager. I did read some successful reports about it. BTW, please Russian speakers friends here... we need the .zip. This is the original link to the thread: courtesy applelife.ru And this translated to English (thanks google). Thanks. Link to comment Share on other sites More sharing options...
Zprood Posted June 16, 2011 Share Posted June 16, 2011 Definitely that's right... Dependencies... and I am almost sure we need the proper DSDT fix for our buggy battery code, because should works, from I know even using AppleACPIBatteryManager. I did read some successful reports about it. BTW, please Russian speakers friends here... we need the .zip. This is the original link to the thread: courtesy applelife.ru And this translated to English (thanks google). Thanks. Actually, I have test the .zip file but get KP, I mean we should correct the dsdt first, here the file. Batary.zip Link to comment Share on other sites More sharing options...
juanerson Posted June 16, 2011 Share Posted June 16, 2011 Actually, I have test the .zip file but get KP, I mean we should correct the dsdt first, here the file.Batary.zip Thank You Very Much... I will do some tests. Ah, almost forget... about your question here, IMHO that's the very poor graphic driver, I have no doubt... and not related to USB ports... because I have Lion on a external USB HDD, so please look booting into 64 Bit (just vga support), the mouse/pointer lag disappear if the x3100 driver is not loaded. Link to comment Share on other sites More sharing options...
Zprood Posted June 16, 2011 Share Posted June 16, 2011 Thank You Very Much... I will do some tests. Ah, almost forget... about your question here, IMHO that's the very poor graphic driver, I have no doubt... and not related to USB ports... because I have Lion on a external USB HDD, so please look booting into 64 Bit (just vga support), the mouse/pointer lag disappear if the x3100 driver is not loaded. Yeah, I have tested under the 64bit without the mouse move issue. So the graphics drivers should be updated again before release GM version. BTW I just update several hours ago with first update of DP4 and see the drivers are changed but it still exists. Link to comment Share on other sites More sharing options...
juanerson Posted June 18, 2011 Share Posted June 18, 2011 DP4 Update 11A494a I feel is a little bit better in graphics performance on my machine. So, IOGraphicsFamily.kext was updated but the AppleIntelGMAX3100 drivers group is the same version from my USB clean installation of DP4 11A480b. Link to comment Share on other sites More sharing options...
mirzab Posted June 22, 2011 Share Posted June 22, 2011 Hello to everyone! This is my first post here, and i want to say thank you for very useful information about OSX on 6720s. I'm new in OSX,so i followed everything form the first post and i had done it without any problems. I updated my BIOS with SLIC 2.1,used bootdisc and 10.6.3. retail,everything was ok but there's error message about APPLEACPIPE.kext when install kext package. Also i have Intel wireless so it's not working. My question is did i miss anything and what does that kext is used for. Also i would like to know what program is used to monitor temperature, and how to be sure that everything is ok with thermal control and sleep. Sorry for al these question but i'm newby and really would like to have osx on my 6720s. My processor is DualCore T2310 1,46GHz Thank you Link to comment Share on other sites More sharing options...
ThirdSmile Posted June 24, 2011 Share Posted June 24, 2011 I have updated to 10.6.8. After update I have problem with wireless(it seams that problem was in configd plug-in /System/Library/SystemConfiguration/Apple80211Monitor.bundle crashes).. The solution for me was to replace it with previous one(from 10.6.7) - now everything working. Probably downgrade of Apple80211Monitor is not better solution, so I have attached crash report and part of log - maybe someone can suggest other solution. Console messages(when configd crashes): Jun 24 12:45:11 laptop com.apple.ReportCrash.Root[334]: 2011-06-24 12:45:11.809 ReportCrash[334:2a03] Saved crash report for configd[333] version ??? (???) to /Library/Logs/DiagnosticReports/configd_2011-06-24-124511_localhost.crash Jun 24 12:45:21 laptop airportd[30]: SCDynamicStoreCreate[WithOptions] configopen(): (ipc/mig) server died Jun 24 12:45:21 laptop com.apple.launchd[1] (com.apple.configd[336]): Job appears to have crashed: Segmentation fault Jun 24 12:45:21 laptop com.apple.launchd[1] (com.apple.configd): Throttling respawn: Will start in 10 seconds Jun 24 12:45:21 laptop com.apple.ReportCrash.Root[334]: 2011-06-24 12:45:21.929 ReportCrash[334:1407] Saved crash report for configd[336] version ??? (???) to /Library/Logs/DiagnosticReports/configd_2011-06-24-124521_localhost.crash Jun 24 12:45:32 laptop airportd[30]: SCDynamicStoreCreate[WithOptions] configopen(): (ipc/mig) server died Jun 24 12:45:32 laptop com.apple.launchd[1] (com.apple.configd[338]): Job appears to have crashed: Segmentation fault Jun 24 12:45:32 laptop com.apple.launchd[1] (com.apple.configd): Throttling respawn: Will start in 10 seconds Jun 24 12:45:32 laptop com.apple.ReportCrash.Root[334]: 2011-06-24 12:45:32.082 ReportCrash[334:4123] Saved crash report for configd[338] version ??? (???) to /Library/Logs/DiagnosticReports/configd_2011-06-24-124532_localhost.crash Jun 24 12:45:42 laptop airportd[30]: SCDynamicStoreCreate[WithOptions] configopen(): (ipc/mig) server died Jun 24 12:45:42 laptop com.apple.launchd[1] (com.apple.configd[340]): Job appears to have crashed: Segmentation fault Jun 24 12:45:42 laptop com.apple.launchd[1] (com.apple.configd): Throttling respawn: Will start in 10 seconds Jun 24 12:45:42 laptop com.apple.ReportCrash.Root[334]: 2011-06-24 12:45:42.289 ReportCrash[334:360b] Saved crash report for configd[340] version ??? (???) to /Library/Logs/DiagnosticReports/configd_2011-06-24-124542_localhost.crash Jun 24 12:45:52 laptop com.apple.launchd[1] (com.apple.configd[342]): Job appears to have crashed: Segmentation fault Jun 24 12:45:52 laptop com.apple.launchd[1] (com.apple.configd): Throttling respawn: Will start in 10 seconds Jun 24 12:45:52 laptop SystemUIServer[175]: SCDynamicStoreCopyValue configget(): (ipc/mig) server died Jun 24 12:45:52 laptop com.apple.ReportCrash.Root[334]: 2011-06-24 12:45:52.500 ReportCrash[334:4627] Saved crash report for configd[342] version ??? (???) to /Library/Logs/DiagnosticReports/configd_2011-06-24-124552_localhost.crash Jun 24 12:46:02 laptop com.apple.launchd[1] (com.apple.configd[344]): Job appears to have crashed: Segmentation fault Jun 24 12:46:02 laptop com.apple.launchd[1] (com.apple.configd): Throttling respawn: Will start in 10 seconds Jun 24 12:46:02 laptop airportd[30]: SCDynamicStoreCreate[WithOptions] configopen(): (ipc/mig) server died Configd crash report: Process: configd [393] Path: /usr/libexec/configd Identifier: configd Version: ??? (???) Code Type: X86-64 (Native) Parent Process: launchd [1] Date/Time: 2011-06-24 12:48:55.737 +0300 OS Version: Mac OS X 10.6.8 (10K540) Report Version: 6 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Crashed Thread: 3 Thread 0: Dispatch queue: com.apple.main-thread 0 libSystem.B.dylib 0x00000001003d3d7a mach_msg_trap + 10 1 libSystem.B.dylib 0x00000001003d43ed mach_msg + 59 2 com.apple.CoreFoundation 0x0000000100087932 __CFRunLoopRun + 1698 3 com.apple.CoreFoundation 0x0000000100086dbf CFRunLoopRunSpecific + 575 4 configd 0x0000000100001d70 server_loop + 72 5 configd 0x000000010000151a main + 2051 6 configd 0x0000000100000d04 start + 52 Thread 1: Dispatch queue: com.apple.libdispatch-manager 0 libSystem.B.dylib 0x00000001003ecc0a kevent + 10 1 libSystem.B.dylib 0x00000001003eeadd _dispatch_mgr_invoke + 154 2 libSystem.B.dylib 0x00000001003ee7b4 _dispatch_queue_invoke + 185 3 libSystem.B.dylib 0x00000001003ee2de _dispatch_worker_thread2 + 252 4 libSystem.B.dylib 0x00000001003edc08 _pthread_wqthread + 353 5 libSystem.B.dylib 0x00000001003edaa5 start_wqthread + 13 Thread 2: 0 libSystem.B.dylib 0x00000001003eda98 start_wqthread + 0 Thread 3 Crashed: 0 com.apple.CoreFoundation 0x0000000100059e00 CFDataGetBytePtr + 80 1 ...temConfiguration.Apple80211 0x0000000100da5d3b deviceNodeForName + 675 2 ...temConfiguration.Apple80211 0x0000000100da689e deviceNodeForName + 3590 3 ...temConfiguration.Apple80211 0x0000000100da7ac2 deviceNodeForName + 8234 4 ...temConfiguration.Apple80211 0x0000000100da8471 ioDriverInit + 1969 5 ...temConfiguration.Apple80211 0x0000000100da59ae start + 72 6 configd 0x0000000100002ca4 callStartFunction + 207 7 com.apple.CoreFoundation 0x0000000100066d6e CFArrayApplyFunction + 222 8 configd 0x0000000100003453 plugin_exec + 1308 9 libSystem.B.dylib 0x000000010040cfd6 _pthread_start + 331 10 libSystem.B.dylib 0x000000010040ce89 thread_start + 13 Thread 4: 0 libSystem.B.dylib 0x00000001004158ba fsync + 10 1 com.apple.SystemConfiguration 0x00000001002e4697 SCPreferencesCommitChanges + 1014 2 ...nfiguration.PowerManagement 0x0000000100d84e50 load + 1645 3 ...nfiguration.PowerManagement 0x0000000100d86365 _io_pm_force_active_settings + 2211 4 libSystem.B.dylib 0x000000010040cfd6 _pthread_start + 331 5 libSystem.B.dylib 0x000000010040ce89 thread_start + 13 Thread 5: com.apple.CFSocket.private 0 libSystem.B.dylib 0x0000000100417932 select$DARWIN_EXTSN + 10 1 com.apple.CoreFoundation 0x00000001000a9498 __CFSocketManager + 824 2 libSystem.B.dylib 0x000000010040cfd6 _pthread_start + 331 3 libSystem.B.dylib 0x000000010040ce89 thread_start + 13 Thread 6: 0 libSystem.B.dylib 0x00000001003d3d7a mach_msg_trap + 10 1 libSystem.B.dylib 0x00000001003d43ed mach_msg + 59 2 com.apple.CoreFoundation 0x0000000100087932 __CFRunLoopRun + 1698 3 com.apple.CoreFoundation 0x0000000100086dbf CFRunLoopRunSpecific + 575 4 com.apple.CoreFoundation 0x0000000100086b46 CFRunLoopRun + 70 5 ...Configuration.PPPController 0x0000000100fca8f5 pppcntl_run_thread + 1595 6 libSystem.B.dylib 0x000000010040cfd6 _pthread_start + 331 7 libSystem.B.dylib 0x000000010040ce89 thread_start + 13 Thread 3 crashed with X86 Thread State (64-bit): rax: 0x0000000000000400 rbx: 0x0000000000000000 rcx: 0x0000000000000050 rdx: 0x0000000000000013 rdi: 0x0000000000000000 rsi: 0x0000000100dbec28 rbp: 0x0000000102180230 rsp: 0x0000000102180220 r8: 0x0000000000000000 r9: 0x0000000102024f20 r10: 0x0000000000000001 r11: 0x0000000000000002 r12: 0x0000000102024920 r13: 0x0000000101829400 r14: 0x0000000100b17f10 r15: 0x0000000100b1bc10 rip: 0x0000000100059e00 rfl: 0x0000000000010283 cr2: 0x0000000000000000 Binary Images: 0x100000000 - 0x100026ff7 configd ??? (???) <754E7289-CEF0-F696-2A99-8F66310FF370> /usr/libexec/configd 0x10003b000 - 0x1001b2fe7 com.apple.CoreFoundation 6.6.5 (550.43) <31A1C118-AD96-0A11-8BDF-BD55B9940EDC> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 0x1002cb000 - 0x10030cfff com.apple.SystemConfiguration 1.10.8 (1.10.2) <78D48D27-A9C4-62CA-2803-D0BBED82855A> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration 0x100330000 - 0x100390fe7 com.apple.framework.IOKit 2.0 (???) <4F071EF0-8260-01E9-C641-830E582FA416> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit 0x1003b4000 - 0x1003cafef libbsm.0.dylib ??? (???) <42D3023A-A1F7-4121-6417-FCC6B51B3E90> /usr/lib/libbsm.0.dylib 0x1003d3000 - 0x100594fef libSystem.B.dylib 125.2.11 (compatibility 1.0.0) <9AB4F1D1-89DC-0E8A-DC8E-A4FE4D69DB69> /usr/lib/libSystem.B.dylib 0x100626000 - 0x100672fff libauto.dylib ??? (???) <F7221B46-DC4F-3153-CE61-7F52C8C293CF> /usr/lib/libauto.dylib 0x10067f000 - 0x10083dfff libicucore.A.dylib 40.0.0 (compatibility 1.0.0) <4274FC73-A257-3A56-4293-5968F3428854> /usr/lib/libicucore.A.dylib 0x1008ac000 - 0x100962ff7 libobjc.A.dylib 227.0.0 (compatibility 1.0.0) <03140531-3B2D-1EBA-DA7F-E12CC8F63969> /usr/lib/libobjc.A.dylib 0x100976000 - 0x100987ff7 libz.1.dylib 1.2.3 (compatibility 1.0.0) <97019C74-161A-3488-41EC-A6CA8738418C> /usr/lib/libz.1.dylib 0x10098c000 - 0x100a09fef libstdc++.6.dylib 7.9.0 (compatibility 7.0.0) <35ECA411-2C08-FD7D-11B1-1B7A04921A5C> /usr/lib/libstdc++.6.dylib 0x100a6a000 - 0x100a6eff7 libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <95718673-FEEE-B6ED-B127-BCDBDB60D4E5> /usr/lib/system/libmathCommon.A.dylib 0x100a71000 - 0x100a7fff7 libkxld.dylib ??? (???) <8145A534-95CC-9F3C-B78B-AC9898F38C6F> /usr/lib/system/libkxld.dylib 0x100ae7000 - 0x100ae7fff com.apple.SystemConfiguration.wwanConfig 2.0.4 (2.0.4b0) <0EC49EE8-AC06-CC03-8359-44B2195C5F2F> /System/Library/SystemConfiguration/wwanConfig.bundle/Contents/MacOS/wwanConfig 0x100aeb000 - 0x100aecfff com.apple.print.notification 6.6 (304.9) <5A0639D4-3D0D-C320-563E-925878AF5AC4> /System/Library/SystemConfiguration/PrinterNotifications.bundle/Contents/MacOS/PrinterNotifications 0x100af1000 - 0x100af7ff7 com.apple.DiskArbitration 2.3 (2.3) <857F6E43-1EF4-7D53-351B-10DE0A8F992A> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration 0x100d83000 - 0x100d94ff7 com.apple.SystemConfiguration.PowerManagement 160.0.0 (160.0.0) <20F4D79D-1834-14C9-650C-C4B588B9E1B9> /System/Library/SystemConfiguration/PowerManagement.bundle/Contents/MacOS/PowerManagement 0x100d9f000 - 0x100da0fff com.apple.SystemConfiguration.Bluetooth 2.4.5 (2.4.5f3) <8C8F39C9-C2A5-B2F1-6ED2-DE89662F6363> /System/Library/SystemConfiguration/Bluetooth.bundle/Contents/MacOS/Bluetooth 0x100da5000 - 0x100dc5ff7 com.apple.SystemConfiguration.Apple80211 6.2.5 (625.6) <1AB7CA40-9ED6-C2C1-E04C-B2E2E4480066> /System/Library/SystemConfiguration/Apple80211Monitor.bundle/Contents/MacOS/Apple80211Monitor 0x100dd1000 - 0x100dd6fff com.apple.SystemConfiguration.EAPOLController 10.0.1 (1.0) <C2B446E4-F556-93B9-184B-F5E6A1A4DA8C> /System/Library/SystemConfiguration/EAPOLController.bundle/Contents/MacOS/EAPOLController 0x100ddc000 - 0x100de9fff com.apple.SystemConfiguration.IP6Configuration 10.1.1 (10.1.1) <A2C6326E-C52C-C337-B98F-8CFEFD3E8D2D> /System/Library/SystemConfiguration/IP6Configuration.bundle/Contents/MacOS/IP6Configuration 0x100df1000 - 0x100df6fef libipsec.A.dylib 300.0.0 (compatibility 1.0.0) <6912BCE9-D6C3-A964-0365-D50915AFE78B> /usr/lib/libipsec.A.dylib 0x100f83000 - 0x100faaff7 com.apple.SystemConfiguration.IPConfiguration 10.1.2 (???) <B55DE3D1-AB1F-320E-EA78-C179A2C95B6B> /System/Library/SystemConfiguration/IPConfiguration.bundle/Contents/MacOS/IPConfiguration 0x100fb8000 - 0x100fe1fff com.apple.SystemConfiguration.PPPController 1.5 (1.5) <7A34D8E1-6EE2-AFBE-CC7A-4D91276AF7EA> /System/Library/SystemConfiguration/PPPController.bundle/Contents/MacOS/PPPController 0x102183000 - 0x10240cff7 com.apple.security 6.1.2 (55002) <4419AFFC-DAE7-873E-6A7D-5C9A5A4497A6> /System/Library/Frameworks/Security.framework/Versions/A/Security 0x102504000 - 0x1025bdfff libsqlite3.dylib 9.6.0 (compatibility 9.0.0) <2C5ED312-E646-9ADE-73A9-6199A2A43150> /usr/lib/libsqlite3.dylib 0x1025cd000 - 0x102603ff7 com.apple.framework.Apple80211 6.2.5 (625.6) <B67C7A65-E4FB-4419-3F31-4482E17EF203> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211 0x7fff5fc00000 - 0x7fff5fc3be0f dyld 132.1 (???) <29DECB19-0193-2575-D838-CF743F0400B2> /usr/lib/dyld 0x7fffffe00000 - 0x7fffffe01fff libSystem.B.dylib ??? (???) <9AB4F1D1-89DC-0E8A-DC8E-A4FE4D69DB69> /usr/lib/libSystem.B.dylib Link to comment Share on other sites More sharing options...
BlackCH Posted June 24, 2011 Author Share Posted June 24, 2011 I just updated from apple´s server. No problems so far. I have +200 score points with geekbench after the update I´ve reinstalled the whole system a couple of days ago, cos there were a lot of bugs going on: wireless lockups, firewire card not working sometimes, some audio crackles here and there, etc. I guess after two years of use the system gets wore out... even osx Now everything seems to be working fine. Link to comment Share on other sites More sharing options...
juanerson Posted June 24, 2011 Share Posted June 24, 2011 I just updated from apple´s server. No problems so far. I have +200 score points with geekbench after the update I´ve reinstalled the whole system a couple of days ago, cos there were a lot of bugs going on: wireless lockups, firewire card not working sometimes, some audio crackles here and there, etc. I guess after two years of use the system gets wore out... even osx Now everything seems to be working fine. Hi Friend, +200 points in geekbench?... Then, I almost sure they are broken your C-States to hardware level (not IOReg)... So, more heat near to +5C. BTW, if you notice all THIS, therefore please type in terminal: ioreg -lw0 | grep AICPMVers But the output is not real/true support. I think is a problem between Chameleon + Update + SSDT. Please see my new version of the legacy injector for speedstep, has some effective changes... check "info.plist" inside. Also, please see my smbios.plist and c.a.B.p for better General results-performance on my system. Attached my DSDT (experimental) JUST FOR REFERENCE about my own C-States addition (for my CPU), and other things on GFX0, SBUS, Scope PR, etc. Alternatives to fix more heat problem: GenerateCStates in c.a.B.p OR inject in DSDT extracted the custom table SSDT-5 (from chameleon) using DSDTSE. The reason why, both native DSDT caller method (CSTH) and native SSDT table (_CST) not worked here. Just want to say I am using Chameleon 2RC5 rev1037, because C2RC5 r755diffv7 has full hardware support (and +150 points) BUT have not Prelinked kernel option. Please report. Good Luck. My terminal output after patch my dsdt. Very different to IOReg w/new legacy, to the right: carpeta_sin_t__tulo.zip Link to comment Share on other sites More sharing options...
yushir Posted June 24, 2011 Share Posted June 24, 2011 Hi Friend, +200 points in geekbench?... Then, I almost sure they are broken your C-States to hardware level (not IOReg)... So, more heat near to +5C. BTW, if you notice all THIS, therefore please type in terminal: ioreg -lw0 | grep AICPMVers But the output is not real/true support. I think is a problem between Chameleon + Update + SSDT. Please see my new version of the legacy injector for speedstep, has some effective changes... check "info.plist" inside. Also, please see my smbios.plist and c.a.B.p for better General results-performance on my system. Attached my DSDT (experimental) JUST FOR REFERENCE about my own C-States addition (for my CPU), and other things on GFX0, SBUS, Scope PR, etc. Alternatives to fix more heat problem: GenerateCStates in c.a.B.p OR inject in DSDT extracted the custom table SSDT-5 (from chameleon) using DSDTSE. The reason why, both native DSDT caller method (CSTH) and native SSDT table (_CST) not worked here. Just want to say I am using Chameleon 2RC5 rev1037, because C2RC5 r755diffv7 has full hardware support (and +150 points) BUT have not Prelinked kernel option. Please report. Good Luck. My terminal output after patch my dsdt. Very different to IOReg w/new legacy, to the right: Prelinked kernel isn't necessary, i still prefer a higher rate at benchmarking & performance than being able to load compiled kernels. That's why i've still got a leopard install on my laptop . I'll try 10.6.8 today with CStates injection, shall it be better. Link to comment Share on other sites More sharing options...
juanerson Posted June 25, 2011 Share Posted June 25, 2011 Prelinked kernel isn't necessary, i still prefer a higher rate at benchmarking & performance than being able to load compiled kernels. That's why i've still got a leopard install on my laptop . I'll try 10.6.8 today with CStates injection, shall it be better. Sorry, that's a wrong argument IMHO. First, Prelinked kernel is the way to go for Lion cache. Second, C2RC5 r755diffv7 + 10.6.8 = audio stuttering and hight temperatures because C-states, and third even patching CST in DSDT or GenerateCStates in c.a.B.p will down your geekbench score. So, the last one its my option, because I prefer stability my friend. This is the extracted code from my 6720s BIOS, the whole C-States SSDT table using AIDA64 (Everest) in windows. Then, we can compare with yours own tables to find differences (textwrangler is useful for that). I think can be Standard for all CPUs. In this case, just copy/paste to add/apply the DSDT patch, properly to be on two sections as follow: 1) Add the line: External (CFGD) 2) Add on both cores: Processor (CPU0, 0x01, 0x00001010, 0x06) Method (ACST, 0, NotSerialized) { Return (Package (0x06) { One, 0x04, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, One, One, 0x03E8 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000010, // Address 0x01, // Access Size ) }, 0x02, One, 0x01F4 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000030, // Address 0x03, // Access Size ) }, 0x04, 0x39, 0x64 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000030, // Address 0x03, // Access Size ) }, 0x05, 0x39, 0x64 } }) } Method (_CST, 0, NotSerialized) { If (LAnd (And (CFGD, 0x01000000), LNot (And (PDC0, 0x10 )))) { Return (Package (0x02) { One, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x00, // Bit Width 0x00, // Bit Offset 0x0000000000000000, // Address ,) }, One, 0x9D, 0x03E8 } }) } If (LAnd (And (CFGD, 0x00200000), And (PDC0, 0x0200))) { If (And (CFGD, 0x0200)) { Return (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 (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000010, // Address 0x01, // Access Size ) }, 0x02, One, 0x01F4 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000050, // Address 0x03, // Access Size ) }, 0x03, 0xA2, 0x64 } }) } If (And (CFGD, 0x80)) { Return (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 (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000010, // Address 0x01, // Access Size ) }, 0x02, One, 0x01F4 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000030, // Address 0x03, // Access Size ) }, 0x03, 0x39, 0x64 } }) } If (And (CFGD, 0x40)) { Return (Package (0x03) { 0x02, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, One, One, 0x03E8 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000020, // Address 0x03, // Access Size ) }, 0x02, 0x11, 0xFA } }) } If (And (CFGD, 0x20)) { Return (Package (0x03) { 0x02, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, One, One, 0x03E8 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000010, // Address 0x01, // Access Size ) }, 0x02, One, 0x01F4 } }) } Return (Package (0x02) { One, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, One, One, 0x03E8 } }) } If (LAnd (And (CFGD, 0x00200000), And (PDC0, 0x0100))) { If (And (CFGD, 0x0200)) { Return (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 0x0000000000001014, // Address ,) }, 0x02, One, 0x01F4 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000001018, // Address ,) }, 0x03, 0xA2, 0x64 } }) } If (And (CFGD, 0x80)) { Return (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 0x0000000000001014, // Address ,) }, 0x02, One, 0x01F4 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000001016, // Address ,) }, 0x03, 0x39, 0x64 } }) } If (And (CFGD, 0x40)) { Return (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 0x0000000000001014, // Address ,) }, 0x02, One, 0x01F4 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000001015, // Address ,) }, 0x03, 0x11, 0xFA } }) } If (And (CFGD, 0x20)) { Return (Package (0x03) { 0x02, 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 0x0000000000001014, // Address ,) }, 0x02, One, 0x01F4 } }) } Return (Package (0x02) { One, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, One, One, 0x03E8 } }) } If (And (CFGD, 0x0200)) { Return (Package (0x04) { 0x03, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x00, // Bit Width 0x00, // Bit Offset 0x0000000000000000, // Address ,) }, One, One, 0x03E8 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000001014, // Address ,) }, 0x02, One, 0x01F4 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000001018, // Address ,) }, 0x03, 0xA2, 0x64 } }) } If (And (CFGD, 0x80)) { Return (Package (0x04) { 0x03, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x00, // Bit Width 0x00, // Bit Offset 0x0000000000000000, // Address ,) }, One, One, 0x03E8 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000001014, // Address ,) }, 0x02, One, 0x01F4 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000001016, // Address ,) }, 0x03, 0x39, 0x64 } }) } If (And (CFGD, 0x40)) { Return (Package (0x04) { 0x03, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x00, // Bit Width 0x00, // Bit Offset 0x0000000000000000, // Address ,) }, One, One, 0x03E8 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000001014, // Address ,) }, 0x02, One, 0x01F4 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000001015, // Address ,) }, 0x03, 0x11, 0xFA } }) } If (And (CFGD, 0x20)) { Return (Package (0x03) { 0x02, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x00, // Bit Width 0x00, // Bit Offset 0x0000000000000000, // Address ,) }, One, One, 0x03E8 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000001014, // Address ,) }, 0x02, One, 0x01F4 } }) } Return (Package (0x02) { One, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x00, // Bit Width 0x00, // Bit Offset 0x0000000000000000, // Address ,) }, One, One, 0x03E8 } }) } Processor (CPU1, 0x02, 0x00001010, 0x06) Method (_CST, 0, NotSerialized) { If (LAnd (And (CFGD, 0x01000000), LNot (And (PDC1, 0x10 )))) { Return (Package (0x02) { One, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x00, // Bit Width 0x00, // Bit Offset 0x0000000000000000, // Address ,) }, One, 0x9D, 0x03E8 } }) } Return (^^CPU0._CST ()) } So, I prefer don't worry about SSDT /C-states problems in the future. Note: For OS X compatibility I adapted those two sections accord to MacBook4,1 tables, I mean a little changes to successfully load, because our factory CST tables are so closer but not 100% natives (structural speaking). Please take a look. For those interested, I Attached all my tables (2009) + MB4,1 and MB3,1 ssdt tables to compare. EDITED: Confirmed after upgrade to T8100 CPU, and extracted again all the SSDT tables from windows (AIDA64), are exactly the same SSDT tables with the prior T5470. So, I think (almost sure) it can be used the above posted code for full C-States support to every CPU from DSDT. No need chameleon injection, or even from the legacy speedstep injector, resulting in the same Legacy_SpeedStep.kext for MB3,1 and MB4,1 because the CST section is the ONLY difference (using texwrangler) between both apple profiles. SSDT.zip Link to comment Share on other sites More sharing options...
XvonabuR Posted June 25, 2011 Share Posted June 25, 2011 Hi! Can anybody help me with the Snow Leopard on my HP 550 (notebook details in my signature)? I've installed Snow Leopard 10.6.2 (made by dan1234) + 10.6.7 combo update + BootCD 0.3. Everything works well, except the powermanagment (it was an ACPIEXEC.kext error during the kexts installation). I tried nullpupowermanagement.kext and it works. As far as I understand, it isn't the best solution for my problem. Any other ideas/manuals ? Thanks in advance and sorry for my english. Link to comment Share on other sites More sharing options...
BlackCH Posted June 25, 2011 Author Share Posted June 25, 2011 Hi Friend, +200 points in geekbench?... Then, I almost sure they are broken your C-States to hardware level (not IOReg)... So, more heat near to +5C. BTW, if you notice all THIS, therefore please type in terminal: ioreg -lw0 | grep AICPMVers Si, despues de algunas pruevas he notado que los pstates cambian constantemente todo el tiempo. He probado algunas de las soluciones que sugieres pero sin exito. Si puedes subir tu "Extra" para ver los archivos y explicar con un poco mas de detalle como lo has solucionado seria genial De momento estoy usando tu nuevo Legacy_Speedstep con las modificaciones del CPU en el DSDT (post 984) y generateCstates=yes en el boot plist. Saludos! Link to comment Share on other sites More sharing options...
juanerson Posted June 25, 2011 Share Posted June 25, 2011 Hola Black, Correcto, exactamente ese es el mal comportamiento, ya que los C-States son los encargados de mantener en calma a los P-States, sin actividad constante, esto se aprecia mejor después de un arranque frío (cold boot). Entonces, con respecto a tus preguntas, la carpeta Extra solo contiene el smbios.plist, c.a.B.p, dsdt.aml y los temas, los cuales subí en el archivo Carpeta_sin_titulo.zip. Todas las extensiones las instalé en /S/L/E... por supuesto, les hice un ajuste al inyector legacy y a otra que no recuerdo en sus info.plist en las líneas finales cambié por ejemplo Safe Boot hacia Root... así cargan sin problemas desde la carpeta principal. También le hice un ajuste a los demonios automatizadores de SleepWatcher para que carguen/descarguen AppleACPIThermal.kext desde /S/L/E, ya sabes que antes y después del sleep, ahorita apuntan hacia /E/E, son detalles, pero importantes para tal función. Te subo mi dsdt.aml (se ve mejor)... y el .dsl por si acaso, con el último ajuste (ayer tarde) de los C-States, con las dos tablas completas (CPU0 es larga) ligeramente modificadas para ser compatibles (allí está el problema de fábrica), creo que dicho código pudiera ser estándar para cualquier CPU, es decir con todos los C-States disponibles para nuestra gama de procesadores soportados, qué opinas?. PERO, y por lo tanto, por favor te pido que las comparares con las tuyas, deben ser las tablas 6 y 7 extraídas con AIDA64. Yo enumeré las mías para no confundirme. En ese sentido, igualmente verás que en la DSDT quité la llamada a las SSDT: Method (CSTH) que funcionó bien hasta 10.6.7. Al inyector le quité la capacidad de generar código erróneo por software, y que ahora el desempeño sea única y directamente a través de hardware. Con los P-States es otra historia. No pude. En otro orden de ideas, también puedes notar que estoy usando la sección gráfica de las MB3,1 y 4,1. De esa forma he suprimido todo el código de la GFX0 nativa y todas sus declaraciones (ver .dsl). Igual hice con la device SBUS para no correr riesgos de que no se están realizando las llamadas correctamente. En fin, quiero tener todo en la DSDT, sin GenerateCStates, ni nada de esos flags innecesarios para nuestras configuraciones santa-rosa. Lástima que no creo que se pueda aplicar el mismo criterio con las zonas térmicas como la dsdt del 2008, o me equivoco? Con eso se podría aplicar tranquilamente los flags DropSSDT=Yes y oemSSDT=No. Por cierto, estoy usando la última rev 1055 de chameleon, porque la r755 fue un experimento de Fabio y nada más, así me lo hizo saber él, a través del cual habilitando IDA, forza al bus a trabajar con la misma frecuencia de la memoria ram (667), y sabemos que no sucede así en windows, ambas son frecuencias dinámicas que dependen del multiplicador (bus ratio) y por ende hacen ajustar al Bus frontal (FSB) para el SpeedStep, por eso el sttutering, porque no hay dinamismo en la memoria según entiendo, no sé si el voltaje también tenga algo que ver, o el mismo kernel vanilla en sí, o tal vez eliminado el P-State de IDA sea una opción. Por mi parte, seguiré haciendo pruebas. Un abrazo. EDITADO: Si bien, en lo cual coincido con el Amigo yushir, debo reconocer que aunque me resulta curioso, y hasta difícil de comprender, que teniendo el código apple de los C-States en el inyector, los mejores resultados en cuanto a Estabilidad y Rendimiento del sistema los obtengo de esta triple combinación: - Legacy SpeedStep ANTERIOR (elimina el sttutering) + - C2RC5r755diffv7 (instalado con Chameleon Wizard método Boot0hfs) + - DSDT (full tablas CST) anexo archivo comprimido. - Nota: Como complemento importante, también pongo adjunto .zip con mis archivos de perfil smbios.plist y c.a.B.p con los ajustes necesarios para dicha "particular" revisión de Chameleon. Que aunque no soporte el prelinked kernel, que tenga fallos y/o inconsistencias con los dos archivos mencionados, que sea experimental entre Anval ACPI loader y chameleon 2RC5r755, a la fuerza o no por culpa de nuestra deficiente BIOS, ... y luego de una búsqueda intensiva, les puedo asegurar que es la única con soporte completo para nuestro hardware, concretamente el multiplicador y por ende el FSB (incluyendo IDA), gracias a Fabio (.: ErmaC :.). Saludos. Archivo_comprimido.zip CABP_SMBIOS_C2RC5r755.zip Link to comment Share on other sites More sharing options...
BlackCH Posted June 26, 2011 Author Share Posted June 26, 2011 Gracias por la respuesta. Estaba utilizando coolbook para monitorear las velocidades del CPU pero despues de varias pruevas creo que no esta reportando los valores correctamente. Ahora estoy utilizando K-Stat-i (una utilidad que viene con FakeSMC) y me muestra que el speedsteping esta funcionando bien. Tambien las temperaturas son buenas. Si el CPU estubiera siempre al maximo como marca coolbook, tendria una temperatura mucho mayor Estoy utilizando la combinacion que describes arriba (que es basicamente la misma que venia usando antes de notar las lecturas de coolbook), aunque no veo ninguna diferencia de performance o temperaturas utilizando mi dsdt anterior. Coolbook reporta diferentes datos segun el dsdt y/o la legacy speedstep kext, pero aun tengo que verificar cuales son los factores Con la combinacion que sugieres coolbook marca siempre maxima velocidad (no IDA) Coolbook reporta la velocidad cambiando constantemente, K-Stat reporta funcionamiento normal de speedstep y las temperaturas ok; ahora un poco mas altas porque aqui ha llegado el verano, pero creo que son normales. De momento no he notado audio stuttering. Seguire haciendo mas pruebas Ok, more news: After using this setup for a while, I started noticing audio problems again: The on board audio device (VoodooHDA 2.7.2 driver) had problems initializing somehow. It will make crackles and cutted audio in the first 5 secs of playing any audio file or system sound. Also logic couldnt set the sample rate correctly and gave synchro errors. This was clearly a FSB problem. So I change chameleon from the C2RC5r755diffv7 version to a newer (trunk 897) just to try and all the audio problems are gone. Off course I loose FSB autodetection and some geekbench points but the audio problem seems to be gone. Theres something definetly wrong with C2RC5r755diffv7 in the way it sets up the FSB for the sistem Speedstep seems to work better with juanerson last CPU definition code (w/ full CST). The CPU seems to idle more. Im monitoring speedstep with K-Stat as coolbook just shows me top speed all the time (and it can´t be true ´cos the temperatures are ok) @juanerson A ti te va bien coolbook? digo, lee las velocidades del cpu correctamente? Yo creo que despues de todo el speedstep no va del todo bien en mi maquina... Link to comment Share on other sites More sharing options...
juanerson Posted June 27, 2011 Share Posted June 27, 2011 @juanersonA ti te va bien coolbook? digo, lee las velocidades del cpu correctamente? Yo creo que despues de todo el speedstep no va del todo bien en mi maquina... Si, Chevere! Me muestra quietos los p-states, y excelente temperatura con mis tablas completas extraídas de los c-states. Sin embargo, debo mencionar que no tuve ningún problema de "velocidades" o "lecturas" hasta la versión 2.20 PERO en la 2.22 me lee valores ajustados (tal vez ficticios) por interpretación de software (creo yo que es un bug) dependiendo de IDA, es decir si quito 1800 mhz en la DSDT entonces toma correctamente 800, 1200 y 1600... pero al agregar IDA (así son mis cuatro p-states de fábrica) coolbook 2.22 me indica cuatro cifras distintas 708, 1062, 1416 y 1593... Los cuales erróneos NO son del todo, ya que resultan exactamente a partir de un mínimo extraño ratio/multiplicador (5) x 177 (el FSB) regulado por chameleon para mi CPU por decirlo de alguna forma, hasta el máximo detectado correctamente (9) para IDA. Esto es lo que me muestra coolbook 2.22..., un jaleo aceptable entre chameleon (cualquier revisión), y su aparente bug: 708 MHz = 177 x 5. Sería 800 MHz si el FSB fuese 200 x 4. Aunque 6 es el mínimo según INTEL... y algo de factor Ram? 1062 Mhz = 177 x 6. Este sería 1200 HHz. 1416 MHz = 177 x 8. Este sería 1600 MHz. 1593 MHz = 177 x 9. Y este sería 1800 MHz. En fin, no creo que sea algo grave. Sólo errores de lectura. Pero jamás de falta de soporte real de P-States y C-States. P.D. Si quieres te adjunto la versión 2.20 de coolbook. Esa es perfecta para mí. No necesito el soporte para Sandy Bridge. EDITADO: Habiendo hecho un ajuste de última hora, luego de mirar el ioreg de una MB4,1, he modificado mi p-state de IDA = 641 (hex) para 1800 Mhz (ver mis p-states) --- y lo cambié a 708 (hex de 1800) y voalá... ya aparecen correctamente todos los p-states en coolbook 2.22 Es decir, por lo visto no se trata de un bug con IDA o si?, sin embargo para darle el beneficio de la duda, "por ahora" me retracto. Repito: en la versión 2.20 no sucede esto. Saludos. Link to comment Share on other sites More sharing options...
BlackCH Posted June 27, 2011 Author Share Posted June 27, 2011 Pues le he dado mil vueltas y no consigo activar speedstep correctamente. IOReg parece normal, pero coolbook (cualquier version) se comporta como he explicado antes. La maquina nunca llega a reposar en una velocidad. Te dejo un par de versiones del DSDT (las dos tienen los CST) y el legacy kext que estoy usando. Si les puedes pegar una ojeada por si ves algo raro te lo agradeceria... Si el problema no esta en estos archivos no se donde podria estar. Alguna idea? Archive.zip Link to comment Share on other sites More sharing options...
juanerson Posted June 27, 2011 Share Posted June 27, 2011 Si son exactamente los mismos archivos que yo conozco y uso perfectamente. Preguntas y recomendaciones si me surgen: 1) Has agregado p-states por tu cuenta? cuántos aparecen de fábrica booteando sin customizar? Yo respeto ese número de p-states, mis cuatro de siempre (incluso en windows), y sólo modifico los voltajes, nada más. 2) Sigues usando el FakeSMC con plugins? Has probado sin dichos plugins? o usar el fakesmc (re-fake) que subí hace algún tiempo, el de netkas con modificaciones para santa-rosa? Ciertamente esa variante de fakesmc + plugins me gustó un rato corto, ya que presentaba problemas en la pantalla al salir de reposo, malas lecturas y retardos generales al salir de reposo. 3) Extrajiste tus tablas SSDT desde windows? Las puedes subir por favor para compararlas con las mías? Junto con tu ioreg. Una sugerencia: Completar el contenido del Método PNOT, mira mi último dsdt, y busca por la palabra MPEN. P.D. Será que te vendría mejor el perfil de MacBook4,1? CPU Penryn. Te recomiendo usar textmate para editar el info.plist. Link to comment Share on other sites More sharing options...
BlackCH Posted June 27, 2011 Author Share Posted June 27, 2011 Ahora viene lo mas extraño. He hecho una nueva instalacion en un disco extra: bootcd 0.3, retail 10.6, 10.6.5 combo update. Todo perfecto (salvo coolbook 2.22 reportando velocidades aproximadas como explicas arriba). Actualize la instalacion con Chameleon trunk 897, fakeSMC rev477 (con plugins), DSDT v0.24 (sin CStates, pero con PStates customizados) y SMBIOS.plist (con perfil MB3,1) y ningun problema. El inyectar los PStates soluciono la lecturas de coolbook. K-Stat-i ahora se condice con coolbook y ademas muestra los voltages correctos. Speedstep funcionando definitivamente. Luego fui aplicando las actualizaciones de sistema una a una 6.6, 6.7 y 6.8. Sin problemas! Speedstep sigue funcionando perfectamente sin modificar el dsdt ni nada. Ahora estoy tratando de comparar las dos instalaciones de 10.6.8 y entender porque una funciona y la otra no. Los kextstat son identicos. Ya seguire experimentando un poco mas a ver si encuentro la causa Por cierto, he usado el codigo de los ssdt de macbook4,1 que tiene el mismo procesador que el mio. Los PStates que utilizo son bastantes mas que los nativos (SSDT), quizas un poco redundante, pero siempre me han funcionado. El macbook tiene 8 Pstates nativos, yo he puesto 10 en mi dsdt... Mystery partially solved: Well, it seems speedstep was activated after all. The cause of the computer not idle´ing was SoundGrid.kext (part of Waves Audio Plugins). Once this kext is removed the machine was able to idle properly. Nevertheless still I cannot explain the erratic behavior of coolbook. Anyway all has been for good: The (second) fresh install is sanppier, cleaner, and everything works as it should. Also I finally managed to create a new working legacy speedstep kext (from the MacBook4,1.plist) specifically for penryn CPUs. Works a lot better for my machine (+50 geekbench score, -2º/3º temperature)... Notice that Im using NATIVE CSTATES from SSDT tables. Only custom PStates injection in the dsdt. For the ones who have upgraded their CPUs with penryn. Here is my speedstep kext: LegacySpeedStepMB42.kext.zip Originally the MacBook 4,1 came with either a T8100 or a T8300, but I think the kext is good for the rest of the penryn 800mhz FSB CPU family. To use this kext the model identifier has to be set as MacBook4,2 within /Extra/smbios.plist Link to comment Share on other sites More sharing options...
ikbenut Posted June 30, 2011 Share Posted June 30, 2011 Hello, Is the dsdt also working on a hp 6710b with T9300 cpu? I have searched the forum back en forth for a solution with my monitor. Resolution must be at 1680x1050 , but everything i do, its black as the night. When i boot from [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] legacy the screen resolution is ok. Link to comment Share on other sites More sharing options...
BlackCH Posted June 30, 2011 Author Share Posted June 30, 2011 Hello, Is the dsdt also working on a hp 6710b with T9300 cpu? I have searched the forum back en forth for a solution with my monitor. Resolution must be at 1680x1050 , but everything i do, its black as the night. When i boot from [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] legacy the screen resolution is ok. I dont think so. Its a different machine You could use it as a reference to patch yours as they have the same chipset Link to comment Share on other sites More sharing options...
juanerson Posted June 30, 2011 Share Posted June 30, 2011 Hello, Is the dsdt also working on a hp 6710b with T9300 cpu? I have searched the forum back en forth for a solution with my monitor. Resolution must be at 1680x1050 , but everything i do, its black as the night. When i boot from [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] legacy the screen resolution is ok. You can take a look to the dsdt posted HERE (free of compilation errors), But please READ that post... because the dsdt is not ready for use without the proper hacks/fixes (essential corrections) which is your job. So, my dsdt.dsl (6720s, 6520s, 550, etc) is a good point of start for reference/guide. Good luck. Important Note: For sure you need the same exactly BIOS VERSION running as Defender666 has installed on his machine. Link to comment Share on other sites More sharing options...
ikbenut Posted July 1, 2011 Share Posted July 1, 2011 Thnx i will give it a try. Your dsdt file from this post is working, but no apple key and sleep, also external screen scrambled. But the resolution was OK Link to comment Share on other sites More sharing options...
juanerson Posted July 1, 2011 Share Posted July 1, 2011 BlackCH, por favor puedes apuntar desde la primera página al DSDT para la 6820s (ATI video). Son tres post con información importante, comenzando la implementación/práctica desde AQUÍ y continúa en los dos comentarios subsiguientes con colaboración de nick (937 y 938)... así como el enlace de descarga (post 939) recomendado para este modelo en particular. P.D. Por cierto, mañana Dios mediante montaré el T8100. Saludos. Link to comment Share on other sites More sharing options...
merlin1201 Posted July 2, 2011 Share Posted July 2, 2011 Hi. Is it posible to make lion work on the 6820s ? And is there a walktrue for dummie's :-) i have osx 10.6.7 working and i wonder is it posible to upgade? grts Merlin/ Link to comment Share on other sites More sharing options...
Recommended Posts