[GUIDE] GridSeed 5-Chip USB, Blade & Black Miner Support/Tuning - page 62.

toxic0n

member

Activity: 413

Merit: 10

Quote from: darkfriend77 on February 22, 2014, 03:07:59 PM

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

After following these steps, is the BTC mode supposed to be disabled? Just wanted to make sure.
Also, is there a patched version without the latest client.reconnect vulnerability or can I compile one myself?

Thinking about it, can we use IP Tables on RPi/Scripta to allow connections to the pools we setup?

wolfey2014

sr. member

Activity: 378

Merit: 250

Quote from: tc61 on March 24, 2014, 10:55:44 AM

Wolfey, can you explain how to change the buffers in windows 7?

Sure.
Start/computer/properties/device manager/ports (comm & lpt)
right click comm port/properties/port settings/advanced
receive buffer = 8
transmit buffer = 14
OK / OK
right click/disable
wait a sec for windows to reset it
right click/enable
wait a sec for windows to reset it

repeat for each comm port

close device manager

start miner/mine/make money Wink

this settings are good for overclocking 850 and above.

remember, you blow it, you eat it Shocked

Wolfey2014

tc61

hero member

Activity: 494

Merit: 500

Wolfey, can you explain how to change the buffers in windows 7?

tc61

hero member

Activity: 494

Merit: 500

Any of you guys running gridseed's and cards on the same computer?

I am running cudaminer with 4 cards and 7 gridseeds, but dont see the pool I'm mining with picking up the right hash rate. Its like -950k .

Should I be using different workers for each?

Thanks

TC

wolfey2014

sr. member

Activity: 378

Merit: 250

Quote from: miner765 on March 24, 2014, 08:24:15 AM

I'm interested - could they be hashing slower or reporting "blank shares" if they have absolutely no fan around them? (at 850MHZ)

No problems here running with no fans at 850MHz. Should only be warm to the touch @ around 85 to 95*F or so. No big deal. They are made to run at 60W so.....with fans of course.

I'm overclocking mine at 1000MHz with no errors and fans powered by 5V with no issues.

One other thing. I found more stable operation by allowing them to run warm instead of ice cold.
This is not unusual where electronic components go.

What you probably need to do is reset your comm port FIFO buffers to a slightly lower setting.
I have found - 14 for Transmit buffer and 8 for Receive buffer works great for 850MHz and above.

Good luck!
Wolfey2014

romang

member

Activity: 112

Merit: 10

Quote from: abbeytim on March 23, 2014, 06:18:35 PM

getting 361.7kh/s cgminer 850 clock ltc mode only

How long has it been running like this? Any crashes?

miner765

member

Activity: 96

Merit: 10

Quote from: ?? on ??

https://www.youtube.com/watch?v=28qHmaZXdmI&feature=youtu.be

So you do have two fans blowing onto them. I was talking about a completely fanless setup.

miner765

member

Activity: 96

Merit: 10

I'm interested - could they be hashing slower or reporting "blank shares" if they have absolutely no fan around them? (at 850MHZ)

pauldulong

newbie

Activity: 59

Merit: 0

I have some problems connecting these to a Windows PC, I tried to follow the guides provided. The problem is, when I connect the HUB all devices show up in the device manager. I can't install the Zagig driver of the HUB (because 10 devices show up - see screenshot) and therefore I can't start CGminer. CPUminer works if I specify a specific COM port for a single unit. My preference strongly goes to get this working on CGminer since I want to over clock and monitor via the API.

Any suggestions??

https://photos-5.dropbox.com/t/0/AAAwtlJIH4Fafe8y6nYQseqlgqwgvPVKNTh2Tt1PIOGdOg/12/3583623/jpeg/320x320/1/_/0/2/screenshot4.jpg/TqlTOiZhhe8w0IEBWvqJb7HpanjD-J1xbvsT_Kyefx8
Sorry for the shitty screenshot
https://www.evernote.com/shard/s12/sh/80639127-52a0-4a86-9cd5-d83d5428662b/3a42e2298dcad63e7a72e5cb3fbbaf2a/res/95578a05-e15a-4545-8510-a3144a32474c/skitch.png?resizeSmall&width=832
https://www.evernote.com/shard/s12/sh/bbf78403-dd53-4111-99c8-56c0c9b7c1c8/def3ce5c8b05ab7558d4302fa9f8717c/res/cfdf990d-d617-42e8-84d4-c196e6567a16/skitch.png?resizeSmall&width=832

darkfriend77

sr. member

Activity: 434

Merit: 265

Quote from: maxzilla on March 24, 2014, 07:06:37 AM

Quote from: darkfriend77 on March 24, 2014, 06:43:05 AM

Quote from: darkfriend77 on March 24, 2014, 05:07:50 AM

Quote from: maxzilla on March 24, 2014, 03:49:52 AM

...

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?

trying out with more then ...

maxzilla

member

Activity: 112

Merit: 10

Quote from: miner765 on March 24, 2014, 07:03:50 AM

Did anyone try making/made a autostart script for pi in case in restarts? e.g. when power restarts -pi starts mining automatically. I think it would be really helpful. And I personally would tip a few coins

CONTROLA starts mining automatically when it boots up.

If you're not using CONTROLA,
you can add the mining command in /etc/rc.local
This command will be called on boot time.

maxzilla

member

Activity: 112

Merit: 10

Quote from: darkfriend77 on March 24, 2014, 06:43:05 AM

Quote from: darkfriend77 on March 24, 2014, 05:07:50 AM

Quote from: maxzilla on March 24, 2014, 03:49:52 AM

...

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?

miner765

member

Activity: 96

Merit: 10

Did anyone try making/made a autostart script for pi in case in restarts? e.g. when power restarts -pi starts mining automatically. I think it would be really helpful. And I personally would tip a few coins

darkfriend77

sr. member

Activity: 434

Merit: 265

Quote from: darkfriend77 on March 24, 2014, 05:07:50 AM

Quote from: maxzilla on March 24, 2014, 03:49:52 AM

...

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

darkfriend77

sr. member

Activity: 434

Merit: 265

Quote from: maxzilla on March 24, 2014, 03:49:52 AM

...

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?

maxzilla

member

Activity: 112

Merit: 10

Quote from: misc2012-de on March 22, 2014, 03:54:49 AM

Quote from: bitcoinreviews on March 21, 2014, 06:52:50 PM

I could really use a tip here. I have followed the instructions or lack of and am still not able to view the interface. I'm sure I'm missing something . . .

Quote from: misc2012-de on March 21, 2014, 05:30:36 PM

Quote from: bitcoinreviews on March 21, 2014, 04:31:26 PM

Quote from: misc2012-de on March 21, 2014, 03:48:41 PM

Quote from: bitcoinreviews on March 21, 2014, 12:03:15 AM

I have the latest firmware for the raspberry pi. It boots up to a command prompt that prompts for

hashracontroller login:

then password.

I cannot find the default settings anywhere in the manuals or online. Can someone please help me out here? Am I doing something wrong?

Thanks in advance!

Fyi, using the controller I'm running at 3.0
3.6 would be nice Wink

If i where you, i would use user:pi pw:hashra Grin

Thanks, I'm curious . . . Where did you come up with that? Lucky guess? Should I have known, lol?

Just trial and error..... Grin

That worked! Thank you very much. I'm still not able to view the interface though after following the instructions in the manuals or lack there of. After logging into hashracontroller command prompt I see this screen. I have tried re-booting and removing the line from the text file that I added to change password.

What am I doing wrong? Huh

Do I need to install Raspian from Noobs before writing the hashra image file to the disk?

Thanks!

Did you enter the IP in your webbrowser ? You are not able to see the interface via ssh-connection. There is no connection necessary, you don't need the ssh password to connect to the hashra gui. Btw. i figured out, that the hashra firmware hashes with really good 7200kh, BUT, the pool only sees around 3000kh.......

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)

wolfey2014

sr. member

Activity: 378

Merit: 250

Quote from: romang on March 23, 2014, 11:52:15 PM

Quote from: darkfriend77 on March 23, 2014, 12:26:49 PM

side view on the rack ... 20 gridseeds, 1 raspberry, 2 usb hubs ... everything powered by the atx psu ..

Love it!

Hey, just a heads up you guys, from the gridseed voltage mod thread... Enjoy!
Nice rig darkfriend! Well done!

Quote from: sandor111 on March 20, 2014, 09:35:57 PM

Quote from: wolfey2014 on March 20, 2014, 08:54:30 PM

Quote from: sandor111 on March 20, 2014, 08:53:52 AM

I am giving out 0.6BTC to the first to get his Gridseed miner stable at 1100 MHz (<10 HW error in 24h) and post the steps to mod the miner. So far I have managed to get it stable at 1013 MHz, but I feel we can push it further.
I have found the only way to push these further is by replacing the 36k resistor with a higher one and playing with PLL voltage, you need to lower the resistance of R211 or R212 by tracing it with a pencil. Measure the voltage across both resistors and it should be around 1.1v total. If you want to increase PLL voltage, trace R212, to decrease it, trace R211 (go back and forth atleast 10-20 times or you will not notice a change). Simply use an eraser to revert the mod. Personally 1.05v seems sweet spot.

Disclaimer: as always, I am not responsible for damage to your miner, do this at your own risk!

What is the test point on the card for checking/monitoring the voltage?

Thanks
Wolfey2014

Core voltage can be measured across the 36k, assuming it's voltmodded (by default it would be the 33k)
PLL voltage can be measured across R211 and R212.

Hello Sandor.
I made the modifications to 2 of my GS5 USB's.
Both jumpers done.
38k @ 5% resistor added in place of the original. I used a 1/8W linear type.
Pencil traced R112 to lower PLL voltage to 1.018 or so -virtually zero red nonce's.
I've never used the pencil trick before. Amazingly effective. Just hope its permanent.
1.05 seemed to high as it still got some red nonce's.
Both GS5's are rock steady for over 40 hours now. No problems at all.

They run sufficiently warm enough now that I put the fan back on them but am running them off the 5V USB with good results. Only pulling about 78mA. 140mA surge at start up but it lasts less than 2 seconds. They are whisper quiet and provide enough air volume to keep them nice and room temp cool. They were running at nearly 118*F fanless as expected after the mods.
I'm sure they can run hotter than that without problems but I also didn't want to just let the fans go to waste Wink

I'm very pleased with their stable performance at 1000MHz!
Running it solo, I'm seeing nearly 600KH's out of it at the pool. Wink

NICE!

So, what's next? How do we squeeze more performance out of them? Any ideas?
I'm game!

Peace!
Wolfey2014

romang

member

Activity: 112

Merit: 10

Quote from: darkfriend77 on March 23, 2014, 12:26:49 PM

side view on the rack ... 20 gridseeds, 1 raspberry, 2 usb hubs ... everything powered by the atx psu ..

Love it!

CartmanSPC

legendary

Activity: 1270

Merit: 1000

Quote from: usao on March 23, 2014, 07:39:21 PM

Quote from: abbeytim on March 23, 2014, 06:18:35 PM

getting 361.7kh/s cgminer 850 clock ltc mode only

That's about what I get, but im worried about the HW errors. I do get a lot of them, about 1-2K over 24 hours at that speed.
When I go down to 800, I only get about 10-20 in a 24 hour period.
Do the HW errors cause any permanent or cumulative damage to the pod?

I have noticed that HW errors depend on the worker diff. The lower the worker diff the higher the HW errors...but im only talking about 10 HW errors over 24 hours worse case.

wolfey2014

sr. member

Activity: 378

Merit: 250

Quote from: b0tzy29 on March 23, 2014, 09:33:33 PM

PLEASE HELP!

Every now and then my miner will stop finding shares. Why does this happen? The green light will stay on for extended period of times and sometime the red light stays on. I feel as though this is a driver issue. The miner has work being sent to it but never finds/accepts any shares and my pool reports hash rate of 0. If someone could help me this, I would be eternally grateful. Thanks in advance.

Right. That's typical. Unfortunately.

Set your comm port Transmit buffer to 14.
Reset your comm ports. Disable, then Enable.
If you are overclocking i.e. over 600MHz, you will probably need to set the Receive buffer to 8, as well.

Give this a try and let me know how it goes.

Funny that the Green LED stays lit, solid? Never seen that before.
Usually blinks on and off in 1 second intervals. That's all it does.
The Red LED blinks on and off in 3 second intervals with intermittent flickering while the hasher is hashing. Wink

Wolfey2014

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