is there any issue using AMD driver 22.19.659.0? I have Vega 64's and am completely new to SRBminer.
You should try It's working with the blockchain drivers.
|
|
|
hi i m trying to set up a multi-algo switching (Monero Ocean+ Miner2gether (XAO) i set these 2 pools in pools-algo-switching with cryptonight_type option by pool when i run miner it restart switching in loop cryptonightv7-->another MO currency-->cryptonight_V7-->another currency again and again with no mining help plz *SRBMiner 1.6.8
maybe a bug in 1.6.8, i will check it out
|
|
|
Loving this miner!
Just a quick query, is there any built in hash rate monitoring? Did I miss it?
Sometimes Vega's are dropping hash and a hash watch dog where you can set a threshold before the miner restarts would be awesome!
I guess you haven't check the first page, or the readme.txt. config.txt "min_rig_speed" : number - in H/S, it defines the minimum rig hashing speed we want to maintain. If 5 minute average hashing speed is less than this, miner restarts. "min_rig_speed_duration" : number - in seconds (minimum is 30 sec), defines the time period for average hashing speed calculation, used with 'min_rig_speed' parameter
|
|
|
Hi
Excuse me because I am very new, I am trying to configure the intensities of the gpus manually.
If I use this configuration it works fine
{ "cryptonight_type" : "bittubev2", "intensity" : 0, "double_threads" : true }
I'm trying to use this configuration but I do not know if it's okay
{ "cryptonight_type" : "bittubev2", "gpu_conf" : [ { "id" : 0, "intensity" : 54, "worksize" : 8, "threads" : 2}, { "id" : 1, "intensity" : 54, "worksize" : 8, "threads" : 2}, { "id" : 2, "intensity" : 54, "worksize" : 8, "threads" : 2}, { "id" : 3, "intensity" : 54, "worksize" : 8, "threads" : 2} ] }
When the active rig is blocked, so I continue to use the initial configuration for now.
My gpus are rx 580/570
Is the configuration I try in manual wrong?
This should work: { "cryptonight_type" : "bittubev2", "intensity" : 0, "double_threads" : true, "gpu_conf" : [ { "id" : 0, "intensity" : 54, "worksize" : 8, "threads" : 2 }, { "id" : 1, "intensity" : 54, "worksize" : 8, "threads" : 2 }, { "id" : 2, "intensity" : 54, "worksize" : 8, "threads" : 2 }, { "id" : 3, "intensity" : 54, "worksize" : 8, "threads" : 2 } ] }
When the active rig is blocked This i don't understand
|
|
|
Hi everyone,
I`m trying to run the miner on a 12card RX580 rig. I`m receiving these errors. Please could you help.
"Error CL_MEM_OBJECT_ALLOCATION_FAILURE when calling clEnqeueNDRangeKernel"
I tried both V1.6.7 and V1.6.8 and drivers 18.6.1
I just see red everywhere.
Thanks
You need to increase virtual memory to a mininum of 96gb
|
|
|
1.6.8 hashrates is lower for me cards (both sapphire nitro+ 4gb) / hashrate 1.6.7 / hashrate 1.6.8 rx470 / 740 / 720 rx570 / 760 / 740 algo: bittubev2 i switch back to 1.6.7 I tried the new 1.6.8 version, the result was worse than previous 1.6.8. rx470: 706H/s rx570: 736H/s I= 0, T=2, WS=8 I don't know what is happening there but i ran 2 tests on TUBE: Intensity:28 Worksize:8 Threads:2 Rx470 4g Sapphire Nitro [1050/1950] 1.6.7 : 588 HS 1.6.8 : 613 HS This is the latest 1.6.8 i uploaded today.
|
|
|
good job everything is working thank you very much
[2018-10-12 10:43:58] CPU AES-NI: FALSE [2018-10-12 10:43:58] GPU0: AMD Radeon (TM) R7 370 Series [pitcairn] [2048 MB][Intensity 27.5][W: 8][T: 2][K: 1][BUS: 7] [2018-10-12 10:43:58] GPU1: AMD Radeon (TM) R7 370 Series [pitcairn] [2048 MB][Intensity 27.5][W: 8][T: 2][K: 1][BUS: 10] [2018-10-12 10:43:58] GPU2: Radeon(TM) RX 460 Graphics [baffin] [2048 MB][Intensity 25.0][W: 8][T: 2][K: 1][BUS: 3] [2018-10-12 10:43:58] GPU3: AMD Radeon R7 200 Series [pitcairn] [2048 MB][Intensity 27.5][W: 8][T: 2][K: 1][BUS: 9] [2018-10-12 10:43:58] GPU4: Radeon(TM) RX 460 Graphics [baffin] [2048 MB][Intensity 12.0][W: 8][T: 2][K: 1][BUS: 1] [2018-10-12 10:43:58] GPU5: AMD Radeon R9 200 Series [tonga] [2048 MB][Intensity 28.0][W: 4][T: 2][K: 1][BUS: 8]
now this is a mixed rig
|
|
|
PITCAIRN guys, re-download 1.6.8, compilation fixed
|
|
|
Doktore, txs for constant development Just quick test new option: "bralock": 1-256, parameter to tune, it *may* add some extra hash, it can differ between algos On V7 algo tested with RX570 4GB, Vega 64, Vega 56. Tried several parameter like: 1, 10, 33, 100, 150, 200, 256. Don't see any benefits for V7 algo so far, but maybe i must wait longer before switching to another parameter in config file... haha, better try 1,4,8,16,32,64 etc
|
|
|
FIXED 1.6.8 IS UP AGAIN ON MEGAHopefully this is the last fix of 1.6.8, and it should compile now on pitcairns, hawaiis etc.. I also rewrote the resources freeing code on miner shutdown/restart, so it may take now a little longer to close the miner, but this should solve the problems with driver sometimes crashing on miner close. If you want to use the old, faster shutdown method, you can use the --forcedshutdown parameter , added in start.bat Also i changed my mind and no more normal and maxi versions, only maxi. Because no one notices the big message on the first page that says which drivers should be used Please report if hawaiis and pitcairns compile now. Thanks Hi dok, I still have the same issue. GPU hash rate drop to zero and miner crashed. V1.6.7 is stable, it does not have such issue. [2018-10-12 00:08:48] watchdog: GPU1 [BUS: 1] hashing speed is 0 H/S [2018-10-12 00:08:48] watchdog: GPU2 [BUS: 4] hashing speed is 0 H/S [2018-10-12 00:08:48] watchdog: GPU3 [BUS: 2] hashing speed is 0 H/S [2018-10-12 00:08:48] watchdog: GPU4 [BUS: 7] hashing speed is 0 H/S [2018-10-12 00:08:48] watchdog: GPU5 [BUS: 8] hashing speed is 0 H/S [2018-10-12 00:08:48] watchdog: GPU6 [BUS: 3] hashing speed is 0 H/S [2018-10-12 00:09:52] watchdog: GPU crash detected, miner will try to restart [2018-10-12 00:09:52] Restarting miner process [2018-10-12 00:09:53] Miner version: 1.6.8 [2018-10-12 00:09:53] Windows version: 10.0 build 16299 [2018-10-12 00:09:53] Video driver version: 24.20.11021.1000 [2018-10-12 00:11:36] AMD Platform ID: 1 [ You should lower intensity until your driver won't crash, so hashrate won't fall to 0 and miner won't restart. It can happen that after driver crash opencl can't be initialised. Try set that startup script and set overdriventtol to reset gpu's every time before run, maybe that will help.
|
|
|
I have problem with start srbminer 1.6.8 on rig with 4 r7 260x 1gb... I have not change any parameters... Just start AS IS... Does srbminer 1.6.8 supports old cards like 7790 or r7 260x?
AMD Radeon R7 260X is Bonaire so it should work. What error do you get, paste it here, or create a screenshot.
|
|
|
possibly heavy algos impacted. Wait for next version, until then use 1.6.7
but rx560\4gb work better on 1.6.8 variable rate on 1.6.7 and stable high rate on 1.6.8 use 1.6.8 on cn-heavy for all rx560\4gb ( 3 rig 12 gpu each) yes, i am trying to tune every card separately, so too much cards and too much settings, i probably messed something for the 4xx 5xx series for heavy algos.
|
|
|
1.6.8 hashrates is lower for me cards (both sapphire nitro+ 4gb) / hashrate 1.6.7 / hashrate 1.6.8 rx470 / 740 / 720 rx570 / 760 / 740 algo: bittubev2 i switch back to 1.6.7 Going to investigate same troube on cn-heavy. need to test new upload 1.6.8 or wait new version? possibly heavy algos impacted. Wait for next version, until then use 1.6.7
|
|
|
1.6.8 hashrates is lower for me cards (both sapphire nitro+ 4gb) / hashrate 1.6.7 / hashrate 1.6.8 rx470 / 740 / 720 rx570 / 760 / 740 algo: bittubev2 i switch back to 1.6.7 Going to investigate
|
|
|
Dear All,
Anyone know the detailed info about startup_script? How to use it?
Thanks
So, how to use it? Create a .bat file where you set for example overdriventool to reset your cards & apply profiles to them. Let's call that file overclock.bat Then in your start.bat add the --startupscript parameter to the end of line for example : SRBMiner-CN.exe --config Config\config-normalv7.txt --pools pools.txt --logfile %LOGTIME% --startupscript overclock.bat
Now the overclock.bat will be run before the miner starts, so this way you can ensure that on every miner start you apply the overclocking settings. If you meant the startup_script in algos.txt file, the principle is same, you just enter the overclock.bat filename in the algos.txt file as a value for the startup_script parameter.
|
|
|
FIXED 1.6.8 IS UP AGAIN ON MEGAHopefully this is the last fix of 1.6.8, and it should compile now on pitcairns, hawaiis etc.. I also rewrote the resources freeing code on miner shutdown/restart, so it may take now a little longer to close the miner, but this should solve the problems with driver sometimes crashing on miner close. If you want to use the old, faster shutdown method, you can use the --forcedshutdown parameter , added in start.bat Also i changed my mind and no more normal and maxi versions, only maxi. Because no one notices the big message on the first page that says which drivers should be used Please report if hawaiis and pitcairns compile now. Thanks
|
|
|
OK, i found that sometimes on miner close the overdriven settings are reset, probably because of the forced miner shutdown. I am going to investigate this issue.
In the meantime, today comes the fixed 1.6.8 that *should* compile on all gpu's. Also added a new gpu tuning parameter which can boost the hash a little bit.
|
|
|
Yes, fix coming in a day or two for hawaii and pitcairn
|
|
|
Heating up system, please wait... [2018-10-11 02:52:51] Created OCL context [2018-10-11 02:52:51] Created OCL command queue for DeviceID 0 (Thread 0) [2018-10-11 02:52:51] Created OCL input buffer for DeviceID 0 (Thread 0) [2018-10-11 02:52:51] Created OCL output buffer for DeviceID 0 (Thread 0) [2018-10-11 02:52:51] Compiling kernel for DEVICE BUS ID 7 ... [2018-10-11 02:52:51] Error CL_LINK_PROGRAM_FAILURE when calling clLinkProgram [ctx->Program] for DeviceID 0 (Thread 0) [2018-10-11 02:52:51] Error CL_INVALID_PROGRAM when calling clGetProgramBuildInfo for length of build log output for DeviceID 0 (Thread 0) [2018-10-11 02:52:51] Error initing GPU's. Stopping miner process [2018-10-11 02:52:51] Stopping miner process
What GPU is this ?
|
|
|
Can you guys share your V7 and V8 results on the same card?
|
|
|
|