Quote from: edonkey on April 20, 2014, 01:03:12 AM

Quote from: tonytre on April 19, 2014, 10:27:38 PM

Hello all,

I have ordered my first gridseed from GAWminers, and have followed the guide to download cgminer for Ubuntu from this post. I believe I have succussfully downloaded it as I was able to get it to start up at the end, but obviously it says no USB device detected.

I have been mining with 3 r7 265's for the past month, but before that had no experiece in linux or computer building. I built my first computer and with some help was able to get my cards mining. I use sgminer and get it started by cd ~/ and then ./mine.sh.

I was wondering if there was a way to start cgminer like that, as I think the only way I was able to get it running was by calling cd ~/ then ./cgminer/cgminer -o xxxxx and all the information for gridseed after. I was wondering if there was a way to start the gridseed mining by calling on a .sh file like I do for my gpus. I am hoping someone doesn't mind answering my elementary question. I want to be prepared to have the gridseed up and running right when it gets here and not have any software issues. Will the gridseed work by running cd ~/ then ./cgminer/cgminer -o stratum+tcp://server:port -u username.worker -p password --gridseed-options=baud=115200,freq=888,chips=5 --hotplug 30? It currently starts to look for a pool when I type that in now and feel like it should work once the gridseed is hooked up, and is there any easier way to get it running other than how I stated.

I also plan to just open cgminer in a second terminal, as my gpu's currently run on sgminer. Will this cause any problems?

Thanks!

Are you running cgminer as root? I think you have to do that or it won't be able to talk to the GSD's.

I have two rigs, one is Gridseed 5 chip based and the other uses DualMiners. In both cases I run cgminer as a service via Daemontools. I've posted a "how to" here in case you're interested:

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

If you're on a real linux box and not a Raspbery Pi, then you can probably skip my instruction about installing ramlog because you probably don't need it.

If your cgminer still can't see the GDSs, then you can tell if they're visible on the USB bus via this command. This might help rule out a USB hub or connection problem:

lsusb -t

If you need an example config, here's the one that I'm using with the mox235 variant of cgminer (same as girnyau but with better JSON API output):

Code:

{
"gridseed-options": "baud=115200,freq=850,chips=5",
"gridseed-freq" : "8D6E50A55748=900,8D9136685748=875",
"kernel-path": "/usr/local/bin",
"failover-only": true,
"verbose": true,
"api-listen": true,
"api-port": "4028",
"expiry": "120",
"hotplug": "5",
"log": "5",
"no-pool-disable": true,
"queue": "1",
"scan-time": "30",
"scrypt": true,
"shares": "0",
"pools": [
{
"url" : "stratum+tcp://uswest.wafflepool.com:3333",
"user" : "REPLACEME_workername",
"pass" : "x"
},
{
"url" : "stratum+tcp://sf.clevermining.com:3333",
"user" : "REPLACEME",
"pass" : "x"
},
{
"url" : "stratum+tcp://us-west.coinshift.com:3333",
"user" : "REPLACEME.workername",
"pass" : "x"
}
]
}

The above config defaults to a frequency of 850 unless overridden. You can see that the "gridseed-freq" option demonstrates overriding the frequency on a per serial number basis.

You have to replace "REPLACEME" in all cases above with your bit coin address. Do yourself a favor and copy and paste the address. These addresses are case sensitive, so one upper or lower case mistake and your earnings go into a hole. Change "workername" to the name you want for your rig, in case you have more than one and you want to be able to tell them apart.

I'm also using the mox235 version of Scripta as the web front end, but it's kind of involved getting it installed and working on an existing Linux system. Here's a link to the basic instructions I followed, if you're feeling up to it:

https://litecointalk.org/index.php?topic=9908.msg138403#msg138403

Remember to use the mox235 version of scripta with the mox235 version of cgminer. They've both been modified to provide improved information, including displaying the serial number and frequency of each GSD (which is insanely useful if you have more than one and want to tune them).

Note that if you use my mechanism of running cgminer under a service, you don't want to integrate the Scripta rc.local file. Also you should replace their start/stop scripts with your own that call daemontools to start and stop the miner. But frankly I just use Script for status, not control.

Also, when I leave the Scripta cron jobs on, they cause USB disconnects. I suspect this is a cgminer bug when multiple cron jobs hit the API simultaneously. Some people have successfully staggered their Script cron jobs to avoid the problem.

Probably too much information, but I hope some of it helps...

Thanks for the good information. First I've heard that it should be run in root, so that will be the first thing I try when it arrives on Monday/Tuesday. Scripta is probably a little too much for me at this time, but I will continue to read up about it, and maybe give it shot.

I probably should have waited to post until I actually have the device, but I am so pumped for it that I couldn't wait. Mining has turned into an addiction for me, and will definitely get more gridseeds if I figure out how to run the first one correctly. So should the first thing I try be cd ~/ then sudo ./cgminer/cgminer -o stratum+tcp://server:port -u username.worker -p password --gridseed-options=baud=115200,freq=888,chips=5 --hotplug 30?
I have followed this guide exactly, and could post screenshots of my home folder/cgminer/cpuminer to make sure I have downloaded everything correctly, but the best course of action is probably too just wait until I have it. I'm trying to understand why there is both cgminer and cpuminer in the linux download. Is the cpuminer there to use incase the cgminer doesn't run right, or is it part of cgminer? I thought they were two seperate programs, but as I mention I just started teaching myself how to use linux and coding. I used a macbook pro throughout college, and this computer I built was the first time doing anything other than installing a new HDD in my laptop. There is still so much for me to learn about the terminal. Thanks for the help!