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

[helipotte]

Installed the new binary on one of my underclocked ants and now the discard rate is much higher.  Averages around 6% now.  With the previous binary (4.3.2)

it was around  .2%.  Is this normal?  

Exact setting I am using:  [196.88  69 5f06] with latest firmware.

Thanks!

Discards do not matter.

Did you mean Rejects?
If so post the full set of relevant numbers:
Elasped, DiffA, DiffR

Rejects are actually very low.  Just curious about the discards.

[kano]

Installed the new binary on one of my underclocked ants and now the discard rate is much higher.  Averages around 6% now.  With the previous binary (4.3.2)

it was around  .2%.  Is this normal?  

Exact setting I am using:  [196.88  69 5f06] with latest firmware.

Thanks!

Discards do not matter.

Did you mean Rejects?
If so post the full set of relevant numbers:
Elasped, DiffA, DiffR

Rejects are actually very low.  Just curious about the discards.

Discards are unused work - so they mean nothing in terms of shares or hash rate.

[kano]

For details and installing: https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

I really appreciate the easy to follow instructions.  They are perfect for someone like me who barely knows what each line is doing, thank you.

Installed the new binary on one of my underclocked ants and now the discard rate is much higher.  Averages around 6% now.  With the previous binary (4.3.2)

it was around  .2%.  Is this normal?  

Exact setting I am using:  [196.88  69 5f06] with latest firmware.

Thanks!

On my now updated to 4.9.1a overclocked (393 freq) S1 I see 0 rejects (used to be around 0.3%), error rate is about the same ~1%.  Hash rate is up a little, too, but we'll see how that levels out.  I had to do the fix for LST time, but no big deal.  I updated the monitor script, too.

Question, I verified the cgminer version via API, but is there a way to see the version from the web GUI, too?  Just curious.

No, the web interface shows the package version, which of course doesn't change when you replace the cgminer binary.

Looking very much forward to updated cgminer for my S3+, keep up the solid work, ck & Kano!

S2 is in the works now, the S3 is after that and will be more effort than the S1 and S2 combined

[Mikestang]

No, the web interface shows the package version, which of course doesn't change when you replace the cgminer binary.

Looking very much forward to updated cgminer for my S3+, keep up the solid work, ck & Kano!

S2 is in the works now, the S3 is after that and will be more effort than the S1 and S2 combined

That's what I figured, but wanted to double check.  Thanks for including the API version check instructions, makes me feel better to verify that I did it correctly.

Good luck with S2 and S3, sorry to hear S3 is going to be so much work, hopefully it's worth it!

[kano]

I had an issue raised on git regarding the S1 API.
Seems it may have been a user typing error?
Anyone else seen any problem like this that they can reproduce?
https://github.com/kanoi/cgminer-binaries/issues/9
The API IPv6 changes by someone else were initially problematic but later fixed.
So, I wasn't 100% certain if there were still any more IPv4 problems from the changes for the IPv6 code.

[Mikestang]

I had an issue raised on git regarding the S1 API.
Seems it may have been a user typing error?
Anyone else seen any problem like this that they can reproduce?
https://github.com/kanoi/cgminer-binaries/issues/9
The API IPv6 changes by someone else were initially problematic but later fixed.
So, I wasn't 100% certain if there were still any more IPv4 problems from the changes for the IPv6 code.

I have no IPv4 problems with my S1 API running 4.9.1a.

Here's cryptoGlance reporting my S1 via API:

[WBF1]

I cloned and built cgminer from https://github.com/ckolivas/cgminer yesterday and it wouldn't work with my ASICMiner Tubes connected via USB.

I decided to try the version here: https://github.com/blockerupter/cgminer and it worked, but it's six months old.

Is this a known issue? Or should I start digging to see what broke it?

[Jay_Pal]

I cloned and built cgminer from https://github.com/ckolivas/cgminer yesterday and it wouldn't work with my ASICMiner Tubes connected via USB.

I decided to try the version here: https://github.com/blockerupter/cgminer and it worked, but it's six months old.

Is this a known issue? Or should I start digging to see what broke it?

If the version you last compiled is working, what features would you need from the new version?
Why not stick to that one?

[WBF1]

I cloned and built cgminer from https://github.com/ckolivas/cgminer yesterday and it wouldn't work with my ASICMiner Tubes connected via USB.

I decided to try the version here: https://github.com/blockerupter/cgminer and it worked, but it's six months old.

Is this a known issue? Or should I start digging to see what broke it?

If the version you last compiled is working, what features would you need from the new version?
Why not stick to that one?

Regressions are usually worth looking into.

[-ck]

I cloned and built cgminer from https://github.com/ckolivas/cgminer yesterday and it wouldn't work with my ASICMiner Tubes connected via USB.

I decided to try the version here: https://github.com/blockerupter/cgminer and it worked, but it's six months old.

Is this a known issue? Or should I start digging to see what broke it?

If the version you last compiled is working, what features would you need from the new version?
Why not stick to that one?

Regressions are usually worth looking into.

You're comparing it to a different codebase. As far as I'm aware, the blockerupter code that was contributed by them to mainline cgminer NEVER worked. None of the main devs ever got any hardware from them to get it working and they never contributed fixes to make sure it was working. I don't go chasing code from other people's branches to get mainline cgminer working with hardware from manufacturers that never really engaged the software community they depend on but I'm very happy to receive fixes from outside sources if they're willing to maintain it. The avalon nano and the blockerupter drivers both fall into the "submitted but broken code" category I'm afraid.

[WBF1]

I cloned and built cgminer from https://github.com/ckolivas/cgminer yesterday and it wouldn't work with my ASICMiner Tubes connected via USB.

I decided to try the version here: https://github.com/blockerupter/cgminer and it worked, but it's six months old.

Is this a known issue? Or should I start digging to see what broke it?

If the version you last compiled is working, what features would you need from the new version?
Why not stick to that one?

Regressions are usually worth looking into.

You're comparing it to a different codebase. As far as I'm aware, the blockerupter code that was contributed by them to mainline cgminer NEVER worked. None of the main devs ever got any hardware from them to get it working and they never contributed fixes to make sure it was working. I don't go chasing code from other people's branches to get mainline cgminer working with hardware from manufacturers that never really engaged the software community they depend on but I'm very happy to receive fixes from outside sources if they're willing to maintain it. The avalon nano and the blockerupter drivers both fall into the "submitted but broken code" category I'm afraid.

Thanks for the reply. I was under the impression that it worked at some point. I'll just use the working version from the blockerupter repo.

[Alien77]

Hi all.
Using Raspberry, OS Raspbian, Cgminer 4.8.0 (from https://github.com/bitmaintech/cgminer) and Antminer U3.
At working, Cgminer show 10-15Gh, but in Bitmain specifications U3 hash rate 63Gh±5%.
Maybe worked 1 of 4 chip in AU3? Any way solve this problem?
Thanks.

[-ck]

Hi all.
Using Raspberry, OS Raspbian, Cgminer 4.8.0 (from https://github.com/bitmaintech/cgminer) and Antminer U3.
At working, Cgminer show 10-15Gh, but in Bitmain specifications U3 hash rate 63Gh±5%.
Maybe worked 1 of 4 chip in AU3? Any way solve this problem?
Thanks.

You're using the cgminer from bitmain instead of the official cgminer which this forum thread is about. Try cgminer 4.9.0 (best for U3) from the official sources (links in top post).

[Alien77]

Hi all.
Using Raspberry, OS Raspbian, Cgminer 4.8.0 (from https://github.com/bitmaintech/cgminer) and Antminer U3.
At working, Cgminer show 10-15Gh, but in Bitmain specifications U3 hash rate 63Gh±5%.
Maybe worked 1 of 4 chip in AU3? Any way solve this problem?
Thanks.

You're using the cgminer from bitmain instead of the official cgminer which this forum thread is about. Try cgminer 4.9.0 (best for U3) from the official sources (links in top post).

Install cgminer-4.9.0 no effect. Still low hash rate(

[NathanB]

--au3-freq 250 --au3-volt 800

try options

[Alien77]

--au3-freq 250 --au3-volt 800

try options

Tried, nothing has changed. I may be incorrectly configured cgminer?   ./configure --enable-icarus

[NathanB]

--au3-freq 250 --au3-volt 800

try options

Tried, nothing has changed. I may be incorrectly configured cgminer?   ./configure --enable-icarus

i do, always worked for me

sudo apt-get update

sudo apt-get install libusb-1.0-0-dev libusb-1.0-0 libcurl4-openssl-dev libncurses5-dev libudev-dev

wget http://ck.kolivas.org/apps/cgminer/4.9/cgminer-4.9.0.tar.bz2

tar xvf cgminer-4.9.0.tar.bz2

cd cgminer-4.9.0

./configure --enable-icarus

make

cd cgminer-4.9.0

./cgminer -o pool:port -u userid -p password --au3-freq 250 --au3-volt 800

[Alien77]

--au3-freq 250 --au3-volt 800

try options

Tried, nothing has changed. I may be incorrectly configured cgminer?   ./configure --enable-icarus

i do, always worked for me

sudo apt-get update

sudo apt-get install libusb-1.0-0-dev libusb-1.0-0 libcurl4-openssl-dev libncurses5-dev libudev-dev

wget http://ck.kolivas.org/apps/cgminer/4.9/cgminer-4.9.0.tar.bz2

tar xvf cgminer-4.9.0.tar.bz2

cd cgminer-4.9.0

./configure --enable-icarus

make

cd cgminer-4.9.0

./cgminer -o pool:port -u userid -p password --au3-freq 250 --au3-volt 800

I erased the cgminer.conf and now u3 is work correctly. Thank you very much.

[Mikestang]

--au3-freq 250 --au3-volt 800

try options

Tried, nothing has changed. I may be incorrectly configured cgminer?   ./configure --enable-icarus

i do, always worked for me

sudo apt-get update

sudo apt-get install libusb-1.0-0-dev libusb-1.0-0 libcurl4-openssl-dev libncurses5-dev libudev-dev

wget http://ck.kolivas.org/apps/cgminer/4.9/cgminer-4.9.0.tar.bz2

tar xvf cgminer-4.9.0.tar.bz2

cd cgminer-4.9.0

./configure --enable-icarus

make

cd cgminer-4.9.0

./cgminer -o pool:port -u userid -p password --au3-freq 250 --au3-volt 800

I erased the cgminer.conf and now u3 is work correctly. Thank you very much.

You will melt the factory psu with those settings, be sure to use an adequate psu.

[NathanB]

--au3-freq 250 --au3-volt 800

try options

Tried, nothing has changed. I may be incorrectly configured cgminer?   ./configure --enable-icarus

i do, always worked for me

sudo apt-get update

sudo apt-get install libusb-1.0-0-dev libusb-1.0-0 libcurl4-openssl-dev libncurses5-dev libudev-dev

wget http://ck.kolivas.org/apps/cgminer/4.9/cgminer-4.9.0.tar.bz2

tar xvf cgminer-4.9.0.tar.bz2

cd cgminer-4.9.0

./configure --enable-icarus

make

cd cgminer-4.9.0

./cgminer -o pool:port -u userid -p password --au3-freq 250 --au3-volt 800

I erased the cgminer.conf and now u3 is work correctly. Thank you very much.

You will melt the factory psu with those settings, be sure to use an adequate psu.

2 things always do, replace psu and usb cable.
I forget sometimes not everyone does that. sorry