[ANN][X11/X13] X11 (Darkcoin)/X13 (Marucoin) miner (based on sph-sgminer)

[ballot]

Code:

set GPU_MAX_ALLOC_PERCENT=100
set GPU_USE_SYNC_OBJECTS=1 

sgminer.exe -k x11mod --rawintensity 1306624 -g 1 --shaders 2560 -w 256 --thread-concurrency 24577 --no-submit-stale -o stratum+tcp://x.rigs.eu.betarigs.com:6519 -u x-x-p x -o stratum+tcp://drkpool.com:3333 -u x.1 -p x 
pause

i use this config

but temperatures and fan rpms  so high?   

[thectspot]

~Snip

Using BAMT 1.6 with these setting on 4 Sapphire Tri-X R9 290 (non x) but can't get over 2.5MH/s per card.  I downloaded and installed the SGminer fork from Benmagro's github: https://github.com/benmagro/Add-SGminer-X11X13Mod-Miner-To-BAMT.  Any suggestions would help.  Thanks!

How much RAM do you have in your system? When I firs purchased my rig I was told by a friend that I needed more system RAM than I had total GPU RAM. I didn't believe him, but for some reason apparently he's correct and having less system RAM than total GPU RAM can effect hash rate negatively. I run 16GB of System RAM, but another difference we have in our setup that is more obvious is that I'm on Win7 running 13.12 CCC drivers.

Just noticed as well that you're using a miner source from "Benmagro", I'm not sure who that is, but try compiling Lasybears sph-sgminer_x11mod_b2_2min_SICK version, as that is the one I'm still using. If you search near the beginning of this thread I believe there are some instructions for compiling the source on BAMT. Good luck!

I have 8GB of ram on my systems, a couple have 4 but there is no difference in hashing amongst those.  I will try one with 16GB and see what it does.  The BAMT 1.6 version I am using has the 13.12 drivers installed.  I will take a look at the SICK version lasybear that you mentioned.  Also going to try the sgminer5 that is out that supposedly has the lasybear forks built into them. 

[Kifissia]

No need for extreme amounts of RAM. I mine on systems with 2GB RAM.

[smalltimer50]

Hey guys, love the miner but I'm having a super frustrating problem (I recently switched to x11 from scrypt). I use the miner on two computers, one upstairs is a 5850, and 270x which hashes just fine and never crashes. The second miner is the basement --two R9 270s, one R9 270x, and two R9 290s. This rig hashes fine for 20 mins - 2 hours until I get the message: "stratum connection to pool 0 interrupted", and sgminer just hangs and stops mining. The computer doesn't crash and I can close sgminer and restart again just fine. I get this same message every time it crashes! I know I have it set up right cause I get 12-13MH and wafflepool accepts my shares just fine. I've run this rig for months on scrypt and never had internet or connection problems so it is definitely not my computer / internet. 

Here is my config file if it is any use.

{
"pools" : [
   {
      "url" : "stratum+tcp://useast.wafflepool.com:3331",
      "user" : "my address",
      "pass" : "d=0.16"
   },
   {
      "url" : "stratum+tcp://uswest.wafflepool.com:3331",
      "user" : "my address",
      "pass" : "d=0.16"
   },
   {
      "url" : "stratum+tcp://eu.wafflepool.com:3331",
      "user" : "my address",
      "pass" : "d=0.16"
   },
   {
      "url" : "stratum+tcp://sea.wafflepool.com:3331",
      "user" : "my address",
      "pass" : "d=0.16"
   }
]
,
"intensity" : "18",
"worksize" : "256",
"kernel" : "x11mod",
"lookup-gap" : "2",
"thread-concurrency" : "8192",
"shaders" : "0",
"gpu-threads" : "2",
"gpu-engine" : "0-0",
"gpu-fan" : "0-0",
"gpu-memclock" : "0",
"gpu-memdiff" : "0",
"gpu-powertune" : "0",
"gpu-vddc" : "0.000",
"temp-cutoff" : "95",
"temp-overheat" : "85",
"temp-target" : "75",
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "28",
"failover-switch-delay" : "60",
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"log" : "5",
"no-pool-disable" : true,
"queue" : "1",
"scan-time" : "7",
"tcp-keepalive" : "30",
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin"
}

If anyone can help solve my problem, I'd love to throw them a small amount of BTC!

Thanks!

[thectspot]

No need for extreme amounts of RAM. I mine on systems with 2GB RAM.

I didn't think that RAM was really an issue.  From what I have experience, read, and talked to others, the main thing is a single rail good PowerSupply, Good Motherboard, and the correct settings.  Processor and Ram can be kind of minimal.

Still wondering why I can't get the speeds you guys are getting though.  Still at around 2.5MH/s with this miner on BAMT 1.6 w/Sapphire R9 290 Tri-x for x13 mining: https://github.com/sgminer-dev/sgminer

[adaseb]

Anybody get any virus issues all of a sudden?

Ran a scan and Ad-aware detected a Trojan horse virus.


12/53 viruses found



https://www.virustotal.com/en/file/0e3cbb6b801920bb78c83e8800dcb73b0c2b743793a3485d92c34aba39be9b8b/analysis/

[thectspot]

Here is what i've got and you guys can give me your advice.  I see all your posts about getting some high hashrates but I cannot get over about 2.5MH/s on x13 with the newest sgminer from https://github.com/sgminer-dev/

My setup is as follows on all of my rigs:
BAMT 1.6 on Sandisk USB (sizes from 8GB - 16GB)
Sapphire R9 290 Tri-x 4GB Video Cards
Two Seasonic 850W Single Rail Power Supplies
Gigabyte GA-990FXA-UD3 Motherboard
4-8GB Ram on each machine
AMD Sempron Processor
Hard Wired Ethernet Connection

Any help is appreciated and I don't mind tipping if it does help out.  

Below are two of my sgminer configs that have been successful at 2.5MH/s:
{
"pools" : [
   {
      "url" : "http://us-east01.miningrigrentals.com:3333",
      "user" : "user",
      "pass" : "pass"
   }
],
"algorithm" : "marucoin-mod",
"rawintensity" : "1306624",
"shaders" : "2560",
"worksize" : "256",
"thread-concurrency" : "24577"
}

&

{
"pools" : [
   {
      "url" : "http://us-east01.miningrigrentals.com:3333",
      "user" : "user",
      "pass" : "pass"
   }
],
"intensity" : "17",
"kernel" : "x13mod",
"lookup-gap" : "2",
"thread-concurrency" : "8192",
"gpu-engine" : "1000",
"gpu-fan" : "40-95",
"gpu-memclock" : "1400",
"gpu-powertune" : "20",

"temp-cutoff" : "96",
"temp-overheat" : "95",
"temp-target" : "75",

"api-listen": true,
"api-port": "4028",
"api-allow": "W:127.0.0.1",

"auto-fan" : true,
"auto-gpu" : true,
"gpu-threads" : "2",
"kernel-path" : "/usr/local/bin"
}

[thectspot]

Has anyone noticed that after the new increased performance on the new sgminer it seems like the mining rigs go down more often than before.  We have 40 triple r290 gpu miners using the old slower sgminer and everyday 2-3 random miners go down.  down as in:

1. sgminer quits by itself, cgwatcher still working.  if we restart the miner, gpu1 usually shows 1/3 the normal hashrate.  Reboot windows and everything is fine.
2. sgminer shows pools being dropped, so cgremote shows mining darkcoin but do not show a pool.  reboot system then works fine.
3. rarely would windows be locked up and require a reset on the system

with the new faster sgminer using the same exact settings, only added the -x11mod the 2-3 random miners become 6-7 random miners.  We've tried to lower intensity from 19 to 18 didnt help on decreasing the crashes.

Any help will be appreciated.

I guess, too much overclocked.
Settings was good for a "classic" darkcoin kernel (single kernel) may not compliant for x11mod (multi kernel). Look this thread for a optimal settings for R9 290.

What are you using for OS for the miners?

[Jherek]

Hello, I am using sgminer to mine x13 coins.
I get lot of "Discarded work" and only 2-3 shares per 10 minutes or so. Is this normal?

[sharnalk]

Hi,

I'd like to ask to developpers, if i want to et familiar with the algorithms used to mine,(and maybe one day improving them),  where should i start ? I'm intrested in X11/X13 but it dosen't seem to be the right algo to start with, since, it's a combination of other algos.

Is there a "documentation" for the code ? And some white papers which explains the way the mining works ?

[neurosponge]

Hey guys, love the miner but I'm having a super frustrating problem (I recently switched to x11 from scrypt). I use the miner on two computers, one upstairs is a 5850, and 270x which hashes just fine and never crashes. The second miner is the basement --two R9 270s, one R9 270x, and two R9 290s. This rig hashes fine for 20 mins - 2 hours until I get the message: "stratum connection to pool 0 interrupted", and sgminer just hangs and stops mining. The computer doesn't crash and I can close sgminer and restart again just fine. I get this same message every time it crashes! I know I have it set up right cause I get 12-13MH and wafflepool accepts my shares just fine. I've run this rig for months on scrypt and never had internet or connection problems so it is definitely not my computer / internet. 

Here is my config file if it is any use.

{
"pools" : [
   {
      "url" : "stratum+tcp://useast.wafflepool.com:3331",
      "user" : "my address",
      "pass" : "d=0.16"
   },
   {
      "url" : "stratum+tcp://uswest.wafflepool.com:3331",
      "user" : "my address",
      "pass" : "d=0.16"
   },
   {
      "url" : "stratum+tcp://eu.wafflepool.com:3331",
      "user" : "my address",
      "pass" : "d=0.16"
   },
   {
      "url" : "stratum+tcp://sea.wafflepool.com:3331",
      "user" : "my address",
      "pass" : "d=0.16"
   }
]
,
"intensity" : "18",
"worksize" : "256",
"kernel" : "x11mod",
"lookup-gap" : "2",
"thread-concurrency" : "8192",
"shaders" : "0",
"gpu-threads" : "2",
"gpu-engine" : "0-0",
"gpu-fan" : "0-0",
"gpu-memclock" : "0",
"gpu-memdiff" : "0",
"gpu-powertune" : "0",
"gpu-vddc" : "0.000",
"temp-cutoff" : "95",
"temp-overheat" : "85",
"temp-target" : "75",
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "28",
"failover-switch-delay" : "60",
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"log" : "5",
"no-pool-disable" : true,
"queue" : "1",
"scan-time" : "7",
"tcp-keepalive" : "30",
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin"
}

If anyone can help solve my problem, I'd love to throw them a small amount of BTC!

Thanks!

Hi, I have the same issue. I was googling some advice with no luck...
I will be happy to share my experience:

- decreasing intensity has no positive effect,
- decreasing engine clock was an improvement of stability with no significant hashrate decrease,
- using default GPU BIOS (without memory timing optimization) seems like a solution. (so far 3 days of stable mining, heureka).

I was using modified GPU BIOS with optimized memory timing increasing hashrate when mining with scryp algo. When mining with X11 algo., using default GPU BIOS (default mem. timing, default voltage) is not decreasing the hashrate.

I have 4 GPU Saphire 280x, two of them Dual-x, two of them Vapor-x set on:
--------------------------------------------------------------------------------
 GPU 0:  68.0C 1679RPM | 3.004M/2.894Mh/s | R:  0.6% HW:0 WU:0.041/m I:17
 GPU 1:  68.0C 1450RPM | 3.116M/2.999Mh/s | R:  0.3% HW:0 WU:0.042/m I:17
 GPU 2:  65.0C 1041RPM | 3.119M/2.998Mh/s | R:  0.8% HW:0 WU:0.043/m I:17
 GPU 3:  67.0C 1527RPM | 3.001M/2.890Mh/s | R:  0.3% HW:0 WU:0.040/m I:17
--------------------------------------------------------------------------------
GPU 0: 3.0 / 2.9 Mh/s | A:1888  R:10  HW:0  U:1.51/m  I:17  xI:0  rI:0
68.0 C  F: 37% (1628 RPM)  E: 1040 MHz  M: 1500 Mhz  V: 1.225V  A: 99%  P: 0%
Last initialised: [2014-06-17 22:25:37]
Thread 0: 1.7 Mh/s Enabled ALIVE
Thread 1: 1.3 Mh/s Enabled ALIVE

GPU 1: 3.1 / 3.0 Mh/s | A:2036  R:7  HW:0  U:1.63/m  I:17  xI:0  rI:0
67.0 C  F: 39% (1446 RPM)  E: 1080 MHz  M: 1500 Mhz  V: 1.200V  A: 99%  P: 0%
Last initialised: [2014-06-17 22:25:37]
Thread 2: 1.7 Mh/s Enabled ALIVE
Thread 3: 1.4 Mh/s Enabled ALIVE

GPU 2: 3.1 / 3.0 Mh/s | A:2104  R:12  HW:0  U:1.68/m  I:17  xI:0  rI:0
65.0 C  F: 23% (1042 RPM)  E: 1080 MHz  M: 1500 Mhz  V: 1.200V  A: 99%  P: 0%
Last initialised: [2014-06-17 22:25:37]
Thread 4: 1.7 Mh/s Enabled ALIVE
Thread 5: 1.4 Mh/s Enabled ALIVE

GPU 3: 3.0 / 2.9 Mh/s | A:1932  R:5  HW:0  U:1.55/m  I:17  xI:0  rI:0
66.0 C  F: 32% (1523 RPM)  E: 1040 MHz  M: 1500 Mhz  V: 1.225V  A: 99%  P: 0%
Last initialised: [2014-06-17 22:25:37]
Thread 6: 1.7 Mh/s Enabled ALIVE
Thread 7: 1.3 Mh/s Enabled A

total 12,2 Mh/s… using bootable USB with updated PIMP 1.55 (pimpupdate of X11/X13mod miner did not solve the problem).

Hope this helps, anyone with more experience please comment…

Let the coins flow through you…

[timk225]

smalltimer50 - I have that problem too and have had it for a while and it is very annoying.  Nothing like the feeling of coming home from work to see that one or more of my mining PCs crapped itself 10 minutes after I walked out the door in the morning!  Much wasted mining time!!!

Is there a way in sgminer 4.1.0 to make it wait longer before declaring a disconnect or to make it reconnect itself?  I looked into that CGWatcher program a while back but it got too confusing very quickly.

I run the x11 mod algorithm now on windows 7 and 8 machines.  All have the same OS and same miner software, yet among the 3 computers, one rarely diconnects (win 7), one might discon 1-2 times a day (win 7), and one discons 4-6 times a day and it is very maddening (win 8.1).

All 3 PCs are currently ethernet cabled to an 8 port Cisco switch, so they are all getting the same signal from the same line.

None of my GPUs have any BIOS or voltage mods.

[smalltimer50]

Hey guys, here is a pic of sgminer when it freezes. In this instance it froze @ around 14 minutes into mining. It will do this randomly from 10 minutes in to 2 1/2 hours in.

https://i.imgur.com/D3j98Zu.jpg

I get those two messages when sgminer crashes everytime! "Stratum connection to Pool 0 interrupted" and the last one "Pool 0 difficultly changed to 0.160". Windows does not crash and I can easily restart sgminer. This is definitely not an internet problem. As I said before I ran scrypt mining on this same machine for months without problem. Longest uptime was 2 months straight without rebooting or crashing cgminer! To double check I ran cgminer with scrypt when I was @ work and all was well when I got home. Booted up x11 and the pic above happened. Boot with a config file or just a .bat... doesn't make a difference, both crash.

More information on my setup for those looking to help: 2 R9 290s (Gigabyte and ASUS), 2 R9 270s (ASUS), and 1 MSI R9 270x -- 4 GB of ram. I am running windows 8.1 currently with the 13.12 AMD drivers. I am literally pulling my hair out cause I have no solution to this problem! I don't know what I could change in the config to help this... lowered intensity, fiddled with the clocks -- all which did not help.

Big fat 0.015 BTC to anyone that can get me running stable!!

[devisger]

Smalltimer, I ran into a problem alot like yours, after many hours pulling hair, turns out I was running out of memory.
Upgraded from 4GB to 8GB solved all my problems.

[ebliever]

I have 8 GB RAM and am still having problems as well with frequent crashes. In my case the system generally goes dead (nothing on screen) but does not reboot. (If it blue-screened, I have it set to reboot so that wouldn't be such a big deal.) In other cases one GPU goes sick (drops to 40% hashrate), in which case I have CGWatcher set to restart the machine to restore it to 100%. I lose a lot of time and leases though with the full crashes. I've cut back to stock engine/memory speeds on my four 290X's and it has not helped, nor has adjusting intensity, thread concurrency, or anything else I can think of. It was much better (not perfect, but much better) with scrypt mining for the prior 3-4 months.

I think the common thread for most of us seems to be the use of 290 or 290X GPU's with this miner. Does that provide any clue?

[yudhistira]

Hey guys, here is a pic of sgminer when it freezes. In this instance it froze @ around 14 minutes into mining. It will do this randomly from 10 minutes in to 2 1/2 hours in.



I get those two messages when sgminer crashes everytime! "Stratum connection to Pool 0 interrupted" and the last one "Pool 0 difficultly changed to 0.160". Windows does not crash and I can easily restart sgminer. This is definitely not an internet problem. As I said before I ran scrypt mining on this same machine for months without problem. Longest uptime was 2 months straight without rebooting or crashing cgminer! To double check I ran cgminer with scrypt when I was @ work and all was well when I got home. Booted up x11 and the pic above happened. Boot with a config file or just a .bat... doesn't make a difference, both crash.

More information on my setup for those looking to help: 2 R9 290s (Gigabyte and ASUS), 2 R9 270s (ASUS), and 1 MSI R9 270x -- 4 GB of ram. I am running windows 8.1 currently with the 13.12 AMD drivers. I am literally pulling my hair out cause I have no solution to this problem! I don't know what I could change in the config to help this... lowered intensity, fiddled with the clocks -- all which did not help.

Big fat 0.015 BTC to anyone that can get me running stable!!

modify your worksize, gpu engine and intensity

I have 2 R280X worksize 128, gpu engine 1130 and I 21 get ~3.3Mhs stable, if gpu engine 1140 (crash), I 20 (to much reject), worksize 256 (blank screen/crash)

sgminer --kernel x11mod -o stratum+tcp://drkpool.com:3333 -u x -p x -I 21 --worksize 128 -g 2 --gpu-powertune 20 --gpu-engine 1130 --gpu-memclock 1500 --thread-concurrency 8192 --auto-fan --gpu-fan 40-70 --temp-cutoff 85 --temp-overheat 80

10 days for 1 DRK coin, maybe 2 years to get my money back 

[jenveno]

Getting 3.3 mh/s on r9-280x's with


"intensity" : "18",
"kernel" : "x11mod",
"worksize" : "128",
"gpu-engine" : "1108",
"gpu-memclock" : "1500",
"gpu-powertune" : "20",
"gpu-threads" : "2"

[tajnost]

to everyone having some issues with hawaii r9 290x cards I recommend my settings:
4.1MH/s x11
-I 16 -g 4 -w 256 --thread-concurrency 24000 --gpu-memclock 1250 --gpu-engine 1025 (that's right INTESITY 16!!! anything higher will cause hashdrop or crash, i found intensity 15 works just as good)
Here's me with two reference asus and gigabyte cards using these same settings. I'm also using 14.6beta drivers and believe it or not crossfire enabled.. If i try disable crossfire with this new driver miner will crash 
http://next-level.co.nz/troy/290x-conf.jpg

[COOLERbyPSP]

> with hawaii r9 290x cards I recommend my settings:
4.1MH/s x11

280x gives me ~4.3 Mh\s =P
http://cgminermonitor.com/Shared/c613d171ae234e87b1cb487f917677131

* COOLERbyPSP RUNS

[crazyearner]

to everyone having some issues with hawaii r9 290x cards I recommend my settings:
4.1MH/s x11
-I 16 -g 4 -w 256 --thread-concurrency 24000 --gpu-memclock 1250 --gpu-engine 1025 (that's right INTESITY 16!!! anything higher will cause hashdrop or crash, i found intensity 15 works just as good)
Here's me with two reference asus and gigabyte cards using these same settings. I'm also using 14.6beta drivers and believe it or not crossfire enabled.. If i try disable crossfire with this new driver miner will crash 

hitting blocks with only 2 gpus that's some going that. What is your average block turn around with them 2 cards as am considering to turn my gpus back on.