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)
Topic: [Mining OS] SimpleMining.net - Manage Your GPU farm the easy way! (30 days free) - page 41. (Read 835786 times)
October 23, 2020, 01:16:16 AM
October 22, 2020, 05: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, 10:49:44 PM
Is there a promotional code for registration? 
October 21, 2020, 01: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, 01: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, 04: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, 02: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, 10: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, 10: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, 08: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, 01: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, 01: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
October 16, 2020, 11:58:25 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?
October 16, 2020, 11:20:37 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?
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?
October 15, 2020, 07:54:51 AM
Miners update:
- lolminer-v1.11 (Added experimental ZOMBIE mode for 4G AMD GPUs Fiji & Polaris. This allow continue mining Ethash above the 4G DAG size limit with some time memory trade of. This allows efficient ETH mining until ~February in Linux. Reworked of Ethash memory allocation strategies. Fixed BeamHashIII for R9 380 8G cards - now use the working 4G code)
- teamredminer-v0.7.14 (Ethash: verified Linux support for 4GB gpus up to and including epoch 381. Ethash: added support for extended 4GB mining from epoch 382 and up. Kawpow: cleaned up false hw errs for some block heights)
- lolminer-v1.11 (Added experimental ZOMBIE mode for 4G AMD GPUs Fiji & Polaris. This allow continue mining Ethash above the 4G DAG size limit with some time memory trade of. This allows efficient ETH mining until ~February in Linux. Reworked of Ethash memory allocation strategies. Fixed BeamHashIII for R9 380 8G cards - now use the working 4G code)
- teamredminer-v0.7.14 (Ethash: verified Linux support for 4GB gpus up to and including epoch 381. Ethash: added support for extended 4GB mining from epoch 382 and up. Kawpow: cleaned up false hw errs for some block heights)
October 12, 2020, 01:17:38 PM
Can you please add T-Rex with cuda 11.1?
October 11, 2020, 10:03:28 AM
Miners update:
- t-rex-v0.18.1 (Added algos: progpow-veriblock (for Veriblock), progpow-veil (VEIL's upcoming fork), megabtx (Bitcore). Stratum+tcp automatically selects the most commonly used pool protocol for a given algorithm (use stratum1/2+tcp). Bug fixes: Occasional crashes on miner shutdown. Miner wouldn't start if some of the GPUs aren't supported even though they are deselected via -d. Ethash consuming memory on the GPUs deselected by -d)
- t-rex-v0.18.1 (Added algos: progpow-veriblock (for Veriblock), progpow-veil (VEIL's upcoming fork), megabtx (Bitcore). Stratum+tcp automatically selects the most commonly used pool protocol for a given algorithm (use stratum1/2+tcp). Bug fixes: Occasional crashes on miner shutdown. Miner wouldn't start if some of the GPUs aren't supported even though they are deselected via -d. Ethash consuming memory on the GPUs deselected by -d)
October 10, 2020, 05:16:16 AM
Miners update:
- gminer-v2.28 (Support ETH/ETC+ZIL mining. Fixed compatibility with luckypool.io for Zano. Fixed "All DevFee pools are unavailable" error for Grimm)
- gminer-v2.28 (Support ETH/ETC+ZIL mining. Fixed compatibility with luckypool.io for Zano. Fixed "All DevFee pools are unavailable" error for Grimm)
October 09, 2020, 05:21:32 PM
I'm building a new rig with 6x 5700xt and all works fine with 5, I get the below when I add the sixth GPU (all stock, brand new - out the box GPUS)
- I've tried multiple risers, all the same... Is this card Dead on arrival?
I don't know what 99% of that is, but this stands out.. [ 6.875772] RIP: 0010:amdgpu_mm_wreg+0x116/0x170 [amdgpu]
RIP? lol
Cheers
- I've tried multiple risers, all the same... Is this card Dead on arrival?
Code:
[ 5.831599] [drm] set register base offset for OSSSYS
[ 5.831599] [drm] set register base offset for SDMA0
[ 5.831600] [drm] set register base offset for SDMA1
[ 5.831600] [drm] set register base offset for SMUIO
[ 5.831600] [drm] set register base offset for THM
[ 5.831601] [drm] set register base offset for UVD
[ 5.831603] [drm] add ip block number 0 _nv_common_
[ 5.831603] [drm] add ip block number 1 _gmc_v10_0_
[ 5.831604] [drm] add ip block number 2 _navi10_ih_
[ 5.831604] [drm] add ip block number 3 _psp_
[ 5.831605] [drm] add ip block number 4 _smu_
[ 5.831605] [drm] add ip block number 5 _gfx_v10_0_
[ 5.831606] [drm] add ip block number 6 _sdma_v5_0_
[ 5.831606] [drm] add ip block number 7 _vcn_v2_0_
[ 5.831607] [drm] add ip block number 8 _jpeg_v2_0_
[ 5.950853] ATOM BIOS: 111
[ 5.950859] [drm] VCN decode is enabled in VM mode
[ 5.950860] [drm] VCN encode is enabled in VM mode
[ 5.950860] [drm] JPEG decode is enabled in VM mode
[ 5.950868] [drm] GPU posting now...
[ 5.950910] [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
[ 5.950917] amdgpu 0000:07:00.0: VRAM: 8176M 0x0000008000000000 - 0x00000081FEFFFFFF (8176M used)
[ 5.950918] amdgpu 0000:07:00.0: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
[ 5.950926] [drm] Detected VRAM RAM=8176M, BAR=256M
[ 5.950927] [drm] RAM width 256bits GDDR6
[ 5.950946] [drm] amdgpu: 8176M of VRAM memory ready
[ 5.950948] [drm] amdgpu: 8176M of GTT memory ready.
[ 5.950956] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 5.951060] [drm] PCIE GART of 512M enabled (table at 0x0000008000000000).
[ 5.951126] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 5.951127] [drm] Driver supports precise vblank timestamp query.
[ 5.952087] [drm] use_doorbell being set to: [true]
[ 5.952116] [drm] use_doorbell being set to: [true]
[ 5.952143] [drm] Found VCN firmware Version ENC: 1.7 DEC: 4 VEP: 0 Revision: 13
[ 5.952145] [drm] PSP loading VCN firmware
[ 6.599450] [drm] reserve 0x7300000 from 0x81f7c00000 for PSP TMR
[ 6.791487] amdgpu: [powerplay] use vbios provided pptable
[ 6.791566] amdgpu: [powerplay] smu driver if version = 0x00000033, smu fw if version = 0x00000035, smu fw version = 0x002a2f00 (42.47.0)
[ 6.791566] amdgpu: [powerplay] SMU driver if version not matched
[ 6.836142] amdgpu: [powerplay] SMU is initialized successfully!
[ 6.836828] [drm] kiq ring mec 2 pipe 1 q 0
[ 6.836963] [drm] ring test on 10 succeeded in 56 usecs
[ 6.837015] [drm] ring test on 10 succeeded in 11 usecs
[ 6.837048] [drm] gfx 0 ring me 0 pipe 0 q 0
[ 6.837085] [drm] ring test on 0 succeeded in 13 usecs
[ 6.837086] [drm] gfx 1 ring me 0 pipe 1 q 0
[ 6.837093] [drm] ring test on 1 succeeded in 1 usecs
[ 6.837093] [drm] compute ring 0 mec 1 pipe 0 q 0
[ 6.837103] [drm] ring test on 2 succeeded in 2 usecs
[ 6.837103] [drm] compute ring 1 mec 1 pipe 1 q 0
[ 6.837113] [drm] ring test on 3 succeeded in 2 usecs
[ 6.837114] [drm] compute ring 2 mec 1 pipe 2 q 0
[ 6.837124] [drm] ring test on 4 succeeded in 2 usecs
[ 6.837124] [drm] compute ring 3 mec 1 pipe 3 q 0
[ 6.837134] [drm] ring test on 5 succeeded in 2 usecs
[ 6.837135] [drm] compute ring 4 mec 1 pipe 0 q 1
[ 6.837144] [drm] ring test on 6 succeeded in 2 usecs
[ 6.837145] [drm] compute ring 5 mec 1 pipe 1 q 1
[ 6.837154] [drm] ring test on 7 succeeded in 2 usecs
[ 6.837155] [drm] compute ring 6 mec 1 pipe 2 q 1
[ 6.837165] [drm] ring test on 8 succeeded in 2 usecs
[ 6.837165] [drm] compute ring 7 mec 1 pipe 3 q 1
[ 6.837175] [drm] ring test on 9 succeeded in 2 usecs
[ 6.837308] [drm] ring test on 11 succeeded in 47 usecs
[ 6.837376] [drm] ring test on 12 succeeded in 47 usecs
[ 6.848290] [drm] VCN decode and encode initialized successfully(under DPG Mode).
[ 6.848575] [drm] JPEG decode initialized successfully.
[ 6.850097] kfd kfd: Allocated 3969056 bytes on gart
[ 6.850393] Virtual CRAT table created for GPU
[ 6.850394] Parsing CRAT table with 1 nodes
[ 6.850400] Creating topology SYSFS entries
[ 6.850566] Topology: Add dGPU node [0x731f:0x1002]
[ 6.850568] kfd kfd: added device 1002:731f
[ 6.850652] amdgpu 0000:07:00.0: ring 0(gfx_0.0.0) uses VM inv eng 4 on hub 0
[ 6.850653] amdgpu 0000:07:00.0: ring 1(gfx_0.1.0) uses VM inv eng 5 on hub 0
[ 6.850654] amdgpu 0000:07:00.0: ring 2(comp_1.0.0) uses VM inv eng 6 on hub 0
[ 6.850655] amdgpu 0000:07:00.0: ring 3(comp_1.1.0) uses VM inv eng 7 on hub 0
[ 6.850656] amdgpu 0000:07:00.0: ring 4(comp_1.2.0) uses VM inv eng 8 on hub 0
[ 6.850657] amdgpu 0000:07:00.0: ring 5(comp_1.3.0) uses VM inv eng 9 on hub 0
[ 6.850657] amdgpu 0000:07:00.0: ring 6(comp_1.0.1) uses VM inv eng 10 on hub 0
[ 6.850658] amdgpu 0000:07:00.0: ring 7(comp_1.1.1) uses VM inv eng 11 on hub 0
[ 6.850659] amdgpu 0000:07:00.0: ring 8(comp_1.2.1) uses VM inv eng 12 on hub 0
[ 6.850659] amdgpu 0000:07:00.0: ring 9(comp_1.3.1) uses VM inv eng 13 on hub 0
[ 6.850660] amdgpu 0000:07:00.0: ring 10(kiq_2.1.0) uses VM inv eng 14 on hub 0
[ 6.850661] amdgpu 0000:07:00.0: ring 11(sdma0) uses VM inv eng 15 on hub 0
[ 6.850662] amdgpu 0000:07:00.0: ring 12(sdma1) uses VM inv eng 16 on hub 0
[ 6.850663] amdgpu 0000:07:00.0: ring 13(vcn_dec) uses VM inv eng 4 on hub 1
[ 6.850663] amdgpu 0000:07:00.0: ring 14(vcn_enc0) uses VM inv eng 5 on hub 1
[ 6.850664] amdgpu 0000:07:00.0: ring 15(vcn_enc1) uses VM inv eng 6 on hub 1
[ 6.850665] amdgpu 0000:07:00.0: ring 16(jpeg_dec) uses VM inv eng 7 on hub 1
[ 6.850875] [drm] Initialized amdgpu 3.36.0 20150101 for 0000:07:00.0 on minor 1
[ 6.850917] amdgpu 0000:0a:00.0: enabling device (0000 -_ 0003)
[ 6.851124] [drm] initializing kernel modesetting (NAVI10 0x1002:0x7310 0x1002:0x7310 0xC0).
[ 6.851134] [drm] register mmio base: 0xB0200000
[ 6.851134] [drm] register mmio size: 524288
[ 6.851141] [drm] PCIE atomic ops is not supported
[ 6.872748] BUG: unable to handle kernel paging request at ffffbf3bffffffff
[ 6.872786] #PF error: [WRITE]
[ 6.872820] PGD 19a542067 P4D 19a542067 PUD 0
[ 6.872856] Oops: 0002 [#1] SMP NOPTI
[ 6.872891] CPU: 0 PID: 355 Comm: systemd-udevd Tainted: G OE 5.0.21-sm11 #1
[ 6.872928] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H81 Pro BTC R2.0, BIOS P1.20 07/22/2014
[ 6.873082] RIP: 0010:amdgpu_mm_wreg+0x116/0x170 [amdgpu]
[ 6.873117] Code: 7c 24 08 49 83 c4 18 44 89 e9 44 89 fa 8b 75 d4 e8 ff 10 22 f0 49 8b 04 24 48 85 c0 75 e0 e9 18 ff ff ff 48 03 83 b8 06 00 00 _44_ 89 28 e9 78 ff ff ff 44 89 e8 48 89 83 78 52 01 00 e9 09 ff ff
[ 6.873161] RSP: 0018:ffffbf3b80a478d0 EFLAGS: 00010086
[ 6.873196] RAX: ffffbf3bffffffff RBX: ffff988bd6820000 RCX: 0000000000000002
[ 6.873232] RDX: 00000000800006bc RSI: 0000000000000000 RDI: ffff988bd6820000
[ 6.873268] RBP: ffffbf3b80a47900 R08: 0000000000000000 R09: ffffe338065a0800
[ 6.873304] R10: 0000000000000002 R11: 0000000000000000 R12: 0000000000000000
[ 6.873340] R13: 00000000800006bc R14: 0000000000000000 R15: 0000000000000000
[ 6.873375] FS: 00007f49aa0368c0(0000) GS:ffff988bdaa00000(0000) knlGS:0000000000000000
[ 6.873412] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 6.873447] CR2: ffffbf3bffffffff CR3: 00000001939fc004 CR4: 00000000000606f0
[ 6.873483] Call Trace:
[ 6.873566] amdgpu_device_vram_access+0x8e/0xe0 [amdgpu]
[ 6.873657] amdgpu_discovery_init+0x65/0x180 [amdgpu]
[ 6.873739] amdgpu_device_init+0x8be/0x1cb0 [amdgpu]
[ 6.873783] ? kmalloc_order+0x18/0x40
[ 6.873823] ? kmalloc_order_trace+0x24/0xb0
[ 6.873905] amdgpu_driver_load_kms+0x5a/0x290 [amdgpu]
[ 6.873954] drm_dev_register+0x136/0x1d0 [drm]
[ 6.874036] amdgpu_pci_probe+0x11c/0x1e0 [amdgpu]
[ 6.874078] local_pci_probe+0x47/0xa0
[ 6.874119] pci_device_probe+0x142/0x1b0
[ 6.874160] really_probe+0xfe/0x3f0
[ 6.874201] driver_probe_device+0x11a/0x130
[ 6.874241] __driver_attach+0xe3/0x110
[ 6.874281] ? driver_probe_device+0x130/0x130
[ 6.874322] ? driver_probe_device+0x130/0x130
[ 6.874363] bus_for_each_dev+0x74/0xb0
[ 6.874404] ? kmem_cache_alloc_trace+0x1a6/0x1c0
[ 6.874445] driver_attach+0x1e/0x20
[ 6.874485] bus_add_driver+0x167/0x260
[ 6.874526] ? 0xffffffffc02f3000
[ 6.874566] driver_register+0x60/0x100
[ 6.874606] ? 0xffffffffc02f3000
[ 6.874646] __pci_register_driver+0x5a/0x60
[ 6.874727] amdgpu_init+0x9f/0xae [amdgpu]
[ 6.874768] do_one_initcall+0x4a/0x1c9
[ 6.874810] ? _cond_resched+0x19/0x40
[ 6.874849] ? kmem_cache_alloc_trace+0x42/0x1c0
[ 6.874891] do_init_module+0x5f/0x216
[ 6.874932] load_module+0x2450/0x2a00
[ 6.874973] __do_sys_finit_module+0xfc/0x120
[ 6.875014] ? __do_sys_finit_module+0xfc/0x120
[ 6.875055] __x64_sys_finit_module+0x1a/0x20
[ 6.875096] do_syscall_64+0x5a/0x120
[ 6.875137] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 6.875177] RIP: 0033:0x7f49a8eb3599
[ 6.875217] Code: 00 f3 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 _48_ 3d 01 f0 ff ff 73 01 c3 48 8b 0d cf 28 2c 00 f7 d8 64 89 01 48
[ 6.875281] RSP: 002b:00007ffd307bc048 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[ 6.875331] RAX: ffffffffffffffda RBX: 000055d3a94d9290 RCX: 00007f49a8eb3599
[ 6.875373] RDX: 0000000000000000 RSI: 000055d3a94f51a0 RDI: 0000000000000019
[ 6.875415] RBP: 000055d3a94f51a0 R08: 0000000000000000 R09: 000000000000003f
[ 6.875457] R10: 0000000000000019 R11: 0000000000000246 R12: 0000000000000000
[ 6.875499] R13: 000055d3a94d9190 R14: 0000000000020000 R15: 0000000000000000
[ 6.875541] Modules linked in: binfmt_misc amdgpu(OE+) nls_iso8859_1 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm amd_iommu_v2 amdttm(OE) amd_sched(OE) amdkcl(OE) drm_kms_helper irqbypass drm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i2c_algo_bit fb_sys_fops syscopyarea cryptd sysfillrect sysimgblt intel_cstate intel_rapl_perf mac_hid lpc_ich mei_me mei autofs4 uas usb_storage r8169 realtek video
[ 6.875650] CR2: ffffbf3bffffffff
[ 6.875690] ---[ end trace e875feff4756b640 ]---
[ 6.875772] RIP: 0010:amdgpu_mm_wreg+0x116/0x170 [amdgpu]
[ 6.875813] Code: 7c 24 08 49 83 c4 18 44 89 e9 44 89 fa 8b 75 d4 e8 ff 10 22 f0 49 8b 04 24 48 85 c0 75 e0 e9 18 ff ff ff 48 03 83 b8 06 00 00 _44_ 89 28 e9 78 ff ff ff 44 89 e8 48 89 83 78 52 01 00 e9 09 ff ff
[ 6.875876] RSP: 0018:ffffbf3b80a478d0 EFLAGS: 00010086
[ 6.875917] RAX: ffffbf3bffffffff RBX: ffff988bd6820000 RCX: 0000000000000002
[ 6.875959] RDX: 00000000800006bc RSI: 0000000000000000 RDI: ffff988bd6820000
[ 6.876001] RBP: ffffbf3b80a47900 R08: 0000000000000000 R09: ffffe338065a0800
[ 6.876043] R10: 0000000000000002 R11: 0000000000000000 R12: 0000000000000000
[ 6.876085] R13: 00000000800006bc R14: 0000000000000000 R15: 0000000000000000
[ 6.876128] FS: 00007f49aa0368c0(0000) GS:ffff988bdaa00000(0000) knlGS:0000000000000000
[ 6.876178] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 6.876218] CR2: ffffbf3bffffffff CR3: 00000001939fc004 CR4: 00000000000606f0
[ 7.831574] [drm] ib test on ring 0 succeeded
[ 7.831708] [drm] ib test on ring 1 succeeded
[ 7.831870] [drm] ib test on ring 2 succeeded
[ 7.832006] [drm] ib test on ring 3 succeeded
[ 7.832170] [drm] ib test on ring 4 succeeded
[ 7.832334] [drm] ib test on ring 5 succeeded
[ 7.832435] [drm] ib test on ring 6 succeeded
[ 7.832514] [drm] ib test on ring 7 succeeded
[ 7.832638] [drm] ib test on ring 8 succeeded
[ 7.832761] [drm] ib test on ring 9 succeeded
[ 7.832846] [drm] ib test on ring 10 succeeded
[ 7.832926] [drm] ib test on ring 11 succeeded
[ 7.833006] [drm] ib test on ring 12 succeeded
[ 8.017202] r8169 0000:11:00.0 eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 8.017259] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 8.856037] [drm] ib test on ring 0 succeeded
[ 8.856174] [drm] ib test on ring 1 succeeded
[ 8.856377] [drm] ib test on ring 2 succeeded
[ 8.856522] [drm] ib test on ring 3 succeeded
[ 8.856765] [drm] ib test on ring 4 succeeded
[ 8.856965] [drm] ib test on ring 5 succeeded
[ 8.857098] [drm] ib test on ring 6 succeeded
[ 8.857205] [drm] ib test on ring 7 succeeded
[ 8.857358] [drm] ib test on ring 8 succeeded
[ 8.857512] [drm] ib test on ring 9 succeeded
[ 8.857625] [drm] ib test on ring 10 succeeded
[ 8.857706] [drm] ib test on ring 11 succeeded
[ 8.857845] [drm] ib test on ring 12 succeeded
[ 24.773734] random: crng init done
[ 24.773778] random: 7 urandom warning(s) missed due to ratelimiting
I don't know what 99% of that is, but this stands out.. [ 6.875772] RIP: 0010:amdgpu_mm_wreg+0x116/0x170 [amdgpu]
RIP? lol
Cheers
October 09, 2020, 04:28:22 AM
Is it possible to change the VRAM timings of stock 580's with SMOS?
No, this operation needs to be done in bios file and flashed to GPU. On our discord guys can help You with that. Jump to: