Search content
Sort by
Showing 20 of 29 results by cafemax
Re: Team Black Miner (Ethereum Ethereum classic Vertcoin Zilliqa 0.5% fee)LHR unlock
v1.46
1. If dag verification fails, copy a verified dag from another gpu. (NVIDIA)
1. If dag verification fails, copy a verified dag from another gpu. (NVIDIA)
I can't understand: if dag verification fail, it's mean a hardware error here,
Is there have any meaning? The card could make a lot invalid shares, the hash rate of pool will be bad.
Re: Team Black Miner (Ethereum Ethereum classic Vertcoin Zilliqa 0.5% fee)LHR unlock
The ver. grow so fast.The 1.40 still has the old problem: stale shares too high.
In my rig, it may add 50% ~ 100% stale shares than other miner. (About 1.5%~2.5% in total)
Because I am using flexpool, and cant change, so it's important to me.
Any way for fix?
BTW,
1. I get xint 71 in autodetect, it's too high, but specify to 24 (old ver), just improved a little....
2. No any hardware info reported. (All ver.)
00:09:12 [2022-01-18 21:53:22.088]
00:09:12 [2022-01-18 21:53:22.088]
00:09:12 [2022-01-18 21:53:22.088] ID BOARD TYPE KERN XINT TEMP FAN CORE MEM WATT
00:09:12 [2022-01-18 21:53:22.088] GPU0 6600 OpenCL 0 24 0/0 0 0 0 0
00:09:12 [2022-01-18 21:53:22.088] GPU1 6600 OpenCL 0 24 0/0 0 0 0 0
00:09:12 [2022-01-18 21:53:22.088] GPU2 6600 OpenCL 0 24 0/0 0 0 0 0
00:09:12 [2022-01-18 21:53:22.088] GPU3 6600 OpenCL 0 24 0/0 0 0 0 0
00:09:12 [2022-01-18 21:53:22.088] GPU4 6600 OpenCL 0 24 0/0 0 0 0 0
00:09:12 [2022-01-18 21:53:22.088] GPU5 6600 OpenCL 0 24 0/0 0 0 0 0
00:09:12 [2022-01-18 21:53:22.088] GPU6 6600 OpenCL 0 24 0/0 0 0 0 0
00:09:12 [2022-01-18 21:53:22.088] GPU7 6600 OpenCL 0 24 0/0 0 0 0 0
00:09:12 [2022-01-18 21:53:22.088]
------
AMD RX6600 * 8 + WIN10
Re: Team Black Miner (Ethereum Ethereum classic Vertcoin Zilliqa 0.5% fee)LHR unlock
v1.40
1. Fix build issue on AMD rigs.
2. Tiny improvement in the cuda kernel.
1. Fix build issue on AMD rigs.
2. Tiny improvement in the cuda kernel.
It's work,
Re: Team Black Miner (Ethereum Ethereum classic Vertcoin Zilliqa 0.5% fee)LHR unlock
xintensity to 1 / ETC algo, all the same.
Don't set --xintensity 1 , use --dagintensity 1
OK, I tested the --dagintensity 1, It's still.
Re: Team Black Miner (Ethereum Ethereum classic Vertcoin Zilliqa 0.5% fee)LHR unlock
I am back.
This time I tried the 1.39, I got this:
00:00:00 [2022-01-15 18:26:54.937]
00:00:00 [2022-01-15 18:26:55.195] OpenCL driver version: 335.0
00:00:00 [2022-01-15 18:26:55.195] Cuda driver version: 0.0
00:00:00 [2022-01-15 18:26:55.195] Cuda runtime API version: 11.6
00:00:00 [2022-01-15 18:26:55.195]
00:00:00 [2022-01-15 18:26:55.195]
00:00:00 [2022-01-15 18:26:55.195]
00:00:00 [2022-01-15 18:26:55.195] Welcome to Team Black Miner 1.39
00:00:00 [2022-01-15 18:26:55.195]
00:00:00 [2022-01-15 18:26:55.195]
00:00:00 [2022-01-15 18:26:55.195] GPU0 gfx1032 8GB added to miner as OpenCL device
00:00:00 [2022-01-15 18:26:55.195] GPU1 gfx1032 8GB added to miner as OpenCL device
00:00:00 [2022-01-15 18:26:55.195] GPU2 gfx1032 8GB added to miner as OpenCL device
00:00:00 [2022-01-15 18:26:55.195] Trying eth-hk.flexpool.io:4444 (ethash)
00:00:00 [2022-01-15 18:26:55.218] GPU0 Started CL work thread
00:00:00 [2022-01-15 18:26:55.233] GPU1 Started CL work thread
00:00:00 [2022-01-15 18:26:55.249] GPU2 Started CL work thread
00:00:00 [2022-01-15 18:26:55.272] Pool responded successfully to subscribe
00:00:00 [2022-01-15 18:26:55.296] Pool responded successfully to extranonce subscribe
00:00:00 [2022-01-15 18:26:55.311] Pool responded successfully to authorize
00:00:00 [2022-01-15 18:26:55.311] Difficulty is set to 0.931308
00:00:00 [2022-01-15 18:26:55.326] GPU0 Starting generating ethash dag (Epoch: 466)
00:00:00 [2022-01-15 18:26:55.326] GPU1 Starting generating ethash dag (Epoch: 466)
00:00:00 [2022-01-15 18:26:55.326] GPU2 Starting generating ethash dag (Epoch: 466)
00:00:00 [2022-01-15 18:26:58.657] Shutting down threads
00:00:00 [2022-01-15 18:26:58.665] Control thread exited
00:00:00 [2022-01-15 18:26:58.665] Stratum thread exited
xintensity to 1 / ETC algo, all the same.
BTW,
1. The rig has a little different from last one, it's 3 card RX 6600 with another MB, AMD Driver: 21.12.1
2. log file was created, but empty (0 size)
3. sometimes can start up correctly, it's randomly in rare.
This time I tried the 1.39, I got this:
00:00:00 [2022-01-15 18:26:54.937]
00:00:00 [2022-01-15 18:26:55.195] OpenCL driver version: 335.0
00:00:00 [2022-01-15 18:26:55.195] Cuda driver version: 0.0
00:00:00 [2022-01-15 18:26:55.195] Cuda runtime API version: 11.6
00:00:00 [2022-01-15 18:26:55.195]
00:00:00 [2022-01-15 18:26:55.195]
00:00:00 [2022-01-15 18:26:55.195]
00:00:00 [2022-01-15 18:26:55.195] Welcome to Team Black Miner 1.39
00:00:00 [2022-01-15 18:26:55.195]
00:00:00 [2022-01-15 18:26:55.195]
00:00:00 [2022-01-15 18:26:55.195] GPU0 gfx1032 8GB added to miner as OpenCL device
00:00:00 [2022-01-15 18:26:55.195] GPU1 gfx1032 8GB added to miner as OpenCL device
00:00:00 [2022-01-15 18:26:55.195] GPU2 gfx1032 8GB added to miner as OpenCL device
00:00:00 [2022-01-15 18:26:55.195] Trying eth-hk.flexpool.io:4444 (ethash)
00:00:00 [2022-01-15 18:26:55.218] GPU0 Started CL work thread
00:00:00 [2022-01-15 18:26:55.233] GPU1 Started CL work thread
00:00:00 [2022-01-15 18:26:55.249] GPU2 Started CL work thread
00:00:00 [2022-01-15 18:26:55.272] Pool responded successfully to subscribe
00:00:00 [2022-01-15 18:26:55.296] Pool responded successfully to extranonce subscribe
00:00:00 [2022-01-15 18:26:55.311] Pool responded successfully to authorize
00:00:00 [2022-01-15 18:26:55.311] Difficulty is set to 0.931308
00:00:00 [2022-01-15 18:26:55.326] GPU0 Starting generating ethash dag (Epoch: 466)
00:00:00 [2022-01-15 18:26:55.326] GPU1 Starting generating ethash dag (Epoch: 466)
00:00:00 [2022-01-15 18:26:55.326] GPU2 Starting generating ethash dag (Epoch: 466)
00:00:00 [2022-01-15 18:26:58.657] Shutting down threads
00:00:00 [2022-01-15 18:26:58.665] Control thread exited
00:00:00 [2022-01-15 18:26:58.665] Stratum thread exited
xintensity to 1 / ETC algo, all the same.
BTW,
1. The rig has a little different from last one, it's 3 card RX 6600 with another MB, AMD Driver: 21.12.1
2. log file was created, but empty (0 size)
3. sometimes can start up correctly, it's randomly in rare.
Re: Team Black Miner (Ethereum Ethereum classic Vertcoin Zilliqa 0.5% fee)LHR unlock
Sometime only 1 card can launch success (My rig has 8 cards).
Did you try --dagintensity 1
You need to setup virtual memory. 40GB or more. Is ethereum classic working?
VRAM 40GB -> yes, my VRAM is set > 55G
--dagintensity 1 / ethereum classic -> no, I have no time to try.
Because the rig is not my own, so I need to switch to the older miner and keep working.
If I have the update information, I will post.
Re: Team Black Miner (Ethereum Ethereum classic Vertcoin Zilliqa 0.5% fee)LHR unlock
I cant start mining even only 1 card in 1.37 & 1.38, but 1.35 is total normally. The config is all the same.
Windows 10, AMD RX 6600
Windows 10, AMD RX 6600
cuda 11.4 or 11.5? whats the config?
Cuda 11.5, but my card is AMD
The parameter:
TBMiner --algo ethash --hostname %POOL% --port 4444 --wallet %WALLET% --worker-name %Worker% --log --logfile log\%datetimef%.txt
BTW,
OpenCL ver 330.0
AMD Driver 21.11.3
Sometime only 1 card can launch success.
Re: Team Black Miner (Ethereum Ethereum classic Vertcoin Zilliqa 0.5% fee)LHR unlock
I cant start mining even only 1 card in 1.38, but 1.35 is total normally. The config is all the same.
Windows 10, AMD RX 6600
00:00:00 [2022-01-13 00:49:50.048]
00:00:00 [2022-01-13 00:49:50.048] GPU0 gfx1032 8GB added to miner as OpenCL device
00:00:00 [2022-01-13 00:49:50.048] Trying eth-hk.flexpool.io:4444 (ethash)
00:00:00 [2022-01-13 00:49:50.075] GPU0 Started CL work thread
00:00:00 [2022-01-13 00:49:50.095] Pool responded successfully to subscribe
00:00:00 [2022-01-13 00:49:50.123] Pool responded successfully to extranonce subscribe
00:00:00 [2022-01-13 00:49:50.140] Pool responded successfully to authorize
00:00:00 [2022-01-13 00:49:50.140] Difficulty is set to 0.931308
00:00:00 [2022-01-13 00:49:50.156] GPU0 Starting generating ethash dag (Epoch: 466)
0x00007FFA39C23E49 (0x00000090F7EFA7B8 0x0000021DA9B889B0 0x00000090F7EFA730 0x0000021D00000000), RaiseException() + 0x69 bytes(s)
0x00007FFA2A894572 (0x00007FF6062B0000 0x00000090F7EFA880 0x0000021DA99E8220 0x00000000FFFFFFF5), _CxxThrowException() + 0xC2 bytes(s)
0x00007FF6062EB03F (0x00000090F7EFA880 0x0000021D96A02210 0x00000090F7EFA888 0x0000021DA9724130)
0x00007FF6062EE004 (0x0000000000000000 0x0000000000000000 0x00007FF606354501 0x00000000000001D2)
0x00007FF606324C4B (0x0000021D969CA070 0x0000000000000000 0x0000000000000000 0x0000000000000000)
0x00007FFA399F14C2 (0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000), _configthreadlocale() + 0x92 bytes(s)
0x00007FFA3BA17034 (0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000), BaseThreadInitThunk() + 0x14 bytes(s)
0x00007FFA3C1BCEC1 (0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000), RtlUserThreadStart() + 0x21 bytes(s)
Windows 10, AMD RX 6600
00:00:00 [2022-01-13 00:49:50.048]
00:00:00 [2022-01-13 00:49:50.048] GPU0 gfx1032 8GB added to miner as OpenCL device
00:00:00 [2022-01-13 00:49:50.048] Trying eth-hk.flexpool.io:4444 (ethash)
00:00:00 [2022-01-13 00:49:50.075] GPU0 Started CL work thread
00:00:00 [2022-01-13 00:49:50.095] Pool responded successfully to subscribe
00:00:00 [2022-01-13 00:49:50.123] Pool responded successfully to extranonce subscribe
00:00:00 [2022-01-13 00:49:50.140] Pool responded successfully to authorize
00:00:00 [2022-01-13 00:49:50.140] Difficulty is set to 0.931308
00:00:00 [2022-01-13 00:49:50.156] GPU0 Starting generating ethash dag (Epoch: 466)
0x00007FFA39C23E49 (0x00000090F7EFA7B8 0x0000021DA9B889B0 0x00000090F7EFA730 0x0000021D00000000), RaiseException() + 0x69 bytes(s)
0x00007FFA2A894572 (0x00007FF6062B0000 0x00000090F7EFA880 0x0000021DA99E8220 0x00000000FFFFFFF5), _CxxThrowException() + 0xC2 bytes(s)
0x00007FF6062EB03F (0x00000090F7EFA880 0x0000021D96A02210 0x00000090F7EFA888 0x0000021DA9724130)
0x00007FF6062EE004 (0x0000000000000000 0x0000000000000000 0x00007FF606354501 0x00000000000001D2)
0x00007FF606324C4B (0x0000021D969CA070 0x0000000000000000 0x0000000000000000 0x0000000000000000)
0x00007FFA399F14C2 (0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000), _configthreadlocale() + 0x92 bytes(s)
0x00007FFA3BA17034 (0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000), BaseThreadInitThunk() + 0x14 bytes(s)
0x00007FFA3C1BCEC1 (0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000), RtlUserThreadStart() + 0x21 bytes(s)
hello, I have a rig of 6 Sapphire Radeon RX 6600 Pulse cards (not XT), currently I use the default settings: core clock 950; memory clock 930 and core voltage 625. Memory voltage and memory control voltage I don’t have them set.
Currently I get 28.2MH/s per card and 50W of power consumption.
The fans are on 10% fixed, with a temperature of 50°C fixed.
Do you think it’s a good setting or you could do better, especially to preserve the GPU over time?
Currently I get 28.2MH/s per card and 50W of power consumption.
The fans are on 10% fixed, with a temperature of 50°C fixed.
Do you think it’s a good setting or you could do better, especially to preserve the GPU over time?
I really hate RX 6600. Everything is weird:
1. Setting is total different between HiveOS and Windows. On those system, they looks like different graphic card.
2. Driver almost in beta. I can't read SoC clock in windows, and there is no SoC VDD in HiveOS.
3. Setting and result maybe 2 different things, especially in Windows.
4. If some GPU crashed, windows will hang up in 1 hours, and reboot is not working. You can remote connect in and bemoan.
5. Run slower and slower in period time.
6. Every time start miner, you may get different hashrate. Or some card could drop it's hashrate when working.
Lot and lot problems here, but no miner developer care, because break through the LHR is hot, and the Big Navi is suck.
In finally, if you can get 28.2M "pool hashrate" at 50W and stable, it's really great.
Yes, It's my weird rigs.
I have some Mining dedicated rig made from China, the motherboard have 8 slot, B85 chipset and G1840 CPU, 1 x 4G DDR3 SODIMM, all things old,
But fast than my X570S with AMD Ryzen PRO 4350G, with 8G DDR4, about ~1%.
I compared everything but no idea why.
I have some Mining dedicated rig made from China, the motherboard have 8 slot, B85 chipset and G1840 CPU, 1 x 4G DDR3 SODIMM, all things old,
But fast than my X570S with AMD Ryzen PRO 4350G, with 8G DDR4, about ~1%.
I compared everything but no idea why.
Re: Team Black Miner (Ethereum Ethereum classic Vertcoin Zilliqa 0.5% fee)LHR unlock
I have a weird bug in 1.35 with flexpool.
When it happend:
01:03:07 [2021-12-29 15:05:57.006] Have not received data from pool for 20 seconds
01:03:07 [2021-12-29 15:05:57.006] Stratum thread exited
01:03:07 [2021-12-29 15:05:57.016] Pool connection disconnected or timed out
In the next period of time, I will get continuously invalid share like this:
01:03:08 [2021-12-29 15:06:41.204] GPU4 Solution found in 10.71s (Submit every 16.72 seconds)
01:03:08 [2021-12-29 15:06:41.234] Rejected (5755/5756) Reply: 23ms
01:03:08 [2021-12-29 15:06:41.234] mining.submit: Pool reponded with error
01:03:08 [2021-12-29 15:06:41.234] Error(-2): Invalid PoW Solution
The period may keep 17 ~ 19 min, make me 50+ invalid shares.
If not in this status, my rig has no any invalid shares.
I am sure not a connect problem, because my other rigs are working correct in the same time, and the gminer is never happend.
Please fix it,
When it happend:
01:03:07 [2021-12-29 15:05:57.006] Have not received data from pool for 20 seconds
01:03:07 [2021-12-29 15:05:57.006] Stratum thread exited
01:03:07 [2021-12-29 15:05:57.016] Pool connection disconnected or timed out
In the next period of time, I will get continuously invalid share like this:
01:03:08 [2021-12-29 15:06:41.204] GPU4 Solution found in 10.71s (Submit every 16.72 seconds)
01:03:08 [2021-12-29 15:06:41.234] Rejected (5755/5756) Reply: 23ms
01:03:08 [2021-12-29 15:06:41.234] mining.submit: Pool reponded with error
01:03:08 [2021-12-29 15:06:41.234] Error(-2): Invalid PoW Solution
The period may keep 17 ~ 19 min, make me 50+ invalid shares.
If not in this status, my rig has no any invalid shares.
I am sure not a connect problem, because my other rigs are working correct in the same time, and the gminer is never happend.
Please fix it,
Re: Team Black Miner (Ethereum Ethereum classic Vertcoin Zilliqa 0.5% fee)LHR unlock
Sorry for this basic question, but I can't find these answer:
1. What dose share 0/0/0 mean? Submitted/Accept/Invalid ?
2. How to specify each AMD card? If I use -Y 0,1 , it blow up 50 cards that I don't have....
3. What different with --
TeamBlackMiner_1_35_cuda_11_2.7z
TeamBlackMiner_1_35_cuda_11_4.7z
TeamBlackMiner_1_35_cuda_11_5.7z
??
Thanks for answer.
1. What dose share 0/0/0 mean? Submitted/Accept/Invalid ?
2. How to specify each AMD card? If I use -Y 0,1 , it blow up 50 cards that I don't have....
3. What different with --
TeamBlackMiner_1_35_cuda_11_2.7z
TeamBlackMiner_1_35_cuda_11_4.7z
TeamBlackMiner_1_35_cuda_11_5.7z
??
Thanks for answer.
Re: GMiner v2.72 Ethash(LHR unlock)/KAWPOW/Equihash/CuckooCycle
How to log a file with auto date/time name?
I use -l log.txt but it log once only, even not overwrite it if restart miner.
What I do wrong?
Windows 10
Gminer v2.72
Thanks.
I use -l log.txt but it log once only, even not overwrite it if restart miner.
What I do wrong?
Windows 10
Gminer v2.72
Thanks.
Re: PhoenixMiner 5.8c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
I can't modify the overclock settings of my RX 6600 with PhoenixMiner 5.9b in windows.
Using AMD driver 21.11.2.
It's my oc settings:
-fanmin 50 -fanmax 50 -mclock 945 -cvddc 735 -mvddc 1150 -cclock 900 -amd
But nothing changed.
What should I do?
System:
Windows 10 20H2
B85 / G1840 / 4G RAM
MSI MECH RX 6600 x 8 (Every card can work)
AMD driver 21.11.2
Thanks.
Amazing.
1. What is your system RAM and HBCC setting?
2. press 'r' to see if the shares are correctly. Pool diff / hashrate should nearby the avg. time.
mining several hours,
https://imgur.com/CknvPMo
with No error. is it ture hashrate??
my test rig set up
CPU:intel core i5 6400
memory:DDR4-2133 8GB
systemdisk:samusung sm961 256GB m.2 pci-e
PSU:500W
virtualmemory:32768MB
I have no idea, the diff is changing... what about your pool report?
And if you increase the memory clock, will it get more hashrate?
You can try use hwinfo64 to monitor.
i bought a new MSI vega56.
it arrived today,so i set up and some tune on my test rig.
first,i tried stock bios and softpowerplay, it set CORE 1400mhz MEM 950Mhz.
probably,hit it around 1800H/s i guess, but it hit 1900H/s.(used block-chain-driver)
i have no idea this situation. its legendly silicon? lol
GPU-Z show MEM 950 actually. anyone have idea?
https://imgur.com/cLYHU17
it arrived today,so i set up and some tune on my test rig.
first,i tried stock bios and softpowerplay, it set CORE 1400mhz MEM 950Mhz.
probably,hit it around 1800H/s i guess, but it hit 1900H/s.(used block-chain-driver)
i have no idea this situation. its legendly silicon? lol
GPU-Z show MEM 950 actually. anyone have idea?
https://imgur.com/cLYHU17
Amazing.
1. What is your system RAM and HBCC setting?
2. press 'r' to see if the shares are correctly. Pool diff / hashrate should nearby the avg. time.
I have a card that ran fine for 3 days with softplaymod 0.9V 1400/1100 but now whenever its on load whether it be mining or a benchmark like furmark it instantly crashes. the GPU tach lights turn off and the fan suddenly seems to run at full speed.
A restart doesnt even fix it. I have to fully shutdown the rig.
Any ideas what could be the cause? I've tried moving slots, risers, PSU, DDU driver uninstall and reinstall, no softplaymod at stock settings and it still happens...
A restart doesnt even fix it. I have to fully shutdown the rig.
Any ideas what could be the cause? I've tried moving slots, risers, PSU, DDU driver uninstall and reinstall, no softplaymod at stock settings and it still happens...
So is it crash at full stock setting now?
Try test one card a time, find out the broken one then RMA.
BTW, why you want to run furmark?
Blockchain mining use a part of GPU only, not all. So you can not measure steady through 3D benchmark.
try to remove 2 rx 560 cards from rig.
With current amd drivers there is a problem with HBCC for Vega if you have more then 4 any AMD cards in the rig.
Also 32 gb virtual memory can be not enough
With current amd drivers there is a problem with HBCC for Vega if you have more then 4 any AMD cards in the rig.
Also 32 gb virtual memory can be not enough
Thank you for the recommend. And also I find the 8G system RAM looks not very enough.
I got a trouble...
My rig have 2 RX560 + 3 RX470 and 1 Vega.
HBCC can be set to en/dis , but slide is fixed:
https://i.imgur.com/ofhjO5u.jpg
Whatever how I change the HBCC en/dis, in XMR-Stak-AMD, hashrate looks like not enabled.
What going on?
Win10 / Blockchain beta driver / 8G system RAM / 32G VRAM
Vega56 w/vega 64 Aircool bios
All other things looks like normal.
Thanks.