I currently have it running 12 gpus. I didn't need to change anything in the bios, however sometimes when it crashes and i do a power cycle, it will not boot up.
I'm able to get it to boot by turning off half the rig to get into bios, and disable csm compatability (uefi only, no legacy). For some reason that setting gets toggled sometimes when the rig crashes.
HTH!
What GPUs did you has? You are a lucky man!  10x rx5700 and 2x radeon vii. I have the same cpu and ram amount as you. also try different pcie speeds, mine are set to 2x |
|
|
|
|
I currently have it running 12 gpus. I didn't need to change anything in the bios, however sometimes when it crashes and i do a power cycle, it will not boot up.
I'm able to get it to boot by turning off half the rig to get into bios, and disable csm compatability (uefi only, no legacy). For some reason that setting gets toggled sometimes when the rig crashes.
HTH!
|
|
|
|
|
I'm unable to generate a log file using --log 1 --logfile log.txt
Am i doing something wrong?
|
|
|
|
So ... very busily spinning last days to make lolMiner 1.03reality as quickly as possible. You can download it here. This time on board (change-log): - New Beam Hash III 4G solver, replaces the 6G solver on AMD Vega GPUs and earlier (+5 - 8% performance on RX 580 & Vega GPUs)
- New Beam Hash III 6G solver on ROCm and for AMD Navi GPUs (+8-10% performance on Navi cards)
- Fixed a bug with the API (--apiport) crashing the miner in Windows on startup
So overall expect the miner to be more performant now on Beam Hash III - and the crashed the miner had last versions on startup when the API was active should now be history. Happy mining! all my rigs now work! no more crashes like in my previous post. Awesome! |
|
|
|
|
On my other 12gpu rig, i get the same problem. I can get it to run by splitting it into 6 devices each instance. Not ideal but at least it works
|
|
|
|
Wired ... 20.0.2 should be way new enough.
What is strange is in particular that it seems to be fine with the first VII, but somehow does not like the 2nd.
What happens when you start on device 4 only and skip 11 (and well other way around: when you start on 11 only) ...
Wonder whats going on there...
It works fine with only device 4. It fails if i only try to run it with device 11. |
|
|
|
Thanks! Now it works on my pc with one vega64, but on some rigs i'm getting this error: Initialize diagnostics (20)
Starting Diagnostics (30s). Awesome Miner Remote Agent version: 7.8.1
OS: Microsoft Windows 10 Pro 64-bit
AMD driver version: 20.2.2
AMD OpenCL Platform ID: 0
Microsoft VC++ 2013 runtime installed: No
Microsoft VC++ 2015 runtime installed: Yes
Microsoft VC++ 2017 runtime installed: Yes
Microsoft VC++ 2019 runtime installed: No
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: LolMiner, Auto Download: True, EnginePath: C:\Users\adrianh\AppData\Local\AwesomeMiner\lolminer_v081_win64_1\0.8.1\lolMiner.exe, Subtype: Disabled, CustomExecutable:
Properties: (WindowMode: ConsoleFormat, EngineType: LolMiner, IsProfitMiner: True)
====================================================================================================
C:\Users\adria\AppData\Roaming\AwesomeMinerService\lolminer_v1.02_win64_1\1.02\lolMiner.exe --tls 0 --devices 4,11 --pool beamv3.usa.nicehash.com:3387 --user xx --pass x --coin BEAM --apiport 4028
Configured command line:
--tls 0
====================================================================================================
Mining Engine Process started, PID: 5948
> +---------------------------------------------------------+
> | _ _ __ __ _ _ ___ ____ |
> | | | ___ | | \/ (_)_ __ ___ _ __ / | / _ \___ \ |
> | | |/ _ \| | |\/| | | '_ \ / _ \ '__| | || | | |__) | |
> | | | (_) | | | | | | | | | __/ | | || |_| / __/ |
> | |_|\___/|_|_| |_|_|_| |_|\___|_| |_(_)___/_____| |
> | |
> | This software is for mining |
> | Equihash 144/5, 192/7, 210/9 |
> | BeamHash I (EquihashR 150/5/0) |
> | BeamHash II (EquihashR 150/5/3) |
> | BeamHash III |
> | ZelHash (EquihashR 125/4/0) |
> | CuckarooD 29 |
> | CuckarooM 29 |
> | Cuckaroo 30 CTX |
> | Cuckatoo 31/32 |
> | |
> | |
> | Made by Lolliedieb, July 2020 |
> +---------------------------------------------------------+
>
> Setup Miner...
> Size:
> Device 0:
> Name: AMD Radeon RX 5700 XT
> Address: 3:0
> Vendor: Advanced Micro Devices (AMD)
> Memory: 8176 MByte (8112 MByte free)
> Active: false (not selected)
> Device 1:
> Name: AMD Radeon RX 5700 XT
> Address: 6:0
> Vendor: Advanced Micro Devices (AMD)
> Memory: 8176 MByte (8112 MByte free)
> Active: false (not selected)
> Device 2:
> Name: AMD Radeon RX 5700 XT
> Address: 9:0
> Vendor: Advanced Micro Devices (AMD)
> Memory: 8176 MByte (8112 MByte free)
> Active: false (not selected)
> Device 3:
> Name: AMD Radeon RX 5700 XT
> Address: 12:0
> Vendor: Advanced Micro Devices (AMD)
> Memory: 8176 MByte (8112 MByte free)
> Active: false (not selected)
> Device 4:
> Name: AMD Radeon VII
> Address: 15:0
> Vendor: Advanced Micro Devices (AMD)
> Memory: 16192 MByte (16128 MByte free)
> Active: true (Selected Algorithm: BeamHash III 6G)
> Device 5:
> Name: AMD Radeon RX 5700 XT
> Address: 18:0
> Vendor: Advanced Micro Devices (AMD)
> Memory: 8176 MByte (8112 MByte free)
> Active: false (not selected)
> Device 6:
> Name: AMD Radeon RX 5700 XT
> Address: 23:0
> Vendor: Advanced Micro Devices (AMD)
> Memory: 8176 MByte (8112 MByte free)
> Active: false (not selected)
> Device 7:
> Name: AMD Radeon RX 5700 XT
> Address: 26:0
> Vendor: Advanced Micro Devices (AMD)
> Memory: 8176 MByte (8112 MByte free)
> Active: false (not selected)
> Device 8:
> Name: AMD Radeon RX 5700 XT
> Address: 30:0
> Vendor: Advanced Micro Devices (AMD)
> Memory: 8176 MByte (8112 MByte free)
> Active: false (not selected)
> Device 9:
> Name: AMD Radeon RX 5700 XT
> Address: 33:0
> Vendor: Advanced Micro Devices (AMD)
> Memory: 8176 MByte (8112 MByte free)
> Active: false (not selected)
> Device 10:
> Name: AMD Radeon RX 5700 XT
> Address: 36:0
> Vendor: Advanced Micro Devices (AMD)
> Memory: 8176 MByte (8112 MByte free)
> Active: false (not selected)
> Device 11:
> Name: AMD Radeon VII
> Address: 39:0
> Vendor: Advanced Micro Devices (AMD)
> Memory: 16192 MByte (16128 MByte free)
> 0x00007FF7236C7543 (0x00000054CE1CFB58 0x0000020DF2F45DA0 0x0000000000000004 0x0000020DF79EA450)
> 0x00007FF72367A2FF (0x00000054CE1CF9A0 0x00007FFFB2B1B997 0x0000020D00258598 0x01D64FB3B5445111)
> 0x00007FF72367B458 (0x0000020DF2E7F7D0 0x00000054CE7F7060 0x00000054CE7F71D0 0x0000000000000000)
> 0x00007FF723676E79 (0x0000020DF2E7F7D0 0x0000020DF2E7F7D0 0x0000020DF2E7F7D0 0x0000000000000000)
> 0x00007FF723678098 (0x0000000000000000 0x0000000000000000 0x00000054CE7F71C0 0x0000020DF2F7B700)
> 0x00007FF723683108 (0x00000054CE1CF9A0 0x0000000000000000 0x0000000000000000 0x00000054CE1CF9A0)
> 0x00007FF72368723A (0x0000000400000004 0x0000020DF2FB63F0 0x00000054CE1CE6F8 0x0000000000000000)
> 0x00007FF723672E2F (0x0000020DF2F77550 0x0000000000000000 0x0000000000000005 0x0000000000000005)
> 0x00007FF723672A39 (0x0000020DF2F77550 0x0000000000000000 0x0000000000000000 0x0000000000000000)
> 0x00007FF723837AE4 (0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000)
> 0x00007FFFB16A7BD4 (0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000), BaseThreadInitThunk() + 0x14 bytes(s)
> 0x00007FFFB2B4CE51 (0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000), RtlUserThreadStart() + 0x21 bytes(s)
====================================================================================================
Unexpected exit of mining software. Possible cause: Incorrect configuration or crashing software
Diagnostics completed
all my rigs are on 20.2.2 driver. Should i update the drivers? edit: also to add, i'm getting this error on my 11x vega + 1x rx5700 rig, but it works just fine on my gaming pc with 1x vega |
|
|
|
Setup Miner...
Size:
Device 0:
Name: AMD Radeon RX 5700 XT
Address: 47:0
Vendor: Advanced Micro Devices (AMD)
Memory: 8176 MByte (8112 MByte free)
Active: true (Selected Algorithm: BeamHash III 6G)
Connecting to pool...
Connected to beamv3.usa.nicehash.com:3387 (TLS enabled)
Error: Handshake failed with message stream truncated
Lost connection to stratum server beamv3.usa.nicehash.com:3387 or server not reachable.
Trying to connect in 3 seconds I'm getting connection errors to nicehash. Am I missing something? TIA |
|
|
|
|
Hi Patrike,
Is there a way to give more details for "dead device detection" for gpu mining rigs? I'd like to know which gpu died. Thanks.
|
|
|
|
|
Hi,
Grin 31 is working on my rx vega cards, however it doesn't seem to be working on my gtx 1080 cards. On the rx vega it uses the 8gb kernel but on the 1080 it uses the 4gb kernel. It shows hashrate of 0 and continues to run without errors. Is this normal?
edit: should have mentioned i'm running windows 10
|
|
|
|
hi,
im not able to get it to work with my vega64 or 8x vega56.
on both rigs i get the same error message “Failed to initialize device number 0.”
ive tried using -d 1, but then the error becomes device 1 is out of range.
any ideas on what to try next?
edit forgot to mention im on win 10 and 18.6.1 drivers
Have you tried this ? --platform=1 hi, yes, i have tried that. Did not work either. turn off hbcc... it's probably recognizing it has gfx901. Just checked that, hbcc is turned off. SRBminer detects it as gfx900. same problem here Can you post the output from the command “clinfo”? You can run it from the command prompt, it’ll be a long text dump. Also, include your command line and the output from the miner when you run it. Think we’ll be able to nail down this one. Everything points to a platform with a single device being tried, doesn’t match your rig description. And, we desperately need to add automatic platform id detection... Platform Name: AMD Accelerated Parallel Processing
Number of devices: 2
Device Type: CL_DEVICE_TYPE_GPU
Vendor ID: 1002h
Board name: Radeon RX Vega
Device Topology: PCI[ B#3, D#0, F#0 ]
Max compute units: 64
Max work items dimensions: 3
Max work items[0]: 1024
Max work items[1]: 1024
Max work items[2]: 1024
Max work group size: 256
Preferred vector width char: 4
Preferred vector width short: 2
Preferred vector width int: 1
Preferred vector width long: 1
Preferred vector width float: 1
Preferred vector width double: 1
Native vector width char: 4
Native vector width short: 2
Native vector width int: 1
Native vector width long: 1
Native vector width float: 1
Native vector width double: 1
Max clock frequency: 1750Mhz
Address bits: 64
Max memory allocation: 4244635648
Image support: Yes
Max number of images read arguments: 128
Max number of images write arguments: 64
Max image 2D width: 16384
Max image 2D height: 16384
Max image 3D width: 2048
Max image 3D height: 2048
Max image 3D depth: 2048
Max samplers within kernel: 16
Max size of kernel argument: 1024
Alignment (bits) of base address: 2048
Minimum alignment (bytes) for any datatype: 128
Single precision floating point capability
Denorms: No
Quiet NaNs: Yes
Round to nearest even: Yes
Round to zero: Yes
Round to +ve and infinity: Yes
IEEE754-2008 fused multiply-add: Yes
Cache type: Read/Write
Cache line size: 64
Cache size: 16384
Global memory size: 8573157376
Constant buffer size: 4244635648
Max number of constant args: 8
Local memory type: Scratchpad
Local memory size: 32768
Max pipe arguments: 16
Max pipe active reservations: 16
Max pipe packet size: 4244635648
Max global variable size: 3820172032
Max global variable preferred total size: 8573157376
Max read/write image args: 64
Max on device events: 1024
Queue on device max size: 8388608
Max on device queues: 1
Queue on device preferred size: 262144
SVM capabilities:
Coarse grain buffer: Yes
Fine grain buffer: Yes
Fine grain system: No
Atomics: No
Preferred platform atomic alignment: 0
Preferred global atomic alignment: 0
Preferred local atomic alignment: 0
Kernel Preferred work group size multiple: 64
Error correction support: 0
Unified memory for Host and Device: 0
Profiling timer resolution: 1
Device endianess: Little
Available: Yes
Compiler available: Yes
Execution capabilities:
Execute OpenCL kernels: Yes
Execute native function: No
Queue on Host properties:
Out-of-Order: No
Profiling : Yes
Queue on Device properties:
Out-of-Order: Yes
Profiling : Yes
Platform ID: 00007FFB858EFFD0
Name: gfx900
Vendor: Advanced Micro Devices, Inc.
Device OpenCL C version: OpenCL C 2.0
Driver version: 2580.6 (PAL,HSAIL)
Profile: FULL_PROFILE
Version: OpenCL 2.0 AMD-APP (2580.6)
Extensions: cl_khr_fp64 cl_amd_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_fp16 cl_khr_gl_sharing cl_khr_gl_depth_images cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt cl_khr_d3d10_sharing cl_khr_d3d11_sharing cl_khr_dx9_media_sharing cl_khr_image2d_from_buffer cl_khr_spir cl_khr_subgroups cl_khr_gl_event cl_khr_depth_images cl_khr_mipmap_image cl_khr_mipmap_image_writes cl_amd_liquid_flash
My command line is teamredminer.exe -a cnv8 -o stratum+tcp://cryptonightv8.eu.nicehash.com:3367 -u xxx -p x --api_listen=0.0.0.0:4028 and the output is Mining Engine Process started, PID: 18540 > Team Red Miner version 0.3.4 > [2018-10-31 01:33:17] Failed to initialize device number 0. Hope it helps. does your system have integrated graphics? if so, you might need --platform=0 or --platform=1, i see that you already tried platform=1, so try the other. Yes it has integrated graphics and an nvidia card. Tried platforms 0 and 2 but it didn't work. 0.35 works though! thanks. |
|
|
|
hi,
im not able to get it to work with my vega64 or 8x vega56.
on both rigs i get the same error message “Failed to initialize device number 0.”
ive tried using -d 1, but then the error becomes device 1 is out of range.
any ideas on what to try next?
edit forgot to mention im on win 10 and 18.6.1 drivers
Have you tried this ? --platform=1 hi, yes, i have tried that. Did not work either. turn off hbcc... it's probably recognizing it has gfx901. Just checked that, hbcc is turned off. SRBminer detects it as gfx900. same problem here Can you post the output from the command “clinfo”? You can run it from the command prompt, it’ll be a long text dump. Also, include your command line and the output from the miner when you run it. Think we’ll be able to nail down this one. Everything points to a platform with a single device being tried, doesn’t match your rig description. And, we desperately need to add automatic platform id detection... Platform Name: AMD Accelerated Parallel Processing
Number of devices: 2
Device Type: CL_DEVICE_TYPE_GPU
Vendor ID: 1002h
Board name: Radeon RX Vega
Device Topology: PCI[ B#3, D#0, F#0 ]
Max compute units: 64
Max work items dimensions: 3
Max work items[0]: 1024
Max work items[1]: 1024
Max work items[2]: 1024
Max work group size: 256
Preferred vector width char: 4
Preferred vector width short: 2
Preferred vector width int: 1
Preferred vector width long: 1
Preferred vector width float: 1
Preferred vector width double: 1
Native vector width char: 4
Native vector width short: 2
Native vector width int: 1
Native vector width long: 1
Native vector width float: 1
Native vector width double: 1
Max clock frequency: 1750Mhz
Address bits: 64
Max memory allocation: 4244635648
Image support: Yes
Max number of images read arguments: 128
Max number of images write arguments: 64
Max image 2D width: 16384
Max image 2D height: 16384
Max image 3D width: 2048
Max image 3D height: 2048
Max image 3D depth: 2048
Max samplers within kernel: 16
Max size of kernel argument: 1024
Alignment (bits) of base address: 2048
Minimum alignment (bytes) for any datatype: 128
Single precision floating point capability
Denorms: No
Quiet NaNs: Yes
Round to nearest even: Yes
Round to zero: Yes
Round to +ve and infinity: Yes
IEEE754-2008 fused multiply-add: Yes
Cache type: Read/Write
Cache line size: 64
Cache size: 16384
Global memory size: 8573157376
Constant buffer size: 4244635648
Max number of constant args: 8
Local memory type: Scratchpad
Local memory size: 32768
Max pipe arguments: 16
Max pipe active reservations: 16
Max pipe packet size: 4244635648
Max global variable size: 3820172032
Max global variable preferred total size: 8573157376
Max read/write image args: 64
Max on device events: 1024
Queue on device max size: 8388608
Max on device queues: 1
Queue on device preferred size: 262144
SVM capabilities:
Coarse grain buffer: Yes
Fine grain buffer: Yes
Fine grain system: No
Atomics: No
Preferred platform atomic alignment: 0
Preferred global atomic alignment: 0
Preferred local atomic alignment: 0
Kernel Preferred work group size multiple: 64
Error correction support: 0
Unified memory for Host and Device: 0
Profiling timer resolution: 1
Device endianess: Little
Available: Yes
Compiler available: Yes
Execution capabilities:
Execute OpenCL kernels: Yes
Execute native function: No
Queue on Host properties:
Out-of-Order: No
Profiling : Yes
Queue on Device properties:
Out-of-Order: Yes
Profiling : Yes
Platform ID: 00007FFB858EFFD0
Name: gfx900
Vendor: Advanced Micro Devices, Inc.
Device OpenCL C version: OpenCL C 2.0
Driver version: 2580.6 (PAL,HSAIL)
Profile: FULL_PROFILE
Version: OpenCL 2.0 AMD-APP (2580.6)
Extensions: cl_khr_fp64 cl_amd_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_fp16 cl_khr_gl_sharing cl_khr_gl_depth_images cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt cl_khr_d3d10_sharing cl_khr_d3d11_sharing cl_khr_dx9_media_sharing cl_khr_image2d_from_buffer cl_khr_spir cl_khr_subgroups cl_khr_gl_event cl_khr_depth_images cl_khr_mipmap_image cl_khr_mipmap_image_writes cl_amd_liquid_flash
My command line is teamredminer.exe -a cnv8 -o stratum+tcp://cryptonightv8.eu.nicehash.com:3367 -u xxx -p x --api_listen=0.0.0.0:4028 and the output is Mining Engine Process started, PID: 18540 > Team Red Miner version 0.3.4 > [2018-10-31 01:33:17] Failed to initialize device number 0. Hope it helps. |
|
|
|
hi,
im not able to get it to work with my vega64 or 8x vega56.
on both rigs i get the same error message “Failed to initialize device number 0.”
ive tried using -d 1, but then the error becomes device 1 is out of range.
any ideas on what to try next?
edit forgot to mention im on win 10 and 18.6.1 drivers
Have you tried this ? --platform=1 hi, yes, i have tried that. Did not work either. turn off hbcc... it's probably recognizing it has gfx901. Just checked that, hbcc is turned off. SRBminer detects it as gfx900. |
|
|
|
hi,
im not able to get it to work with my vega64 or 8x vega56.
on both rigs i get the same error message “Failed to initialize device number 0.”
ive tried using -d 1, but then the error becomes device 1 is out of range.
any ideas on what to try next?
edit forgot to mention im on win 10 and 18.6.1 drivers
Have you tried this ? --platform=1 hi, yes, i have tried that. Did not work either. |
|
|
|
|
hi,
im not able to get it to work with my vega64 or 8x vega56.
on both rigs i get the same error message “Failed to initialize device number 0.”
ive tried using -d 1, but then the error becomes device 1 is out of range.
any ideas on what to try next?
edit forgot to mention im on win 10 and 18.6.1 drivers
|
|
|
|
|
Is there a problem with payouts or a delay? I havent had one in 2 days.
|
|
|
|
(UK) £0.09/$0.12  who is your provider if you don't mind me asking? I'm with outfoxthemarket and am paying 0.11p |
|
|
|
it looks it supports the Ryzen G apu, i need support of the A-series APU (the HD7000D), which are no longer supported by amd opencl since 2015  to answer above about 4G memory : not the full 4G can be allocated, the mining program and the drivers take some room. GPUZ gives info about max opencl allocation. on 4G with a screen (or dummy plug) on, it may be limited to ~3.5G don't forget to setup the environment variable GPU_MAX... geck: i didn't even know Awesome supports jce. look at your pool, you'll see i don' cheat 35% of your shares… i don't know what Awesome get its numbers from. the Effective hashrate is avaible in the native json output. I'm not saying you cheat the shares. I'm thinking there maybe something wrong with the hash rate reporting via api to awesomeminer? awesomeminer picks up the right hashrate with 0.31f but something must have changed with 0.32a. It isn't a big deal, i only need the hash rate reading as i set up rules to restart the miner |
|
|
|
|
wanted to add, awesomeminer is reporting a much lower hashrate with 0.32a compared to 0.31f. the miner shows 15k but awesomeminer reports around 11k.
|
|
|
|
|
Just tried out 32a with the auto function and im getting CL_MEM_ALLOCATION_ERROR on one thread. The thread number that fails is random. Reducing the multihash value to 1840 solves it but it seems like there is a lot of speed left on the table
I have tried reducing the memory clocks all the way down but it still fails. This is on an 8x vega56 rig.
|
|
|
|
|
Show Posts
