Jump to content

[GUIDE] Snow Leopard with 100% vanilla /S/L/E - Comprehensive DSDT patching guide

Silencers

By Silencers,
in General Discussion

 Share
125 posts in this topic

Recommended Posts

Silencers
Silencers
Posted
  • Author
Posted
0x9 not 0x0 how do i fix that.. {censored} it was 0x0 before i think

I'll check your legacy kext later. Most probably the problem is there, you don't have correct p-limit overrides there.

Link to comment
Share on other sites
00diabolic
00diabolic
Posted
Posted
I'll check your legacy kext later. Most probably the problem is there, you don't have correct p-limit overrides there.

 

I have it copied from the MacBook4,1 almost exactly.. I really wonder what if anything I am missing.. I used beyond compare in win7 to compare them side by side. If you know the app it makes things really easy.. Thats why I really wonder what it could be. Maybe I just dont have it setup right which would make more sense. I had to make some changes to update the osbundle part for 10.6.4 computability and that is where I think I made the mistake if any.

 

I also wonder if the reason I dont have cstateoverride value set to true is because I dont have a cstatedict value in my legacy kext. But as I said before the MBP4,1 does not have a cstatedict at all so that is what I followed instead of having the 1 Cstate C6 turned off as the MB4,1 plist has it. I best match the MB41 plist but dont have the CPU so followed some of the MBP4,1 there. If you have any suggestions I'm open to hear them.

 

Thanks

Link to comment
Share on other sites
Silencers
Silencers
Posted
  • Author
Posted
I have it copied from the MacBook4,1 almost exactly.. I really wonder what if anything I am missing.. I used beyond compare in win7 to compare them side by side. If you know the app it makes things really easy.. Thats why I really wonder what it could be. Maybe I just dont have it setup right which would make more sense. I had to make some changes to update the osbundle part for 10.6.4 computability and that is where I think I made the mistake if any.

It is not enough to simply copy existing model's plist. You need to add a few entries in your legacy kext that are not present in the original. Please check my guide again.

 

You can also compare your legacy kext with my legacy kext, which I attached a few posts ago.

Link to comment
Share on other sites
00diabolic
00diabolic
Posted
Posted
It is not enough to simply copy existing model's plist. You need to add a few entries in your legacy kext that are not present in the original. Please check my guide again.

 

You can also compare your legacy kext with my legacy kext, which I attached a few posts ago.

 

Well I compared my legacy kext to yours and another person and the parts that are needed match. The part I'm referring to is the osbundles and all that that i updated to 10.6.4. All the parts that are in the MB4,1 plist match also. Ive looked at it so much it might help to have another set of eyes to check my work.

 

Did u see anything wrong with it?

Link to comment
Share on other sites
Silencers
Silencers
Posted
  • Author
Posted
Well I compared my legacy kext to yours and another person and the parts that are needed match. The part I'm referring to is the osbundles and all that that i updated to 10.6.4. All the parts that are in the MB4,1 plist match also. Ive looked at it so much it might help to have another set of eyes to check my work.

 

Did u see anything wrong with it?

What exactly did you compare? I have opened your legacy kext, compared to the one I posted here and I immediately spotted a number of differences in the ACPI_SMC_PlatformPlugin section.

 

Where's CStateDemotionDict in your plist? Where's ConfigArray->restart-actions for your model? Where's PLimitDict in your plist? Seriously, did you even look at the stuff I posted?

Link to comment
Share on other sites
00diabolic
00diabolic
Posted
Posted
What exactly did you compare? I have opened your legacy kext, compared to the one I posted here and I immediately spotted a number of differences in the ACPI_SMC_PlatformPlugin section.

 

Where's CStateDemotionDict in your plist? Where's ConfigArray->restart-actions for your model? Where's PLimitDict in your plist? Seriously, did you even look at the stuff I posted?

 

 

Here is the MacBook4,1 plist 10.6.4.. Youl notice that it does NOT have CstateDemotionDict like MacBookPro2,1 does. Restart action also does not exist. There are a few mentions of plimit dict and I do have those in my legacy kext as there in the MB4,1. Believe me I read your guide and I said I had this working perfectly in 10.6.2.. Its just gone haywire since 10.6.4 with my cpu not throttling up and down.

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>IOPlatformThermalProfile</key>
<dict>
	<key>CStateDict</key>
	<dict>
		<key>CSD3</key>
		<dict>
			<key>C6</key>
			<dict>
				<key>enable</key>
				<false/>
			</dict>
		</dict>
		<key>MacBook4,1</key>
		<string>CSD3</string>
	</dict>
	<key>ConfigArray</key>
	<array>
		<dict>
			<key>WWEN</key>
			<true/>
			<key>model</key>
			<string>MacBook4,1</string>
		</dict>
	</array>
	<key>ControlArray</key>
	<array>
		<dict>
			<key>Desc-Key</key>
			<string>CPU_PLIMIT</string>
			<key>IOClass</key>
			<string>AppleSMCControl</string>
			<key>control-flags</key>
			<integer>2</integer>
			<key>control-id</key>
			<integer>10</integer>
			<key>location</key>
			<string>cpu plimit</string>
			<key>type</key>
			<string>smc</string>
		</dict>
		<dict>
			<key>Desc-Key</key>
			<string>CPU_STATE</string>
			<key>IOClass</key>
			<string>AppleSMCControl</string>
			<key>control-flags</key>
			<integer>2</integer>
			<key>control-id</key>
			<integer>13</integer>
			<key>location</key>
			<string>cpu state</string>
			<key>type</key>
			<string>smc</string>
		</dict>
		<dict>
			<key>Desc-Key</key>
			<string>GPU_PLIMIT</string>
			<key>IOClass</key>
			<string>AppleSMCControl</string>
			<key>control-flags</key>
			<integer>2</integer>
			<key>control-id</key>
			<integer>11</integer>
			<key>location</key>
			<string>gpu plimit</string>
			<key>type</key>
			<string>smc</string>
		</dict>
		<dict>
			<key>Desc-Key</key>
			<string>GPU_STATE</string>
			<key>IOClass</key>
			<string>AppleSMCControl</string>
			<key>control-flags</key>
			<integer>2</integer>
			<key>control-id</key>
			<integer>14</integer>
			<key>location</key>
			<string>gpu state</string>
			<key>type</key>
			<string>smc</string>
		</dict>
		<dict>
			<key>Desc-Key</key>
			<string>MEM_PLIMIT</string>
			<key>IOClass</key>
			<string>AppleSMCControl</string>
			<key>control-flags</key>
			<integer>2</integer>
			<key>control-id</key>
			<integer>12</integer>
			<key>location</key>
			<string>mem plimit</string>
			<key>type</key>
			<string>smc</string>
		</dict>
	</array>
	<key>CreationDate</key>
	<string>Tue May 26 15:26:07 PDT 2009</string>
	<key>CtrlLoopArray</key>
	<array>
		<dict>
			<key>Description</key>
			<string>SMC_CPU_Control_Loop</string>
			<key>IOClass</key>
			<string>ACPI_SMC_CtrlLoop</string>
			<key>MetaStateArray</key>
			<array>
				<dict>
					<key>Description</key>
					<string>Normal</string>
				</dict>
				<dict>
					<key>Description</key>
					<string>Reduced Power</string>
				</dict>
				<dict>
					<key>Description</key>
					<string>User Low Power</string>
				</dict>
				<dict>
					<key>Description</key>
					<string>User High Power</string>
				</dict>
			</array>
			<key>PLimitClass</key>
			<array>
				<string>CPU</string>
				<string>Idle</string>
			</array>
			<key>StepDataDict</key>
			<dict>
				<key>MacBook4,1</key>
				<string>SP1</string>
				<key>SP1</key>
				<data>
				qAYAAAAAAAEAAgQAACEAAAACAAAB//8A/wD/
				AP8A/wD/AAYAAP8BAAP/AAsPAAD/AQAD/wAL
				DwAA/wEAA/8ACw8AAP8BAAP/AAsPAAD/AQAD
				/wALDwAA/wEAA/8ACw8AAP8BAAP/AAsPAAD/
				AQAD/wALDwAA/wEAA/8ACw8AAP8BAAP/AAsP
				AAD/AQAD/wALDwAA/wEAA/8ACw8AAP8BAAP/
				AAsPAAD/AQAD/wALDwAA/wEAA/8ACw8AAP8B
				AAP/AAsPAAD/AQAD/wALDwAA/wEAA/8ACw8A
				AP8BAAP/AAsPAAD/AQAD/wALDwAA/wEAA/8A
				Cw8AAP8BAAP/AAsPAAD/AQAD/wALDwAA/wEA
				A/8ACw8AAP8BAAP/AAsPAAD/AQAD/wALDwAA
				/wEAA/8ACw8AAP8BAAP/AAsPAAD/AQAD/wAL
				DwAA/wEAA/8ACw8AAP8BAAP/AAsPAAD/AQAD
				/wALDwAA/wEAA/8ACw8AAP8BAAP/AAsPAAD/
				AQAD/wALDwAA/wEAA/8ACw8AAP8BAAP/AAsP
				AAD/AQAD/wALDwAA/wEAA/8ACw8AAP8BAAP/
				AAsPAAD/AQAD/wALDwAA/wEAA/8ACw8AAP8B
				AAP/AAsPAAD/AQAD/wALDwAA/wEAA/8ACw8A
				AP8BAAP/AAsPAAD/AQAD/wALDwAA/wEAA/8A
				Cw8AAP8BAAP/AAsPAAD/AQAD/wALDwAA/wEA
				A/8ACw8AAP8BAAP/AAsPAAD/AQAD/wALDwAA
				/wEAA/8ACw8AAP8BAAP/AAsPAAD/AQAD/wAL
				DwAA/wEAA/8ACw8AAP8BAAP/AAsPAAD/AQAD
				/wALDwAA/wEAA/8ACw8AAP8BAAP/AAsPAAD/
				AQAD/wALDwAA/wEAA/8ACw8AAP8BAAP/AAsK
				AAABCgAAAQAAAAEAAAD1AAEFAAABAAAF/wAB
				AAAAAQAAAAEGAAACAAAABAEAAIAAwwC3AC4A
				NAALAAAAAgAAAAEAAAABAAAAAgAAAAICAAAC
				BgAAAQAAAAEAAAD1AAEFAAADAAAF/wADAgAA
				AwYAAAkAAAAEAAAATAAEBQAABAAABf8AAwAA
				AAEAAAAEBAAAgAAAAAoKAAAIAAAABQAAAAgA
				AAAFAAAAAwAAAAIAAAAFBgAABwAAAAEAAAD1
				AAEFAAAGAAAF/wADAAAAAwAAAAYGAAACAAAA
				BAAAAKAADwUAAAcEAAAHAAAAAwAAAAQAAAAH
				BgAACAoAAAMAAAX/AAQCAAAIBgAAAQAAAAEA
				AADoAAMFAAAJAAAF/wAFAgAACQYAAAIAAAAE
				AAAA6AADBQAADQAAAAoAAAANAAAACgAAAAUA
				AAABAAAACgYAAAcAAAABAAAA9QABBQAACwAA
				Bf8ABQAAAAIAAAALBgAAAgAAAAQAAACgAA8F
				AAAMBAAADAAAAAUAAAADAAAADAYAAAgKAAAJ
				AAAF/wAGAgAADQYAAAEAAAABAAAA6AADBQAA
				DgAABf8ABwIAAA4GAAACAAAABAAAAFgAGwUA
				ABIAAAAPAAAAEgAAAA8AAAAHAAAAAQAAAA8G
				AAAHAAAAAQAAAPUAAQUAABAAAAX/AAcAAAAC
				AAAAEAYAAAIAAAAEAAAAoAAPBQAAEQQAABEA
				AAAHAAAAAwAAABEGAAAICgAADgAABf8ACAIA
				ABIGAAABAAAAAQAAAOgAAwUAABMAAAX/AAkC
				AAATBgAAAgAAAAQAAAD8AAgFAAAXAAAAFAAA
				ABcAAAAUAAAACQAAAAEAAAAUBgAABwAAAAEA
				AAD1AAEFAAAVAAAF/wAJAAAAAgAAABUGAAAC
				AAAABAAAAKAADwUAABYEAAAWAAAACQAAAAMA
				AAAWBgAACAoAABMAAAX/AAoCAAAXBgAAAQAA
				AAEAAADoAAMFAAAYAAAF/wALAgAAGAYAAAIA
				AAAEAAAAKAAKBQAAHAAAABkAAAAcAAAAGQAA
				AAsAAAABAAAAGQYAAAcAAAABAAAA9QABBQAA
				GgAABf8ACwAAAAIAAAAaBgAAAgAAAAQAAACg
				AA8FAAAbBAAAGwAAAAsAAAADAAAAGwYAAAgK
				AAAYAAAF/wAMAgAAHAYAAAEAAAABAAAA9AAB
				BQAAHQAABf8ADQIAAB0GAAACAAAABAEAAIAA
				wwC3AC4ANAALAAAAHQAAAB4AAAAdAAAAHgAA
				AA0AAAABAAAAHgYAAAcAAAABAAAA9QABBQAA
				HwAABf8ADQAAAAIAAAAfBgAAAgAAAAQAAACg
				AA8FAAAgBAAAIAAAAA0AAAADAAAAIAYAAAgK
				AAAdAAAF/w==
				</data>
			</dict>
			<key>ctrlloop-id</key>
			<integer>0</integer>
			<key>is-state-driven</key>
			<integer>1</integer>
		</dict>
		<dict>
			<key>Description</key>
			<string>SMC_GPU_sensor_Control_Loop</string>
			<key>GPUPowerMgmtFloorArray</key>
			<array>
				<integer>1</integer>
			</array>
			<key>GPUThresholdDict</key>
			<dict>
				<key>MacBook4,1</key>
				<string>TA3</string>
				<key>TA3</key>
				<array>
					<dict>
						<key>high-threshold</key>
						<integer>25</integer>
						<key>low-threshold</key>
						<integer>0</integer>
					</dict>
					<dict>
						<key>high-threshold</key>
						<integer>33</integer>
						<key>low-threshold</key>
						<integer>25</integer>
					</dict>
					<dict>
						<key>high-threshold</key>
						<integer>99</integer>
						<key>low-threshold</key>
						<integer>33</integer>
					</dict>
					<dict>
						<key>high-threshold</key>
						<integer>100</integer>
						<key>low-threshold</key>
						<integer>99</integer>
					</dict>
				</array>
			</dict>
			<key>IOClass</key>
			<string>ACPI_SMC_CtrlLoop</string>
			<key>MetaStateArray</key>
			<array>
				<dict>
					<key>Description</key>
					<string>Normal</string>
				</dict>
				<dict>
					<key>Description</key>
					<string>Reduced Power</string>
				</dict>
				<dict>
					<key>Description</key>
					<string>User Low Power</string>
				</dict>
				<dict>
					<key>Description</key>
					<string>User High Power</string>
				</dict>
			</array>
			<key>PLimitClass</key>
			<array>
				<string>GPU</string>
			</array>
			<key>SensorIDArray</key>
			<array>
				<integer>6</integer>
			</array>
			<key>ctrlloop-id</key>
			<integer>1</integer>
			<key>is-state-driven</key>
			<integer>1</integer>
		</dict>
		<dict>
			<key>Description</key>
			<string>SMC_Memory_Control_Loop</string>
			<key>IOClass</key>
			<string>ACPI_SMC_CtrlLoop</string>
			<key>MCHThrottleDict</key>
			<dict>
				<key>MT3</key>
				<array>
					<dict>
						<key>DTC_WAB</key>
						<integer>32</integer>
						<key>DTC_WAT</key>
						<integer>0</integer>
						<key>GTC_WAB</key>
						<integer>0</integer>
						<key>GTC_WAT</key>
						<integer>15</integer>
					</dict>
					<dict>
						<key>DTC_WAB</key>
						<integer>32</integer>
						<key>DTC_WAT</key>
						<integer>0</integer>
						<key>GTC_WAB</key>
						<integer>0</integer>
						<key>GTC_WAT</key>
						<integer>15</integer>
					</dict>
					<dict>
						<key>DTC_WAB</key>
						<integer>32</integer>
						<key>DTC_WAT</key>
						<integer>0</integer>
						<key>GTC_WAB</key>
						<integer>0</integer>
						<key>GTC_WAT</key>
						<integer>15</integer>
					</dict>
					<dict>
						<key>DTC_WAB</key>
						<integer>32</integer>
						<key>DTC_WAT</key>
						<integer>0</integer>
						<key>GTC_WAB</key>
						<integer>0</integer>
						<key>GTC_WAT</key>
						<integer>15</integer>
					</dict>
				</array>
				<key>MacBook4,1</key>
				<string>MT3</string>
			</dict>
			<key>MetaStateArray</key>
			<array>
				<dict>
					<key>Description</key>
					<string>Normal</string>
				</dict>
				<dict>
					<key>Description</key>
					<string>Reduced Power</string>
				</dict>
				<dict>
					<key>Description</key>
					<string>User Low Power</string>
				</dict>
				<dict>
					<key>Description</key>
					<string>User High Power</string>
				</dict>
			</array>
			<key>PLimitClass</key>
			<array>
				<string>Mem</string>
			</array>
			<key>ctrlloop-id</key>
			<integer>2</integer>
			<key>is-state-driven</key>
			<integer>1</integer>
		</dict>
	</array>
	<key>SensorArray</key>
	<array>
		<dict>
			<key>Desc-Key</key>
			<string>GPU</string>
			<key>IOClass</key>
			<string>IOPlatformSensor</string>
			<key>sensor-id</key>
			<integer>6</integer>
		</dict>
	</array>
</dict>
</dict>
</plist>

Link to comment
Share on other sites
Silencers
Silencers
Posted
  • Author
Posted
Here is the MacBook4,1 plist 10.6.4.. Youl notice that it does NOT have CstateDemotionDict like MacBookPro2,1 does. Restart action also does not exist. There are a few mentions of plimit dict and I do have those in my legacy kext as there in the MB4,1. Believe me I read your guide and I said I had this working perfectly in 10.6.2.. Its just gone haywire since 10.6.4 with my cpu not throttling up and down.

I know that those values do not exist. You have to add them to unlock stepping and c-states! Please remember, you DO NOT HAVE Mac hardware. That means your hardware cannot properly identify itself to OSX, and that means that OSX cannot enable some features for some hardware. That is exactly why we do those tricks with legacy plists and whatnot.

 

Again, YOU NEED TO ADD mentioned values to your legacy kext. Basically, you need to compare my legacy kext to yours and replicate all sections you find in mine that you don't have in yours. But do not delete what you have, and I don't.

 

Please, until you do all that, don't ask any more questions. This has been repeated numerous times, and if you refuse to listen, I cannot really help you.

Link to comment
Share on other sites
00diabolic
00diabolic
Posted
Posted
I know that those values do not exist. You have to add them to unlock stepping and c-states!

 

Silencers.. I am REALLY sorry i did not know that I had to add those extra sections. I thought I had to use only the sections & values in my matching model. Odd that I had speedstep working in 10.6.2 without them. Either way Ill add them now and see what happens. This could be what solves a few other issues.

 

What Ill do now is add everything your legacy kext has and just replace where mine is different and I should have it all. Does that sound right?

 

Thanks again.

 

UPDATE: Damn I dont know how I missed this. I looked at the MacBookPro2,1 and it also does not have cstatedict and cstatedemotiondict either. So I should have had these in my legacy kext all along seeing as you did. Still odd how it worked in 10.6.2.. Must have just been lucky with that. Sorry again for my incompetence.

 

Update 2: Sure enough that extra code was needed. I also now see the cstateoverride = true in my Ioreg. Stepping is working as it should and even fan control is better no doubt tied to cstatedict also.

 

Now I just wish I could find a way to force my 800fsb that my bios reports as 736mhz instead of 800 as it should be.

 

Silencer when you run this command? sudo setpci -s 00:1f.0 0xa6.b

 

What do you get? 00 or 80. I get 00. The command shows 80 if you have deeper c-states working. I hope yours is 00 because I dont know what else I could do to fix mine unless I add them to the DSDT as you did. But I was hoping there being read from my SSDT tables as my p-sates are and I do get this when I grep CST.

 

ioreg -lw0 | grep CST

"CSTInfo" = 19136773 Is this the same for you?

 

and CSTinfo in ioreg explorer still shows 0x1240105

Link to comment
Share on other sites
Silencers
Silencers
Posted
  • Author
Posted
Silencer when you run this command? sudo setpci -s 00:1f.0 0xa6.b

 

What do you get? 00 or 80. I get 00. The command shows 80 if you have deeper c-states working. I hope yours is 00 because I dont know what else I could do to fix mine unless I add them to the DSDT as you did. But I was hoping there being read from my SSDT tables as my p-sates are and I do get this when I grep CST.

 

ioreg -lw0 | grep CST

"CSTInfo" = 19136773 Is this the same for you?

 

and CSTinfo in ioreg explorer still shows 0x1240105

Nah, trust me, your c-states are now working. I only checked CSTInfo and whenever it was not set, CPU temperature was 10 degrees hotter. As far as I know, 0x1240105 is the correct value, and it means you have more than one c-state. If you would have only one, it would be 0x1140105 (I did a lot of experimenting with mine).

Link to comment
Share on other sites
00diabolic
00diabolic
Posted
Posted
Nah, trust me, your c-states are now working. I only checked CSTInfo and whenever it was not set, CPU temperature was 10 degrees hotter. As far as I know, 0x1240105 is the correct value, and it means you have more than one c-state. If you would have only one, it would be 0x1140105 (I did a lot of experimenting with mine).

 

Thanks for the info. Good to know that the value does change if you have only one. That command I gave you came from a thread with desktop users. They have some deep c-states for those cpus. Apparently mobile cpus dont have them or at least I dont. Would like to know what results you get from that command.

 

Have you done any more DSDT edits since you made this guide? I have a firewire fix if you need it. I know you said your sleep problem was related to audio what did you do to fix that? Was it what you included in the legacy kext that allowed you to have audio with shutdown and no voodooHDA. I might have to try that. I have my linux audio codec info and I was able to use a efi string to get audio in 10.5 but no volume adjust or mic or jacks.

 

Do you know if the SSDT tables include the value that the bios has for the FSB. I have a bios that reports my FSB as 736mhz when its supposed to be 800. The only known solution is a modded kernel using a flag. Smbios.plist override is only superficial unfortunately. Any suggestions?

 

Thanks again

00D

Link to comment
Share on other sites
Silencers
Silencers
Posted
  • Author
Posted
Apparently mobile cpus dont have them or at least I dont. Would like to know what results you get from that command.

Mobile CPUs have deep sleep, they had it before desktop CPUs. But modern CPUs have a lot of c-states, as compared to my Core2Duo, which has only 4, and only 3 can be active at the same time.

 

Have you done any more DSDT edits since you made this guide? I have a firewire fix if you need it. I know you said your sleep problem was related to audio what did you do to fix that? Was it what you included in the legacy kext that allowed you to have audio with shutdown and no voodooHDA. I might have to try that. I have my linux audio codec info and I was able to use a efi string to get audio in 10.5 but no volume adjust or mic or jacks.

I did some minor fixes, but nothing important. I don't have firewire, so it's not actual for me. As for the audio, it was a complex problem. With my codec, AD1981HD and T60p it is also related to modem settings in BIOS. I had to enable modem to have sleep working. Don't ask me why, apparently it is a bug in the codec implementation by Lenovo. Thank ThinkWiki for help.

 

Do you know if the SSDT tables include the value that the bios has for the FSB. I have a bios that reports my FSB as 736mhz when its supposed to be 800. The only known solution is a modded kernel using a flag. Smbios.plist override is only superficial unfortunately. Any suggestions?

Are you sure it is BIOS who reports it wrong and not your bootloader? If it is indeed BIOS, then why do you care? It's not such a big deal after all.

Link to comment
Share on other sites
00diabolic
00diabolic
Posted
Posted
Are you sure it is BIOS who reports it wrong and not your bootloader? If it is indeed BIOS, then why do you care? It's not such a big deal after all.

 

Yeah I'm sure its the bios. Ive had the problem ever since I started using Leopard and it does not happen in windows because Windows does not relie on the {censored} bios giving it the FSB value (there is no more bios updates for my system either). The 736fsb happens with EFI 8 and then with every bootloader I have tried. I am using aserelBLN now as it is the best overall. Ive tried Anval, and of course chameleon none of them have a FSB flag I can use so only the modded kernels allow for a flag. It makes a pretty big difference actually. I used to have a FSB locked smbios in leopard that superhai made for me and my geekbench scores went from a 2800 to a 3400. So it does make a difference. I cant use the smbios now because it wont work with SL. I guess Ill keep looking.

Link to comment
Share on other sites
Silencers
Silencers
Posted
  • Author
Posted
I cant use the smbios now because it wont work with SL. I guess Ill keep looking.

You can always try to see if SMBIOS.plist solution works for you. You should be able to override FSB values from there.

Link to comment
Share on other sites
00diabolic
00diabolic
Posted
Posted
You can always try to see if SMBIOS.plist solution works for you. You should be able to override FSB values from there.

 

No like I said before its only superficial.

 

In all of the chameleon based bootloaders its superficial to make OSX happy. If you pull the real value or benchmark in Windows vs OSX you get the results that prove its still the same. Voodoo Monitor is one app that shows it correctly regardless of smbios superficial fix.

Link to comment
Share on other sites
MartysMind
MartysMind
Posted
Posted

Hi @Silencers,

 

I tried your suggestion to alter the _Q14/_Q15 (brightness buttons) in the DSDT to control the fan.. and only succeeded in disabling brightness ;-)

 

Can you share a working version of your DSDT that allows us to control the fan manually?

 

Well, this is probably hardware dependent. I'm thinking about writing a custom kext for Thinkpads to allow fan control, but it cannot be universal solution I'm afraid. I've currently enabled in DSDT ThinkPad button. When I press it, fan swtiches off, when I press again - it switches to automatic mode.
Link to comment
Share on other sites
Mac Man 50
Mac Man 50
Posted
Posted

Silencers:

 

Awesome job!! I have read your postings on forum.thinkpads.com. Keep up the good work!

 

I have a HP dv8t-1200 (Motherboard: HP, Core i7-720 with Nvidia GT 230M) notebook running on vanilla SL 64 bit. All is fine and thanks to expert souls in this forum. I'm struggling with the following issues:

 

a. Enabling SpeedStep (the fan seems to be running all the time and also the machine seems to be a bit hot on the upper left and I ran MSR Tools (32 bit). I have attached a screenshot and also dsdt.aml out of my dv8t-1200.

 

b. The Graphics card shows "Unknown".

 

The MSR Tool is not showing all 4 cores and some of the stuff shown in the tool seems to be incorrect. I saw the run cool SSDT in DSDTSE tool and I'm not sure whether I can apply the cool SSDT inside my DSDT.aml.

 

If you point me to how to control the fan and make the machine run cool, it would be awesome.

 

Please help.

 

Thanks.

dsdt.aml.zip

post-607801-1279428973_thumb.png

Link to comment
Share on other sites
  • 4 months later...
sanigo
sanigo
Posted
Posted

Hi there!

 

The C-State cannot be stablely enabled upon every reboot, sometimes its is enabled and the CSTInfo is in ioreg,but sometimes it cannot be enabled.

I have reboot system several times to enable C-State.

How could I fix this?

 

Thanks!

Link to comment
Share on other sites
Silencers
Silencers
Posted
  • Author
Posted
The C-State cannot be stablely enabled upon every reboot, sometimes its is enabled and the CSTInfo is in ioreg,but sometimes it cannot be enabled.

I have reboot system several times to enable C-State.

How could I fix this?

I believe in this case it's not a problem with C-states configuration per se, but rather something with CPU Power Management all together. You need to check if you have all other DSDT fixes and patches applied correctly.

Link to comment
Share on other sites
sanigo
sanigo
Posted
Posted
I believe in this case it's not a problem with C-states configuration per se, but rather something with CPU Power Management all together. You need to check if you have all other DSDT fixes and patches applied correctly.

 

Hi,

Thanks for your reply. Did you mean the AppleLPC and AppleIntelCPUPowerManagement?

I have checked that both of the two kexts are loaded normally even when the CSTInfo doest not exist.

The other DSDT fixes seems ok, and the /S/L/E is vanilla, but the system can not sleep.

I am fairly new to DSDT and hackintosh, my DSDT fixes is very according to your post.

Could you please give my more advice?

Thanks you !

Link to comment
Share on other sites
sanigo
sanigo
Posted
Posted

Are you kind enough to check my DSDT and Legacy.kext?

This is a Thinkpad T400-2767R28 box.

The main problems are:

1. C-State cannot be stablely enabled.

2. The lid display cannot sleep while the display sleep time.

3. The system cannot sleep at all, when I try to put the system to sleep, I just got freezed system.

 

I think that I am very near to the right place , but I just cannot find the way.

Thank you in advance!

DSDT.zip

Link to comment
Share on other sites
  • 2 weeks later...
b004004
b004004
Posted
Posted
Great Guide Silencers! It definitely helped getting my T60 2007-55u up.

I was wondering though if you managed to get Sleep/Wake working?

 

I have put C1M4 C-states and got CSTInfo and working P-states, but when I call dashboard, the animations were very very slow. Please help me!

 

 

T60 2007G4U

 

CPU: T2500

 

video: ATIx1400

Link to comment
Share on other sites
  • 1 year later...
musashiz
musashiz
Posted
Posted

I must say amazing.... work.... Confirmed everything working on a t60 w/ coreduo and x1400. Just used the final release of your extra folder... everything works incl. sleep, speedstep, fan control. Just edited the legacyt60 kext with my dev id and used the readeonhd.noload you included . qe, ci, resolution changing. missing the brightness slider but whatevs. Again thank you silencer for your perfect dsdt for my darling t60

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...