As those number approach near 1 ms, we'll begin hitting the usb bus limit per miner.
Those other chip states were part of an earlier attempt to sense per chip health.
The extra details is for the early phase releases and sidehack's burn in testing.

They'll fade further into the debug logs in future builds as they become un-interesing for normal use.

@cjsummers82
new build (0d524aa) : works with prohashing.com in --gekko-noboost mode.   they report vmask support but then rejects shares.  adding to review later pile.

As those number approach near 1 ms, we'll begin hitting the usb bus limit per miner.
Those other chip states were part of an earlier attempt to sense per chip health.
The extra details is for the early phase releases and sidehack's burn in testing.

They'll fade further into the debug logs in future builds as they become un-interesing for normal use.

@cjsummers82
new build (0d524aa) : works with prohashing.com in --gekko-noboost mode.   they report vmask support but then rejects shares.  adding to review later pile.

--gekko-r606-freq

Cool, at least the pools on the supported list are behaving for the miner.
If you would like me to take a closer look at prohashing.com, sent me a pm with a user I can send work shares to.
Ideally your full run syntax to mimic what you see.

You are welcome.

I'm little confused. This thread title says 100GH/s but the link point to 130 GH/s. So is it the same? How can you push them to 130 GH/s?

And where is the 8 port HUB. I don't see it on the link.

 

Hey guys,

I am having some difficulty with the newpacs and hope someone can shed some light. Currently, I am running 6 newpacs off of a BrovSS USB hub with active cooling. All of the sticks are connected to this hub. The frequency they are running off of is 100 Mhz each. The version of cgminer is the gekkoscience cgminer 4.1 and using on Windows 10. I have been able to mine a couple blocks but eventually cgminer displays a “GSH 3 missing nonces” and “GSH 4 missing nonces” and then displays “Toggling reset on GSH 3” amd “Toggling reset on GSH” and my worker goes offline and have to reboot everything each time. Again, I appreciate any help someone can offer.

I don't recall explicitly adjusting anything related to hardware error percentages.
Try attaching a screen shot of what you notice was omitted in this build.

Not much has changed recently on the display side.

Jan 2017 (about two years ago)

http://23.108.83.14/images/2Pac-0004.png

Dec 2018 (this build)

http://23.108.83.14/images/2Pac-0012.png

If you are comparing pre 4.10, I wouldn't be able to answer.  

There would probably be some notes in GitHub.

A new build is available (9d66fd3):

Windows binary: cgminer-4.11.1-windows-gekko-9d66fd3.7z

  - Fixed datetime display.

  - Closed gaps in data transmission to reduce line power fluxations.
    - Spin off dedicated work tx thread.
    - Switch from blocking get_work to get_queued.
    - Send null work to keep asic busy during network glitches and when pool is reacting to block events.

Reminder best practice update process: keep old working (or favorite) build readily available.

• move the existing "cgminer" folder to "cgminer.yyyymmdd"
• clone repository to create a new cgminer folder as noted from first post instructions.