Jump to content

Search the Community: Showing results for tags 'sleep trick'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace


  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 1 result

  1. OK, so the goal here is/was two-fold. 1) Not fill the 10.8.3 thread with our 7xxx discussions. 2) Consolidate any testing results, thoughts, ideas, informations, theories, rumors, whatevers...In hopes we can boot without using the "Sleep Trick" (I hate that name BTW, I'm open to anything better :wink2: ). Oh, any other 7xxx cool stuff, updates, tweaks, etc. is all good and is "on topic". However this is not a support thread. If and when Apple actually releases Macs that have these GPU's, it may become much easier to figure out what we need to do different, or maybe a bootloader fix to handle differences in vbios vs. EFI. For right now with 10.8.3 in beta, we are but a small few, so I would expect more progress to be possible after an official release. Also this is not a "how to" thread. If your posting here, you should already have full HW acceleration working, CI, QE, transparent Chess ripples, yada, yada. Basically 100% "Bad Ass" except for having to sleep and wake you Hack at boot to get the desktop to show!. To start off, I'm just copying a post I was about to put in the 10.8.3 thread, but realized it was not the appropriate place. Quoted in full, including the part where I apologize for doing so Me neither, but I don't expect Apple to fix it, we will! Right now there is just a small handful of us using 7xxx cards in OSX, with our shared knowledge mostly consisting of either "it works!" or "help, how do I make it work?" There are quite a few settings that can be changed in the controller's plist. The ones actually showing for certain FB's are those that are different from default. So you'll see a few options listed for each framebuffer, then what appears to be a "default" set. I honestly don't know what half of them do (OK more than half). Easiest would be if any 7xxx card would boot straight to desktop, then we could see what framebuffer it uses and what settings maybe different for it. If it's not that easy and tinkering with various parameters is needed, the more people out there to try things, the faster it will go. So for example here are the "default" options in the controller. <key>aty_config</key> <dict> <key>CFG_CAA</key> <integer>0</integer> <key>CFG_FB_LIMIT</key> <integer>0</integer> <key>CFG_GEN_FLAGS</key> <integer>0</integer> <key>CFG_INT_SSPC</key> <integer>25</integer> <key>CFG_NO_HDCP</key> <false/> <key>CFG_NO_PP</key> <false/> <key>CFG_USE_FBC</key> <false/> <key>CFG_USE_STUTTER</key> <false/> <key>DALReadDelayStutterOff</key> <integer>4</integer> <key>DALUseUrgencyWaterMarkOffset</key> <integer>0</integer> </dict> <key>aty_properties</key> <dict> <key>PP_ActivitySamplingInterval</key> <integer>1000</integer> <key>PP_DALPowerLevel</key> <integer>1</integer> <key>PP_DisableCAC</key> <integer>0</integer> <key>PP_DisablePowerContainment</key> <integer>0</integer> <key>PP_DisableULV</key> <integer>0</integer> <key>PP_DriverCalculateCACLeakage</key> <integer>1</integer> <key>PP_HighSamplingInterval</key> <integer>200000</integer> <key>PP_MCLKStutterModeThreshold</key> <integer>40000</integer> <key>PP_PowerGatingDisable</key> <integer>0</integer> <key>PP_R600ActivityHysteresis</key> <integer>5</integer> <key>PP_R600LoweringHighPercentage</key> <integer>25</integer> <key>PP_R600LoweringMediumPercentage</key> <integer>10</integer> <key>PP_R600RaisingLowPercentage</key> <integer>10</integer> <key>PP_R600RaisingMediumPercentage</key> <integer>25</integer> <key>PP_R600VotingRightsClients</key> <integer>12583475</integer> <key>PP_UserMaxClockForMultiDisplays</key> <integer>1</integer> and the FB specific options: <key>ATY,Chutoro</key> <dict> <key>aty_config</key> <dict> <key>CFG_USE_STUTTER</key> <true/> </dict> <key>aty_properties</key> <dict> <key>PP_DriverCalculateCACLeakage</key> <integer>1</integer> </dict> </dict> <key>ATY,Hamachi</key> <dict> <key>aty_config</key> <dict> <key>CFG_USE_SM</key> <true/> </dict> one of those FB specific options CFG_USE_SM does not appear in the larger default list. Now maybe I completely wrong here, which is very possible, but in my mind that tells me that the possible options that could be added to the controller's info.plist is actually much larger. looking at the controller in a hex editor and searching for one of the above options like "PP_DriverCalculateCACLeakage" we can find it, along with many more "option looking" entries all around it. Here is just a excerpt: PP_PCIeLaneOverridePP_DALPowerLevelPP_DisableEngineTransitionPP_DisableMemoryTransitionPP_DisableVoltageTransitionPP_CGCGDisablePP_MMClockGatingEnabledPP_MemorySSEnabledPP_EngineSSEnabledPP_DynamicPCIEGen2EnabledPP_MGCGDisablePP_MGCGCGTSSMDisablePP_LSCGDisablePP_PowerGatingDisablePP_StayInBootStatePP_DisableLightSleepPP_DisableDPMPP_UserMaxClockForMultiDisplaysPP_DisableSMUUVDHandshakePP_DisablePCIePerformanceRequestPP_ThermalAutoThrottlingEnablePP_UVDDPMPP_VCEDPMPP_SAMUDPMPP_ACPDPMPP_MCLKRttModeThresholdPP_DisablePowerContainmentPP_DisableCACPP_DisableSQRampingPP_FastWaterMarkTresholdPP_NearTDPDecPP_AboveSafeIncPP_BelowSafeIncPP_TDPSafeLimitPercentPP_MaxPSPercent_HPP_MaxPSPercent_MPP_DriverCalculateCACLeakagePP_CACConfigurationRequiredPP_EnableCACLongTermAveragePP_LTAWindowSizePP_LTSTruncatePP_UsePowerBoostLimitPP_RegisterWriteRingSizePP_SQRampingThresholdPP_DisablePPMPP_Apple_Bootcamp_EnablePP_FanControlCycleDelayPP_PhmSoftPowerPlayTablePP_ASPML0sInactivity Some of them look very interesting. Again, kinda thinking out loud and I am no GPU driver guru. I apologize for going way off topic with a huge post. Please don't respond to it here. I'll start a ATI/AMD 7xxx development thread and copy it and a few others from here to it as a starting point, any further discussion can can be done there.