compute unit configuration reader
compute unit configuration reader
THIS SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.
IN NO EVENT SHALL AUTHOR, OR ANY PERSON BE LIABLE FOR ANY LOSS,
EXPENSE OR DAMAGE, OF ANY TYPE OR NATURE ARISING OUT OF THE USE
OF, OR INABILITY TO USE THIS SOFTWARE OR PROGRAM, INCLUDING,
BUT NOT LIMITED TO, CLAIMS, SUITS OR CAUSES OF ACTION INVOLVING
ALLEGED INFRINGEMENT OF COPYRIGHTS, PATENTS, OR TRADE SECRETS.
This tool can be used to read information about active and disabled CU units in Hawaii, Tonga and Fiji.
Tool is based on public sources with some amount of guess-work. Any data interpretations are not official.
Tested on all supported chips.
It's still interesting to get output from cuinfo tool from ANY Tonga and Fiji / Fury chips.
There are a well-known tool named Memory Info uploaded by some kind guys:
Download it and copy to some folder.
CUinfo v1.4: outdated
CUinfo v1.5: outdated
Download it and unzip into Memory info's folder. This tool uses DLLs from Memory info package for direct access to HW. Elevated privileges required because of that. This tool is not a virus and is not malicious in any kind. Tools may crash just like Memory info do if you don't have compatible graphics card, run it at limited user account and so on. Windows 8 compatibility is limited to ULPS-disabled configurations.
Make sure no single 3D application is running while trying this tool!.
If you've got the files from untrusted source, please check exe's SHA1 hash to make sure it wasn't altered:
Please run this tool, copy it's output to clipboard and post it here together with basic info about your card's model.
If you're running big CF setup, all information could not fit the window, so please don't make screenshots. Just select, copy and paste text info from the tool's window.
Data readout may not work in CF configuration with ULPS enabled. If you're getting "DevID " on some adapter, consider all following data from this adapter to be incorrect. Turn off ULPS to read data correctly.
Explanation of data read by cuinfo:
Adapters detected: 1 Card #1 PCI ID: 1002:67B0 - 1043:0466 00 DevID [67B0] Rev  (0), memory config: 0x500036A9 Hynix Hawaii-class chip with 11 compute units per Shader Engine SE1 hw/sw: F8000005 / 00000000 [...........] SE2 hw/sw: F8000005 / 00000000 [...........] SE3 hw/sw: F8000005 / 00000000 [...........] SE4 hw/sw: F8000005 / 00000000 [...........] 44 of 44 CUs are active. HW locks: 0 / SW locks: 0. All CUs in this chip are already active.
SEn corresponds to Shader Engine n (one of 4 SE's in total).
hw/sw digits are raw readouts of hardware and software CU configuration.
dotted map like [...........] represent status of each CU in SE, from maximum number of the left to 1 on the right. Dot stands for an active core, 'x' for HW-locked and 'o' for SW-locked. You may also encounter 'X' if both locks are engaged (unlikely).
Different dot patterns may indicate real ASIC screening information (positions of faulty or disabled cores in each SE).
* minor bugfix in R/W and R/O reports.
+ Added DevID + RevID readout;
* improved HW locks interpretation based on first Fiji PRO readouts.
1. How to understand is my card unlockable or no?
Current version of cuinfo tries to speak human language. Last strings for each adapter describe possible unlockability or inform about a fully enabled chip.
2. How do I unlock?
This tool only provides information about core configuration. Please read BIOS reflashing threads about actual unlocking techniques.
3. Is this info official or reliable?
NO. Readings are based on open source driver and are partially guessed.
4. How did you found out how to read out this information?
I'v examined core configuration process in GPL sources of latest mainline Linux kernel (4.2-rc). It's legal to explore and learn open source software. However, no GPL code from OS driver is used in this tool.
5. I need sources.
Tool's sources are now proprietary. Source code may be released as open source later.
6. What "override is possible at your own risk" means in human language?
For some reason HW locks were left in writable state so they can be overwritten with arbitrary value. However, at least some of HW locks represent real binning information about failed blocks. Activation of these failed blocks may lead to unpredictable effects.
Thanks for reading!
Edited by tx12 - 8/1/15 at 11:18am