Topic: [GUIDE] GridSeed 5-Chip USB, Blade & Black Miner Support/Tuning - page 57. (Read 308807 times)

hmm i dunno still seems way off to me http://imgur.com/tnVBpzk

what should i set for BAUD?
cgminer.exe --scrypt -u podizzle.x -p x -o stratum+tcp://us.dogepool.net:2222 --gridseed-options=baud=115200,freq=800,chips=5 --hotplug 5


800 is working much better at what point is too many HW errors is your guys opinion is there some ratio A:HW that i should shoot for?

hey guys can anyone tell me whats wrong here? all 18 are being detected but only some are accepting shares so far? my total accepted and hash looks right at top but its not even coming close to what the pool is showing.

http://imgur.com/2xT57GG

Your Mhz is probably wrong. You should start at 800 and step up only if it's stable. Most unmodified Gridseeds don't work well above 850. It's unclear from your screenshots how long it's been running, but there a lot of HW errors.

hey guys can anyone tell me whats wrong here? all 18 are being detected but only some are accepting shares so far? my total accepted and hash looks right at top but its not even coming close to what the pool is showing.

http://imgur.com/2xT57GG

I would suggest to try to plug the Gridseed directly into Raspberry with a known good USB cable. Make sure the Raspberry is powered off, plug in the Gridseed, power both on. If that works you can then test the hub.

Odd, on my rpi, I have to start both the miner and the rpi with the usb cable un-plugged in, then plug it in after it's running. Otherwise it won't see the devices.
Im using the hashra image and 10 GSDs on a powered hub.

When you say it crashes, are you talking about the cgminer itself, or your Raspberry Pi?

If it's the Raspberry Pi, you should probably check that you've got the "slub_debug=FP" hack in place. This has been discussed in other places, but to save you searching time, here's what you need to do (if it's not already in place):

sudo nano /boot/cmdline.txt

Add the following code at the end of the first line (on the same line as the other text, DO NOT add new line!)


Save the file then reboot your Raspberry Pi.

What the above does is basically enable some kernel debug mode on the Raspberry Pi. I have no idea why debug mode prevents the system kernel crash, but there's a lot of anecdotal evidence that it does work. In my case, I couldn't run for more than an hour before my Pi would crash.

I suspect that there's a kernel bug that cgminer is somehow triggering. I don't know if anyone has seriously investigated this, given that most people just want a work around so that they can keep mining reliably. But if you're interested, here's a related thread that I found:

http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=55370

If the issue is that cgminer is crashing, not your Pi, doesn't it get restarted by the Scripta /etc/rc.local?

I've seen cgminer crash too. I got about 48 hours the last time before it crapped out. I'm using the dtbartle version that I built myself from the git sources, and I've got 10 GridSeed units.

This morning I decided to run cgminer in text only mode under daemontools. I've been running my Dual Miner version of cgminer like that for weeks on another rig and have never seen a crash of either the Pi or cgminer (and I don't have the slub_debug hack enabled on that Raspberry Pi, either). There's a lot to like about daemontools, including logging. And I see no need to have a terminal output in a detached screen process when Scripta does a nicer job of giving me visual miner status.

I have no idea if running cgminer in its default terminal mode under screen is in fact problematic or not. The stability problems might just be in the gc3355 implementation of cgminer. But I like how my other rig is running and it's nice to keep things consistent.

Anyway HTH...

I would suggest to try to plug the Gridseed directly into Raspberry with a known good USB cable. Make sure the Raspberry is powered off, plug in the Gridseed, power both on. If that works you can then test the hub.

I did used this command to install cgminer -   wget https://db.tt/UygLkqwd -O cgminer
based on this tutorial on reddit - http://www.reddit.com/r/litecoinmining/comments/20qddx/a_simple_guild_to_set_up_gridseed_ltc_mining_rig/

With the gridseed plugged into hub(green LED is on, red lights up occasionally), with hub powered on (plugged into PSU and red LED is on) and plugged into RPi, this is what I get when I run lsusb -

Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 050d:945a Belkin Components F7D1101 v1 Basic Wireless Adapter [Realtek RTL8188SU]

I tried the standard zoomhash image, hashra and scripta yesterday, but had trouble setting up the wifi adapter so I went with the standard raspbian setup that was in the Unicorn Hasher guide.
Posted from Bitcointa.lk - #lk0YcbSLv4yyRo9e

Are you using the cgminer optimised for gridseed? normal cgminer doesn't detect gridseed devices.

can you type in

and post the results here please?

by the way- I've read perhaps or in another thread that some here warn against putting more than 3 or 4 gridseeds on one pcie connector.

please remember this: on my mining rig I have two pcie connectors powering a GPU that draws 350 watts when it's hashing away.

my 1200W PSU runs the MOB and 3 of the electric hogs that each hash at about 800 Kh/s

therefore this weekend I'm putting all two of my twenty gridseeds on one 750W power supply and I'm going to run 10 gridseeds off one pcie connector.

hell - even if I leave myself 150 watts of headroom and allocating 10 watts per gridseed I should be able to run 60 gridseeds off one 750W PSU

Here is the output with that command, it's definitely not seeing them for some reason. GSD is plugged into hub, which is plugged into the RPi. Red LED is lit on hub. It's the one that came with the order from zoom hash, should I buy a different one?

    root@raspberrypi:~# ./cgminer -n
    [2014-03-28 00:37:52] USB all: found 4 devices - listing known devices  
    [2014-03-28 00:37:52] No known USB devices

Thanks for the quick response!
Posted from Bitcointa.lk - #Y9uUj3i2zccUIx7O