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

[Mikestang]

hello to everyone I'm new here and I'm having trouble installing the Zeusminer litecoin Miner28MH in Mandriva could you direct me to a tutorial or even commands

Try the altcoin forums, you won't get support in this thread.

[-ck]

I also posted this in the general mining software forum...  Anyone have information to share?

Cgminer ( ver 4.9.0 ) never says accepted, it only tells me the block height changes.  If I turn on verbose, I get lots of "share above target" notifications and an occasional Hashrate report ( same information that is in the header ).  I am hashing at about 50 GH/s with an Antminer U3 so I am sure it needs to be optimized, however, I  have seen it peak around 65 when I was mining in a pool.

My question is this:  Is this reporting normal?  I have tried to find a post about what solo reporting looks like online, but have not been able to find anything.  I am okay with it not providing the information, as long as it is mining.

Cgminer is happy with the set-up ( no reported errors ) but not very informative..

"Shares" are a "share of the reward" when you're pooled mining. When you're solo mining you either have found a block or you've found nothing. So you will get nothing but information about when the block changes except in the ludicrously rare situation when you find a block. Try cgminer 4.9.2 for a better hashrate.

[rylord]

Hey guys,

Anyone know how I can get a BTC Garden AM-V1 4 Blade working with BFGminer or a newer version of CGminer. The cgminer they have compiled with the support is way old. I know there is a way to have the newer versions see it just unsure how to go about doing it. Here is some info that might help....

Started cgminer 4.3.3
 [2015-09-08 01:25:44] Core clock: 310MHz
 [2015-09-08 01:25:44] SPI clock: 3000KHz
 [2015-09-08 01:25:44] Work time window: 345ms ~ 518ms
 [2015-09-08 01:25:44] SPI '/dev/spidev0.0': mode=0, bits=8, speed=3000000
 [2015-09-08 01:25:44] spidev0.0, CS delay 0us
 [2015-09-08 01:25:44] UART baud rate: 115200
 [2015-09-08 01:25:44] Chip selection delay: 80us
 [2015-09-08 01:25:45] All chips hard reset period: 5 min
 [2015-09-08 01:25:45] Number of chips 64
 [2015-09-08 01:25:45] Enabled chips:
 [2015-09-08 01:25:45] 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15
 [2015-09-08 01:25:45] 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31
 [2015-09-08 01:25:45] 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47
 [2015-09-08 01:25:45] 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63
 [2015-09-08 01:25:45] Probing for an alive pool
 [2015-09-08 01:25:45] Pool 0 difficulty changed to 512.0
 [2015-09-08 01:25:46] Network diff set to 57G
 [2015-09-08 01:25:46] Going to hard reset all chips


Newer versions of cgminer I can't get to work or find anyone who has info on it... should I just junk these??? when its working it's pretty fast but I'm getting a boat load of errors and the support for this hardware, well, unless u know hieroglyphics language ... good luck... any help would be appreciated.. =)

Thanks

[Agamenon]

Hi, I always try to restart CGMINER with the command "restart" from api and client CRASH... any experience or solution with it? I use API for PHP, JAVA and Python, and always the same crash.. thanks

[Askit2]

Hi, I always try to restart CGMINER with the command "restart" from api and client CRASH... any experience or solution with it? I use API for PHP, JAVA and Python, and always the same crash.. thanks

Depending on the operating system there is a very easy way to fix this. Start cgminer from a script in an infinite loop. Don't restart, quit. The script will start cgminer again and everything will be peachy.

[CustomDesigned]

When I try to use the api, the pogoplug running cgminer crashes.  I'm wondering if it has to do with running off a USB stick and cgminer using libusb.  I've been using since 3.8.  No console on pogoplug (without soldering a special USB cable - which I tried and failed).  cgminer does not run as root, so it really shouldn't be able to crash the system - unless it is one of those infinite thread/fork bugs.

[kano]

When I try to use the api, the pogoplug running cgminer crashes.  I'm wondering if it has to do with running off a USB stick and cgminer using libusb.  I've been using since 3.8.  No console on pogoplug (without soldering a special USB cable - which I tried and failed).  cgminer does not run as root, so it really shouldn't be able to crash the system - unless it is one of those infinite thread/fork bugs.

You'll have to find someone in one of the pogoplug threads and ask them what's wrong with how they build it.

Also note that we have a modified libusb in cgminer and don't use the system libusb since libusb has a bug on many systems that makes timeouts fail and mining thus doesn't work properly.
If there's something special about making libusb work on a pogoplug then someone who uses one will need to submit changes to cgminer.

FYI there are no such problems on RPi.

[WBF1]

Any plan to merge novak's compac driver back into master?

[-ck]

Any plan to merge novak's compac driver back into master?

Unfortunately we don't "suck code" from others, they "push code" and we accept it after making suggestions, so no.

[WBF1]

Any plan to merge novak's compac driver back into master?

Unfortunately we don't "suck code" from others, they "push code" and we accept it after making suggestions, so no.

Got it. So once it's mature he'd push back this way then possibly you merge it if it looks acceptable?

[-ck]

Any plan to merge novak's compac driver back into master?

Unfortunately we don't "suck code" from others, they "push code" and we accept it after making suggestions, so no.

Got it. So once it's mature he'd push back this way then possibly you merge it if it looks acceptable?

Yep.

[novak@gekkoscience]

Any plan to merge novak's compac driver back into master?

Unfortunately we don't "suck code" from others, they "push code" and we accept it after making suggestions, so no.

Got it. So once it's mature he'd push back this way then possibly you merge it if it looks acceptable?

Yep.

I doubt it looks acceptable yet, it's pretty much the half of icarus that I wanted plus some initialization.  I intend to clean it up more when I add multi-chip support. 

But I do plan to push it into cgminer so it's available.

--
novak

[kano]

Make sure it uses USB, not serial.
Serial is crap.

... and if you don't do most of this I will label it trash:
https://asktom.cf/index.php?topic=294499.0

(as I do consider trash things like the U3 that ignore all that)

[WBF1]

Any plan to merge novak's compac driver back into master?

Unfortunately we don't "suck code" from others, they "push code" and we accept it after making suggestions, so no.

Got it. So once it's mature he'd push back this way then possibly you merge it if it looks acceptable?

Yep.

I doubt it looks acceptable yet, it's pretty much the half of icarus that I wanted plus some initialization.  I intend to clean it up more when I add multi-chip support. 

But I do plan to push it into cgminer so it's available.

--
novak

Awesome, thanks.

[o_solo_miner]

Sorry for asking:

I am running Bitcoin Core v0.11.0 on a Debian64 PC and it runs well.
Now i added the bitcoin.conf and start with -server.

On my Win PC I am able to mine solo with cgminer 4.7.1 to my Bitcoin core XXX.
EDIT:
It look's like i am wrong, http request failed connect.


Then I tryed using cgminer 4.9.2 and I got the Message:
No Stratum, GBT or Solo support  in pool 0 http://192.168.2.112:8332 unable to use.

To test that the compile is ok I did a change from my bitcoin core to solockpool
and it works with stratum ok.


I am a bit lost about what i am doing (config on Debian site or cgminer) wrong?

[kano]

You need to send an address
https://github.com/ckolivas/cgminer/blob/master/README#L57

[-ck]

Sorry for asking:

I am running Bitcoin Core v0.11.0 on a Debian64 PC and it runs well.
Now i added the bitcoin.conf and start with -server.

On my Win PC I am able to mine solo with cgminer 4.7.1 to my Bitcoin core XXX.
EDIT:
It look's like i am wrong, http request failed connect.


Then I tryed using cgminer 4.9.2 and I got the Message:
No Stratum, GBT or Solo support  in pool 0 http://192.168.2.112:8332 unable to use.

To test that the compile is ok I did a change from my bitcoin core to solockpool
and it works with stratum ok.


I am a bit lost about what i am doing (config on Debian site or cgminer) wrong?

Did you compile with libcurl and are you specifying a btc address in your configuration? They're essential for solo mining. Furthermore the bitcoin-qt binary alone isn't enough to solo mine with any more, you need the rpc component.

[o_solo_miner]

@Kano:
yes I did, same as I used before on Windows bitcoin-qt (v 0.8.0 because of xp).

@ck:
Did you compile with libcurl and are you specifying a btc address in your configuration?

yes I did compile with libcurl and a btc adress was also supplyed.


BUT: it is my first attempt on Debian64 and the v0.11.0 bitcoin core.

=> you need the rpc component

in bitcoin.conf stored under ~/.bitcoin I enter the rpcuser / rpcpassword and rpcipallow=the raspi ip where
cgminer is running on.

or do i need to start something on the Debian64 server?
at the moment I do ./bitcoin-qt -server

[-ck]

@Kano:
yes I did, same as I used before on Windows bitcoin-qt (v 0.8.0 because of xp).

@ck:
Did you compile with libcurl and are you specifying a btc address in your configuration?

yes I did compile with libcurl and a btc adress was also supplyed.


BUT: it is my first attempt on Debian64 and the v0.11.0 bitcoin core.

=> you need the rpc component

in bitcoin.conf stored under ~/.bitcoin I enter the rpcuser / rpcpassword and rpcipallow=the raspi ip where
cgminer is running on.

or do i need to start something on the Debian64 server?
at the moment I do ./bitcoin-qt -server

Check you are explicitly using http:// as well for the address, and check the syntax of your rpcipallow as it changed not too long ago.

[o_solo_miner]

Thank you ck!

=>and check the syntax of your rpcipallow as it changed not too long ago.

that is what I found out now on github:

 -rpcallowip=<ip>
       Allow JSON-RPC connections from specified source. Valid for <ip> are a
       single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0)
       or a network/CIDR (e.g. 1.2.3.4/24). This option can be specified
       multiple times


my fault was located in bitcoin.conf:

rpcallowip=192.168.2.0/192.168.2.255 WRONG!

should be:
rpcallowip=192.168.2.0/24

  I am sorry!


Anyway I am happy that it works now!

Sometimes I wounder about where a central source for those kind of Information exist?