Jump to content

Silencers

Members
  • Content count

    87
  • Joined

  • Last visited

About Silencers

  • Rank
    InsanelyMac Protégé
  • Birthday 01/03/1982

Contact Methods

  • Website URL
    http://govnoblog.net

Profile Information

  • Gender
    Male
  • Location
    Riga, Latvia
  1. I usually formatted the partition with FAT32 before installing OSX, then Disk Utility was able to reformat it without any problems.
  2. You need to restore retail 10.6 image to a USB stick and then replace files there. You can also start with this linke http://osx86.sojugarden.com/installer/ It is possible, but it is a bit tricky. You need to make OSX partition an active partition from Windows and then install OSX there. Or you can do it from OSX (with Chameleon installer or whatever), but Windows 7 won't be booting, until you boot with Win7 DVD and go to console and deactivate Windows partition with DISKPART command-line tool. It's not very complicated, but it's also not straight-forward.
  3. Too many questions You should use 10.6.6 no matter what, there are different methods how to make video work there, just need to read more threads. I suggest to remove 10.5.8 and start with 10.6 from scratch. Yes, it is possible to install OSX on MBR. Look for the info. NTFS resizing can only be done from Windows. Don't try to do it in OSX.
  4. Check out RadeonHD.kext, it should work for you (http://www.insanelymac.com/forum/index.php?showtopic=190586), don't use pkg from 10.5. It might work, but it also might break your setup. There's no way to use Windows energy profiles with OSX, but there's now a great DSDT hack how to control fan speed. Check our this thread: http://forum.thinkpads.com/viewtopic.php?f=32&t=91141
  5. 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.
  6. From what I know, ATI should be working just fine. There are plenty of solutions, one of them is RadeonHD.kext, a project by some forum members, which provides pretty good support. A little patience, and you will find something. You need to install bootloader on to your HDD. I've described how to do it my DSDT guide: http://www.insanelymac.com/forum/index.php?showtopic=211705 Check it out, it's rather easy.
  7. Well, I always used vanilla OSX DVD copy, original 10.6.0. Restored it to USB flash, added bootloader and /Extra, booted from it, installed OSX, and then upgraded to the latest version (10.6.4) at the moment. There are plenty of guides on how to do it.
  8. You can find Thinkpad keyboard/trackpoint kext (driver) here.
  9. You can always try to see if SMBIOS.plist solution works for you. You should be able to override FSB values from there.
  10. 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. 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. 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.
  11. 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).
  12. 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.
  13. 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?
  14. 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.
  15. I'll check your legacy kext later. Most probably the problem is there, you don't have correct p-limit overrides there.
×