Topic: [GUIDE] GridSeed 5-Chip USB, Blade & Black Miner Support/Tuning - page 75. (Read 308807 times)
March 13, 2014, 07:34:28 PM
March 13, 2014, 07:12:02 PM
I just entered the pool info and saved it. Refreshed the page and it worked.
March 13, 2014, 06:12:39 PM
I just made an image, gridseed supported.
Just write image it to 4gb sdcard, stick it into your pi, fire up. Miners should start automatically after you've entered mining pool.
Hope this helps.
I am sorry, first upload was bad.....
https://mega.co.nz/#!uZAGFI6S!xVhHZdNvGij2L6gJk_VXnaTewgr7gFjOjnOCTtO_HHU
Thanks to all from litecointalk, who made this possible.
Let me know if that works for you.
Just write image it to 4gb sdcard, stick it into your pi, fire up. Miners should start automatically after you've entered mining pool.
Hope this helps.
I am sorry, first upload was bad.....
https://mega.co.nz/#!uZAGFI6S!xVhHZdNvGij2L6gJk_VXnaTewgr7gFjOjnOCTtO_HHU
Thanks to all from litecointalk, who made this possible.
Let me know if that works for you.
Sorry, but can someone tell me what needs to be done step by step once the image has been copied over?
I can access the page and enter a pool but when I restart it never starts mining...
March 13, 2014, 06:10:30 PM
Scripta is the way to go on the pi. Finally have scryptguild showing the same speed as cgminer. Running 20 off 2 rosewill 10 port hubs.
March 13, 2014, 05:01:48 PM
Question about SSH:
I can figure out how to SSH into the Ubuntu box, and start it mining. If I close the connection, what happens to the terminal process that is running the miners? If I SSH back into the computer, does it reopen that window?
I still do not have the ubuntu box fully set up. I was able to simultaneously open multiple SSH windows into the Ubuntu box, and it started me thinking.
I can figure out how to SSH into the Ubuntu box, and start it mining. If I close the connection, what happens to the terminal process that is running the miners? If I SSH back into the computer, does it reopen that window?
I still do not have the ubuntu box fully set up. I was able to simultaneously open multiple SSH windows into the Ubuntu box, and it started me thinking.
Use screen:
Code:
screen -S miner
"miner" can be anything, it's just a name that you can use later to get back to it. This will give you a new shell. Start cgminer there.
Ctrl-A, then Ctrl-D will exit the new shell and will keep cgminer running.
To verify that it's indeed running in the background use this:
Code:
ps auxwww | grep cgminer
You can now disconnect SSH etc. To get back to your cgminer:
Code:
screen -D -r miner
March 13, 2014, 04:59:41 PM
Question about SSH:
I can figure out how to SSH into the Ubuntu box, and start it mining. If I close the connection, what happens to the terminal process that is running the miners? If I SSH back into the computer, does it reopen that window?
I still do not have the ubuntu box fully set up. I was able to simultaneously open multiple SSH windows into the Ubuntu box, and it started me thinking.
I can figure out how to SSH into the Ubuntu box, and start it mining. If I close the connection, what happens to the terminal process that is running the miners? If I SSH back into the computer, does it reopen that window?
I still do not have the ubuntu box fully set up. I was able to simultaneously open multiple SSH windows into the Ubuntu box, and it started me thinking.
Hop over to the purchase and setup guide: https://bitcointalksearch.org/topic/guide-gridseed-gc3355-5-chip-setuppowerwindowslinuxrpi-by-unicornhasher-494625
Then come back here once you have everything set.
You use screen to run the miner sessions and keep them running after you close the ssh session.
March 13, 2014, 04:56:27 PM
March 13, 2014, 04:52:58 PM
Question about SSH:
I can figure out how to SSH into the Ubuntu box, and start it mining. If I close the connection, what happens to the terminal process that is running the miners? If I SSH back into the computer, does it reopen that window?
I still do not have the ubuntu box fully set up. I was able to simultaneously open multiple SSH windows into the Ubuntu box, and it started me thinking.
I can figure out how to SSH into the Ubuntu box, and start it mining. If I close the connection, what happens to the terminal process that is running the miners? If I SSH back into the computer, does it reopen that window?
I still do not have the ubuntu box fully set up. I was able to simultaneously open multiple SSH windows into the Ubuntu box, and it started me thinking.
March 13, 2014, 04:37:55 PM
Has anyone tried a large amount of gridseeds on cgminer? I am trying 28 of them on a rasberry pi and it stops accepting shares and eventually crashes after about 2 minutes. Running 28 instances of cpuminer works great, stable, and multipool reports right about where the hash rate should be.
Mine's been stable since upgrading to the "next" kernel (3.10.30+):
sudo apt-get install rpi-update
sudo BRANCH=next rpi-update
This is potentially great news! I've been having stability issues and set a cron job to do a reboot every 6 hours. I've applied the update and disabled the cron job on 1 of 2 of my Pi's and i'll monitor over the next 24 hours.
Oh and just a recommendation, i've been using JuiceSSH for Android to remotely manage my RPI's and it works great. I even set up some port forwarding on my router so I can remote access from anywhere I have cell service! Has come in handy on several occasions (issuing a quick reboot command when needed).
-EMoomjean
I tried that and now cgminer just crashes on startup. Did you have to recompile cgminer after updating?
Nope, I just executed the 2 commands and performed a reboot afterwards. BTW, I double checked and the slub debug command in the cmdline.txt persists through the update (I only mention it because I saw cmdline.txt scroll by as one of the files that was touched in the patch).
-EMoomjean
Just recompiled and checked my cmdline.txt, was missing the stability fix. Changed and now cgminer starts, but I get some HW errors and some miners dont accept any shares. Power usage is only 140 watts compared to 240 running cpuminer.
Sounds like either cgminer isn't seeing all your miners or the RPI isnt seeing them. I would try running the lsusb -t command to verify all of your miners are recognized by the RPI as a first step.
If you're using the 10 port hub that came with the Lightning Asic kits the ports with comm/data are the miner ports (should be 1-6, then 7 is Class=hub under which you'll see another 1-4).
-EMoomjean
Thanks for all your help. I am using the monoprice 24 port hub, with another 7 port hub daisy chained. Cpuminer sees all of the devices so I assume cgminer would as well. 28 total gridseeds
screen -dmS 1 sudo ./cgminer --scrypt -o stratum+tcp://us-west2.multipool.us:7777 -u myuser.gs1 -p x --gridseed-options=baud=115200,freq=800,chips=5 --hotplug 0
When I run lsusb -t I get this:
Code:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
|__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/3p, 480M
|__ Port 1: Dev 3, If 0, Class=vend., Driver=smsc95xx, 480M
|__ Port 2: Dev 4, If 0, Class=hub, Driver=hub/7p, 480M
|__ Port 1: Dev 5, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 1: Dev 5, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 2: Dev 6, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 2: Dev 6, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 3: Dev 7, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 3: Dev 7, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 4: Dev 8, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 4: Dev 8, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 5: Dev 9, If 0, Class=hub, Driver=hub/7p, 480M
|__ Port 1: Dev 12, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 1: Dev 12, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 2: Dev 13, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 2: Dev 13, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 3: Dev 14, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 3: Dev 14, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 4: Dev 15, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 4: Dev 15, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 6: Dev 16, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 6: Dev 16, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 7: Dev 17, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 7: Dev 17, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 6: Dev 10, If 0, Class=hub, Driver=hub/7p, 480M
|__ Port 1: Dev 18, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 1: Dev 18, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 2: Dev 19, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 2: Dev 19, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 3: Dev 20, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 3: Dev 20, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 4: Dev 21, If 0, Class=hub, Driver=hub/4p, 480M
|__ Port 1: Dev 32, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 1: Dev 32, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 2: Dev 33, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 2: Dev 33, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 4: Dev 34, If 0, Class=hub, Driver=hub/4p, 480M
|__ Port 1: Dev 35, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 1: Dev 35, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 2: Dev 36, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 2: Dev 36, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 3: Dev 37, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 3: Dev 37, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 5: Dev 22, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 5: Dev 22, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 6: Dev 23, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 6: Dev 23, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 7: Dev 24, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 7: Dev 24, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 7: Dev 11, If 0, Class=hub, Driver=hub/7p, 480M
|__ Port 1: Dev 25, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 1: Dev 25, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 2: Dev 26, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 2: Dev 26, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 3: Dev 27, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 3: Dev 27, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 4: Dev 28, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 4: Dev 28, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 5: Dev 29, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 5: Dev 29, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 6: Dev 30, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 6: Dev 30, If 1, Class=data, Driver=cdc_acm, 12M
|__ Port 7: Dev 31, If 0, Class=comm., Driver=cdc_acm, 12M
|__ Port 7: Dev 31, If 1, Class=data, Driver=cdc_acm, 12M
March 13, 2014, 04:33:50 PM
Has anyone tried a large amount of gridseeds on cgminer? I am trying 28 of them on a rasberry pi and it stops accepting shares and eventually crashes after about 2 minutes. Running 28 instances of cpuminer works great, stable, and multipool reports right about where the hash rate should be.
Mine's been stable since upgrading to the "next" kernel (3.10.30+):
sudo apt-get install rpi-update
sudo BRANCH=next rpi-update
This is potentially great news! I've been having stability issues and set a cron job to do a reboot every 6 hours. I've applied the update and disabled the cron job on 1 of 2 of my Pi's and i'll monitor over the next 24 hours.
Oh and just a recommendation, i've been using JuiceSSH for Android to remotely manage my RPI's and it works great. I even set up some port forwarding on my router so I can remote access from anywhere I have cell service! Has come in handy on several occasions (issuing a quick reboot command when needed).
-EMoomjean
I tried that and now cgminer just crashes on startup. Did you have to recompile cgminer after updating?
Nope, I just executed the 2 commands and performed a reboot afterwards. BTW, I double checked and the slub debug command in the cmdline.txt persists through the update (I only mention it because I saw cmdline.txt scroll by as one of the files that was touched in the patch).
-EMoomjean
Just recompiled and checked my cmdline.txt, was missing the stability fix. Changed and now cgminer starts, but I get some HW errors and some miners dont accept any shares. Power usage is only 140 watts compared to 240 running cpuminer.
Sounds like either cgminer isn't seeing all your miners or the RPI isnt seeing them. I would try running the lsusb -t command to verify all of your miners are recognized by the RPI as a first step.
If you're using the 10 port hub that came with the Lightning Asic kits the ports with comm/data are the miner ports (should be 1-6, then 7 is Class=hub under which you'll see another 1-4).
-EMoomjean
March 13, 2014, 04:30:43 PM
Has anyone tried a large amount of gridseeds on cgminer? I am trying 28 of them on a rasberry pi and it stops accepting shares and eventually crashes after about 2 minutes. Running 28 instances of cpuminer works great, stable, and multipool reports right about where the hash rate should be.
Mine's been stable since upgrading to the "next" kernel (3.10.30+):
sudo apt-get install rpi-update
sudo BRANCH=next rpi-update
This is potentially great news! I've been having stability issues and set a cron job to do a reboot every 6 hours. I've applied the update and disabled the cron job on 1 of 2 of my Pi's and i'll monitor over the next 24 hours.
Oh and just a recommendation, i've been using JuiceSSH for Android to remotely manage my RPI's and it works great. I even set up some port forwarding on my router so I can remote access from anywhere I have cell service! Has come in handy on several occasions (issuing a quick reboot command when needed).
-EMoomjean
I tried that and now cgminer just crashes on startup. Did you have to recompile cgminer after updating?
Nope, I just executed the 2 commands and performed a reboot afterwards. BTW, I double checked and the slub debug command in the cmdline.txt persists through the update (I only mention it because I saw cmdline.txt scroll by as one of the files that was touched in the patch).
-EMoomjean
Just recompiled and checked my cmdline.txt, was missing the stability fix. Changed and now cgminer starts, but I get some HW errors. Power usage is only 140 watts compared to 240 running cpuminer. It seems some miners are lazy and rarely accept shares, they all eventually start but some already have over 1000 accepted while some have 32. I also am getting many more rejects. I'll stick with cpuminer until thebugs get sorted.
Here is my command to launch:
screen -dmS 1 sudo ./cgminer --scrypt -o stratum+tcp://us-west2.multipool.us:7777 -u myuser.gs1 -p x --gridseed-options=baud=115200,freq=800,chips=5 --hotplug 0
March 13, 2014, 03:46:12 PM
Has anyone tried a large amount of gridseeds on cgminer? I am trying 28 of them on a rasberry pi and it stops accepting shares and eventually crashes after about 2 minutes. Running 28 instances of cpuminer works great, stable, and multipool reports right about where the hash rate should be.
Mine's been stable since upgrading to the "next" kernel (3.10.30+):
sudo apt-get install rpi-update
sudo BRANCH=next rpi-update
This is potentially great news! I've been having stability issues and set a cron job to do a reboot every 6 hours. I've applied the update and disabled the cron job on 1 of 2 of my Pi's and i'll monitor over the next 24 hours.
Oh and just a recommendation, i've been using JuiceSSH for Android to remotely manage my RPI's and it works great. I even set up some port forwarding on my router so I can remote access from anywhere I have cell service! Has come in handy on several occasions (issuing a quick reboot command when needed).
-EMoomjean
I tried that and now cgminer just crashes on startup. Did you have to recompile cgminer after updating?
Nope, I just executed the 2 commands and performed a reboot afterwards. BTW, I double checked and the slub debug command in the cmdline.txt persists through the update (I only mention it because I saw cmdline.txt scroll by as one of the files that was touched in the patch).
-EMoomjean
March 13, 2014, 03:11:49 PM
Has anyone tried a large amount of gridseeds on cgminer? I am trying 28 of them on a rasberry pi and it stops accepting shares and eventually crashes after about 2 minutes. Running 28 instances of cpuminer works great, stable, and multipool reports right about where the hash rate should be.
Mine's been stable since upgrading to the "next" kernel (3.10.30+):
sudo apt-get install rpi-update
sudo BRANCH=next rpi-update
This is potentially great news! I've been having stability issues and set a cron job to do a reboot every 6 hours. I've applied the update and disabled the cron job on 1 of 2 of my Pi's and i'll monitor over the next 24 hours.
Oh and just a recommendation, i've been using JuiceSSH for Android to remotely manage my RPI's and it works great. I even set up some port forwarding on my router so I can remote access from anywhere I have cell service! Has come in handy on several occasions (issuing a quick reboot command when needed).
-EMoomjean
I tried that and now cgminer just crashes on startup. Did you have to recompile cgminer after updating?
March 13, 2014, 02:32:57 PM
Anyone try out the CuBox-i? Comes with Ubuntu (and android). Do you think I could compile from cgminer from github on it? It's ARM based like the Pi.
http://images10.newegg.com/productimage/15-580-003-06.jpg
I'm using similar ARM based Odroid U3 myself. Everything compiles and runs nicely. No problems at all! I've tried compiling cgminer, bfgminer, cpuminer, using scripta etc. http://images10.newegg.com/productimage/15-580-003-06.jpg
March 13, 2014, 02:13:29 PM
Looking for some insight -
I have one miner that immediately posts HW errors and will not submit shares. Possibly a DOA unit? Does anyone have experience with this issue? Can it be fixed or am I out of luck?
I'm using Scripta and a Raspberry Pi as a controller and my other 9 work perfectly, so its a bummer that this one isn't cooperating.
Have you tried connecting another miner to the same port/cable? Or connecting the presumed faulty miner to known good power supply and USB cables?I have one miner that immediately posts HW errors and will not submit shares. Possibly a DOA unit? Does anyone have experience with this issue? Can it be fixed or am I out of luck?
I'm using Scripta and a Raspberry Pi as a controller and my other 9 work perfectly, so its a bummer that this one isn't cooperating.
I have one dead miner but it doesn't produce anything at all, not even HW errors. Will be sending it back for replacement.
I've had 3 bad ones so far. When their good their oh so good....but when their bad
March 13, 2014, 01:38:00 PM
Looking for some insight -
I have one miner that immediately posts HW errors and will not submit shares. Possibly a DOA unit? Does anyone have experience with this issue? Can it be fixed or am I out of luck?
I'm using Scripta and a Raspberry Pi as a controller and my other 9 work perfectly, so its a bummer that this one isn't cooperating.
I have one miner that immediately posts HW errors and will not submit shares. Possibly a DOA unit? Does anyone have experience with this issue? Can it be fixed or am I out of luck?
I'm using Scripta and a Raspberry Pi as a controller and my other 9 work perfectly, so its a bummer that this one isn't cooperating.
Have you tried connecting another miner to the same port/cable? Or connecting the presumed faulty miner to known good power supply and USB cables?
I have one dead miner but it doesn't produce anything at all, not even HW errors. Will be sending it back for replacement.
Yep, and I've tried to run it through CGminer and CPUminer in windows, used different cables and plugged it directly into a PC usb port. Same behavior. Bummer.
March 13, 2014, 01:23:58 PM
Has anyone tried a large amount of gridseeds on cgminer? I am trying 28 of them on a rasberry pi and it stops accepting shares and eventually crashes after about 2 minutes. Running 28 instances of cpuminer works great, stable, and multipool reports right about where the hash rate should be.
Mine's been stable since upgrading to the "next" kernel (3.10.30+):
sudo apt-get install rpi-update
sudo BRANCH=next rpi-update
This is potentially great news! I've been having stability issues and set a cron job to do a reboot every 6 hours. I've applied the update and disabled the cron job on 1 of 2 of my Pi's and i'll monitor over the next 24 hours.
Oh and just a recommendation, i've been using JuiceSSH for Android to remotely manage my RPI's and it works great. I even set up some port forwarding on my router so I can remote access from anywhere I have cell service! Has come in handy on several occasions (issuing a quick reboot command when needed).
-EMoomjean
March 13, 2014, 01:22:08 PM
Looking for some insight -
I have one miner that immediately posts HW errors and will not submit shares. Possibly a DOA unit? Does anyone have experience with this issue? Can it be fixed or am I out of luck?
I'm using Scripta and a Raspberry Pi as a controller and my other 9 work perfectly, so its a bummer that this one isn't cooperating.
I have one miner that immediately posts HW errors and will not submit shares. Possibly a DOA unit? Does anyone have experience with this issue? Can it be fixed or am I out of luck?
I'm using Scripta and a Raspberry Pi as a controller and my other 9 work perfectly, so its a bummer that this one isn't cooperating.
Have you tried connecting another miner to the same port/cable? Or connecting the presumed faulty miner to known good power supply and USB cables?
I have one dead miner but it doesn't produce anything at all, not even HW errors. Will be sending it back for replacement.
March 13, 2014, 01:13:15 PM
Looking for some insight -
I have one miner that immediately posts HW errors and will not submit shares. Possibly a DOA unit? Does anyone have experience with this issue? Can it be fixed or am I out of luck?
I'm using Scripta and a Raspberry Pi as a controller and my other 9 work perfectly, so its a bummer that this one isn't cooperating.
I have one miner that immediately posts HW errors and will not submit shares. Possibly a DOA unit? Does anyone have experience with this issue? Can it be fixed or am I out of luck?
I'm using Scripta and a Raspberry Pi as a controller and my other 9 work perfectly, so its a bummer that this one isn't cooperating.
March 13, 2014, 12:45:56 PM
Anyone try out the CuBox-i? Comes with Ubuntu (and android). Do you think I could compile from cgminer from github on it? It's ARM based like the Pi.
This says it's 8" x 8" x 8"
Jump to: