Author

Topic: Can anyone help to configure Gridseed G-Blade? (Read 332 times)

brand new
Activity: 0
Merit: 0
February 09, 2018, 06:19:12 PM
#4
http://highoncoins.com/litecoin-rig/how-to-make-gridseed-blade-mining-rig-pre-built-cgminer/


http://highoncoins.com/litecoin-rig/how-to-make-gridseed-blade-mining-rig-pre-built-cgminer/


Download HighOnCoins Gridseed image with Pre-built CGminer
http://downloadandroidrom.com/file/zedomax/highoncoins/gridseed/HighOnCoinsGridSeedBLADERaspberryPi.zip

Download Win32DiskImager
http[Suspicious link removed]



Step 4. Next, download the HighOnCoins Gridseed Blade image and flash to your SD card using Win32DiskImager.   (You can also use DD with Linux/Mac but that’s outside the scope of this tutorial, just Google it.)

Step 5. Put the new SD card with HighOnCoins Gridseed Blade image into your Raspberry Pi and turn it on by connecting a micro-USB cable to it.

        You can connect to the Raspberry Pi by connecting a DVI cable to a monitor and a keyboard via USB.  OR my preferred method is to connect an ethernet cable to your router then
        remotely SSH (using Putty or terminal), you can check for the IP address by checking your router’s LAN status.

Connect to Raspberry Pi using the following credentials:

id: root
password: raspberry

*Note – I used root user for Raspberry Pi as the USB-based Gridseeds require a lot of root access and it’s just pain in the butt to enter your password everytime you use sudo.


Step 6. Once connected, you can type “nano cgminer/cgminer.conf” to edit the cgminer configuration files. 
        There you will be able to change the pool info to yours.  Save when done.

save with crtl,x

Step 7. To start the cgminer, simply type, “sh test.sh”.  If you see “FAILED!”, it means it’s successful. (Sorry I forgot to edit that part while writing the script.)
        This will run cgminer in the background.


Step 8. To actually see cgminer running, type “cgm”.  To get out of it, press Ctrl + a + d.


Step 9. Once you get everything working great, you can enable auto-start script, which will start cgminer automatically upon boot, power-failure, lock-up, etc…etc…

       Type “nano /etc/cron.d/saupdate” and remove the “#” from the first line and save.


Once that’s done, cron job will automatically check every minute for cgminer and start it if its not running.

I’ve also enabled the watchdog timer on the Raspberry Pi so your Pi will restart upon any lock-ups, which was crucial to getting my new rig running 24/7.

I found that the Gridseed Blades run best at 838Mhz but you can try running them higher with a big fan blowing to your blades to cool them more.


MANDATORY UPDATE April 30th 2014: There’s a way to prevent freezing Raspberry Pi for good, do:

sudo nano /boot/cmdline.txt


Then add the line at the end of the line (do not make a new line!!):

slub_debug=FP


After that reboot by typing:

sudo reboot


This prevented most of reboots on the Raspberry Pi so you should get more hashing power!

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

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 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


other option=

"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"
}




legendary
Activity: 1498
Merit: 1030
Realistically, 800 Mhz is VERY VERY overclocked on a Gridseed blade. they SHOULD have specced as "stock" at 600, not the 750 they "stock" clocked at (which was already a mild overclock given their badly UNDERdesigned power supply circuitry).


 It's not the actual mining chips that are the issue, it's the overload on the buck converter.

hero member
Activity: 748
Merit: 523
Not too much to configure...

Only needs to select your desired frecuency.
You can start with 800 MHz...

Put more than 800 and you will do overclocking...
Put less than 800 and you will do undercloking...

More important is the pool you select for mining...
full member
Activity: 406
Merit: 101
99% of the guides are kinda useless Sad
Jump to: