blix: Hi there. DSDTs are unique for every different system. Lenovo use the same system board as much as they can for systems in the same model. It saves them money you see. They tend to disable or not install components when they are not available for a particular model variant.

My model number is 7676-3PM. The specifications for it can be easily found on the Lenovo support website. If your system specifications differ from mine in things like front-side bus frequency (e.g RAM frequency) or main chipset then you'll have to roll your own DSDT. BTW: may I suggest always keeping a backup copy of your working DSDT. That way you can recover an installation if a boot failure creeps in from DSDT tweaks.

For those wanting some info on how I have things setup in my mac partition. I have a folder (/Awesome) in the root folder and in that I have Original, Updated, DSDT, Testing and Bundle folders. The Bundle folder is what you see in the ZIP bundles posted to this thread.

I use the Testing folder for kexts that I'm testing out. If something fails with a kernel panic it will happen in one of two stages in the boot and these stages can be seen in the single user boot mode (-s boot flag in Chameleon). First stage starts all the lower level parts of the OS and the second occurs after you type exit.

If you can boot to the shell prompt in single user mode you can easily remove the broken kext and replace it with a known working version from the Bundle folder. Remember to set the permissions correctly.

If you can't boot to the shell prompt because the kernel panic happens before that (like when SleepEnabler.kext isn't updated for the new version of OS X - *cough* - see next message) then you have to boot to the Snow OSX installation CD to copy the known good version from /Volumes/<disk label>/Awesome/Bundle to /Volumes/<disk label>/System/Library/Extensions/.

Same thing applies for DSDT problems though you'd be copying your known good DSDT.aml from the DSDT or Bundle folder instead.

Pretty easy stuff.

P.S. The only way you can be certain a new version of a kext is faulty is if it's the only thing you changed since you last booted the system. Change two kexts and you have to test both independently!