Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About gmacman

  • Rank
    InsanelyMac Geek

Profile Information

  • Location
    Bay Area, California
  1. Do you have an AppleHDA.kext in your Extra folder? The one I use is from Eliade's original (again on the first post).
  2. As usual I waited a while before doing the 10.7.2 update. And at this time I think it's even easier to upgrade (if you haven't already done the update). But I should say that I'm only interested is basic sound, so please only follow these instructions if you too are okay with just sound out of the regular Line Out (Green) jack. Okay, so all I did was the following: 1. MAKE A BACKUP!!! I may sound like a broken record since I say this almost every time, but I highly recommend using two hard drives in a hackintosh. Use one as your stable system drive and the other as your update test drive. I use SuperDuper to make a fully bootable backup (although you must reinstall Chameleon on the new backup for it to truly be a standalone bootable drive). So, anyway go ahead and do your backup (which for my large drives can take up to 3 hours). 2. Install Chameleon on the newly created backup drive (any installation means is fine. I used the most current Chameleon v1684 and installed via Chameleon Wizard). 3. Test the new drive (I absolutely make sure it's 100% standalone bootable by removing the old drive, or at least uplugging the sata cable, and then only booting up with the new copy drive). 4. Run Software Update to install 10.7.2 5. Rerun the original sound fix from Eliade's pack (from the first post). Basically it's just copying over the three files (ALC885_889a.kext, layout885.xml, and Platforms.xml) And basically that was it.
  3. bigpoppa206 thanks so much. These added sound features (pardon the pun) sound cool, so I'll need to give this a try. I actually just went ahead while waiting for your reply and just reinstalled the sound commands from Eliade's original (the replacing the xml files thing) and that got my sound back. However, those of course do not provide the improved sound options you touted, so as mentioned I'll give those a try this weekend and see if they work. But for those who just want basic sound back after the 10.7.1, you can just follow the exact same directions you have for the original install of 10.7. Cheers, Steve
  4. So I just want to verify the steps involved on your fix. Currently I have an AppleHDA from Eliade that is in E/E, so the fix you suggest is to get the AppleHDA (from here) and replace the one in S/L/E with it and then go back to the last working LegacyHDA from my SL drive and install it in E/E. I suspect I must also then delete the current AppleHDA from Eliade that is in E/E. Is this correct?
  5. Hey guys, I'm back. Been running SL but finally decided to update to Lion and was soooooooo thankful to see Eliade had written a guide for Lion. Anyway, everything worked perfectly until I just updated to 10.7.1 and then I lost sound (everything else is fine). Any suggestions? Do you think I just need to redo the sudo commands for the xml files and the ALC885_889a.kext? Cheers, Steve
  6. Got it. Thank you both. I had to laugh at my own stupidity a bit. I'm so old in college I had a Mac Plus as my first computer. It's easy to forget that an OS does not necessarily require GBs of space. On a side note, I'm just really happy that my Hack is getting so clean (or pure if you will) between the speedstepping and the plethora of dsdt fixes I've done so far. A good deal of work, but well worth it.
  7. I was afraid I was going to get that answer. I do realize I need to invest a bit more time on this to get it right. As stated, I only run OS X so I'll have to do some additional work to load another OS. Can I get this info by running it (the OS I mean) through Parallels? That way I don't have to add a new HD and partition it, load the OS, etc.
  8. Okay, so with much appreciated help from swavek and valv I believe I have a correct _PSS section for my Q6600. For the _PSD section I am merely taking the one from the instructions on the first page as I see nearly all other dsdt files have the same thing. My main concern now is the correct way to have the _CST. I only run OS X on the Hackintoshes (and of course my real Macs) so I don't have access to Linux or Windows to see the SSDT (not to mention I'm not 100% sure what I need to be looking at). I did get the MacPro 3,1 SSDT that are available but within the folder are SSDT and then SSDT-1 thru SSDT-18. Should I be using the _CST section from the generic ssdt? Or is there a better way to get the info required? Scope (_PR) { Processor (CPU0, 0x00, 0x00000410, 0x06) { Name (_PSS, Package (0x04) { Package (0x06) { 2700, 56694, 10, 10, 0x91E, 0 }, Package (0x06) { 2400, 48100, 10, 10, 0x81B, 1 }, Package (0x06) { 2100, 40080, 10, 10, 0x717, 2 }, Package (0x06) { 1800, 32633, 10, 10, 0x614, 3 } }) Name (_PSD, Package (0x05) { 0x05, 0x00, 0x00, 0xFC, 0x04 }) // remainder of the scope (_CST) needs to be completed EDIT: The one I think I can use is as follows: Name (_CST, Package (0x02) {One,Package (0x04) {ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x0000000000000000,0x00,)},One,One,0x03E8},})
  9. Okay, I think I'm getting this now. With each multiplier matching the number of p states I see within the P state changer. For example in the P State Changer I see 2700, 2400, 2100 and 1800 so with my 300 FSB I should select my current 9, then 8, 7, and 6. But why didn't the Voodoo P-States button do anything? Or should I not really care since at least the fog is beginning to lift.
  10. Thanks swavek. Okay, added VoodooPState.kext to /E/E, reboot and then launched P-states calculator. At first it showed the following: Then I changed the Bus Speed to 300 which I know is what I'm running and see this: So I get they are changing and I'm assuming I am suppose to use the one I "made" by changing the Bus Speed to the correct number I've got in my BIOS. I did try to hit the Voodoo P-States button but nothing happened, no changes either with the default data or with my 300 I put in. I'm guessing I'm doing something wrong there (I see that the kext did load so that can't be the issue). orig_shot.tiff mycpu_numbers.tiff
  11. I'm afraid after having read and reread this thread I'm still a bit confused. I've looked at other dsdt files from people who have similar mobo and the exact same cpu as I have (Q6600) and I find very different info (and yes I understand that some is dependent on the speed they are running and thus the FID and VID). But I find other differences that are not mentioned in the instructions. For example these two PSS sections below are both from people who have Q6600's. Obviously the FID/VID combo entry is different but why are the other entries within each Package (0x06) different? And so, which one do I use? Or more correctly, how do I find the right one to use? The fact one is cosmetically using Name and the other Method does not concern me. What I'm trying to determine is within the Package (0x06) areas. Here's one: Method (_PSS, 0, NotSerialized) { Return (Package (0x04) { Package (0x06) { 0x0D5C, 0xFDE7, 0x0A, 0x0A, 0x0926, Zero }, Package (0x06) { 0x0BE0, 0xFDE8, 0x0A, 0x0A, 0x0822, One }, Package (0x06) { 0x0A64, 0xFDE7, 0x0A, 0x0A, 0x071D, 0x02 }, Package (0x06) { 0x0A64, 0xFDE7, 0x0A, 0x0A, 0x071D, 0x03 } }) } And here's the other Q6600: Name (_PSS, Package (0x04) { Package (0x06) { 2403, 0, 10, 10, 0x0928, 0 }, Package (0x06) { 2136, 0, 10, 10, 0x0824, 1 }, Package (0x06) { 1869, 0, 10, 10, 0x0720, 2 }, Package (0x06) { 1602, 0, 10, 10, 0x061B, 3 } })
  12. DSDT fixes for Gigabyte boards

    I'm sure that was probably it. My bad. I was actually using DSDTSE which is pretty old. But again I want to thank you since my initial goal is to clean up my own by seeing what things I can safely remove and the DSDT you provided was nice and slim.
  13. Many thanks. That's been my story as well. "It it ain't broke..." However, I do wish to clean things up a bit and want to at least see what items I have that others do not. Currently my dsdt is significantly longer than what others on the dsdt fix thread have. I know enough now to get the CPU part working, but I'm more interested in getting some of the garbage out. Anyway, again (and as always) thanks for your help.
  14. @d00m42 Can you or some of the other seasoned vets post your currently working DSDTs. I've been spinning my wheels trying to clean up mine using the DSDT fixes for Gibabyte boards thread but I'm having a tough road the one someone gave me is so full of errors it doesn't even compile. I'd like to at least look at our mobo dsdts so I can really see what things I can edit out before I start on getting the CPU edits in there (and SMBUS, etc.). The only edits I have were the adds from your original guide. Thanks
  15. DSDT fixes for Gigabyte boards

    I appreciate the help but I just tried to compile the dsdt and I get errors. However, your file is what I'm looking for in terms of trying to weed out the garbage in my current dsdt. I can't quite figure out why your dsdt won't compile and of course don't wish to edit mine until I know yours truly works.