Hawaiinfo core config information reader
UPD: hawaiinfo v1.2 with detailed reading and multiple adapter (CF) support.
I'd like to try to get (possible) core config information from 290(x) chips.
It's interesting to get output from hawaiinfo tool from ANY 290 and 290X chips.
For unlockable 290's its interesting to get reading from running BOTH locked and unlocked BIOSes.
There are a well-known tool named Memory Info uploaded by some kind guys:
www.mediafire.com/download/voj4j1rlk0ucfz4/MemoryInfo+1005.rar
Download it and copy to some folder.
(outdated) And here is hawaiinfo tool:
http://rghost.ru/50367865
If you've got it from somethere else, please check exe's SHA1 hash to make sure it wasn't altered:
21ec161f47fbcaea0b4ee10defe03da6c4bf6a24 hawaiinfo.exe
(outdated) UPDATE V1.1: Experimental hawaiinfo v1.1 tries to get more detailed reading.
Make sure no single 3D application is running while trying hawaiinfo v1.1.
http://rghost.ru/50375416
If you've got it from somethere else, please check exe's SHA1 hash to make sure it wasn't altered:
11ab2edab8c454203c31309354ec0cc7bc16556e hawaiinfo11.exe
UPDATE V1.2: hawaiinfo v1.2 with detailed reading and multiple adapter (CF) support.
Make sure no single 3D application is running while trying hawaiinfo v1.2.
http://rghost.ru/50379538 (may be outdated)
refreshed link:
http://rghost.ru/51128084 or
http://rghost.net/51128084
If you've got it from somethere else, please check exe's SHA1 hash to make sure it wasn't altered:
542252e0d0a0f1f97d8c64ee5a05dbc71e3eb880 hawaiinfo12.exe
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.
Please run this tool, copy it's output to clipboard and post it here together with basic info about your card:
- is it originally 290 or 290X;
- if 290, is it unlockable ?
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 "Memory config: 0x00000000" 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 hawaiinfo:
Rx1 corresponds to
HW core status and
Rx2 to
SW core status.
x = [A,B,C,D] - one of 4 Hawaii's shader engines.
Rx1 HW lock status:
Look at the 2 high bytes of Rx1, they should read as FXXX:
F800.... - no locked units. Anything but F800.... results in presence of disabled cores.
Rx2: SW lock status, decoded in the same manner as Rx1.
Non-zero Rx2 indicates software-engaged core lock (by BIOS or via driver).
In short words:
1. If your card reads F800yyyy at Rx1 for all x, its either 290X or unlockable 290 (215-0852000). If it's currently locked you can unlock it by flashing stock 290X BIOS at your own risk. See also N3.
2. If your card have an extra '1' bit in F800 half of Rx1, your card is locked 290 (215-0852020) and cannot be unlocked via stock 290X BIOS.
3. If your card reads F800yyyy at Rx1 for all x and Rx2 reads F801yyyy, you have 290X chips locked by BIOS to 290. You can unlock it by flashing stock 290X BIOS at your own risk.
4. Non-F800 Rx1 may indicate real ASIC screening information. Please post here your dumps with non-F800 chips.
FAQ:
1. Why it may be useful to upload dumps to the forum?
Even the same type of chip may give various readings. For present moment its very interesting to get some statistics about locked 290 chips. Exact Rx1 dumps together with some info about your card (like its brand or manufacturing date) are needed for that. Predominance of F801.... readings in locked chips is somewhat strange.
2. Is it true my all-F800xxxx chip from 290 is indeed of the same quality as in 290X?
Its true what F800xxxx chips doesn't have failing cores inside it and is fully functional as 290X. It's still possible it was downgraded to 290 via some kind of last-minute thermal screening. This can lead to worse thermal characteristics of unlocked chip when compared to 290X.
3. Will my 290 card burn out if I'll unlock that extra cores?
Unlocked card could have the same power consumption as stock 290X card. Reference design cards should be able to withstand extra power consumption caused by extra load from unlocked cores. However, hypothetical future custom designed 290 cards may feature power sources tightly optimized for 290 limits to make them cheaper. Such cards's VRM may burn out because of extra 290X-like load. Even a reference card may exhibit worse thermal characteristics and harder throttling in an unlocked configuration.
4. Will my unlocked 290 card have a shorter life?
If core unlocking will lead to higher working temperature or you're pushing the card to OC limits, especially involving over-voltage, your card's life may be shortened. This is true for any OC activity leading to higher working temperatures regardless of core unlocking. Good cooling solution should remove that negative effects of OC. Over-the-specification voltage and high temperature are worst enemies of complex semiconductor's longevity and reliability. Still, technical obsolescence should drive your card out of game much sooner than thermal wearing.
5. How did you found out how to read out this information?
I'v examined Hawaii core configuration process in GPL sources of latest Linux kernel (git head and 3.13-rc1). It's legal to explore and learn open source software.
Thanks for reading and waiting for more dumps from any brands of 290's!
.
