srcxxx
7950, 1.3.0, 14.6, ATH, -k optimized - works
7950, 1.3.0M, 14.6, ATH, -k optimized - does not work
why?
Topic: [ANN][Groestl/MyriadGroestl] Pool closed - page 8. (Read 37007 times)
srcxxx
7950, 1.3.0, 14.6, ATH, -k optimized - works
7950, 1.3.0M, 14.6, ATH, -k optimized - does not work
why?
You can download full set of BOP files compiled on AMD drivers version 13.12 from here: https://mega.co.nz/#!IFZHCTRY!yo3CpPN_SLrYq0JU2mH1cKvqGcIZG7ZI4352s5nS8Bk
It may be faster for old videocards like 7950 and earlier.
Please reply to this thread with videocard model if 13.12 BOP was better for you.
Thanks!
It may be faster for old videocards like 7950 and earlier.
Please reply to this thread with videocard model if 13.12 BOP was better for you.
Thanks!
Yes, it is already included in the 3.1.0M release. See my post above.
Or if you have 3.1.0 and just need this particular file, get it from github repository: https://github.com/srcxxx/grs-sgminer/raw/master/myriad-groestlCypress256.bop
Thanks for the fast reply but sgminer's error demanded myriadcoin-groestlCypress256.bop and not myriad-groestlCypress256.bop.
I tried and renamed the bop file but it still doesnt work.
There are just a few bop files included which goes myriadcoin-groestl instead of myraid-groestl.. Whats the difference?
I think this is my screwup. I apologize.
myriad-groestl is supposed to be myriadcoin-groestl.
Will re-upload 1.3.0M.
What's the error that you are getting after you rename the file? What is the videocard and driver version?
Yes, it is already included in the 3.1.0M release. See my post above.
Or if you have 3.1.0 and just need this particular file, get it from github repository: https://github.com/srcxxx/grs-sgminer/raw/master/myriad-groestlCypress256.bop
Thanks for the fast reply but sgminer's error demanded myriadcoin-groestlCypress256.bop and not myriad-groestlCypress256.bop.
I tried and renamed the bop file but it still doesnt work.
There are just a few bop files included which goes myriadcoin-groestl instead of myraid-groestl.. Whats the difference?
hi
no change with 1.3 or 1.3M 15.7mhs on 6970, better than "older" 15 mhs.
i'd like 18-20 mhs
good job
no change with 1.3 or 1.3M 15.7mhs on 6970, better than "older" 15 mhs.
i'd like 18-20 mhs
good job
hi
no hope for hd 69xx?
no hope for hd 69xx?
Why not? I think it should work. The new 1.3.0M should have the BOP file for your video card.
If there is a specific error message - please let me know.
sgminer 1.2.5 with -k optimized - OK
sgminer 1.3.0 with -k optimized - OK
sgminer 1.3.0.M with -k optimized - error :
GPU0 - R9_270x; GPU1 - 7850.
...
My result on groestl on old videocards:
radeon 5870 (900Mhz, driver ver. 13.12) on the original groestlcoin.cl - 6.535 Mh, and on the optimized groestlcoin.cl - 6.91 Mh = better in 6%;
radeon 6850 (800Mhz, driver ver. 13.12) on the original groestlcoin.cl - 3.22 Mh, and on the optimized groestlcoin.cl - 3.39 Mh = better in 5%;
Version 1.3.0 with -k optimized - error:
sgminer 1.3.0 with -k optimized - OK
sgminer 1.3.0.M with -k optimized - error :
Code:
sgminer 1.3.0 - Started: [2014-07-08 22:56:39]
--------------------------------------------------------------------------------
(5s):0.000 (avg):0.000h/s | A:0 R:0 HW:0 WU:0.000/m
ST: 1 SS: 0 NB: 1 LW: 18 GF: 0 RF: 0
Connected to Pool 0 (stratum) diff 0.031 as user FnzMEE2fkX31J5EjheNMo8pq2672Q5kjGh
Block: 4f990c0c... Diff:39 Started: [22:56:39] Best share: 0
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 34.0C 1948RPM | OFF / 0.000h/s | R: 0.0% HW:0 WU:0.000/m I:22
GPU 1: 36.0C 3293RPM | OFF / 0.000h/s | R: 0.0% HW:0 WU:0.000/m I:19
--------------------------------------------------------------------------------
[22:56:37] Started sgminer 1.3.0
[22:56:37] Optimized groestlcoin kernel invoked.
[22:56:37] Optimized groestlcoin kernel invoked.
[22:56:37] Probing for an alive pool
[22:56:38] Pool 0 difficulty changed to 0.031
[22:56:39] Network diff set to 39
[22:56:39] Error -54: Enqueueing kernel onto command queue. (clEnqueueNDRangeKernel)
[22:56:39] Error -54: Enqueueing kernel onto command queue. (clEnqueueNDRangeKernel)
[22:56:39] GPU 1 failure, disabling!
[22:56:39] GPU 0 failure, disabling!
...
My result on groestl on old videocards:
radeon 5870 (900Mhz, driver ver. 13.12) on the original groestlcoin.cl - 6.535 Mh, and on the optimized groestlcoin.cl - 6.91 Mh = better in 6%;
radeon 6850 (800Mhz, driver ver. 13.12) on the original groestlcoin.cl - 3.22 Mh, and on the optimized groestlcoin.cl - 3.39 Mh = better in 5%;
Version 1.3.0 with -k optimized - error:
Code:
sgminer 1.3.0 - Started: [2014-07-08 23:43:01]
--------------------------------------------------------------------------------
(5s):0.000 (avg):0.000h/s | A:0 R:0 HW:0 WU:0.000/m
ST: 2 SS: 0 NB: 1 LW: 10 GF: 0 RF: 0
Connected to Pool 0 (stratum) diff 0.031 as user FnzMEE2fkX31J5EjheNMo8pq2672Q5k
Block: e42a4b72... Diff:37 Started: [23:43:01] Best share: 0
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 51.0C 2974RPM | OFF / 0.000h/s | R: 0.0% HW:0 WU:0.000/m I:16
--------------------------------------------------------------------------------
[23:42:59] Started sgminer 1.3.0
[23:42:59] Optimized groestlcoin kernel invoked.
[23:42:59] Probing for an alive pool
[23:43:00] Pool 0 difficulty changed to 0.031
[23:43:01] Network diff set to 37
[23:43:01] Error -54: Enqueueing kernel onto command queue. (clEnqueueNDRangeKer
nel)
[23:43:01] GPU 0 failure, disabling!
hi
no hope for hd 69xx?
no hope for hd 69xx?
I believe that I have found a way to compile .BOP files for all AMD videocards, not just for 79X0, R9 290, R9 280X and R9 270X.
So if you had some problems with an old videocard, please re-download grs-sgminer 1.3.0 from here: https://github.com/srcxxx/grs-sgminer/releases/download/1.3.0/grs-sgminer1_3_0_M.7z
The file is compressed with 7-zip (http://www.7-zip.org) to reduce the filesize.
Note: there are no changes to the distributable rather than addition of .BOP files. So if everything is working fine, don't bother re-downloading.
PS: These .bop files were compiled in 14.6 beta. I'll also compile another set in 13.12, perhaps it'll be faster for some hardware (for example I think 7970 works better with 13.12 drivers).
I'm on LinuxSo if you had some problems with an old videocard, please re-download grs-sgminer 1.3.0 from here: https://github.com/srcxxx/grs-sgminer/releases/download/1.3.0/grs-sgminer1_3_0_M.7z
The file is compressed with 7-zip (http://www.7-zip.org) to reduce the filesize.
Note: there are no changes to the distributable rather than addition of .BOP files. So if everything is working fine, don't bother re-downloading.
PS: These .bop files were compiled in 14.6 beta. I'll also compile another set in 13.12, perhaps it'll be faster for some hardware (for example I think 7970 works better with 13.12 drivers).
My 7850 (myriadcoin-groestlPitcairn256.bop) works with 13.12 & 14.6 but my 7950 cards (myriadcoin-groestlTahiti256.bop) only works in 14.6, not in 13.12 like you recommend...
I get these errors :
[17:15:14] Error -11: Building Program (clBuildProgram)
[17:15:14] Frontend phase failed compilation.
Error: Compilation from LLVMIR binary to IL text failed!
Hi!
Did I understand correctly that current version of myriadcoin-groestlTahiti256.bop does not work in 13.12 on Linux for 7950 cards?
Which driver version are you using on Linux? 13.12?
PS: I'll probably upload a 13.12 compile of all .bop files in approx 14 hours from now.
Thanks
I just reinstalled 14.6 beta drivers and my 7950 does work with these but indeed it was not with 13.12 drivers, i got the errors above
Your normal kernel works fine in 13.12 also, i only have my problem with the optimized version, maybe your 13.12 bop files will solve it
I believe that I have found a way to compile .BOP files for all AMD videocards, not just for 79X0, R9 290, R9 280X and R9 270X.
So if you had some problems with an old videocard, please re-download grs-sgminer 1.3.0 from here: https://github.com/srcxxx/grs-sgminer/releases/download/1.3.0/grs-sgminer1_3_0_M.7z
The file is compressed with 7-zip (http://www.7-zip.org) to reduce the filesize.
Note: there are no changes to the distributable rather than addition of .BOP files. So if everything is working fine, don't bother re-downloading.
PS: These .bop files were compiled in 14.6 beta. I'll also compile another set in 13.12, perhaps it'll be faster for some hardware (for example I think 7970 works better with 13.12 drivers).
I'm on LinuxSo if you had some problems with an old videocard, please re-download grs-sgminer 1.3.0 from here: https://github.com/srcxxx/grs-sgminer/releases/download/1.3.0/grs-sgminer1_3_0_M.7z
The file is compressed with 7-zip (http://www.7-zip.org) to reduce the filesize.
Note: there are no changes to the distributable rather than addition of .BOP files. So if everything is working fine, don't bother re-downloading.
PS: These .bop files were compiled in 14.6 beta. I'll also compile another set in 13.12, perhaps it'll be faster for some hardware (for example I think 7970 works better with 13.12 drivers).
My 7850 (myriadcoin-groestlPitcairn256.bop) works with 13.12 & 14.6 but my 7950 cards (myriadcoin-groestlTahiti256.bop) only works in 14.6, not in 13.12 like you recommend...
I get these errors :
[17:15:14] Error -11: Building Program (clBuildProgram)
[17:15:14] Frontend phase failed compilation.
Error: Compilation from LLVMIR binary to IL text failed!
Hi!
Did I understand correctly that current version of myriadcoin-groestlTahiti256.bop does not work in 13.12 on Linux for 7950 cards?
Which driver version are you using on Linux? 13.12?
PS: I'll probably upload a 13.12 compile of all .bop files in approx 14 hours from now.
Thanks
I believe that I have found a way to compile .BOP files for all AMD videocards, not just for 79X0, R9 290, R9 280X and R9 270X.
will there be a myriadcoin-groestlCypress256.bop file in the future too?
Yes, it is already included in the 3.1.0M release. See my post above.
Or if you have 3.1.0 and just need this particular file, get it from github repository: https://github.com/srcxxx/grs-sgminer/raw/master/myriad-groestlCypress256.bop
I believe that I have found a way to compile .BOP files for all AMD videocards, not just for 79X0, R9 290, R9 280X and R9 270X.
So if you had some problems with an old videocard, please re-download grs-sgminer 1.3.0 from here: https://github.com/srcxxx/grs-sgminer/releases/download/1.3.0/grs-sgminer1_3_0_M.7z
The file is compressed with 7-zip (http://www.7-zip.org) to reduce the filesize.
Note: there are no changes to the distributable rather than addition of .BOP files. So if everything is working fine, don't bother re-downloading.
PS: These .bop files were compiled in 14.6 beta. I'll also compile another set in 13.12, perhaps it'll be faster for some hardware (for example I think 7970 works better with 13.12 drivers).
I'm on LinuxSo if you had some problems with an old videocard, please re-download grs-sgminer 1.3.0 from here: https://github.com/srcxxx/grs-sgminer/releases/download/1.3.0/grs-sgminer1_3_0_M.7z
The file is compressed with 7-zip (http://www.7-zip.org) to reduce the filesize.
Note: there are no changes to the distributable rather than addition of .BOP files. So if everything is working fine, don't bother re-downloading.
PS: These .bop files were compiled in 14.6 beta. I'll also compile another set in 13.12, perhaps it'll be faster for some hardware (for example I think 7970 works better with 13.12 drivers).
My 7850 (myriadcoin-groestlPitcairn256.bop) works with 13.12 & 14.6 but my 7950 cards (myriadcoin-groestlTahiti256.bop) only works in 14.6, not in 13.12 like you recommend...
I get these errors :
[17:15:14] Error -11: Building Program (clBuildProgram)
[17:15:14] Frontend phase failed compilation.
Error: Compilation from LLVMIR binary to IL text failed!
I believe that I have found a way to compile .BOP files for all AMD videocards, not just for 79X0, R9 290, R9 280X and R9 270X.
will there be a myriadcoin-groestlCypress256.bop file in the future too?
I believe that I have found a way to compile .BOP files for all AMD videocards, not just for 79X0, R9 290, R9 280X and R9 270X.
So if you had some problems with an old videocard, please re-download grs-sgminer 1.3.0 from here: https://github.com/srcxxx/grs-sgminer/releases/download/1.3.0/grs-sgminer1_3_0_M.7z
The file is compressed with 7-zip (http://www.7-zip.org) to reduce the filesize.
Note: there are no changes to the distributable rather than addition of .BOP files. So if everything is working fine, don't bother re-downloading.
PS: These .bop files were compiled in 14.6 beta. I'll also compile another set in 13.12, perhaps it'll be faster for some hardware (for example I think 7970 works better with 13.12 drivers).
So if you had some problems with an old videocard, please re-download grs-sgminer 1.3.0 from here: https://github.com/srcxxx/grs-sgminer/releases/download/1.3.0/grs-sgminer1_3_0_M.7z
The file is compressed with 7-zip (http://www.7-zip.org) to reduce the filesize.
Note: there are no changes to the distributable rather than addition of .BOP files. So if everything is working fine, don't bother re-downloading.
PS: These .bop files were compiled in 14.6 beta. I'll also compile another set in 13.12, perhaps it'll be faster for some hardware (for example I think 7970 works better with 13.12 drivers).
Heavily disappointed that the optimized only works on a specific pool. Also, why can you not run dmd without --normal-hashing true? I would like to be able to switch between grs and dmd pools at will without having to take that config in and out.
Normal hashing parameter was introduced exactly for this reason. To be able to switch between grs and dmd pools in realtime.
See example.conf. You also should be able to specify normal-hashing true, false in command line if you are specifying two pools: dmd and grs
See that is the problem I am having. I have my rig setup under Mining Rig Rentals and don't have the option to put flags in depending on what pool I am mining at.
If I want to change it, I would need to restart the miner everytime with and without the parameter. Do you think setting it up as pool 1 and 2 with and without the parameter would work?
There must be some way to tell Groestlcoin algo pools from Diamondcoin algo pools.
Because the two coins use different merkle tree hashing (Groestlcoin uses single sha256, while Diamondcoin uses double sha256).
Perhaps it is possible to do something on the mining rig rentals site. Actually when I went to https://www.miningrigrentals.com/, there are no Diamond or Groestl algorithms.
They removed it from the front page with the addition of Fresh algorithm because it doesn't sell well with not many groestl coins out there.
https://www.miningrigrentals.com/rigs/groestl is the direct link to it now.
The problem is that on MRR you can enter 5 pools that you'd like to fall back to. The problem comes in because you still have to point your rig to MRR with the --normalhashing true command. So switching to a GRS coin wouldnt work because --normalhashing is still in there. Do you get what im saying?
Sorry this is hard to explain for some reason. It's basically 2 diff algorithms as far as MMR is concerned.
1) The only rig they have there right now is actually "myriad-groestl". This is not the same groestl as in DMD and GRS.
2) Yes, I understand exactly what you are saying.
The only thing that I have in mind is modifying the sgminer app to automatically guess the "normal-hashing" parameter for DMD pools. There are just a few of them after all, perhaps 5.
Heavily disappointed that the optimized only works on a specific pool. Also, why can you not run dmd without --normal-hashing true? I would like to be able to switch between grs and dmd pools at will without having to take that config in and out.
Normal hashing parameter was introduced exactly for this reason. To be able to switch between grs and dmd pools in realtime.
See example.conf. You also should be able to specify normal-hashing true, false in command line if you are specifying two pools: dmd and grs
See that is the problem I am having. I have my rig setup under Mining Rig Rentals and don't have the option to put flags in depending on what pool I am mining at.
If I want to change it, I would need to restart the miner everytime with and without the parameter. Do you think setting it up as pool 1 and 2 with and without the parameter would work?
There must be some way to tell Groestlcoin algo pools from Diamondcoin algo pools.
Because the two coins use different merkle tree hashing (Groestlcoin uses single sha256, while Diamondcoin uses double sha256).
Perhaps it is possible to do something on the mining rig rentals site. Actually when I went to https://www.miningrigrentals.com/, there are no Diamond or Groestl algorithms.
They removed it from the front page with the addition of Fresh algorithm because it doesn't sell well with not many groestl coins out there.
https://www.miningrigrentals.com/rigs/groestl is the direct link to it now.
The problem is that on MRR you can enter 5 pools that you'd like to fall back to. The problem comes in because you still have to point your rig to MRR with the --normalhashing true command. So switching to a GRS coin wouldnt work because --normalhashing is still in there. Do you get what im saying?
Sorry this is hard to explain for some reason. It's basically 2 diff algorithms as far as MMR is concerned.
Heavily disappointed that the optimized only works on a specific pool. Also, why can you not run dmd without --normal-hashing true? I would like to be able to switch between grs and dmd pools at will without having to take that config in and out.
Normal hashing parameter was introduced exactly for this reason. To be able to switch between grs and dmd pools in realtime.
See example.conf. You also should be able to specify normal-hashing true, false in command line if you are specifying two pools: dmd and grs
See that is the problem I am having. I have my rig setup under Mining Rig Rentals and don't have the option to put flags in depending on what pool I am mining at.
If I want to change it, I would need to restart the miner everytime with and without the parameter. Do you think setting it up as pool 1 and 2 with and without the parameter would work?
There must be some way to tell Groestlcoin algo pools from Diamondcoin algo pools.
Because the two coins use different merkle tree hashing (Groestlcoin uses single sha256, while Diamondcoin uses double sha256).
Perhaps it is possible to do something on the mining rig rentals site. Actually when I went to https://www.miningrigrentals.com/, there are no Diamond or Groestl algorithms.
Heavily disappointed that the optimized only works on a specific pool. Also, why can you not run dmd without --normal-hashing true? I would like to be able to switch between grs and dmd pools at will without having to take that config in and out.
Normal hashing parameter was introduced exactly for this reason. To be able to switch between grs and dmd pools in realtime.
See example.conf. You also should be able to specify normal-hashing true, false in command line if you are specifying two pools: dmd and grs
See that is the problem I am having. I have my rig setup under Mining Rig Rentals and don't have the option to put flags in depending on what pool I am mining at.
If I want to change it, I would need to restart the miner everytime with and without the parameter. Do you think setting it up as pool 1 and 2 with and without the parameter would work?
grs-sgminer 1.3.0 is out. See first page for details.
If you do not plan to mine Saffroncoin or Myriadcoin, you can skip this release. Groestl mining speed is not changed.
Main improvement is addition of myriadcoin-groestl mining in "optimized" mode. Myriadcoin-groestl speed is:
R9 290 - 33 MH/s
R9 270X - 16 MH/s
You can mine Saffroncoin and Myriadcoin on the optimized pool. See example-myriad.conf.
{
"pools" : [
{
"url" : "stratum+tcp://cryptohunger.com:60001",
"user" : "MUbwYW4NmmkR4Ejg5v7tQye5DW5jSQVz3X",
"pass" : "xxx",
"poolname" : "MyriadCoinOptimized"
},
{
"url" : "stratum+tcp://cryptohunger.com:60002",
"user" : "SSY2UGmZfkPasNdjZy3YCgQF8yFx3w899C",
"pass" : "xxx",
"poolname" : "SaffronCoinOptimized"
}
],
"gpu-engine" : "1150",
"gpu-memclock" : "150",
"intensity" : "22",
"gpu-threads" : "1",
"auto-fan" : true,
"temp-cutoff" : "90",
"temp-overheat" : "80",
"temp-target" : "70",
"gpu-fan" : "40-80",
"worksize" : "256",
"api-port" : "4028",
"kernel" : "myriadcoin-optimized",
"gpu-powertune" : "20"
}
If you do not plan to mine Saffroncoin or Myriadcoin, you can skip this release. Groestl mining speed is not changed.
Main improvement is addition of myriadcoin-groestl mining in "optimized" mode. Myriadcoin-groestl speed is:
R9 290 - 33 MH/s
R9 270X - 16 MH/s
You can mine Saffroncoin and Myriadcoin on the optimized pool. See example-myriad.conf.
{
"pools" : [
{
"url" : "stratum+tcp://cryptohunger.com:60001",
"user" : "MUbwYW4NmmkR4Ejg5v7tQye5DW5jSQVz3X",
"pass" : "xxx",
"poolname" : "MyriadCoinOptimized"
},
{
"url" : "stratum+tcp://cryptohunger.com:60002",
"user" : "SSY2UGmZfkPasNdjZy3YCgQF8yFx3w899C",
"pass" : "xxx",
"poolname" : "SaffronCoinOptimized"
}
],
"gpu-engine" : "1150",
"gpu-memclock" : "150",
"intensity" : "22",
"gpu-threads" : "1",
"auto-fan" : true,
"temp-cutoff" : "90",
"temp-overheat" : "80",
"temp-target" : "70",
"gpu-fan" : "40-80",
"worksize" : "256",
"api-port" : "4028",
"kernel" : "myriadcoin-optimized",
"gpu-powertune" : "20"
}
Quote
EDIT: after scrcxxx's posting in the DMD official Bitcointalk.org thread, there indeed seems to be a pool fee (see: https://bitcointalksearch.org/topic/m.7611037)
Of course there is a fee. But there is one important difference!
The hashrate that you see in sgminer is already multiplied by it.
So there is no fee on top of what you see in sgminer. Period.
It is different from other pools. In other pools if you have 10.0 mhs in sgminer and 2% fee, you'll actually be paid for 9.8 mhs.
Transaction fees are even harder to account for.
If you are so curious to know what the pool fee is, you can figure out this value with at least two different ways on your own. (I'm not going to explain them here of course)
I'm setting up the fee in a way, so that it is interesting for you miners to mine on my pool instead of using non optimized kernel with other pools.
PS: in case you are wonderinv why I wrote so many messages in this thread today... :-) I'm at my son's tae kwon do grading and there are like 30 people besides my son. I'm happy my iPhone is with me..
Jump to: