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

[KNK]

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.

Yes, this in my own code and I am not removing the work (by design), just mark it as started (tv_work_start) and send it to the chip, by keeping a pointer to it inside the chip data structure. Later on when chip is done with the job, I call work_completed() under the same private lock and request a new work.
This approach allows to avoid keeping another list, but just a pointer to the queue.
My plan is to set subid to the chip number which will work on it, so i can detect if the job is somehow sent to another chip ... it seems to be safe to have duplicate subid, as it is not used anywhere except from the driver

[Michael_KMS]

Hi, I just compiled cgminer 4.2.3 on Linux Mint with the additional technobit drivers. After starting cgminer I cant see the status window, also i cant interact with cgminer via the console. Same problem with cgminer 3.12.3. Raspberry Pi works great...

can someone help me?

thanks in advance!

[-ck]

Hi, I just compiled cgminer 4.2.3 on Linux Mint with the additional technobit drivers. After starting cgminer I cant see the status window, also i cant interact with cgminer via the console. Same problem with cgminer 3.12.3. Raspberry Pi works great...

can someone help me?

thanks in advance!

Well, you're asking for help with something you patched that isn't our code... However your problem is the classic one of not installing the  libncurses development library prior to building it.

[Michael_KMS]

Hi, I just compiled cgminer 4.2.3 on Linux Mint with the additional technobit drivers. After starting cgminer I cant see the status window, also i cant interact with cgminer via the console. Same problem with cgminer 3.12.3. Raspberry Pi works great...

can someone help me?

thanks in advance!

Well, you're asking for help with something you patched that isn't our code... However your problem is the classic one of not installing the  libncurses development library prior to building it.

And I really appreciate your help! Thanks a lot.

[kano]

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.

Yes, this in my own code and I am not removing the work (by design), just mark it as started (tv_work_start) and send it to the chip, by keeping a pointer to it inside the chip data structure. Later on when chip is done with the job, I call work_completed() under the same private lock and request a new work.
This approach allows to avoid keeping another list, but just a pointer to the queue.
My plan is to set subid to the chip number which will work on it, so i can detect if the job is somehow sent to another chip ... it seems to be safe to have duplicate subid, as it is not used anywhere except from the driver

Unless you invalidate the work when it finds one nonce (which of course you can't since it can find multiple nonces) then of course a duplicate share is possible if the driver or device can return duplicate nonces.

Quite normal for Bitfury chips since it is hard to ensure you don't lose work without getting lots of HW errors ... why my BaB driver has such a good error rate, but on occasion I get duplicate shares.
The only way, in this case, to avoid duplicate shares, would be to keep a history of valid nonces per work item and don't submit the duplicates.
Hmm yeah I can add that to the BaB driver easily enough!
Heh funny how while explaining something (as is common) you can see something you missed before

[KNK]

Unless you invalidate the work when it finds one nonce (which of course you can't since it can find multiple nonces) then of course a duplicate share is possible if the driver or device can return duplicate nonces.

In my driver i know when the chip has switched to the next job and then I call work_completed for the old one ... i don't see how the same job could be processed again

Quite normal for Bitfury chips since it is hard to ensure you don't lose work without getting lots of HW errors

Not exactly ... when the chip switches to the new job - the next nonces will never be from the old one, so it's safe to drop it and not loose nonces.

The only way, in this case, to avoid duplicate shares, would be to keep a history of valid nonces per work item and don't submit the duplicates.

Duplicates should not happen (in my driver logic) except when the chip has started working on the same job, because it was asked to ... then again i don't see how that could happen except if i missed a whole work and the job was switched twice
 ... hmm this may happen when there are few bad reads caused by hardware problems, which may well be my case, as there are some bad chips in the chain

Heh funny how while explaining something (as is common) you can see something you missed before

Seems to be the same here thanks

[thrym]

Hi all, and hi ckolivas - thank you for your excellent work.

I have been using cgminer for a while on my raspberry pi with 8 Antminers U1 and U2 mixed.

There is no big Problem, especially at startup everything works fine - but after a while (5min-1Hour) I get this:

Code:

[2014-04-10 10:16:01] ANU 8: No valid hashes for over 53 secs, attempting to reset
[2014-04-10 10:16:01] ANU 8 attempted reset got err:(0) LIBUSB_SUCCESS
[2014-04-10 10:17:23] ANU 8: No valid hashes for over 53 secs, attempting to reset
[2014-04-10 10:17:24] ANU 8 attempted reset got err:(0) LIBUSB_SUCCESS
[2014-04-10 10:18:24] ANU 8: Device failed to respond to restart
[2014-04-10 10:18:24] ANU 8 failure, disabling!

The device is then listed as OFF.

Interrestingly enough, when I press U + U + 8 (in this case it was it redetects the miner without problem and hashes away happily for the next 1-10 hours.

I suspected the power supply on my USB-Hubs, but no matter wich one or how many (I have 3 hubs with 3.5Amp supply per hub) I use, I keep running into that error. Currently I use version 4.1.0

Anyone got an Idea what to check next?

Also @ckolivas, is it possible to automize the USB-Unplug for disbled devices somehow?

Thanks in advance for any replies.

[-ck]

Currently I use version 4.1.0

Anyone got an Idea what to check next?

This.

[JPoet]

Hello, I apologize of I did this wrong, I am new and have tried to mine bitcoins solo, to see it work.

Three weeks ago I used cgminer to mine bitcoins using "cgminer.exe -o http://127.0.0.1:xxxx  -u xxx -p xxxx".  Everything worked ok I got the messages as per the cgminer output. 

A week later I went back to bitcoin 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.  I no longer see the messages" accepted ccccc from anu0". For example.

So I set btc-address to the address in my bitcoin 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

Basically what btc-address do I use as the default no longer seems to work.

[-ck]

Hello, I apologize of I did this wrong, I am new and have tried to mine bitcoins solo, to see it work.

Three weeks ago I used cgminer to mine bitcoins using "cgminer.exe -o http://127.0.0.1:xxxx  -u xxx -p xxxx".  Everything worked ok I got the messages as per the cgminer output. 

A week later I went back to bitcoin 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.  I no longer see the messages" accepted ccccc from anu0". For example.

So I set btc-address to the address in my bitcoin 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

Basically what btc-address do I use as the default no longer seems to work.

Just pick any valid btc address that you own. It does not even matter if the wallet that contains that address isn't on the bitcoind you are mining to.

[thrym]

Currently I use version 4.1.0

Anyone got an Idea what to check next?

This.

stupid me.

Upgraded the little bugger to 4.2.3, will report results.

[thrym]

stupid me.

Upgraded the little bugger to 4.2.3, will report results.

AAAnd we have a Winner!

Thank you very much!

Code:

[2014-04-10 16:19:16] ANU 4: Device failed to respond to restart
[2014-04-10 16:19:16] ANU 4 failure, disabling!
[2014-04-10 16:19:21] Hotplug: Icarus added ANU 9

[GigaWave]

Kano, would like to know if you have any input on this issue of pool hash rate  being only %1 of cgminer hash rate. Providing links below to 'posts' as the text is on the larger side.

https://bitcointalk.org/index.php?topic=514758.msg6159291#msg6159291
https://bitcointalk.org/index.php?topic=441465.msg6159311#msg6159311

[-ck]

Kano, would like to know if you have any input on this issue of pool hash rate  being only %1 of cgminer hash rate. Providing links below to 'posts' as the text is on the larger side.

https://bitcointalk.org/index.php?topic=514758.msg6159291#msg6159291
https://bitcointalk.org/index.php?topic=441465.msg6159311#msg6159311

This is their custom fork of cgminer + driver. They do not have proper diff checking in their code. That's the sort of thing you get with a poorly done custom driver by a manufacturer. Tell them to fix their driver. In the interim try to use a pool that allows you to use a fixed diff that matches whatever the device is set to.

[GigaWave]

Kano, would like to know if you have any input on this issue of pool hash rate  being only %1 of cgminer hash rate. Providing links below to 'posts' as the text is on the larger side.

https://bitcointalk.org/index.php?topic=514758.msg6159291#msg6159291
https://bitcointalk.org/index.php?topic=441465.msg6159311#msg6159311

This is their custom fork of cgminer + driver. They do not have proper diff checking in their code. That's the sort of thing you get with a poorly done custom driver by a manufacturer. Tell them to fix their driver. In the interim try to use a pool that allows you to use a fixed diff that matches whatever the device is set to.

Someone with reading comprehension...amazing. Excuse me, Just sick of no one reading what I write and then telling me I'm wrong.

The diff. was set to '1000', I lowered it to '256' and it seems to be working petty good. I may lower it to '128', to see if it gives a more stable result. I have next to no idea how stratum works, so feel free to give any further advice how ever small it may be. If they will fix it, I bet it won't be for a while. I will pass this along though.

Thanks!

[rgr_rgr]

Is it possible to extend cgminer to switch of the led of a nanofury not using? It would be easier to find the faulty one.

[kano]

Is it possible to extend cgminer to switch of the led of a nanofury not using? It would be easier to find the faulty one.

Doesn't really make sense since if it can talk to it, it will mine on it.
If it can't mine on it, then that would be coz it can't talk to it thus it can't tell it to turn the led off.

[rgr_rgr]

Doesn't really make sense since if it can talk to it, it will mine on it.
If it can't mine on it, then that would be coz it can't talk to it thus it can't tell it to turn the led off.

It is possible to enable/disable a device using the USB menu. I have sometimes slow nanofurys because of several reasons. To find them I disable and wait. Then I try to find the cold one. If the LED would be switched off, it would be much easier.

[JPoet]

Hi,

Using cgminer.exe -o http://127.0.0.1:8332 -u xxx -p xxx --btc-address 1Q51EGQbiKNwznDtXByUHAbCL9XtiP9ndU which

is from my receive address in my bitcoin wallet on my PC, solo mining.

I get this output, three weeks ago I did not use the --btc-address and got the expected output, then it throw an error on the default btc-address.

Code:

cgminer version 4.2.0 - Started: [2014-04-12 14:29:33]
--------------------------------------------------------------------------------
 (5s):3.798G (avg):3.130Gh/s | A:0  R:0  HW:15  WU:44.0/m
 ST: 6  SS: 0  NB: 7  LW: 5888  GF: 0  RF: 0
 Connected to 127.0.0.1 diff 6.12G without LP as user joe
 Block: 7022bade...  Diff:6.12G  Started: [15:22:41]  Best share: 1.02K
--------------------------------------------------------------------------------
 [U]SB device management [P]ool management [S]ettings [D]isplay options [Q]uit
 1: ANU 0:                         | 1.597G/1.594Gh/s | A:0 R:0 HW:6 WU:22.2/m
 2: AMU 1:                         | 335.6M/335.0Mh/s | A:0 R:0 HW:3 WU: 5.1/m
 3: ANU 1:                         | 1.592G/1.594Gh/s | A:0 R:0 HW:5 WU:22.5/m
--------------------------------------------------------------------------------
 [2014-04-12 14:55:26] Block height change to 295460 detected on pool 0
 [2014-04-12 15:01:38] Block height change to 295461 detected on pool 0
 [2014-04-12 15:02:35] Block height change to 295462 detected on pool 0
 [2014-04-12 15:21:09] Block height change to 295463 detected on pool 0
 [2014-04-12 15:22:41] Block height change to 295464 detected on pool 0

Thanks for any help you can give.

[Krak]

Hi,

Using cgminer.exe -o http://127.0.0.1:8332 -u xxx -p xxx --btc-address 1Q51EGQbiKNwznDtXByUHAbCL9XtiP9ndU which

is from my receive address in my bitcoin wallet on my PC, solo mining.

I get this output, three weeks ago I did not use the --btc-address and got the expected output, then it throw an error on the default btc-address.

Code:

cgminer version 4.2.0 - Started: [2014-04-12 14:29:33]
--------------------------------------------------------------------------------
 (5s):3.798G (avg):3.130Gh/s | A:0  R:0  HW:15  WU:44.0/m
 ST: 6  SS: 0  NB: 7  LW: 5888  GF: 0  RF: 0
 Connected to 127.0.0.1 diff 6.12G without LP as user joe
 Block: 7022bade...  Diff:6.12G  Started: [15:22:41]  Best share: 1.02K
--------------------------------------------------------------------------------
 [U]SB device management [P]ool management [S]ettings [D]isplay options [Q]uit
 1: ANU 0:                         | 1.597G/1.594Gh/s | A:0 R:0 HW:6 WU:22.2/m
 2: AMU 1:                         | 335.6M/335.0Mh/s | A:0 R:0 HW:3 WU: 5.1/m
 3: ANU 1:                         | 1.592G/1.594Gh/s | A:0 R:0 HW:5 WU:22.5/m
--------------------------------------------------------------------------------
 [2014-04-12 14:55:26] Block height change to 295460 detected on pool 0
 [2014-04-12 15:01:38] Block height change to 295461 detected on pool 0
 [2014-04-12 15:02:35] Block height change to 295462 detected on pool 0
 [2014-04-12 15:21:09] Block height change to 295463 detected on pool 0
 [2014-04-12 15:22:41] Block height change to 295464 detected on pool 0

Thanks for any help you can give.

Where's the error?