Bug found! I used a few AVX2 instructions in my aes_avx assembly. And there are some CPUs with AES and AVX but not AVX2
Will be fixed soon, this bug occurs in a pretty rare case, the AVX2 instruction is enabled by autoconfig only for CN-Heavy.
edit: next features
* http server to ease integration into 3rd party tools
* option to reconnect forever, for people with bad Internet access.
edit: 0.27a online - minor revision
fix AVX2 and add --forever parameter
also merge the Monero forks, and stepback XTL to CN-v7, will be XTL-fork later
Thanks for update! And very nice name "forever" for parameter. I like it! |
|
|
|
[...]
1. Windows 10 and Adrenalin 18.4.1 detected my RX 570's as RX 580's. Apparently downgrading Adrenaline to 18.3.4 fixed this.
2.With Pete_X's suggestions, I was able to get my Samsungs around 1000 h/s and my Hynixes around 900 h/s but when I put them together GGS would throttle and I would run out of memory. Any thoughts on this zawawa or anyone?
1. 18.4.1. is just one thing -> bugged ... better stay away from it  2. That is normally i sign for a: wrong intensity or b: a gpu crashed - or both. You should see on the graph or at the speed if it wortks - or not. Second Thread starts with a dely - so don't get fooled by some cards - it can take up to 2 Min or so till the 2nd thread is running at full speed ... Graphs tell also a lot ... flatline, up'n down etc ... Best to test it out is to enable just one card. Voltages in the safe zone and intensity conservative at a lower start. Card by card and notes taken should lead to success .... Not to forget - the swap file - it can't be big enough. For my rigs i simply use a old HDD (1TB) and W10 got a 156GB swap file on that drive  PS: Got my hands on an old 570 Pulse 8GB with Hynix MJR - right now running 2-122-8 1200-950-2100-950 @1025h/s Don't forget to point algo on wich you have 1025 h/s. Heavy algo on 8Gb cards give about 50-75 h/s more than normal cryptonight v7. |
|
|
|
The 11.7 version is with no fees? True?  Who sad? |
|
|
|
Today's Schedule- Run the code optimizer on X16R.
- Optimize default settings for Sapphire Nitro+ RX 570/580.
- Enable memory timing mods for RX 550/560.
My wife wants me to clean the living room, but who cares! You better listen to her )))) |
|
|
|
Here's another rig I have running Cryptonight-Heavy with GGS 1.3.7 alpha. This rig has 10x RX 570 8GB Nitro+ but somehow Windows 10 detects them as RX 580 after upgrading to Adrenaline 18.4.1  and my GGS settings:  Those churning ~820 h/s are Samsung DDRs and the rest at ~750 h/s are Hynix I haven't toyed with the Memory Timings, kind of scared to fuck up my cards. Anyone can help me improve my hashrate please? Will be happy to give a tip (0.005 BTC) if someone can help me get them to ~900-1000+ with stability. So let's help and get these cards over 1000h/s on CN-Heavy : Depending on the driver you use: 18.3.4 2-124-8 and 1200-900-2150-900 Hynix (Voltages can be tweaked when max hash is found) 2-124-8 and 1200-900-2050-900 Samsung (Voltages can be tweaked when max hash is found) 18.4.1 2-118-8 and 1200-900-2150-900 Hynix (Voltages can be tweaked when max hash is found) 2-118-8 and 1200-900-2050-900 Samsung (Voltages can be tweaked when max hash is found) Start with Intensity around 110 and raise it step by step (best is only a single card to get the idea what they like). I let each card run 5min as a test - that sould give you an idea how the card likes the settings - as not all cards are eqaul. On 18.3.4 most cards top around 124, 18.4.1 differs a bit - there it is around 118+-. With 1225 on the cores you should reach/top 1100 on Samsung and get close to 1100 on Hynix. I know it's a bit tweaking needed - but the results pay back easy Check the straps you use on both of them, normaly everyone useds on Samsung the "1Click" one -> 1750 and up -> 777000000000000022CC1C00AD615C41C0590E152ECC8608006007000B031420FA8900A00300000 010122F3FBA354019 Hynix 1750 and up -> 999000000000000022339D00CEDD6B4470551414B80D960B0040C400750314204A8900A00200000 018123745B92B3A16 There is still some room for tweaks, as the rams probably can do more then what i wrote - but needs testing ... Hope i could help and you get these GPUs over 1000h/s soon  18.3.4 -> https://imgur.com/a/aKu7ZRjCheers Wow thanks Pete_X really appreciate this. I got my Samsungs up around 1015 h/s at 110 intensity with your settings. Still working on the Hynix but I'm hopeful I can get them there too now. Please DM me your BTC address! Thanks for ignoring me. My posts to find right intensity from 112 to 124 you just ignored. Anyway you must know that cards with different manufacters even with the same type of memory must not work on the same timings on the same clocks. For example, Saphire Nitro+ with hynix mjr will good work on 2150MHz memory clock on timings 999000000000000022339D00CEDD6B4470551414B80D960B0040C400750314204A8900A00200000 018123745B92B3A16 but MSI Gaming X with the same hynix mjr on these timings didn't work even on 2100MHz. On clocks lower 2100MHz it will give speed lower than with other timings. But if I look you allready got all what you want. Hope that all your hynix mjr cards are fine quality... |
|
|
|
@PhoenixMiner My rig restarted after about 6 hours of running because hash rate fell below my specified limit. Please notice that in the logs the main Eth speed: 0.000 MH/s happened just after the set VMEM clocks was done. Do you see any reason for this ? Thanks
2018.05.07:21:35:03.270: main Phoenix Miner 2.9e Windows/msvc - Release
2018.05.07:21:35:03.270: main Cmd line:
2018.05.07:21:35:03.270: main config.txt: -pool ssl://us1.ethermine.org:5555 -wal 0x2b333365d68ea485aE8D810a9F62E49267eDF1D2.ETH-Miner-1 -pass x -coin eth -stales 1 -proto 2 -pool2 ssl://us2.ethermine.org:5555 -wal2 0x2b3E8d65db8e6285aEbD819a9F62E49267e754D6.ETH-Miner-1 -pass2 x -coin2 eth -stales2 1 -proto2 2 -fret 2 -ftimeout 600 -ptimeout 30 -gswin 30 -fanmin 25 -fanmax 90 -tmax 0 -rate 1 -cdm 2 -cdmport 1234 -cdmpass xxxxx123 -amd -mi 14 -gt 15 -clKernel 1 -minRigSpeed 25 -eres 2 -wdog 1 -rmode 2 -log 1 -tt 67 -tstop 75 -tstart 65 -fanmax 80 -fanmin 40 -cclock 1355 -cvddc 1150 -mclock 2125 -mvddc 900
2018.05.07:21:35:03.354: main Available GPUs for mining:
2018.05.07:21:35:03.354: main GPU1: Radeon RX 580 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.05.07:21:35:03.365: main ADL library initialized
2018.05.07:21:35:04.821: main Listening for CDM remote manager at port 1234 in full mode
2018.05.07:21:35:04.822: main Eth: the pool list contains 4 pools
2018.05.07:21:35:04.822: main Eth: primary pool: ssl://us1.ethermine.org:5555
2018.05.07:21:35:04.822: main Starting GPU mining
2018.05.08:03:43:51.333: main *** 6:08 ***************************************************
2018.05.08:03:43:51.333: main Eth: Mining ETH on ssl://us1.ethermine.org:5555 for 6:08
2018.05.08:03:43:51.333: main Eth speed: 30.531 MH/s, shares: 178/0/0, time: 6:08
2018.05.08:03:43:51.333: main Eth: Accepted shares 178 (0 stales), rejected shares 0 (0 stales)
2018.05.08:03:43:51.333: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2018.05.08:03:43:51.333: main Eth: Maximum difficulty of found share: 374.9 TH (!!!)
2018.05.08:03:43:51.333: main Eth: Average speed (5 min): 30.514 MH/s
2018.05.08:03:43:51.333: main Eth: Effective speed: 32.18 MH/s; at pool: 32.18 MH/s
2018.05.08:03:43:51.333: main
2018.05.08:03:43:53.404: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x23c1a4944022e5ffcd73c594768357d1b06db61d04bf7268d01176b8c7ee170f","0xad15d04b13b18ecbb6bc1c05cefa1e952fe584f2c79fb5f3dbc48656704b0f95","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5518f3"]}
2018.05.08:03:43:53.404: eths Eth: New job #23c1a494 from ssl://us1.ethermine.org:5555; diff: 4000MH
2018.05.08:03:43:56.411: main Eth speed: 30.530 MH/s, shares: 178/0/0, time: 6:08
2018.05.08:03:43:56.630: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
2018.05.08:03:43:56.672: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
2018.05.08:03:43:56.672: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x23c1a4944022e5ffcd73c594768357d1b06db61d04bf7268d01176b8c7ee170f","0xad15d04b13b18ecbb6bc1c05cefa1e952fe584f2c79fb5f3dbc48656704b0f95","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5518f3"]}
2018.05.08:03:44:00.359: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x40f4f48fbc938c264da7f6c8789aa3bcebfd0efc9799a55b10178eed45d1b8ae","0xad15d04b13b18ecbb6bc1c05cefa1e952fe584f2c79fb5f3dbc48656704b0f95","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5518f4"]}
2018.05.08:03:44:00.360: eths Eth: New job #40f4f48f from ssl://us1.ethermine.org:5555; diff: 4000MH
2018.05.08:03:44:01.505: main Eth speed: 30.530 MH/s, shares: 178/0/0, time: 6:08
2018.05.08:03:44:04.299: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x2f42b668929a2c1f0c34138807db7e3a0c518eaca7e83f3941519546d5045d2f","0xad15d04b13b18ecbb6bc1c05cefa1e952fe584f2c79fb5f3dbc48656704b0f95","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5518f4"]}
2018.05.08:03:44:04.299: eths Eth: New job #2f42b668 from ssl://us1.ethermine.org:5555; diff: 4000MH
2018.05.08:03:44:06.584: main Eth speed: 30.530 MH/s, shares: 178/0/0, time: 6:09
2018.05.08:03:44:06.631: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
2018.05.08:03:44:06.631: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x1d198ae","0x166a3919cd8eb5f97e73825151f940c73ba2ec6fc2e0eab34881a71fe91477bb"]}
2018.05.08:03:44:06.671: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x2f42b668929a2c1f0c34138807db7e3a0c518eaca7e83f3941519546d5045d2f","0xad15d04b13b18ecbb6bc1c05cefa1e952fe584f2c79fb5f3dbc48656704b0f95","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5518f4"]}
2018.05.08:03:44:08.821: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x7bd03f94d8907ea4be800aa69301a5db8de6279db5d23d2cfaa7c730e838b4aa","0xad15d04b13b18ecbb6bc1c05cefa1e952fe584f2c79fb5f3dbc48656704b0f95","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5518f5"]}
2018.05.08:03:44:08.821: eths Eth: New job #7bd03f94 from ssl://us1.ethermine.org:5555; diff: 4000MH
2018.05.08:03:44:13.540: hwmc GPU1: set VMEM clocks to 2125 MHz (Vddc 900 mV)
2018.05.08:03:44:13.692: main Eth speed: 0.000 MH/s, shares: 178/0/0, time: 6:09
2018.05.08:03:44:13.692: main GPU1: 54C 34%
2018.05.08:03:44:16.639: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
2018.05.08:03:44:16.681: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
2018.05.08:03:44:16.681: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x7bd03f94d8907ea4be800aa69301a5db8de6279db5d23d2cfaa7c730e838b4aa","0xad15d04b13b18ecbb6bc1c05cefa1e952fe584f2c79fb5f3dbc48656704b0f95","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5518f5"]}
2018.05.08:03:44:18.452: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x783cbe962bbd26f08f5526abe82f581a7b0bec429d70f706eaa70645c625f90b","0xad15d04b13b18ecbb6bc1c05cefa1e952fe584f2c79fb5f3dbc48656704b0f95","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5518f6"]}
2018.05.08:03:44:18.452: eths Eth: New job #783cbe96 from ssl://us1.ethermine.org:5555; diff: 4000MH
2018.05.08:03:44:18.891: main Eth speed: 0.000 MH/s, shares: 178/0/0, time: 6:09
2018.05.08:03:44:23.928: main Eth speed: 0.000 MH/s, shares: 178/0/0, time: 6:09
2018.05.08:03:44:29.008: main Eth speed: 0.000 MH/s, shares: 178/0/0, time: 6:09
2018.05.08:03:44:34.101: main Eth speed: 0.000 MH/s, shares: 178/0/0, time: 6:09
2018.05.08:03:44:37.960: main GPU1: 51C 34%
2018.05.08:03:44:39.179: main
2018.05.08:03:44:39.179: main *** 6:09 ***************************************************
2018.05.08:03:44:39.179: main Eth: Mining ETH on ssl://us1.ethermine.org:5555 for 6:09
2018.05.08:03:44:39.179: main Eth speed: 0.000 MH/s, shares: 178/0/0, time: 6:09
2018.05.08:03:44:39.179: main Eth: Accepted shares 178 (0 stales), rejected shares 0 (0 stales)
2018.05.08:03:44:39.179: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2018.05.08:03:44:39.179: main Eth: Maximum difficulty of found share: 374.9 TH (!!!)
2018.05.08:03:44:39.179: main Eth: Average speed (5 min): 26.934 MH/s
2018.05.08:03:44:39.179: main Eth: Effective speed: 32.11 MH/s; at pool: 32.11 MH/s
2018.05.08:03:44:39.179: main
2018.05.08:03:44:44.258: main Eth speed: 0.000 MH/s, shares: 178/0/0, time: 6:09
2018.05.08:03:44:49.336: main Eth speed: 0.000 MH/s, shares: 178/0/0, time: 6:09
2018.05.08:03:44:54.414: main Eth speed: 0.000 MH/s, shares: 178/0/0, time: 6:09
2018.05.08:03:44:59.710: main Eth speed: 0.000 MH/s, shares: 178/0/0, time: 6:09
2018.05.08:03:45:04.790: main Eth speed: 0.000 MH/s, shares: 178/0/0, time: 6:09
2018.05.08:03:45:06.415: main GPU1: 49C 0%
2018.05.08:03:45:09.868: main Eth speed: 0.000 MH/s, shares: 178/0/0, time: 6:10
2018.05.08:03:45:14.947: main Eth speed: 0.000 MH/s, shares: 178/0/0, time: 6:10
2018.05.08:03:45:20.025: main Eth speed: 0.000 MH/s, shares: 178/0/0, time: 6:10
2018.05.08:03:45:25.103: main
2018.05.08:03:45:25.103: main *** 6:10 ***************************************************
2018.05.08:03:45:25.103: main Eth: Mining ETH on ssl://us1.ethermine.org:5555 for 6:10
2018.05.08:03:45:25.103: main Eth speed: 0.000 MH/s, shares: 178/0/0, time: 6:10
2018.05.08:03:45:25.103: main Eth: Accepted shares 178 (0 stales), rejected shares 0 (0 stales)
2018.05.08:03:45:25.103: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2018.05.08:03:45:25.103: main Eth: Maximum difficulty of found share: 374.9 TH (!!!)
2018.05.08:03:45:25.103: main Eth: Average speed (5 min): 22.240 MH/s
2018.05.08:03:45:25.103: main Eth: Effective speed: 32.04 MH/s; at pool: 32.04 MH/s
2018.05.08:03:45:25.103: main
2018.05.08:03:45:25.103: main Average ethash speed for 5 min is below minimum of 25 MH/s. Restarting!
Not enough info. What system, drivers? If you use 18.4.1 drivers. Uninstall them and install 18.3.4. If 18.3.4 using, try to lower overclock, or rise voltage. |
|
|
|
i get it, but how non-assignment can help ?
If i've 8 cores for example, isn't it better to assign 4 cores to get the turbo, rather than having 8 cores running anywhere at 50% each, with no turbo ?
If use all 8 cores there is no way to use turbo and there is no effect on no assigning. And, of course, it's no matter. I mean for these who not use all CPU to mining, like me )))) Especially on CPU's on wich almost max speed can be achieved without using all cores, like my FX8320. Max speed is about 250 h/s. It's need to say that this result can be recieved with 8 single cores, or 6 single cores, due to small cache result between 8 threads and 6 differes not much. 200+ h/s can be achieved with 3 threads - thanks to double threads and turbo techno... But with assigning threads to cores turbo techno works not so efficient as without assignment. Result is 70-80% of max hashspeed + only 40-50% of CPU usage + low power consumption + user can normal work with computer. Even play not hard games. |
|
|
|
hi
found why my rig 580 doesn t love srb :auto intensity was 100 or 118....works great at 53.
why auto intensity is so high??
For normal cryptonight v7 100-118 is best. For CN heavy it's need half of CN V7 intensity. |
|
|
|
Same issue with 18.4.1. Goes from 27k+ to 0. Crash, restart, repeat. This is with Compute mode on or off. The old blockchain drivers still work well. Have not yet tried with 18.3.4 09:20:17:882 3634 ETH: GPU0 27.570 Mh/s
09:20:20:720 3634 ETH: checking pool connection...
09:20:20:721 3634 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
09:20:20:773 3634 buf: {"id":3,"jsonrpc":"2.0","result":SNIP]}
09:20:24:900 360c GPU0 t=62C fan=35%
09:20:25:696 3608 em hbt: 0, fm hbt: 15,
09:20:25:696 3608 watchdog - thread 0 (gpu0), hb time 2953
09:20:25:697 3608 watchdog - thread 1 (gpu0), hb time 2609
09:20:28:200 3634 buf: {"id":0,"jsonrpc":"2.0","result":}
09:20:28:200 3634 ETH: 05/08/18-09:20:28 - New job from us1.ethermine.org:5555
09:20:28:201 3634 target: 0x0000000112e0be82 (diff: 4000MH), epoch 185(2.45GB)
09:20:28:201 3634 ETH - Total Speed: 0.000 Mh/s, Total Shares: 1, Rejected: 0, Time: 00:02
09:20:28:202 3634 ETH: GPU0 0.000 Mh/s
09:20:30:595 3634 sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate",SNIP]}
09:20:30:632 3634 buf: {"id":6,"jsonrpc":"2.0","result":true}
09:20:30:735 3634 ETH: checking pool connection... You can free use 18.3.4 - they working fine. Claymore gone very quiet these days, hope everything is ok?
I'm fine, thanks, is v11.7 too old and you want v11.8 right now? Claymore, I'm encountered problems with Win 10 1803 and 18.4.1 drivers. My 1st GPU (active - monitor connected) drops hashrate to 0 after several minites (sometimes even less minute) after start. Sometimes hasrate rises than drops again, sometimes drops until restart miner. 2nd card (inactive - nothing connected) works normal. Use modded bios and setting OC and voltages in your miner. RX 580 8Gb cards. Maybe it's need to add something in miner to compatibilty with new drivers? 1803 and old 18.3.4 driver works normal. But I'm afraid that it will be on all new drivers too... Currently I recommend not to use 18.4.1 drivers. Thanks. That's what I use now. We'll see what will be with next drivers... |
|
|
|
i tried, but always got a few h/s less than with affinity set. The autoconfig always assign one CPU.
Did you find a case where no assignment really gave better result ?
No assignment can rise hashrate only with enabled Turbo technology and when less or equal half of cores used for mining. If more than half cores used Turbo didn't work... |
|
|
|
give me your bios
Samsung BIOS:  Hynix BIOS:  Bioses are allready modded. You must set right intensity. Read my previous post. Also you can try SRB Polaris Bios editor. In it doctor make it's own mods for bioses - so called "pumped" timings. |
|
|
|
|
Did you tried to not set affinity for threads? But it can affect only when not all cores used...
|
|
|
|
Here's another rig I have running Cryptonight-Heavy with GGS 1.3.7 alpha. This rig has 10x RX 570 8GB Nitro+ but somehow Windows 10 detects them as RX 580 after upgrading to Adrenaline 18.4.1 and my GGS settings: Those churning ~820 h/s are Samsung DDRs and the rest at ~750 h/s are Hynix I haven't toyed with the Memory Timings, kind of scared to fuck up my cards. Anyone can help me improve my hashrate please? Will be happy to give a tip (0.005 BTC) if someone can help me get them to ~900-1000+ with stability. Try other intensity. For heavy best is from 112 to 124. Also... You use original bioses? What memory vendor of your cards? |
|
|
|
Claymore gone very quiet these days, hope everything is ok?
I'm fine, thanks, is v11.7 too old and you want v11.8 right now? Claymore, I'm encountered problems with Win 10 1803 and 18.4.1 drivers. My 1st GPU (active - monitor connected) drops hashrate to 0 after several minites (sometimes even less minute) after start. Sometimes hasrate rises than drops again, sometimes drops until restart miner. 2nd card (inactive - nothing connected) works normal. Use modded bios and setting OC and voltages in your miner. RX 580 8Gb cards. Maybe it's need to add something in miner to compatibilty with new drivers? 1803 and old 18.3.4 driver works normal. But I'm afraid that it will be on all new drivers too... |
|
|
|
0.26 online - major updateTriple, Quad, Penta and Hexa hash
Faster on IPBC and Cryptolight (tested on my Ryzen, don't know how it behaves on Intel)
Faster on CN-Heavy (ditto)
New coin: Gadcoin
New coin: Loki
Next tasks: * Update the documentation * Add Stellite variation (that will be --variation 7) edit: bug reported about LOKI detection, workaround params: --any --variation 5
hotfix release to come soon Thanks! Wee will see... Did you compared triple, Quad, etc. speeds to XMRig? Strange situation with my FX8320 (Vishera). It have 8Mb L3 cache shared between all cores, and 8Mb L2 cache shered 4x2Mb, each 2Mb per 2 cores. So if I use 2 cores it can use 8Mb L3 and 2Mb L2 cache = 10Mb. But if I setup miner to 2 double threads (8Mb need) speed is faster 10-15 h/s than if I set 3+2 multihash threads (10Mb need). The same situation with any variants. Any variant with 8Mb cache is faster than 10Mb config... Not only 2 threads variants... Did you have Vishera to check? Maybe miner didn't use L2 cache? Or something else... On XMRig the same situation... |
|
|
|
BTW: When using the 18.3.4 driver, will the hashrate be the same or almost the same as with blockchain driver?
All AMD drivers released after august blockchain drivers contains all fixes from them. All next drivers gives speed not less than blockchain drivers. Only reason to stay on blockchain drivers is for Vega owners, as I know... |
|
|
|
|
Hi, zawawa! How are you?
It's new algo - PHI1612. Can you add him to GGS?
|
|
|
|
Can someone please share RX 570 hash rate and settings for Cryptonight-heavy algo? I'm getting around 500 H/s with Intensity 0 (auto).
It's low speed. Try setting intencity manual. |
|
|
|
Quote from: Littlegrand on Today at 08:51:51 AM
Quote
It is all right. The log shows cryptonight heave loaded, the share submitted to the correct url, just rejected wrong algo...
Correct url didn't means that you select correct url for cryptonight heavy algo.
Most pools have several ports for different algos. If you chose port for cryptonightv7 but in miner you select CN heavy algo, miner will connect to pool via seleted port, and pool allows to connect, but miner will finds shares for heavy and send them on pool to port from wich pool wait shares for cryptonightV7, due to port.
Check port number for your pool. Is you right pointed it for CN heavy.
Yes it is correct port(though it does not show port in log). The Haven address in log is correct as well.
It normal to say Switching to Monero 2 in log?
Any ideas?
Thanks
It's normal. But why you recieve rejected shares... Did you tried other miners?
What pool? Give address. Both Claymore and SRBMiner work fine. Wrote address and port of pool. zawawa will check it. Without these data how he can help you? |
|
|
|
|
Show Posts
