New BETA SimpleMining image:
- SM-5.4.52-7-a20.30-n455.38
- New NVIDIA beta driver with RTX 3070 support
- Image is available in download section and in "Advanced commands"
Topic: [Mining OS] SimpleMining.net - Manage Your GPU farm the easy way! (30 days free) - page 40. (Read 835515 times)
October 30, 2020, 07:19:16 AM
October 30, 2020, 03:48:20 AM
Miners update:
- miniz-v1.6w2 (192,7 major improvements: 2-11% - most on Turing GPUs, and 1050 Ti. Reduced invalid shares on 192,7. Added 2GB kernel for 192,7. Added experimental support for Ampere GPUs)
- nbminer-nebutech-v33.1 (Fix some format error on console. Optimize octopus lower CPU usage. New option --share-check, if no share found in a set period of time, miner will reboot. default to 30 minutes. SOLO miners should set this option to 0 to turn off check)
- miniz-v1.6w2 (192,7 major improvements: 2-11% - most on Turing GPUs, and 1050 Ti. Reduced invalid shares on 192,7. Added 2GB kernel for 192,7. Added experimental support for Ampere GPUs)
- nbminer-nebutech-v33.1 (Fix some format error on console. Optimize octopus lower CPU usage. New option --share-check, if no share found in a set period of time, miner will reboot. default to 30 minutes. SOLO miners should set this option to 0 to turn off check)
October 29, 2020, 09:31:14 AM
Update v1294:
- Fixed missing system RAM size information in dashboard details
- Fixed "Checking Internet connection" issues during rig startup
- Fixed lolminer API units stats with ethash mining
- Fixed missing system RAM size information in dashboard details
- Fixed "Checking Internet connection" issues during rig startup
- Fixed lolminer API units stats with ethash mining
October 29, 2020, 03:55:09 AM
Miners update:
- t-rex-v0.18.5 (Ethash performance improvements for Pascal GPUs on some configurations. Ethash allow mining at a decreased hashrate when DAG no longer fits GPU memory)
- t-rex-v0.18.5 (Ethash performance improvements for Pascal GPUs on some configurations. Ethash allow mining at a decreased hashrate when DAG no longer fits GPU memory)
October 28, 2020, 07:18:09 AM
Miners update:
- nbminer-nebutech-v33.0 (New algo octopus for mining conflux - support both solo and pool mining, need Nvidia GPU above 6G. Ethash improve performance on Vega & Navi. Beamv3 improve performance on high end 10xx Nvidia. Modify summary output on console, add share statistics for each GPU. Ethash fix zero hashrate on certain cases for AMD)
- nbminer-nebutech-v33.0 (New algo octopus for mining conflux - support both solo and pool mining, need Nvidia GPU above 6G. Ethash improve performance on Vega & Navi. Beamv3 improve performance on high end 10xx Nvidia. Modify summary output on console, add share statistics for each GPU. Ethash fix zero hashrate on certain cases for AMD)
October 26, 2020, 06:08:37 AM
Advanced Command update:
- New option with custom reflash to make rig as local image file cache for faster reflash more than one rig. Option called "download" for downloading image and share it for other rigs in network makes them faster download via local network in case of utilizing slow Internet connection every time. More details with examples available in Advanced Commands by selecting "Reflash: custom image".
- New option with custom reflash to make rig as local image file cache for faster reflash more than one rig. Option called "download" for downloading image and share it for other rigs in network makes them faster download via local network in case of utilizing slow Internet connection every time. More details with examples available in Advanced Commands by selecting "Reflash: custom image".
October 24, 2020, 03:27:01 PM
/root/xminer.sh: line 174: 6805 Killed $minerSudo /root/miner/$MINER_PKG_NAME_/_$MINER_FILE $MINER_OPTIONS_GO
Miner ended or crashed. Restarting miner in 30 seconds...
having that error TeamRedMiner , any idea ?
my rig just reboot every 2mins
Miner ended or crashed. Restarting miner in 30 seconds...
having that error TeamRedMiner , any idea ?
my rig just reboot every 2mins
October 24, 2020, 11:35:39 AM
Miners update:
- teamredminer-v0.7.16c (Beta release. Chukwa2: fixed kernels loading for Radeon VII gpus and fixed mem footprint for 2GB gpus)
- teamredminer-v0.7.16c (Beta release. Chukwa2: fixed kernels loading for Radeon VII gpus and fixed mem footprint for 2GB gpus)
October 23, 2020, 02:16:16 AM
Miners update:
- teamredminer-v0.7.16b (Beta release - Added algo trtl_chukwa2 for the Turtlecoin fork on 2020-10-22. Only use for the Turtlecoin fork. Navi gpus are NOT supported on chukwa2 for now)
- teamredminer-v0.7.16b (Beta release - Added algo trtl_chukwa2 for the Turtlecoin fork on 2020-10-22. Only use for the Turtlecoin fork. Navi gpus are NOT supported on chukwa2 for now)
October 22, 2020, 06:42:33 AM
Update v1292:
- Fixed NVIDIA RTX 3000 series fan problem that caused nearly 100% fan speed
- Fixed NVIDIA RTX 3000 series fan problem that caused nearly 100% fan speed
October 21, 2020, 11:49:44 PM
Is there a promotional code for registration? 
October 21, 2020, 02:45:11 AM
Miners update:
- teamredminer-v0.7.15 (Ethash: fixed bug for ZIL (epoch 0) mining on 4GB gpus (bug appeared in 0.7.14). Ethash: reverted to v0.7.10 kernels for stability purposes except for ROCm-based rigs)
- teamredminer-v0.7.15 (Ethash: fixed bug for ZIL (epoch 0) mining on 4GB gpus (bug appeared in 0.7.14). Ethash: reverted to v0.7.10 kernels for stability purposes except for ROCm-based rigs)
October 20, 2020, 02:24:25 PM
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
October 19, 2020, 05:58:07 AM
Miners update:
- xmrig-v6.4.0-fix (Fixed release with cn/r and kawpow mining fault issue on NVIDIA)
- xmrig-v6.4.0-fix (Fixed release with cn/r and kawpow mining fault issue on NVIDIA)
October 19, 2020, 03:31:13 AM
Miners update:
- xmrig-v6.4.0 (Removed rx/loki. Added argon2/chukwav2. Added benchmark and stress test. RandomX: improved software AES performance, fixed unexpected resume due to disconnect during dataset init, fixed randomx_create_vm call, fixed crash on x86, added huge-pages-jit config parameter. Fixed possible race condition in hashrate counting code. General code improvements. Added more precise hashrate calculation. Fixed libuv performance issue)
- xmrig-v6.4.0 (Removed rx/loki. Added argon2/chukwav2. Added benchmark and stress test. RandomX: improved software AES performance, fixed unexpected resume due to disconnect during dataset init, fixed randomx_create_vm call, fixed crash on x86, added huge-pages-jit config parameter. Fixed possible race condition in hashrate counting code. General code improvements. Added more precise hashrate calculation. Fixed libuv performance issue)
October 18, 2020, 11:56:36 AM
Miners update:
- gminer-v2.29 (Caching DAG file, very useful for Ethash+ZIL mining, miner will not spend time on creating DAG file on Ethash/ZIL change after caching. Minimize memory allocation for DAG file. Fixed All DevFee mining pool are unavailable error on Ethash)
- t-rex-v0.18.2 (New parameter --watchdog-exit-mode to perform actions when miner gets restarted multiple times. Print current mining pool in the GPU hashrate table. Bug fixes with progpow-veil for VEIL's upcoming fork. Now miner available with CUDA 9.1/9.2/10.0/11.1 compatibility)
- gminer-v2.29 (Caching DAG file, very useful for Ethash+ZIL mining, miner will not spend time on creating DAG file on Ethash/ZIL change after caching. Minimize memory allocation for DAG file. Fixed All DevFee mining pool are unavailable error on Ethash)
- t-rex-v0.18.2 (New parameter --watchdog-exit-mode to perform actions when miner gets restarted multiple times. Print current mining pool in the GPU hashrate table. Bug fixes with progpow-veil for VEIL's upcoming fork. Now miner available with CUDA 9.1/9.2/10.0/11.1 compatibility)
October 18, 2020, 11:28:56 AM
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
October 17, 2020, 09:50:39 AM
Miners update:
- wildrig-multi-v0.28.1 (Beta release. Updated progpow-veil for started testnet. Lowered devfee on megabtx and megamec to default 1%)
- wildrig-multi-v0.28.1 (Beta release. Updated progpow-veil for started testnet. Lowered devfee on megabtx and megamec to default 1%)
October 16, 2020, 02:52:11 PM
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
October 16, 2020, 02:43:03 PM
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
Jump to: