Guys! We do not need more optimization! If all we get a faster kernel, then the difficulty will increase proportionally. Accordingly, we will not get more coins, but will pay more for electricity. Profits will only decrease.  Faster kernel good for dev only (as a reward for their hard work), i think so. true.... until you have half the hashpower by a couple fpga miners (or so they say) ;-) |
|
|
|
there is absolute no reason why someone cant go solomining
over long time average earning will always beat pool mining because u have 0 fee 0 transaction cost for withdraw from pool
Not only because of the fees, but solo mining is always more profitable, IF you have the hash power to find blocks frequently enough AND the tools to monitor that hash power. Pool mining has significant overheads, pushpool much more than stratum, but these overheads exist. Using a pool also assumes you accept the possibility that it might malfunction and that *you* cannot fix it. If you want absolute control over your mining earnings, solo mining is the only answer. I have tried solo mining for about 10 days but I'm generating too many orphans: about 1 out of every 7/8 valid blocks. It's like having a pool with 10% fee. Hashpower is ok, probably my network is too slow. |
|
|
|
|
HOW TO TELL IF AN SGMINER BIN FILE IS 32 OR 64 BIT
If the filename, generated by sgminer, ends in l4.bin it is 32 bit (8 x 4 = 32)
If the filename, generated by sgminer, ends in l8.bin it is 64 bit (8 x 8 = 64)
They are incompatible.
|
|
|
|
I built my bins with Wolf0's x64 miner. Works perfectly.
could you share your bin files please? Personally, I wouldn't download this. I'd generate my own. But here it is. Use at your own risk! http://ge.tt/2uga0R82/v/0?cThanks, but it's 32 bit, I need 64 bit. |
|
|
|
I built my bins with Wolf0's x64 miner. Works perfectly.
could you share your bin files please? |
|
|
|
@pallas: Thanks for fiddling with Win7!  What does it means by 32 bit code? That has no meaning regarding the GCN hardware o.O But I'm 100% sure that you can't use my Capeverde binary unless you have that chip in the device you selected. ( var dev:=cl.devices[CLdeviceIndex]; ) Bins generated by sgminer on a 32 bit system will not work on a 64 bit one and viceversa, so I suppose the same is true for your kernels. Min end in l4.bin ... am I 32 or 64 ... (win 7 x64) 4 * 8 (bits) = 32 it's the size of a long integer. probably the sgminer build you are using is 32 bit. question is does hetpas use 32 or 64 bit ... I'd assume 32 bit since it runs ok on my sgminer ... my sgminer is old 4.1.0 ... so you main prob is needing hetpas src to run on linux ... Probably realhet coded it for 32 bit; I don't know what changes, maybe the parameter passing part. I hope realhet has time to look into this. I also use version 4.1. Hetpas can't run on linux: I'll try again with the new version when I can access my workstation and make it boot on windows. |
|
|
|
@pallas: Thanks for fiddling with Win7! What does it means by 32 bit code? That has no meaning regarding the GCN hardware o.O But I'm 100% sure that you can't use my Capeverde binary unless you have that chip in the device you selected. ( var dev:=cl.devices[CLdeviceIndex]; ) Bins generated by sgminer on a 32 bit system will not work on a 64 bit one and viceversa, so I suppose the same is true for your kernels. Min end in l4.bin ... am I 32 or 64 ... (win 7 x64) 4 * 8 (bits) = 32 it's the size of a long integer. probably the sgminer build you are using is 32 bit. |
|
|
|
@pallas: Thanks for fiddling with Win7! What does it means by 32 bit code? That has no meaning regarding the GCN hardware o.O But I'm 100% sure that you can't use my Capeverde binary unless you have that chip in the device you selected. ( var dev:=cl.devices[CLdeviceIndex]; ) Bins generated by sgminer on a 32 bit system will not work on a 64 bit one and viceversa, so I suppose the same is true for your kernels. infact: [10:25:27] Internal error: Input OpenCL binary is not for the target! |
|
|
|
@pallas: Thanks for fiddling with Win7! What does it means by 32 bit code? That has no meaning regarding the GCN hardware o.O But I'm 100% sure that you can't use my Capeverde binary unless you have that chip in the device you selected. ( var dev:=cl.devices[CLdeviceIndex]; ) Bins generated by sgminer on a 32 bit system will not work on a 64 bit one and viceversa, so I suppose the same is true for your kernels. |
|
|
|
|
"when Pallas says that R9 280x is 18MH/s he counts it in Groestl hashes."
no my hashrates are taken from sgminer.
|
|
|
|
I'm running it for an hour now and I got a 'rejected'. I'm solo mining GRS. Do I need to worry? Or is it usual? Can it be caused by slow network?
yes it can be cause of the network: if the wallet is behind sync, the block may be rejected (or orphaned). try with a pool... |
|
|
|
|
Realhet, thanks for the capeverde bin, unfortunately I can't use it because it's 32 bit.
I created a bootable win7 stick in order to compile the kernel: it compiles fine but, when run, it says "no target Hawaii" and no bin is created.
|
|
|
|
I've got a little issue with the headless wallet.
Recently I started solo mining and got some dmds; the wallet created two new addresses, according to "listaddressgroupings", and put the generated dmds there.
What's weird is that those two addresses do not show up on any "getaddressesbyaccount" for all the accounts of "listaccounts".
So where are those addresses? How can I send the coins they contain to another address, in order to consolidate my earnings?
Thanks!
bump! |
|
|
|
|
The compiled bin file should work regardless of catalyst version or operating system, so could you please post a link to the bin file? Thanks.
There is something weird about the sgminer screenshot, are you sure it's working correctly? It shows a single, disabled GPU with id 0, and the share got accepted was from GPU id 1. The diff numbers are also kinda weird.
|
|
|
|
Well, I found it better not to alter sgminer, that I'm totally unfamiliar with it and rather started to turn my kernel to be exactly the same as groestlcoin.cl from the outside. It will be a half page of additional code that deals with the kernel parameters. With a small dummy kernel it is already working now, but I'm just too tired to continue now. well that's easier to use for the people. waiting forward to seeing your progress! :-) |
|
|
|
|
I see there is very little interest in mining groestl coins with GPU: very few users joined the recent discussion (2/3).
Let alone contributing to the code (2) or donating (2), in the whole life of this thread.
|
|
|
|
I'm using your kernel: groestlcoin.cl.
Now I disassembled a dummy kernel with the appropriate parameters and I forgot about the T buffers. OpenCL uploads them in an extra buffer automatically. I don't even wanna know how the driver send that extra buffer and most importantly can't make an automatic skeleton kernel to get the binary with a placeholder for constant data that my program can patch with the output of the assembler.
So the easiest way would be to modify sgminer to handle my kernel. I have found the the 'queue_sph_kernel()' function where I can start from.
I never tested my kernel with cards smaller than tahiti, I also have no reports of it running on <= pitcairn: other groestlcoin kernels might be faster in that case. |
|
|
|
Thanks for help. Now it runs, and I found that this command produces the best results: sgminer -d 1 -k groestlcoin --difficulty-multiplier 0.0039062500 -o http://localhost:1441 -u u -p p --shaders 1280 --worksize 256 -g 1 --intensity 24 It produces (avg)2MH/s which is the half of the 4Mh/s I calculated earlier. Does sgminer divides the Groestl-hash calculation number by 2? Although, It would be more reasonable. Or something is really wrong, that It runs on half speed (exactly hald speed)? Intensity 24 is too much, I'd stay between 20 and 22, otherwise you'll produce a lot of rejected shares (or orphans if solo mining). The shaders option is ignored for groestl. The hashrate should be calculated on the full computation, i.e. 2 chained hashes. What kernel are you using? |
|
|
|
Unfortunately there is no --benchmark parameter. I checked in in the source code too, but nothing similar https://github.com/sgminer-dev/sgminer/blob/master/sgminer.c. Is there a simple war to run it? Now I have a groestl wallet, but where can I get username from? What parameters should I use other than -k groestl and -d 1? Probably they removed it, I'm using an older version. I run it like this, for solo mine: sgminer -k groestlcoin --difficulty-multiplier 0.0039062500 -o http://localhost:GROESTLCOIN_RPC_PORT -u YOURUSER -p YOURPASSWORD Then you have to find and add your best intensity and worksize (my OS kernel works with 256 only). username and password are set in groestlcoin.conf; the port you can easily find in their thread (or via netstat). |
|
|
|
I'd run a pool myself, if it wasn't for all the ddos attacks.
Have you considered Cloud Flare free service ? no, I just saw how most pools have troubles so I stopped considering making one ;-) |
|
|
|
|
Show Posts
