Pages:
Author

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

member
Activity: 413
Merit: 10
...

You probably plugged in 20 miners on the PI, this is a problem with CGMiner.
When you click on the UPDATE CONTROLA link, it will upgrade your firmware to version 1.2.0, which has BFGMiner for scrypt hashing This solves the Cgminer problem. After this, your pi will be mining at a solid 7200mhs (and this time, it will also reflect on the pool)

I'm using for my 20 miner rig on one rasbian a clean weezy img + cgminer .... this works stable and reports 7.1 gh at the pool ... is there a cgminer problem? for more then 10 miners?

Here a 4gb Hashra image ... be sure to change pools before mining ... it's set to my setup right now ... as I used to test it ...
will try it out with 20 miners in a few minutes ...

Hashra 4 gb image

yes CGMiner is not stable with the GD5 chips, It causes them to "zombie out" after a while. When 20 miners are plugged in to 1 CGMiner instance, only half of them are actually hashing properly, while still showing maximum local hashrate, hence the much lower hashrate on the pools. BFGMiner (installed on CONTROLA 1.2.0) works perfectly with 20 miners (or more? haven't tried more). I would love to see the performance of CONTROLA with 30 - 40 miners on 1 PI...anyone want to try it? Smiley

Maxzilla, did you have anything to do with developing the HASHRA firmware? Saw your name as the default username on mine...Anyway, after the latest update that switched to BGMiner i started seeing 30+ reject rates on WafflePool only, other pools were fine.
I changed over to Scripta which has been running rock solid for a couple of days now. Are all cgminer versions unstable and did I just get lucky so far?
member
Activity: 112
Merit: 10

9. Patch: More Stability for Raspberry Pi
Code:
nano /boot/cmdline.txt
add the parameter
Code:
slub_debug=FP
( no new line! )
press Ctrl + o , Return, Ctrl + x to save changes



Manfred slub_debug is a bad idea. It will slow down your hashrate by 20%. I've tried it Wink. you should switch to BFGMiner.

I have never heard anyone else having a slowdown from this command.  I have always gotten around ~360kh per miner at 850mhz with or without slub_debug.

Please provide more info!

-EMoomjean



well to be honest I was using slub_debug=FPUZ not FP ... the latter didn't have any effect (PI still crashes). But FPUZ worked but was showing lower performance (on remote pools) local hashrates were showing 360kh/s per unit as always ofcourse, but I don't think it's submitting shares at that rate. for example on a 10 unit I got around 2.5 mhs compared to 3.4mhs without (but crashes)

In the end I didn't use slub_debug but did a
Code:
sudo BRANCH=next rpi-update

Which solved all my crashing problems.

Maybe my problem was related to raspbian. Scripta is using a different OS I think?
newbie
Activity: 39
Merit: 0

9. Patch: More Stability for Raspberry Pi
Code:
nano /boot/cmdline.txt
add the parameter
Code:
slub_debug=FP
( no new line! )
press Ctrl + o , Return, Ctrl + x to save changes



Manfred slub_debug is a bad idea. It will slow down your hashrate by 20%. I've tried it Wink. you should switch to BFGMiner.

I have never heard anyone else having a slowdown from this command.  I have always gotten around ~360kh per miner at 850mhz with or without slub_debug.

Please provide more info!

-EMoomjean

member
Activity: 112
Merit: 10
COMPLETE HOW-TO:
modify Scripta from Stock to automatically detect Gridseed GC3355 and show them in Web-Interface. ( No more ssh needed )

1. Download http://www.lateralfactory.com/download.php?file=scripta-1_1.tgz
2. Windows-User extract the .img-File and bring it to SD Card with http://sourceforge.net/projects/win32diskimager/
3. Boot Raspberry Pi with this SD Card
4. Detect IP Adress of Raspberry Pi in your Router
5. open ssh connection to port 7722 of that IP, user root, password scripta

6. Get modified cgminer
Code:
cd /opt/minepeon/bin
Code:
wget https://db.tt/UygLkqwd -O cgminer

7. Patch: Apply Gridseed Settings
Code:
nano /opt/minepeon/etc/miner.options.json
add here ( mind the { ... }, { ... } -Structure! )
How to's:

  • STEP BY STEP RASPBERRY SCRIPTA INSTALLATION
  • BUILD CGMINER ON THE RASPBERRY
  • ROOT ACCESS TO LIGHTNINGASIC CONTROLLER
  • UBUNTU/LINUX INSTALLATION GUIDE


STEP BY STEP RASPBERRY SCRIPTA INSTALLATION


Step by Step Raspberry SCRIPTA Installation:



  • 1 - SD Formatter (link) clean up your SD Card. At least a 4GB SD.
  • 2 - Download the SCRIPTA Image (link)
  • 3 - Win 32 Disk Imager (link) and write the scripta image on the SD Card.
  • 4 - Put the SD Card into your Raspberry.
  • 5 - SSH access on port 7722, user: root / psw: scripta
  • 6 - Use WinSCP (link) to move over the latest rasp cgminer for gridseed (https://db.tt/UygLkqwd) or Use PuTTY (link)
Code:
wget https://db.tt/UygLkqwd -O cgminer
  • 7 - Go to the location where you copied over your cgminer and do "chmod 777 cgminer"
  • 8 - Go to the SCRIPTA Web GUI, under Miner hit Miner commands, STOP
  • 9 - Go to the location where you copied over your cgminer and run it from there using these commands:
Code:
./cgminer --scrypt -o -u -p --gridseed-options=baud=115200,freq=850

    Stability-Fix:
    Code:
    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!)
    Code:
    slub_debug=FP

    Orginal Sources from: https://litecointalk.org/index.php?topic=9908.0

    How to get Scripta working as it was intended

    Follow the instructions by Darkfriend77 below but when you get to step 6, go to directory opt/minepeon/bin and remove the original cgminer there (rm cgminer). Now copy the new cgminer into this folder to replace the original and chmod it as below.
    Now go to directory opt/minepeon/startup and edit the file miner-start.sh with nano.
    Change the line -
    Code:
    sudo /usr/bin/screen -dmS cgminer /opt/minepeon/bin/cgminer -c /opt/minepeon/etc/miner.conf
    to
    Code:
    sudo /usr/bin/screen -dmS cgminer /opt/minepeon/bin/cgminer --scrypt --no-submit-stale --gridseed-options=baud=115200,freq=850 -c /opt/minepeon/etc/miner.conf
    Lastly apply the stability fix.
    Now you can close ssh and restart your pi and it should automatically fire up your gridseeds and start mining.


    BUILD CGMINER ON THE RASPBERRY


    referenced from litecointalk

    Ok, I will post this here, since I think people could benefit from it. I'll have to give most of the credits to Girhes, since he told me about the failsafe mode of openWRT, and assisted me while trying to gain access (he did not have a controller himself yet).

    Please note that this is at YOUR OWN RISK, you could brick your device when you have root access to the controller. Please do NOT install any programs when you have root access, unless you really know what you are doing. There is almost no room left on the device, so installing a program could brick your device.

    1 - Start the controller in failsafe mode:

    Quote from: Girhes
    There are different HW versions of the TL-WR703N - on version 1.6 you have to power on the controller, wait until the led starts flashing twice a second (it takes about 4 seconds to get there), then push the reset button immediately. When the led starts to flash much faster your device is in failsafe mode. All other HW versions: power on the controller, wait 10-12 seconds until the led starts flashing, then immediately push the reset button for 1-2 seconds. Again, if the led will start blinking rapidly you are in failsafe mode.

    The versioin of your device is stated on the back of the device, underneath the barcode.

    2 - Telnet into the device:

    On windows go to start, type 'cmd' in the search bar, and start 'cmd.exe'. In the command window you get afterwards, type 'telnet 192.168.1.1'. Make sure you use the correct IP, my device used 192.168.1.1 in failsafe mode.

    There is no user/pass required in failsafe mode.

    3 - Switch to the live partition:

    Type 'mount_root'

    Warning! You are in the live partition now, with root permissions. You could seriously fuck thing up now!

    4 - Change the root password:

    Type 'passwd', and enter the password you would like (twice).

    5 - Enable SSH:

    Type 'vim /etc/config/dropbear', this will open the SSH config file in the vim text editor. You need to change "option enable" to "on".

    You can start editing the file by hitting the 'i' key. You can now insert/delete characters. After you are finished editing hit the 'esc' key to stop editing. Now hit the ':' key, and type 'wq'. This will write the file, and quit the editor. If you made mistakes while editing, and just want to quit (without writing the file), type 'q' instead of 'wq'.

    6 - Reboot the device:

    Just unplug the usb power, and plug it in again.

    7 - Have fun!

    You can now SSH into the device while it is running in normal mode. (user: root, password whatever you entered in step 4). Just be carefull not to mess things up. If you are not at least a little familiar with linux, please be very carefull.



    UBUNTU/LINUX INSTALLATION GUIDE


    Hi Scrypt miners,

    I was lucky enough to get one of the first Scrypt ASICs produced by Chinese GridSeed during my stay in South Korea last month. Cheers to Dis Btopia of xbitcoinx.com! Smiley I just hooked up one unit containing 5 chips to my Ubuntu box via USB port and here is what I did to get it running. Mind you, these instructions are for mining Scrypt, not SHA256 or dual mode, which the ASIC can also do. Most of the information I pieced together from this post in Chinese: http://cybtc.com/article-468-1.html

    Download GridSeed's modified cpuminer and unpack zip file:
    Code:
    wget https://github.com/gridseed/cpuminer/archive/master.zip
    unzip master.zip
    cd cpuminer-master

    ..or download via git:
    Code:
    git clone [email protected]:gridseed/cpuminer.git
    cd cpuminer

    Install automake:
    Code:
    sudo apt-get install automake

    You might need to install other compiling tools. I didn't need to, because I compiled other things before.

    Compile:
    Code:
    ./autogen.sh
    ./configure CFLAGS="-O3"
    make

    Connect and power up ASIC.

    Find correct USB device:
    Code:
    ls /dev/*USB*

    ..or watch syslog while plugging in ASIC:
    Code:
    tail -f /var/log/syslog

    Start mining (replace "ttyUSB0" with device found above and add your pool data):
    Code:
    sudo ./minerd --freq=600 --gc3355=/dev/ttyUSB0 --url= --userpass=user:pass

    You should now see lots of output with yellow "LTC" lines. If you see red lines, that's bad. Wink Anyway, post here if you run into troubles.

    I am not quite sure what the green and red LEDs are about. As far as I can tell there is no English documentation about that anywhere. I assume green (which is on as soon as power and USB are connected) indicates a certain ready state and red (which flashes sometimes) means hardware errors.

    I am getting a lot of "Invalid nonce" errors in the cpuminer output along with red LED flashing. Probably because by mistake I got a 12V/0.5A power supply instead of 12V/5A and chips run low on power. So I can't tell you much about hash rates etc. right now. I'll get another power supply next week, so stay tuned.


    Manfred slub_debug is a bad idea. It will slow down your hashrate by 20%. I've tried it Wink. you should switch to BFGMiner.
    member
    Activity: 96
    Merit: 10
    Hey,

    I'm new to mining but I keep getting this in my feed.  Is this normal or am I doing something wrong?

    https://www.dropbox.com/s/7jw5kdibooeefpl/workupdate.png

    Any help is appreciated. Thanks.
    Having 0 accepted shares in 45 mins is not normal.
    Im using cgminer on 5x GSDs which have been running non-stop for 3.5 days.

    As you can see from the pix, im getting plenty of accepted shares...

    Nice stats, you are getting really few HW errors.
    legendary
    Activity: 1109
    Merit: 1000
    Hey,

    I'm new to mining but I keep getting this in my feed.  Is this normal or am I doing something wrong?

    https://www.dropbox.com/s/7jw5kdibooeefpl/workupdate.png

    Any help is appreciated. Thanks.
    Having 0 accepted shares in 45 mins is not normal.
    Im using cgminer on 5x GSDs which have been running non-stop for 3.5 days.

    As you can see from the pix, im getting plenty of accepted shares...
    sr. member
    Activity: 338
    Merit: 251
    Has anyone managed to compile CGMiner and get it to run stable for 24 hours? I am running about 20 gridseeds, but when I compile CGMiner as per instructions my system crashes after a few hours of mining, giving these messages:

    SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT

    When I use the pre-compiled version, I dont get this error. I really want to use the manually compiled version so I can see the device IDs and tweak each device individually, the pre-compiled version does not show device IDs for me for some reason ;((
    newbie
    Activity: 4
    Merit: 0
    Hey,

    I'm new to mining but I keep getting this in my feed.  Is this normal or am I doing something wrong?

    https://www.dropbox.com/s/7jw5kdibooeefpl/workupdate.png

    Any help is appreciated. Thanks.
    hero member
    Activity: 854
    Merit: 506
    Nice work Manfred, BUT the problem is, it's not stable........RaspPi will crash with 20 of those gridseed units after an uncertain time........even if you modifiy cmdline.txt with slub_debug=FP....

    Code:
    smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110

    Try Hashra controla 1.2.0
    It detects all gridseeds automatically in the webconsole (even 20 of them) and runs a solid 7200 khs (also on remote pool) stable .

    agreed. i have 60 gridseeds. 20 to every pi on 10 port usb hubs. installed it yesterday and ran 24 hours nice and smooth on Coinmine.pw.
    newbie
    Activity: 56
    Merit: 0
    member
    Activity: 413
    Merit: 10
    Anyone know how to setup IP Tables on the Scripta image to avoid the client.reconnect attack?
    legendary
    Activity: 3654
    Merit: 8909
    https://bpip.org
    Is it only me that hashra controlla shows 7.2mh/s and pool shows around 6-6.5?

    What pool are you mining on? Gridseed chips are at their best when you set the pool difficulty to 64. Most pools allows you to hint the difficulty (wafflepool put d=64 as password)

    They are ok at high difficulties too, even middlecoin with 1024 is fine. Only short term variance might be affected.

    Wafflepool's "d=" doesn't go below 512.
    member
    Activity: 96
    Merit: 10
    Is it only me that hashra controlla shows 7.2mh/s and pool shows around 6-6.5?

    What pool are you mining on? Gridseed chips are at their best when you set the pool difficulty to 64. Most pools allows you to hint the difficulty (wafflepool put d=64 as password)

    Scryptguild. Will try setting difficulty to 64, had it on 256.
    member
    Activity: 112
    Merit: 10
    Is it only me that hashra controlla shows 7.2mh/s and pool shows around 6-6.5?

    What pool are you mining on? Gridseed chips are at their best when you set the pool difficulty to 64. Most pools allows you to hint the difficulty (wafflepool put d=64 as password)
    member
    Activity: 96
    Merit: 10
    Is it only me that hashra controlla shows 7.2mh/s and pool shows around 6-6.5?
    legendary
    Activity: 1109
    Merit: 1000
    Does Hashra controla run cgminer or cpuminer?
    The original question contained the phrase "Lazy", which is why I replied in the first place.
    I actually have no idea. It just has a web interface where you enter your pool, and MHZ speed and hit "Start".
    That's about as lazy as it gets. Right up my alley.
    legendary
    Activity: 1270
    Merit: 1000
    Does Hashra controla run cgminer or cpuminer?
    legendary
    Activity: 1109
    Merit: 1000
    whats the best/most up to date raspi image for the lazy people?
    hashra
    legendary
    Activity: 2242
    Merit: 1057
    whats the best/most up to date raspi image for the lazy people?
    member
    Activity: 112
    Merit: 10
    Nice work Manfred, BUT the problem is, it's not stable........RaspPi will crash with 20 of those gridseed units after an uncertain time........even if you modifiy cmdline.txt with slub_debug=FP....

    Code:
    smsc95xx 1-1.1:1.0 eth0: Failed to read reg index 0x00000114: -110

    Try Hashra controla 1.2.0
    It detects all gridseeds automatically in the webconsole (even 20 of them) and runs a solid 7200 khs (also on remote pool) stable .
    Pages:
    Jump to: