background

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Buy bitcoins anywhere in the world at localbitcoins.com

Buy Monero at local Monero

Trade BTC for Monero at AgoraDesk

Use Anonymous Ads
Use Anonymous Ads

Gridseed Help

13»

Comments

  • I guess the bfgminer needs looking at… when did that start happening with the CPU miner, and does it not mine now? Maybe try lowering the freq
  • The most interest of the Gridsee is the scrypt mode, it's SHA mode will not pay the energy.
  • Have you tried this one?
    It's for the rasperian.


    ./configure --enable-scrypt --enable-gridseed

    .make install

    cgminer install to /usr/local/bin

    screen -dmS gs /root/cgminer-gc3355-master/cgminer --scrypt -o stratum+tcp://hk2.wemineltc.com:3336 -u sunyiwu.syw2 -p 1234 --gridseed-options=baud=115200,freq=850,chips=5 --hotplug 1
    add to /etc/rc.local
  • edited March 2014
    Hi again...

    I saw your mention of set up someone used with more than one device so I tried this...



    --freq=800 -G /dev/cu.usbmodem142431, /dev/cu.usbmodem142471

    RESULT:
    /Applications/MacMiner - Gridseed/MacMiner.app/Contents/Resources/gridseedcpu4/bin/minerd: unsupported non-option argument '/dev/cu.usbmodem142471'
    Try `minerd --help' for more information.

    Then I tried this...


    -S gridseed:/dev/cu.usbmodem142431, -S gridseed:/dev/cu.usbmodem142471
    RESULT:
    /Applications/MacMiner - Gridseed/MacMiner.app/Contents/Resources/gridseedcpu4/bin/minerd: unsupported non-option argument 'gridseed:/dev/cu.usbmodem142431,'
    Try `minerd --help' for more information.

    And then... (I think this was for CGMiner... but I tried anyway)
    -S gridseed:all --set-device gridseed:clock=750
    RESULT:
    minerd: unrecognized option `--set-device'
    Try `minerd --help' for more information. 

    I would not mind being able to mine both SHA256 and Scrypt, but I'm mainly focused on Scrypt for now.

    Oh, I also installed your latest version.

    Thanks again for all your efforts!

    PS... I've been running for awhile with --freq 850 and so far that's been the best setting.
  • edited March 2014
    Hi, baronetta:

    Have you tried mining with the fan off, use a extern fan. Your device will work better, you can work with more freq. But only in LTC mode.

  • No I have not tried that... did not know I could turn the fan off.  The image you included is not showing. I'm guessing it tells me how to turn the fan off?
  • edited March 2014
    You can cut  to cable. You economy energy using um external fan and take more speed for grid seed. Search in internet, you'll see the how. You can do tower to organize better. It's very interest. (ONLY FOR LTC MODE) 

    • Hash = 330kh/s at 800 MHz(Scrypt)
    • These mining units can be overclocked to 850 MHz = 400KHs per USB miner
  • OK, thanks. I don't pay for electricity (I'm a property manager, utilities paid) so I'm not concerned about that, but if it speeds them up then I'll give it a try.

    I am finding that overclocking at 850MHz is giving me the best hash rate. 

    I still cannot seem to get both of my devices recognized. 

    Thanks again!

  • So, fan alway causes errors by his magnetic field. In multipool.us, my device made 433KH (freq 850).
  • hmmm, I can't get them to hash if I cut power to the fans.

    So, still just hoping that there will be a way that my computer will recognize both of them. 

    I would put one one the MacBookPro, but there seems to be a conflict with the Antminers and they are running well and I don't want to mess them up.

    Any new ideas on getting my iMac to recognize two Gridseed units???
  • Not surprised the fans cause electro magnetic interference, with the much lower energy usage of just scrypt mining i bet you could get away without the fans. Maybe there's some workaround, like connecting the fan's + and - cables after cutting them.

    Sorry I really should have thought earlier, but duplicate the MacMiner you're using and set up the manual flags in the copy for the other device!
  • edited March 2014
    Hi,
    Do you have some good news for us?
    Did you see the upgrade in https://github.com/gridseed/usb-miner? It promises to work in dual mode with CPUminer.
  • Hmmm... Well, running two instances of MacMiner with different settings in the flags seems like a good idea but I can't seem to get both hashing. Whichever one I fire up first seems to do OK, but the second shows "starting" but never produces any accepted shares. 

    Any suggestions? I'm stumped.

    Oh... Update... I kept fiddling around and now it seems they are both hashing away on two different pools!
  • Hi,
    I've tried this frag: 
    --freq 850 -G /dev/cu.usbmodemfd1211,/dev/cu.usbmodemfd1241

    Result

    [2014-03-13 09:37:33] Starting Stratum on stratum+tcp://us-east.multipool.us:7777

    [2014-03-13 09:37:33] 0: GC3355 chip mining thread started, in SINGLE mode

    [2014-03-13 09:37:33] 0: Open UART device /dev/cu.usbmodemfd1211

    [2014-03-13 09:37:33] 0: Set GC3355 core frequency to 850Mhz

    [2014-03-13 09:37:33] 1: GC3355 chip mining thread started, in SINGLE mode

    [2014-03-13 09:37:33] 1: Open UART device /dev/cu.usbmodemfd1211

    [2014-03-13 09:37:33] 1: Set GC3355 core frequency to 850Mhz

    [2014-03-13 09:37:33] Stratum detected new block

    [2014-03-13 09:37:34] 0: Dispatching new work to GC3355 LTC core

    [2014-03-13 09:37:34] 1: Dispatching new work to GC3355 LTC core

    [1;33m0: >>> LTC :[0m 55aac000808080800000000001000000

    [1;33m0: >>> LTC :[0m 55aac000c0c0c0c00500000001000000

    [1;33m0: >>> LTC :[0m 55aaef020000000000000000000000000000000000000000

    [1;33m0: >>> LTC :[0m 55aaef3020000000

    [1;33m0: >>> LTC :[0m 55aa1f2817000000

    [1;33m0: >>> LTC :[0m 55aaef0005002084

    [1;33m1: >>> LTC :[0m 55aac000808080800000000001000000

    [1;33m1: >>> LTC :[0m 55aac000c0c0c0c00500000001000000

    [1;33m1: >>> LTC :[0m 55aaef020000000000000000000000000000000000000000

    [1;33m1: >>> LTC :[0m 55aaef3020000000

    [1;33m1: >>> LTC :[0m 55aa1f2817000000

    [1;33m1: >>> LTC :[0m 55aaef0005002084

    [1;33m0: >>> LTC :[0m 55aa1f2816000000

    [1;33m0: >>> LTC :[0m 55aa1f2817000000

    [1;33m0: >>> LTC :[0m 55aa1f00000000000000000000000000000000000000000000000000000080ff7f000000f94babee4b443f94cd0ddf4ef9c5838c151653b256b1a8022311634937d44b3f00000001dc7a2a4aa0c0efc472577e7c7c5a603e2c0374e9e310b96648338c1e5922560cd85f48c684b4bb49019b57222d0394a3d39d2a6f392f5ebb67d16485efda4b995321a6861c07507c00000000ffffffff12345678

    [1;33m1: >>> LTC :[0m 55aa1f2816000000

    [1;33m1: >>> LTC :[0m 55aa1f2817000000

    [1;33m1: >>> LTC :[0m 55aa1f00000000000000000000000000000000000000000000000000000080ff7f000000f94babee4b443f94cd0ddf4ef9c5838c151653b256b1a8022311634937d44b3f00000001dc7a2a4aa0c0efc472577e7c7c5a603e2c0374e9e310b96648338c1e5922560cd85f48c684b4bb49019b57222d0394a3d39d2a6f392f5ebb67d16485efda4b995321a6861c07507c00000000ffffffff12345678


    But Accept 50% only.
  • @baronetta any tips for us on what fiddling you did to get both running?
  • edited March 2014


    Well, I've definitely learned a few things about these Gridseeds in the last day or so.

    Originally I think it was by luck that some of the fiddling got good results. As I fiddled more, things got worse... then I finally found a pattern that gives me consistent results of each device hashing at around 400 kh/s, and sometimes even better!

    Here's some things I've learned...

    I have the first instance of MacMiner (Gridseed edition) in the Applications folder. The second instance is in a folder inside the Applications folder. I tried with both in the same folder with one named MacMiner 2 and that gave me very unreliable results.

    I always open the MacMiner in the Applications folder first - this may not make a difference, but it is working for me so I'm just sharing what works.

    I move the windows of the first instance to the left side of my screen. When I open the second instance I move it to the right so I can have both open and I can double check my settings to be sure they are different in each instance.

    Before opening the second instance, I get the first instance running and wait to be sure shares are accepted.

    For getting them each running I first open the miner options. The flag settings still don't "stick" but I have them easy to get to to paste in. Once pasted, I click the button to open the preferences pane to enter my pool settings. Then I click apply in the miner options window, then I reopen the options pane. I do this so I can be sure I'm entering the right flags for the second device by checking the first. Then I hit the Start button and wait until shares are accepted.

    I open the second instance, and move the windows to the right so none of them overlap the windows of the first instance. The flag area will be empty, which is fine since I need to put different flags in for my other device. The pool preferences will be the same as what was just set for the first instance, so I edit that and save and apply. I usually open the options pane again to double check my settings are different and then hit Start!

    I have learned that if I want to change the pool for one of the devices, I MUST stop the miners and quit both instances of MacMiner and start the whole process from scratch, even if I do not want to change the settings for the other device. If I don't start both of them fresh, my hash rate runs 50-80 kh/s for each device. Ugly!

    When I was still trying to get both of these to run from the same instance, the two flag formats below seemed to both work just fine (but with disappointing hashing):

    --freq=850 -G /dev/cu.usbmodem142431, -G /dev/cu.usbmodem142471
    and
    --freq=850 --gc3355=/dev/cu.usbmodem142431 --gc3355=/dev/cu.usbmodem142471

    But, I am getting nothing but errors if I try: --freq=850 -G /dev/cu.usbmodem142431

    So, now I only use this format: --freq=800 --gc3355=/dev/cu.usbmodem142431 

    I think those are all the tricks I've learned... now I'm just leaving them alone so they can make me some coin!

    Hope that helps!

    Tami


    Oh, I haven't messed with the wiring on the fans. I'm guessing I would need to get inside to the wiring to get them disconnected? Don't know that I'm brave enough for that.




  • I noticed a few things as well with MacMiner. Even though I tell it to open CPU Miner automatically. It seems to open up GPU Miner for some reason. As mentioned above manual flags don't seem to stick. I seem to get good results with --freq=850 -G /dev/cu.usbmodemxxxxx, maybe it's the distance to your particular pool? I have seen more errors when the sites were of further distance away.


  • Baronetta,

    I get it. Thanks! All of them are working, now.
  • edited March 2014
    It's work as in RaspberryPi. Open one terminal per Gridseed.
    I just configure my RaspberryPi.
  • so the standard procedure is actually to run one instance for each device? That sucks. Thanks for the info! If you want to do that with MacMiner you can run it at the command line like

    /Applications/MacMiner-gridseed.app/Contents/Resources/gridseedcpu4/bin/minerd -o pool.address.com:1234 -u user -p password --freq=800 --gc3355=/dev/cu.usbmodem142431 

    Thanks for the other reports too, I'm doing a beta update today so I should get some of these issues ironed out!
  • Hmmm... don't really know anything about RaspberryPi but I'll check it out, thanks!

    As for running one instance of MacMiner for each device, it's not so bad now that I figured out the steps to do it right. Not sure I would want to deal with more than 4 tops, but not there yet.

    By the way, I see the price of the Gridseed is dropping nicely. I got mine from ZoomHash at $249 each (they had them on ebay for $299) and free shipping. They included the wrong usb cords but refunded me the cost of them.  Now I see the price is down to $215 for their next batch arriving in two weeks. Nice to see prices dropping. 

    I might try running them in terminal... I already have some cloud mining going in so have it open all the time, but for now I'm just enjoying the nice hashing and taking a "fiddling break."

    Great weekend to all!

  • I have no such luck in the UK, prices are still obscene. I wonder what the announced 100Mh KNC device will do to scrypt currencies…

    Please try this version now:

    Which should work with bfgminer updated by luke-jr an hour ago. 

    LTC in the GPU window and BTC in the ASIC window both use the flag
    -S dualminer:all
  • Sorry to hear about pricing there. Haven't heard of the other device you mentioned but a quick check shows me that's going to be out of common person's reach for quite some time... but it may change the balance of things again... Kind of a wild ride in this realm right now. 

    Thanks for the updated version... I'll give it a whirl!


  • Hey all- thanks for creating this thread- it helped me get at least part of the way set up.

    I'm using gridseed build 8, and may be having an issue?

    This build of MacMiner is not showing my hashrate for me, and the pool i'm pointed at (waffle) is reporting a hashrate around 170khash (mildly disappointing).

    My manual flags, in accordance with what others learned:

    --freq=850 --gc3355=/dev/cu.usbmodemfd122241

    Anyone have advice on what I might do to optimize for full hashrate?

    (Note: I am also running a sha256 instance of MacMiner, and followed the advice of killing it and restarting before firing up the Gridseed8 build.)
  • The best thing to do would be play with the frequency, 850 may be overheating your device, and some people have reported lower frequencies running faster. Try 750 or 800 and see how that changes things.

    Unfortunately the backend miner gridseed released doesn't show the hash rate, which is a known bug, but you could try the instructions in this thread to see whether that helps matters

  • I should have been more patient :] One 5-chip device is "slow" enough that you see a constantly fluctuating hashrate on Waffle, depending on when in the 5-minute shift you are. Example- last refresh I got 492.

    http://wafflepool.com/miner/13gkdcu42tFFcT2vpy5m1PmSLSZGMTX4J3

    I'll check heat when I get home- what should I be looking for in the logs as an indicator of overheating?

    Thanks for all your work on MacMiner & supporting other devices.

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file