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

[Mikestang]

I've put yet another updated AntS3 update archive in my binaries git hub of latest 4.9.2 cgminer.
For details and installing: https://github.com/kanoi/cgminer-binaries/tree/master/AntS3

It's another (minor) update to the previous AntS3 release I did:

Code:

2015-Jul-10 Update cgminer-ants3-4.9.2-94e04f6-3.tgz
----------------------------------------------------
Add a table of miner hardware settings to the bottom of the Miner Status page

Tested and running on my pool of course

If you are already running the 2015-Jul-7 version (the previous update)

Code:

If you update from the 2015-Jul-7 version to the 2015-Jul-10 version,
instead of 'sync' and 'reboot' at the end of the update,
you can instead run this command on your AntS3:
 rm /tmp/luci-modulecache/*
Then the update is complete and nothing else needs to be done.

Very cool, no reboot necessary is nice.

Is there somewhere I can read what each new field is?  Some are obvious, but I'm curious about a couple.

[kano]

...

Very cool, no reboot necessary is nice.

Is there somewhere I can read what each new field is?  Some are obvious, but I'm curious about a couple.

They are on the Miner Configuration page and the Advanced Settings page (for most)

Voltage is ... voltage
Timeout/Frequency/RegData are the values you choose for the Frequency drop down on the Advanced page.
 See /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua

WorkDelay is the new option I added to fix the massive waste of CPU by their driver ...

MinerCount and AsicCount match the hardware so you don't change them.

[TheRealSteve]

Fairly minor bug report - local impact is negligible (only cosmetic), API impact would depend on what polling software does with the information.  I suspect the scheduling feature isn't used very much.

summary: Devices declared as SICK -> DEAD outside of scheduled on time
platform: Windows 8x64
software: cgminer 4.9.2
reliability: always
description:
When using --sched-start, if the scheduled start time is long enough into the future from launching, devices are declared sick (60s), and ultimately dead (10m).
When using --sched-start in combination with --sched-stop, then after the scheduled stop time, devices are declared sick (60s), and ultimately dead (10m).

[luthermarcus]

I've put yet another updated AntS3 update archive in my binaries git hub of latest 4.9.2 cgminer.
For details and installing: https://github.com/kanoi/cgminer-binaries/tree/master/AntS3

It's another (minor) update to the previous AntS3 release I did:

Code:

2015-Jul-10 Update cgminer-ants3-4.9.2-94e04f6-3.tgz
----------------------------------------------------
Add a table of miner hardware settings to the bottom of the Miner Status page

Tested and running on my pool of course

If you are already running the 2015-Jul-7 version (the previous update)

Code:

If you update from the 2015-Jul-7 version to the 2015-Jul-10 version,
instead of 'sync' and 'reboot' at the end of the update,
you can instead run this command on your AntS3:
 rm /tmp/luci-modulecache/*
Then the update is complete and nothing else needs to be done.

Hey I got to say thanks for that july 10 update love the table at the bottom I can actually see if my settings go through instead of rely on faith. I knew something wasn't setting right with my miner and now i actually see my hashrate at the point it is suppose to be with the overclocking.
This exceeded my expectations and was worth the wait!
Simple things make me so happy.
Wow BITMAIN definitely fails to do there job after seeing what could be possible and yet so simple.

Question though if i do a hard rest will it load your firmware I notice i get better performance after hard resets on some miners.

[kano]

...
Hey I got to say thanks for that july 10 update love the table at the bottom I can actually see if my settings go through instead of rely on faith. I knew something wasn't setting right with my miner and now i actually see my hashrate at the point it is suppose to be with the overclocking.
This exceeded my expectations and was worth the wait!
Simple things make me so happy.
Wow BITMAIN definitely fails to do there job after seeing what could be possible and yet so simple.

Question though if i do a hard rest will it load your firmware I notice i get better performance after hard resets on some miners.

A power cycle doesn't lose the changes.

A Factory reset or a bitmain firmware update will put it back to the bitmain firmware, then you need to run the update again.

[Mikestang]

WorkDelay is the new option I added to fix the massive waste of CPU by their driver ...

MinerCount and AsicCount match the hardware so you don't change them.

Thank you, I could figure out the first ones you listed, but these were some I was wondering about.

I figured the two counter were tied to hardware, but what do they mean?
Should WorkDelay ever read anything beside 1; is it a 0/1 toggle?
What is an example of BadWork?

[kano]

WorkDelay is the new option I added to fix the massive waste of CPU by their driver ...

MinerCount and AsicCount match the hardware so you don't change them.

Thank you, I could figure out the first ones you listed, but these were some I was wondering about.

I figured the two counter were tied to hardware, but what do they mean?
Should WorkDelay ever read anything beside 1; is it a 0/1 toggle?
What is an example of BadWork?

Work delay is only settable by editing /etc/init.d/cgminer - but for the S3, 1 is optimal and it's the default inside cgminer.
I spent days/weeks adjusting it from 1 to 3 and ended up deciding 1 was best
1ms delay means it checks to send work about 1000 times a second (instead of about 60,000 times - wasting much CPU)

The two counters - well - ask bitmain they put them in the --bitmain-options
The first one is how many sets of data are returned ... so that's why the table above it has 2 rows.
It's somewhat like saying it has two cards (as the S3 does)

BadWork is a new cgminer API value - it counts work from the pool that has very few transactions - i.e. bad for bitcoin.
Some pools send one of them every network block change ...

[kano]

Since I have no idea which versions you are talking about and which AntMiner you have ... I'll take a guess.

The S3 update in https://github.com/kanoi/cgminer-binaries/AntS3/

Once you have updated it, it is wise (as it says there) to check the settings and see that they are what you had before.
The easiest way to do that is to look at the "Miner Status" page at the bottom when cgminer is running.
If you've got the Frequency set a lot higher than standard then you can expect to get more HW errors.

--

Now, whatever AntMiner you do have, please enlighten us with exactly where you got the firmware, how you built the cgminer or where you got the cgminer, what AntMiner you have and the actual numbers shown on the web page before and after, including how long it ran and what the settings were before and after.
Thanks

[luthermarcus]

can somebody please explain to me why when I install cgminer fork from bitmaintech

Code:

https://github.com/bitmaintech/cgminer

i have only 10 HW errors per day

and when i install

Code:

https://github.com/ckolivas/cgminer

i have 10 HW per minute ??

does HW destroy my antminers ?

Please provide a screenshot because my  miners HW% went down minimally but seem to start jumping around now but still at good levels what is the percentage of hw screen shot would give us a good overall of what is going on.

[studysession]

With the USB devices being plug-n-play does that mean for removal as well?

I started down this path for some self learning and now long as I keep finding these little USB Asic miners for cheap on eBay I keep buying them. Even though I keep adding them I also want to remove as I want for testing another RasPi box.

When I remove one does software keep working like normal? I want to add and remove freely.

Thanks -
Keith

[os2sam]

When I remove one does software keep working like normal? I want to add and remove freely.

It does with my Block Erupters.

[studysession]

It does with my Block Erupters.

Thanks

[philipma1957]

Hi ck and kano

I have been testing sidehack's

new usb sticks in this thread.

https://bitcointalk.org/index.php?topic=1086011.0


I used the 4.9.2 build from the first page of this thread.

and the sticks work great up to  freq 250

is it possible you can add support from  freq 250 to  freq 300

that would be :

 256.25
 262.50
 268.75
 275.00
 281.25
 287.50
 293.75
 300.00

 Side hack's sticks use your cgminer software and base it on your U-3 part of the build.

Basically I am really poor on the software end of the game. and cgminer is too hard for me to add these freq's

I use window's 7 to run my gear.

thanks phil

maybe in the 4.9.3 build.

[pekatete]

@Kano, any chance of  updating the S1 cgminer with the power-reboot fix you applied to the S3 cgminer?

[Mikestang]

hello again

2 mins ago my Antminer U3 start to biping.
Lol
First time hear that

Before today I used bitmaintech fork of cgminer
install with this

Code:

su
cd /opt
git clone https://github.com/bitmaintech/cgminer.git
cd cgminer
./autogen.sh
CFLAGS="-O2 -Wall -march=native" ./configure --enable-bmsc
make install

everything works perfect. I used freq 250MHz and 0.8V (I know that I overclocked it)
With that overclocked stats my cgminer shows max 10-15 HW per day, and I have 5 U3's

Today I decided to install ckoliva's fork of cgminer 4.9.2

Since I posted my last post (12h ago) cgminer show around 1300 HW errors

That's 100 times more. Why

Probably because Bitmain's fork was showing HW incorrectly.

Or the U3 finally burned something out running overclocked all the time.

[kano]

@Kano, any chance of  updating the S1 cgminer with the power-reboot fix you applied to the S3 cgminer?

There is already an updated cgminer-monitor script in my AntS1 binaries git, but I guess you also mean the change to try to force the time correct in the script that starts cgminer?

Next time I update the AntS1 version I'll probably do an archive like I did for S3 that does away with the API hack and uses a similar Status screen as the S3 one I did - just that's way down on the todo list at the moment since it's only a visual change - my AntS1 binary already (since I first did it) has the Bitmain problems removed and the cgminer version is almost current, behind by less one version.

Unless I get some Bitmain go-ahead on S5 stuff, for now (since I put out the last S3 update) priority is the pool and pool code (and it's tax time also)

[rkinnin]

I upgraded my s3's as was suggested.

I checked one of them tonight and now it says it found 6 blocks. 

How can I really verify the validity of the 6?

[kano]

I upgraded my s3's as was suggested.

I checked one of them tonight and now it says it found 6 blocks. 

How can I really verify the validity of the 6?

Clearly alt-coin blocks.

No idea - we don't really care about alt-coins ... at all

[NathanB]

win 7, version 4.9.2
rotate doesn't seem to work
tried different amt of time from 0 to 60 minutes
always stayed on which ever pool it was running on at time of change to rotate.
all pools were alive, and could switch pools manual
let run all night with rotate set to 13 minutes and when check this AM.
found it had ran the same pool all night.
checked pools web site, have graph showing hash over time
only one show hashing on graph, all other pools showed no hashing at all
pressed p for pool in cgminer display and still showed rotate at 13 minutes.
didn't switch off pool to next one.
bug?

[rkinnin]

I upgraded my s3's as was suggested.

I checked one of them tonight and now it says it found 6 blocks. 

How can I really verify the validity of the 6?

Clearly alt-coin blocks.

No idea - we don't really care about alt-coins ... at all

agreed. 

Ty