Bitcoin Forum

Alternate cryptocurrencies => Mining (Altcoins) => Topic started by: Bixbitecoin on June 19, 2018, 03:10:41 PM



Title: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on June 19, 2018, 03:10:41 PM





Support CPU / AMD / Nvidia GPU Graphics with fan control. For test only.

https://bixbite.pro/wp-content/uploads/2018/10/vse.png (https://github.com/BixBite-project/bxb-miner/releases/tag/0.1.8.1)
Miner is early beta version.
Download:

Github: https://github.com/BixBite-project/bxb-miner/releases

Supported algo/coins:
Cryptonight
Cryptonight v7
Cryptonight v8(new algo)
Cryptonight-Fast (Masari)
Cryptonight-Heavy (Bixbite, Ryo, Loki)
New Stellite
New Haven
BitTube (IPBC), Alloy
Cryptonight Lite
Cryptonight Lite v7

Without Dev fee ! Not a fork of any miner software!


Config example:
Code:
{
"pools":[ // POOLS section
{
"name": "Bixbite", // pool configuration name
"url": "pool.bixbite.pro", // pool address
"port": 3333, // pool port
"stale-time": 0, // stale share time interval allowing window in milliseconds (0 means don't submit stale shares)
"user": "<WALLET>", // your wallet address
"pass": "<PASSWORD", // your password
"algo": "heavy" // mining algorithm: old, v7, v8, stellite, heavy, haven, ipbc(new BitTube variant), alloy, lite, lite_v7, masari, auto (for old/v7)
}
],
"ocl":{ // AMD (OpenCL) section
"gpu": "0", // GPU ID using to mine, for multiple set as "0,1,2,3,4"
"intensity": "896", // GPU intensity (one value for all GPUs, separated list for individual intensity per adapter ("896,432,896")
"threads": "2", // threads per GPU, can be set for multiple GPUs ("2,1,1,2,2")
"worksize": "8", // Worksize per GPU, can be set for multiple GPUs ("8,8,8,7,8")
"auto-fan": true, // fan auto-control
"target-temp": 60 // target temperature
},
"cuda":{ // NVIDIA (CUDA) section
"gpu": "0", // GPU ID using to mine, for multiple set as "0,1,2,3,4"
"blocks": "36", // blocks per GPU, may be set ("24,36,36,24,36")
"threads": "16", // threads per GPU, may be set ("8,8,16,32,8")
"temp-monitor": true // temperature monitoring
},
"cpu":{ // CPU section
"use-cpu": true, // Enable CPU mining
"cpu-threads": 2 // Manual settings for cpu threads (not recommend). Exclude this option to auto-select thread count.
},
"server": true, // this option enabling server monitoring feature, other rigs may acts as clients
"server-ip": "0.0.0.0", // server IP address to connect (when acts as client)
"rig-name": "PROG", // rig name on monitoring server
"log": true // show log at start and write into file
}

Use the "-c" switch to run different configurations (ex: bxb-miner.exe -c config_heavy.json)


BXB-Miner client-server usage:


If your have many rig`s in mine, you can use this function for simplefy monitoring and management

Next commands avalible for use:

  • Change current pool in all rigs;
  • Pause/Start all rig`s in mine;
  • Reset statistics on all rig`s connceted for server;
  • Reload pool list from file, without restart miner;
  • Update pool list in rigs (send list from server). Use macros $$$name$$$ in config for automaticaly replace to rig-name on recieved rig`s;

Recommended:
  • Use large pagefile, more 32gb
  • Set system variable:
  • GPU_FORCE_64BIT_PTR in 1
  • GPU_MAX_ALLOC_PERCENT 100
  • GPU_MAX_HEAP_SIZE 100
  • GPU_MAX_SINGLE_ALLOC_PERCENT 100
  • GPU_MAX_USE_SYNC_OBJECTS 1

Tested CPU`s:
Intel(R) Core(TM) i5-3450 CPU @ 3.10GHz // 3 threads // cryptonight v7 // 195 H/s

Intel(R) Core(TM) i5-3450 CPU @ 3.10GHz // 4 threads // cryptonight light v7 // 595 H/s

Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz // 12 threads // cryptonight v7 // 495 H/s

Intel(R) Xeon(R) CPU E3-1245 @ 3.30GHz // 4 threads // cryptonight v7 // 260 H/s

Tested cards:

BIXBITE COIN

~ BITCOINTALK ~ (https://bitcointalk.org/index.php?topic=3443277.0)
~ MINING POOL~  (https://pool.bixbite.pro/)
~ CLI WALLET ~ (https://github.com/BixBite-project/bixbite/releases)




Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: treanski on June 19, 2018, 06:45:41 PM
thank you speed is good like other miners with fee ;D

just haven dont works, i get no valid shares... i use haven algo in config

other heavy / cnv7 coins work fine

is it possible to prevent miner from autostart mining?

suggestion for next version...->different gpu configs in one config file

seperate them by name, select them on pool config with name


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Elder III on June 19, 2018, 08:42:58 PM
Are those hashrates for GPUs with modified Bios or with stock Bios?  Are they undervolted at all? 

Out of curiosity, what is your motivation to develop this without any fee implemented?


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: ro2sf on June 19, 2018, 09:25:24 PM
Perfect timing for announcing this miner as I'm trying to get into Cryptonight with my RX 580s. Thank you for this.

+1 for the curiosity of why this has 0% dev fee


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: igotek on June 19, 2018, 10:01:31 PM
I see so many big values for Core and MEM.
RX470 4GB HYNIX 1300/2020 ?? Wooow.
I m using SRBMiner currently and the mining software crash if i set such a high values for Core and MEM.

Did you use modified Bios ? I used PBE 2.2 to make modified Bios. 1276/1750 gives 696 h/s for heavy.
Currently mining Bixebite. I want to get 780 h/s for bixbite.


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: igotek on June 19, 2018, 10:18:24 PM
I have edited the config.json but the mining start with pool.supportxmr.com
I dont have this information in the config file.
why ?


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: grendel25 on June 19, 2018, 10:18:36 PM
Are those hashrates for GPUs with modified Bios or with stock Bios?  Are they undervolted at all?  

Out of curiosity, what is your motivation to develop this without any fee implemented?

Reminds me of the good old days when people developed fresh and new miners for free because they liked what they were doing and they wanted to share it with those in the community.  Nowadays people simply run existing miners through enhancement/optimization programs and then do a little work of compiling and adding in developer fees.  

Maybe things are looking up...


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: treanski on June 20, 2018, 03:22:52 AM
I have edited the config.json but the mining start with pool.supportxmr.com
I dont have this information in the config file.
why ?

remove the  -> , <- after the last pool


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on June 20, 2018, 05:14:30 AM
thank you speed is good like other miners with fee ;D

just haven dont works, i get no valid shares... i use haven algo in config

other heavy / cnv7 coins work fine

is it possible to prevent miner from autostart mining?

suggestion for next version...->different gpu configs in one config file

seperate them by name, select them on pool config with name

Did you set "algo": "haven" in your config file for Haven mining?


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: treanski on June 20, 2018, 05:49:24 AM
thank you speed is good like other miners with fee ;D

just haven dont works, i get no valid shares... i use haven algo in config

other heavy / cnv7 coins work fine

is it possible to prevent miner from autostart mining?

suggestion for next version...->different gpu configs in one config file

seperate them by name, select them on pool config with name

Did you set "algo": "haven" in your config file for Haven mining?

    {
      "name": "Haven",
      "url": "haven.miner.rocks",
      "port": 4005,
      "stale-time": 0,
      "user": "xxx",
      "pass": "x",
      "algo": "haven"
    },

--found another bug, if you close the miner by clicking on the x, its still running in the background as process

Quote
07:50:06, Connection to pool... haven.miner.rocks port: 4005
07:50:06, Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz
07:50:06, cache L2: 256
07:50:06, cache L3: 6144
07:50:06, Algo use 4 Mb memory/thread ...
07:50:06, Using 1 cpu threads ...
07:50:13, Device: #4 set lock pages privilege
07:50:13, Device: #4 set lock pages privilege
07:50:13, Device: #4 used virtual memory ...
07:50:13, Device: #4 used virtual memory ...
07:50:13, set worker algo: 9, device: 4, worker 0
07:50:13, Select pool algo: 9
07:50:13, Device: #0, worker #0 start calc new work ...
07:50:13, Device: #0, worker #1 start calc new work ...
07:50:13, Device: #1, worker #1 start calc new work ...
07:50:13, Device: #1, worker #0 start calc new work ...
07:50:13, Device: #2, worker #1 start calc new work ...
07:50:13, Device: #2, worker #0 start calc new work ...
07:50:13, Device: #3, worker #1 start calc new work ...
07:50:13, Device: #3, worker #0 start calc new work ...
07:50:13, Device: #4, worker #2 start calc new work ...
07:50:13, {"id":1,"jsonrpc":"2.0","error":null,"result":{"id":"384073909209323","job":{"blob":"0303acd5a7d905ed06cf349cd74820c775b6b78aacb7112071adbe7b5979d16e35dba37ca63a6a0 00000002e0042bd3fafef1da0454e04dad9532a5287ba86d79b8a63bd2236ba4189810909","job_id":"281989074608852","target":"b7d10000"},"status":"OK"}}
07:50:13, Pool work diff: 80000.1

07:50:13, Block diff: 3.32847e+7

07:50:13, Logon Ok!
07:50:13, Device: #0, worker #0 start calc new work ...
07:50:13, Device: #1, worker #1 start calc new work ...
07:50:14, Device: #1, worker #0 start calc new work ...
07:50:14, Device: #2, worker #1 start calc new work ...
07:50:14, {"jsonrpc":"2.0","method":"job","params":{"blob":"0303acd5a7d905ed06cf349cd74820c775b6b78aacb7112071adbe7b5979d16e35dba37ca63a6a0 000000025d11b6229548243506a0c812ba8c15c63da6501ead89eed32113f5bb11934b709","job_id":"529784849982997","target":"b7d10000"}}
07:50:14, Pool work diff: 80000.1
07:50:14, Block diff: 8.1474e+7

07:50:14, Device: #0, worker #1 start calc new work ...
07:50:14, Device: #3, worker #1 start calc new work ...
07:50:14, Device: #2, worker #0 start calc new work ...
07:50:14, Device: #3, worker #0 start calc new work ...
07:50:14, Device: #1, worker #1 start calc new work ...
07:50:14, Device: #0, worker #0 start calc new work ...
07:50:15, Device: #1, worker #0 start calc new work ...
07:50:15, Device: #2, worker #1 start calc new work ...
07:50:19, Device: #1 worker #0 OCL NONCE 33333b23 (858995491) found in slot 0 (found = 255)
07:50:19, Device: #1 worker #0 share diff: 1.72533, needed: 80000.1
07:50:21, Device: #0 worker #1 OCL NONCE 1999ae72 (429502066) found in slot 0 (found = 255)
07:50:21, Device: #0 worker #1 share diff: 3.12378, needed: 80000.1
07:50:23, Device: #4, worker #0 start calc new work ...
07:50:26, Device: #0 worker #1 OCL NONCE 1999bad5 (429505237) found in slot 0 (found = 255)
07:50:26, Device: #0 worker #1 share diff: 3.47199, needed: 80000.1
07:50:45, Device: #1 worker #1 OCL NONCE 4ccd2272 (1288512114) found in slot 0 (found = 255)
07:50:45, Device: #1 worker #1 share diff: 3.97704, needed: 80000.1


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: abhiseshakana on June 20, 2018, 06:26:32 AM
already used  this program (Beta Version) and i like the interface .. first used on Bixbite (test net) and still using this miner on Loki for now.
But sometimes the miner can't be opened, when i tried the third time and need to restart the Rig to solve this issue and i think it belong to OpenCL or ADL conflict.


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on June 20, 2018, 06:31:26 AM
--found another bug, if you close the miner by clicking on the x, its still running in the background as process

Why you decide it's a bug (only devs can confirm issue and mark some "abnormal action" as bug)? We're tested a lot before release first version, it's a normal process on exit when miner wait until all calculating jobs finished.


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: treanski on June 20, 2018, 07:44:31 AM
--found another bug, if you close the miner by clicking on the x, its still running in the background as process

Why you decide it's a bug (only devs can confirm issue and mark some "abnormal action" as bug)? We're tested a lot before release first version, it's a normal process on exit when miner wait until all calculating jobs finished.

oh my fucking god do not be pissed off directly for me it just looked like a bug -.-

maybe you should comment it in readme, because if you close miner and start it directly with another config the whole rig crash because of this background miningprocess
which is completely normal if you have two miners running at the same time


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on June 20, 2018, 09:21:18 AM
thank you speed is good like other miners with fee ;D

just haven dont works, i get no valid shares... i use haven algo in config

other heavy / cnv7 coins work fine

is it possible to prevent miner from autostart mining?

suggestion for next version...->different gpu configs in one config file

seperate them by name, select them on pool config with name

Did you set "algo": "haven" in your config file for Haven mining?

    {
      "name": "Haven",
      "url": "haven.miner.rocks",
      "port": 4005,
      "stale-time": 0,
      "user": "xxx",
      "pass": "x",
      "algo": "haven"
    },

--found another bug, if you close the miner by clicking on the x, its still running in the background as process

Quote
07:50:06, Connection to pool... haven.miner.rocks port: 4005
07:50:06, Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz
07:50:06, cache L2: 256
07:50:06, cache L3: 6144
07:50:06, Algo use 4 Mb memory/thread ...
07:50:06, Using 1 cpu threads ...
07:50:13, Device: #4 set lock pages privilege
07:50:13, Device: #4 set lock pages privilege
07:50:13, Device: #4 used virtual memory ...
07:50:13, Device: #4 used virtual memory ...
07:50:13, set worker algo: 9, device: 4, worker 0
07:50:13, Select pool algo: 9
07:50:13, Device: #0, worker #0 start calc new work ...
07:50:13, Device: #0, worker #1 start calc new work ...
07:50:13, Device: #1, worker #1 start calc new work ...
07:50:13, Device: #1, worker #0 start calc new work ...
07:50:13, Device: #2, worker #1 start calc new work ...
07:50:13, Device: #2, worker #0 start calc new work ...
07:50:13, Device: #3, worker #1 start calc new work ...
07:50:13, Device: #3, worker #0 start calc new work ...
07:50:13, Device: #4, worker #2 start calc new work ...
07:50:13, {"id":1,"jsonrpc":"2.0","error":null,"result":{"id":"384073909209323","job":{"blob":"0303acd5a7d905ed06cf349cd74820c775b6b78aacb7112071adbe7b5979d16e35dba37ca63a6a0 00000002e0042bd3fafef1da0454e04dad9532a5287ba86d79b8a63bd2236ba4189810909","job_id":"281989074608852","target":"b7d10000"},"status":"OK"}}
07:50:13, Pool work diff: 80000.1

07:50:13, Block diff: 3.32847e+7

07:50:13, Logon Ok!
07:50:13, Device: #0, worker #0 start calc new work ...
07:50:13, Device: #1, worker #1 start calc new work ...
07:50:14, Device: #1, worker #0 start calc new work ...
07:50:14, Device: #2, worker #1 start calc new work ...
07:50:14, {"jsonrpc":"2.0","method":"job","params":{"blob":"0303acd5a7d905ed06cf349cd74820c775b6b78aacb7112071adbe7b5979d16e35dba37ca63a6a0 000000025d11b6229548243506a0c812ba8c15c63da6501ead89eed32113f5bb11934b709","job_id":"529784849982997","target":"b7d10000"}}
07:50:14, Pool work diff: 80000.1
07:50:14, Block diff: 8.1474e+7

07:50:14, Device: #0, worker #1 start calc new work ...
07:50:14, Device: #3, worker #1 start calc new work ...
07:50:14, Device: #2, worker #0 start calc new work ...
07:50:14, Device: #3, worker #0 start calc new work ...
07:50:14, Device: #1, worker #1 start calc new work ...
07:50:14, Device: #0, worker #0 start calc new work ...
07:50:15, Device: #1, worker #0 start calc new work ...
07:50:15, Device: #2, worker #1 start calc new work ...
07:50:19, Device: #1 worker #0 OCL NONCE 33333b23 (858995491) found in slot 0 (found = 255)
07:50:19, Device: #1 worker #0 share diff: 1.72533, needed: 80000.1
07:50:21, Device: #0 worker #1 OCL NONCE 1999ae72 (429502066) found in slot 0 (found = 255)
07:50:21, Device: #0 worker #1 share diff: 3.12378, needed: 80000.1
07:50:23, Device: #4, worker #0 start calc new work ...
07:50:26, Device: #0 worker #1 OCL NONCE 1999bad5 (429505237) found in slot 0 (found = 255)
07:50:26, Device: #0 worker #1 share diff: 3.47199, needed: 80000.1
07:50:45, Device: #1 worker #1 OCL NONCE 4ccd2272 (1288512114) found in slot 0 (found = 255)
07:50:45, Device: #1 worker #1 share diff: 3.97704, needed: 80000.1


Show your full config.json, please


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on June 20, 2018, 09:37:40 AM
Are those hashrates for GPUs with modified Bios or with stock Bios?  Are they undervolted at all?  

Out of curiosity, what is your motivation to develop this without any fee implemented?

This tool is part of the Bixbit coin project and we decided to make him free, but you can always donate. Donate address specified inside miner window at bottom.


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: treanski on June 20, 2018, 10:16:03 AM


Show your full config.json, please

Quote
{
  "pools": [
    {
      "name": "Saronite",
      "url": "saronite.miner.rocks",
      "port": 5555,
      "stale-time": 2,
      "user": "x.80000",
      "pass": "x",
      "algo": "heavy"
    },
    {
      "name": "Haven",
      "url": "haven.ingest.cryptoknight.cc",
      "port": 5832,
      "stale-time": 2,
      "user": "x.80000",
      "pass": "x",
      "algo": "haven"
    },
    {
      "name": "loki",
      "url": "loki.miner.rocks",
      "port": 5555,
      "stale-time": 2,
      "user": "x.80000",
      "pass": "x",
      "algo": "heavy"
    },
    {
      "name": "ryo",
      "url": "mine.ryo.fairpool.xyz",
      "port": 5555,
      "stale-time": 2,
      "user": "x",
      "pass": "x",
      "algo": "heavy"
    }
  ],
  "intensity": "896",
  "gpu": "0,1,2,3,4",
  "gpu-threads": "2",
  "worksize":"8",
  "auto-fan": false,
  "target-temp": 60,
  "server": true,
  "server-ip": "0.0.0.0",
  "rig-name": "MAIN_RIG",
  "use-cpu":false,
  "cpu-threads": 3
}


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: raske on June 20, 2018, 10:52:24 AM
will do some tests on my cards, hope that will work for me too


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on June 20, 2018, 11:02:16 AM


Show your full config.json, please

Quote
{
  "pools": [
    {
      "name": "Saronite",
      "url": "saronite.miner.rocks",
      "port": 5555,
      "stale-time": 2,
      "user": "x.80000",
      "pass": "x",
      "algo": "heavy"
    },
    {
      "name": "Haven",
      "url": "haven.ingest.cryptoknight.cc",
      "port": 5832,
      "stale-time": 2,
      "user": "x.80000",
      "pass": "x",
      "algo": "haven"
    },
    {
      "name": "loki",
      "url": "loki.miner.rocks",
      "port": 5555,
      "stale-time": 2,
      "user": "x.80000",
      "pass": "x",
      "algo": "heavy"
    },
    {
      "name": "ryo",
      "url": "mine.ryo.fairpool.xyz",
      "port": 5555,
      "stale-time": 2,
      "user": "x",
      "pass": "x",
      "algo": "heavy"
    }
  ],
  "intensity": "896",
  "gpu": "0,1,2,3,4",
  "gpu-threads": "2",
  "worksize":"8",
  "auto-fan": false,
  "target-temp": 60,
  "server": true,
  "server-ip": "0.0.0.0",
  "rig-name": "MAIN_RIG",
  "use-cpu":false,
  "cpu-threads": 3
}

Set the haven pool is first in list. Swapping between different algoritms not yet working correctly. We will add this feature in next releases.

If your dont use server-client function set "server": false


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: raske on June 20, 2018, 11:03:23 AM
can someone share the "start.bat" file, I cant atart the miner  ??? :-\


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on June 20, 2018, 11:07:06 AM
can someone share the "start.bat" file, I cant atart the miner  ??? :-\
What is your problem?
your config please


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: raske on June 20, 2018, 11:19:57 AM
can someone share the "start.bat" file, I cant atart the miner  ??? :-\
What is your problem?
your config please

sorry, I did it, now I wave to play with my intensity to run this miner on higher levels than SRBminer


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: treanski on June 20, 2018, 11:44:16 AM
can someone share the "start.bat" file, I cant atart the miner  ??? :-\

there is no start.bat

if you want to run specicif config file use bxb-miner.exe -c configfile.json

@dev thanks, this way it works


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: abhiseshakana on June 20, 2018, 04:19:52 PM
can someone share the "start.bat" file, I cant atart the miner  ??? :-\

use the config.json and hit the "bxb-miner.exe" directly

this is config.json that i use

Code:
{
  "pools": [
  {
      "name":"LoKi",
      "url": "loki.miner.rocks",
      "port":7777,
      "stale-time":0,
      "user": "L9ftbfMEB1SRjvZcX4cvsxBg3dib2r4nMCe7vDbJjWDNHxKvMGmCfWbQX8xbFQfLQVCuFxQQWpai1SxnCWg67oY5Hb7zwpy.180000",
      "pass": "LoKi02",
      "algo":"heavy"
   }
  ],
  "intensity": "920,920,1024,1024,1024,920",
  "gpu":"0,1,2,3,4,5",
  "gpu-threads": "2",
  "auto-fan":false,
  "target-temp":60,
  "server":true,
  "server-ip":"127.0.0.1", 
  "rig-name":"LoKi02"
}


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: igotek on June 20, 2018, 06:19:47 PM
What is the problem ?
Where is pool.supportxmr.com in the config file ?????

Picture:
http://fs5.directupload.net/images/180620/dxj6o4r2.png

Code:
{
  "pools": [
  {
      "name":"test_coin",
      "url": "loki.miner.rocks",
      "port":7777,
      "stale-time":0,
      "user": "L9ftbfMEB1SRjvZcX4cvsxBg3dib2r4nMCe7vDbJjWDNHxKvMGmCfWbQX8xbFQfLQVCuFxQQWpai1SxnCWg67oY5Hb7zwpy.180000",
      "pass": "LoKi02",
      "algo":"heavy"
   }
  ],
  "intensity": "896",          // GPU intensity (one value for all GPUs, separated list for individual intensity per adapter ("896,432,896")
  "gpu":"0,1,2,3,4,5,6,7,8",            // GPU ID using to mine, for multiple set as "0,1,2,3,4"
  "gpu-threads": "2",         // threads per GPU, may be set ("2,1,1,2,2")
  "worksize":"8",         // Worksize per GPU, may be set ("8,8,8,7,8")
  "auto-fan":true,         // fan auto-control
  "target-temp":60,         // target temperature
  "server":true,          // this option enabling server monitoring feature, other rigs may acts as clients
  "server-ip":"0.0.0.0",        // server IP address for server monitoring
  "rig-name":"PROG",            // rig name on monitoring server
  "use-cpu":true,          // Enable CPU mining
  "cpu-threads": 2          // Manual settings for cpu threads (not recomended). Not set this otion for auto select thread count.
}


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: treanski on June 20, 2018, 06:52:13 PM
What is the problem ?
Where is pool.supportxmr.com in the config file ?????

Picture:
http://fs5.directupload.net/images/180620/dxj6o4r2.png

Code:
{
  "pools": [
  {
      "name":"test_coin",
      "url": "loki.miner.rocks",
      "port":7777,
      "stale-time":0,
      "user": "L9ftbfMEB1SRjvZcX4cvsxBg3dib2r4nMCe7vDbJjWDNHxKvMGmCfWbQX8xbFQfLQVCuFxQQWpai1SxnCWg67oY5Hb7zwpy.180000",
      "pass": "LoKi02",
      "algo":"heavy"
   }
  ],
  "intensity": "896",          // GPU intensity (one value for all GPUs, separated list for individual intensity per adapter ("896,432,896")
  "gpu":"0,1,2,3,4,5,6,7,8",            // GPU ID using to mine, for multiple set as "0,1,2,3,4"
  "gpu-threads": "2",         // threads per GPU, may be set ("2,1,1,2,2")
  "worksize":"8",         // Worksize per GPU, may be set ("8,8,8,7,8")
  "auto-fan":true,         // fan auto-control
  "target-temp":60,         // target temperature
  "server":true,          // this option enabling server monitoring feature, other rigs may acts as clients
  "server-ip":"0.0.0.0",        // server IP address for server monitoring
  "rig-name":"PROG",            // rig name on monitoring server
  "use-cpu":true,          // Enable CPU mining
  "cpu-threads": 2          // Manual settings for cpu threads (not recomended). Not set this otion for auto select thread count.
}


if you have only 1 pool in config and you put a -> , <- instead of leaving it blank at the end of pool config the miner connects to supportxmr pool


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on June 20, 2018, 07:06:06 PM
What is the problem ?
Where is pool.supportxmr.com in the config file ?????

Picture:
http://fs5.directupload.net/images/180620/dxj6o4r2.png

Code:
{
  "pools": [
  {
      "name":"test_coin",
      "url": "loki.miner.rocks",
      "port":7777,
      "stale-time":0,
      "user": "L9ftbfMEB1SRjvZcX4cvsxBg3dib2r4nMCe7vDbJjWDNHxKvMGmCfWbQX8xbFQfLQVCuFxQQWpai1SxnCWg67oY5Hb7zwpy.180000",
      "pass": "LoKi02",
      "algo":"heavy"
   }
  ],
  "intensity": "896",          // GPU intensity (one value for all GPUs, separated list for individual intensity per adapter ("896,432,896")
  "gpu":"0,1,2,3,4,5,6,7,8",            // GPU ID using to mine, for multiple set as "0,1,2,3,4"
  "gpu-threads": "2",         // threads per GPU, may be set ("2,1,1,2,2")
  "worksize":"8",         // Worksize per GPU, may be set ("8,8,8,7,8")
  "auto-fan":true,         // fan auto-control
  "target-temp":60,         // target temperature
  "server":true,          // this option enabling server monitoring feature, other rigs may acts as clients
  "server-ip":"0.0.0.0",        // server IP address for server monitoring
  "rig-name":"PROG",            // rig name on monitoring server
  "use-cpu":true,          // Enable CPU mining
  "cpu-threads": 2          // Manual settings for cpu threads (not recomended). Not set this otion for auto select thread count.
}

Remove all comment from config file

valid:
Code:
{
  "pools": [
    {
      "name": "test_coin",
      "url": "loki.miner.rocks",
      "port": 7777,
      "stale-time": 0,
      "user": "L9ftbfMEB1SRjvZcX4cvsxBg3dib2r4nMCe7vDbJjWDNHxKvMGmCfWbQX8xbFQfLQVCuFxQQWpai1SxnCWg67oY5Hb7zwpy.180000",
      "pass": "LoKi02",
      "algo": "heavy"
    }
  ],
  "intensity": "896",
  "gpu": "0,1,2,3,4,5,6,7,8",
  "gpu-threads": "2",
  "worksize": "8",
  "auto-fan": true,
  "target-temp": 60,
  "server": true,
  "server-ip": "0.0.0.0",
  "rig-name": "PROG",
  "use-cpu": true,
  "cpu-threads": 2
}


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: schriss on June 20, 2018, 07:39:00 PM
--found another bug, if you close the miner by clicking on the x, its still running in the background as process

Why you decide it's a bug (only devs can confirm issue and mark some "abnormal action" as bug)? We're tested a lot before release first version, it's a normal process on exit when miner wait until all calculating jobs finished.

It is usability issue that can allow users to crash rig by running miner multiple times.
Possible solutions:
- show some kind of "Exiting, please wait" popup while miner finishes up and exists.
- do not allow to start more than one instance of the miner
Ideally, both of the above..


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: gameboy366 on June 21, 2018, 07:17:58 AM
Which gpu is better overall for mining

msi Armour rx 570 8gb  or Sapphire Nitro+ Rx 580 4gb

Sapphire is $45 expensive. I think Armour is better because it has 8gb, right ? What would u choose.


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: edwardceng on June 21, 2018, 07:33:45 AM
yeah, choose RX570 8 GB if prepare for Dag Size until 4GB

but for performance, I choose RX580 4GB because have a bit different with RX570 such as GPU clock, Boost clock, Shading unit.


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: gameboy366 on June 21, 2018, 08:14:18 AM
yeah, choose RX570 8 GB if prepare for Dag Size until 4GB

but for performance, I choose RX580 4GB because have a bit different with RX570 such as GPU clock, Boost clock, Shading unit.
I am not worried about dag size. I don't mine ethereum, and by the time dag crosses 4gb ethereum will go pos. I think 8gb gives advantage on Cryptonight, just look at table.


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: ggarbi on June 22, 2018, 04:35:39 PM
Guys what is your hashrate with this miner ?
because i have no clue that should i try it or not


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: eemm on June 23, 2018, 04:32:42 PM
How about vega56 ?


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: treanski on June 23, 2018, 07:45:27 PM
fr my vegas this miner is faster than xmrstak, srb or ggs miner...and no fee ;D


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Pennywis3 on June 23, 2018, 11:39:54 PM
socket error 1 :/


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: lexele on June 24, 2018, 07:58:55 AM
hello,
I tried with my vegas, vega 64 I got same speed than other miners, but not with vega 56 flashed to 64...those are a bit lazy. But well I'm not sure I found best intensity.

This miner does not support Nicehash, does he?


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Pennywis3 on June 24, 2018, 08:02:35 AM
hello,
I tried with my vegas, vega 64 I got same speed than other miners, but not with vega 56 flashed to 64...those are a bit lazy. But well I'm not sure I found best intensity.

This miner does not support Nicehash, does he?

Indeed it doesn't.


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Iamtutut on June 24, 2018, 12:58:46 PM
Has anyone tested with RX 470/570 4GB ?


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Sgsg666 on June 25, 2018, 09:18:17 AM
Are you guys going to add/support cn-fast & cn-saber(Bittube)? thanks! can someone post a pic of vega 56/64 h/s?


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Ballscack on June 25, 2018, 01:20:08 PM
What intensity should a vega 64 have?

its set to 1024 and worksize 8 only 1700 hashes and 2100 on srb @2 1502 core 1100 mem

* update: @ 1800 intensity i get arround 2050 hs a card on 1502 core 1100 mem*
* update 2 @ 1792 intensity i get arround 2089 hs a card on 1502 core 1100 mem *


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Ballscack on June 25, 2018, 02:47:08 PM
https://ibb.co/fqmpc8


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: proffe14 on June 26, 2018, 12:12:10 PM
What intensity should a vega 64 have?

its set to 1024 and worksize 8 only 1700 hashes and 2100 on srb @2 1502 core 1100 mem

* update: @ 1800 intensity i get arround 2050 hs a card on 1502 core 1100 mem*
* update 2 @ 1792 intensity i get arround 2089 hs a card on 1502 core 1100 mem *
Have you achieved a good result?)


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: RaidoP2 on June 26, 2018, 05:48:30 PM
I tested the miner, v7 works ok but Stellite is only giving incorrect shares:

 Device: #2 worker #0 share diff: 1.29969, needed: 50000.2

Anyone else having this problem when mining Stellite?


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: treanski on June 28, 2018, 11:38:56 AM
I tested the miner, v7 works ok but Stellite is only giving incorrect shares:

 Device: #2 worker #0 share diff: 1.29969, needed: 50000.2

Anyone else having this problem when mining Stellite?

you probably have different algos in one config file, this dont work on current version. you need seperate config for each algo


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: RaidoP2 on June 28, 2018, 11:48:16 AM
I tested the miner, v7 works ok but Stellite is only giving incorrect shares:

 Device: #2 worker #0 share diff: 1.29969, needed: 50000.2

Anyone else having this problem when mining Stellite?

you probably have different algos in one config file, this dont work on current version. you need seperate config for each algo

Thanks for the reply, but I had only Stellite algo in the config file, removed every other algo from there.


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bitmakin on June 28, 2018, 12:04:39 PM
Does it work well on R9 290?


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on June 28, 2018, 12:08:30 PM
Are you guys going to add/support cn-fast & cn-saber(Bittube)? thanks! can someone post a pic of vega 56/64 h/s?

Yes, if it will be demanded


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on June 28, 2018, 12:09:27 PM
I tested the miner, v7 works ok but Stellite is only giving incorrect shares:

 Device: #2 worker #0 share diff: 1.29969, needed: 50000.2

Anyone else having this problem when mining Stellite?

you probably have different algos in one config file, this dont work on current version. you need seperate config for each algo

Thanks for the reply, but I had only Stellite algo in the config file, removed every other algo from there.

What is your processor? Write a model, please


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on June 28, 2018, 12:28:30 PM
Does it work well on R9 290?

No tested on R290 only on r390. We will be thankful if you send your results


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: RaidoP2 on June 28, 2018, 12:44:27 PM
Does it work well on R9 290?

No tested on R290 only on r390. We will be thankful if you send your results

I tested it on R9 290 and 290X, seem to work fine on regular v7.

Are you planning to improve this software somehow or is this the final release?


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on June 28, 2018, 05:22:36 PM
Does it work well on R9 290?

No tested on R290 only on r390. We will be thankful if you send your results

I tested it on R9 290 and 290X, seem to work fine on regular v7.

Are you planning to improve this software somehow or is this the final release?

For the release of the final version is still far away, there are many interesting ideas that are not yet implemented. They will be implemented in future versions. Also, the code will be optimized.


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: xpulse on June 28, 2018, 06:07:10 PM
Hi,

Is anyway to add nicehash support to this miner? Currently all orders rejected by the pool.


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Robbowz on July 03, 2018, 09:52:40 AM
Hey! Great program from what i can see.

I have one issue only so far, and the GUI won't show and my GPU's don't start to mine.
The process starts (can see it in task manager) and my CPU starts mining.

Config:

{
  "pools": [
    {
      "name": "Monero",
      "url": "xmr-eu1.nanopool.org",
      "port": 14433,
      "stale-time": 60000,
      "user": "**HIDDEN**",
      "pass": "x",
      "algo": "v7"
    }   
  ],
  "intensity": "432",
  "gpu": "0,1,2,3",
  "gpu-threads": "2",
  "worksize":"8",
  "auto-fan": true,
  "target-temp": 60,
  "server": true,
  "server-ip": "0.0.0.0",
  "rig-name": "MAIN_RIG",
  "use-cpu":true,
  "cpu-threads": 1
}

Also tried port 14444
And run as Administrator, run it through CMD with -c config.json behind it.

Same issue every time, process starts but no GPU or GUI.

Any tips?


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on July 03, 2018, 05:21:09 PM
Hey! Great program from what i can see.

I have one issue only so far, and the GUI won't show and my GPU's don't start to mine.
The process starts (can see it in task manager) and my CPU starts mining.

Config:

{
  "pools": [
    {
      "name": "Monero",
      "url": "xmr-eu1.nanopool.org",
      "port": 14433,
      "stale-time": 60000,
      "user": "**HIDDEN**",
      "pass": "x",
      "algo": "v7"
    }    
  ],
  "intensity": "432",
  "gpu": "0,1,2,3",
  "gpu-threads": "2",
  "worksize":"8",
  "auto-fan": true,
  "target-temp": 60,
  "server": true,
  "server-ip": "0.0.0.0",
  "rig-name": "MAIN_RIG",
  "use-cpu":true,
  "cpu-threads": 1
}

Also tried port 14444
And run as Administrator, run it through CMD with -c config.json behind it.

Same issue every time, process starts but no GPU or GUI.

Any tips?

Use option "server: false" if your have one rig

p.s.

Set  "stale-time": 0,


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Chacello on July 07, 2018, 07:46:46 PM
Hey! Great program from what i can see.

I have one issue only so far, and the GUI won't show and my GPU's don't start to mine.
The process starts (can see it in task manager) and my CPU starts mining.

Config:

{
  "pools": [
    {
      "name": "Monero",
      "url": "xmr-eu1.nanopool.org",
      "port": 14433,
      "stale-time": 60000,
      "user": "**HIDDEN**",
      "pass": "x",
      "algo": "v7"
    }    
  ],
  "intensity": "432",
  "gpu": "0,1,2,3",
  "gpu-threads": "2",
  "worksize":"8",
  "auto-fan": true,
  "target-temp": 60,
  "server": true,
  "server-ip": "0.0.0.0",
  "rig-name": "MAIN_RIG",
  "use-cpu":true,
  "cpu-threads": 1
}

Also tried port 14444
And run as Administrator, run it through CMD with -c config.json behind it.

Same issue every time, process starts but no GPU or GUI.

Any tips?

Use option "server: false" if your have one rig

p.s.

Set  "stale-time": 0,

Hello, or change "server-ip": "0.0.0.0", to "server-ip": "127.0.0.1",   
;)
btw
@Bixbitecoin Greate miner, tested on:
Intel(R) Xeon(R) CPU E31245 @ 3.30GHz // 4 threads // cryptonight v7 // ~260 H/s
5 servers this is average stat.



Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on July 08, 2018, 06:48:08 PM
New version (0.0.7.0) of BXB-Miner released!
Added support for BitTube (IPBC), Saber variant
Fixed bug with Cryptonight-Light algo
New functions in client-server mode


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on July 08, 2018, 06:52:44 PM
Intel(R) Xeon(R) CPU E31245 @ 3.30GHz // 4 threads // cryptonight v7 // ~260 H/s

Thanks, added!


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: naermiller on July 13, 2018, 09:06:58 PM
I have stale time set to 0. I seem to be getting a lot of stale shares on cn heavy and v7. Is this a proper setting?


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: treanski on July 13, 2018, 09:53:14 PM
I have stale time set to 0. I seem to be getting a lot of stale shares on cn heavy and v7. Is this a proper setting?

just set to 1 or 2 and look if results are better X_X..dont forget breathing


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: naermiller on July 13, 2018, 10:17:26 PM
I have stale time set to 0. I seem to be getting a lot of stale shares on cn heavy and v7. Is this a proper setting?




just set to 1 or 2 and look if results are better X_X..dont forget breathing



I will try it out. Fantastic miner and great speeds even on my vegas with hynix. I already deleted XMR STAK


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: naermiller on July 14, 2018, 02:43:09 AM
Does the newest version support cn fast (Masari)?


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on July 14, 2018, 02:52:54 PM
Does the newest version support cn fast (Masari)?
No
Will be added in the next version


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on July 14, 2018, 06:03:06 PM
Does the newest version support cn fast (Masari)?

New 0.0.7.1 version of BXB-miner has been released
Added support for Masari for you and for everyone. Download the lastest .exe file from github and use "algo": "masari" for  mining Masari


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: naermiller on July 15, 2018, 02:23:49 AM
Does the newest version support cn fast (Masari)?

New 0.0.7.1 version of BXB-miner has been released
Added support for Masari for you and for everyone. Download the lastest .exe file from github and use "algo": "masari" for  mining Masari

Working great so far..nicely done


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Elder III on July 15, 2018, 03:56:14 AM
What kind of hashrate can be expected on a Rx 580/480 mining Masari?  I haven't ever mined that before, so I'm not sure what to expect for a normal hashrate.


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: AndikaTanpaH on July 16, 2018, 03:35:22 AM
hi everyone, im new here...

my question how to i know max GPU intensity? any tools there?

so far i just tested with my old rig
CPU AMD A8 7800 : 45-55 H/s (4 threads)
GPU ICooler R7 240 2GB : 150-160 H/s (2 threads)

maybe i can run with higher hash?


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on July 16, 2018, 03:18:58 PM
hi everyone, im new here...

my question how to i know max GPU intensity? any tools there?

so far i just tested with my old rig
CPU AMD A8 7800 : 45-55 H/s (4 threads)
GPU ICooler R7 240 2GB : 150-160 H/s (2 threads)

maybe i can run with higher hash?

for each algorithm its own intensity
Which algo do you use?


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: aini97 on July 16, 2018, 03:41:14 PM



Miner is early beta version.

Support CPU / AMD GPU Graphics with fan control. For test only.

Download:

Github: https://github.com/BixBite-project/bxb-miner/releases

Supported algo/coins:
Cryptonight
Cryptonight v7
Cryptonight-Fast (Masari)
Cryptonight-Heavy (Bixbite, Sumocoin)
New Stellite
New Haven
BitTube (IPBC), Alloy
Cryptonight Lite
Cryptonight Lite v7

Without Dev fee ! Not a fork of any miner software!


Config example:
Quote
{
  "pools": [             // list pools
  {
   "name":"Bixbite",      // configuration name
   "url": "pool.bixbite.pro",   // pool url address
   "port": 3333,         // pool port
    "stale-time":0,         // stale share time interval allowing window (ms)
   "user": "<WALLET>",      // wallet address
   "pass": "",          // password
   "algo":"heavy"         // supported algorithm: old, v7, stellite, heavy, haven, ipbc, alloy, lite, lite_v7, masari, auto (for old/v7)
  }
  ],
  "intensity": "896",          // GPU intensity (one value for all GPUs, separated list for individual intensity per adapter ("896,432,896")
  "gpu":"0",            // GPU ID using to mine, for multiple set as "0,1,2,3,4"
  "gpu-threads": "2",         // threads per GPU, may be set ("2,1,1,2,2")
  "worksize":"8",         // Worksize per GPU, may be set ("8,8,8,7,8")
  "auto-fan":true,         // fan auto-control
  "target-temp":60,         // target temperature
  "server":true,          // this option enabling server monitoring feature, other rigs may acts as clients
  "server-ip":"0.0.0.0",        // server IP address for server monitoring
  "rig-name":"PROG",            // rig name on monitoring server
  "use-cpu":true,          // Enable CPU mining
  "cpu-threads": 2          // Manual settings for cpu threads (not recomended). Not set this otion for auto select thread count.
}

Use the "-c" switch to run different configurations (ex: bxb-miner.exe -c config_heavy.json)


BXB-Miner client-server usage:


If your have many rig`s in mine, you can use this function for simplefy monitoring and management

Next commands avalible for use:

  • Change current pool in all rigs;
  • Pause/Start all rig`s in mine;
  • Reset statistics on all rig`s connceted for server;
  • Reload pool list from file, without restart miner;
  • Update pool list in rigs (send list from server). Use macros $$$name$$$ in config for automaticaly replace to rig-name on recieved rig`s;

Recommended:
  • Use large pagefile, more 32gb
  • Set system variable:
  • GPU_FORCE_64BIT_PTR in 1
  • GPU_MAX_ALLOC_PERCENT 100
  • GPU_MAX_HEAP_SIZE 100
  • GPU_MAX_SINGLE_ALLOC_PERCENT 100
  • GPU_MAX_USE_SYNC_OBJECTS 1

Tested CPU`s:
Intel(R) Core(TM) i5-3450 CPU @ 3.10GHz // 3 threads // cryptonight v7 // 195 H/s

Intel(R) Core(TM) i5-3450 CPU @ 3.10GHz // 4 threads // cryptonight light v7 // 595 H/s

Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz // 12 threads // cryptonight v7 // 495 H/s

Intel(R) Xeon(R) CPU E3-1245 @ 3.30GHz // 4 threads // cryptonight v7 // 260 H/s

Tested cards:

BIXBITE COIN

~ BITCOINTALK ~ (https://bitcointalk.org/index.php?topic=3443277.0)
~ MINING POOL~  (https://pool.bixbite.pro/)
~ CLI WALLET ~ (https://github.com/BixBite-project/bixbite/releases)


agree really comrades, indeed in berbinis especially with matters relating to the world of bitcoin is very in need kehati0-hatian dalm sell certain goods. and I think this is a lucky information for me in terms of doing business and hopefully be a very useful lesson for myself,.,..


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: hamesh on July 21, 2018, 09:01:50 PM
can someone share the "start.bat" file, I cant atart the miner  ??? :-\

Here's mine.  Monitors for crash and restarts if no longer in memory.

Code:
setx GPU_FORCE_64BIT_PTR 1
setx GPU_MAX_HEAP_SIZE 100
setx GPU_MAX_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_MAX_SINGLE_ALLOC_PERCENT 100
@echo off
cd %~dp0

cls
SETLOCAL EnableExtensions
set EXE=bxb-miner.exe

:START
FOR /F %%x IN ('tasklist /NH /FI "IMAGENAME eq %EXE%"') DO IF %%x == %EXE% goto RUNNING
%EXE% -c config_lite_v7.json
TIMEOUT /T 15 /NOBREAK
goto START
:RUNNING
echo "%EXE% is already running"
pause


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: naermiller on July 22, 2018, 08:59:19 PM
How accurate is the 'found blocks' statistic? My miner says Ive found a block but the pool doesnt show it. Im currently the only one mining loki on the pool


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: treanski on July 23, 2018, 04:09:22 AM
How accurate is the 'found blocks' statistic? My miner says Ive found a block but the pool doesnt show it. Im currently the only one mining loki on the pool

in this case it seems not to be very accurate :P


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on July 24, 2018, 09:02:37 AM
Because all the GPU code is ripped from XMR-Stak while in the OP, they lie about not being a fork of anything, I decided to make a fork with the kernels exposed for easy viewing:

https://github.com/OhGodAPet/bxb-miner

People can't keep getting away with this bullshit.

Good day!

GPU Kernels from XMR-STAK not used. Miner based on kernels of Sgminer-gm. We are make changes that gave a larger hashrate compared to XMR-Stack. Please note that miner does not consist only gpu kernels and the rest of the code was rewritten from scratch.

p.s.

Analyze the kernels for difference and you'll realize what a ridiculous omission gives hashrate loss in the XMR-Stak

p.p.s.

Words about ripped code is bullshit !


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on July 24, 2018, 09:03:28 AM
How accurate is the 'found blocks' statistic? My miner says Ive found a block but the pool doesnt show it. Im currently the only one mining loki on the pool

Unfortunately this function does not work correctly


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: alanchi on July 30, 2018, 02:20:35 AM
hi please add to BXB Miner for this coin.

webchain with modified cryptonightV7
https://bitcointalk.org/index.php?topic=3649170.0


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Ballscack on August 11, 2018, 01:21:47 PM
Because all the GPU code is ripped from XMR-Stak while in the OP, they lie about not being a fork of anything, I decided to make a fork with the kernels exposed for easy viewing:

https://github.com/OhGodAPet/bxb-miner

People can't keep getting away with this bullshit.

so they stole parts? did they add a dev fee for them or just removed it


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: hamesh on September 04, 2018, 06:25:58 PM
Great miner.  Love the management functionality.  Tried it for BitTube but sounds like needs to be updated to support tube's new Cryptonight-Heavy variant named Saber.  IPBC results in rejected shares.  Any chance to add Saber in a future release?  :)


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: proffe14 on September 10, 2018, 01:43:35 PM
Great miner.  Love the management functionality.  Tried it for BitTube but sounds like needs to be updated to support tube's new Cryptonight-Heavy variant named Saber.  IPBC results in rejected shares.  Any chance to add Saber in a future release?  :)
I think the developer adds support for new algorithms. It remains only to wait


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on October 17, 2018, 05:24:27 PM
New version of bxb-miner released!

Changes:
CNv2 support was added (Monero from OCT 18th, Wownero).
Use in configuration file "algo":"v8" param.
Also we are  recommend to use worksize 16.
Fixed several bugs.

https://github.com/BixBite-project/bxb-miner/releases/tag/0.0.7.9


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: jamesverdy on October 24, 2018, 01:19:41 PM
Great miner - I have the highest hash on this miner :o


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Bixbitecoin on October 30, 2018, 09:39:22 AM
New version BXB-Miner released!  

https://bixbite.pro/wp-content/uploads/2018/10/vse.png (https://github.com/BixBite-project/bxb-miner/releases/tag/0.1.8.1)

https://github.com/BixBite-project/bxb-miner/releases/tag/0.1.8.1

We are glad to announce that our miner now supports nVidia GPU. It was not easy, but we successfully solved this, having spent a lot of time. Now we ready to follow our plan further.


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: justoiurii on October 31, 2018, 08:40:29 AM
Hello. I can't test the miner due message "bad syntax's in config file"(((( With earlier version I had no problems. Could you share the example config for only heavy algo? Thanks in advance) 


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: proffe14 on October 31, 2018, 05:22:48 PM
Hello. I can't test the miner due message "bad syntax's in config file"(((( With earlier version I had no problems. Could you share the example config for only heavy algo? Thanks in advance) 
You need to adjust the intensity for algo heavy / haven - I have an RX 584, I put an intensity of 477

Code:
{
"pools":[ // POOLS section
{
"name": "Bixbite", // pool configuration name
"url": "pool.bixbite.pro", // pool address
"port": 3333, // pool port
"stale-time": 0, // stale share time interval allowing window in milliseconds (0 means don't submit stale shares)
"user": "<WALLET>", // your wallet address
"pass": "<PASSWORD", // your password
"algo": "heavy" // mining algorithm: old, v7, v8, stellite, heavy, haven, ipbc(new BitTube variant), alloy, lite, lite_v7, masari, auto (for old/v7)
}
],
"ocl":{ // AMD (OpenCL) section
"gpu": "0", // GPU ID using to mine, for multiple set as "0,1,2,3,4"
"intensity": "896", // GPU intensity (one value for all GPUs, separated list for individual intensity per adapter ("896,432,896")
"threads": "2", // threads per GPU, can be set for multiple GPUs ("2,1,1,2,2")
"worksize": "8", // Worksize per GPU, can be set for multiple GPUs ("8,8,8,7,8")
"auto-fan": true, // fan auto-control
"target-temp": 60 // target temperature
},
"cuda":{ // NVIDIA (CUDA) section
"gpu": "0", // GPU ID using to mine, for multiple set as "0,1,2,3,4"
"blocks": "36", // blocks per GPU, may be set ("24,36,36,24,36")
"threads": "16", // threads per GPU, may be set ("8,8,16,32,8")
"temp-monitor": true // temperature monitoring
},
"cpu":{ // CPU section
"use-cpu": true, // Enable CPU mining
"cpu-threads": 2 // Manual settings for cpu threads (not recommend). Exclude this option to auto-select thread count.
},
"server": true, // this option enabling server monitoring feature, other rigs may acts as clients
"server-ip": "0.0.0.0", // server IP address to connect (when acts as client)
"rig-name": "PROG", // rig name on monitoring server
"log": true // show log at start and write into file
}


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: Pesovanid on November 01, 2018, 03:51:14 PM
Can I use this miner with R9 390 for CNV8 mining?


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: herrdrone on November 06, 2018, 11:00:54 PM
Can I use this miner with R9 390 for CNV8 mining?
Yes.

Recently, got some benchmarks submitted using this miner on monerobenchmarks.info
Added to mining software list: https://monerobenchmarks.info/tools.php (https://monerobenchmarks.info/tools.php)  8)


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: marcrblevins on November 12, 2018, 12:00:01 AM
I'm trying to use the latest version, 1.8.5.

I have 12 Vega FEs and an embeded Intel graphic chip.  No Nvidia GPUs.

It brings up a little dialog numbering 1 thru 12, the big screen supposed to show up.  Never does.

I'm back to version 0.0.7.9 with no issues.

From my log file:
Code:
Connection to pool... mine.xhv.fairpool.xyz port: 5566

Select pool algo: 9
CPU AES support

Skip cpu...

Find CUDA devices...

No found ...

ADL is init...
Found adl devices: 40

Active Adapter:
Adapter Index: 2
UDID: PCI_VEN_1002&DEV_6863&SUBSYS_6B761002&REV_00_6&195D7A5A&0&00000008A
Location: PCI bus 3, device 0, function 0
VendorID: 1002
Adapter Name: Radeon Vega Frontier Edition
Display Name:
Present: no
Primary: no
Active: no
Adapter Id: -1322640768

Adapter temp: 28 C
Adapter fan: 4746 RPM
Adapter iCoreClock: 26 Mhz
Adapter iCurrentBusLanes: 16
Adapter iCurrentBusSpeed: 8000
Adapter iCurrentCorePerformanceLevel: 0
Adapter iCurrentDCEFPerformanceLevel: 0
Adapter iCurrentGFXPerformanceLevel: 0
Adapter iCurrentMemoryPerformanceLevel: 0
Adapter iDCEFClock: 0
Adapter iGFXClock: 0
Adapter iGPUActivityPercent: 0
Adapter iMaximumBusLanes: 16
Adapter iMemoryClock: 167 Mhz
Adapter iUVDClock: 0
Adapter iUVDPerformanceLevel: 0
Adapter iVCEClock: 0
Adapter iVCEPerformanceLevel: 0
Adapter iVDDC: 750 v
Adapter iVDDCI: 0 A

Active Adapter:
Adapter Index: 20
UDID: PCI_VEN_1002&DEV_6863&SUBSYS_6B761002&REV_00_6&6534E71&0&000000D8A
Location: PCI bus 6, device 0, function 0
VendorID: 1002
Adapter Name: Radeon Vega Frontier Edition
Display Name:
Present: no
Primary: no
Active: no
Adapter Id: -1238029504

Adapter temp: 30 C
Adapter fan: 4922 RPM
Adapter iCoreClock: 26 Mhz
Adapter iCurrentBusLanes: 16
Adapter iCurrentBusSpeed: 8000
Adapter iCurrentCorePerformanceLevel: 0
Adapter iCurrentDCEFPerformanceLevel: 0
Adapter iCurrentGFXPerformanceLevel: 0
Adapter iCurrentMemoryPerformanceLevel: 0
Adapter iDCEFClock: 0
Adapter iGFXClock: 0
Adapter iGPUActivityPercent: 0
Adapter iMaximumBusLanes: 16
Adapter iMemoryClock: 167 Mhz
Adapter iUVDClock: 0
Adapter iUVDPerformanceLevel: 0
Adapter iVCEClock: 0
Adapter iVCEPerformanceLevel: 0
Adapter iVDDC: 750 v
Adapter iVDDCI: 0 A

Active Adapter:
Adapter Index: 12
UDID: PCI_VEN_1002&DEV_6863&SUBSYS_6B761002&REV_00_6&345659DD&0&000000DDA
Location: PCI bus 9, device 0, function 0
VendorID: 1002
Adapter Name: Radeon Vega Frontier Edition
Display Name:
Present: no
Primary: no
Active: no
Adapter Id: -1402318784

Adapter temp: 30 C
Adapter fan: 4921 RPM
Adapter iCoreClock: 26 Mhz
Adapter iCurrentBusLanes: 16
Adapter iCurrentBusSpeed: 8000
Adapter iCurrentCorePerformanceLevel: 0
Adapter iCurrentDCEFPerformanceLevel: 0
Adapter iCurrentGFXPerformanceLevel: 0
Adapter iCurrentMemoryPerformanceLevel: 0
Adapter iDCEFClock: 0
Adapter iGFXClock: 0
Adapter iGPUActivityPercent: 0
Adapter iMaximumBusLanes: 16
Adapter iMemoryClock: 167 Mhz
Adapter iUVDClock: 0
Adapter iUVDPerformanceLevel: 0
Adapter iVCEClock: 0
Adapter iVCEPerformanceLevel: 0
Adapter iVDDC: 750 v
Adapter iVDDCI: 0 A

Active Adapter:
Adapter Index: 22
UDID: PCI_VEN_1002&DEV_6863&SUBSYS_6B761002&REV_00_8&351F250A&0&0000000800DEA
Location: PCI bus 14, device 0, function 0
VendorID: 1002
Adapter Name: Radeon Vega Frontier Edition
Display Name:
Present: no
Primary: no
Active: no
Adapter Id: -1508577216

Adapter temp: 31 C
Adapter fan: 4861 RPM
Adapter iCoreClock: 26 Mhz
Adapter iCurrentBusLanes: 16
Adapter iCurrentBusSpeed: 8000
Adapter iCurrentCorePerformanceLevel: 0
Adapter iCurrentDCEFPerformanceLevel: 0
Adapter iCurrentGFXPerformanceLevel: 0
Adapter iCurrentMemoryPerformanceLevel: 0
Adapter iDCEFClock: 0
Adapter iGFXClock: 0
Adapter iGPUActivityPercent: 0
Adapter iMaximumBusLanes: 16
Adapter iMemoryClock: 167 Mhz
Adapter iUVDClock: 0
Adapter iUVDPerformanceLevel: 0
Adapter iVCEClock: 0
Adapter iVCEPerformanceLevel: 0
Adapter iVDDC: 750 v
Adapter iVDDCI: 0 A

Active Adapter:
Adapter Index: 4
UDID: PCI_VEN_1002&DEV_6863&SUBSYS_6B761002&REV_00_6&19CE544B&0&000000DFA
Location: PCI bus 23, device 0, function 0
VendorID: 1002
Adapter Name: Radeon Vega Frontier Edition
Display Name:
Present: no
Primary: no
Active: no
Adapter Id: -1469060672

Adapter temp: 30 C
Adapter fan: 4684 RPM
Adapter iCoreClock: 26 Mhz
Adapter iCurrentBusLanes: 16
Adapter iCurrentBusSpeed: 8000
Adapter iCurrentCorePerformanceLevel: 0
Adapter iCurrentDCEFPerformanceLevel: 0
Adapter iCurrentGFXPerformanceLevel: 0
Adapter iCurrentMemoryPerformanceLevel: 0
Adapter iDCEFClock: 0
Adapter iGFXClock: 0
Adapter iGPUActivityPercent: 0
Adapter iMaximumBusLanes: 16
Adapter iMemoryClock: 167 Mhz
Adapter iUVDClock: 0
Adapter iUVDPerformanceLevel: 0
Adapter iVCEClock: 0
Adapter iVCEPerformanceLevel: 0
Adapter iVDDC: 750 v
Adapter iVDDCI: 0 A

Active Adapter:
Adapter Index: 0
UDID: PCI_VEN_1002&DEV_6863&SUBSYS_6B761002&REV_00_6&12F6D60B&0&000000E0A
Location: PCI bus 26, device 0, function 0
VendorID: 1002
Adapter Name: Radeon Vega Frontier Edition
Display Name:
Present: no
Primary: no
Active: no
Adapter Id: -405167680

Adapter temp: 29 C
Adapter fan: 4812 RPM
Adapter iCoreClock: 26 Mhz
Adapter iCurrentBusLanes: 16
Adapter iCurrentBusSpeed: 8000
Adapter iCurrentCorePerformanceLevel: 0
Adapter iCurrentDCEFPerformanceLevel: 0
Adapter iCurrentGFXPerformanceLevel: 0
Adapter iCurrentMemoryPerformanceLevel: 0
Adapter iDCEFClock: 0
Adapter iGFXClock: 0
Adapter iGPUActivityPercent: 0
Adapter iMaximumBusLanes: 16
Adapter iMemoryClock: 167 Mhz
Adapter iUVDClock: 0
Adapter iUVDPerformanceLevel: 0
Adapter iVCEClock: 0
Adapter iVCEPerformanceLevel: 0
Adapter iVDDC: 750 v
Adapter iVDDCI: 0 A

Active Adapter:
Adapter Index: 18
UDID: PCI_VEN_1002&DEV_6863&SUBSYS_6B761002&REV_00_6&3B281BE3&0&000000E5A
Location: PCI bus 29, device 0, function 0
VendorID: 1002
Adapter Name: Radeon Vega Frontier Edition
Display Name:
Present: no
Primary: no
Active: no
Adapter Id: -1449542208

Adapter temp: 31 C
Adapter fan: 4805 RPM
Adapter iCoreClock: 26 Mhz
Adapter iCurrentBusLanes: 16
Adapter iCurrentBusSpeed: 8000
Adapter iCurrentCorePerformanceLevel: 0
Adapter iCurrentDCEFPerformanceLevel: 0
Adapter iCurrentGFXPerformanceLevel: 0
Adapter iCurrentMemoryPerformanceLevel: 0
Adapter iDCEFClock: 0
Adapter iGFXClock: 0
Adapter iGPUActivityPercent: 0
Adapter iMaximumBusLanes: 16
Adapter iMemoryClock: 167 Mhz
Adapter iUVDClock: 0
Adapter iUVDPerformanceLevel: 0
Adapter iVCEClock: 0
Adapter iVCEPerformanceLevel: 0
Adapter iVDDC: 750 v
Adapter iVDDCI: 0 A

Active Adapter:
Adapter Index: 14
UDID: PCI_VEN_1002&DEV_6863&SUBSYS_6B761002&REV_00_6&34803EF3&0&000000E7A
Location: PCI bus 32, device 0, function 0
VendorID: 1002
Adapter Name: Radeon Vega Frontier Edition
Display Name:
Present: no
Primary: no
Active: no
Adapter Id: -1508644096

Adapter temp: 30 C
Adapter fan: 4896 RPM
Adapter iCoreClock: 26 Mhz
Adapter iCurrentBusLanes: 16
Adapter iCurrentBusSpeed: 8000
Adapter iCurrentCorePerformanceLevel: 0
Adapter iCurrentDCEFPerformanceLevel: 0
Adapter iCurrentGFXPerformanceLevel: 0
Adapter iCurrentMemoryPerformanceLevel: 0
Adapter iDCEFClock: 0
Adapter iGFXClock: 0
Adapter iGPUActivityPercent: 0
Adapter iMaximumBusLanes: 16
Adapter iMemoryClock: 167 Mhz
Adapter iUVDClock: 0
Adapter iUVDPerformanceLevel: 0
Adapter iVCEClock: 0
Adapter iVCEPerformanceLevel: 0
Adapter iVDDC: 750 v
Adapter iVDDCI: 0 A

Active Adapter:
Adapter Index: 8
UDID: PCI_VEN_1002&DEV_6863&SUBSYS_6B761002&REV_00_6&297395EA&0&000000E8A
Location: PCI bus 35, device 0, function 0
VendorID: 1002
Adapter Name: Radeon Vega Frontier Edition
Display Name:
Present: no
Primary: no
Active: no
Adapter Id: -1500253888

Adapter temp: 30 C
Adapter fan: 4718 RPM
Adapter iCoreClock: 26 Mhz
Adapter iCurrentBusLanes: 16
Adapter iCurrentBusSpeed: 8000
Adapter iCurrentCorePerformanceLevel: 0
Adapter iCurrentDCEFPerformanceLevel: 0
Adapter iCurrentGFXPerformanceLevel: 0
Adapter iCurrentMemoryPerformanceLevel: 0
Adapter iDCEFClock: 0
Adapter iGFXClock: 0
Adapter iGPUActivityPercent: 0
Adapter iMaximumBusLanes: 16
Adapter iMemoryClock: 167 Mhz
Adapter iUVDClock: 0
Adapter iUVDPerformanceLevel: 0
Adapter iVCEClock: 0
Adapter iVCEPerformanceLevel: 0
Adapter iVDDC: 750 v
Adapter iVDDCI: 0 A

Active Adapter:
Adapter Index: 10
UDID: PCI_VEN_1002&DEV_6863&SUBSYS_6B761002&REV_00_6&2CDD8055&0&000000E9A
Location: PCI bus 38, device 0, function 0
VendorID: 1002
Adapter Name: Radeon Vega Frontier Edition
Display Name:
Present: no
Primary: no
Active: no
Adapter Id: -1514598976

Adapter temp: 34 C
Adapter fan: 4829 RPM
Adapter iCoreClock: 26 Mhz
Adapter iCurrentBusLanes: 16
Adapter iCurrentBusSpeed: 8000
Adapter iCurrentCorePerformanceLevel: 0
Adapter iCurrentDCEFPerformanceLevel: 0
Adapter iCurrentGFXPerformanceLevel: 0
Adapter iCurrentMemoryPerformanceLevel: 0
Adapter iDCEFClock: 0
Adapter iGFXClock: 0
Adapter iGPUActivityPercent: 0
Adapter iMaximumBusLanes: 16
Adapter iMemoryClock: 167 Mhz
Adapter iUVDClock: 0
Adapter iUVDPerformanceLevel: 0
Adapter iVCEClock: 0
Adapter iVCEPerformanceLevel: 0
Adapter iVDDC: 750 v
Adapter iVDDCI: 0 A

Active Adapter:
Adapter Index: 6
UDID: PCI_VEN_1002&DEV_6863&SUBSYS_6B761002&REV_00_6&22DA2C61&0&000000EAA
Location: PCI bus 41, device 0, function 0
VendorID: 1002
Adapter Name: Radeon Vega Frontier Edition
Display Name:
Present: no
Primary: no
Active: no
Adapter Id: -1326142912

Adapter temp: 31 C
Adapter fan: 4922 RPM
Adapter iCoreClock: 26 Mhz
Adapter iCurrentBusLanes: 16
Adapter iCurrentBusSpeed: 8000
Adapter iCurrentCorePerformanceLevel: 0
Adapter iCurrentDCEFPerformanceLevel: 0
Adapter iCurrentGFXPerformanceLevel: 0
Adapter iCurrentMemoryPerformanceLevel: 0
Adapter iDCEFClock: 0
Adapter iGFXClock: 0
Adapter iGPUActivityPercent: 0
Adapter iMaximumBusLanes: 16
Adapter iMemoryClock: 167 Mhz
Adapter iUVDClock: 0
Adapter iUVDPerformanceLevel: 0
Adapter iVCEClock: 0
Adapter iVCEPerformanceLevel: 0
Adapter iVDDC: 750 v
Adapter iVDDCI: 0 A

Active Adapter:
Adapter Index: 16
UDID: PCI_VEN_1002&DEV_6863&SUBSYS_6B761002&REV_00_6&3B05FDCF&0&000000EBA
Location: PCI bus 44, device 0, function 0
VendorID: 1002
Adapter Name: Radeon Vega Frontier Edition
Display Name:
Present: no
Primary: no
Active: no
Adapter Id: -317463104

Adapter temp: 32 C
Adapter fan: 4790 RPM
Adapter iCoreClock: 26 Mhz
Adapter iCurrentBusLanes: 16
Adapter iCurrentBusSpeed: 8000
Adapter iCurrentCorePerformanceLevel: 0
Adapter iCurrentDCEFPerformanceLevel: 0
Adapter iCurrentGFXPerformanceLevel: 0
Adapter iCurrentMemoryPerformanceLevel: 0
Adapter iDCEFClock: 0
Adapter iGFXClock: 0
Adapter iGPUActivityPercent: 0
Adapter iMaximumBusLanes: 16
Adapter iMemoryClock: 167 Mhz
Adapter iUVDClock: 0
Adapter iUVDPerformanceLevel: 0
Adapter iVCEClock: 0
Adapter iVCEPerformanceLevel: 0
Adapter iVDDC: 750 v
Adapter iVDDCI: 0 A

init...is OK!
Found platforms: 2

Id: 0
Vendor: Intel(R) Corporation
Version: OpenCL 2.1
Name: Intel(R) OpenCL
Profile: FULL_PROFILE
Id: 1
Vendor: Advanced Micro Devices, Inc.
Version: OpenCL 2.1 AMD-APP (2580.6)
Name: AMD Accelerated Parallel Processing
Profile: FULL_PROFILE
Found gpu devices: 12 this platform
BUS ID 3
CL_DEVICE_GLOBAL_MEM_CACHE_SIZE 16384
CL_DEVICE_GLOBAL_MEM_SIZE 17163091968
CL_DEVICE_LOCAL_MEM_SIZE 32768
CL_DEVICE_MAX_MEM_ALLOC_SIZE 16894656512
CL_DEVICE_MAX_COMPUTE_UNITS 64
CL_DEVICE_MAX_WORK_GROUP_SIZE 64
CL_DEVICE_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
Init device: #0
Device: gfx900
Building or load programm...
Use intensity: 1984
No binary found, generating from source

Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 0, worker 0
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 0, worker 1
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Init device complete!
BUS ID 6
CL_DEVICE_GLOBAL_MEM_CACHE_SIZE 16384
CL_DEVICE_GLOBAL_MEM_SIZE 17163091968
CL_DEVICE_LOCAL_MEM_SIZE 32768
CL_DEVICE_MAX_MEM_ALLOC_SIZE 16894656512
CL_DEVICE_MAX_COMPUTE_UNITS 64
CL_DEVICE_MAX_WORK_GROUP_SIZE 64
CL_DEVICE_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
Init device: #1
Device: gfx900
Building or load programm...
Use intensity: 1984
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 1, worker 0
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 1, worker 1
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Init device complete!
BUS ID 9
CL_DEVICE_GLOBAL_MEM_CACHE_SIZE 16384
CL_DEVICE_GLOBAL_MEM_SIZE 17163091968
CL_DEVICE_LOCAL_MEM_SIZE 32768
CL_DEVICE_MAX_MEM_ALLOC_SIZE 16894656512
CL_DEVICE_MAX_COMPUTE_UNITS 64
CL_DEVICE_MAX_WORK_GROUP_SIZE 64
CL_DEVICE_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
Init device: #2
Device: gfx900
Building or load programm...
Use intensity: 1984
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 2, worker 0
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 2, worker 1
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Init device complete!
BUS ID 14
CL_DEVICE_GLOBAL_MEM_CACHE_SIZE 16384
CL_DEVICE_GLOBAL_MEM_SIZE 17163091968
CL_DEVICE_LOCAL_MEM_SIZE 32768
CL_DEVICE_MAX_MEM_ALLOC_SIZE 16894656512
CL_DEVICE_MAX_COMPUTE_UNITS 64
CL_DEVICE_MAX_WORK_GROUP_SIZE 64
CL_DEVICE_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
Init device: #3
Device: gfx900
Building or load programm...
Use intensity: 1984
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 3, worker 0
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 3, worker 1
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Init device complete!
BUS ID 23
CL_DEVICE_GLOBAL_MEM_CACHE_SIZE 16384
CL_DEVICE_GLOBAL_MEM_SIZE 17163091968
CL_DEVICE_LOCAL_MEM_SIZE 32768
CL_DEVICE_MAX_MEM_ALLOC_SIZE 16894656512
CL_DEVICE_MAX_COMPUTE_UNITS 64
CL_DEVICE_MAX_WORK_GROUP_SIZE 64
CL_DEVICE_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
Init device: #4
Device: gfx900
Building or load programm...
Use intensity: 1984
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 4, worker 0
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 4, worker 1
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Init device complete!
BUS ID 26
CL_DEVICE_GLOBAL_MEM_CACHE_SIZE 16384
CL_DEVICE_GLOBAL_MEM_SIZE 17163091968
CL_DEVICE_LOCAL_MEM_SIZE 32768
CL_DEVICE_MAX_MEM_ALLOC_SIZE 16894656512
CL_DEVICE_MAX_COMPUTE_UNITS 64
CL_DEVICE_MAX_WORK_GROUP_SIZE 64
CL_DEVICE_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
Init device: #5
Device: gfx900
Building or load programm...
Use intensity: 1984
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 5, worker 0
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 5, worker 1
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Init device complete!
BUS ID 29
CL_DEVICE_GLOBAL_MEM_CACHE_SIZE 16384
CL_DEVICE_GLOBAL_MEM_SIZE 17163091968
CL_DEVICE_LOCAL_MEM_SIZE 32768
CL_DEVICE_MAX_MEM_ALLOC_SIZE 16894656512
CL_DEVICE_MAX_COMPUTE_UNITS 64
CL_DEVICE_MAX_WORK_GROUP_SIZE 64
CL_DEVICE_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
Init device: #6
Device: gfx900
Building or load programm...
Use intensity: 1984
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 6, worker 0
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 6, worker 1
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Init device complete!
BUS ID 32
CL_DEVICE_GLOBAL_MEM_CACHE_SIZE 16384
CL_DEVICE_GLOBAL_MEM_SIZE 17163091968
CL_DEVICE_LOCAL_MEM_SIZE 32768
CL_DEVICE_MAX_MEM_ALLOC_SIZE 16894656512
CL_DEVICE_MAX_COMPUTE_UNITS 64
CL_DEVICE_MAX_WORK_GROUP_SIZE 64
CL_DEVICE_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
Init device: #7
Device: gfx900
Building or load programm...
Use intensity: 1984
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 7, worker 0
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 7, worker 1
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Init device complete!
BUS ID 35
CL_DEVICE_GLOBAL_MEM_CACHE_SIZE 16384
CL_DEVICE_GLOBAL_MEM_SIZE 17163091968
CL_DEVICE_LOCAL_MEM_SIZE 32768
CL_DEVICE_MAX_MEM_ALLOC_SIZE 16894656512
CL_DEVICE_MAX_COMPUTE_UNITS 64
CL_DEVICE_MAX_WORK_GROUP_SIZE 64
CL_DEVICE_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
Init device: #8
Device: gfx900
Building or load programm...
Use intensity: 1984
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 8, worker 0
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 8, worker 1
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Init device complete!
BUS ID 38
CL_DEVICE_GLOBAL_MEM_CACHE_SIZE 16384
CL_DEVICE_GLOBAL_MEM_SIZE 17163091968
CL_DEVICE_LOCAL_MEM_SIZE 32768
CL_DEVICE_MAX_MEM_ALLOC_SIZE 16894656512
CL_DEVICE_MAX_COMPUTE_UNITS 64
CL_DEVICE_MAX_WORK_GROUP_SIZE 64
CL_DEVICE_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
Init device: #9
Device: gfx900
Building or load programm...
Use intensity: 1984
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 9, worker 0
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 9, worker 1
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Init device complete!
BUS ID 41
CL_DEVICE_GLOBAL_MEM_CACHE_SIZE 16384
CL_DEVICE_GLOBAL_MEM_SIZE 17163091968
CL_DEVICE_LOCAL_MEM_SIZE 32768
CL_DEVICE_MAX_MEM_ALLOC_SIZE 16894656512
CL_DEVICE_MAX_COMPUTE_UNITS 64
CL_DEVICE_MAX_WORK_GROUP_SIZE 64
CL_DEVICE_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
Init device: #10
Device: gfx900
Building or load programm...
Use intensity: 1984
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 10, worker 0
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 10, worker 1
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Init device complete!
BUS ID 44
CL_DEVICE_GLOBAL_MEM_CACHE_SIZE 16384
CL_DEVICE_GLOBAL_MEM_SIZE 17163091968
CL_DEVICE_LOCAL_MEM_SIZE 32768
CL_DEVICE_MAX_MEM_ALLOC_SIZE 16894656512
CL_DEVICE_MAX_COMPUTE_UNITS 64
CL_DEVICE_MAX_WORK_GROUP_SIZE 64
CL_DEVICE_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
Init device: #11
Device: gfx900
Building or load programm...
Use intensity: 1984
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 11, worker 0
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Loaded binary image ... gfx900_int1984_ws8_haven.bin
...is Ok!
set worker algo: 9, device: 11, worker 1
Buffer sizes: 0 RW, 128 R
Using read buffer sized 128
Using output buffer sized 1024
Init device complete!



Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: marcrblevins on November 12, 2018, 12:24:18 AM
Where is the support to talk to the developer for the BXB Miner project?


Title: Re: BXB-Miner Cryptonight AMD GPU/CPU
Post by: helipotte on December 11, 2018, 04:40:27 PM
Great miner! Nice replacement for SGminer.  Does this use the same API backend as SGminer?  What port is default?