Show Posts
|
Pages: « 1 2 [3] 4 5 6 »
|
@Elun
Are u working for a fix to use only 1 sgminer when using multi-algo?
"algorithm" : "marucoinmod,marucoinmod-old,marucoinmod"
No, I'm not. I think mrbrdo had some reason to implement algo option like this, maybe it's easier to code algo-switching with only one algo for all gpus, maybe something else.
|
|
|
Test what? I went to the link and say something about a "remove-disabled" : "true" but that didn't change anything. I still get 0's hashs
We know about this issue: https://github.com/sgminer-dev/sgminer/issues/249"remove-disabled" : true (true without quotes) worked for me and in last comment i said why 0 hashes happens. Please, try to remove everything from config about device with '0' id. For example i see this: but here 6 settings "gpu-threads": "2,1,1,2,2,1", If after that you still get zero hashrate i can send you sgminer version with additional logging about this issue, your output will be really helpful. The "device" tells it which devices to use. you still have to have all six settings in other areas, otherwise it would incorrectly assign the settings you want. Anyhow, I got it to work by fenagling with this: "algorithm" : "marucoin-mod", "kernel-path": "/usr/local/bin" I used the c:/path/to/my/bin instead of /usr/local/bin... have no idea if that was the right thing to do but I did that, deleted bins and it works now. What a PITA lol Never mind... it worked for a few minutes and then seems to cutout when switching algos edit: works just fine on my rig with 4 x 7970s and I didn't have to have an "algo" specified in the conf with my other device settings. But the rig with 280x and 5870/5970 is failing Yeah, looked in code deeply, suggestion to remove settings for disabled card was wrong idea. Let's try to solve it step by step: 1. Is miner stable with pool-algortihm setting equal for all pools? 2. Is miner stable without device option? 3. Can you send log file when miner crashes? 4. If miner crashes only on algoswitch, can you send log file from this version: https://www.dropbox.com/s/2zb0f3sal6kkrgl/sgminer_algoswitch_addlog.zip ? I added some messages to thread restart procedure. Also, can you post your current conf file?
|
|
|
Test what? I went to the link and say something about a "remove-disabled" : "true" but that didn't change anything. I still get 0's hashs
We know about this issue: https://github.com/sgminer-dev/sgminer/issues/249"remove-disabled" : true (true without quotes) worked for me and in last comment i said why 0 hashes happens. Please, try to remove everything from config about device with '0' id. For example i see this: but here 6 settings "gpu-threads": "2,1,1,2,2,1", If after that you still get zero hashrate i can send you sgminer version with additional logging about this issue, your output will be really helpful.
|
|
|
For everyone who have issues with sgminer_5 and "device" option, you can use this option in configure file, until it is not fixed: "remove-disabled" : true
|
|
|
50 mh/s limit? stats: 1 anonymous 155,922 55,945.796 2 anonymous 139,968 50,221.536 3 anonymous 122,621 43,997.353
|
|
|
I really would rather see the switching happen on the server end rather than the client...
That would be impossible... the miners are on the client side. The server just rents the hash speed out. It might be possible with a whole new algorithm dedicated to giving hashrate to the server on the backend. It would need to be designed from the ground up just for this sole purpose. Hmm... That still seems insanely impossible... For instance, you're essentially talking about trying to 'convert' Scrypt hashes to X11 hashes, or vice versa... Trying to match a hash with 1 algorithm is already difficult enough, yeah? mmmm yeahh something like that. If it is possible, it opens up the door to a whole new world of possibilities... ESPECIALLY if you can do it with sha-256 to x11 or scrypt ... hell or whatever actually works. My ASIC miners for SHA run like clockwork for weeks straight, .. the GPU rigs are quickly taking up all of my time again now with the multi-algo switching. *edit* Think of a mining algo in which a GPU rig connects to, mines, and its work gets automatically converted to the X11, X13, etc. etc. hell, name the kernel nicehash.cl ... it would need to be a proprietary design Guys, think about it, it's just impossible. SHA256, X11, X13, nFactor, Scrypt are all algorithms, what we submit to the pool is the result of that algorithm (mathematical operation). What you are asking is basically for the server to do the job for you (hence mine for you). You can't take a SHA256 (or whatever else) hash and convert it to X11, X13, etc. The reason why they come up with those algos is in part to make them asic resistant (for a while at least), so that GPUs remain somewhat profitable. For a server to "convert" a hash into another algo's hash would literally imply that the server would have to do the work for you which defeats the purpose of mining (you're supposed to be doing the work yourself, not the server). So the data contained in the share that your GPU hashed and submitted cant be translated and converted into a different share? Maybe in a scenario of miner to miner on both ends? In the end, isnt it just data of 1's and 0's? Suggest that you can convert hash from one algo to another: fuck cryptography in this case. For example "blablabla" without quotes in sha256: 892cd4be79b2bea361b51a472ef8a587730ca3c95816e1a2a8761a82a787bbdf and same in sha-3 256: 0744ea4be0f20ad77cace16010f20019a126a4fd1e07cc5f9d2e59c316cbcf02 No link between them, except encrypted word inside. Hashing algorithms are one-way i.e. They cannot be reversed unlike Encryption-Decryption algorithms. You can use with same probability random number generator for mining.
|
|
|
Using the new 10062014 v5 release, no matter what settings i put for gpu-threads and worksize in the conf file, they default to 2 and 256 in the .bin file name. TC & n-factor seems to be the only thing changing
Is this normal?
No, this isn't normal. Anyone who have linux, can you update your sgminer 5 and confirm that this options don't work?
|
|
|
Windows build with latests fixes: http://www.dropbox.com/s/fkju7a7fjo4swco/sgminer_v5_0_10062014.zipI'm using BAMT 1.6.9 and I've compiled sgminer amd updated the bamt.conf with my pool details but whenever I restart the mining i just get a load of invalids. my conf is below.. any helpwould be greatly appreaciated.. been doing my head in for days trying to get it to work:-
{ "pools": [ { "url": "stratum+tcp://am01.eu.trademybit.com:4011", "user": "1", "pass": "x", "name": "x13", "algorithm": "marucoin-mod" }, { "url": "stratum+tcp://am01.eu.trademybit.com:4010", "user": "1", "pass": "x", "name": "x11", "algorithm": "darkcoin-mod" } ], "worksize": "128", "kernel": "marucoin-mod", "intensity": "18", "lookup-gap": "2", "thread-concurrency": "8192", "auto-fan": true, "gpu-threads": "2", "gpu-engine": "1090", "gpu-memclock": "1500" }
{ "pools": [ { "url": "stratum+tcp://am01.eu.trademybit.com:4011", "user": "1", "pass": "x", "name": "x13", " pool-algorithm": "marucoin-mod" }, { "url": "stratum+tcp://am01.eu.trademybit.com:4010", "user": "1", "pass": "x", "name": "x11", " pool-algorithm": "darkcoin-mod" } ], "worksize": "128", "intensity": "18", "lookup-gap": "2", "thread-concurrency": "8192", "auto-fan": true, "gpu-threads": "2", "gpu-engine": "1090", "gpu-memclock": "1500" } Try this one.
|
|
|
Thank you.
Unfortunately, none of that helped. Even adding the Kernel-path setting (modified to my SGMiner location of course) didn't resolve the issue. I tried it both with the 06062014 and the 09062014 builds. I tried it with my config, and it would close a few seconds after opening. I tried it with your config and it started, but still threw endless rejects. I tried the path with both single and double back-slashes, no difference. I deleted the .bin files, no effect.
I am using driver 13.11, with other stuff (e.g. Catalyst & AMD APP SDK) installed. It's been super stable for months like that though mining Scrypt & Scrypt-N with an older release of SGMiner.
Any other thoughts or suggestions?
can you add "pause" in your bat file and see what happens before sgminer die, for example: setx GPU_MAX_ALLOC_PERCENT 100 setx GPU_USE_SYNC_OBJECTS 1 sgminer.exe --config sgminer.conf pause I have 4x7950 and 1x 6970, so I can't delete the device options. But I'll send u a pm with my output.log and my config
I understand that you can't remove device option for full time, i just need a confirmation that with device option algo on-fly change doesn't work, and miner too(zero hashrate). After that i can create an issue on github, now i have confirmation of this bug only on my pc.
|
|
|
Thanks, but the same shit everytime..Using win8.1. back to x13mod As i understand you have "device" option in your config and you get zero hashrate? Try to remove "device" option. As i understand "device" option doesn't work correctly in sgminer 5 with algo on-fly switch. Please, post your results if i understand your issue correctly.
|
|
|
Settings still don't work... is there a debug anywhere?
You can try use --debug option. Also, can you say your driver version?
|
|
|
It doesnt seem to work for me.... It just opens then closes straight away... I am using
""pools" : [ { "name" : "NiceHash_X11", "url" : "stratum+tcp://stratum.nicehash.com:3336", "user" : "MY ADD", "pass" : "x", "pool-nfactor" : "10", "pool-algorithm" : "darkcoin-mod", "pool-gpu-engine" : "1100", "pool-thread-concurrency" : "24000", "pool-xintensity" : "4", "pool-gpu-threads" : "2" }, ]
Anyone know why it may not be working?
Your json isn't valid, try this one: { "pools" : [ { "name" : "NiceHash_X11", "url" : "stratum+tcp://stratum.nicehash.com:3336", "user" : "ADDR", "pass" : "x", "pool-nfactor" : "10", "pool-algorithm" : "darkcoin-mod", "pool-gpu-engine" : "1100", "pool-thread-concurrency" : "24000", "pool-xintensity" : "4", "pool-gpu-threads" : "2" } ] } Hello, Hashrate is better for qubit but no hash is seen on pool... Thanks Check your settings or pool, works fine: http://pixs.ru/showimage/qubitpng_1109791_12436729.png
|
|
|
x13modold already added(5 June 2014). You can use marucoin-modold.
|
|
|
Just a note - I think the uptime counter re-initializes each time it flips to a different kernel. I've left my rigs on all night, and a few are only counting up to ~53 minutes at the current moment - checked against Nicehash graphs and it looks like it was last on X11 about an hour ago... That's kind of a cool feature, but I wonder if we can get it to stretch through the whole mining instance... Here's an example of the calc error on the uptime counter -> https://i.imgur.com/GPPXuDj.pngRig has been up for a good 6 (started at 0400, it's now 1015) hours but the uptime counter is only at 1 hour. Maybe we can make it the current algo uptime counter? yep, found what is wrong, going to create issue on github.
|
|
|
Elun this build crashes out immediately with HW errors even if you use the exact same .conf file from the previous build. Something we're missing? Wow, can i see your conf file?
|
|
|
Look here: https://en.bitcoin.it/wiki/Running_Bitcoin#Bitcoin.conf_Configuration_FileThis option: # By default, only RPC connections from localhost are allowed. Specify # as many rpcallowip= settings as you like to allow connections from # other hosts (and you may use * as a wildcard character). # NOTE: opening up the RPC port to hosts outside your local # trusted network is NOT RECOMMENDED, because the rpcpassword # is transmitted over the network unencrypted. #rpcallowip=10.1.1.34 #rpcallowip=192.168.1.* And check other options, maybe they will help you.
|
|
|
|