OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[LARTAS]

Thanks. I hope It works. Great¡¡¡

[1534466582]

1534466582

[1534466582]

1534466582

[1534466582]

1534466582

[1534466582]

1534466582

[1534466582]

1534466582

[1534466582]

1534466582

[-ck]

Thanks. I hope It works. Great¡¡¡

The new release was not specifically for your problem though it might help if you're lucky. You seem to still have hardware instability.

[LARTAS]

Thanks. I hope It works. Great¡¡¡

The new release was not specifically for your problem though it might help if you're lucky. You seem to still have hardware instability.

Yes . i have try and it not started, says differente
"checksum bad". I will use again 4.3.4

[-ck]

Thanks. I hope It works. Great¡¡¡

The new release was not specifically for your problem though it might help if you're lucky. You seem to still have hardware instability.

Yes . i have try and it not started, says differente
"checksum bad". I will use again 4.3.4

The cointerra changes are for new firmware only which you won't have.

[LARTAS]

Thanks. I hope It works. Great¡¡¡

The new release was not specifically for your problem though it might help if you're lucky. You seem to still have hardware instability.

Yes . i have try and it not started, says differente
"checksum bad". I will use again 4.3.4

The cointerra changes are for new firmware only which you won't have.

But Firmware is with Beaglebone. Perhaps I need to update USB Driver for windows Goldstrike For CGMINER 4.3.5 works. But There isn't newer

[-ck]

The cointerra changes are for new firmware only which you won't have.

But Firmware is with Beaglebone. Perhaps I need to update USB Driver for windows Goldstrike For CGMINER 4.3.5 works. But There isn't newer

Yes but the firmware updates both the mining device and the beaglebone cgminer. There is no new firmware yet. This code is all experimental for the next firmware which is not released yet so regular users should not use it...

[LARTAS]

The cointerra changes are for new firmware only which you won't have.

But Firmware is with Beaglebone. Perhaps I need to update USB Driver for windows Goldstrike For CGMINER 4.3.5 works. But There isn't newer

Yes but the firmware updates both the mining device and the beaglebone cgminer. There is no new firmware yet. This code is all experimental for the next firmware which is not released yet so regular users should not use it...

Yes

I think the problem is in that device
http://www.sfcable.com/1504-SF-12.html?utm_medium=shoppingengine&utm_source=productads
something like that which TERRACOIN Put there
I want to conect each CTA to Computer but
How can I do to CTA'S don't appear like COM Ports and Appear like USB Devices

[terrapinflyer]

Hey guys,

I keep getting an error that I have never seen before running cgminer 4.3.4 on Arch via the Raspi.

The error is BaB0: Delay getting work reply

I cant find any one else having this issue, any help is greatly appreciated.

[kano]

Hey guys,

I keep getting an error that I have never seen before running cgminer 4.3.4 on Arch via the Raspi.

The error is BaB0: Delay getting work reply

I cant find any one else having this issue, any help is greatly appreciated.

Firstly, this should show up in the API stats as [SPI Waiting] or [SPI Sent] growing.
That's the work waiting to be sent to the board or that has been sent but waiting for the code to process the reply.
It should be low (0 or 1 - possibly 2 ...)

One most likely cause of this is if you are getting a LOT of HW errors due to faulty hardware it can overload the CPU checking all the bad results.
This will show up as high CPU usage.
It can thus starve the SPI thread of CPU so it takes longer than expected to send the work and store the reply.

To check your CPU usage:
In one terminal window run 'top' and press 'P'
In another window do an API summary ... and at the same time note the CPU usage of cgminer under TIME+

e.g. for me just now:
 10821 root      10 -10  199356  17700   2716 S 15.0  3.7  73:59.57 cgminer-4.+
and
 [Elapsed] => 31890

So that says cgminer elapsed total 31890 seconds, used 73m 59.57s of CPU or ... 13.92% of CPU for my 7 boards - not bad

Uptime for me shows:
 load average: 0.26, 0.57, 0.62
So clearly no CPU issue

Also check [Delay Bands] and see if they are high.
Most work should be in "<1.5" or less

The API estats (or API stats if you are running an older cgminer) has a truck load of data in there for BaB0 saying what is going on
I guess a link to a pastebin of that, if you are not getting high CPU, would help.
Also add API summary since that says a lot of useful info also.

[xjack]

- Driver updates for cointerra, minion, hashfast, A1, antminer S1.

Is there a changelog somewhere for the updated hashfast driver?

edit: found it "Avoid dereference on getting API stats on partially initialised HFA instances"

Thanks!

[kano]

I've created an AntMinerS2 firmware.
Master cgminer code - and no changes/hacks (that are required for the S1)

I've been using various versions of this for a while now without cgminer problems.
However, do consider it still in testing until it has been run more widely ... than just a few people
It's easy to undo - just flash a Bitmain 'firmware'

There are issues with the Bitmain AntMinerS2 firmware that for some would make this upgrade rather important

The README and "How to" information is here:
https://github.com/kanoi/cgminer-binaries/tree/master/AntS2

Some of that:

How to upgrade your AntS2:
Download the lastest 'firmware' file from:
 https://github.com/kanoi/cgminer-binaries/tree/master/AntS2
 The filename will be like:
   initramfs.bin.SD-Kano-NNNNNNNNNNNNNN.tar
  where NNNNNNNNNNNNNN is the date stamp
  the newest one will be last down the page
 To download it, you will need to first click on the filename and then on the
  page that comes up, "right-click" on "View Raw" and then "Save Link As..."
  or "Save Target As..." to save it on your computer

Upgrading is the same as the standard Bitmain 'firmware' upgrade details:
 From the AntS2 web interface tab: "System" -> "Upgrade":
  make sure you have "Keep settings:" ticked,
  click on "Browse..." to select the 'firmware' file you downloaded
  then click on "Flash image..."

See "SD Recovery" below for possible ways how to recover the SD card if the
 udpate was interrupted or failed

Releases:

The cgminer binary is compiled on a BeagleBone Black with the configure:
 CFLAGS="-W -Wall -O2" ./configure --enable-ants2

11-Jun-2014
 initramfs.bin.SD-Kano-20140611145346.tar
 cgminer official release version 4.3.5 plus initial 'firmware' changes

Changelog:

Initial 11-Jun-2014
 cgminer 4.3.5 with a modified AntS2 driver - see master git for details
 Web "Miner Status" uses standard cgminer API fields, highlights some issues
  in the "AntMiner" section in colour, provides good/bad chip counts and also
  displays an expected performance
 Web "Miner Configuration" expanded to include setting "API Allow"
 LCD display includes block found count "N" in the bottom left "B:N"
 If an executable exists "/config/cgminer", that will be used instead of the
  system /usr/bin/cgminer - this allows for easy cgminer binary upgrades
 If you factory reset the AntS2, the default mining is Kano instead of Bitmain
 Tidied up the default mining configuration to be only in one place (rather
  than 3 copies of it) /etc/cgminer.conf.factory
 Web interface and LCD report "Ant Miner/K" and a little (kano) in the top
  right of the AntMiner image - so you can definitely see if you are running
  a modified Kano 'firmware' or an original Bitmain 'firmware'

[PatMan]

Kano is king!!!  You da man 

Will begin testing straight away & report back - many, many thanks Kano!!

[ManeBjorn]

Did support for the R-Box make it into this release?  I did not see it listed but I was hoping it made it in there.
Thanks again. 

New release: Version 4.3.5, 10th June 2014

Please note linux x86_64 builds are now based on ubuntu 14.04


Human readable changelog:

- Fixed the problem where if there was no internet connection at startup for long enough, it would never connect to anything and the display would not refresh to tell you of it.
- Fixed some crashes due to trying to act on corrupted USB messages. You will now get error messages about invalid memcpy sizes instead when there is a corrupt message. This means you have hardware issues.
- Fixed the disable-libcurl build.
- Added some checking of messages received via stratum to prevent security issues or crashes from corrupt/malicious intermediate pools.
- Driver updates for cointerra, minion, hashfast, A1, antminer S1.


Full changelog:

- Cointerra driver updates.
- Sleep before retrying in the test pool thread after a pool has died
- Use valid_ascii testing for job_id since it need not be hex only
- Only show slow/down message till pool is flagged idle
- Do some random sanity checking for stratum message parsing
- Keep looking for when a pool comes to life at startup and touch the logwin so
the message is not invisible
- Fix no libcurl build
- Added Drillbit Thumb to udev rules.
- Avoid dereference on getting API stats on partially initialised HFA instances
- A1: add support for updated product variants, small fixes
- Add one more usbutils fix
- Convert uses of usbutils memcpy to cg_memcpy
- Add a sanity checking memcpy function which checks for overflows
- minion - count force use reread
- minion - add a disabled ioctl() test
- minion - add more checking of SPI results for corruption
- minion - optional (disabled) ioctl() debug
- Increase S1 overheat to 75 degrees C
- Add ruby api-example to API-README
- minion - allow core selection at runtime
- API - lcd all-in-one brief summary

[BenTuras]

I have a rather technical question about using cgminer with Bitfury based hardware (The OneStringMiner boards I am selling).
In driver-bitfury.c, the target that is sent to the boards is always ffffffff, no matter what the difficulty is on the pool.
I think the value of ffffffff corresponds to a difficulty of 2.
If the pool is set or gets to a higher difficulty, a lot of shares are thrown away because they are above target.
This means a lot of useless traffic between the boards and the host computer running cgminer.

In order to prevent this, I changed the above mentioned ffffffff to 0fffffff to lower the number of shares that are thrown away. A simple trick with a drawback, the speeds shown by cgminer is now incorrect. Not a big issue, but it would be nice if the values would be correct.
Also 0fffffff corresponds with a fixed pool difficulty. It would be better if this would be changed automatically when the pool sets a new difficulty.

Of course, the speed that I see on the pool is correct, because that's calculated by the pool software.

What's the best way to improve this ?

[-ck]

From the protocol document:

Code:

       target <target number>

The 'target' command tells the firmware the desired difficulty of returned blocks. The target number
is a 32 bit hexadecimal number, which gives the upper limit of the hash. The firmware compares the
target value with the 7th word of the hash (the 8th word must be zero).
If the target number equals FFFFFFFF, the firmware returns difficulty 1 shares. If the target value
equals 7FFFFFFE, the firmware only returns difficulty 2 shares. For any given difficulty, target
should be FFFFFFFF / difficulty.

As for cgminer, the hashrate reported is based on shares returned via bitfury_rate * a fixed value for one full nonce range (0xffffffff) by the number of info->nonces returned which increments in parse_bxf_submit.  As the full nonce range is hardcoded in the bitfury rate function, it would need a rewrite to support variable difficulty being changed on the fly or if you want to play with a hardcoded value for your own use, just change the full nonce range to how much bigger you're aiming for, so if you halve the target diff you double the value. As you can see it affects a lot of different types of devices and the code for associating a changing diff with the nonce range would need quite some rework still.

[IYFTech]

Hello guys,

First off, thanks to Kano for all his work on the S1 & S2's - it is appreciated - thanks 

I've been testing out the newly released S2 firmware on one of my S2's in the hope it would improve it's compatibility with p2pool, but I'm unable to even connect with my local node using the "stratum+tcp" prefix using both the IP address or the web address - the pool shows up as "dead" on the S2 web interface. I've also tried using "http" which gives me 100% stales & just the IP address:port but still am unable to connect - can you give me any pointers at all?

Cheers guys.

[BenTuras]

As for cgminer, the hashrate reported is based on shares returned via bitfury_rate * a fixed value for one full nonce range (0xffffffff) by the number of info->nonces returned which increments in parse_bxf_submit.  As the full nonce range is hardcoded in the bitfury rate function, it would need a rewrite to support variable difficulty being changed on the fly or if you want to play with a hardcoded value for your own use, just change the full nonce range to how much bigger you're aiming for, so if you halve the target diff you double the value. As you can see it affects a lot of different types of devices and the code for associating a changing diff with the nonce range would need quite some rework still.

So, if I understand you correctly I need to make the following changes to driver-bitfury.c :

   sprintf(buf, "target ffffffff\n");
into
   sprintf(buf, "target %08lx\n",(0xffffffff/pool_difficulty));

      ret = (double)0xffffffff * nonce_rate;
into
      ret = (double)(0xffffffff/pool_difficulty) * nonce_rate;

      info->nonces++;
(occurs twice) into
      info->nonces += pool_difficulty;

I do understand that I also need to take into account that more than one OneStringMiner could be connected and that they could be mining on different difficulty, but normal use will be one or more connected miners mining on the same pool on the same account and hence the same difficulty.

I also understand that if you change it for one device, you will be asked/want to change it for all.
To me it looks like a valuable change, given the waste of traffic that now occurs.

[mdude77]

I've created an AntMinerS2 firmware.
Master cgminer code - and no changes/hacks (that are required for the S1)

Thanks!

I applied it to one of my S2s.  Results haven't been good.

It won't connect at all to p2pool.  On the p2pool side, it throws a TON of errors I've never seen before.
I then pointed it to my slush proxy for Eligius.  Every single hash is rejected. "u'high-hash'".

Going back to prior firmware...

M

[PatMan]

Yup, same here - unable to connect to p2pool node. I'm also seeing some HUGE hash rate variation - anything between 2000Gh/s(!) to 600Gh/s - but the average rate is slightly higher than the standard firmware. I'll keep playing.......

[mdude77]

Yup, same here - unable to connect to p2pool node. I'm also seeing some HUGE hash rate variation - anything between 2000Gh/s(!) to 600Gh/s - but the average rate is slightly higher than the standard firmware. I'll keep playing.......

I couldn't get any hashrate to p2pool or slush's proxy.  I like the additional visual changes to the status page.. however the avg hashrate was unintelligible (said something like 16423), and the 5m hashrate was blank.  API response on hashrate was also gone/unintelligible.

M