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

[patrike]

Hi, I have a question about the Cgminer API, and I hope this is the correct thread for these questions.

The Network Difficulty is reported by the Coin command, but if you have two pools with different coins, you don't know for which pool the Network Difficulty is reported. It looks like the Coin command reports the network difficulty for the pool/coin that had the last network difficulty change, but that isn't always the highest prioritized pool where you actually mine.

Isn't the Network Difficulty something that would be better to include in the Pool command, and specified for each pool?

Thanks for a great API and please let me know if I got all this wrong.

[-ck]

Hi, I have a question about the Cgminer API, and I hope this is the correct thread for these questions.

The Network Difficulty is reported by the Coin command, but if you have two pools with different coins, you don't know for which pool the Network Difficulty is reported. It looks like the Coin command reports the network difficulty for the pool/coin that had the last network difficulty change, but that isn't always the highest prioritized pool where you actually mine.

Isn't the Network Difficulty something that would be better to include in the Pool command, and specified for each pool?

Thanks for a great API and please let me know if I got all this wrong.

We don't care about anything but bitcoin so we have no interest in making changes for multiple coin support.

[frankenmint]

what does this mean?:

AMU 57 SendWork usb write err:(-9) LIBUSB_ERROR_PIPE

I'm getting hashrate to build up to 2/3rds the way then half of it shuts off and it stats to reload again until the cycle repeats.  Cannot get everything on and mining in harmony. 

[-ck]

what does this mean?:

AMU 57 SendWork usb write err:(-9) LIBUSB_ERROR_PIPE

I'm getting hashrate to build up to 2/3rds the way then half of it shuts off and it stats to reload again until the cycle repeats.  Cannot get everything on and mining in harmony. 

It means there has been a fatal usb communication error and cgminer drops the device to allow it to restart again. You probably don't have enough power or dodgy connections etc.

[frankenmint]

what does this mean?:

AMU 57 SendWork usb write err:(-9) LIBUSB_ERROR_PIPE

I'm getting hashrate to build up to 2/3rds the way then half of it shuts off and it stats to reload again until the cycle repeats.  Cannot get everything on and mining in harmony. 

It means there has been a fatal usb communication error and cgminer drops the device to allow it to restart again. You probably don't have enough power or dodgy connections etc.

Its not that simple though - I've have them all up and running before but for some reason I see that after a little that a string of them would turn on (an entire hub wont seem to connect, I have 9 hubs, of those 3 are daisy chained to a 4th.

[-ck]

what does this mean?:

AMU 57 SendWork usb write err:(-9) LIBUSB_ERROR_PIPE

I'm getting hashrate to build up to 2/3rds the way then half of it shuts off and it stats to reload again until the cycle repeats.  Cannot get everything on and mining in harmony. 

It means there has been a fatal usb communication error and cgminer drops the device to allow it to restart again. You probably don't have enough power or dodgy connections etc.

Its not that simple though - I've have them all up and running before but for some reason I see that after a little that a string of them would turn on (an entire hub wont seem to connect, I have 9 hubs, of those 3 are daisy chained to a 4th.

Doesn't matter how complex your setup is, the error means the same thing. Often when something fails it can take out/reset a whole hub since the communication channel is shared.

[frankenmint]

Thanks, you called it.  Problem down to one hub now I'm happy

[-ck]

I'm willing to do some cgminer testing with the latest stable kernel (mainline 3.14), albeit I'll have to make some fake devices to test the cgminer API on the latest kernel (I don't own any ASICs).

On that note, I'm making my own GNU/Linux distribution - I've compiled the kernel (3.14) and bash (4.3) in its own fs/partition and I'm creating the linux directory hierarchy by hand. Basically my policy is everything mainline - everything latest stable. (Reason for creating this is if I want to run 3.14 none of the distros want to know about me, and I want to see the driver code for my hardware and muck around with it.)

And yes, Ted Ts'o is a bit of a smarty pants on the linux kernel mailing list, which I've found out personally. (Not sure how he treated you, conman)

The choice and features of each linux kernel pretty much has precisely zero impact on cgminer so there's nothing to test.

[alekseikt]

How to/What commnads to overclock miner? Using Hashcoins Apollo? Help) i'm newbie

[everest556]

Any chance there'll be support for Technobit's HEX16A2 boards?

[-ck]

Any chance there'll be support for Technobit's HEX16A2 boards?

If they submit their code in a way consistent with other driver submissions, or provide one of us devs hardware to help massage the code to get into mainline cgminer then sure.

[oskuro]

Are those steps apply for the Raspberry pi as well. I was looking for a detailed Installation instruction like this a page before and ended up with backing up my previews version 1.8 or so. I am mining on 2GH/s with a Antminer U2 with a 14% error rate.

Yes  

The different is you don't need sudo while compile cgminer & add --enable-icarus

Code:

1. git clone https://github.com/ckolivas/cgminer.git
2. mv cgminer cgminer-4.2.3
3. cd cgminer-4.2.3
4. ./autogen.sh --enable-ants1 --enable-avalon --enable-bitfury --enable-icarus
5. make

Hi guys.

I have a raspberry pi with a rosewill hub with 2 antminers U2.

I installed minepeon last version for raspberry pi and im mining with default bfgminer. Im getting default 1.95GH/s per miner.

I would like to know if its best to use cgminer instead of default bfgminer, and what are the steps to install it, and then run it.

That quote will work for me? thanks

[everest556]

Any chance there'll be support for Technobit's HEX16A2 boards?

If they submit their code in a way consistent with other driver submissions, or provide one of us devs hardware to help massage the code to get into mainline cgminer then sure.

There is a patch for these boards: https://bitcointalk.org/index.php?topic=355031.0
Is it possible to integrate it into the main code?

[-ck]

Any chance there'll be support for Technobit's HEX16A2 boards?

If they submit their code in a way consistent with other driver submissions, or provide one of us devs hardware to help massage the code to get into mainline cgminer then sure.

There is a patch for these boards: https://bitcointalk.org/index.php?topic=355031.0
Is it possible to integrate it into the main code?

No, we do not go out of our way to scrounge up patches from elsewhere and make them work in the master cgminer code. I already described the process above.

[everest556]

I think that's a patch from the official Technobit site, not a third-party patch:
http://technobit.eu/index.php?controller=attachment&id_attachment=23

[-ck]

I think that's a patch from the official Technobit site, not a third-party patch:
http://technobit.eu/index.php?controller=attachment&id_attachment=23

Sure but they've not tried submitting it for inclusion. You seem to be missing how the process works despite me describing it a few times.

[KNK]

I am having a problem with rejected duplicate shares, which is weird, because there is no way that could happen:

Code:

wr_lock(&cgpu->qlock);
HASH_ITER(hh, cgpu->queued_work, work, tmp) {
if ( !work->stale && !(work->tv_work_start.tv_sec) ) {
cgtime(&work->tv_work_start);
wr_unlock(&cgpu->qlock);
return work;
}

1. Iteration is inside a wr_lock
2. Once accepted the work is marked as used/started again inside the lock
3. The whole function is called inside a thread private lock and no other thread is calling that function at all
4. Adding a job to the queue is also done under the same private lock

but still there are duplicates returned from different chips (if the same chip that may be just delayed chip scanning and work reuse), which points to the same work being returned in two consecutive calls or sending a work to the wrong chip.

Any pointers how to debug this?
Is the (struct work) job_id unique enough to identify that or subid (any driver as example?) should be used instead?

[-ck]

I am having a problem with rejected duplicate shares, which is weird, because there is no way that could happen:

Code:

wr_lock(&cgpu->qlock);
HASH_ITER(hh, cgpu->queued_work, work, tmp) {
if ( !work->stale && !(work->tv_work_start.tv_sec) ) {
cgtime(&work->tv_work_start);
wr_unlock(&cgpu->qlock);
return work;
}

1. Iteration is inside a wr_lock
2. Once accepted the work is marked as used/started again inside the lock
3. The whole function is called inside a thread private lock and no other thread is calling that function at all
4. Adding a job to the queue is also done under the same private lock

but still there are duplicates returned from different chips (if the same chip that may be just delayed chip scanning and work reuse), which points to the same work being returned in two consecutive calls or sending a work to the wrong chip.

Any pointers how to debug this?
Is the (struct work) job_id unique enough to identify that or subid (any driver as example?) should be used instead?

Is this in your own code because that doesn't look familiar. It doesn't look like you're actually removing the work item from the hash list before unlocking the write lock, you're only finding it so the work remains on the hash list.

[JPoet]

Hello,

Three weeks ago I used cgminer to mine Zetacoins using "cgminer.exe -o http://127.0.0.1:17335 -u xxx -p xxxx".  Everything worked ok I mined over 60 Zetacoins.

A week later I went back to Zetacoin after a break pool mining bitcoins.

Now I get an error "bit coin address is invalid 15qSxp..." seems to be the default address for a mandatory field.

So now I am getting back blockchain size and diff but am not mining.

So I set btc-address to the address in my Zetacoin wallet from the receive menu. I do not understand the instruction to set it to bitcoind.

So now I can't solo mine, can anybody help?  Thanks

[crazyates]

Three weeks ago I used cgminer to mine Zetacoins

I understand it was one page back, so I'll quote it for you:

We don't care about anything but bitcoin.