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 jvolkman

  • Rank
    InsanelyMac Protégé
  1. Can you list what you patched in the kernel so it can be done to subsequent updates until Apple releases native support?
  2. Is the custom kernel required for these? Any news on Mavericks?
  3. I'm in a similar boat with an EVGA X79 Dark and 4930k. I've been attempting to use Clover and haven't yet gotten past "Loading drivers".
  4. Also, Half-Life 2 seems to perform a *lot* better at 1920x1200.
  5. No problems here other than the standard AppleHDA issues. Fixed after replacing with the 10.6.2 version. Specs in sig.
  6. 10.6.3 Released !

    Updated without problems. Had to replace AppleHDA with the one from 10.6.2. Still need RealtekR1000SL.kext for ethernet.
  7. I could never get my EVGA to boot with MacPro4,1. The Gigabyte did it no problem.
  8. I don't think it's a faulty board. Like I said, I've experienced almost the exact same symptoms with 3 different boards from 3 different manufacturers. The chances of all three being defective are pretty slim. More likely it's due to a design all three have in common (they all use the same socket after all) that is interacting with Snow Leopard and something else in my environment/configuration.
  9. Everything works great. Minimal DSDT mods, and this board does everything i've tried -- sleep and native speed-step included. Before the gigabyte I had an EVGA board and had some issues. One thing to note with the new gigabytes is that the new USB3 and SATA3 stuff isn't supported in OS X.
  10. I suppose it could be. The only thing I can't change as easily is my location on the power grid. (although I guess i could take my comp elsewhere)
  11. This problem has been bothering me for a while. With native speedstepping, either configuring it myself via DSDT or using the BIOS' built-in SSDT tables, my motherboard emits noises. In Snow Leopard, one area where I can *always* reproduce squealing is when scrolling the iTunes cover-flow view. Even clicking and holding the scrollbar sends the machine into song. I've also experienced "hissing" from the machine -- much more subtle than the squealing, yet constant. These noises have plagued me through multiple power supplies, mother boards, i7s, and video cards. Not one of the components in my machine is definitely at blame. One interesting thing I've noticed is that the noises disappear when using the PState monitor posted at http://www.insanelymac.com/forum/index.php?showtopic=188954. So, for now, I've got that running full-time and managing my CPU. Does anyone else have these problems? Am I the only one? I've had an EVGA x58, an Asus p6x58d, and now this GA-X58A-UD5. All of them have made similar noises.
  12. I attempted to hack the AppleHDA binary as per The King's advice, but I couldn't get it working. Hopefully there will be more info once 10.6.3 comes out.
  13. Just wanted to chime in and say I had the same problem. Seems like more people might run into this once 10.6.3 comes out, since I believe this "Mac Pro Audio Update" only affects people with MacPro4,1.
  14. Where does that definition for that field come from? According to ACPIspec40.pdf, those fields are: The last two fields are what we're talking about. The spec is pretty general about them, and they don't appear to contain any useful data other than being opaque identifiers. I might be wrong, but if so is there somewhere that describes them as something more important? Do you have MacPro4,1 as well?
  15. I'm slightly confused about p-states. I have an i7-920, and VoodooPower is reporting 10 p-states: bus * 12-21. The default bus speed for this processor is 133, so the top p-state is 2793mhz. I'm running a slight overclock with the bus at 160mhz. Should I update the p-state table and multiply each multiplier by 160 instead of 133? If so, do I need to worry about the power (wattage) element? My current table: Package (0x06) { 2793, 130000, 10, 10, 21, 21 }, Package (0x06) { 2664, 130000, 10, 10, 20, 20 }, Package (0x06) { 2527, 109000, 10, 10, 19, 19 }, Package (0x06) { 2394, 100000, 10, 10, 18, 18 }, Package (0x06) { 2261, 83000, 10, 10, 17, 17 }, Package (0x06) { 2128, 76000, 10, 10, 16, 16 }, Package (0x06) { 1995, 63000, 10, 10, 15, 15 }, Package (0x06) { 1862, 57000, 10, 10, 14, 14 }, Package (0x06) { 1729, 47000, 10, 10, 13, 13 }, Package (0x06) { 1596, 43000, 10, 10, 12, 12 }