[burstcoin-jminer-0.5.3-SNAPSHOT]
Download:
https://github.com/de-luxe/burstcoin-jminer/releases
Updates:
- #72 jminer crashes if a plot file is actively being plotted
- #73 listPlotFiles=true does not always show list
- improved re-start round after wallet fork handling
- prevent concurrent modification while creating real capacity lookup
- ensure lowestCommitted does not get updated with higher committed deadline due to bad timing
- removed obsolete properties triggerServer, recommitDeadlines, poc2ActivationBlockHeight
- some code cleanup and update to latest libs
Topic: [ANN] jminer v0.5.3 - GPU assisted PoC-Miner for Burstcoin (BURST) - PoC2 (Read 23320 times)
July 19, 2018, 09:22:16 AM
May 30, 2018, 03:15:57 PM
[burstcoin-jminer-0.5.2-RELEASE]
Download:
https://github.com/de-luxe/burstcoin-jminer/releases
Notice:
Supports both, POC1 and POC2 plotfiles. This will also be the case after the fork.
However, to handle POC2 pre-fork and POC1 post-fork, twice the amount of data needs to be read and also more CPU and memory resources will be used.
The best case for a miner would be, to have converted up to 50% of plotfiles once the fork happens. That would cause the mining setup to behave exactly the same pre and post fork.
- Only use one type, POC1 or POC2 on one drive ('plotPath'), mixed will be skipped.
- Ensure your POC2 plotfiles do not have staggersize in filename , or they will be treated like POC1.
Download:
https://github.com/de-luxe/burstcoin-jminer/releases
Notice:
Supports both, POC1 and POC2 plotfiles. This will also be the case after the fork.
However, to handle POC2 pre-fork and POC1 post-fork, twice the amount of data needs to be read and also more CPU and memory resources will be used.
The best case for a miner would be, to have converted up to 50% of plotfiles once the fork happens. That would cause the mining setup to behave exactly the same pre and post fork.
- Only use one type, POC1 or POC2 on one drive ('plotPath'), mixed will be skipped.
- Ensure your POC2 plotfiles do not have staggersize in filename , or they will be treated like POC1.
May 25, 2018, 04:22:27 PM
[burstcoin-jminer-0.5.1-SNAPSHOT]
Download:
https://github.com/de-luxe/burstcoin-jminer/releases
Notice:
burstcoin-jminer-0.5.x supports both, POC1 and POC2 plotfiles. This will also be the case after the fork.
However, to handle POC2 pre-fork and POC1 post-fork, twice the amount of data needs to be read and also more CPU and memory resources will be used.
The best case for a miner would be, to have converted up to 50% of plotfiles once the fork happens. That would cause the mining setup to behave exactly the same pre and post fork.
- Only use one type, POC1 or POC2 on one drive ('plotPath'), mixed will be skipped.
- Ensure your POC2 plotfiles do not have staggersize in filename , or they will be treated like POC1.
- Read speed is calculated by plotsize, so if jminer reads twice the data on e.g. POC2 pre-fork, the numbers displayed will not be accurate.
Download:
https://github.com/de-luxe/burstcoin-jminer/releases
Notice:
burstcoin-jminer-0.5.x supports both, POC1 and POC2 plotfiles. This will also be the case after the fork.
However, to handle POC2 pre-fork and POC1 post-fork, twice the amount of data needs to be read and also more CPU and memory resources will be used.
The best case for a miner would be, to have converted up to 50% of plotfiles once the fork happens. That would cause the mining setup to behave exactly the same pre and post fork.
- Only use one type, POC1 or POC2 on one drive ('plotPath'), mixed will be skipped.
- Ensure your POC2 plotfiles do not have staggersize in filename , or they will be treated like POC1.
- Read speed is calculated by plotsize, so if jminer reads twice the data on e.g. POC2 pre-fork, the numbers displayed will not be accurate.
January 28, 2017, 04:01:47 AM
@morantis
Sorry if the included jminer.properties leads to this confusion .... i updated OP and added a link to the github wiki page.
As far as i can see you did everything correctly ...
But to clarify ... nearly all settings have a implemented default value, so there is no need to configure more than you did.
The walletServer is only used to get the last winner and not relevant for mining at all.
There are some 'hidden' features and fine tuning, it is all described here: https://github.com/de-luxe/burstcoin-jminer/wiki/configure-jminer.properties
Just want to mention 'showDriveInfo=true' to see how your single drives perform, may help to optimize your setup.
Or 'listPlotFiles=true' (again requires a walletServer) Will list all your plotfiles on startup and show how many blocks they won etc.
So nice to see your interest, play arround and ask if something is not clear ...
This thread was not very active due to the fact that burst has a very active forum, and most ask questions there (https://forums.burst-team.us).
Sorry if the included jminer.properties leads to this confusion .... i updated OP and added a link to the github wiki page.
As far as i can see you did everything correctly ...
But to clarify ... nearly all settings have a implemented default value, so there is no need to configure more than you did.
The walletServer is only used to get the last winner and not relevant for mining at all.
There are some 'hidden' features and fine tuning, it is all described here: https://github.com/de-luxe/burstcoin-jminer/wiki/configure-jminer.properties
Just want to mention 'showDriveInfo=true' to see how your single drives perform, may help to optimize your setup.
Or 'listPlotFiles=true' (again requires a walletServer) Will list all your plotfiles on startup and show how many blocks they won etc.
So nice to see your interest, play arround and ask if something is not clear ...
This thread was not very active due to the fact that burst has a very active forum, and most ask questions there (https://forums.burst-team.us).
it is very possible that it was my screen resolution combined with the word wrap, but literally the "example" of each parameter fell directly on the next line and character 1, appearing to a coder like me as a line of code outside of a comment block, lol. that is what led to most of my confusion was not realizing that lines were part of the preceding line as a remark
so what i saw was something like this
Code:
//you can use the message method to include a private message, this is set later in this code, nearly 40 lines later, lol
message='why did these words wrap at EXACTLY the wrong space break'
.....and much later
//here is the setting of the message method as spoke about before
message='and here i am AGAIN, i imagine, since it is Java that this is the one going to the Jar, as it is the last one in the code block, but feel free to set the variable as many times as you like, lol'
//end code block that my pc got a kick out of formatting is the PERFECT way to confuse
message='why did these words wrap at EXACTLY the wrong space break'
.....and much later
//here is the setting of the message method as spoke about before
message='and here i am AGAIN, i imagine, since it is Java that this is the one going to the Jar, as it is the last one in the code block, but feel free to set the variable as many times as you like, lol'
//end code block that my pc got a kick out of formatting is the PERFECT way to confuse
I understand ... i will think about how to improve that ....
I was using notepad++ or comparable to edit jminer.properties and therefore i did not see, that this may be a issue.
For me it looks like this ...
January 28, 2017, 01:55:28 AM
@morantis
Sorry if the included jminer.properties leads to this confusion .... i updated OP and added a link to the github wiki page.
As far as i can see you did everything correctly ...
But to clarify ... nearly all settings have a implemented default value, so there is no need to configure more than you did.
The walletServer is only used to get the last winner and not relevant for mining at all.
There are some 'hidden' features and fine tuning, it is all described here: https://github.com/de-luxe/burstcoin-jminer/wiki/configure-jminer.properties
Just want to mention 'showDriveInfo=true' to see how your single drives perform, may help to optimize your setup.
Or 'listPlotFiles=true' (again requires a walletServer) Will list all your plotfiles on startup and show how many blocks they won etc.
So nice to see your interest, play arround and ask if something is not clear ...
This thread was not very active due to the fact that burst has a very active forum, and most ask questions there (https://forums.burst-team.us).
Sorry if the included jminer.properties leads to this confusion .... i updated OP and added a link to the github wiki page.
As far as i can see you did everything correctly ...
But to clarify ... nearly all settings have a implemented default value, so there is no need to configure more than you did.
The walletServer is only used to get the last winner and not relevant for mining at all.
There are some 'hidden' features and fine tuning, it is all described here: https://github.com/de-luxe/burstcoin-jminer/wiki/configure-jminer.properties
Just want to mention 'showDriveInfo=true' to see how your single drives perform, may help to optimize your setup.
Or 'listPlotFiles=true' (again requires a walletServer) Will list all your plotfiles on startup and show how many blocks they won etc.
So nice to see your interest, play arround and ask if something is not clear ...
This thread was not very active due to the fact that burst has a very active forum, and most ask questions there (https://forums.burst-team.us).
it is very possible that it was my screen resolution combined with the word wrap, but literally the "example" of each parameter fell directly on the next line and character 1, appearing to a coder like me as a line of code outside of a comment block, lol. that is what led to most of my confusion was not realizing that lines were part of the preceding line as a remark
so what i saw was something like this
Code:
//you can use the message method to include a private message, this is set later in this code, nearly 40 lines later, lol
message='why did these words wrap at EXACTLY the wrong space break'
.....and much later
//here is the setting of the message method as spoke about before
message='and here i am AGAIN, i imagine, since it is Java that this is the one going to the Jar, as it is the last one in the code block, but feel free to set the variable as many times as you like, lol'
//end code block that my pc got a kick out of formatting is the PERFECT way to confuse
message='why did these words wrap at EXACTLY the wrong space break'
.....and much later
//here is the setting of the message method as spoke about before
message='and here i am AGAIN, i imagine, since it is Java that this is the one going to the Jar, as it is the last one in the code block, but feel free to set the variable as many times as you like, lol'
//end code block that my pc got a kick out of formatting is the PERFECT way to confuse
January 27, 2017, 01:45:03 PM
@morantis
Sorry if the included jminer.properties leads to this confusion .... i updated OP and added a link to the github wiki page.
As far as i can see you did everything correctly ...
But to clarify ... nearly all settings have a implemented default value, so there is no need to configure more than you did.
The walletServer is only used to get the last winner and not relevant for mining at all.
There are some 'hidden' features and fine tuning, it is all described here: https://github.com/de-luxe/burstcoin-jminer/wiki/configure-jminer.properties
Just want to mention 'showDriveInfo=true' to see how your single drives perform, may help to optimize your setup.
Or 'listPlotFiles=true' (again requires a walletServer) Will list all your plotfiles on startup and show how many blocks they won etc.
So nice to see your interest, play arround and ask if something is not clear ...
This thread was not very active due to the fact that burst has a very active forum, and most ask questions there (https://forums.burst-team.us).
Sorry if the included jminer.properties leads to this confusion .... i updated OP and added a link to the github wiki page.
As far as i can see you did everything correctly ...
But to clarify ... nearly all settings have a implemented default value, so there is no need to configure more than you did.
The walletServer is only used to get the last winner and not relevant for mining at all.
There are some 'hidden' features and fine tuning, it is all described here: https://github.com/de-luxe/burstcoin-jminer/wiki/configure-jminer.properties
Just want to mention 'showDriveInfo=true' to see how your single drives perform, may help to optimize your setup.
Or 'listPlotFiles=true' (again requires a walletServer) Will list all your plotfiles on startup and show how many blocks they won etc.
So nice to see your interest, play arround and ask if something is not clear ...
This thread was not very active due to the fact that burst has a very active forum, and most ask questions there (https://forums.burst-team.us).
January 27, 2017, 08:17:10 AM
ok, pretty significant difference. i use s very simple conf file that i will tweak over time.
i will go through the original one line at a time and through the github help and see if i can use any other parameters to improve things. but it seems that the gpu miner jminer versus the other cpu miners i have used shows a good 50% or greater increase in production. it is hard to gauge exactly, as this is a new rig, building from the bottom up and i switched to the jminer at the same time that i nearly doubled the plot sizes. but, compared the the same rig that is already running and the time when it had the same amount of plots/sizes there is a big difference
Code:
plotPaths=D:/Burst/plots,C:/Burst/plots,E:/Burst/plots
numericAccountId=xxxxxxx
poolServer=http://pool.burstcoin.uk:80
walletServer=https://wallet.burst-team.us:8125
numericAccountId=xxxxxxx
poolServer=http://pool.burstcoin.uk:80
walletServer=https://wallet.burst-team.us:8125
i will go through the original one line at a time and through the github help and see if i can use any other parameters to improve things. but it seems that the gpu miner jminer versus the other cpu miners i have used shows a good 50% or greater increase in production. it is hard to gauge exactly, as this is a new rig, building from the bottom up and i switched to the jminer at the same time that i nearly doubled the plot sizes. but, compared the the same rig that is already running and the time when it had the same amount of plots/sizes there is a big difference
January 26, 2017, 11:19:54 PM
until the block chain gets fully synced for me locally and on some other sites i will have no real answer here. I removed the parameters i added for a wallet server because the software claimed to not be able to get mining info. it now works, my dl info is displayed on the pool, but the software is pissed because the mining info is not being reported to it correctly.
once my local wallet is fully recovered from the mess over the past few days, i will point jminer at it for mining info. to test jminer i only used a drive that has 200 GB plotted on it and i am not impressed at the results versus the regular mining software. i saw a dl of a year, and another in the 9 month range. I am using the same pc to plot at this moment, so that could be an issue.
once i am locally snyced and i have stopped my current plotting, i will try it for an hour with all my plots and then use uray's for an hour with the same plots and report back here. it seems that the software can and will run with only the three parameters set, setting a walletserver via the config can do nothing but improve things.
once my local wallet is fully recovered from the mess over the past few days, i will point jminer at it for mining info. to test jminer i only used a drive that has 200 GB plotted on it and i am not impressed at the results versus the regular mining software. i saw a dl of a year, and another in the 9 month range. I am using the same pc to plot at this moment, so that could be an issue.
once i am locally snyced and i have stopped my current plotting, i will try it for an hour with all my plots and then use uray's for an hour with the same plots and report back here. it seems that the software can and will run with only the three parameters set, setting a walletserver via the config can do nothing but improve things.
January 26, 2017, 10:48:43 PM
i have a question. i just downloaded jminer for burst coin and the config file is huge. it looks like for pool mining there are only three variables that need to be set. the files reads really odd. there is an explanation for each parameter given in a comment. the way my line breaks are, it looks like the parameter is set right after the comment, but i think that is not the case, as i see the parameters more clearly used later in the file.
the question is this. if i only need to set three parameters in the file, are there other settings in there that are used. can i just make a new config file that contains nothing other than the three parameters and use it or is the included file more important. i know coding and i can read through the file line by line, but would rather avoid that and get it moving more quickly
edit:creating my own config file using this method. i started with these three parameters,
Then I started the script and got an info/error saying that a wallet server is not defined. I will set everything one at a time using the errors that the software spits out. I think this is a nice way of seeing each and every piece of info the software uses and better understanding the program. I will post a final config file that was created using this method here for the info of others.
the question is this. if i only need to set three parameters in the file, are there other settings in there that are used. can i just make a new config file that contains nothing other than the three parameters and use it or is the included file more important. i know coding and i can read through the file line by line, but would rather avoid that and get it moving more quickly
edit:creating my own config file using this method. i started with these three parameters,
Code:
plotPaths=D:/,C:/,E:/plots,F:/plots
numericAccountId=
poolServer=http://pool.com:port
numericAccountId=
poolServer=http://pool.com:port
Then I started the script and got an info/error saying that a wallet server is not defined. I will set everything one at a time using the errors that the software spits out. I think this is a nice way of seeing each and every piece of info the software uses and better understanding the program. I will post a final config file that was created using this method here for the info of others.
July 20, 2016, 03:05:02 PM
[New Wallet version 1.2.5]
burstcoin-1.2.5
Thread:
https://bitcointalksearch.org/topic/annburstpoc-burstcoin-hard-fork-coming-approximately-june-20th-1541310
Download:
https://github.com/burst-team/burstcoin/releases/tag/1.2.5
Sources:
https://github.com/burst-team/burstcoin
+ Bugs fixed
+ Added maven support
+ some minor changes/updates
Notice:
There are just 4 Days left until block 255000 ... update your wallets!
https://forums.burst-team.us/topic/767/howto-update-burstcoin-wallet-from-1-2-3-to-1-2-5
There are several things that could cause 1.2.3 users to fork off from correct fork after that!
1.2.3 wallets can stuck anytime if AT transaction happens, after block 255000!
Anyone on 1.2.3 past the fork point should re-sync when they upgrade!
burstcoin-1.2.5
Thread:
https://bitcointalksearch.org/topic/annburstpoc-burstcoin-hard-fork-coming-approximately-june-20th-1541310
Download:
https://github.com/burst-team/burstcoin/releases/tag/1.2.5
Sources:
https://github.com/burst-team/burstcoin
+ Bugs fixed
+ Added maven support
+ some minor changes/updates
Notice:
There are just 4 Days left until block 255000 ... update your wallets!
https://forums.burst-team.us/topic/767/howto-update-burstcoin-wallet-from-1-2-3-to-1-2-5
There are several things that could cause 1.2.3 users to fork off from correct fork after that!
1.2.3 wallets can stuck anytime if AT transaction happens, after block 255000!
Anyone on 1.2.3 past the fork point should re-sync when they upgrade!
July 06, 2016, 06:55:49 PM
Thank you for your great piece of software!
New Core Version of Burst is out!
https://bitcointalksearch.org/topic/annburstpoc-burstcoin-hard-fork-coming-approximately-june-20th-1541310
New Core Version of Burst is out!
https://bitcointalksearch.org/topic/annburstpoc-burstcoin-hard-fork-coming-approximately-june-20th-1541310
April 02, 2016, 11:18:38 AM
I tried for days and I can say that the newest version is very very stable. No memory leaks. I'm using it on Win10.
Great piece of software!
Great piece of software!
March 26, 2016, 09:39:35 AM
burstcoin-jminer-0.4.4-SNAPSHOT
Download
https://github.com/de-luxe/burstcoin-jminer/releases/tag/0.4.4-SNAPSHOT
Info
Writing logfile is now optional and disabled per default.
Added some additional openCL info/support for easy setup. e.g.:
Copied from logs:
Fixed smaller bugs and stuck issue while solo-mining
Added debug mode (will e.g. list incomplete plot-files)
Changes
- support all available openCL devices
- check for openCL support on startup, list available platforms/devices
- prevent wallet from stuck on solo-mining e.g. on slow blocks/no open gui
- writing logfile as optional feature
- stop using jocl 0.2.0 as long as there is no performance improvement
- provide info about 'incomplete' plot-files
- enable selection logLevel DEBUG for users that are interested in more details
Download
https://github.com/de-luxe/burstcoin-jminer/releases/tag/0.4.4-SNAPSHOT
Info
Writing logfile is now optional and disabled per default.
Added some additional openCL info/support for easy setup. e.g.:
Copied from logs:
Code:
List of system openCL platforms and devices (* = used for mining)
* PLATFORM-[0] AMD Accelerated Parallel Processing
OpenCL 2.0 AMD-APP (1642.5)
* DEVICE-[0] Tahiti (2GB) - Advanced Micro Devices, Inc.
OpenCL 1.2 AMD-APP (1642.5) | '1642.5 (VM)'
work group size '256', computing units '32', available 'true'
DEVICE-[1] Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz (17GB) - GenuineIntel
OpenCL 1.2 AMD-APP (1642.5) | '1642.5 (sse2,avx)'
work group size '1024', computing units '12', available 'true'
(*) openCL context successfully started! (platformId: 0, deviceId: 0)
Added debug mode (will e.g. list incomplete plot-files)
Changes
- support all available openCL devices
- check for openCL support on startup, list available platforms/devices
- prevent wallet from stuck on solo-mining e.g. on slow blocks/no open gui
- writing logfile as optional feature
- stop using jocl 0.2.0 as long as there is no performance improvement
- provide info about 'incomplete' plot-files
- enable selection logLevel DEBUG for users that are interested in more details
March 23, 2016, 02:56:37 PM
...
However, openCL does not necessarily has to run on GPU, there are also CPU drivers available.
...
However, openCL does not necessarily has to run on GPU, there are also CPU drivers available.
...
Just noticed, that jminer only 'allows' GPU openCL devices, kind of confused, cause i got feedback, that it also works on CPU ... however, next version will allow all available openCL devices.
March 17, 2016, 02:03:17 PM
How are use your miner in servers ? he has integrated video card Matrox G200eW and i do not find opencl driver or sdk for this card.
error in log miner:
Stack trace from the attempt to load the library as a resource:
java.lang.UnsatisfiedLinkError: Could not initialize native library. Implementation library 'OpenCL.dll' could not be loaded
2016-03-17 11:16:23.427 INFO 1808 --- [main] burstcoin.jminer.CommandLineRunner : Starting CommandLineRunner v0.4.3-SNAPSHOT on User-PC with PID 1808 (C:\burstcoin-jminer-0.4.3-SNAPSHOT\burstcoin-jminer-0.4.3-SNAPSHOT.jar started by User in C:\burstcoin-jminer-0.4.3-SNAPSHOT)
2016-03-17 11:16:23.461 INFO 1808 --- [main] burstcoin.jminer.CommandLineRunner : No active profile set, falling back to default profiles: default
2016-03-17 11:16:26.297 WARN 1808 --- [main] s.c.a.AnnotationConfigApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'OCLChecker': Invocation of init method failed; nested exception is org.jocl.CLException: CL_DEVICE_NOT_FOUND
2016-03-17 11:16:26.315 ERROR 1808 --- [main] o.s.boot.SpringApplication : Application startup failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'OCLChecker': Invocation of init method failed; nested exception is org.jocl.CLException: CL_DEVICE_NOT_FOUND
error in log miner:
Stack trace from the attempt to load the library as a resource:
java.lang.UnsatisfiedLinkError: Could not initialize native library. Implementation library 'OpenCL.dll' could not be loaded
2016-03-17 11:16:23.427 INFO 1808 --- [main] burstcoin.jminer.CommandLineRunner : Starting CommandLineRunner v0.4.3-SNAPSHOT on User-PC with PID 1808 (C:\burstcoin-jminer-0.4.3-SNAPSHOT\burstcoin-jminer-0.4.3-SNAPSHOT.jar started by User in C:\burstcoin-jminer-0.4.3-SNAPSHOT)
2016-03-17 11:16:23.461 INFO 1808 --- [main] burstcoin.jminer.CommandLineRunner : No active profile set, falling back to default profiles: default
2016-03-17 11:16:26.297 WARN 1808 --- [main] s.c.a.AnnotationConfigApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'OCLChecker': Invocation of init method failed; nested exception is org.jocl.CLException: CL_DEVICE_NOT_FOUND
2016-03-17 11:16:26.315 ERROR 1808 --- [main] o.s.boot.SpringApplication : Application startup failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'OCLChecker': Invocation of init method failed; nested exception is org.jocl.CLException: CL_DEVICE_NOT_FOUND
The main benefit of using jminer, is the use of openCL.
If your hardware does not support openCL, you should consider using another miner.
However, openCL does not necessarily has to run on GPU, there are also CPU drivers available.
Quote
The following implementations of OpenCL are currently available:
- The AMD OpenCL driver with support for OpenCL 2.0: AMD OpenCL website (http://support.amd.com/en-us/kb-articles/Pages/OpenCL2-Driver.aspx)
- The NVIDIA drivers with support for OpenCL 1.2: NVIDIA OpenCL website (http://developer.nvidia.com/opencl)
- OpenCL for OSX: Apple OpenCL website (https://developer.apple.com/opencl/)
- Intel OpenCL SDK: Intel OpenCL SDK website. (http://software.intel.com/en-us/articles/intel-opencl-sdk/) [see the Installation Notes (http://jocl.org/IntelInstallationNotes.txt) for using this implementation]
Source: http://jocl.org/
- The AMD OpenCL driver with support for OpenCL 2.0: AMD OpenCL website (http://support.amd.com/en-us/kb-articles/Pages/OpenCL2-Driver.aspx)
- The NVIDIA drivers with support for OpenCL 1.2: NVIDIA OpenCL website (http://developer.nvidia.com/opencl)
- OpenCL for OSX: Apple OpenCL website (https://developer.apple.com/opencl/)
- Intel OpenCL SDK: Intel OpenCL SDK website. (http://software.intel.com/en-us/articles/intel-opencl-sdk/) [see the Installation Notes (http://jocl.org/IntelInstallationNotes.txt) for using this implementation]
Source: http://jocl.org/
If its not a hardware, but a setup problem (setting correct device and platform) ... instructions can be found e.g. here (thanks cryo):
https://github.com/bhamon/gpuPlotGenerator/blob/master/README.md (check List platforms + List devices)
cutout from jminer.properties (https://github.com/de-luxe/burstcoin-jminer/blob/master/jminer.default.properties):
Code:
# -----------------------------------------------------------------------------------
# - GPU -----------------------------------------------------------------------------
# -----------------------------------------------------------------------------------
# the miner uses openCL for most of the mining calculations, ensure it is setup correctly.
# ...
#
# platformId - id of openCL platform on your system. one platform may have multiple
# (default:0) devices, the miner currently uses just one (in general not the bottleneck)
#
# deviceId - specifies the device used by OCLCecker, can be your first GPU,
# (default:0) in most cases it will not be 100% used. (depends on capacity)
# -----------------------------------------------------------------------------------
platformId=
deviceId=
Maybe there will be a alternative/fallback 'Checker' without openCL in the future, but thats is not implemented, yet.
March 17, 2016, 07:56:01 AM
How are use your miner in servers ? he has integrated video card Matrox G200eW and i do not find opencl driver or sdk for this card.
error in log miner:
Stack trace from the attempt to load the library as a resource:
java.lang.UnsatisfiedLinkError: Could not initialize native library. Implementation library 'OpenCL.dll' could not be loaded
2016-03-17 11:16:23.427 INFO 1808 --- [main] burstcoin.jminer.CommandLineRunner : Starting CommandLineRunner v0.4.3-SNAPSHOT on User-PC with PID 1808 (C:\burstcoin-jminer-0.4.3-SNAPSHOT\burstcoin-jminer-0.4.3-SNAPSHOT.jar started by User in C:\burstcoin-jminer-0.4.3-SNAPSHOT)
2016-03-17 11:16:23.461 INFO 1808 --- [main] burstcoin.jminer.CommandLineRunner : No active profile set, falling back to default profiles: default
2016-03-17 11:16:26.297 WARN 1808 --- [main] s.c.a.AnnotationConfigApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'OCLChecker': Invocation of init method failed; nested exception is org.jocl.CLException: CL_DEVICE_NOT_FOUND
2016-03-17 11:16:26.315 ERROR 1808 --- [main] o.s.boot.SpringApplication : Application startup failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'OCLChecker': Invocation of init method failed; nested exception is org.jocl.CLException: CL_DEVICE_NOT_FOUND
error in log miner:
Stack trace from the attempt to load the library as a resource:
java.lang.UnsatisfiedLinkError: Could not initialize native library. Implementation library 'OpenCL.dll' could not be loaded
2016-03-17 11:16:23.427 INFO 1808 --- [main] burstcoin.jminer.CommandLineRunner : Starting CommandLineRunner v0.4.3-SNAPSHOT on User-PC with PID 1808 (C:\burstcoin-jminer-0.4.3-SNAPSHOT\burstcoin-jminer-0.4.3-SNAPSHOT.jar started by User in C:\burstcoin-jminer-0.4.3-SNAPSHOT)
2016-03-17 11:16:23.461 INFO 1808 --- [main] burstcoin.jminer.CommandLineRunner : No active profile set, falling back to default profiles: default
2016-03-17 11:16:26.297 WARN 1808 --- [main] s.c.a.AnnotationConfigApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'OCLChecker': Invocation of init method failed; nested exception is org.jocl.CLException: CL_DEVICE_NOT_FOUND
2016-03-17 11:16:26.315 ERROR 1808 --- [main] o.s.boot.SpringApplication : Application startup failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'OCLChecker': Invocation of init method failed; nested exception is org.jocl.CLException: CL_DEVICE_NOT_FOUND
March 11, 2016, 06:50:55 PM
Works for me in win7 thanks
You are welcome ...
The miner works on Win7, but with more and more TB of plots, the memory Win7 uses for caching is increasing ... thats not the case on Linux/Win8+.
If you say it works for you, some more details like size of your plots and used memory would be helpful.
March 05, 2016, 12:34:22 AM
Works for me in win7 thanks
March 03, 2016, 05:11:19 PM
burstcoin-jminer-0.4.3-SNAPSHOT
Download:
https://github.com/de-luxe/burstcoin-jminer/releases/tag/0.4.3-SNAPSHOT
...
@equipoise you could try, if the lastest changes have positive effects on memory issues with Win7 ...
OK. Thank you. I'll test in a few days and I'll let you know.Download:
https://github.com/de-luxe/burstcoin-jminer/releases/tag/0.4.3-SNAPSHOT
...
@equipoise you could try, if the lastest changes have positive effects on memory issues with Win7 ...
Thanks, looking forward to that ... even i'm not very optimistic, there have been some big improvements in memory usage and maybe that changes something.
March 02, 2016, 06:39:45 PM
burstcoin-jminer-0.4.3-SNAPSHOT
Download:
https://github.com/de-luxe/burstcoin-jminer/releases/tag/0.4.3-SNAPSHOT
...
@equipoise you could try, if the lastest changes have positive effects on memory issues with Win7 ...
OK. Thank you. I'll test in a few days and I'll let you know.Download:
https://github.com/de-luxe/burstcoin-jminer/releases/tag/0.4.3-SNAPSHOT
...
@equipoise you could try, if the lastest changes have positive effects on memory issues with Win7 ...
Thanks, looking forward to that ... even i'm not very optimistic, there have been some big improvements in memory usage and maybe that changes something.
Jump to: