HASHRA CONTROLA on Raspberry Pi for Gridseed - page 9.

vaudvaud

member

Activity: 60

Merit: 10

Quote from: ZBC3 on April 21, 2014, 05:53:48 PM

First I want to thank Hashra for making the image available for download. Now I need some help setting up the Controla. Looking at the output below, it appears that only one gridseed mini is working. Does anyone know what I may be doing wrong?

1.036 Mh/s current hashrate 1.019 Mh/s avg hashrate 69 / 20 Acc./Rej.
28.99 % rejection rate
3 Hardware errors

SCRYPT Miners hashrate 1017 Kh/s

Scrypt Miner 1
Mining...5/5 (0%)339 Kh/s
Scrypt Miner 2
Mining...64/67 (4.48%)339 Kh/s
Scrypt Miner 3
Mining...0/0 (0%)

Total hashing listed on clever mining is 363.

I've seen a few posts similar with this issue using Clevermining, Multipool and a few others... it's your rejects - out of 69, 20 of them were rejected by the pool, that's pretty high - for example on Rapidhash I'm only averaging about a 2% reject rate at most... so it looks to be a pool side issue. You can see others are having the same issue over at the Cleverming thread here.. https://bitcointalk.org/index.php?topic=448649.3840

*edit -never mind - looking closer your miner #3 is not doing anything, and #1 is not doing much at all. I've had a few hang, the best practice I've found is to power up the hub and Gridseeds first, until the red light comes on with each unit, then boot the Pi.

ZBC3

sr. member

Activity: 361

Merit: 250

Rosewill 10 port hub. I've used this hub with several pi's previously.

maxzilla

member

Activity: 112

Merit: 10

Quote from: ZBC3 on April 22, 2014, 06:07:49 AM

I have it set at 800, but I've tried going as low as 700.

hmm strange. What kind of hub are you using?

ZBC3

sr. member

Activity: 361

Merit: 250

I have it set at 800, but I've tried going as low as 700.

maxzilla

member

Activity: 112

Merit: 10

Quote from: ZBC3 on April 21, 2014, 05:53:48 PM

First I want to thank Hashra for making the image available for download. Now I need some help setting up the Controla. Looking at the output below, it appears that only one gridseed mini is working. Does anyone know what I may be doing wrong?

1.036 Mh/s current hashrate 1.019 Mh/s avg hashrate 69 / 20 Acc./Rej.
28.99 % rejection rate
3 Hardware errors

SCRYPT Miners hashrate 1017 Kh/s

Scrypt Miner 1
Mining...5/5 (0%)339 Kh/s
Scrypt Miner 2
Mining...64/67 (4.48%)339 Kh/s
Scrypt Miner 3
Mining...0/0 (0%)

Total hashing listed on clever mining is 363.

I think your clock speed might have been set too high ?

ZBC3

sr. member

Activity: 361

Merit: 250

First I want to thank Hashra for making the image available for download. Now I need some help setting up the Controla. Looking at the output below, it appears that only one gridseed mini is working. Does anyone know what I may be doing wrong?

1.036 Mh/s current hashrate 1.019 Mh/s avg hashrate 69 / 20 Acc./Rej.
28.99 % rejection rate
3 Hardware errors

SCRYPT Miners hashrate 1017 Kh/s

Scrypt Miner 1
Mining...5/5 (0%)339 Kh/s
Scrypt Miner 2
Mining...64/67 (4.48%)339 Kh/s
Scrypt Miner 3
Mining...0/0 (0%)

Total hashing listed on clever mining is 363.

bexwhitt

newbie

Activity: 50

Merit: 0

Quote from: compumine on April 21, 2014, 01:44:02 PM

The SD card I got with my PI is a 16GB. I read that some of you able to use 8GB! Will the new 1.4 fit on an 8GB? What class of cards better to use with PI?

I have used a class-4 8GB card with no problems

but hashra controla will work with a 32GB card as it is Up my stairs ATM

HASHRA

member

Activity: 112

Merit: 10

HASHRA - MINING TO THE MOON

Quote from: compumine on April 21, 2014, 01:44:02 PM

The SD card I got with my PI is a 16GB. I read that some of you able to use 8GB! Will the new 1.4 fit on an 8GB? What class of cards better to use with PI?

New IMG file is 3.88GB, I would suggest to use an 8GB card.

Please see this list for details on SD cards best for the Pi.
http://elinux.org/RPi_SD_cards

compumine

sr. member

Activity: 252

Merit: 250

The SD card I got with my PI is a 16GB. I read that some of you able to use 8GB! Will the new 1.4 fit on an 8GB? What class of cards better to use with PI?

mazedk

sr. member

Activity: 457

Merit: 250

Quote from: compumine on April 21, 2014, 10:15:18 AM

Quote from: HASHRA on April 20, 2014, 08:42:07 AM

Please see hashra.com/support to download version 1.4.0

Now called "HASHRA MINI CONTROLA" as we will have a version for BLADE and another for ATLANTIS.

"MINI" is what we are now calling the Gridseed "5 Chip Devices".

Under the current Hashra controla, you can't do an update?

So I just want to confirm, I have to load the image to the sd cards manually?

You do, it was mentioned earlier that the 1.4 will need a new image.

compumine

sr. member

Activity: 252

Merit: 250

Quote from: HASHRA on April 20, 2014, 08:42:07 AM

Please see hashra.com/support to download version 1.4.0

Now called "HASHRA MINI CONTROLA" as we will have a version for BLADE and another for ATLANTIS.

"MINI" is what we are now calling the Gridseed "5 Chip Devices".

Under the current Hashra controla, you can't do an update?

So I just want to confirm, I have to load the image to the sd cards manually?

bexwhitt

newbie

Activity: 50

Merit: 0

Quote from: HASHRA on April 20, 2014, 12:06:59 PM

Quote from: bexwhitt on April 20, 2014, 12:01:23 PM

what's the root password for 1.4?

it's not root, hashra or pi

Sorry Bexwhitt but the user and password will not be public for this version.

We are working on some features for the future where having the user and password public is just not going to work.

Sorry about that.

so there in no safe way to shut down the pi if I need to make some adjustments, clever

lajz99

hero member

Activity: 756

Merit: 500

Quote from: HASHRA on April 20, 2014, 08:42:07 AM

Please see hashra.com/support to download version 1.4.0

Now called "HASHRA MINI CONTROLA" as we will have a version for BLADE and another for ATLANTIS.

"MINI" is what we are now calling the Gridseed "5 Chip Devices".

When will the BLADE version be released?

HASHRA

member

Activity: 112

Merit: 10

HASHRA - MINING TO THE MOON

Quote from: nogdog21 on April 20, 2014, 09:27:08 PM

Just wanted to say thank you to the Hashra guys and everyone else who helped me narrow down the possible issues with my machines. As it turns out a bad ethernet hub was creating a data collision domain with all the machines. Once removed all was well. Thanks again!!

-Andrew

Good to hear!

nogdog21

newbie

Activity: 28

Merit: 0

Just wanted to say thank you to the Hashra guys and everyone else who helped me narrow down the possible issues with my machines. As it turns out a bad ethernet hub was creating a data collision domain with all the machines. Once removed all was well. Thanks again!!

-Andrew

sandor111

hero member

Activity: 616

Merit: 500

Quote from: mazedk on April 20, 2014, 12:49:17 PM

Quote from: maxzilla on April 20, 2014, 04:43:26 AM

Quote from: vaudvaud on April 19, 2014, 11:50:40 PM

Quote from: mazedk on April 19, 2014, 08:50:16 AM

Hey Hashra

Any idea if/when you guys are gonna be working on individual clock speeds and/or auto-tuning as there is in the lightningasic controller?

Ditto.. this would be a huge benefit, esp for those of us that are running multiple units. Right now I have to downclock to the weakest unit, I have 14 others that can run 50-100 Mhz faster, it's a huge disadvantage to using your product, but I really like the rest of it. Another feature I'd like is in addition for each unit showing the shares/reject like it does now, is to show the HW errors for each unit, it would make it a lot easier to figure out which units are having issues when running so many of them.

And set a failover pool..or long shot add load balance between pools.

what is the algorithm for auto tuning? the slower the unit the lower the clock speed? measured by pool hashrate and hw errors?

if you really want to set different clock speed per miner, this also possible with CONTROLA btw, it's a hack, but it works. I don't know if it will have any effect in overall mining performance though.

PM me if you want to know how to do this.

failover is already available in version 1.4.0

LA coder explained a bit here:

Quote from: sandor111 on April 10, 2014, 08:32:50 AM

To elaborate a bit on how the auto overclocking works, if the chip has hashed for over 600s it will attempt to change the frequency. If there is more than 1 HW error or if the current hashrate is less than the previous hashrate (after that 600s period), it will decrease the frequency, otherwise increase it. It will stop adjusting if the frequency has been decreased atleast once, so make sure to pick a low enough frequency to start with. The frequency adjusts in steps of 25MHz, I have found this to give the most stable results while overclocking, and it also makes sense if you look at how the frequency is calculated from the PLL variables.

I have changed the algo meanwhile, https://github.com/siklon/usb-miner/blob/master/software/cpuminer/gc3355.h
Getting 3700 KH/s poolside consistently with 10 miners, unmodded.

Feel free to compile it for Rpi.

mazedk

sr. member

Activity: 457

Merit: 250

Quote from: maxzilla on April 20, 2014, 04:43:26 AM

Quote from: vaudvaud on April 19, 2014, 11:50:40 PM

Quote from: mazedk on April 19, 2014, 08:50:16 AM

Hey Hashra

Any idea if/when you guys are gonna be working on individual clock speeds and/or auto-tuning as there is in the lightningasic controller?

Ditto.. this would be a huge benefit, esp for those of us that are running multiple units. Right now I have to downclock to the weakest unit, I have 14 others that can run 50-100 Mhz faster, it's a huge disadvantage to using your product, but I really like the rest of it. Another feature I'd like is in addition for each unit showing the shares/reject like it does now, is to show the HW errors for each unit, it would make it a lot easier to figure out which units are having issues when running so many of them.

And set a failover pool..or long shot add load balance between pools.

what is the algorithm for auto tuning? the slower the unit the lower the clock speed? measured by pool hashrate and hw errors?

if you really want to set different clock speed per miner, this also possible with CONTROLA btw, it's a hack, but it works. I don't know if it will have any effect in overall mining performance though.

PM me if you want to know how to do this.

failover is already available in version 1.4.0

LA coder explained a bit here:

Quote from: sandor111 on April 10, 2014, 08:32:50 AM

To elaborate a bit on how the auto overclocking works, if the chip has hashed for over 600s it will attempt to change the frequency. If there is more than 1 HW error or if the current hashrate is less than the previous hashrate (after that 600s period), it will decrease the frequency, otherwise increase it. It will stop adjusting if the frequency has been decreased atleast once, so make sure to pick a low enough frequency to start with. The frequency adjusts in steps of 25MHz, I have found this to give the most stable results while overclocking, and it also makes sense if you look at how the frequency is calculated from the PLL variables.

HASHRA

member

Activity: 112

Merit: 10

HASHRA - MINING TO THE MOON

Quote from: bexwhitt on April 20, 2014, 12:01:23 PM

what's the root password for 1.4?

it's not root, hashra or pi

Sorry Bexwhitt but the user and password will not be public for this version.

We are working on some features for the future where having the user and password public is just not going to work.

Sorry about that.

bexwhitt

newbie

Activity: 50

Merit: 0

what's the root password for 1.4?

it's not root, hashra or pi

bexwhitt

newbie

Activity: 50

Merit: 0

Quote from: maxzilla on April 20, 2014, 09:41:33 AM

Quote from: omgitsjoe on April 20, 2014, 08:38:33 AM

Quick question for you guys. I have 20 gridseeds running on controlla. would it be worth it to dual mine? also if it is worth it i have a spare seasonic 1050watt psu, would that be enough power?

Personally I don't think it's worth it.

I've tested it with 10 miners. 20 makes controla unresponsive in dual mode. I set the btc cores to 5 in system settings. It get's like 3.5 gh for sha and 300k for scrypt per miner. So for a 10 unit, 35ghs / 3mhs

BTC mining on the gridseed would probably not even pay for the electric used these days, it's a feature that when designed was at a difficulty that would have been making money but that ship has long since sailed.

Topic: HASHRA CONTROLA on Raspberry Pi for Gridseed - page 9. (Read 39584 times)