can i use this miner behind a http proxy?
Not currently. I use and ssh client to an external machine in order to bypass firewall and proxy. (putty can work over http proxies)
Topic: [ANN][MTC] GPU Miner for Metiscoin - 35% FASTER on R9 280x - page 2. (Read 6553 times)
Not currently. I use and ssh client to an external machine in order to bypass firewall and proxy. (putty can work over http proxies)
can i use this miner behind a http proxy?
Well, the difference between this version and gigawatt's version is how we manage the lookup tables. Depending on how your card organizes its memory, his version will be faster. You can try his version here: https://bitcointalksearch.org/topic/mtc-high-performance-gpu-miner-for-metiscoin-updated-19-feb-2014-452738
on my 7870 it shows around 1.5% more hash rates but no significant changes in shares found
the only big difference i noticed was around 20% decrease in power consumption !!!
wot ever u did, it is a great work girino
i am replacing all miners with yours in next few hours
Probably copying from constant memory to local memory spends less energy than copying from global to local. The only difference, as I said, is that I use constant memory instead of global for the lookup tables.
Well, the difference between this version and gigawatt's version is how we manage the lookup tables. Depending on how your card organizes its memory, his version will be faster. You can try his version here: https://bitcointalksearch.org/topic/mtc-high-performance-gpu-miner-for-metiscoin-updated-19-feb-2014-452738
on my 7870 it shows around 1.5% more hash rates but no significant changes in shares found
the only big difference i noticed was around 20% decrease in power consumption !!!
wot ever u did, it is a great work girino
i am replacing all miners with yours in next few hours
Im using R9 280X but im getting 12900 kash only? i need to upgrade any things???
Well, the difference between this version and gigawatt's version is how we manage the lookup tables. Depending on how your card organizes its memory, his version will be faster. You can try his version here: https://bitcointalksearch.org/topic/mtc-high-performance-gpu-miner-for-metiscoin-updated-19-feb-2014-452738
Im using R9 280X but im getting 12900 kash only? i need to upgrade any things???
great job! i get about 48000k@6xGV-N660OC-2GD GTX660 2G DDR5,win7x64.but unfortunately，it only work a few minutes，then the miner error and quit,the computer crashed.gigawatt'sbuild get the same result。
Can you capture the screen or not even that? Maybe a picture?
NEW RELEASE, FASTER THAN EVER.
Hi all,
I just released a new build of this miner with several improvements, thanks to gigawatt. My current version is slightly faster than his, but this might depend on the machine you're running it. (Mostly because i copy AES tables from __constant memory space and he copies it from __global).
The binaries for windows, osx and linux are still available on the same old place:
https://www.dropbox.com/sh/2wv2awwgebpdo0m/STzOU5tlXa
Please run and enjoy.
great job! i get about 48000k@6xGV-N660OC-2GD GTX660 2G DDR5,win7x64.but unfortunately，it only work a few minutes，then the miner error and quit,the computer crashed.gigawatt'sbuild get the same result。 Hi all,
I just released a new build of this miner with several improvements, thanks to gigawatt. My current version is slightly faster than his, but this might depend on the machine you're running it. (Mostly because i copy AES tables from __constant memory space and he copies it from __global).
The binaries for windows, osx and linux are still available on the same old place:
https://www.dropbox.com/sh/2wv2awwgebpdo0m/STzOU5tlXa
Please run and enjoy.
NEW RELEASE, FASTER THAN EVER.
Hi all,
I just released a new build of this miner with several improvements, thanks to gigawatt. My current version is slightly faster than his, but this might depend on the machine you're running it. (Mostly because i copy AES tables from __constant memory space and he copies it from __global).
The binaries for windows, osx and linux are still available on the same old place:
https://www.dropbox.com/sh/2wv2awwgebpdo0m/STzOU5tlXa
Please run and enjoy.
Hi all,
I just released a new build of this miner with several improvements, thanks to gigawatt. My current version is slightly faster than his, but this might depend on the machine you're running it. (Mostly because i copy AES tables from __constant memory space and he copies it from __global).
The binaries for windows, osx and linux are still available on the same old place:
https://www.dropbox.com/sh/2wv2awwgebpdo0m/STzOU5tlXa
Please run and enjoy.
Getting
I really don't have any idea what I'm doing. Was I supposed to add everything from the two folders together into 1 folder then run? Because that's pretty much all I did, and also edited example file for my pools info. Thats it tho.
Code:
ERROR: -1001, ,No valid ICDs found
assertion "_MY_ERR_X == CL_SUCCESS" failed: file "xptMiner/OpenCLObjects.cpp line 159, funntion: OpenCLMain::OpenCLMain<>
0 [main] xptminer 1876 open_stackdumpfile: dumping stack trace to xptminer.
assertion "_MY_ERR_X == CL_SUCCESS" failed: file "xptMiner/OpenCLObjects.cpp line 159, funntion: OpenCLMain::OpenCLMain<>
0 [main] xptminer 1876 open_stackdumpfile: dumping stack trace to xptminer.
I really don't have any idea what I'm doing. Was I supposed to add everything from the two folders together into 1 folder then run? Because that's pretty much all I did, and also edited example file for my pools info. Thats it tho.
Nope, you should not have messed with the folders! But the error does not seem to be that. Looks like it is unable to identify the vendor/model of your graphics card. Which card do you have? does it support opencl?
Getting
I really don't have any idea what I'm doing. Was I supposed to add everything from the two folders together into 1 folder then run? Because that's pretty much all I did, and also edited example file for my pools info. Thats it tho.
Code:
ERROR: -1001, ,No valid ICDs found
assertion "_MY_ERR_X == CL_SUCCESS" failed: file "xptMiner/OpenCLObjects.cpp line 159, funntion: OpenCLMain::OpenCLMain<>
0 [main] xptminer 1876 open_stackdumpfile: dumping stack trace to xptminer.
assertion "_MY_ERR_X == CL_SUCCESS" failed: file "xptMiner/OpenCLObjects.cpp line 159, funntion: OpenCLMain::OpenCLMain<>
0 [main] xptminer 1876 open_stackdumpfile: dumping stack trace to xptminer.
I really don't have any idea what I'm doing. Was I supposed to add everything from the two folders together into 1 folder then run? Because that's pretty much all I did, and also edited example file for my pools info. Thats it tho.
do you have some recommandation? i don't know which one can support to change multi-displaycard gpu-clock.
your driver should have come with such utility. You should look for it in the support forums for your card manufacturer...
do you have some recommandation? i don't know which one can support to change multi-displaycard gpu-clock.
how to set params to change the gpu-clock and gpu-memclock?
xptminer --gpu-engine ? it doesn't work
xptminer --gpu-engine ? it doesn't work
This miner doesn't change the GPU clock. You need to use and external tool for that.
how to set params to change the gpu-clock and gpu-memclock?
xptminer --gpu-engine ? it doesn't work
xptminer --gpu-engine ? it doesn't work
Compiled from code.
strange. Couldn't reproduce it here. But this code is outdated, you should use gigawatt's version which has some optimizations i didn't port back yet. (he used vector types for shavite and metis/fugue, and gained some 20% speed).
his code is at: https://github.com/llamasoft/xptMiner
In the same time I have tried gigawatt's version also - and with the same results.
Maybe it's due to BAMT 1.2 used (32 bits OS)
Hum, probably yes! Even the original networking code from ypool was not meant for 32 bits. This might be solvable, but would take me some time...
Compiled from code.
strange. Couldn't reproduce it here. But this code is outdated, you should use gigawatt's version which has some optimizations i didn't port back yet. (he used vector types for shavite and metis/fugue, and gained some 20% speed).
his code is at: https://github.com/llamasoft/xptMiner
In the same time I have tried gigawatt's version also - and with the same results.
Maybe it's due to BAMT 1.2 used (32 bits OS)
Compiled from code.
strange. Couldn't reproduce it here. But this code is outdated, you should use gigawatt's version which has some optimizations i didn't port back yet. (he used vector types for shavite and metis/fugue, and gained some 20% speed).
his code is at: https://github.com/llamasoft/xptMiner
NEW RELEASE
Build 5, fixes the following bugs:
New Features:
- counts invalid and valid shares separately, so it is easier to spot problems.
Todo:
- several AMD optimizations are on the pipeline, but they were not yet mature (too many invalid shares) so they were NOT included in this version.
Build 5, fixes the following bugs:
New Features:
- counts invalid and valid shares separately, so it is easier to spot problems.
Todo:
- several AMD optimizations are on the pipeline, but they were not yet mature (too many invalid shares) so they were NOT included in this version.
My test rather unsuccessfull:
root@bamt-miner:~/xptMiner-master# ./xptminer -o ypool.net -u xxx.w11 -p xxx -d 0 | grep total
kHash/s: 10747.90 Shares total: 300 (Valid: 0, Invalid: 2)
kHash/s: 10846.21 Shares total: 651 (Valid: 0, Invalid: 2)
kHash/s: 10857.13 Shares total: 986 (Valid: 0, Invalid: 4)
kHash/s: 10878.98 Shares total: 1294 (Valid: 0, Invalid: 6)
kHash/s: 10865.87 Shares total: 1589 (Valid: 0, Invalid: 5)
kHash/s: 10857.13 Shares total: 1964 (Valid: 0, Invalid: 7)
kHash/s: 10869.61 Shares total: 2322 (Valid: 0, Invalid: 1)
kHash/s: 10878.98 Shares total: 2643 (Valid: 0, Invalid: 3)
kHash/s: 10886.26 Shares total: 2955 (Valid: 0, Invalid: 73)
kHash/s: 10892.08 Shares total: 3281 (Valid: 0, Invalid: 4)
kHash/s: 10896.85 Shares total: 3623 (Valid: 0, Invalid: 115)
^C
root@bamt-miner:~/xptMiner-master#
card: Gigabyte 7950 WF3
Did you build it from code or did you use one of the binaries? The code might be buggy since I was doing some tests in it. I'll check what went wrong.
Compiled from code.
NEW RELEASE
Build 5, fixes the following bugs:
New Features:
- counts invalid and valid shares separately, so it is easier to spot problems.
Todo:
- several AMD optimizations are on the pipeline, but they were not yet mature (too many invalid shares) so they were NOT included in this version.
Build 5, fixes the following bugs:
New Features:
- counts invalid and valid shares separately, so it is easier to spot problems.
Todo:
- several AMD optimizations are on the pipeline, but they were not yet mature (too many invalid shares) so they were NOT included in this version.
My test rather unsuccessfull:
root@bamt-miner:~/xptMiner-master# ./xptminer -o ypool.net -u xxx.w11 -p xxx -d 0 | grep total
kHash/s: 10747.90 Shares total: 300 (Valid: 0, Invalid: 2)
kHash/s: 10846.21 Shares total: 651 (Valid: 0, Invalid: 2)
kHash/s: 10857.13 Shares total: 986 (Valid: 0, Invalid: 4)
kHash/s: 10878.98 Shares total: 1294 (Valid: 0, Invalid: 6)
kHash/s: 10865.87 Shares total: 1589 (Valid: 0, Invalid: 5)
kHash/s: 10857.13 Shares total: 1964 (Valid: 0, Invalid: 7)
kHash/s: 10869.61 Shares total: 2322 (Valid: 0, Invalid: 1)
kHash/s: 10878.98 Shares total: 2643 (Valid: 0, Invalid: 3)
kHash/s: 10886.26 Shares total: 2955 (Valid: 0, Invalid: 73)
kHash/s: 10892.08 Shares total: 3281 (Valid: 0, Invalid: 4)
kHash/s: 10896.85 Shares total: 3623 (Valid: 0, Invalid: 115)
^C
root@bamt-miner:~/xptMiner-master#
card: Gigabyte 7950 WF3
Did you build it from code or did you use one of the binaries? The code might be buggy since I was doing some tests in it. I'll check what went wrong.
Jump to: