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

[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.

[1532231568]

1532231568

[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

[Mikestang]

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

Oh yea, I forgot about the (crap) usb cable they ship with.

2 things I always remind people of with the U3, replace psu and usb cable.

I also tell people who haven't bought one yet to not bother, they are generally crap.

[Mikestang]

Please don't read this as "are we there yet?", but I was wondering if there is an ETA for the S2 and S3 cgminer updates?  Even if it's months out, I was just curious. Thanks in advance.

[Cheffe]

I downloaded cgminer-4.9.1.windows.zip from http://kolivas.org/apps/cgminer/ but can someone tell me how to use it proper?

I have put my pool in the conf like


      "url" : "url1:8332",
      "user" : "user1",
      "pass" : "pass1"

but i dont see my GPU when i open with

cgminer -n


Kind Regards

[os2sam]

I downloaded cgminer-4.9.1.windows.zip from http://kolivas.org/apps/cgminer/ but can someone tell me how to use it proper?

I have put my pool in the conf like


      "url" : "url1:8332",
      "user" : "user1",
      "pass" : "pass1"

but i dont see my GPU when i open with

cgminer -n


Kind Regards

CG Miner doesn't support GPU's.  You really don't want to mine bitcoins with GPU's anymore, anyway.