X11mod, X13mod, X15 and catalyst 14.7 RC

[utahjohn]

Not doing anything wrong, sgminer v5 has been modified in that when you specity x11mod you actually get darkcoin-mod kernel.  Look at the binfile created by v5.  same thing happens with x13mod kernel specified, you get marucoin-mod bin file.
The x11mod and x13mod .cl posted in OP and the bin posted on OP do work great with sgminer 4.1.0

The optimized x11mod and x13mod .cl DO NOT WORK on sgminer v5

[tytanick]

sgmienr 4.1.0 wont accept x11mod.cl
hmm ?

[Amgclk65]

Hello..

So it kinda seems like everyone is running there gpu full tilt boogie on x11 etc ! Which is  fine, if you have cheap power rates. Im paying about .12 a killa watt. So its a bit high. I ran scypt for full throttle for about 4 months. I finally realized that running a heavy under volt was the way to go. It didn't really pay off to have the rig pulling massive watts form the wall. Heres a little example. One rig with 6 270 was pulling 1080 watts on scrypt. Hashing around 2900 kh/s. I undervolted to .950 and was able to get 2520 kh/s at 705 watts. So my question is has anyone found some good hashing power with new or old drivers on x11 while still pulling minimal watts from the wall?

[m0narch]

Hello..

So it kinda seems like everyone is running there gpu full tilt boogie on x11 etc ! Which is  fine, if you have cheap power rates. Im paying about .12 a killa watt. So its a bit high. I ran scypt for full throttle for about 4 months. I finally realized that running a heavy under volt was the way to go. It didn't really pay off to have the rig pulling massive watts form the wall. Heres a little example. One rig with 6 270 was pulling 1080 watts on scrypt. Hashing around 2900 kh/s. I undervolted to .950 and was able to get 2520 kh/s at 705 watts. So my question is has anyone found some good hashing power with new or old drivers on x11 while still pulling minimal watts from the wall?

x11 uses about half the power of scrypt which is another reason why it's so popular with GPU miners. Using the newest 14.6 drivers with any x11 supported sgminer version should give you good hashing at a much lower power cost compared to scrypt. Plus it'll be more profitable.

[jedimstr]

utahjohn - so continuing the conversation from the Wafflepool thread...

I backed up all my configs and updated to the PiMP 1.5.5-amd-14.4 distro image which has Catalyst 14.4.

Copied over your optimized cl files and the bin files (your X13 bin and someone else's optimized bin for X11).

Results are almost exactly the same as I had under the 13.12 drivers on 14.4:


Any higher on "some" of the GPU's core/mem speeds get me HW errors or SICK GPUs.

Playing with other values such as variations on intensity, shaders, GPU threads, etc, get me lower values than these.

Any ideas?

[forcefedvr6]

utahjohn - so continuing the conversation from the Wafflepool thread...

I backed up all my configs and updated to the PiMP 1.5.5-amd-14.4 distro image which has Catalyst 14.4.

Copied over your optimized cl files and the bin files (your X13 bin and someone else's optimized bin for X11).

Results are almost exactly the same as I had under the 13.12 drivers on 14.4:


Any higher on "some" of the GPU's core/mem speeds get me HW errors or SICK GPUs.

Playing with other values such as variations on intensity, shaders, GPU threads, etc, get me lower values than these.

Any ideas?

I've been seeing my highest hashrates using I=18.  If I go to 19 or higher, or 17 or lower, it will fall off.  

Try I=18 and then see if you can goose the memclocks up 10 at a time and see what happens.

(If I go above 1500 memclock, or  1100 engine clock, my gpus will start checking out.)

What are you using for gpu threads? 4 seems to work ok for me,  I will lose hash if I go to 1. I forget what happens if I go to 2 or 3.  

I have sapphire hd7950 though,  don't know much about the MSI cards other than they might drink a little more power.

Edit: Also wanted to add that I'm using the lasybear x11/x13 miner,  although I don't know if the modded x13 kernel loaded into a different sgminer basically would give the same performance. Maybe trying  that miner would help.  It is based  off of the "2% fee" miner but does not send hash out to anyone.

[utahjohn]

Forcefed may be on to something there I'm pretty sure i'm using lasybear's version of sgminer ... I forgotten where I got it, been quite a while ago.
Sorry I didn't get back to you sooner but I had to take a nap

[forcefedvr6]

Forcefed may be on to something there I'm pretty sure i'm using lasybear's version of sgminer ... I forgotten where I got it, been quite a while ago.

Link to the thread:

https://bitcointalk.org/index.php?topic=623409.0

[utahjohn]

I've seen "hamsi-expand-big" : "4"
in some configs scattered about bitcointalk threads ... any explanation what this is for?

[RoyalSands]

Anyone know how to get x15 on PiMP?

[dark8011]

on my 1g memory (or above) 5xxx and 6xxx cards ,the bitblockold algorithm works fine,but 512m cards can't run,says not enough memory.
I tried to decrease TC or increase LG,can't work neither.
seems that parameter "--thread-concurrency" and "--lookup-gap" don't play a part in Bitblockold algorithm.
Is there any other ways that can  decrease the memory occupancy in order to let my 512m cards run the x15 algo？

[utahjohn]

on my 1g memory (or above) 5xxx and 6xxx cards ,the bitblockold algorithm works fine,but 512m cards can't run,says not enough memory.
I tried to decrease TC or increase LG,can't work neither.
seems that parameter "--thread-concurrency" and "--lookup-gap" don't play a part in Bitblockold algorithm.
Is there any other ways that can  decrease the memory occupancy in order to let my 512m cards run the x15 algo？

Drop WS to 64 (or even 32 which I have not tried), gpu-threads 1.  However I never got my 5450 to work on X15 ...

[dark8011]

on my 1g memory (or above) 5xxx and 6xxx cards ,the bitblockold algorithm works fine,but 512m cards can't run,says not enough memory.
I tried to decrease TC or increase LG,can't work neither.
seems that parameter "--thread-concurrency" and "--lookup-gap" don't play a part in Bitblockold algorithm.
Is there any other ways that can  decrease the memory occupancy in order to let my 512m cards run the x15 algo？

Drop WS to 64 (or even 32 which I have not tried), gpu-threads 1.  However I never got my 5450 to work on X15 ...

I've already tried,but it didn't take effect

[utahjohn]

on my 1g memory (or above) 5xxx and 6xxx cards ,the bitblockold algorithm works fine,but 512m cards can't run,says not enough memory.
I tried to decrease TC or increase LG,can't work neither.
seems that parameter "--thread-concurrency" and "--lookup-gap" don't play a part in Bitblockold algorithm.
Is there any other ways that can  decrease the memory occupancy in order to let my 512m cards run the x15 algo？

Drop WS to 64 (or even 32 which I have not tried), gpu-threads 1.  However I never got my 5450 to work on X15 ...

I've already tried,but it didn't take effect

https://bitcointalk.org/index.php?topic=666252.msg7573845#msg7573845

https://bitcointalk.org/index.php?topic=666252.msg7573377#msg7573377

Make sure to delete the .bin file before restarting sgminer or your changed config will not be recompiled ...

[ErikW79]

Cant get my 280X work with new X15 sgminer, even did some Fire coin mining some days ago. Any idea? Thx

[ShibecoinSucks]

Hi everyone, I have been trying to get my Sgminer5.0 to mine X15 for the past few days. I'm having problems with the config file, evey config i try gives me no connection to the pool, or HW errors with invalid noncecount, also the other issue is low difficulty shares being rejected. I am using BAMT with SGMINER 5.0 and its the only way I can mine x15, if anyone has a config file i can try please I will pay for you help.

I'm using the bitblock kernel and this config to just try to get the x11 to work, but it still comes with low difficulty shares. Anytime i try another config with bitblock kernel or if i try to change this config i get invalid nonce count and HW errors. PLEASE HELP ME!

{
  "pools": [
    {
      "name":"Testpool X11",
      "url": "stratum+tcp://url1:4440",
      "user": "user",
      "pass": "x",
      "priority": "1",
      "profile": "x11"
    },
    {
      "name":"Testpool Scrypt",
      "url": "stratum+tcp://url2:3339",
      "user": "user",
      "pass": "x",
      "priority": "2",
      "profile": "scrypt"
    },
    {
      "name":"Testpool X11 with other profile",
      "url": "stratum+tcp://url3:4440",
      "user": "user",
      "pass": "x",
      "priority": "0",
      "profile": "x11test"
    },
    {
      "name":"Testpool Using default profile",
      "url": "stratum+tcp://url4:3333",
      "user": "user",
      "pass": "x"
    }
  ],
  "profiles": [
    {
      "name": "x11",
      "algorithm": "darkcoin-mod",
      "intensity": "19",
      "thread-concurrency": "10696,8192",
      "worksize": "128",
      "gpu-engine": "1100",
      "gpu-threads": "2",
      "gpu-fan": "75"
    },
    {
      "name": "scrypt",
      "algorithm": "ckolivas",
      "lookup-gap": "2",
      "intensity": "19,13",
      "thread-concurrency": "19656,8192",
      "worksize": "256",
      "gpu-engine": "1000,1065",
      "gpu-memclock": "1500",
      "gpu-threads": "1,2",
      "gpu-fan": "85",
      "gpu-powertune": "20"
    },
    {
      "name": "x11test",
      "algorithm": "darkcoin-mod",
      "device": "1",
      "intensity": "19",
      "thread-concurrency": "10696,8192",
      "worksize": "512",
      "gpu-engine": "1100",
      "gpu-threads": "2",
      "gpu-fan": "75"
    }
  ],
  "failover-only": true,
  "default-profile": "scrypt",
  "temp-cutoff": "95,95",
  "temp-overheat": "90,90",
  "temp-target": "80,80",
  "gpu-memdiff": "0,0",
  "shares": "0",
  "kernel-path": "/usr/local/bin",
  "api-allow": "W:127.0.0.1",
  "api-listen": true,
  "api-mcast-port": "4028",
  "api-port": "4028",
  "expiry": "1",
  "failover-switch-delay": "60",
  "gpu-dyninterval": "7",
  "gpu-platform": "-1",
  "hamsi-expand-big": "4",
  "log": "5",
  "no-pool-disable": true,
  "no-client-reconnect": true,
  "queue": "0",
  "scan-time": "1",
  "tcp-keepalive": "30",
  "temp-hysteresis": "3"
}

[golden0707]

Hi everyone! Im sorry for not exect topic theme , but please tell my. Does amd 14.6 drivers no longer support scrypt/Nscrypt mining ? Im getting only HWs at any config.
2*270x+3*280x.

It worked just fine on BAMT 1.3-1.6 and PIMP 14.4 drivers.


Thanks.

P.S.

StatusTemp   Fan            Rate                     Pool                ccept/Reject                   I   HW       Core   Memory   Power
0   64.0 C   30% (1341)   2808 Kh/s   wafflepool.com:3331   557 / 7   1.24%   19   0   1155 Mhz   1500 Mhz   1.206v
1   57.0 C   30% (1579)   2822 Kh/s   wafflepool.com:3331   527 / 5   0.94%   19   0   1155 Mhz   1500 Mhz   1.206v
2   62.0 C   44% (1846)   4355 Kh/s   wafflepool.com:3331   854 / 9   1.04%   19   0   1155 Mhz   1500 Mhz   1.163v
3   65.0 C   41% (1611)   4374 Kh/s   wafflepool.com:3331   876 / 5   0.57%   19   0   1155 Mhz   1500 Mhz   1.200v
4   64.0 C   42% (1826)   4353 Kh/s   wafflepool.com:3331   848 / 6   0.70%   19   0   1155 Mhz   1500 Mhz   1.170v


My stats for X11 mining. GPUs as written.

[induktor]

Cant get my 280X work with new X15 sgminer, even did some Fire coin mining some days ago. Any idea? Thx

What version?
I am using sgminer-5.0-pre-release-2014-06-25-win32
I know it is a pre-release, but hey, it works pretty well, so why change it?

my cards are MSI 280X Gaming 3G, driver 14.4, win 7
settings: (mine.bat)

Code:

setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
sgminer.exe --algorithm bitblock -o stratum+tcp://east01.us.trademybit.com:6660 -u USERNAME -p PASS -w 128 --lookup-gap 2 -I 18 -g 4 --gpu-powertune 10 --gpu-engine 1030 --gpu-memclock 1500 --gpu-fan 35-80 --temp-target 62 --temp-overheat 67 --temp-cutoff 74 --auto-fan --hamsi-expand-big 1

I am using the modded bin, posted here, I get 2.9M per card at 1030 Mhz in X15
if you cannot find the modded bin or the miner, contact me, I will upload it to mega or something.

anyone with R9 280X getting better results, can please post settings and what you are using?
thanks!

[utahjohn]

I have not looked at sgminer-dev v5 for a while are there any new windows binaries that are current with the dev tree?
I am looking forward to ability to switch kernels on the fly   (last time I tried v5 I had GPU's going DEAD occasionally).  Anyone with recent experience please post your findings, I am most interested in X11 X13 X15 and Groestl switching capability.

[utahjohn]

Yep, I'm like the large freighter, it takes me much longer to turn the ship. I'm paying closer attention once again, it's just such a pain keeping up to date, but that said, it's missed profit if I don't. Really need to get this algorithm switching working with CGminer and SGminer 5. That is my next goal.

Let me know when u get it all worked out, a working solution with sgminer-dev v5 is also my goal.

Interesting sidenote ... I find my 7950's do better than 280x's on groestl algo, Don't know why

Last time I tried cgwatcher and cgremote (months ago) I found my hashrates were lower than without.  Maybe API polling has this effect on the miner IDK.

Have two rigs (3x7970 and 4x7950) working right now using multi-algo.. Seems I had it figured out yesterday, just needed to restart the machines for whatever reason. I've witnessed them switch 3-4 times each, very interesting. Will keep it going while I sleep before changing over any others.

Cgwatcher and CGremote is a must for me, it gives me one panel to see all my rigs, and it is used often.