Bitcoin Forum
December 06, 2016, 10:12:13 AM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 [257] 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 ... 830 »
  Print  
Author Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.9.2  (Read 4819227 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
The00Dustin
Hero Member
*****
Offline Offline

Activity: 806


View Profile
April 27, 2012, 08:04:28 PM
 #5121

Issue two is related to submission of stale shares.  Note that I did not have --submit-stale on the command line in this case, but I have previously seen cgminer submit detected stales to the pool because it was instructed to (pool is eligius).  This morning, I just happened to look at my miner while this was still on the screen:
Quote
[2012-03-23 08:22:53] LONGPOLL requested work restart, waiting on fresh work
[2012-03-23 08:22:57] Accepted 00000000.949b59d0.7ecd59ab GPU 0 thread 1 pool 0
[2012-03-23 08:23:03] Accepted 00000000.58e019ff.7a3bc657 GPU 0 thread 1 pool 0
[2012-03-23 08:23:05] Pool 0 communication failure, caching submissions
[2012-03-23 08:23:05] Stale share detected, discarding
[2012-03-23 08:23:07] Pool 0 communication resumed, submitting work
[2012-03-23 08:23:07] Accepted 00000000.ade4193a.07083649 GPU 0 thread 0 pool 0
I had recently restarted cgminer, so I can't be 100% certain cgminer was again instructed to submit stales, but assuming it was, I believe the discarded share above would indicate a bug in stale share handling in this scenario.  I also believe it would have been accepted based on the length of time between the last longpoll and this event and the fact that other shares were accepted before and after this one with no other new block event shown.
If you don't tell cgminer to submit stales, then it will discard what it considers stale.
The thing to know about stales is that a work request is stale based on when it was received, not when you see it's share(s) shown in cgminer.
Cgminer threw away that share coz it wasn't told to submit stales and the getwork time implied the share was stale.
You can't assume the getwork order matches the share display order.

Edit: oops yes the pool can also tell cgminer to submit stales - forgot to mention that - as mentioned above.
Today seems like a good day to beat a dead horse...
Quote
[2012-04-27 15:48:45] LONGPOLL detected new block on network, waiting on fresh work
[2012-04-27 15:48:45] Stale share detected, submitting as pool requested
[2012-04-27 15:48:51] Accepted 00000000.1cf4d45e.99314e90 GPU 0 thread 0 pool 0
[2012-04-27 15:48:56] Accepted 00000000.ce0e4d50.781165a9 GPU 0 thread 1 pool 0
[2012-04-27 15:49:10] Accepted 00000000.3ae325b1.654a64ff GPU 0 thread 1 pool 0
[2012-04-27 15:49:16] Pool 0 communication failure, caching submissions
[2012-04-27 15:49:16] Stale share detected, discarding
[2012-04-27 15:49:21] Pool 0 communication resumed, submitting work
[2012-04-27 15:49:21] Accepted 00000000.bfeef9eb.14ed8c5e GPU 0 thread 1 pool 0
[2012-04-27 15:49:23] Accepted 00000000.95be4b9a.137f31c6 GPU 0 thread 1 pool 0
So, given that there was a longpoll, and then a stale share submitted (that was apparently accepted), and there was not another longpoll, should it be safe to assume submitold was enabled during this [~11 second] communication failure?  If it is safe to assume that, does this output indicate that maybe I really did see what I thought I saw before regardless of my faulty assumptions at that time?  If so, note that this is on 2.3.2 (in case the relevant code may not be the same after the recent network changes), but I figured I should report it anyway since I'm not specifically looking for this and it's dumb luck when I catch a communication failure or stale share being discarded.
1481019133
Hero Member
*
Offline Offline

Posts: 1481019133

View Profile Personal Message (Offline)

Ignore
1481019133
Reply with quote  #2

1481019133
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481019133
Hero Member
*
Offline Offline

Posts: 1481019133

View Profile Personal Message (Offline)

Ignore
1481019133
Reply with quote  #2

1481019133
Report to moderator
-ck
Moderator
Legendary
*
Offline Offline

Activity: 1988


Ruu \o/


View Profile WWW
April 27, 2012, 09:43:46 PM
 #5122

Pools usually selectively request submitold on work items, usually for merged mining reasons - that is because a share for an old nmc block is still a relevant share for the existing BTC block. Most pools do not universally enable it except in the case of p2pool.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
Luke-Jr
Legendary
*
Offline Offline

Activity: 2086



View Profile
April 27, 2012, 10:01:37 PM
 #5123

Pools usually selectively request submitold on work items, usually for merged mining reasons - that is because a share for an old nmc block is still a relevant share for the existing BTC block. Most pools do not universally enable it except in the case of p2pool.
Eloipool always enables submitold. There's no real reason not to enable it, unless the pool wants to misreport a lower stale rate.

-ck
Moderator
Legendary
*
Offline Offline

Activity: 1988


Ruu \o/


View Profile WWW
April 27, 2012, 11:06:22 PM
 #5124

Ah there was also one bug where submitold was not being checked on re-submission. This has been fixed in my git tree.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
DeathAndTaxes
Donator
Legendary
*
Offline Offline

Activity: 1218


Gerald Davis


View Profile
April 28, 2012, 01:12:19 AM
 #5125

Likely a simple fix but trying to run cgminer 2.3.4 under Debian 6.01 x64 I get

./cgminer -n
cgminer: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory

Any ideas?


Nevermind I finally stopped being a Linux wimp and using the prebuilt binary and compiled it myself.  It only took .... (don't laugh I am a SQL Server developer by trade) ... little over an hour.

Still I learned something and it working fine now.
bitcoindaddy
Hero Member
*****
Offline Offline

Activity: 481


View Profile
April 28, 2012, 01:41:05 AM
 #5126

I tried moving my hard drive from a motherboard that only had one GPU to a motherboard that had three GPU's plugged in.

I did the sudo aticonfig -f --adapter=all --initial and rebooted, I also deleted the .bin file in cgminer's directory.

CGminer gave an error about the number of devices not matching. It saw three devices, but OpenCL was only seeing one?

Where else does OpenCL know about the number of video cards besides xorg.conf and what else should I have done besides running aticonfig?

The system was build with these instructions: https://github.com/kanoi/linux-usb-cgminer/blob/master/linux-usb-cgminer
-ck
Moderator
Legendary
*
Offline Offline

Activity: 1988


Ruu \o/


View Profile WWW
April 28, 2012, 02:16:53 AM
 #5127

Likely a simple fix but trying to run cgminer 2.3.4 under Debian 6.01 x64 I get

./cgminer -n
cgminer: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory

Any ideas?


Nevermind I finally stopped being a Linux wimp and using the prebuilt binary and compiled it myself.  It only took .... (don't laugh I am a SQL Server developer by trade) ... little over an hour.

Still I learned something and it working fine now.
Just for further reference:
Code:
sudo apt-get install libusb

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
-ck
Moderator
Legendary
*
Offline Offline

Activity: 1988


Ruu \o/


View Profile WWW
April 28, 2012, 02:18:00 AM
 #5128

I tried moving my hard drive from a motherboard that only had one GPU to a motherboard that had three GPU's plugged in.

I did the sudo aticonfig -f --adapter=all --initial and rebooted, I also deleted the .bin file in cgminer's directory.

CGminer gave an error about the number of devices not matching. It saw three devices, but OpenCL was only seeing one?

Where else does OpenCL know about the number of video cards besides xorg.conf and what else should I have done besides running aticonfig?

The system was build with these instructions: https://github.com/kanoi/linux-usb-cgminer/blob/master/linux-usb-cgminer
opencl has nothing to do with xorg I'm afraid, but what you need before starting cgminer is:
Code:
export DISPLAY=:0

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
bitlane
Internet detective
Sr. Member
****
Offline Offline

Activity: 462


I heart thebaron


View Profile
April 28, 2012, 02:28:27 AM
 #5129

Updated git tree:
The most significant change is a massive change to the way network connections are made, so there should be MUCH less connections opened which should more or less abolish the overloaded networks people use. Also longpoll is now tied to each pool set up, but only the longpoll attached to the primary pool causes a work restart. Also updated ztex support.


Changelog(reverse order):
Start longpoll only after we have tried to extract the longpoll URL.
Check for submitold flag on resubmit of shares, and give different message for stale shares on retry.
Check for submitold before submitstale.
Don't force fresh curl connections on anything but longpoll threads.
Create one longpoll thread per pool, using backup pools for those pools that don't have longpoll.
Use the work created from the longpoll return only if we don't have failover-enabled, and only flag the work as a longpoll if it is the current pool.
This will work around the problem of trying to restart the single longpoll thread on pool changes that was leading to race conditions.
It will also have less work restarts from the multiple longpolls received from different pools.
Remove the ability to disable longpoll. It is not a useful feature and will conflict with planned changes to longpoll code.
Remove the invalid entries from the example configuration file.
Add support for latest ATI SDK on windows.
Export missing function from libztex.
miner.php change socktimeoutsec = 10 (it only waits once)
Bugfix: Make initial_args a const char** to satisfy exec argument type warning (on Windows only)
miner.php add a timeout so you don't sit and wait ... forever
Create discrete persistent submit and get work threads per pool, thus allowing all submitworks belonging to the same pool to reuse the same curl handle, and all getworks to reuse their own handle.
Use separate handles for submission to not make getwork potentially delay share submission which is time critical.
This will allow much more reusing of persistent connections instead of opening new ones which can flood routers.
This mandated a rework of the extra longpoll support (for when pools are switched) and this is managed by restarting longpoll cleanly and waiting for a thread join.
miner.php only show the current date header once
miner.php also add current time like single rig page
miner.php display rig 'when' table at top of the multi-rig summary page
README - add some Ztex details
api.c include zTex in the FPGA support list
api.c ensure 'devs' shows PGA's when only PGA code is compiled
cgminer.c sharelog code consistency and compile warning fix
README correct API version number
README spelling error
api.c combine all pairs of sprintfs()
api.c uncomment and use BLANK (and COMMA)
Code style cleanup
Annotating frequency changes with the changed from value
README clarification of 'notify' command
README update for API RPC 'devdetails'
api.c 'devdetails' list static details of devices
Using less heap space as my TP-Link seems to not handle this much


So, is this all currently reflected in 2.3.4 ? or upcoming in 2.3.5 ?

-ck
Moderator
Legendary
*
Offline Offline

Activity: 1988


Ruu \o/


View Profile WWW
April 28, 2012, 02:29:49 AM
 #5130

So, is this all currently reflected in 2.3.4 ? or upcoming in 2.3.5 ?
2.3.5, which I'm in the process of completing shortly.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
bitcoindaddy
Hero Member
*****
Offline Offline

Activity: 481


View Profile
April 28, 2012, 02:41:20 AM
 #5131

I tried moving my hard drive from a motherboard that only had one GPU to a motherboard that had three GPU's plugged in.

I did the sudo aticonfig -f --adapter=all --initial and rebooted, I also deleted the .bin file in cgminer's directory.

CGminer gave an error about the number of devices not matching. It saw three devices, but OpenCL was only seeing one?

Where else does OpenCL know about the number of video cards besides xorg.conf and what else should I have done besides running aticonfig?

The system was build with these instructions: https://github.com/kanoi/linux-usb-cgminer/blob/master/linux-usb-cgminer
opencl has nothing to do with xorg I'm afraid, but what you need before starting cgminer is:
Code:
export DISPLAY=:0


I'm not running as root. DISPLAY is already set. And I'm not using SSH, I'm on the local console.
The00Dustin
Hero Member
*****
Offline Offline

Activity: 806


View Profile
April 28, 2012, 03:07:37 AM
 #5132

Pools usually selectively request submitold on work items, usually for merged mining reasons - that is because a share for an old nmc block is still a relevant share for the existing BTC block. Most pools do not universally enable it except in the case of p2pool.
Eloipool always enables submitold. There's no real reason not to enable it, unless the pool wants to misreport a lower stale rate.
I'm not sure what Eloipool is, but assuming it is the backend for Eligius, yes, that output was while mining on Eligius.  Incidentally, if you go back to the original quote, I was then, too, but I don't think you were active in this thread yet.  However, it sounds plausible that I could have been witnessing this:
Ah there was also one bug where submitold was not being checked on re-submission. This has been fixed in my git tree.
In which case I will need to update to 2.3.5 (which might also help with my disconnects if it has fewer sessions as previously indicated.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 1988


Ruu \o/


View Profile WWW
April 28, 2012, 04:28:23 AM
 #5133

NEW RELEASE - VERSION 2.3.5, 28 APRIL 2012

Human readable changelog:
Much nicer on networks, should have significantly less connections and not induce network congestion. This will help both miner and pool hardware.
Much smoother across longpolls, uses one longpoll per pool now at all times
Simpler screen output, yet more info
More ztex hardware support
New diakgcn kernel
Numerous bugfixes surrounding stale handling and display
Updated miner.php
--no-longpoll does not exist any more
Numerous min(e)r improvements Wink

Full changelog:
- Restarting cgminer leads to a socket that can't be bound for 60 seconds, so
increase the interval that API binding waits to 30 seconds to minimise the
number of times it will retry, spamming the logs.
- Give a longpoll message for any longpoll that detects a block change, primary
or backup, and also display which pool it was.
- Decrease utility display to one decimal place.
- Small cosmetic output alignment.
- Add pool number to stale share message.
- Add space to log output now that there is more screen real estate available.
- Indentation clean up.
- Merge branch 'master' of github.com:ckolivas/cgminer
- Remove thread id display from rejected shares as well.
- Merge pull request #185 from Diapolo/diakgcn
- add goffset support for diakgcn with -v 1 and update kernel version
- Set have_longpoll to true when there is at least one pool with longpoll.
- Don't display the thread ID since it adds no useful information over the
device number.
- Don't display the first 8 bytes of a share since they will always be zero at
>= 1 difficulty.
- work->longpoll is reset across test_work_current so we need to recheck what
pool it belongs to.
- Use longpolls from backup pools with failover-only enabled just to check for
block changes, but don't use them as work.
- Start longpoll only after we have tried to extract the longpoll URL.
- Check for submitold flag on resubmit of shares, and give different message for
stale shares on retry.
- Check for submitold before submitstale.
- Don't force fresh curl connections on anything but longpoll threads.
- Create one longpoll thread per pool, using backup pools for those pools that
don't have longpoll.
- Use the work created from the longpoll return only if we don't have
failover-enabled, and only flag the work as a longpoll if it is the current
pool.
- This will work around the problem of trying to restart the single longpoll
thread on pool changes that was leading to race conditions.
- It will also have less work restarts from the multiple longpolls received from
different pools.
- Remove the ability to disable longpoll. It is not a useful feature and will
conflict with planned changes to longpoll code.
- Remove the invalid entries from the example configuration file.
- Add support for latest ATI SDK on windows.
- Export missing function from libztex.
- miner.php change socktimeoutsec = 10 (it only waits once)
- Bugfix: Make initial_args a const char** to satisfy exec argument type warning
(on Windows only)
- miner.php add a timeout so you don't sit and wait ... forever
- Create discrete persistent submit and get work threads per pool, thus allowing
all submitworks belonging to the same pool to reuse the same curl handle, and
all getworks to reuse their own handle.
- Use separate handles for submission to not make getwork potentially delay
share submission which is time critical.
- This will allow much more reusing of persistent connections instead of opening
new ones which can flood routers.
- This mandated a rework of the extra longpoll support (for when pools are
switched) and this is managed by restarting longpoll cleanly and waiting for a
thread join.
- miner.php only show the current date header once
- miner.php also add current time like single rig page
- miner.php display rig 'when' table at top of the multi-rig summary page
- README - add some Ztex details
- api.c include zTex in the FPGA support list
- api.c ensure 'devs' shows PGA's when only PGA code is compiled
- cgminer.c sharelog code consistency and compile warning fix
- README correct API version number
- README spelling error
- api.c combine all pairs of sprintfs()
- api.c uncomment and use BLANK (and COMMA)
- Code style cleanup
- Annotating frequency changes with the changed from value
- README clarification of 'notify' command
- README update for API RPC 'devdetails'
- api.c 'devdetails' list static details of devices
- Using less heap space as my TP-Link seems to not handle this much


Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
miscreanity
Legendary
*
Offline Offline

Activity: 1078


View Profile
April 28, 2012, 05:51:42 AM
 #5134

Queued work seems to be about 6-7x normal for my setup. At start, LP looks like it's being enabled for multiple pools. Ran 1k shares with 2.3.4 to verify, and E was much higher than 2.3.5 using the same conf.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 1988


Ruu \o/


View Profile WWW
April 28, 2012, 06:01:12 AM
 #5135

Queued work seems to be about 6-7x normal for my setup. At start, LP looks like it's being enabled for multiple pools. Ran 1k shares with 2.3.4 to verify, and E was much higher than 2.3.5 using the same conf.
Yes, the changelog said as much... LP is being used on every pool you are connected to now.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
miscreanity
Legendary
*
Offline Offline

Activity: 1078


View Profile
April 28, 2012, 06:11:37 AM
 #5136

Yes, the changelog said as much... LP is being used on every pool you are connected to now.

And I read it too... I think that's my cue to get some sleep.
Diapolo
Hero Member
*****
Offline Offline

Activity: 769



View Profile WWW
April 28, 2012, 08:39:47 AM
 #5137

Great work Con and my goffset mod for diakgcn also works Smiley.

Edit: One small glitch, after pressing Q and a succesful shutdown on Windows at the end is this line here
Code:
[201S2h-u0t4d-o2w8n  1s0i:g5n5al: 2r0e]c eliovnegdp.o
ll

Could there be an overwritten char * buffer or sth. like that?

Dia

Liked my former work for Bitcoin Core? Drop me a donation via:
1PwnvixzVAKnAqp8LCV8iuv7ohzX2pbn5x
bitcoin:1PwnvixzVAKnAqp8LCV8iuv7ohzX2pbn5x?label=Diapolo
TheSeven
Hero Member
*****
Offline Offline

Activity: 504


FPGA Mining LLC


View Profile WWW
April 28, 2012, 10:00:26 AM
 #5138

Great work Con and my goffset mod for diakgcn also works Smiley.

Edit: One small glitch, after pressing Q and a succesful shutdown on Windows at the end is this line here
Code:
[201S2h-u0t4d-o2w8n  1s0i:g5n5al: 2r0e]c eliovnegdp.o
ll

Could there be an overwritten char * buffer or sth. like that?

Dia

This looks like two threads are writing to the console at the same time, interleaving their characters Smiley
So it's probably harmless, just a logging annoyance...

Judging from the garbage you posted, the original messages seem to have been:
Code:
[2012-04-28 10:55:20] longpoll
Code:
Shutdown signal received.

My tip jar: 13kwqR7B4WcSAJCYJH1eXQcxG5vVUwKAqY
The00Dustin
Hero Member
*****
Offline Offline

Activity: 806


View Profile
April 28, 2012, 12:24:49 PM
 #5139

- Add pool number to stale share message.
Now I get it AND feel stupid!  Oh well, I bet I don't have to bring that issue I saw up again after this update whether it was the bug you found or not.   Wink
kano
Legendary
*
Offline Offline

Activity: 1918


Linux since 1997 RedHat 4


View Profile
April 28, 2012, 12:28:11 PM
 #5140

Great work Con and my goffset mod for diakgcn also works Smiley.

Edit: One small glitch, after pressing Q and a succesful shutdown on Windows at the end is this line here
Code:
[201S2h-u0t4d-o2w8n  1s0i:g5n5al: 2r0e]c eliovnegdp.o
ll

Could there be an overwritten char * buffer or sth. like that?

Dia

This looks like two threads are writing to the console at the same time, interleaving their characters Smiley
So it's probably harmless, just a logging annoyance...

Judging from the garbage you posted, the original messages seem to have been:
Code:
[2012-04-28 10:55:20] longpoll
Code:
Shutdown signal received.
Heh - nice detective work.
I can clearly see how you got the answer!
Now I can make sense of it also when I'm windows testing
(I always thought it might be windows printf's fault with variable sizes - but that clearly shows it isn't)
Yeah curses on windows is ... well ... 'nuff said.

Pool: https://kano.is BTC: 1KanoiBupPiZfkwqB7rfLXAzPnoTshAVmb
CKPool and CGMiner developer, IRC FreeNode #ckpool and #cgminer kanoi
Help keep Bitcoin secure by mining on pools with Stratum, the best protocol to mine Bitcoins with ASIC hardware
Pages: « 1 ... 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 [257] 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 ... 830 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!