Share is Above Target error - how do I fix this?

[bfriedly]

Running 2 Gridseed units and have the BFGMiner that was customized to work with the gridseed units. Its spitting out errors on GSD 0 and 1. Both are getting rejected and it says the "Share is above Target".

I've got the virtual comport drivers installed and I can see the hash changing on a regular bases for both GSDs. Anyone have any ideas on how to get around this situation?

[1715305819]

1715305819

[1715305819]

1715305819

[1715305819]

1715305819

[1715305819]

1715305819

[1715305819]

1715305819

[Chrithu]

Hmm I do not own gridseeds, but I get these errors when trying to mine scrypt coins using my Antminers.

My suspicion is that you forgot to put your BFGMiner into scrypt mode via the --scrypt start parameter.

[bfriedly]

Don't think that is it. Here is the bat file I use to login.

Bfgminer -S gridseed:all --set-device gridseed:clock=850 --scrypt -o stratum+tcp://stratum.bitcoin.cz:3333 -u xxx.x -p xxx

Also as a note, I'm trying to do BTC, not LTC. I have some ASIC USB antminers running on another machine that are working fine but after I got my hands on these gridseed devices, I haven't been able to get them working with any version of BFGminer yet.

I could be overlooking something obvious here so I apologize if that's the case. Still trying to learn the ropes (Its only been a couple days since I got into BTC mining...)

Thanks all!

[Chrithu]

Oh ok. If you want to mine BTC you need to actually remove the --scrypt option.

To explain:

BTC uses the sha256 algorithm for the proof of work in mining. ASICS are Specially designed chips to solve this algorithm fast.

LTC and many other altcoins use the SCRYPT algorithm, which is a memory intensive algorithm (that is derived from the SHA256 afaik) especially designed to make most sha256 asics invalid for mining those coins.

The Gridseeds are a hybrid hardware that is capable of mining both SCRYPT and SHA256 coins, but you need to set the mining software in the approriate mode to use the correct algorythm. BFGMIners default is SHA 256, hence the need to use the --scrypt option if you want to mine scrypt coins.

[bfriedly]

Thanks for the feedback and suggestions.

It loads now - and shows GSD 0 and 1, which I'm thrilled about. After a short period of time the first set of #'s start refreshing (Ie: 358.9/359.3/ etc). But the 2nd set of #'s continually show 0.0kh/s. I also get a "Stratum from pool 0 requested work update" and an occasional "Stratum from pool - detected new block.

Heres a link to the screen snipping: http://1drv.ms/TwzeQy

Here is the batch file content I'm using:

Bfgminer -S gridseed:all --set-device gridseed:clock=850 -o stratum.bitcoin.cz:3333 -u username.1 -p xxx

While I'm not sure if it will make a difference the version of BFGminer I'm using is 3.10. I know its an older version but when I downloaded the newer version (3.99 was the latest I could find that said it would work with gridseed units for BTC) I am not able to get the software to detect the units at all. 3.10 is the only version I've found that can detect the GSD's.

Also, I have the two gridseed units connected to a BuyaHash 20 port USB hub. I already installed the virtual com port software so I think I'm good there.

[topnetdeal]

Do not use sha-256 with gridseed, mining scrypt more You earn.

Now You mining bitcoin's, but the speed is shown suitable for scrypt. Too slow, so you will not find share.

[Chrithu]

Ok like I said I am not experienced with the gridseeds myself. As far as I could see you definetly set up bfgminer correctly but for some reason it isn't using the Gridseeds at their full speed and thus doesn't find shares to send to the pool.

Maybe you should try to follow the guides in this thread's first post step by step.

[emu512]

AS far as I know,lowering the core clock until it adjusts fixes this error.