Jump to content
InsanelyMac Forum


  • Content count

  • Joined

  • Last visited

About kako007

  • Rank
    InsanelyMac Protégé
  1. According to the Mavericks DP release notes when you try to enable iCould keychain from system preferences you could be presented with a blank dialog box. Then it mentions the workaround is to force quit system preferences and try again. I have tried beyond what is considered a reasonable number of attempts and keep getting the same issue. How is every one else's experience with this? Any effective workaround?
  2. kako007

    Anyone try installing Mavericks DP4

    When it's stuck on the spinner unplug your monitor for a few seconds then plug it back in. Tell me if that fixes the issue.
  3. kako007

    Anyone try installing Mavericks DP4

    AMD 7970M Cause of my issue: When both my external monitor (HDMI) and laptop internal screen are being used, it will freeze during boot. Workaround: I have to unplug the HDMI display and plug it back in. This unfreezes the boot process. This issue is new for me in DP4.
  4. kako007

    Anyone try installing Mavericks DP4

    It has been working fine with full QE/CI, sleep and etc for me until the DP4 update. After DP 4 It can only start in safe mode. In regular mode it just freezes with an unrelated log message during boot. Ivy i7 3630QM AMD 7970M
  5. Using "Buri" framebuffer. HDMI works OOB. Internal LCD doesn't work OOB and requires patching the frame buffer. In order to fix that modify the first connector of Buri, from: 02 00 00 00 00 01 00 00 29 05 01 00 10 00 05 05 to: 02 00 00 00 40 00 00 00 09 01 00 00 00 03 00 05 This is the result of reading http://rampagedev.wordpress.com/kext-editing/editing-atiamd-framebuffer-personality/ and the referenced articles. I also got direct help from the author of rampagedev. The offset of the frame buffers in the Mavericks ATI7000Controller.kext is different from what's posted in rampagedev and other sites. So you have to search for the connector HEX data directly rather than looking up the framebuffer offset. Hope this helps.
  6. I have the same exact issue with my AMD 7970M in both Mountain Lion and Mavericks and have not been able to solve it. I also tried swapping a friend's nVidia 680M in there and even though it pretty much worked OOB, I had the same color banding/depth issue. I have experimented a lot with modifying the framebuffer (Buri in ATI7000Controller.kext) to no luck. The following is the original connector and the modified one that is working fine but has the same color depth issue with my 7970M card: Original: 02000000400000002905010010050505 Modified: 02000000000100002905010010000505
  7. I noticed that in both DP1 and DP2 some sites that use any of the popular plugins out there or even sites that solely rely on HTML5 Audio/Video capability have become glitchy. Some times it works, sometimes it doesn't. This issue went away for me once I disabeld Safari --> Preferences --> Advanced --> Stop plug-ins to save power. I am fairly certain this is a new feature in Mavericks/Safari 7. Seems like major bugs for this feature are not flushed out yet.
  8. I have also noticed Apple has been slowly refactoring references of ATI to AMD in various Kexts.
  9. DP2 has fixed this issue. HMDI audio with my 7970M is also working OOB.
  10. kako007

    Image corruption safari and quicktime

    DP2 has solved this issue for me and HDMI audio with my 7970M is also working OOB.
  11. The topic says it all!. Finally they fixed it. I have an ATI 7970M and the HDMI audio is working perfectly now with AppleHDA. Also there was an Image corruption issue with Safari, Quicktime and etc with ATI 7000 that is now solved as well.
  12. kako007

    Image corruption safari and quicktime

    Which Framebuffer are you using or is being loading automatically?
  13. I'm using Clover. MacPro SMBIOS works fine. It's probably irrelevant but with MacPro SMBIOS my cpu is stuck in turbo mode all the time. But as I mentioned above the corruption problem is still there.
  14. The custom SMBIOS doesn't seem to work for me. I did copy and rename the Mac13,2 resource plist to for example Mac-FC02E91DDD3FA6A5. Then in my SMBIOS I used the new board ID and iMac13,3. When I boot it immediately says: This version of mac is not supported on this platform: Mac-FC02E91DDD3FA6A5 I also tried with new board ID and iMac13,2 but same issue. I have a feeling somewhere we need to add the new board ID before it allows us to use it?
  15. I see. I'm gonna try this when I get home. if I understood correctly Safari has a direct reference to Mac-FC02E91DDD3FA6A4 and some other built-in board IDs. By creating my own ID, it will no longer match the list of IDs Safari is referencing?