Author

Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 618. (Read 6590565 times)

newbie
Activity: 4
Merit: 0

Appreciate it if someone can give some input Smiley

Need help from Ubuntu experts

Hi!  I need some help from Ubuntu experts.  I set up a test rig using the Sapphire Nitro+ RX580 on Windows 10, using Afterburner to do some mild overclocking - Stable on Claymore 9.8 with customised fan profile.  I flashed the bios with the Hynix timing straps and I am getting around 24mhs, which is not bad, but not great either.   It is stable.

However, when I tried set up an Ubuntu environment (16.04), I can get it stable at standard clock rates - however it crashes when I raised the clock rate using the flashed bios with the overclocked memory that works well in windows.   The fan seems to be kicking in very late, and I was getting 76 degrees at 25% fan. 

Here's a list of my questions that I hope the Ubuntu/Claymore experts can help with as I am a beginner in Ubuntu:

1.  I tried using the -tt and -fanmin command in Claymore.  I get the error message "Failed to set new fan speed, check if miner has root access!".   How do I set the miner to have root access?   Right now, I am starting the miner with the command in terminal "./mine.sh", where mine.sh is the claymore start file. 

2.  I am getting a list of error messages off the standard environment variables in Claymore.  As below:

"alvin@cryptominer-one:~/Desktop/Claymore98$ ./mine.sh
./mine.sh: line 1: export: `0': not a valid identifier
./mine.sh: line 2: export: `100': not a valid identifier
./mine.sh: line 3: export: `1': not a valid identifier
./mine.sh: line 4: export: `100': not a valid identifier
./mine.sh: line 5: export: `100': not a valid identifier?

Appreciate some insights into the above.

3.  -mclock 2100 doesn't seem to have any impact on the hash rate (standard is 2000).   Am I using it correctly?

4.  How do I monitor GPU status in Ubuntu?  Aticonfig doesn't seem to work.

Thanks!




full member
Activity: 363
Merit: 100
Does anyone know how to solve the errors of 999. When the Windows locks the video card and then unlocks it, then the program restarts but without the overclocking settings. I would suggest that this is due to overclocking, but this happens without overclocking and only on video cards that are on the second power supply. Swapping blocks and video cards does not help.
member
Activity: 119
Merit: 10
How many of them do you have?
Have you checked HWInfo for memory errors on your cards?
What is your power consumption per card?
What are your overclock / undervolt settings?

Well I only have Hynix ones but those numbers does not sound too bad..
If I would change something I would increase the -dcri parameter in order to reach 900mh on DCR (the sacrifice in ETH actually has a minor stability benefit - less fluctuations- at least for me)
full member
Activity: 533
Merit: 100
Does anyone have RX580 cards with Elpida?
In dual mining, I have ETH 28.7mh  DCR 717mh.
I can't push them anymore Huh
newbie
Activity: 41
Merit: 0
Ok so I did the my first successful 1500 strapping on my two rx 470 4g. One is at 23 mh/s and the other 22. Up from around 19.5. Is that good? What can I do next for more performance!

1150 MHz core clock, 2000 - 2100 MHz memory clock should get you to ~29 MH/s stable with a good timing strap bios mod. Also run HWinfo 'sensors only' to check for memory errors and reduce the memory clock by 25-50 MHz until there are no errors.

Im up to 26 mh/ each now. at 1150 1950 -70 voltage. Past 1950 is black screen. Not bad for 470 4g

It should be higher. Try increasing the -ethi to 8. My eight card mixed RX 570/570 4GB/8GB rig is getting 28.5 to almost 30 MH/s dual mining UBQ.

https://image.ibb.co/hEa7Rv/Screenshot_from_2017_09_05_03_34_35.png

If you are on Windows mining ETH make sure you have the blockchain drivers with the epoch Dag fix patch.

you got that 28.5-30 mh/s owing to low epoch of Ubiq I believe. Smiley try to mine etc at epoch 144 and you will see.
newbie
Activity: 44
Merit: 0
Ok so I did the my first successful 1500 strapping on my two rx 470 4g. One is at 23 mh/s and the other 22. Up from around 19.5. Is that good? What can I do next for more performance!

1150 MHz core clock, 2000 - 2100 MHz memory clock should get you to ~29 MH/s stable with a good timing strap bios mod. Also run HWinfo 'sensors only' to check for memory errors and reduce the memory clock by 25-50 MHz until there are no errors.

Im up to 26 mh/ each now. at 1150 1950 -70 voltage. Past 1950 is black screen. Not bad for 470 4g

It should be higher. Try increasing the -ethi to 8. My eight card mixed RX 570/570 4GB/8GB rig is getting 28.5 to almost 30 MH/s dual mining UBQ.

https://image.ibb.co/hEa7Rv/Screenshot_from_2017_09_05_03_34_35.png

If you are on Windows mining ETH make sure you have the blockchain drivers with the epoch Dag fix patch.

some fantastic hashrates you have.. Smiley if you would log in to my teamviewer and make my rx570s work like yours, I would mine on your wallet for some time!
hero member
Activity: 1036
Merit: 606
Ok so I did the my first successful 1500 strapping on my two rx 470 4g. One is at 23 mh/s and the other 22. Up from around 19.5. Is that good? What can I do next for more performance!

1150 MHz core clock, 2000 - 2100 MHz memory clock should get you to ~29 MH/s stable with a good timing strap bios mod. Also run HWinfo 'sensors only' to check for memory errors and reduce the memory clock by 25-50 MHz until there are no errors.

Im up to 26 mh/ each now. at 1150 1950 -70 voltage. Past 1950 is black screen. Not bad for 470 4g

It should be higher. Try increasing the -ethi to 8. My eight card mixed RX 570/570 4GB/8GB rig is getting 28.5 to almost 30 MH/s dual mining UBQ.



If you are on Windows mining ETH make sure you have the blockchain drivers with the epoch Dag fix patch.
sr. member
Activity: 854
Merit: 262
Ok so I did the my first successful 1500 strapping on my two rx 470 4g. One is at 23 mh/s and the other 22. Up from around 19.5. Is that good? What can I do next for more performance!

1150 MHz core clock, 2000 - 2100 MHz memory clock should get you to ~29 MH/s stable with a good timing strap bios mod. Also run HWinfo 'sensors only' to check for memory errors and reduce the memory clock by 25-50 MHz until there are no errors.

Im up to 26 mh/ each now. at 1150 1950 -70 voltage. Past 1950 is black screen. Not bad for 470 4g
member
Activity: 119
Merit: 10
So I have been using the latest Claymore version since it came out.

My rig:

ASUZ Prime Z270-P
8x RX 580 8GB Nitro+ (Hynix)
Windows 10
Blockchain Beta Official Drivers
Claymore Dual Miner v.10.0
Modded BIOS, OC through Claymore @162w from the wall per card
Dual mining ETH (233 Mh/s) +DCR (7000 Mh/s)


I am overall happy with the new update, but I have had some issues:

  • Sometimes miner can't reach maximum speed. I open the miner, clocks and voltages are being set properly but hashrate lies in the 225mh/s area. A simple miner restart resolves the issue
  • Computer freezes. This has happened 2 times in my rig and 1 time in my PC (same setup with 1 gpu only) in the last 2 days. Here is the last part of the log @Claymore in case you find something interesting here
Code:
01:32:31:853 10f0 ETH: Share accepted (78 ms)!
01:32:26:712 10f0 new buf size: 0
01:32:28:462 1d4c GPU 0 temp = 69, old fan speed = 47, new fan speed = 35
01:32:28:493 1d4c GPU 1 temp = 68, old fan speed = 33, new fan speed = 25
01:32:28:525 1d4c GPU 2 temp = 68, old fan speed = 51, new fan speed = 39
01:32:28:540 1d4c GPU 3 temp = 61, old fan speed = 36, new fan speed = 25
01:32:28:556 1d4c GPU 4 temp = 68, old fan speed = 37, new fan speed = 28
01:32:28:572 1d4c GPU 5 temp = 68, old fan speed = 41, new fan speed = 32
01:32:28:587 1d4c GPU 6 temp = 68, old fan speed = 43, new fan speed = 32
01:32:28:618 1d4c GPU 7 temp = 66, old fan speed = 46, new fan speed = 32
01:32:30:603 10f0 ETH: checking pool connection...
01:32:30:603 10f0 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
01:32:30:619 6d4 recv: 66
01:32:30:619 6d4 srv pck: 65
01:32:30:665 10f0 got 248 bytes
01:32:30:665 10f0 buf: {"id":3,"jsonrpc":"2.0","result":["0x5f62e74681e5c356df92c659e1dc03b508de7690db773a735eab4b18e3ce54fd","0x89ec0600d6137ca02d3089f808f6fb2b550cd6ab12a76d8b20320e52403a20d3","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x40ae6f"]}
01:32:30:665 10f0 parse packet: 247
01:32:30:665 10f0 ETH: job is the same
01:32:30:665 10f0 new buf size: 0
01:32:30:853 6d4 srv bs: 0
01:32:30:853 6d4 sent: 312
01:32:31:103 1d04 recv: 66
01:32:31:103 1d04 srv pck: 65
01:32:31:322 1d04 srv bs: 0
01:32:31:322 1d04 sent: 312
01:32:31:759 f2c ETH: put share nonce 71397fb8c855326c
01:32:31:759 f2c ETH round found 1 shares
01:32:31:775 10f0 ETH: 09/05/17-01:32:31 - SHARE FOUND - (GPU 4)
01:32:31:775 10f0 send: {"id":4,"method":"eth_submitWork","params":["0x71397fb8c855326c","0x5f62e74681e5c356df92c659e1dc03b508de7690db773a735eab4b18e3ce54fd","0x077aca16b879eb83a278749a8b79e880ccacb30f7570b9efb6c4d5103f1d53d2"]}
01:32:31:853 10f0 got 39 bytes
01:32:31:853 10f0 buf: {"id":4,"jsonrpc":"2.0","result":true}
01:32:31:853 10f0 parse packet: 38
01:32:31:853 10f0 ETH: Share accepted (78 ms)!
01:32:31:853 10f0 new buf size: 0
01:32:32:134 1d4c GPU 0 temp = 69, old fan speed = 47, new fan speed = 35
01:32:32:166 1d4c GPU 1 temp = 68, old fan speed = 33, new fan speed = 25
01:32:32:181 1d4c GPU 2 temp = 68, old fan speed = 51, new fan speed = 39
01:32:32:213 1d4c GPU 3 temp = 61, old fan speed = 36, new fan speed = 25
01:32:32:228 1d4c GPU 4 temp = 68, old fan speed = 37, new fan speed = 28
01:32:32:244 1d4c GPU 5 temp = 68, old fan speed = 41, new fan speed = 32
01:32:32:275 1d4c GPU 6 temp = 68, old fan speed = 43, new fan speed = 32
01:32:32:306 1d4c GPU 7 temp = 66, old fan speed = 45, new fan speed = 31
01:32:32:431 b48 ETH: put share nonce 792b4840c4e1aa22
01:32:32:431 b48 ETH round found 1 shares
01:32:32:447 10f0 ETH: 09/05/17-01:32:32 - SHARE FOUND - (GPU 7)
01:32:32:447 10f0 send: {"id":4,"method":"eth_submitWork","params":["0x792b4840c4e1aa22","0x5f62e74681e5c356df92c659e1dc03b508de7690db773a735eab4b18e3ce54fd","0x8b7613c5a3bf1d953bccc84c41968f0d3f1ecfd511efc2769f807721ceba1c78"]}
01:32:32:744 10f0 got 248 bytes
01:32:32:744 10f0 buf: {"id":0,"jsonrpc":"2.0","result":["0xacecab87c2a7b1b5dfc7311bffcf58c5c0c509790210e2dc63fcdaa8b66fdad5","0x89ec0600d6137ca02d3089f808f6fb2b550cd6ab12a76d8b20320e52403a20d3","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x40ae70"]}
01:32:32:744 10f0 parse packet: 247
01:32:32:744 10f0 ETH: job changed
01:32:32:744 10f0 new buf size: 0
01:32:32:744 10f0 ETH: 09/05/17-01:32:32 - New job from eu2.ethermine.org:4444
01:32:32:744 10f0 target: 0x0000000112e0be82 (diff: 4000MH), epoch 141(2.10GB)
01:32:32:744 10f0 ETH - Total Speed: 232.917 Mh/s, Total Shares: 832, Rejected: 1, Time: 04:07
01:32:32:759 10f0 ETH: GPU0 29.339 Mh/s, GPU1 29.327 Mh/s, GPU2 28.714 Mh/s, GPU3 29.929 Mh/s, GPU4 29.196 Mh/s, GPU5 29.020 Mh/s, GPU6 28.907 Mh/s, GPU7 28.485 Mh/s
01:32:32:759 10f0 DCR - Total Speed: 6987.511 Mh/s, Total Shares: 821, Rejected: 9
01:32:32:759 10f0 DCR: GPU0 880.163 Mh/s, GPU1 879.796 Mh/s, GPU2 861.411 Mh/s, GPU3 897.882 Mh/s, GPU4 875.890 Mh/s, GPU5 870.601 Mh/s, GPU6 867.216 Mh/s, GPU7 854.552 Mh/s
01:32:32:947 10f0 got 79 bytes
01:32:32:947 10f0 buf: {"id":4,"jsonrpc": "2.0","result": false,"error": "Unrequested work provided"}
01:32:32:947 10f0 parse packet: 73
01:32:32:947 10f0 ETH: Share rejected (500 ms)!
01:32:32:947 10f0 new buf size: 0
01:32:32:963 10f0 Socket was closed remotely (by pool)
01:32:32:963 10f0 ETH: Connection lost, retry in 20 sec...
01:32:35:635 12c0 recv: 66
01:32:35:635 12c0 srv pck: 65
01:32:35:791 1d4c GPU 0 temp = 63, old fan speed = 48, new fan speed = 32
01:32:35:807 1d4c GPU 1 temp = 63, old fan speed = 34, new fan speed = 25
01:32:35:822 1d4c GPU 2 temp = 63, old fan speed = 51, new fan speed = 36
01:32:35:838 1d4c GPU 3 temp = 55, old fan speed = 37, new fan speed = 25
01:32:35:885 1d4c GPU 4 temp = 62, old fan speed = 37, new fan speed = 25
01:32:35:916 1d4c GPU 5 temp = 63, old fan speed = 42, new fan speed = 29
01:32:35:947 1d4c GPU 6 temp = 63, old fan speed = 44, new fan speed = 29
01:32:35:979 1d4c GPU 7 temp = 61, old fan speed = 44, new fan speed = 27
01:32:36:088 2158 recv: 66
01:32:36:104 2158 srv pck: 65
01:32:36:197 12c0 srv bs: 0
01:32:36:197 12c0 sent: 290
01:32:36:354 2158 srv bs: 0
01:32:36:354 2158 sent: 290
01:32:39:479 1d4c GPU 0 temp = 60, old fan speed = 44, new fan speed = 28
01:32:39:495 1d4c GPU 1 temp = 60, old fan speed = 34, new fan speed = 25
01:32:39:510 1d4c GPU 2 temp = 60, old fan speed = 48, new fan speed = 32
01:32:39:510 1d4c GPU 3 temp = 52, old fan speed = 37, new fan speed = 25
01:32:39:526 1d4c GPU 4 temp = 59, old fan speed = 34, new fan speed = 25
01:32:39:541 1d4c GPU 5 temp = 60, old fan speed = 38, new fan speed = 25
01:32:39:541 1d4c GPU 6 temp = 60, old fan speed = 40, new fan speed = 25
01:32:39:557 1d4c GPU 7 temp = 59, old fan speed = 39, new fan speed = 25
01:32:40:604 166c recv: 66
01:32:40:604 166c srv pck: 65
01:32:40:807 166c srv bs: 0
01:32:40:807 166c sent: 207
01:32:41:088 1310 recv: 66
01:32:41:104 1310 srv pck: 65
01:32:41:307 1310 srv bs: 0
01:32:41:307 1310 sent: 207
01:32:43:042 1d4c GPU 0 temp = 59, old fan speed = 39, new fan speed = 25
01:32:43:057 1d4c GPU 1 temp = 59, old fan speed = 34, new fan speed = 25
01:32:43:073 1d4c GPU 2 temp = 59, old fan speed = 43, new fan speed = 27
01:32:43:073 1d4c GPU 3 temp = 51, old fan speed = 37, new fan speed = 25
01:32:43:089 1d4c GPU 4 temp = 58, old fan speed = 33, new fan speed = 25
01:32:43:104 1d4c GPU 5 temp = 59, old fan speed = 34, new fan speed = 25
01:32:43:120 1d4c GPU 6 temp = 59, old fan speed = 36, new fan speed = 25
01:32:43:120 1d4c GPU 7 temp = 58, old fan speed = 36, new fan speed = 25
01:32:43:292 1d4c GPU0 t=59C fan=39%, GPU1 t=59C fan=34%, GPU2 t=59C fan=42%, GPU3 t=51C fan=37%, GPU4 t=58C fan=33%, GPU5 t=58C fan=34%, GPU6 t=59C fan=36%, GPU7 t=58C fan=36%
01:32:43:292 1d4c em hbt: 10329, dm hbt: 0, fm hbt: 94,
01:32:43:292 1d4c watchdog - thread 0 (gpu0), hb time 79
01:32:43:307 1d4c watchdog - thread 1 (gpu0), hb time 47
01:32:43:307 1d4c watchdog - thread 2 (gpu1), hb time 62
01:32:43:307 1d4c watchdog - thread 3 (gpu1), hb time 31
01:32:43:307 1d4c watchdog - thread 4 (gpu2), hb time 78
01:32:43:307 1d4c watchdog - thread 5 (gpu2), hb time 109
01:32:43:307 1d4c watchdog - thread 6 (gpu3), hb time 78
01:32:43:307 1d4c watchdog - thread 7 (gpu3), hb time 47
01:32:43:307 1d4c watchdog - thread 8 (gpu4), hb time 78
01:32:43:307 1d4c watchdog - thread 9 (gpu4), hb time 0
01:32:43:307 1d4c watchdog - thread 10 (gpu5), hb time 31
01:32:43:307 1d4c watchdog - thread 11 (gpu5), hb time 78
01:32:43:307 1d4c watchdog - thread 12 (gpu6), hb time 78
01:32:43:307 1d4c watchdog - thread 13 (gpu6), hb time 109
01:32:43:307 1d4c watchdog - thread 14 (gpu7), hb time 47
01:32:43:307 1d4c watchdog - thread 15 (gpu7), hb time 78
01:32:45:761 55c recv: 66
01:32:45:761 55c srv pck: 65
01:32:45:964 55c srv bs: 0
01:32:45:964 55c sent: 207
01:32:46:105 10e0 recv: 66
01:32:46:105 10e0 srv pck: 65
01:32:46:292 10e0 srv bs: 0
01:32:46:308 10e0 sent: 207
01:32:46:792 1d4c GPU 0 temp = 58, old fan speed = 35, new fan speed = 25
01:32:46:808 1d4c GPU 1 temp = 58, old fan speed = 34, new fan speed = 25
01:32:46:823 1d4c GPU 2 temp = 58, old fan speed = 36, new fan speed = 25
01:32:46:823 1d4c GPU 3 temp = 50, old fan speed = 37, new fan speed = 25
01:32:46:839 1d4c GPU 4 temp = 56, old fan speed = 33, new fan speed = 25
01:32:46:855 1d4c GPU 5 temp = 57, old fan speed = 34, new fan speed = 25
01:32:46:855 1d4c GPU 6 temp = 58, old fan speed = 35, new fan speed = 25
01:32:46:870 1d4c GPU 7 temp = 57, old fan speed = 36, new fan speed = 25
01:32:50:371 1d4c GPU 0 temp = 57, old fan speed = 35, new fan speed = 25
01:32:50:386 1d4c GPU 1 temp = 57, old fan speed = 34, new fan speed = 25
01:32:50:386 1d4c GPU 2 temp = 57, old fan speed = 34, new fan speed = 25
01:32:50:402 1d4c GPU 3 temp = 49, old fan speed = 37, new fan speed = 25
01:32:50:418 1d4c GPU 4 temp = 55, old fan speed = 33, new fan speed = 25
01:32:50:433 1d4c GPU 5 temp = 57, old fan speed = 34, new fan speed = 25
01:32:50:433 1d4c GPU 6 temp = 57, old fan speed = 36, new fan speed = 25
01:32:50:449 1d4c GPU 7 temp = 56, old fan speed = 37, new fan speed = 25
01:32:50:605 1454 recv: 66
01:32:50:605 1454 srv pck: 65
01:32:50:808 1454 srv bs: 0
01:32:50:808 1454 sent: 207

I know the fun part is
Code:
01:32:32:963   10f0   Socket was closed remotely (by pool)
01:32:32:963   10f0   ETH: Connection lost, retry in 20 sec...
    but this does not justify a computer freeze
hero member
Activity: 1036
Merit: 606
I dont understand the bios modding. What am I to be changing on my Polaris cards I am only get roughly 20mh/s out of them on ETH.

When i load the bios following instructions, they say change timing, the timings are all kinds of crazy hex numbers.

I also get an error about my bois being too small



You cannot use GPU-Z to save the BIOS as it only saves half of modern bioses. You must use ati flash to save the bios. You are copying the memory straps from either 1500 (hynix, micron and elpida) or 1750 (samsung) and pasting it to all memory straps higher than it, such as 1650, 1700, etc up to 2000 or higher. This makes the memory run with tighter memory settings so hashes more. But it can also make the card unstable and/or crash.

How do I tell memory brand... also I am using ATI flash to pull them. They appear to already read as 2000 as thier default memory speed?
When you start GPU-Z, it reports the memory brand. Also use the following article for BIOS flashing as it tells you the correct Polaris BIOS editor version to use in order to get rid of the craxy hex numbers you're seeing:
http://1stminingrig.com/sapphire-nitro-rx-470-8gb-oc-bios-flash-mod-tutorial-hynix-samsung/

Okay all m y cards are hynix so I can OC them a bit? My screen for timing looks nothing like his.



You are using outdated version of PBE. Find a good step by step instruction with the links to the 1.4.1 version

The most current version of PBE is v1.6. It now includes 'one click' bundled performance timings. Very easy to use. Just save your original Bios using Atiwinflash and open it in PBE. The 'one click' option automatically applies the bundled performance timings and then save the bBios and flash it using Atiwinflash.

https://bitcointalksearch.org/topic/m.21518785


This version applies performance timings to the 2000 strap by default. Any way to get it to apply performance timings to a lower strap?

The timing is applied according to what your cards memory type is. If you want you could copy it to the other timings manually by clicking on the strap you want to change and using the box on the bottom. I found it wasn't necessary and the cards are more stable than when I was just copying the 1500 Mhz strap to the higher frequencies.
hero member
Activity: 751
Merit: 517
Fail to plan, and you plan to fail.
I dont understand the bios modding. What am I to be changing on my Polaris cards I am only get roughly 20mh/s out of them on ETH.

When i load the bios following instructions, they say change timing, the timings are all kinds of crazy hex numbers.

I also get an error about my bois being too small



You cannot use GPU-Z to save the BIOS as it only saves half of modern bioses. You must use ati flash to save the bios. You are copying the memory straps from either 1500 (hynix, micron and elpida) or 1750 (samsung) and pasting it to all memory straps higher than it, such as 1650, 1700, etc up to 2000 or higher. This makes the memory run with tighter memory settings so hashes more. But it can also make the card unstable and/or crash.

How do I tell memory brand... also I am using ATI flash to pull them. They appear to already read as 2000 as thier default memory speed?
When you start GPU-Z, it reports the memory brand. Also use the following article for BIOS flashing as it tells you the correct Polaris BIOS editor version to use in order to get rid of the craxy hex numbers you're seeing:
http://1stminingrig.com/sapphire-nitro-rx-470-8gb-oc-bios-flash-mod-tutorial-hynix-samsung/

Okay all m y cards are hynix so I can OC them a bit? My screen for timing looks nothing like his.



You are using outdated version of PBE. Find a good step by step instruction with the links to the 1.4.1 version

The most current version of PBE is v1.6. It now includes 'one click' bundled performance timings. Very easy to use. Just save your original Bios using Atiwinflash and open it in PBE. The 'one click' option automatically applies the bundled performance timings and then save the bBios and flash it using Atiwinflash.

https://bitcointalksearch.org/topic/m.21518785


This version applies performance timings to the 2000 strap by default. Any way to get it to apply performance timings to a lower strap?
hero member
Activity: 1036
Merit: 606
I dont understand the bios modding. What am I to be changing on my Polaris cards I am only get roughly 20mh/s out of them on ETH.

When i load the bios following instructions, they say change timing, the timings are all kinds of crazy hex numbers.

I also get an error about my bois being too small



You cannot use GPU-Z to save the BIOS as it only saves half of modern bioses. You must use ati flash to save the bios. You are copying the memory straps from either 1500 (hynix, micron and elpida) or 1750 (samsung) and pasting it to all memory straps higher than it, such as 1650, 1700, etc up to 2000 or higher. This makes the memory run with tighter memory settings so hashes more. But it can also make the card unstable and/or crash.

How do I tell memory brand... also I am using ATI flash to pull them. They appear to already read as 2000 as thier default memory speed?
When you start GPU-Z, it reports the memory brand. Also use the following article for BIOS flashing as it tells you the correct Polaris BIOS editor version to use in order to get rid of the craxy hex numbers you're seeing:
http://1stminingrig.com/sapphire-nitro-rx-470-8gb-oc-bios-flash-mod-tutorial-hynix-samsung/

Okay all m y cards are hynix so I can OC them a bit? My screen for timing looks nothing like his.



You are using outdated version of PBE. Find a good step by step instruction with the links to the 1.4.1 version

The most current version of PBE is v1.6. It now includes 'one click' bundled performance timings. Very easy to use. Just save your original Bios using Atiwinflash and open it in PBE. The 'one click' option automatically applies the bundled performance timings and then save the Bios and flash it using Atiwinflash.

https://bitcointalksearch.org/topic/m.21518785
full member
Activity: 238
Merit: 100
I dont understand the bios modding. What am I to be changing on my Polaris cards I am only get roughly 20mh/s out of them on ETH.

When i load the bios following instructions, they say change timing, the timings are all kinds of crazy hex numbers.

I also get an error about my bois being too small



You cannot use GPU-Z to save the BIOS as it only saves half of modern bioses. You must use ati flash to save the bios. You are copying the memory straps from either 1500 (hynix, micron and elpida) or 1750 (samsung) and pasting it to all memory straps higher than it, such as 1650, 1700, etc up to 2000 or higher. This makes the memory run with tighter memory settings so hashes more. But it can also make the card unstable and/or crash.

How do I tell memory brand... also I am using ATI flash to pull them. They appear to already read as 2000 as thier default memory speed?
When you start GPU-Z, it reports the memory brand. Also use the following article for BIOS flashing as it tells you the correct Polaris BIOS editor version to use in order to get rid of the craxy hex numbers you're seeing:
http://1stminingrig.com/sapphire-nitro-rx-470-8gb-oc-bios-flash-mod-tutorial-hynix-samsung/

Okay all m y cards are hynix so I can OC them a bit? My screen for timing looks nothing like his.



You are using outdated version of PBE. Find a good step by step instruction with the links to the 1.4.1 version
full member
Activity: 238
Merit: 100
Can't undervolt/overclock with AMD Blockchain driver even with v10.0 Sad I know we can do that with Wattman, but I don't want. And with Afterburner we can't undervolt memory and it's limited.
Is it planned in next update ? Thanks Smiley

You problem is elsewhere. I an undervolt/overclock with AMD Blockchain driver even with v10.0
full member
Activity: 238
Merit: 100
I dont understand the bios modding. What am I to be changing on my Polaris cards I am only get roughly 20mh/s out of them on ETH.

When i load the bios following instructions, they say change timing, the timings are all kinds of crazy hex numbers.

I also get an error about my bois being too small



You cannot use GPU-Z to save the BIOS as it only saves half of modern bioses. You must use ati flash to save the bios. You are copying the memory straps from either 1500 (hynix, micron and elpida) or 1750 (samsung) and pasting it to all memory straps higher than it, such as 1650, 1700, etc up to 2000 or higher. This makes the memory run with tighter memory settings so hashes more. But it can also make the card unstable and/or crash.

How do I tell memory brand... also I am using ATI flash to pull them. They appear to already read as 2000 as thier default memory speed?

It is obvious that you do not know what to do.
Just google and find a good step by step instruction and follow.
That is it. You are not the first one nor the last one.
full member
Activity: 238
Merit: 100
Is there an other possibity for fixing the DAG epoch issues for Ethereum mining than the aug 23 blockchain driver?
I ask this because in my side, i have not found any way to run the blockchain driver with stability on my rig 8 gpu's under Windows 10, therefore i see the drop hashrate and i can do nothing to solve this issue at this day.

Thanks in advance for help.

Aug 11 driver Wink
Your problems are elsewhere with the rig.
If you want to have a stable system you have to back to basics, find a good instruction online and do changes step by step carefully.
I have 3 rigs with W10 and they all work fine with Aug 11 driver.
hero member
Activity: 1036
Merit: 606
Ok so I did the my first successful 1500 strapping on my two rx 470 4g. One is at 23 mh/s and the other 22. Up from around 19.5. Is that good? What can I do next for more performance!

1150 MHz core clock, 2000 - 2100 MHz memory clock should get you to ~29 MH/s stable with a good timing strap bios mod. Also run HWinfo 'sensors only' to check for memory errors and reduce the memory clock by 25-50 MHz until there are no errors.
hero member
Activity: 1036
Merit: 606
I get error 43 after flashing straps with atiwinflash. Is it true that I need pixel patcher to solve the bios signature check?

For most cards yes. Some RX 580's I have don't need the pixel patcher.
sr. member
Activity: 854
Merit: 262
Ok so I did the my first successful 1500 strapping on my two rx 470 4g. One is at 23 mh/s and the other 22. Up from around 19.5. Is that good? What can I do next for more performance!
newbie
Activity: 6
Merit: 0
anyone having issues with Eth Mining + Sia (using rx vega)

v9.8 works perfect, get around 36 Mhs and 900 Mh/s Sia.

v10 works with ETH however SIA reports all shares rejected ?

I'm using the same command line for both versions.

EthDcrMiner64.exe -epool us2.ethermine.org:4444 -ewal xxxx  -epsw x  -dpool stratum+tcp://asia.siamining.com:7777 -dwal yyyyyy -dcoin sia

tried searching for others with same, but can't find any hits.

Any ideas would be great ? currently rolled back to 9.8 as it mines flawlessly.
Jump to: