Jump to content


  • Content Count

  • Joined

  • Last visited

About agrafuese

  • Rank
    InsanelyMac Geek
  1. blackosx, thanks for the quick response to the update. the edited AppleHDA is working for me, but is throwing these errors. anyone else seeing this? repeats about 6 times on boot up.
  2. yeah, it seems to do some messing around with any UUID you put in. almost as if it is re-generating a new one based on the one you put in the com.apple.Boot.plist. very interesting...anyone know anything about this?
  3. GUIDE UPDATE I have stopped support for this guide, and will not be updating the main post any longer. I will append the following to the main post, but this is a reply for recent visitors as well: This guide is not intended for Snow Leopard. For everyone looking for an SL solution, I recommend researching the Chameleon Bootloader (preferably RC3, the most current version as of this writing), and loading your hardware via a DSDT patch. That is the most preferred way to run the 8800GT now, and is a verified 100% working solution. There are countless guides on how to make this happen by guys much more knowledgeable than myself. Doing a search will be sure to bring up lots of helpful information. If you don't want to try DSDT patching, the (old) EFI methods described in this guide may or may not still work for you in SL, but I offer no promises. As time goes on, this guide will be visited by fewer and fewer people, so really it's a wise choice to move on to more current methods that are more widely supported.
  4. agrafuese

    VoodooPower 1.2.3

    thanks mitch. i had 1.2.1 working fine and decided to move to 1.2.3, but it's freezing my MSI Wind. i'll give mini a try and see if it acts any differently. EDIT: ok, never mind, i got 1.2.3 to work after reading up on a solution for the Wind (it may have been mentioned here too, but it was easier to find over at the MSI Wind forums). i just needed to make all TstateControl values = false in the Info.plist. seems to have stopped the system freezes and video/audio playback issues, but i'm keeping my eye on it for now.
  5. agrafuese

    VoodooPower 1.2.3

    superhai, what's the story on the VoodooPower "Mini" kext?
  6. Just a heads-up to everyone here that wants their trackpad preferences working: marko_tmf's suggestion is the old way to get it to work. It's not really recommended because your modifications could get overwritten by future OS updates (not to mention that it's long-winded and unnecessary). The new and preferred method goes like this (Note to MrFluff: maybe put this into your next release?): After installing MrFluff's kext, go into Terminal and type: sudo nano /System/Library/Extensions/ApplePS2Controller.kext/Contents/Plugins/ApplePS2Trackpad.kext/Contents/Info.plist Then, inside the editor you will see a block of code that looks like this: <key>Sentelic FSP</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.driver.ApplePS2Trackpad</string> <key>IOClass</key> <string>ApplePS2SentelicFSP</string> <key>IOProbeScore</key> <integer>6000</integer> <key>IOProviderClass</key> <string>ApplePS2MouseDevice</string> </dict> Replace that ENTIRE block with this new code: <key>Sentelic FSP</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.driver.ApplePS2Trackpad</string> <key>HIDPointerAccelerationType</key> <string>HIDTrackpadAcceleration</string> <key>VendorID</key> <integer>1452</integer> <key>IOClass</key> <string>ApplePS2SentelicFSP</string> <key>IOProbeScore</key> <integer>6000</integer> <key>IOProviderClass</key> <string>ApplePS2MouseDevice</string> </dict> Save your changes with CTRL-X, hit Y to save, and then ENTER Finally, clear your kext caches by typing: rm -rf /System/Library/Extensions.mkext rm -rf /System/Library/Extensions/Caches/ rm -rf /System/Library/Caches/ Now, reboot with -f and you should have the trackpad prefpane
  7. I had someone ask me how to remove EFI strings, so I thought I'd leave the instructions here in case anyone else needed to know how to do it as well. You can do it a couple different ways, but here's how to do it quickly in Terminal: sudo -s [enter password when prompted] nano /Library/Preferences/SystemConfiguration/com.apple.Boot.plist This will take you to a text editor showing you the contents of your com.apple.Boot.plist. Look for these two lines: <key>device-properties</key> <string>YOUR LONG EFI STRING HERE</string> Using your arrow keys, navigate the block cursor down to each of those two lines and hit CONTROL+K on both. This will cut the corresponding line out of the script (quicker than hitting the delete button, trust me). When you're done, hit CONTROL+X and then Y, and ENTER to save the file. Now simply restart OSX, and you should boot up again without EFI strings. Note: If you're running OSX 10.5.2 and replaced your graphics kexts with the ones included in my tutorial here, you will have to replace them with the original ones (located in /System/Library/Extensions.update if you followed my tutorial properly). For the sake of keeping this post short, I wont say how to do that here, but if you need to know, either search the boards or PM me.
  8. Cheers to that man! Solutions can pop up in the most unlikely places. Gotta love it.
  9. I find that after a long hard day, Oregon Trail is the solution to MOST of my problems. AND guess what? It will definitely run in software mode...no fancy shmancy QE/CI bullsh*t! How about this...kill all of your Ge* and NV* kexts from the Extensions directory (don't replace yet). Clear kext cache. Reboot (with -f). It will go into software mode at 1024x768 (of course, since there are no kexts). Now, reinstall all of my kexts from scratch, properly chmoded/chowned. Clear kext cache once again, repair permissions, reboot (with -f again). Now tell me what happens. If you do those steps right and you STILL can't get it to work, something really fishy is going on. It's a conflicting kext or something else really rare. You have made sure to remove NVinject/NVKush, riiiiight? (btw, NVKush??? is that really the name? it better be a damn good kext with a name like that!)
  10. your bootup log output is normal (yeah, even the part about "NVDA::start(display) <1> failed"). so that's nothing. i dunno. we have the same video card. so, what are you at right now, 10.5.2 or 10.5.3? 10.5.3 uses new video kexts, and they work without hacking. someone here was talking about using my 10.5.2 kexts in their 10.5.3, but man, i don't know if i'd call that a fix. are you able to get into the OS with safemode? and a stupid question, but the card DOES work in windows, right? sorry, i know...i just had to ask. um, repair permissions? do those Ge* and NV* kexts all have proper ownership (the part in my tutorial that says to do chown and chmod)? i'm just throwing stuff out there for you at this point...i know it's gotta be a little mis-step somewhere. also, some people a few pages back were talking about IO80211Family.kext giving them problems, i think...? they were using kalyway, but who knows, maybe...? i have a feeling this is something easy, but i don't know what. i think you'll get it with some more messing around.
  11. Awesome! I'll put this up at the top of my tutorial If you followed the whole thing properly for your version of OSX, I would suggest trying the app that karaakeha1 just posted. If you still have problems, I'm going to guess it has to do with your NV* and/or Ge* kexts. You can try using the ones in my tutorial (typically for 10.5.2 users, but might be worth a try in your case, just to get things working).
  12. My pleasure! I'm always happy to see first-time posters breaking the seal on this thread Welcome to the community, and happy hacking!
  13. Ah, hmmm. I think maybe the reason is because when you updated to 10.5.3, the GFX kext files needed to be patched with the proper CPUID. The AMD patch included in both packs does not patch the CPUID for the kexts - it patches the frameworks only. However, the kexts from the 10.5.2 pack may be patched already for AMD (I can't remember, though I DID edit those kexts when I had an AMD machine), so maybe that's why they worked for you...? The only reason I am not sure about this is because I've already seen AMD users get this working for 10.5.3...maybe they ran Marvin's utility after doing my tutorial? Can anyone comment on this?
  14. With my system (see specs), chess is choppy when you move the board around. If there is anything that could be done about it, I definitely am not aware of it Others have reported that OpenGL games like WoW work fantastically. Some have even claimed that they run better than their PC counterparts. If you really want to test your system, try playing a real game in OSX - after all, that's the only real test. Though I do have to say, AMD for Leopard is very limited. No offense to anyone who has an AMD, but I've been down that road, and I can't tell you what an improvement Intel has been for me. Smartest investment I ever made....but that's for another thread at another time
  15. Seems pretty normal for your setup. I get higher scores, but this is because I have an intel machine. I had bad performance with my old AMD machine. I think other cards work okay with slower processors, but the 8800GT works a lot better with faster ones. ddrkdark is right though - the performance for this card in general is much lower than it should be on macs/hacks. But that's why I play games in windows