Search content
Sort by
Showing 20 of 27 results by LeonManveli
Re: PhoenixMiner 5.3b: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
I can mining with PhoenixMiner and GTX970, but with very low hashrate 7,8 mh/s .. is there any PhoenixMiner settings for ETChash mining for this card? Admin don't remove this post please 
Re: PhoenixMiner 5.1c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
Re: PhoenixMiner 5.1c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
Hello miners and devs.
Does anyone solved the problem with R9 390 [Hawaii] and Linux?
Does anyone solved the problem with R9 390 [Hawaii] and Linux?
Code:
GPU1 GPU1: Allocating DAG for epoch #384 (4.00) GB
GPU1 GPU1: Allocating buffers failed with: clCreateBuffer (-61).
Fatal error detected. Restarting.
GPU1 GPU1: Allocating buffers failed with: clCreateBuffer (-61).
Fatal error detected. Restarting.
+1
Re: [ANN] TeamRedMiner 0.7.15 - Nimiq/Kawpow/Ethash/Cryptonight and More
I installed the new version 0.7.15.
Pool - ethermine, RAVE OS
Card - Msi RX 5500XT, 4 GB
Yesterday her hash became 95KH/S !!
Put it on phoenix, on ELLA - got 27MH / s
I tried to prescribe the DAG-File limitation,"--eth_4g_max_alloc=374", "--eth_4g_max_alloc=4078", it does not help
Sapphires 470 4GB work great in the same Rig.
Should the PX 5500XT 4GB be supported by Team Red?
Pool - ethermine, RAVE OS
Card - Msi RX 5500XT, 4 GB
Yesterday her hash became 95KH/S !!
Put it on phoenix, on ELLA - got 27MH / s
I tried to prescribe the DAG-File limitation,"--eth_4g_max_alloc=374", "--eth_4g_max_alloc=4078", it does not help
Sapphires 470 4GB work great in the same Rig.
Should the PX 5500XT 4GB be supported by Team Red?
Ah man... I'm sorry to say I've completely forgotten about the 5500XT being another 4GB card. We only provide the special 4GB kernels for Polaris/Ellesmere right now. We need to include Navi versions of these kernels as well. Probably need to get a 5500XT to test as well. Thanks for mentioning.
Btw was this mining ETH or ETC? For ETC it's expected, hitting a pretty high epoch now.
Ah man... also you completely forgotten about the AMD R9 390
(Re: [Mining OS] SimpleMining.net - Manage Your GPU farm the easy way! (30 days free)
Hi, I've been mining with 7x r9 390 8GB with phoenix miner, but from 2/3 days ago it has started to reboot very often
So I disabled one to test if with only 6 would have the same error, but it mined for half hour and rebooted again
this a print form last crash:
GPUs: 1: 29.970 MH/s (18) 2: 29.970 MH/s (15) 3: 29.972 MH/s (13) 4: 29.971 MH/s (15) 5: 29.972 MH/s (14) 6: 29.972 MH/s (12)
GPU3: Starting up... (0)
GPU3: Generating ethash light cache for epoch #380
GPU6: Starting up... (0)
GPU4: Starting up... (0)
GPU5: Starting up... (0)
GPU1: Starting up... (0)
GPU2: Starting up... (0)
Light cache generated in 2.6 s (24.3 MB/s)
GPU3: Disabling DAG pre-allocation (not enough VRAM)
GPU6: Disabling DAG pre-allocation (not enough VRAM)
GPU4: Disabling DAG pre-allocation (not enough VRAM)
GPU5: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU2: Disabling DAG pre-allocation (not enough VRAM)
GPU3: Allocating DAG for epoch #380 (3.97) GB
GPU3: Allocating buffers failed with: clCreateBuffer (-61).
Fatal error detected. Restarting.
GPU6: Allocating DAG for epoch #380 (3.97) GB
GPU6: Allocating buffers failed with: clCreateBuffer (-61).
GPU4: Allocating DAG for epoch #380 (3.97) GB
GPU4: Allocating buffers failed with: clCreateBuffer (-61).
GPU5: Allocating DAG for epoch #380 (3.97) GB
GPU5: Allocating buffers failed with: clCreateBuffer (-61).
GPU1: Allocating DAG for epoch #380 (3.97) GB
GPU1: Allocating buffers failed with: clCreateBuffer (-61).
GPU2: Allocating DAG for epoch #380 (3.97) GB
GPU2: Allocating buffers failed with: clCreateBuffer (-61).
Eth speed: 0.000 MH/s, shares: 83/4/0, time: 0:26
Is this a miner error? Claymore also has this behaviour
teamred doesnt recognize hawaii?
witch version of linux image you have?So I disabled one to test if with only 6 would have the same error, but it mined for half hour and rebooted again
this a print form last crash:
GPUs: 1: 29.970 MH/s (18) 2: 29.970 MH/s (15) 3: 29.972 MH/s (13) 4: 29.971 MH/s (15) 5: 29.972 MH/s (14) 6: 29.972 MH/s (12)
GPU3: Starting up... (0)
GPU3: Generating ethash light cache for epoch #380
GPU6: Starting up... (0)
GPU4: Starting up... (0)
GPU5: Starting up... (0)
GPU1: Starting up... (0)
GPU2: Starting up... (0)
Light cache generated in 2.6 s (24.3 MB/s)
GPU3: Disabling DAG pre-allocation (not enough VRAM)
GPU6: Disabling DAG pre-allocation (not enough VRAM)
GPU4: Disabling DAG pre-allocation (not enough VRAM)
GPU5: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU2: Disabling DAG pre-allocation (not enough VRAM)
GPU3: Allocating DAG for epoch #380 (3.97) GB
GPU3: Allocating buffers failed with: clCreateBuffer (-61).
Fatal error detected. Restarting.
GPU6: Allocating DAG for epoch #380 (3.97) GB
GPU6: Allocating buffers failed with: clCreateBuffer (-61).
GPU4: Allocating DAG for epoch #380 (3.97) GB
GPU4: Allocating buffers failed with: clCreateBuffer (-61).
GPU5: Allocating DAG for epoch #380 (3.97) GB
GPU5: Allocating buffers failed with: clCreateBuffer (-61).
GPU1: Allocating DAG for epoch #380 (3.97) GB
GPU1: Allocating buffers failed with: clCreateBuffer (-61).
GPU2: Allocating DAG for epoch #380 (3.97) GB
GPU2: Allocating buffers failed with: clCreateBuffer (-61).
Eth speed: 0.000 MH/s, shares: 83/4/0, time: 0:26
Is this a miner error? Claymore also has this behaviour
teamred doesnt recognize hawaii?
It's running this image - SimpleMiningOS (SM-5.0.21-9-a18.20-n430.40)
- Kernel / Drv / upd: 5.0.21-sm9 / amd18.20r5.2.6 / v1291
I installed that image, and it has been also having random reboots with that error clCreateBuffer, but since today 8:00 AM it has been mining with no interruption, let's see how it goes, thanks
ah, with this image it lost core and mem speeds readings, it only shows 300/150,
I can change the powerstage slider but it won't show the correct readings
Re: PhoenixMiner 5.1c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
How to switch ETH to ETC?
i could mine ETH but not etc. i use PhoenixMiner 5.1c.
Any solution ?
Thanks
i could mine ETH but not etc. i use PhoenixMiner 5.1c.
Any solution ?
Thanks
-coin etc
Re: [Mining OS] SimpleMining.net - Manage Your GPU farm the easy way! (30 days free)
Hi, I've been mining with 7x r9 390 8GB with phoenix miner, but from 2/3 days ago it has started to reboot very often
So I disabled one to test if with only 6 would have the same error, but it mined for half hour and rebooted again
this a print form last crash:
GPUs: 1: 29.970 MH/s (18) 2: 29.970 MH/s (15) 3: 29.972 MH/s (13) 4: 29.971 MH/s (15) 5: 29.972 MH/s (14) 6: 29.972 MH/s (12)
GPU3: Starting up... (0)
GPU3: Generating ethash light cache for epoch #380
GPU6: Starting up... (0)
GPU4: Starting up... (0)
GPU5: Starting up... (0)
GPU1: Starting up... (0)
GPU2: Starting up... (0)
Light cache generated in 2.6 s (24.3 MB/s)
GPU3: Disabling DAG pre-allocation (not enough VRAM)
GPU6: Disabling DAG pre-allocation (not enough VRAM)
GPU4: Disabling DAG pre-allocation (not enough VRAM)
GPU5: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU2: Disabling DAG pre-allocation (not enough VRAM)
GPU3: Allocating DAG for epoch #380 (3.97) GB
GPU3: Allocating buffers failed with: clCreateBuffer (-61).
Fatal error detected. Restarting.
GPU6: Allocating DAG for epoch #380 (3.97) GB
GPU6: Allocating buffers failed with: clCreateBuffer (-61).
GPU4: Allocating DAG for epoch #380 (3.97) GB
GPU4: Allocating buffers failed with: clCreateBuffer (-61).
GPU5: Allocating DAG for epoch #380 (3.97) GB
GPU5: Allocating buffers failed with: clCreateBuffer (-61).
GPU1: Allocating DAG for epoch #380 (3.97) GB
GPU1: Allocating buffers failed with: clCreateBuffer (-61).
GPU2: Allocating DAG for epoch #380 (3.97) GB
GPU2: Allocating buffers failed with: clCreateBuffer (-61).
Eth speed: 0.000 MH/s, shares: 83/4/0, time: 0:26
Is this a miner error? Claymore also has this behaviour
teamred doesnt recognize hawaii?
witch version of linux image you have?So I disabled one to test if with only 6 would have the same error, but it mined for half hour and rebooted again
this a print form last crash:
GPUs: 1: 29.970 MH/s (18) 2: 29.970 MH/s (15) 3: 29.972 MH/s (13) 4: 29.971 MH/s (15) 5: 29.972 MH/s (14) 6: 29.972 MH/s (12)
GPU3: Starting up... (0)
GPU3: Generating ethash light cache for epoch #380
GPU6: Starting up... (0)
GPU4: Starting up... (0)
GPU5: Starting up... (0)
GPU1: Starting up... (0)
GPU2: Starting up... (0)
Light cache generated in 2.6 s (24.3 MB/s)
GPU3: Disabling DAG pre-allocation (not enough VRAM)
GPU6: Disabling DAG pre-allocation (not enough VRAM)
GPU4: Disabling DAG pre-allocation (not enough VRAM)
GPU5: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU2: Disabling DAG pre-allocation (not enough VRAM)
GPU3: Allocating DAG for epoch #380 (3.97) GB
GPU3: Allocating buffers failed with: clCreateBuffer (-61).
Fatal error detected. Restarting.
GPU6: Allocating DAG for epoch #380 (3.97) GB
GPU6: Allocating buffers failed with: clCreateBuffer (-61).
GPU4: Allocating DAG for epoch #380 (3.97) GB
GPU4: Allocating buffers failed with: clCreateBuffer (-61).
GPU5: Allocating DAG for epoch #380 (3.97) GB
GPU5: Allocating buffers failed with: clCreateBuffer (-61).
GPU1: Allocating DAG for epoch #380 (3.97) GB
GPU1: Allocating buffers failed with: clCreateBuffer (-61).
GPU2: Allocating DAG for epoch #380 (3.97) GB
GPU2: Allocating buffers failed with: clCreateBuffer (-61).
Eth speed: 0.000 MH/s, shares: 83/4/0, time: 0:26
Is this a miner error? Claymore also has this behaviour
teamred doesnt recognize hawaii?
It's running this image - SimpleMiningOS (SM-5.0.21-9-a18.20-n430.40)
- Kernel / Drv / upd: 5.0.21-sm9 / amd18.20r5.2.6 / v1291
Re: [Mining OS] SimpleMining.net - Manage Your GPU farm the easy way! (30 days free)
Hi, I've been mining with 7x r9 390 8GB with phoenix miner, but from 2/3 days ago it has started to reboot very often
So I disabled one to test if with only 6 would have the same error, but it mined for half hour and rebooted again
this a print form last crash:
GPUs: 1: 29.970 MH/s (18) 2: 29.970 MH/s (15) 3: 29.972 MH/s (13) 4: 29.971 MH/s (15) 5: 29.972 MH/s (14) 6: 29.972 MH/s (12)
GPU3: Starting up... (0)
GPU3: Generating ethash light cache for epoch #380
GPU6: Starting up... (0)
GPU4: Starting up... (0)
GPU5: Starting up... (0)
GPU1: Starting up... (0)
GPU2: Starting up... (0)
Light cache generated in 2.6 s (24.3 MB/s)
GPU3: Disabling DAG pre-allocation (not enough VRAM)
GPU6: Disabling DAG pre-allocation (not enough VRAM)
GPU4: Disabling DAG pre-allocation (not enough VRAM)
GPU5: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU2: Disabling DAG pre-allocation (not enough VRAM)
GPU3: Allocating DAG for epoch #380 (3.97) GB
GPU3: Allocating buffers failed with: clCreateBuffer (-61).
Fatal error detected. Restarting.
GPU6: Allocating DAG for epoch #380 (3.97) GB
GPU6: Allocating buffers failed with: clCreateBuffer (-61).
GPU4: Allocating DAG for epoch #380 (3.97) GB
GPU4: Allocating buffers failed with: clCreateBuffer (-61).
GPU5: Allocating DAG for epoch #380 (3.97) GB
GPU5: Allocating buffers failed with: clCreateBuffer (-61).
GPU1: Allocating DAG for epoch #380 (3.97) GB
GPU1: Allocating buffers failed with: clCreateBuffer (-61).
GPU2: Allocating DAG for epoch #380 (3.97) GB
GPU2: Allocating buffers failed with: clCreateBuffer (-61).
Eth speed: 0.000 MH/s, shares: 83/4/0, time: 0:26
Is this a miner error? Claymore also has this behaviour
teamred doesnt recognize hawaii?
witch version of linux image you have?So I disabled one to test if with only 6 would have the same error, but it mined for half hour and rebooted again
this a print form last crash:
GPUs: 1: 29.970 MH/s (18) 2: 29.970 MH/s (15) 3: 29.972 MH/s (13) 4: 29.971 MH/s (15) 5: 29.972 MH/s (14) 6: 29.972 MH/s (12)
GPU3: Starting up... (0)
GPU3: Generating ethash light cache for epoch #380
GPU6: Starting up... (0)
GPU4: Starting up... (0)
GPU5: Starting up... (0)
GPU1: Starting up... (0)
GPU2: Starting up... (0)
Light cache generated in 2.6 s (24.3 MB/s)
GPU3: Disabling DAG pre-allocation (not enough VRAM)
GPU6: Disabling DAG pre-allocation (not enough VRAM)
GPU4: Disabling DAG pre-allocation (not enough VRAM)
GPU5: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU2: Disabling DAG pre-allocation (not enough VRAM)
GPU3: Allocating DAG for epoch #380 (3.97) GB
GPU3: Allocating buffers failed with: clCreateBuffer (-61).
Fatal error detected. Restarting.
GPU6: Allocating DAG for epoch #380 (3.97) GB
GPU6: Allocating buffers failed with: clCreateBuffer (-61).
GPU4: Allocating DAG for epoch #380 (3.97) GB
GPU4: Allocating buffers failed with: clCreateBuffer (-61).
GPU5: Allocating DAG for epoch #380 (3.97) GB
GPU5: Allocating buffers failed with: clCreateBuffer (-61).
GPU1: Allocating DAG for epoch #380 (3.97) GB
GPU1: Allocating buffers failed with: clCreateBuffer (-61).
GPU2: Allocating DAG for epoch #380 (3.97) GB
GPU2: Allocating buffers failed with: clCreateBuffer (-61).
Eth speed: 0.000 MH/s, shares: 83/4/0, time: 0:26
Is this a miner error? Claymore also has this behaviour
teamred doesnt recognize hawaii?
Re: [Mining OS] SimpleMining.net - Manage Your GPU farm the easy way! (30 days free)
Hi guys! what wrong in my Teamredminer config? -a ethash -o stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -u 3GESoRhV1JLyBJLyBV61JLyBJop1Bd.Test -p x --api_listen=127.0.0.1:4029 --watchdog_script
If you have a Vega, and want to mine V7 algos, use Adrenaline 18.6.1 drivers, if you want to mine Heavy algos, use Adrenaline 18.3.4
And what about RX580 driver version to mine heavy and V7? Thank you Doktor83 for your work
Why are almost all the XMR coins in the Maintenance mode?
there's a bug
fix double counting outs if the tx pubkey is duplicated
https://github.com/monero-project/monero/commit/58cceaad7102c8e1c7130c47fa22cdb50eab97e8
most likely incorporating fixes
Thanks.
Hi All! is there any SRBMiner benchmark mode to test speed for (like Claymore) ?
- Cryptonight
- Cryptonight V7
- Cryptonight Lite
- Cryptonight Lite V7
- Cryptonight Heavy
- Cryptonight Ipbc
- Cryptonight ArtoCash
- Cryptonight Alloy
- Cryptonight MarketCash
- Cryptonight B2N
- Cryptonight StelliteV4
- Cryptonight Fast
- Cryptonight Haven
- Cryptonight
- Cryptonight V7
- Cryptonight Lite
- Cryptonight Lite V7
- Cryptonight Heavy
- Cryptonight Ipbc
- Cryptonight ArtoCash
- Cryptonight Alloy
- Cryptonight MarketCash
- Cryptonight B2N
- Cryptonight StelliteV4
- Cryptonight Fast
- Cryptonight Haven
Hi all! where is the SRBMiner Cryptonight AMD GPU Miner V1.6.0 link? there are only old versions
http://
http://
does any one have a amd 390? im mining haven and im seeing around 675-690hashs which seems low, my 580 with 2 threads is getting 1000-1100 on it.
maybe i don't have the config set up right for it.
usely the 390 beats the 580 in everything and usely comes really close too the 580 in normal crytonight. everything else the 390 edges it out.
maybe i don't have the config set up right for it.
usely the 390 beats the 580 in everything and usely comes really close too the 580 in normal crytonight. everything else the 390 edges it out.
I have Asus R9 390 and 730~800h/s. I'm mining Haven & Loki.. settings is Core v=-100mv, power limit =0, GPU clock=1100~1150mhz, Memory clock=1500.
miner: SRBminer v1.5.5, intensity=34, double Threads=True. Good Luck..