Jump to content

eep357

eep357

Member Since 08 Feb 2011
Offline Last Active May 29 2014 02:27 AM
*****

Topics I've Started

User Feedback, Suggestions and Feature Requests

21 March 2013 - 11:13 AM

The title says it all I think!

Bug Reporting

21 March 2013 - 11:10 AM

Hello Pandora's Box Beta testers! Here is a location to report any bugs, and as a beta, there will be bugs.

Please keep the comments here on topic, there are other topics to discuss any suggestions, opinions or support issues not related to a bug in the application.

Note: Please include any possible photos, screenshots, installation or system logs, etc so that we may be able to determine the cause and/or solution to your problem.

HD 7xxx-Can we eliminate the Sleep Trick?

18 January 2013 - 09:42 PM

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 :)



Still no straight boot with 7870. I'm not giving up hope yet.

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 <key>CFG_USE_SM</key> 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_UsePowerBoostLimitPP_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.

iMessage/Messages Fix-How To

10 January 2013 - 06:48 AM

HOW TO FIX MESSAGES APP
work in progress-subject to change



This is only for those of you who are running Mountain Lion and getting this error since the Messages Beta for Lion ended on 12/14/12, but can still sign into other services like iCloud, App Store, etc.

Attached File  Messages-Not SignIn.jpg   40.69KB   466 downloads


To fix this, we need an added value to the NVRAM which as of the time of this writing, can only be done by using the latest revision (r980) of boot loader by Slice, dmazar and others: Attached File  Clover.png   45.83KB   896 downloads
To get the most recent installer package, we"ll use the tool created by STLVNUB: "Clover Grower" which can be downloaded here. You'll need Xcode's Command Line Tools installed, available for download in Xcode's preferences. The full list of instructions and options can be found here. Highly recommend reading them since every person's setup is different and there are many additional features you may want to explore. Only the basics here.

Once you've downloaded Clover Grower, open Terminal.app from /Application/Utilities/Terminal.app. From your downloaded Clover Grower, drag and drop CloverGrower.command into terminal window and hit enter. Follow the prompts and enter password, Yes, etc. when asked. I recommend using all default settings unless you know what your doing. The process may take a little while as additional tools to compile are installed by the script. Once it's all done you should now have a folder with the package installer in it looking like this:
Attached File  CloverGrowerV4.9.jpg   110.34KB   1274 downloads

Next prepare a USB thumb drive to install it onto. Use Disk Utility and format it as FAT32 with a MBR partition scheme. You can install the boot loader to your main hard drive later once your sure it all works and are comfortable with the configuration.

Run the Clover package installer, leaving all settings as default except choose your thumb drive as the install location.

Attached File  Install Clover v2 rL980 x32 x64 EFI bootloader.jpg   65.77KB   858 downloadsAttached File  fat.jpg   72.25KB   597 downloads


Once the install is complete navigate to your new Clover USB drive and open the config.plist with text editor (RT Click and "Open With")
Attached File  FAT32files.jpg   94.89KB   1692 downloads

This plist is like org.chameleon.Boot.plist and smbios.plist all in one file. Some options are the same, some are similar but have different names, and some are new for added config ability. This is where some system specific changes maybe needed, but first try simple leaving everything as is, and will only add info from our current smbios and what's needed for messages fix. Copy all info from your smbios into config.plist, and then you will need to change the names of the values inside each <key></key> to match the new format. Here is how they need to be named in Clover:
Attached File  SMBIOS.png   100.71KB   3058 downloads

Additional examples can be found in /EFI/doc/ inside Clover drive.

For UEFI boot and additional Graphics config, follow dmazar's instructions here

For the Message part, first get your current serial which is in the smbios you just copied, and can also be found in system information:
Attached File  Mac Pro-Serial.jpg   55.98KB   2939 downloads

Now we add a new entry to config.plist that includes that 11 digit serial #, but we need to append 6 more digits onto it to make it a 17 digit #. So for example RM9MYSERIAL becomes RM9MYSERIAL234567 and the entry looks like this:

<key>RtVariables</key>
<dict>
  <key>MLB</key>
  <string>RM916W05EEP3574PC</string>
</dict>

In the image below you can see inserted into the list with some of the entry before and after visible to give an idea how it should look.
This is mine for my own PC, not yours, it's for frame of reference on how the code is inserted and should not to be copied in full if you want anything to work!
Attached File  config.plist2.jpg   77.15KB   1764 downloads
If you use a patched DSDT, copy it to the root of your main OSX drive.

Try it!

Please, please, please read all the instructions for Clover here before asking any Clover related questions!

Edit or maybe Warning: One note, a few people have had message saying "account locked, call customer service" either right away or even after a successful login and a reboot. Not sure the cause, but I recommend rebooting twice before trying to log into Messages incase there are nvram values such as platform-uuid that if you are not specifying them in config.plist, Clover will set them at shutdown to be applied on the next reboot, which would then be the second time your booting using Clover.--Further reports on this have indicated success after a credit card has been tied to appleID account through the appstore, or when a small $1 app is purchased.

Credits: The testing, brainstorming and collaborating involved was an unprecedented (in recent history) effort by the entire community, with valued efforts by too many people to list, but a special thank you to ElNono and flux84 for putting the final pieces together, to Slice for Clover and dmazar for pushing and update so quickly! Great work everyone!!!

How can I see if I am running 32bit or 64bit? How can I change this?

13 December 2012 - 02:49 AM

To see if your currently running 64 bit or 32 bit kernel:

Mountain Lion- You already are and nothing to check.

Lion and Snow Leopard- The easiest way is to go to the Apple logo in the Menubar and click About This Mac > More Info> System Report or go to Apple logo in the Menubar and hold down the option key, the "About This Mac" item will change to "System Information" and you can click it. Either way should get you to the System Info screen:
Attached File  MacBook-1.jpg   74.18KB   74 downloads
Click on Software as seen in the left column as seen in the picture above. It will say "Yes" if running 64-bit and "No" if running 32-bit. This image is taken from a early 2008 MacBook which is not capable of running 64-bit kernel, or Mountain Lion for that matter.

Can This be Changed?

Lion and Snow Leopard are capable of running either 32-bit or 64-bit kernel, not to be confused with 32/64-bit kernel extensions, where 64-bit extensions can run on a 32-bit kernel, but 32-bit extensions will not run on a 64-bit kernel. So to run 64-bit, all your extensions loaded need to be 64-bit capable.

There may be cases where you need to specify if you wan't one or the other to load, usually due to hardware or other compatibility reasons. To do this on a temporary basis, at the Chameleon boot promt type:

for 32-bit
arch=i386
or for 64-bit
arch=x86_64

To make the change more permanent, open the org.chameleon.Boot.plist in your /Extra folder and add either of the above (only one, not both) into the string after kernel flags like this
<key>Kernel Flags</key>
<string>arch=i386</string>
© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy