The segmentation of the timing straps differs for different series, so you have to use many different parsing rules to get the right numbers.
You have to gather all the required data.
Collected 1100+ bioses for R? [234]?? and HD [78]?? with GDDR5 and auto(nailed previous question already) extracted all timing tables (>90 unique variants excluding subsets and compositions). It seems to me that RX and preRX should be segmented differently(and i know how) but for different preRX visible difference is few bits only (if any at all). Edit: For example this is different values for 1250 strap for Elpida EDW2032BBBG from different cards ranging from HD 7730 to R9 380. 7771332000000000ad494930705509102d23e9030066e30022aa1c08640f2420ba8980a700000000130e1e2331242e11
7771332000000000ad495930705509102d15e9030068c30022aa1c08640f1420ba8980a700000000130e1e233e242e11
7771332000000000ad495930705509102d15e9030068c30022aa1c08640f1420ba8980a7000007c0130e1e233e242e11
7771332000000000ad495930705509102d23e9030066a30022aa1c08640f1420ba8980a7000007e0130e1e2331242e11
7771332000000000ad495930705509102d23e9030068c30022aa1c00640f1420ba8980a700000000130e1e2331242e11
7771332000000000ad495930705509102d23e9030068c30022aa1c00640f1420ba8980a7000007c0130e1e2331242e11
7771332000000000ad495930705509102d23e9030068c30022aa1c08640f1420ba8980a700000000130e1e2331242e11
7771332000000000ad495930705509102d23e9030068c30022aa1c08640f1420ba8980a700000000130e1e233e242e11
7771332000000000ad495930705509102d23e9030068c30022aa1c08640f1420ba8980a7000007c0130e1e2331242e11
7771332000000000ad495930705509102d23e9030068c30022aa1c08640f1420ba8980a7000007c0130e1e233e242e11
7771332000000000ad495930705509102d23e9030068c30022aa1c08640f1420ba8980a7000007e0130e1e2331242e11
7771332000000000ad497930705309102d23e9030066e30022aa1c00640f1420ba8980a700000000130e1e2331242e11
7771332000000000ad497930705309102d23e9030066e30022aa1c00640f1420ba8980a700000000130e1e2331242e11
7771332000000000ad497930705309102d23e9030066e30022aa1c00640f1420ba8980a700000000130e1e2331242e11
7771332000000000ad497930705309102d23e9030066e30022aa1c00640f1420ba8980a7000007c0130e1e2331242e11
7771332000000000ad497930705309102d23e9030066e30022aa1c00640f1420ba8980a7000007c0130e1e2331242e11
7771332000000000ad497930705309102d23e9030066e30022aa1c00640f1420ba8980a7000007c0130e1e2331242e11
7771332000000000ad497930705309102d23e9030066e30022aa1c08640f1420ba8980a700000000130e1e2331242e11
7771332000000000ad497930705309102d23e9030066e30022aa1c08640f1420ba8980a700000000130e1e2331242e11
7771332000000000ad497930705309102d23e9030066e30022aa1c08640f1420ba8980a700000000130e1e2331242e11
7771332000000000ad497930705309102d23e9030066e30022aa1c08640f1420ba8980a700000200130e1e2331242e11
7771332000000000ad497930705309102d23e9030066e30022aa1c08640f1420ba8980a7000007c0130e1e2331242e11
7771332000000000ad497930705309102d23e9030066e30022aa1c08640f1420ba8980a7000007c0130e1e2331242e11
7771332000000000ad497930705309102d23e9030066e30022aa1c08640f1420ba8980a7000007c0130e1e2331242e11
7771332000000000ad497930705309102e23e9030066e30022aa1c0064001420ba8980a702000200130e1e2331242f11
7771332000000000ad497930705309102e23e9030066e30022aa1c0864001420ba8980a702000200130e1e2331242f11
7771332000000000ad497930705509102d23e9030066e30022aa1c00640f1420ba8980a700000000130e1e2331242e11
7771332000000000ad497930705509102d23e9030066e30022aa1c00640f1420ba8980a7000007c0130e1e2331242e11
7771332000000000ad497930705509102d23e9030066e30022aa1c08640f1420ba8980a700000000130e1e2331242e11
7771332000000000ad497930705509102d23e9030066e30022aa1c08640f1420ba8980a7000007c0130e1e2331242e11
7771332000000000ad497930705509102d23e9030066e30022aa1c08640f1420ba8980a7000007e0130e1e2331242e11
Edit: Pre HD 7??? timing tables look different from pre RX and RX tables. Edit: It seems the proper way is to look not at card series but at bios version (AMD VERblalbla at the begining of the bios unless vendor messed it). Timing structure (at least for GDDR5) is the same for each of VER015.50 (RX series), VER015.(00-49) (R? [23], HD 7???, HD 8???), VER013 (middle/high-end HD 6???, some low-end HD 7???), VER012(low/middle-end HD 6???, all HD 5???). VER013 timing structure looks like VER015.(00-49) but located at different place (at least i do not know how to get offset difference). VER015.50 timing structure seems to be like VER015.(00-49) but with bits moved around. |
|
|
|
|
For the sake of scientific discovery collected 640+ bioses for R? [234]?? cards and written parser to extract timing table and related tables.
Here is the question.
Is there a proper way to determine size of timing table?
|
|
|
|
RAS and CAS timings the same, MISC differ
They are exactly the same (RAS, CAS, MISC but not entire strap), just encoded differently for MISC (current info in this thread about decoding MISC for RX seems partially wrong) and of course different offsets. But why? |
|
|
|
Question. Here is the strap table for Hynix H5GC4H24AJR (according to amdmeminfo) in stock r9 390: 400 555133200000000084941212f0540b07150973020020410022dd1c081b0414209a8800a00000012006050d0e270f160e
800 7771332000000000e7ac352210550d0a208ef5040024810022dd1c08340914209a8800a0000001200c08171b4f172110
900 77713320000000002931462620550e0b220f96050026a20022dd1c083c0a1420aa8800a0000001200d0a1a1d59192311
1000 777133200000000029b5462930550e0c249026060026a20022dd1c08440b1420aa8800a0000001200e0a1c20621b2511
1125 77713320000000006bbd572f40550f0d2892f7060048c50022ff1c084c0d14205a8900a000000120100c20246f1e2912
1250 77713320000000008cc5583460550f0f2c94b8070048c50022ff1c085c0f14205a8900a000000120120d23287b222d13
1375 7771332000000000cecd5939805511112e1589080048c60022339d086c0014206a8900a002000120140f262b88252f15
1425 7771332000000000ce516a3b805511112f96d908004ae60022339d086c0014206a8900a002000120150f272d8d263015
1500 7771332000000000ce516a3d9055111230964909004ae60022339d08740114206a8900a002000120150f292f94273116
1625 999133200000000010de7b448055131237194b0a004c060122559d08750414206a8900a00200012018112d34a42a3816
1750 999133200000000031627c4890551313399adb0a004c060122559d087d0514206a8900a00200012019123037ad2c3a17
2000 bbb133200000000073ee8d53805515133e9e5d0c004e260122889d087e0514206a8900a0020001201c143840c5303f17
Why does it looks so different from Hynix H5GC4H24AJR in rx 480/470? |
|
|
|
Because it is not 7 bits? This is from linux kernel. #define MC_SEQ_MISC_TIMING_LP__TRP_WRA_MASK 0x3f
#define MC_SEQ_MISC_TIMING_LP__TRP_WRA__SHIFT 0x0
#define MC_SEQ_MISC_TIMING_LP__TRP_RDA_MASK 0x3f00
#define MC_SEQ_MISC_TIMING_LP__TRP_RDA__SHIFT 0x8
#define MC_SEQ_MISC_TIMING_LP__TRP_MASK 0xf8000
#define MC_SEQ_MISC_TIMING_LP__TRP__SHIFT 0xf
#define MC_SEQ_MISC_TIMING_LP__TRFC_MASK 0x1ff00000
#define MC_SEQ_MISC_TIMING_LP__TRFC__SHIFT 0x14
Surely 0x1ff00000 gives 9 bits? The way i see it, it should be decoded as (highter to lower bits): Bits("unused3", 3), #Unused
Bits("TRFC", 9), #Auto-refresh command period - 1
Bits("TRP", 5), #Precharge command period - 1
Bits("unused2", 1), #Unused but defined as 1
Bits("TRP_RDA", 6), #From read with auto-precharge to active - 1
Bits("unused1", 2), #Unused
Bits("TRP_WRA", 6), #From write with auto-precharge to active - 1
If so then MISC_TIMING decodes from 1500 hynix strap as unused3 = 0
TRFC = 148
TRP = 9
unused2 = 1
TRP_RDA = 11
unused1 = 0
TRP_WRA = 48
I am more interested why unused2 contains data. Did i miss something? |
|
|
|
|
Does somebody tested it with r9 390?
What is cryptonight hashrate?
|
|
|
|
Noticed messages like [2017-01-13 01:18:32.010] [error] Found solution index out of range: 1266366814
in logs (probably due overclocking). Current version of miner does not print which card got bad solution. Could this info (card id for bad solitions) be added to logs in new version? |
|
|
|
Ubuntu 15.04 + fglrx + R9 390 gives error. [2017-01-07 09:08:20.350] [info] Using highly optimized kernel code for Hawaii devices.
[2017-01-07 09:08:20.350] [info] Autodetected '--intensity 6' for device 1.
[2017-01-07 09:08:20.515] [info] [GPU1] Using device Hawaii.
[2017-01-07 09:08:21.167] [error] Build Status: -2
[2017-01-07 09:08:21.167] [error] Build Log:
Internal error: Link failed.
Make sure the system setup is correct. |
|
|
|
Hello, any linux users ? What drivers do you use ? Is it working on Ubuntu 16 + amdgpupro ?
Thanks !
Ubuntu 16 + amdgpupro + rx series card gives me immediate segfault. |
|
|
|
Of course not
I will synchronize now the old blocks and you will get the earnings that you will have
Ok. This is all I wanted to hear. |
|
|
|
It does not answer my question at all. From block ~41400 to block 41555 (where last split occured) xci.cryptonotepool.com mined ~150 blocks on good chain.
Where are they? They are removed from pool statistic now.
Pool got ~150 blocks on good chain. They should be in the pool wallet. You are saying that pool will keep these blocks to itself? |
|
|
|
But I'm still missing understanding what happened (technically) and how to avoid it in the future. If "nicehash" indeed can do such a mess filtering seems to be a temporary solution.
Some 'bug' leads to chain split. Since chain splited some pools mine on 'bad' chain. Therefore hashrate allocated to 'good' chain is reduced and difficulty on 'good' chain eventually falls. Therefore profits/hash on 'good' chain raise above marker average. Someone sees raised profits/hash and decides to 'pick it up'. Goes to nicehash for hashrate. Mines. Difficulty raises. Nicehash miner goes away. |
|
|
|
|
Question to xci.cryptonotepool.com owner.
From block ~41400 to block 41555 (where last split occured) xci.cryptonotepool.com mined ~150 blocks on good chain.
Where are they? They are removed from pool statistic now.
|
|
|
|
|
It seems now attacker moved to gorillapool.
Could pools just firewall-out nicehash IPs?
|
|
|
|
It seems I was right. Network seems to agree with attacker.
On the other hand just right now network==attacker.
|
|
|
|
In this chain last ~300 blocks was mined by attacker. |
|
|
|
|
Network seems to agree with attacker.
On the other hand just right now network==attacker.
|
|
|
|
Where is the right chain?
Max height is here xci.ms-pool.net.ua. If it is the right chain is debatable. I think that network is 'under nicehash attack'. |
|
|
|
Yes once more. This time at block 41555. |
|
|
|
i don't understand still other trouble i switch to xci.cryptonotepool but there is also something weird last network block is 41402 but pool last block found is 41506  It seems yesterday xci.cryptonotepool.org was on 'gorilla' chain (at least part of the day). Since client from https://github.com/xcicoin/xcicoin could not sync beyond block 41380 I have no idea how it got to block 41506. So all information about blocks beyond 41409 at xci.cryptonotepool.org is yesterday leftovers in xci.cryptonotepool.org database. Probably will be rewritten as time comes. |
|
|
|
|
Show Posts
