1 TH/s-miner with only 16 GH/s

[inzli]

have you tried contacting the company about your findings?

Yup, and they claim that I only can use the machine with BTCGuild with the setting 1024/1THs as minimal diff. So this would be a limitation I can't accept.

Did you try BTCGuild with 1024 min diff? You'd need to run it for a day, but at least you'd know if they were completely full of shit or just a little full of shit.

Okay, BTCGuild with 1024 min diff works with somewhat over 1 TH/s. However, this means I can't put it on other pools - unless I want my heater to run for 16 GH/s...

[inzli]

I have the exakt same issue.
I received my machine 1 day ago and after setting up i was happy. Until today.
I normally use Slush pool. I now tried Elegius and GHashIO with same result.
Besides that,  I can´t login with SSH, i dont have the correct user and password... Anyone know the default password? No info in the box... The webinterface  doesn´t require user and password.
In the display and also in webinterface all looks perfect. 1.02 Th and WU 12m somethings. Looks OK.
BUT. No money, no hashrate on pool side. Only between 1-16 Gh. Mostly 1 Gh.

I am totally out in the blue here.
Any suggestions?

Thanks

Urbie

Don't know if we have the same machine, but here the default user is pi, password is raspberry. sudo su makes you root where you can set your root-password. At least worth a try...

[inzli]

Hmm, my miner.php there is showing you are mining on Eligius ... which has been DDOSed for a few? days.

Although they like to say their magical unicorns can solve all DDOS problems, maybe that's the reason?

I'm running one of my micro-pool (hey, I like this term!) with ten Antminer on Eligius with no problem. However, Eligius, ghash and others don't work with this machine, only BTCguild - at the moment...

[inzli]

It seems as if they have produced their own little hacks for running cgminer....

Since cgminer is released under a free license that insists all code modifications distributed in binary form must be available on request, since you have received a cgminer binary that is modified from the original, you can ask them for the source code to their modifications and they will be obliged to provide their source modifications within 30 days or they will be in violation of the license agreement and not be allowed to further distribute their binaries or be up for legal action.

See:
https://www.gnu.org/copyleft/gpl.html

Interesting for me is the fact that there is a lot of references to bitmine in the history. For example here in the history of user "pi":

  173  gvim bitmine.h
  392  cd cgminer-bitmine-A1-scratchpad/
  395  cd cgminer-bitmine-A1-scratchpad/
  398  cd cgminer-bitmine-A1-scratchpad/
  399  gvim driver-SPI-bitmine-A1.c
  402  cd lichen/cgminer-bitmine-A1-scratchpad/
  404  cd lichen/cgminer-bitmine-A1-scratchpad/
  406  cd lichen/cgminer-bitmine-A1-scratchpad/
  408  cd lichen/cgminer-bitmine-A1-scratchpad/
  445  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  447  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  454  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  457  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  460  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  464  gvim ./lichen/old/cgminer-bitmine-A1-scratchpad/driver-SPI-bitmine-A1.c
  466  gvim ./lichen/old/cgminer-bitmine-A1-scratchpad/run.sh
  469  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  474  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  480  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  487  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  488  gvim driver-SPI-bitmine-A1.c
  495  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  509  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  519  gvim /home/pi/lichen/old/cgminer-bitmine-A1-scratchpad/run.sh
  520  /home/pi/lichen/old/cgminer-bitmine-A1-scratchpad/run.sh &
  521  sudo /home/pi/lichen/old/cgminer-bitmine-A1-scratchpad/run.sh &
  523  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  548  cd /home/pi/lichen/old/cgminer-bitmine-A1-scratchpad
  550  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  562  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  637  cd lichen/old/cgminer-bitmine-A1-scratchpad/


Now given the fact that Bitmine in Switzerland can't deliver, but here obviously some software from Bitmine pops up in a Chinese machine which is sold from a Swiss company, I guess I'll use some forensic tools to examine this issue further...

[kano]

Well it shouldn't be hard to see where the device is actually mining.
A tcpdump on the network should show where packets are going to and coming from.
More so, if you start the log when it is first powered on, it should show all pools and accounts it is connecting to.

[Gator-hex]

A1 chips need a high diff or a pool that supports 0 diff (auto).

I run my Hex8A1 (8x A1 chips) on BitMinter and BTCGuild.

I've also thought the new Dragon miner (4 boards x 8 chips) may be running too low voltage which would result in high hardware errors/rejects.

[kano]

..
In the display and also in webinterface all looks perfect. 1.02 Th and WU 12m somethings. Looks OK.
...

WU 12/m means 829MH/s ... so not what it should be.
for 1TH/s WU should be around 14000/m

[Kenshin]

Well it shouldn't be hard to see where the device is actually mining.
A tcpdump on the network should show where packets are going to and coming from.
More so, if you start the log when it is first powered on, it should show all pools and accounts it is connecting to.

Or Wireshark for people who like GUI.

[inzli]

Well it shouldn't be hard to see where the device is actually mining.
A tcpdump on the network should show where packets are going to and coming from.
More so, if you start the log when it is first powered on, it should show all pools and accounts it is connecting to.

Or Wireshark for people who like GUI.

tststststs... as an old bash-er, I do not like GUIs :-)

[eleuthria]

It may be a problem with the machines ability to handle low difficulties, causing it to basically create a backlog it can't escape from.  Have you tried setting your difficulty to 1024 on another pool?  You're going to be running at 512-1024 diff no matter what, standard variable difficulty on all pools is going to put you in that range if your machine is functioning properly.

[Anddos]

why wouldnt the company tell you about this before figuring it your self tho?

[ManeBjorn]

That is weird.
Have you tried a packet sniffer to see if it is mining somewhere else as well?
I have heard complaints of some of the miners that are run with Pi's using a small amount of mining power to mine to a different pool with out showing up.
I wonder if that is going on here but it malfunctioned and instead is mining mostly to the hidden setup.

It seems as if they have produced their own little hacks for running cgminer....

Since cgminer is released under a free license that insists all code modifications distributed in binary form must be available on request, since you have received a cgminer binary that is modified from the original, you can ask them for the source code to their modifications and they will be obliged to provide their source modifications within 30 days or they will be in violation of the license agreement and not be allowed to further distribute their binaries or be up for legal action.

See:
https://www.gnu.org/copyleft/gpl.html

Interesting for me is the fact that there is a lot of references to bitmine in the history. For example here in the history of user "pi":

  173  gvim bitmine.h
  392  cd cgminer-bitmine-A1-scratchpad/
  395  cd cgminer-bitmine-A1-scratchpad/
  398  cd cgminer-bitmine-A1-scratchpad/
  399  gvim driver-SPI-bitmine-A1.c
  402  cd lichen/cgminer-bitmine-A1-scratchpad/
  404  cd lichen/cgminer-bitmine-A1-scratchpad/
  406  cd lichen/cgminer-bitmine-A1-scratchpad/
  408  cd lichen/cgminer-bitmine-A1-scratchpad/
  445  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  447  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  454  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  457  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  460  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  464  gvim ./lichen/old/cgminer-bitmine-A1-scratchpad/driver-SPI-bitmine-A1.c
  466  gvim ./lichen/old/cgminer-bitmine-A1-scratchpad/run.sh
  469  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  474  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  480  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  487  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  488  gvim driver-SPI-bitmine-A1.c
  495  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  509  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  519  gvim /home/pi/lichen/old/cgminer-bitmine-A1-scratchpad/run.sh
  520  /home/pi/lichen/old/cgminer-bitmine-A1-scratchpad/run.sh &
  521  sudo /home/pi/lichen/old/cgminer-bitmine-A1-scratchpad/run.sh &
  523  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  548  cd /home/pi/lichen/old/cgminer-bitmine-A1-scratchpad
  550  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  562  cd lichen/old/cgminer-bitmine-A1-scratchpad/
  637  cd lichen/old/cgminer-bitmine-A1-scratchpad/


Now given the fact that Bitmine in Switzerland can't deliver, but here obviously some software from Bitmine pops up in a Chinese machine which is sold from a Swiss company, I guess I'll use some forensic tools to examine this issue further...

[kano]

It may be a problem with the machines ability to handle low difficulties, causing it to basically create a backlog it can't escape from.  Have you tried setting your difficulty to 1024 on another pool?  You're going to be running at 512-1024 diff no matter what, standard variable difficulty on all pools is going to put you in that range if your machine is functioning properly.

Yeah it may have internal firmware diff mining and if it is mining at 1k diff (i.e. only returning nonces at 1k diff) while the pool is asking for 10diff, it will effectively be returning only 1/100 of the nonces the pool wants and this would make it appear 100 times slower than it is.

[LouReed]

Could you have gotten one of these: http://bitmine.ch/?p=5178

[inzli]

Could you have gotten one of these: http://bitmine.ch/?p=5178

Nope. I've ordered with Bitmine (yeah, beat me), so I would recognize them :-)

[blackvoice]

I think the saler cheat you

You should return it

[Leogheo]

I think the saler cheat you

You should return it

That's sound like a true ! I guess that company would like to get money despite everything

[TrollboxChamp]

I think its honestly just a compatibility issue with the getwork software poolside.

The miner is showing actual hashrate clientside and then share hashrate poolside and its submitting shares at a rate of 16gh aka 1.06% share submission rate(99% stales/rejects). My guess...

[HighInBC]

I have this machine and it is getting 1.05 terrhash per second no problem. I used btc guild at difficulty 1024. No problems.

My guess is that lower difficulty settings result in so many hits that it cannot communicate them fast enough. At 1024 I am getting a hit every few seconds. It may also be optimized for that difficulty.

Thanks to the guy who told me the ssh username and password!

[-ck]

I think its honestly just a compatibility issue with the getwork software poolside.

The miner is showing actual hashrate clientside and then share hashrate poolside and its submitting shares at a rate of 16gh aka 1.06% share submission rate(99% stales/rejects). My guess...

getwork has nothing to do with modern mining. It's almost certainly just a minimum share diff in their broken driver implementation, as discussed before.