DSDT Patching for Dummies - SnowLeo with 100% vanilla /S/L/E

Silencer · **Posted:** Thu Apr 29, 2010 4:12 am

Blue Thunder wrote:

Um ok... well your guide tells me to do this:

Well, you have mistaken, because that part of the code is for Native AHCI driver (SATA) and not USB. I can see that it's not very clear in the guide, where should that code be. In the Questionable fixes I say that patching USB/EHCI is not necessary, because T60p already has proper IDs. It might be that you too have proper IDs, and the problem with Sleep lies elsewhere.

Blue Thunder · **Posted:** Fri Apr 30, 2010 7:04 am

Ahhh ok. I just searched my DSDT for the text "Method (_DSM, 4, NotSerialized)". Only the AHCI fix came up so I assumed that was where the USB fix was supposed to be applied.

I might try patching the USB/EHCI.

EDIT: Hmmm was looking into this UHCI/EHCI fix and it seems that I don't need it, at least according to this page http://apocolipse.com/?p=14.
I think my sleep problem might be caused by my WWAN card.

Here is everything from the console log after the system woke. It seems to mention that USB 1 to 7 is the source and specifically mentions 1 (which is my WWAN card) and 2 (fingerprint reader), but also 8 (appears to be an empty slot).

I wonder if its my WLAN card. OSX might be trying to turn it off even though it doesn't recognise it. Or maybe its my bluetooth card since I'm not sure if a WLAN card would show up as a USB connect (even thou the WWAN does). I wonder if I can disable them in BIOS. (btw do you have an Intel WLAN card in your T60p?).

Code:

30/04/10 10:31:31 PM   kernel   FakeSMC: key info not found CLWK, length - 6
30/04/10 10:31:31 PM   kernel   hibernate image path: /var/vm/sleepimage
30/04/10 10:31:31 PM   kernel   sizeof(IOHibernateImageHeader) == 512
30/04/10 10:31:31 PM   kernel   Opened file /var/vm/sleepimage, size 1073741824, partition base 0x5d1da95a00, maxio 400000
30/04/10 10:31:31 PM   kernel   hibernate image major 14, minor 3, blocksize 512, pollers 5
30/04/10 10:31:31 PM   kernel   hibernate_alloc_pages flags 00000000, gobbling 0 pages
30/04/10 10:31:33 PM   kernel   System SafeSleep
30/04/10 10:31:36 PM   kernel   hibernate_page_list_setall start
30/04/10 10:31:36 PM   kernel   hibernate_page_list_setall time: 62 ms
30/04/10 10:31:36 PM   kernel   pages 217489, wire 42400, act 27989, inact 28, spec 38, zf 0, throt 0, could discard act 15242 inact 10199 purgeable 2107 spec 119486
30/04/10 10:31:36 PM   kernel   hibernate_page_list_setall found pageCount 70455
30/04/10 10:31:36 PM   kernel   IOHibernatePollerOpen, ml_get_interrupts_enabled 0
30/04/10 10:31:36 PM   kernel   IOHibernatePollerOpen(0)
30/04/10 10:31:36 PM   kernel   writing 69195 pages
30/04/10 10:31:36 PM   kernel   image1Size 68623872
30/04/10 10:31:36 PM   kernel   PMStats: Hibernate write took 2264 ms
30/04/10 10:31:36 PM   kernel   all time: 2264 ms, comp time: 539 ms, deco time: 0 ms, 
30/04/10 10:31:36 PM   kernel   image 111118336, uncompressed 283422720 (69195), compressed 105618696 (37%), sum1 f5e48230, sum2 54b2cffa
30/04/10 10:31:36 PM   kernel   hibernate_write_image done(0)
30/04/10 10:31:36 PM   kernel   sleep
30/04/10 10:31:36 PM   kernel   Wake reason = USB1 USB7
30/04/10 10:31:36 PM   kernel   Unsynchronized  TSC for cpu 1: 0x0000000038f12148, delta 0x96e28
30/04/10 10:31:36 PM   kernel   System Wake
30/04/10 10:31:36 PM   kernel   Previous Sleep Cause: 0
30/04/10 10:31:36 PM   kernel   USB (EHCI):Port 8 on bus 0xfd connected or disconnected: portSC(0x101803)
30/04/10 10:31:36 PM   kernel   The USB device Biometric Coprocessor (Port 2 of Hub at 0x7d000000) may have caused a wake by being disconnected
30/04/10 10:31:36 PM   kernel   The USB device Mini Card (Port 1 of Hub at 0x3d000000) may have caused a wake by being disconnected
30/04/10 10:31:37 PM   mDNSResponder[27]   mDNSPlatformRawTime: last_mach_absolute_time 4B22F7BE80515923
30/04/10 10:31:37 PM   mDNSResponder[27]   mDNSPlatformRawTime: this_mach_absolute_time 4B1F318D00000000
30/04/10 10:31:37 PM   mDNSResponder[27]   mDNSPlatformRawTime: last_mach_absolute_time 5BD3577680515923
30/04/10 10:31:37 PM   mDNSResponder[27]   mDNSPlatformRawTime: this_mach_absolute_time 5BCF9E0800000000
30/04/10 10:31:37 PM   kernel   Ethernet [Intel8254x]: Link up on en0, 10-Megabit, Half-duplex, No flow-control, Debug [796d,6d4c,0de1,0e00,45e1,4000]
30/04/10 10:31:38 PM   mDNSResponder[27]   RegisterInterface: Frequent transitions for interface en0 (FE80:0000:0000:0000:0216:41FF:FEA8:E814)
30/04/10 10:31:38 PM   configd[13]   network configuration changed.
30/04/10 10:31:38 PM   configd[13]   setting hostname to "Blue-Thunders-MacBook-Pro.local"
30/04/10 10:31:38 PM   mDNSResponder[27]   mDNSPlatformRawTime: last_mach_absolute_time 8F9F640C80515923
30/04/10 10:31:38 PM   mDNSResponder[27]   mDNSPlatformRawTime: this_mach_absolute_time 8F9B15CB00000000
30/04/10 10:31:38 PM   configd[13]   network configuration changed.
30/04/10 10:31:38 PM   mDNSResponder[27]   DeregisterInterface: Frequent transitions for interface en0 (FE80:0000:0000:0000:0216:41FF:FEA8:E814)
30/04/10 10:31:38 PM   mDNSResponder[27]   RegisterInterface: Frequent transitions for interface en0 (192.168.1.5)
30/04/10 10:31:40 PM   configd[13]   setting hostname to "***data blanked out by BT***"
30/04/10 10:31:42 PM   mDNSResponder[27]   RegisterInterface: Frequent transitions for interface en0 (FE80:0000:0000:0000:0216:41FF:FEA8:E814)
30/04/10 10:31:52 PM   blued[151]   Apple Bluetooth daemon started

Ok after turning on my bluetooth and trying to sleep again, I got these additional errors

Code:

30/04/10 10:45:08 PM   kernel   USB (EHCI):Port 7 on bus 0xfd connected or disconnected: portSC(0x101803)
30/04/10 10:45:08 PM   kernel   The USB device BCM2045B (Port 1 of Hub at 0x7d000000) may have caused a wake by being disconnected

So it looks like it could be my WLAN card. I'll try disabling it in the BIOS.
EDIT2: Nope didn't work, except this time it dims the screen upon sleep, but doesn't really brighten it again when it comes out of sleep a few seconds later. The screen is on, but barely. I clicked to sleep again and the screen came back to full brightness.

I tried it with bluetooth off (via Fn+F5) and the screen came back as normal, but no sleep and it's still mentions USB ports 1, 2 and 8.

EDIT3: Ok... I got it working. I went into BIOS and disabled InfraRed, Parallel, Bluetooth, WLAN and WWAN (I've since re-enabled bluetooth, WLAN and WWAN without breaking sleep). I suspect the problem was InfraRed port and yes I know in your guide you "suggested" that I turn off all unecessary/legacy ports. :oops:

Anyways what I find unusual about sleep is that it will put my computer into sleep mode but the fan keeps spining (infact it sounds as if the computer is still on). I couldn't wake the computer by pressing a key or the power button. So I held down the power button to turn the computer off. Then the next time I booted OSX, it "woke" the kernel and I found that I could resume where I left off... it seems like OSX's sleep is like Windows's hibernate.... ah well at least sleep is working.

Silencer · **Posted:** Fri Apr 30, 2010 9:00 am

Blue Thunder wrote:

EDIT3: Ok... I got it working. I went into BIOS and disabled InfraRed, Parallel, Bluetooth, WLAN and WWAN (I've since re-enabled bluetooth, WLAN and WWAN without breaking sleep). I suspect the problem was InfraRed port and yes I know in your guide you "suggested" that I turn off all unecessary/legacy ports. :oops:

Anyways what I find unusual about sleep is that it will put my computer into sleep mode but the fan keeps spining (infact it sounds as if the computer is still on). I couldn't wake the computer by pressing a key or the power button. So I held down the power button to turn the computer off. Then the next time I booted OSX, it "woke" the kernel and I found that I could resume where I left off... it seems like OSX's sleep is like Windows's hibernate.... ah well at least sleep is working.

Great to hear you've made some progress. It's good idea to disable legacy stuff just to be sure.

Regarding sleep. If your fan keeps spinning, you didn't go to full sleep

Need to investigate further, what keeps it on. I had similar problem, but I managed to fix is fast (and then I couldn't wake up, but that's another story). Make sure that you have vanilla SpeedStep, AppleIntelCPUPowerManagement, AppleHPET and AppleLPC loading and running fine.

Regarding hibernate. There's a number of "sleep" modes on MacBooks. By default you are running on mode 3 which is "safe sleep" it goes to normal "powered" sleep, but also saves the image of the memory on hard drive. If you run out of juice, it will load that image into memory, like regular hibernate. If you switch to mode 1, you will only have hibernate mode, computer will power off when going to sleep. With sleep mode 0 you will only have regular sleep, and computer will go to sleep faster. You need to experiment, it is possible that you were simply impatient, saving memory to hard drive takes some time, and fan keeps spinning.

To change sleep mode you need to run the following command from terminal:

Code:

sudo pmset -a hibernatemode X

X - is the mode you desire. Read more here.

Silencer · **Posted:** Fri Apr 30, 2010 11:17 am

plastikman, I have fixed brightness issue with ATI1600Controller and the EFI string you provided. Basically, i just removed a bunch of stuff from EFI, a lot of information that is provided by the video adapter itself and shouldn't be hardcoded. Now the display doesn't dim automatically after a certain period of time (it was very annoying).

Get the updated EFI string here: ATI_V5200_EFIString.zip

Silencer · **Posted:** Fri Apr 30, 2010 11:26 am

And I have an update on the Sleep issue.

Sometime ago I have found out that the problem with Sleep I had, was related to VoodooHDA. The problem was very specific - I could get the computer to Sleep, but it never woke up (all other issues are not related to VoodooHDA). Whenever I loaded AppleHDA (even not working one) I could go to Sleep and wake up just fine.

Then I have stumbled upon a ThinkWiki page, that described a number of problems with our audio codec AD1981HD in Linux. Nothing related to sleep per se, but it got me thinking, and after a couple of tries I now have sleep working with VoodooHDA!

The solution is simple: go to BIOS and enable modem device and disable WWAN card. It did the trick for me. I've then tested to be sure, disabled modem again and got the same problem as before - couldn't wake up. So it is definitely problem with modem. Try yourself and let me know if you succeed.

plastikman · **Posted:** Fri Apr 30, 2010 11:22 pm

Silencer wrote:

plastikman, I have fixed brightness issue with ATI1600Controller and the EFI string you provided. Basically, i just removed a bunch of stuff from EFI, a lot of information that is provided by the video adapter itself and shouldn't be hardcoded. Now the display doesn't dim automatically after a certain period of time (it was very annoying).

Get the updated EFI string here: ATI_V5200_EFIString.zip

Thanks Silencer! when i was making the EFI string i was throwing the kitchen sink at it to get it going

thanks for taking the time to make it right.

i am using it right now and the string works nicely.

Blue Thunder · **Posted:** Fri Apr 30, 2010 11:45 pm

Quote:

Make sure that you have vanilla SpeedStep, AppleIntelCPUPowerManagement, AppleHPET and AppleLPC loading and running fine.

How exactly do I check for AppleIntelCPUPowerManagement, AppleHPET and AppleLPC?

I think I may not have vanila SpeedStep (P-states) working properly becuase in your guide you say:

Quote:

...on right handside you should see that CPUPlimit is 0x0 and PerformanceStateArray contains 5 values. This means you're golden.
....
If you have successfully enabled C-states, you will see CSTInfo parameter.

I only have 4 values next to PerformanceStateArray, but my CPUPlimit is 0x0.
I do have CSTinfo so I think my C-states are ok.

Anyways I tried clicking sleep and letting the computer run for awhile just incase I was impatient, but it didn't seem to help (the HDD light doesn't flicker, only the battery, power and sleep lights are on). And OSX doesn't complain about not saving the sleep image properly when I reboot (I assume it would throw up an error if it didn't save properly) so I assume it saved the sleep image properly.

EDIT: I was reading that page you linked to, describing sleep states. I wonder if I'm having a problem because I'm using unsecured virtual memory...

Quote:

The solution is simple: go to BIOS and enable modem device and disable WWAN card. It did the trick for me.

Heh, after doing this my computer doesn't sleep anymore - same problem as before. (Note: I forgot to mention in my last post that I also disabled the modem, so maybe it wasn't InfraRed causing my sleep problems). I've gone and re-enabled everything, including legacy ports. Heres what I get:

- If serial port is enabled, OSX kernal panics on boot.
- If modem is enabled, OSX does NOT sleep.
- Everything else doesn't seem to matter. OSX sleeps but does not shutdown the computer and I can't wake it without a hard reboot.

It seems that I've got the same result as you when my Modem is disabled, but not the same result when my modem is enabled.

Anyways I'll check out the new ATI strings aswell. I've just copy the numbers from ati.hex into the appropriate section in my com.apple.Boot.plist. Everything seems to be ok on this front.

Silencer · **Posted:** Sat May 01, 2010 4:44 am

Blue Thunder wrote:

How exactly do I check for AppleIntelCPUPowerManagement, AppleHPET and AppleLPC?

Go to System Profiler and check Extensions.

Blue Thunder wrote:

I think I may not have vanila SpeedStep (P-states) working properly becuase in your guide you say:
I only have 4 values next to PerformanceStateArray, but my CPUPlimit is 0x0.
I do have CSTinfo so I think my C-states are ok.

You have everything running fine there. Number of P-states depends on the CPU. You only need to see CPUPlimi=0 and CSTInfo set to something.

Blue Thunder wrote:

Heh, after doing this my computer doesn't sleep anymore - same problem as before. (Note: I forgot to mention in my last post that I also disabled the modem, so maybe it wasn't InfraRed causing my sleep problems). I've gone and re-enabled everything, including legacy ports. Heres what I get:

- If serial port is enabled, OSX kernal panics on boot.
- If modem is enabled, OSX does NOT sleep.
- Everything else doesn't seem to matter. OSX sleeps but does not shutdown the computer and I can't wake it with a hard reboot.

You should try to remove VoodooHDA and change your DSDT back to allow AppleHDA to load (rename AZAL back to HDEF). Modem device is actually part of audio codec, and looks like you might have problems in that area. Doesn't hurt to try anyways.

Blue Thunder · **Posted:** Sun May 02, 2010 5:09 am

Ok I see an entry for AppleLPC and AppleHPET when I search for those terms in IORegistryExplorer and in System Profiler --> Extentions, so everything seems to be good there.

I'll re-enable "Device (HDEF)" in my DSDT and see if that fixes my modem-sleep problem. But doesn't this mean I won't be able to use VoodooHDA? (might not be a bad thing if AppleHDA handles my sound properly).

EDIT: Modded DSDT, removed VoodooHDA, enabled modem and set WWAN to "hidden", but the computer still won't sleep.

Silencer · **Posted:** Sun May 02, 2010 5:22 am

Blue Thunder wrote:

I'll re-enable "Device (HDEF)" in my DSDT and see if that fixes my modem-sleep problem. But doesn't this mean I won't be able to use VoodooHDA? (might not be a bad thing if AppleHDA handles my sound properly).

No-no, AppleHDA won't work, but you need to find out what causes problems with sleep, for this you need to disable VoodooHDA and see.

Blue Thunder · **Posted:** Sun May 02, 2010 5:55 am

Hmmm this is getting stranger and stranger:

If I enable modem and disabled WWAN (WLAN and bluetooth enabled), the computer won't sleep.
If I disable modem and disable WWAN (WLAN and bluetooth enabled), the computer won't sleep.
If I disable everything except the modem, the computer won't sleep.
If I disable everything, the computer won't sleep.

Note: This does not include InfraRed, Serial or Parallel. These ports are all diabled.

Basically seems that enabling "Device (HDEF)" breaks sleep for me.

I put back my old DSDT with "Device (HDEF)" disabled and disabled the modem --> sleep is working (although I can't wake without a hard reboot).

Quote:

You should try to remove VoodooHDA and change your DSDT back to allow AppleHDA to load (rename AZAL back to HDEF).

Hmmm, I haven't got AZAL because I've followed your inital guide. I've taken a look at your latest DSDT file and it seems you've got more code in there, so I'll try using your DSDT instead.

EDIT: Same problem, even with your dsdt. However one thing I've noticed is that the sleep LED indicator flashes.

Silencer · **Posted:** Sun May 02, 2010 10:11 am

Blue Thunder wrote:

I put back my old DSDT with "Device (HDEF)" disabled and disabled the modem --> sleep is working (although I can't wake without a hard reboot).

Ok, this is something that I had before with VoodooHDA. I only managed to fix this problem with waking up by enabling modem.

Blue Thunder wrote:

EDIT: Same problem, even with your dsdt. However one thing I've noticed is that the sleep LED indicator flashes.

I don't really know what else to suggest, it's hard when you can't actually mess around with kexts yourself. I personally didn't manage to fix sleep for a long time an had to live without it, which was ok, because everything else was working fine.

Blue Thunder · **Posted:** Sun May 02, 2010 12:39 pm

Do you get any errors in your console log after waking?

Anyway well I might have to leave it. At least I've got sleep half working, what is of more concern would be finding a compatible WLAN card... either that or waiting till the 3945abg drivers are done.

Oh one more thing, while testng out DSDT's I used some advice on your guide about manually specifying an .aml file in Charmelon (or AsereBLN) during boot:

Quote:

13. If you booted to SnowLeo successfully, go to /Extra and copy DSDT.aml to DSDT_stable.aml. If your further patches raise kernel panic during boot, you can type the following command in Chameleon: DSTD=/Extra/DSDT_stable.aml and it will use that older and stable version of DSDT. Lifesaver!

However I think you mistyped DSDT when you say "DSTD=/Extra/DSDT_stable.aml".

unbehagen · **Posted:** Thu May 06, 2010 12:59 pm

Just to let you guys know: I got sleep working on my T60 with X1400 with this version of the RadeonHD kext: http://www.insanelymac.com/forum/index. ... &p=1462665

Blue Thunder · **Posted:** Fri May 07, 2010 9:31 am

unbehagen wrote:

Just to let you guys know: I got sleep working on my T60 with X1400 with this version of the RadeonHD kext: http://www.insanelymac.com/forum/index. ... &p=1462665

Oh hay, not bad. Did you have to enable your modem device and disable your WWAN device in BIOS to get sleep to work?

unbehagen · **Posted:** Sat May 08, 2010 7:08 pm

Blue Thunder wrote:

Oh hay, not bad. Did you have to enable your modem device and disable your WWAN device in BIOS to get sleep to work?

I don't have a WWAN device. And I did not change that modem setting - and I currently don't know what the default is, sorry. Regarding WLAN: I got myself a Broadcom BCM94311MCG and the patched BIOS by Zender and it works really well OOB.

bozilla · **Posted:** Wed Jun 23, 2010 4:27 pm

Silencer,

You are an inspiration to the osx86 community. Clear and detailed guide and very well organized. I was able to migrate my "hacked kext" version of OSX to a DSDT patched (upgrade-proof) version in a few hours.

In order to get my 2007-CQ8 T60p operational I merely had to add my PCI_ID to the legacy kext you provided for my Atheros wireless card (168c,1014).

The Vanilla Speedstepping appears to be working but the speed step definitely keeps the CPU running a little hotter than I had with VoodooMini. I will experiment some more with that as I go.

As I have a 2.16G CoreDuo I had to make some changes (minimal) to the SMBIOS.plist and the P-States. Really no big deal.

Have you run any video tests with your Vanilla DSDT video patches? I've noticed about a 40% hit on performance from my original ATIinject method and it appears that it may also be related to the CPU getting too hot. I will play around with these things and see if we can make your method even cooler (literally) and faster at the same time.

Great groundwork. I'm betting you saved me months of research on DSDT patching.

bozilla · **Posted:** Thu Jun 24, 2010 1:32 am

I ran some experiments with the Video performance:

I updated the EFI string for my EDID blocks from my old ATIinject.kext and updated my com.apple.Boot.plist. This resulted in good performance with EFI string injection. I tested the video performance with xbench and then with a 720p video feed off youtube.

I then removed the EFI string from com.apple.boot.plist and disabled ATINDRV.kext from the Extras/Extensions and enabled RadeonHD.kext.
Interesting that both video performance results are very similar!

EFI Injection with ATINDRV frame buffers
====
Results 179.01
System Info
Xbench Version 1.3
System Version 10.6.3 (10D578)
Physical RAM 3072 MB
Model MacBookPro1,3
Drive Type SAMSUNG MMCQE28G8MUP-0VA
Quartz Graphics Test 160.85
Line 125.51 8.36 Klines/sec [50% alpha]
Rectangle 153.85 45.93 Krects/sec [50% alpha]
Circle 133.75 10.90 Kcircles/sec [50% alpha]
Bezier 148.79 3.75 Kbeziers/sec [50% alpha]
Text 413.08 25.84 Kchars/sec
OpenGL Graphics Test 201.80
Spinning Squares 201.80 256.00 frames/sec

NOTES:
- CPU gets pretty hot under high video load but sleep works consistently

RadeonHD.kext
====
Results 180.56
System Info
Xbench Version 1.3
System Version 10.6.3 (10D578)
Physical RAM 3072 MB
Model MacBookPro1,3
Drive Type SAMSUNG MMCQE28G8MUP-0VA
Quartz Graphics Test 162.12
Line 127.21 8.47 Klines/sec [50% alpha]
Rectangle 154.69 46.18 Krects/sec [50% alpha]
Circle 134.68 10.98 Kcircles/sec [50% alpha]
Bezier 148.99 3.76 Kbeziers/sec [50% alpha]
Text 420.32 26.29 Kchars/sec
OpenGL Graphics Test 203.72
Spinning Squares 203.72 258.43 frames/sec
NOTES:
- CPU runs cooler at high video loads
- Sleep is rather inconsistent on this one with random crashes and bluetooth going down

Silencer · **Posted:** Sat Jun 26, 2010 2:45 pm

bozilla wrote:

The Vanilla Speedstepping appears to be working but the speed step definitely keeps the CPU running a little hotter than I had with VoodooMini. I will experiment some more with that as I go.

Do check if C-states are enabled and working fine. This is the most important part for the temperature control.

bozilla wrote:

Have you run any video tests with your Vanilla DSDT video patches? I've noticed about a 40% hit on performance from my original ATIinject method and it appears that it may also be related to the CPU getting too hot. I will play around with these things and see if we can make your method even cooler (literally) and faster at the same time.

Would be great, but I have to say that I did test all different options for performance with OpenGL Extensions quick test, and I did not find any different between RadeonHD.kext, vanilla X1600 controller and ATIinject. The same goes for the temperature.

bozilla wrote:

Great groundwork. I'm betting you saved me months of research on DSDT patching.

Glad to help. No point of spending months on personal research and then not share it with the rest. And so I did

Silencer · **Posted:** Sat Jun 26, 2010 2:48 pm

bozilla wrote:

I then removed the EFI string from com.apple.boot.plist and disabled ATINDRV.kext from the Extras/Extensions and enabled RadeonHD.kext.
Interesting that both video performance results are very similar!

You need to try vanilla X1600 controller instead of ATINDRV.kext, this is the best solution of them all. Just check the posts in the end of this thread. I haven't yet updated the guide with the new information.

bozilla · **Posted:** Mon Jun 28, 2010 11:19 am

Thanks Silencer,

I believe my current configuration uses the legacy.kext to add my PCIID string for the X1000. Are you saying I should update my legacy.kext to try to match my PCI string to the X1600 driver instead?

I'll have to look at my settings again to sort that out. So far the performance is quite good so I'm pretty happy. As for the C-States I have confirmed they are working (as far as I can tell). I Have all the expected listings in my IOREG and I appears I have 4states instead of the 5 you listed (I run a Core Duo (not core 2 duo)).

Temps idle around 60 to 65C when my prior setup idled around 45C. However when temps hit around 90C I can see CPU starts ramping down to keep temps back into the 70s. I used to have a problem with intensive processing causing CPU spikes to above 100C and then the thinkpad BIOS starts a thermal shutdown at 105ish. This has not happened since I went to the vanilla speedstepping.

One other fun fact, I tried the "upgrade proofness" of the build by upgrading to 10.6.4 - no problems whatsoever!

Wonderful stuff.

Silencer · **Posted:** Mon Jun 28, 2010 11:32 am

bozilla wrote:

I believe my current configuration uses the legacy.kext to add my PCIID string for the X1000. Are you saying I should update my legacy.kext to try to match my PCI string to the X1600 driver instead?

Here's the archive with my files related to video: T60p_Legacy_Kext_Boot_plist.zip

In the legacy kext you should use ATIRadeonX1000 and Controller sections under IOKitPersonalities. From com.apple.Boot.plist you can copy entire EFI device-properties string. It doesn't contain EDID and will work with all V5200.

bozilla wrote:

One other fun fact, I tried the "upgrade proofness" of the build by upgrading to 10.6.4 - no problems whatsoever!

Great stuff, haven't yet upgraded myself

bozilla · **Posted:** Mon Jun 28, 2010 1:11 pm

Is this the setup where you do EFI strings injection plus the ATIRadeonX1000 PCI_ID add-on? Do you still need to load ATINDrv for framebuffer support?

Where did you get the device-properties for the EFI string in your com.apple.Boot.plist? Mine contains my EDID specifically, is yours some magical EFI for the X1600?

Thanks man!

Silencer · **Posted:** Mon Jun 28, 2010 1:34 pm

bozilla wrote:

Is this the setup where you do EFI strings injection plus the ATIRadeonX1000 PCI_ID add-on? Do you still need to load ATINDrv for framebuffer support?

Where did you get the device-properties for the EFI string in your com.apple.Boot.plist? Mine contains my EDID specifically, is yours some magical EFI for the X1600?

No, you don't need ATINDRV, because it will be replaced by X1600 controller and vanilla framebuffers. You do need to replace Info.plist for X1000, the same as before (included in the legacy kext).

I've used plastikman's EFI string, decoded it and removed some stuff. It works like a charm with resolution switching. I haven't tested dual monitor setup. The only problem is that you can't use 60Hz, only 50Hz. But I prefer to use vanilla solutions.

plastikman · **Posted:** Mon Jun 28, 2010 3:00 pm

Silencer wrote:

No, you don't need ATINDRV, because it will be replaced by X1600 controller and vanilla framebuffers. You do need to replace Info.plist for X1000, the same as before (included in the legacy kext).

I've used plastikman's EFI string, decoded it and removed some stuff. It works like a charm with resolution switching. I haven't tested dual monitor setup. The only problem is that you can't use 60Hz, only 50Hz. But I prefer to use vanilla solutions.

Dual Monitors is confirmed. you have to set the bios to use LCD + VGA and boot the system up with the monitor connected.

teladoy · **Posted:** Thu Jul 01, 2010 3:48 am

silencer
I bough a T60p last night it has ATI 5250, I notice yours is 5250 and I have google it and haven't find no very encourage post that make me wonder.
Your guide is hard for a novice like me, even so I will like to try it.
Will this application help in anyway is called EvO DSDTse and I found in here: http://www.osx86.es/?page_id=5 the site is in spanish but has english support as well.
I should ask you this one before asking others questions, but I been wonder on the pfix command as well as other commands, after you type the the command in the terminal you press return or what? And them you click on the the red dot to close the terminal window?

Silencer · **Posted:** Thu Jul 01, 2010 8:40 am

teladoy wrote:

silencer
Will this application help in anyway is called EvO DSDTse and I found in here: http://www.osx86.es/?page_id=5 the site is in spanish but has english support as well.

If you read the guide, you will notice that I recommend this application for compiling and decompiling DSDT

teladoy wrote:

I should ask you this one before asking others questions, but I been wonder on the pfix command as well as other commands, after you type the the command in the terminal you press return or what? And them you click on the the red dot to close the terminal window?

I usually have a terminal window open to run various commands and I don't close it. You type commands as they are written in the examples (you can also copy/paste them) and then hit Enter (Return), command will run and you can then run the following commands.

teladoy · **Posted:** Thu Jul 01, 2010 10:44 am

Thank you but what about the video card yours 5200 mine 5250 would I be able to fix it.

Silencer · **Posted:** Thu Jul 01, 2010 11:48 am

teladoy wrote:

Thank you but what about the video card yours 5200 mine 5250 would I be able to fix it.
And will you encourage me to try your guide if yes I will read it more carefully.

It's not really a guide per se, but rather an extensive knowledge base on the subject. You should definitely at least read it, you will be able to answer a lot of questions.

As for V5250, I think this is something that can be solved, I've seen some custom kexts for that video, so if not vanilla solution, but something will work for sure.

bozilla · **Posted:** Fri Jul 02, 2010 12:55 am

teladoy wrote:

silencer
I should ask you this one before asking others questions, but I been wonder on the pfix command as well as other commands, after you type the the command in the terminal you press return or what? And them you click on the the red dot to close the terminal window?

Actually Teledoy,

The pfix script is just that. A script. The first thing it will ask is which /dev/disk to run on. Make sure you know which disk and partition has your OSX on it. If you only have one drive then more than likely it will be option 1. The script takes a while to run and will return you to the terminal prompt when it is done. Once you are back in the terminal prompt (ie you can type other commands etc) it is safe to close that window.

My t60p has a v5250 and the X1600 drivers mention on this page of the discussion works perfectly.

P.S. Silencer I solved my heat issues (combination of a fan cleaning, heatpipe hack and i had an error in my thermal management profile. Running nice and cool now!

DSDT Patching for Dummies - SnowLeo with 100% vanilla /S/L/E

Who is online