FREE Newsletter for People High On Coins!

Stay ahead of the pack with our newsletter and receive "RIG of the Month", get free help from author, get FREE tips/tricks for your litecoin rig, stay updated on what's HOT with Litecoin rigs right now.



Get your Copy of "Rig of the Month!" Today!



No spam. We promise.

Latest Optimized CGMiner Configuration for Gridseed Blades!

optimized-cgminer-gridseed-blade
Well, just wanted to do a short update on optimizing the Gridseed Blades a bit more.

I found that you can actually run these Gridseed Blades at 850Mhz just fine, there’s some more hardware errors but hashing is a bit faster and getting around 2.879Mh/s per blade.

Here’s my cgminer.conf file:

{
"pools": [
{
"url": "stratum+tcp://us.clevermining.com:3333",
"user": "1NqW6oZ5bvLPjWfr6DrzUhLF8X9iLA7TVW",
"pass": "123123"
},
{
"url": "stratum+tcp://192.168.2.254:22550",
"user": "DFMVvKYruZKkuAapuHx1wHvZPxPYFayAZa",
"pass": "123123"
},
{
"url": "stratum+tcp://mining.usa.hypernova.pw:3333",
"user": "zedomax.blade1",
"pass": "123123"
},
{
"url": "stratum+tcp://zedomax.blogdns.com:8888",
"user": "DKvhL9zroRNV7D683ze1BRFQdWSw3KhXw6",
"pass": "123123"
},
{
"url": "stratum+tcp://atron.blogdns.com:80",
"user": "DKvhL9zroRNV7D683ze1BRFQdWSw3KhXw6",
"pass": "123123"
}
],
"gridseed-options": "baud=115200,freq=850,chips=40,modules=1,usefifo=0",
"hotplug": "30",
"worksize": "1",
"kernel": "scrypt",
"thread-concurrency": "50000",
"lookup-gap": "0",
"gpu-threads": "2",
"queue": "0",
"scan-time": "1",
"expiry": "1",
"auto-fan": true,
"scrypt": true,
"api-listen": true,
"api-allow": "W:192.168.2.0/24",
"api-port": "4028",
"kernel-path": "/usr/local/bin"
}

I found that these Gridseed Blades run better with 2 GPU thread and a high concurrency of around 50000 as you can see here. Not sure exactly why but they do seem to hash a bit faster with higher thread concurrency. If you have better optimized settings, don’t forget to share it with our users by using the comment box below!

Like my tutorial? You can send me coins!
LTC: LVvcUvmkXGnDGzEod2zVXfwb7b3C76fD4L
DOGE: D6f3F8ohqGq9dpouS66mkNLeSFpt4RtT6h


Need Help? Follow/add me on Google+, Facebook, or Twitter!
GooglePlus
Facebook
Twitter
Want to stay updated on latest Litecoin rig news?
Sign up for our High On Coins Newsletter here so you get Rig of the month and more!
First time to digital currency?
Please see What is a Litecoin? FIRST!!!

24 thoughts on “Latest Optimized CGMiner Configuration for Gridseed Blades!

    1. Max Lee Post author

      dtbartle doesn’t report the megahashes correctly for Gridseed Blades, JMoridca is the one that has it fixed.

      Reply
    1. Max Lee Post author

      It’s great, the megahashes reported are usually right-on or slightly less but the payouts are pretty good, always above average. Highly Recommended. http://CleverMining.com Pays in bitcoins. Oops I sound like an ad.

      Reply
        1. Max Lee Post author

          Check your rigs and make sure you are getting full 5.2Mh/s, also check your WU rates on CGMiner also if you graphic rig.

          Reply
  1. Mark

    Hi Max, what would I be getting for the WU value? im getting around 1.5/m is it normal. its showing 2.878 Mh/s per side of the blade but on the pool side its showing maximum 4.2 Mh/s. Do you think there’s an issue with the blade?

    Reply
    1. Max Lee Post author

      Optimized, you should be getting around 4.5/m for WU value although it’s not super accurate. Raising it will def. help hashing power.

      Are you using the configuration on this page?

      Reply
  2. Nuno

    Hi!

    I am currently running 3 gridseeds on a raspberry pi and just received a Gridseed Blade. I want to run the blade as well as the gridseeds on the same raspberry pi. Is that possible and if so, how would you configure the cgminer.conf file to do this?

    Reply
    1. Max Lee Post author

      You will need to run two separate instances of two different CGMiners. It’s gonna be a bit complex to explain here but I don’t recommend that, just run them on two separate Pis as it will be more stable.

      Reply
  3. Wayne

    Fan went out my blade after two weeks. I called about returning it and I’m not getting any feedback therefore I thought I would reset everything back up. I’m seeing 2.8Mhs on each blade. Accepts are staying at 0 and Work Utility is 0. I’m assuming the blades are fried. Does anyone have any comments with the exception of RIP?

    Reply
  4. Mark

    Hi,
    I’m pretty new into mining and bought a G-blade. What should be normal WU rates for my blade running at 800 MHz?
    I’m getting values of about 2.2 – 2.7 per blade. Does this looks like normal values? I don’t use a config file just a bat file.

    Thanks.

    Reply
  5. Randy

    First let me start by saying this has been a great help. I’m use to bfgminer and cgminer but my g-blades came with ready to use cpuminer from zoomhash. I can NOT stand cpuminer. “sudo screen -ls” “sudo screen -x xxxx.x” can not see all the screens on one screen. It was great to see cgminer for raspberry pi. I wish I found it sooner.

    I do have to say that cpuminer was getting me 22MH on a Multipool but when I got cgminer and used this config I was getting 16MH. cgminer stated that I was getting 23MH + but the HW rates where high. You stated this in this post. 850 MHz is what I’m use to with cpuminer but I just changed this posted config file back to 838 MHz and I’m getting 22MH with little to no HW on my multipool.

    Here’s what I change in this config file.
    freq=838
    baud=230400
    hotplug=5
    Everything else is the same.

    login as: root
    root@192.168.1.149‘s password:
    Linux raspberrypi 3.10.25+ #622 PREEMPT Fri Jan 3 18:41:00 GMT 2014 armv6l

    The programs included with the Debian GNU/Linux system are free software;
    the exact distribution terms for each program are described in the
    individual files in /usr/share/doc/*/copyright.

    Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
    permitted by applicable law.
    Last login: Thu Jun 26 14:20:19 2014 from 192.168.1.7
    root@raspberrypi:~# cgm
    There is no screen to be attached matching cgm.
    root@raspberrypi:~# sudo screen -ls
    There is a screen on:
    2199.cgm (26/06/14 14:23:27) (Detached)
    1 Socket in /var/run/screen/S-root.

    root@raspberrypi:~# cgm
    cgminer version 3.7.2 – Started: [2014-06-26 14:23:34]
    ——————————————————————————–
    (5s):22.52M (avg):22.66Mh/s | A:628224 R:15360 HW:50 WU:35.3/m
    ST: 1 SS: 0 NB: 120 LW: 9069 GF: 0 RF: 0
    Connected to uswest.wafflepool.com diff 512 with stratum as user 1QJoj61hmoBYQg8j4YEhxLJDxRjGVyYMtw_RBP1
    Block: 75a0b4df… Diff:38 Started: [14:58:47] Best share: 2.51M
    ——————————————————————————–
    [P]ool management [S]ettings [D]isplay options [Q]uit
    GSD 0: 48ED655F3137 838 MHz | 2.837M/2.836Mh/s | A:86528 R:2048 HW: 1 WU: 4.9/m
    GSD 1: 48FD814A3137 838 MHz | 2.837M/2.833Mh/s | A:82432 R:2048 HW: 6 WU: 4.6/m
    GSD 2: 48FB727A3137 838 MHz | 2.837M/2.837Mh/s | A:72704 R:2048 HW: 3 WU: 4.1/m
    GSD 3: 48E0565B3137 838 MHz | 2.837M/2.842Mh/s | A:84480 R:1536 HW: 0 WU: 4.7/m
    GSD 4: 48FD824E3731 838 MHz | 2.838M/2.836Mh/s | A:80384 R:2048 HW:13 WU: 4.5/m
    GSD 5: 48FC6F5E3731 838 MHz | 2.838M/2.835Mh/s | A:81408 R:2560 HW: 1 WU: 4.6/m
    GSD 6: 48F975483430 838 MHz | 2.838M/2.839Mh/s | A:63488 R: 512 HW:21 WU: 3.5/m
    GSD 7: 48F2633A3430 838 MHz | 2.838M/2.838Mh/s | A:77824 R:2560 HW: 5 WU: 4.4/m
    ——————————————————————————–

    [2014-06-26 14:58:52] Accepted 5d8c38ba Diff 701/512 GSD 5 pool 0
    [2014-06-26 14:58:52] Accepted 31ded4d1 Diff 1.31K/512 GSD 5 pool 0
    [2014-06-26 14:58:53] Accepted 0ce35fbf Diff 5.08K/512 GSD 5 pool 0
    [2014-06-26 14:58:56] Accepted 0d9b61fc Diff 4.82K/512 GSD 4 pool 0
    [2014-06-26 14:58:59] Accepted 6611934e Diff 642/512 GSD 3 pool 0
    [2014-06-26 14:58:59] Accepted 0cd3c6cc Diff 5.11K/512 GSD 0 pool 0
    [2014-06-26 14:59:00] Accepted 23736e63 Diff 1.85K/512 GSD 4 pool 0
    [2014-06-26 14:59:02] Accepted 70447ad9 Diff 584/512 GSD 1 pool 0
    [2014-06-26 14:59:03] Accepted 0381eb5c Diff 18.7K/512 GSD 3 pool 0
    [2014-06-26 14:59:03] Accepted 6e513109 Diff 594/512 GSD 2 pool 0
    [2014-06-26 14:59:04] Accepted 41778fa7 Diff 1K/512 GSD 2 pool 0
    [2014-06-26 14:59:04] Accepted 12a60a5d Diff 3.51K/512 GSD 7 pool 0
    [2014-06-26 14:59:05] Accepted 090b81cd Diff 7.25K/512 GSD 5 pool 0
    [2014-06-26 14:59:06] Accepted 688ceacf Diff 627/512 GSD 7 pool 0
    [2014-06-26 14:59:08] Accepted 03cec899 Diff 17.2K/512 GSD 3 pool 0
    [2014-06-26 14:59:09] Accepted 4d0d07b1 Diff 851/512 GSD 5 pool 0
    [2014-06-26 14:59:11] Accepted 7580c5d7 Diff 558/512 GSD 5 pool 0
    [2014-06-26 14:59:12] Accepted 69e2dfe6 Diff 619/512 GSD 5 pool 0

    Reply
  6. Randy

    Hey Max,

    Actually I owe you a world of thanks for putting this together in the first place. cpuminer was way too frustrating. It’s nice to be able to see all my equipment running on one screen again.

    Thanks bro for helping noobs like me get a handle on mining crypto currencies.

    Reply
    1. Max Lee Post author

      Yeah exactly, I detest cpuminer, it’s a piece of crap software, cgminer is so much better you can actually SEE your hashrates plus more API features.

      Reply
  7. VQP2000

    Just bought a blade on EBay. Set it up with the config you suggest here minus some api lines which seemed to cause an error for me. I can’t get more than 600Kh/s per board from the thing. I’m not sure if I got a dud or if there’s something I’m missing in the setup. any thoughts?

    {
    “pools” : [

    {
    “url” : “stratum+tcp://coinotron.com:3334”,
    “user” : “VQP2000.coinbot”,
    “pass” : “0V3106YN”
    },
    {
    “url” : “stratum+tcp://coinotron.com:3334”,
    “user” : “VQP2000.coinbot”,
    “pass” : “0V3106YN”
    }
    ]
    ,
    “gridseed-options”: “baud=230400,freq=850,chips=40,modules=1,usefifo=0”,
    “hotplug”: “30”,
    “worksize”: “1”,
    “kernel”: “scrypt”,
    “thread-concurrency”: “50000”,
    “lookup-gap”: “0”,
    “gpu-threads”: “2”,
    “queue”: “0”,
    “scan-time”: “1”,
    “expiry”: “1”,
    “auto-fan”: true,
    “scrypt”: true,
    “api-listen”: true,
    “api-port” : “4028”,
    “no-pool-disable” : true,
    “kernel-path” : “/usr/local/bin”
    }

    Reply
  8. marcelo

    high max!

    your step by step setup guide really helped, but now i a have a problem,
    i have 2 blades on my raspberry mining. but one of them has a power mod to get more m/h and now i need to config the Hz rate for every blade, can you help me ou

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This blog is kept spam free by WP-SpamFree.