Topic: [ANN] sgminer v5 - optimized X11/X13/NeoScrypt/Lyra2RE/etc. kernel-switch miner - page 190. (Read 877844 times)
July 22, 2014, 09:04:45 PM
Can anyone help me set up a .bat file for x15 mining? Whatever i 've tried so far doesn't seem to work and for the first time since i started mining i can't figure it out for the life of me.
July 22, 2014, 07:16:26 AM
no bro, windows 7 x64 with 4gb ddr3 RAM
i imagine that it would go even faster on linux ... because my usb errupters mining aprox 300 kh/s per errupter on windows ... yesterday i put them to xubuntu and with same errupters im mining aprox 380kh/s with one errupter
i imagine that it would go even faster on linux ... because my usb errupters mining aprox 300 kh/s per errupter on windows ... yesterday i put them to xubuntu and with same errupters im mining aprox 380kh/s with one errupter
Cheers for the reply. 20%+ is a significant increase, definitely worth a try.
Please also note, i'm using Debian (Linux) and this Gigabyte R9 280x hasn't been modded or clocked. With a small tweak to the config it's now stable @ 3.921Mh/s. Have you modded your bios / undervolted your 280x to achieve 4.4 mh/s?
EDIT: 3.921Mh/s stable using https://nicehash.com/software/#sgminer and updated config.
July 22, 2014, 06:37:27 AM
no bro, windows 7 x64 with 4gb ddr3 RAM
i imagine that it would go even faster on linux ... because my usb errupters mining aprox 300 kh/s per errupter on windows ... yesterday i put them to xubuntu and with same errupters im mining aprox 380kh/s with one errupter
i imagine that it would go even faster on linux ... because my usb errupters mining aprox 300 kh/s per errupter on windows ... yesterday i put them to xubuntu and with same errupters im mining aprox 380kh/s with one errupter
July 22, 2014, 06:33:02 AM
im mining more than a month @ 4.4 mh/s with 280x DC2 @ 1150mhz GPU, 1500mhz memory, 1.25v @ intensity 19
Hi Rux, that sure is running well, well done.
Under Win 7, O/C 280x I had it running @ 4.1 mh/s (not 4.4 mh/s, envious now!
). Is your 4.4 mh/s also under linux? The Gigabyte 280x i'm using under hasn't had it's bios flashed. July 22, 2014, 06:20:26 AM
anyone got a full 280x config to share?
Hi Vampiro4L,
I'm using the following config on Debian with a Gigabyte R9 280x using an old GA-8I945P Pro M/B with a PCI-Express V1* port (just from my experience, there's no degradation in mining using PCI-E 1.* with newer graphic cards).
Currently averaging 3.106Mh/s over the past 24 hours mining X11.
#!/bin/bash
export DISPLAY=:0
export GPU_MAX_ALLOC_PERCENT=100
export GPU_USE_SYNC_OBJECTS=1
./sgminer -k darkcoin-mod -o stratum+tcp://URL:PORT -u USER.USERNAME -p PASSWORD --no-submit-stale --thread-concurrency 8192 --intensity 20 -w 256 -g 2 --lookup-gap 2
I hope this helps.
im mining more than a month @ 4.4 mh/s with 280x DC2 @ 1150mhz GPU, 1500mhz memory, 1.25v @ intensity 19
July 21, 2014, 11:19:16 PM
anyone got a full 280x config to share?
Hi Vampiro4L,
I'm using the following config on Debian with a Gigabyte R9 280x (OOTB) using an old GA-8I945P Pro M/B with a PCI-Express V1* port (just from my experience, there's no degradation in mining using PCI-E 1.* with newer graphic cards).
Currently averaging 3.921Mh/s over the past 24 hours mining X11.
#!/bin/bash
export DISPLAY=:0
export GPU_MAX_ALLOC_PERCENT=100
export GPU_USE_SYNC_OBJECTS=1
./sgminer -k darkcoin-mod -o stratum+tcp://URL:PORT -u USER.USERNAME -p PASSWORD -I 18 -g 2 -w 256 --no-submit-stale --auto-fan --thread-concurrency 11200 --lookup-gap 2
I hope this helps.
EDIT: 3.921Mh/s stable using https://nicehash.com/software/#sgminer and updated config.
July 21, 2014, 06:16:05 PM
Felows ,which speeds do you reach with R9 280X on X14
July 21, 2014, 11:42:20 AM
Again in the Night the Rig close down SGMiner
Dont know why it closed. SGminer didnt try to get on the Backup Pool
I'm on the latest sgminer5 version available on PiMP and I'm getting similar stratum disconnects using the auto-switching TMB ports. I have setup a cron job to reboot every 6 hours as a workaround but the issue still randomly happens. I have lowered clocks but this seems to have no impact whatsoever.Code:
23:21:05] NH x15 multi extranonce change requested
[23:21:05] NH x15 multi difficulty changed to 0.100
[23:21:08] Accepted Coin 182 Diff 0.113/0.100 GPU 1 at NH x15 multi
[23:21:12] Accepted Coin 182 Diff 0.892/0.100 GPU 2 at NH x15 multi
[23:21:30] Accepted Coin 182 Diff 0.330/0.100 GPU 0 at NH x15 multi
[23:22:14] Accepted Coin 189 Diff 0.112/0.100 GPU 5 at NH x15 multi
[23:22:26] Accepted Coin 189 Diff 0.171/0.100 GPU 5 at NH x15 multi
[23:22:55] Accepted Coin 189 Diff 0.306/0.100 GPU 0 at NH x15 multi
[23:23:16] Accepted Coin 189 Diff 1.319/0.100 GPU 1 at NH x15 multi
[23:23:26] Accepted Coin 189 Diff 9.627/0.100 GPU 0 at NH x15 multi
[23:23:41] NH x11 multi alive, testing stability
[23:23:41] Accepted Coin 176 Diff 0.394/0.100 GPU 5 at NH x15 multi
[23:23:49] NH x11 multi stable for 30 seconds
[23:23:49] Switching to NH x11 multi
[23:23:54] Stratum connection to NH x11 multi interrupted
[23:23:54] NH x11 multi not responding!
[23:23:54] Switching to NH x15 multi
[23:24:50] thread was not cancelled in 60 seconds after restart_mining_threads
[23:24:50]
Summary of runtime statistics:
Dont know why it closed. SGminer didnt try to get on the Backup Pool
Anyone aware of this? Is it a Sgminer issue or TMB? It seems from previous posts that it probably is the former.
July 21, 2014, 09:48:59 AM
Cool... slowly testing.
Able to get 5.4MH stable with RI:225280 and 1025/1250, as well as the Luffa_Parallel trick. Will nudge it up from here and see if I can get the fabled 6MH.
Able to get 5.4MH stable with RI:225280 and 1025/1250, as well as the Luffa_Parallel trick. Will nudge it up from here and see if I can get the fabled 6MH.
July 21, 2014, 04:52:47 AM
try this
http://www.reddit.com/r/vertcoin/comments/298gqc/greenpool_x11_amd_144146_drivers_trick_for_extra/
http://www.reddit.com/r/vertcoin/comments/298gqc/greenpool_x11_amd_144146_drivers_trick_for_extra/
Wow. Confirmed, this works.
A little shaky on x15 though...
I'm behind... is this unnecessary now that we have 14.7
July 21, 2014, 02:54:39 AM
try this
http://www.reddit.com/r/vertcoin/comments/298gqc/greenpool_x11_amd_144146_drivers_trick_for_extra/
http://www.reddit.com/r/vertcoin/comments/298gqc/greenpool_x11_amd_144146_drivers_trick_for_extra/
Wow. Confirmed, this works.
A little shaky on x15 though...
I'm behind... is this unnecessary now that we have 14.7
July 21, 2014, 01:10:13 AM
try this
http://www.reddit.com/r/vertcoin/comments/298gqc/greenpool_x11_amd_144146_drivers_trick_for_extra/
http://www.reddit.com/r/vertcoin/comments/298gqc/greenpool_x11_amd_144146_drivers_trick_for_extra/
Wow. Confirmed, this works.
A little shaky on x15 though...
July 21, 2014, 12:54:39 AM
Hi, platinum4!
My level of knowledge does not allow to understand this magic completely :-)
If I have a different cards in the rig (7950 + 7850 + 7850), how can I to calculate intencity/rawintencity?
Total number of threads will be 1792*5 + 1024*5 + 1024*5 = 8960 + 5120 + 5120 = 19200. How it should be distributed to cards?
And a second question: is the method above suitable for nist5 only, or for x11/x13/x15 too?
idk, did you just try rawintensity: 84480 and see if it increased your results?
Yes. It is no significant rate changes from "intensity" : "17,20,20"...
July 20, 2014, 11:33:32 PM
is this the best x11 and x13 miner right now?
July 20, 2014, 11:04:18 PM
Here's how to nick up to 18M on nist5
Take your shaders and multiply by 5
For me was 2816x5 = 14080, this is your base thread concurrency if you specify an algo that doesn't exist, and it builds ckolivas with that TC
Next multiply this value by the total number of threads you are passing through your entire rig.
For me was 3 cards X 2 gpu-threads = 6 x 14080 = 84480 = xI: 30 as opposed to I:16=65536
Take your shaders and multiply by 5
For me was 2816x5 = 14080, this is your base thread concurrency if you specify an algo that doesn't exist, and it builds ckolivas with that TC
Next multiply this value by the total number of threads you are passing through your entire rig.
For me was 3 cards X 2 gpu-threads = 6 x 14080 = 84480 = xI: 30 as opposed to I:16=65536
Hi, platinum4!
My level of knowledge does not allow to understand this magic completely :-)
If I have a different cards in the rig (7950 + 7850 + 7850), how can I to calculate intencity/rawintencity?
Total number of threads will be 1792*5 + 1024*5 + 1024*5 = 8960 + 5120 + 5120 = 19200. How it should be distributed to cards?
And a second question: is the method above suitable for nist5 only, or for x11/x13/x15 too?
idk, did you just try rawintensity: 84480 and see if it increased your results?
July 20, 2014, 06:08:32 PM
anyone got a full 280x config to share?
July 20, 2014, 03:06:51 PM
Here's how to nick up to 18M on nist5
Take your shaders and multiply by 5
For me was 2816x5 = 14080, this is your base thread concurrency if you specify an algo that doesn't exist, and it builds ckolivas with that TC
Next multiply this value by the total number of threads you are passing through your entire rig.
For me was 3 cards X 2 gpu-threads = 6 x 14080 = 84480 = xI: 30 as opposed to I:16=65536
Take your shaders and multiply by 5
For me was 2816x5 = 14080, this is your base thread concurrency if you specify an algo that doesn't exist, and it builds ckolivas with that TC
Next multiply this value by the total number of threads you are passing through your entire rig.
For me was 3 cards X 2 gpu-threads = 6 x 14080 = 84480 = xI: 30 as opposed to I:16=65536
Hi, platinum4!
My level of knowledge does not allow to understand this magic completely :-)
If I have a different cards in the rig (7950 + 7850 + 7850), how can I to calculate intencity/rawintencity?
Total number of threads will be 1792*5 + 1024*5 + 1024*5 = 8960 + 5120 + 5120 = 19200. How it should be distributed to cards?
And a second question: is the method above suitable for nist5 only, or for x11/x13/x15 too?
July 20, 2014, 09:18:54 AM
Just started using this with my 5x7950 rig. It seems whenever the pool is set to X13, one of my GPU goes sick. X11 seemed stable for a while.
I've been running this rig in scrypt mode for months. I have a GPU go sick about once every 2 weeks. I simply reboot.
However, mining X13 it's going dead in a couple minutes.
Any suggestions? I've tried lowering the GPU clock for it, but that didn't make any difference.
Nope, allow me to introduce you to hamsi, it's an unforgiving bitch. I've been running this rig in scrypt mode for months. I have a GPU go sick about once every 2 weeks. I simply reboot.
However, mining X13 it's going dead in a couple minutes.
Any suggestions? I've tried lowering the GPU clock for it, but that didn't make any difference.
July 20, 2014, 09:09:07 AM
Just started using this with my 5x7950 rig. It seems whenever the pool is set to X13, one of my GPU goes sick. X11 seemed stable for a while.
I've been running this rig in scrypt mode for months. I have a GPU go sick about once every 2 weeks. I simply reboot.
However, mining X13 it's going dead in a couple minutes.
Any suggestions? I've tried lowering the GPU clock for it, but that didn't make any difference.
I've been running this rig in scrypt mode for months. I have a GPU go sick about once every 2 weeks. I simply reboot.
However, mining X13 it's going dead in a couple minutes.
Any suggestions? I've tried lowering the GPU clock for it, but that didn't make any difference.
July 19, 2014, 11:24:45 PM
I'm currently getting a virtual TON of "stale shares detected, discarding." Which variable(s) should I add or tweak to try and fix this problem? Is this normally an Intensity issue?
Thank you ahead of time!
try to dial back you intensity till your hashrate starts to dropThank you ahead of time!
sometimes if you set it too high you will get stale shares
also can be caused by latency to the pool server
if you are on a p2pool try to find one with the lowest latency
Code:
"no-submit-stale" : false,
Increase your expiry (and potentially scan-time if you have it set low too) first. Only decrease intensity if you're getting REAL stale shares.
I'm willing to bet that opet has expiry set to 1 or something equally silly.
Jump to: