Author

Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 718. (Read 5806004 times)

-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
The problem was solved for each machine by restarting cgminer.

I dont see anything common between the machines that could explain this.

Anyone have a clue? Pretty please?
When it happens again, go into the display menu and enable Verbose mode, Rpc debugging and Debug mode and see what is output.
hero member
Activity: 518
Merit: 500
18.5 degree... i hate you  Cheesy Wink

Because its not doing anything. When its actually working it gets scorching hot.. like 40C! Wink
legendary
Activity: 1022
Merit: 1000
BitMinter
18.5 degree... i hate you  Cheesy Wink
hero member
Activity: 518
Merit: 500
Ive posted this a few times, but never got any response.
It happened again. On both my rigs:



Left one is running on linuxcoin, right one is local on windows.

Hashrate basically drops to zero as cgminer keeps switching pools and not being able to connect to either.

My network and internet connection is fine. Ive (again) tried restarting the routers, just in case but it changed nothing. Both miners where still in limbo after that
My public IP address has not changed.
The problem is not the pools, both were up.

The problem was solved for each machine by restarting cgminer.

I dont see anything common between the machines that could explain this.

Anyone have a clue? Pretty please?
donator
Activity: 1218
Merit: 1079
Gerald Davis
Did the graphics drivers update? There have been lots of reports of the recent drivers dropping hash rates. A reboot would cause newly installed drivers to load.

Nope, I'm already at 11.12 (didn't see a performance drop that everyone else reports - interesting).

On that note, what are the suggested drivers for mining in Windows? 11.6?

My guess is that you installed 11.12 but maybe didn't reboot thus older drivers were still loaded.  You reboot.  11.12 and its lower performance loads and bingo.  Or maybe the driver had nothing to do with it and the sdk was updated after reboot (2.4 or 2.5 to 2.6).

God I wish AMD could write some halfway decent drivers.  It is a complete lottery on each driver update.
newbie
Activity: 36
Merit: 0
11.6 with sdk 2.4  remains the best for both windows and linux for mining, if not for gaming.

Installed 11.6 and SDK 2.4, hash back up to ~82, which is OK. We'll see how that goes in the future. Thanks Smiley
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Did the graphics drivers update? There have been lots of reports of the recent drivers dropping hash rates. A reboot would cause newly installed drivers to load.

Nope, I'm already at 11.12 (didn't see a performance drop that everyone else reports - interesting).

On that note, what are the suggested drivers for mining in Windows? 11.6?
11.6 with sdk 2.4  remains the best for both windows and linux for mining, if not for gaming.
sr. member
Activity: 392
Merit: 250
Just has to pursued Norton Antivirus that v2.1.0 isn't a Trojan :/
Same here with AVG and cgminer 2.0.6... Looks like the antivirus guys drank too much on Xmas.

The drop was after a restart (the whole previous day it was 84Mhash). It's a Radeon HD 4830, mining at 72C.
Just had the same issue after restarting my miner: one of the GPU would barely mine, the other would mine around 250 MHs vs the usual 380. Turned out the auto-intensity was screwing up, forcing it manually to 8 fixed the drop (and even increased hashrate above what I was used to). PC feels a bit laggy though now  Grin

Going to try 2.1.0...
newbie
Activity: 36
Merit: 0
Did the graphics drivers update? There have been lots of reports of the recent drivers dropping hash rates. A reboot would cause newly installed drivers to load.

Nope, I'm already at 11.12 (didn't see a performance drop that everyone else reports - interesting).

On that note, what are the suggested drivers for mining in Windows? 11.6?
hero member
Activity: 742
Merit: 500
When I first start my miner, it usually shows a higher than accurate rate.  Over what timeframe did you see this drop?  What are you mining on that gives you 84 MH/s? nvidia?

What are your system's temps?

The drop was after a restart (the whole previous day it was 84Mhash). It's a Radeon HD 4830, mining at 72C.
Did the graphics drivers update? There have been lots of reports of the recent drivers dropping hash rates. A reboot would cause newly installed drivers to load.
newbie
Activity: 36
Merit: 0
When I first start my miner, it usually shows a higher than accurate rate.  Over what timeframe did you see this drop?  What are you mining on that gives you 84 MH/s? nvidia?

What are your system's temps?

The drop was after a restart (the whole previous day it was 84Mhash). It's a Radeon HD 4830, mining at 72C.
hero member
Activity: 742
Merit: 500
My hash rate dropped from 84 to 61 without making any changes to the system (upon a simple shut down and power on). Great.

I don't suppose anyone has any suggestions?
When I first start my miner, it usually shows a higher than accurate rate.  Over what timeframe did you see this drop?  What are you mining on that gives you 84 MH/s? nvidia?

What are your system's temps?
newbie
Activity: 36
Merit: 0
My hash rate dropped from 84 to 61 without making any changes to the system (upon a simple shut down and power on). Great.

I don't suppose anyone has any suggestions?
legendary
Activity: 1795
Merit: 1208
This is not OK.
Just has to pursued Norton Antivirus that v2.1.0 isn't a Trojan :/
donator
Activity: 798
Merit: 500
I had to lower the clocks on 5 cards (2 separate rigs) with 2.1.0 because they were locking up, and they were not previously, but they are more stable at I 9 now where I was using I 7 and 8.  But my rejects are down. Maybe SAC is seeing 2 different issues...drop the clocks and see what happens.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
I'd suggest this is a known old problem and not cgminer either.
A few months back I had issues connecting to one pool and it worked fine on all other pools.
The problem occurred when my network link included my PowerLine link from my garage to my unit over the electrical cables - it's a low quality connection and somehow that affected connecting to a single pool but worked fine with others.
Redirecting the link via an ssh tunnel over the PowerLine also resolved it for that pool.
So, basically, network issues seem to affect mining even when other network access seems to be OK. (curl+json sux)
I guess it's valid to blame the network link (as was the pool decision back then) so I'd also suggest such current problems are network related also.
donator
Activity: 798
Merit: 500
No, not that. My donor pool has had all sorts of problems so I migrated it yet again Undecided

I meant
https://bitcointalksearch.org/topic/m.666309

"Enough of 2.1.0..."

As I said, none of that connectivity code was touched...

You mean this:

Code:
[2011-12-28 21:31:13] Accepted 00000000.9db18e77.6b722002 GPU 0 thread 6 pool 0
[2011-12-28 21:31:13] Pool 0 not providing work fast enough
[2011-12-28 21:32:13] Pool 0 http://us.eclipsemc.com:8337 not responding!
[2011-12-28 21:32:13] Switching to http://pool.ABCPool.co:8332
[2011-12-28 21:33:13] Pool 1 http://pool.ABCPool.co:8332 not responding!
[2011-12-28 21:33:15] Pool 0 http://us.eclipsemc.com:8337 recovered
[2011-12-28 21:33:15] Switching to http://us.eclipsemc.com:8337
[2011-12-28 21:33:16] Accepted 00000000.7b06b191.ab3607c6 GPU 0 thread 6 pool 0
[2011-12-28 21:33:17] Accepted 00000000.104c9527.facc368c GPU 0 thread 0 pool 0
[2011-12-28 21:33:18] Accepted 00000000.c4afa757.9d4765cf GPU 3 thread 9 pool 0
[2011-12-28 21:33:18] Accepted 00000000.435cb5e0.5d300998 GPU 2 thread 8 pool 0
[2011-12-28 21:33:20] Accepted 00000000.f88ea6e0.1ab894ec GPU 4 thread 4 pool 0
[2011-12-28 21:33:21] Accepted 00000000.79df871e.6b0cc209 GPU 1 thread 1 pool 0
[2011-12-28 21:33:27] Accepted 00000000.bd418242.b589be17 GPU 4 thread 4 pool 0
[2011-12-28 21:33:27] Accepted 00000000.d4de7026.d23e87a4 GPU 4 thread 4 pool 0
[2011-12-28 21:33:28] Accepted 00000000.5193ccbb.c64c46ba GPU 5 thread 11 pool 0
[2011-12-28 21:33:29] Accepted 00000000.1a451c77.7b262020 GPU 0 thread 6 pool 0
[2011-12-28 21:33:30] Accepted 00000000.d00a7af4.f7b04e30 GPU 5 thread 11 pool 0
[2011-12-28 21:33:31] Accepted 00000000.9bac68f6.e8bfc665 GPU 2 thread 8 pool 0
[2011-12-28 21:33:34] Accepted 00000000.0d624e1a.6846e255 GPU 5 thread 5 pool 0
[2011-12-28 21:33:35] Accepted 00000000.6e9713fa.d1cf32e7 GPU 4 thread 4 pool 0
[2011-12-28 21:33:37] Accepted 00000000.74bbad98.506943ce GPU 2 thread 8 pool 0
[2011-12-28 21:33:38] Pool 0 not providing work fast enough
[2011-12-28 21:33:38] Accepted 00000000.71952990.4c0d45ff GPU 3 thread 3 pool 0
[2011-12-28 21:34:16] Pool 1 http://pool.ABCPool.co:8332 recovered
[2011-12-28 21:34:19] Accepted 00000000.add93703.991b48db GPU 0 thread 6 pool 1
[2011-12-28 21:34:38] Pool 0 http://us.eclipsemc.com:8337 not responding!
[2011-12-28 21:34:38] Switching to http://pool.ABCPool.co:8332
[2011-12-28 21:35:38] Pool 1 http://pool.ABCPool.co:8332 not responding!
[2011-12-28 21:35:39] Pool 0 http://us.eclipsemc.com:8337 recovered
[2011-12-28 21:35:39] Switching to http://us.eclipsemc.com:8337
[2011-12-28 21:35:41] Accepted 00000000.b9eb377a.3ce6ecd2 GPU 1 thread 7 pool 0
[2011-12-28 21:35:43] Accepted 00000000.a5eeea48.c20b48fb GPU 5 thread 11 pool 0
[2011-12-28 21:35:44] Accepted 00000000.adbc5783.de798509 GPU 0 thread 0 pool 0
[2011-12-28 21:35:44] Accepted 00000000.39c29bcd.702936fa GPU 2 thread 8 pool 0
[2011-12-28 21:35:45] Accepted 00000000.6235e2e3.7ebdfc32 GPU 4 thread 10 pool 0
[2011-12-28 21:35:46] Accepted 00000000.8b8383d1.08ee4027 GPU 5 thread 5 pool 0
[2011-12-28 21:35:50] Accepted 00000000.92c4510c.11078e6f GPU 3 thread 9 pool 0
[2011-12-28 21:35:54] Accepted 00000000.8abf6d30.2266e590 GPU 3 thread 9 pool 0
[2011-12-28 21:35:55] Accepted 00000000.3214ada6.ffb465a6 GPU 3 thread 3 pool 0
[2011-12-28 21:35:57] Accepted 00000000.49a15d5d.761c8082 GPU 1 thread 7 pool 0
[2011-12-28 21:35:59] Accepted 00000000.65be925f.2d5327c9 GPU 4 thread 10 pool 0
[2011-12-28 21:36:01] Accepted 00000000.0b86c772.9dbb634e GPU 4 thread 10 pool 0
[2011-12-28 21:36:02] Pool 0 not providing work fast enough
[2011-12-28 21:36:41] Pool 1 http://pool.ABCPool.co:8332 recovered
[2011-12-28 21:36:42] Accepted 00000000.8d0c118c.a9f151a3 GPU 1 thread 1 pool 1
[2011-12-28 21:36:42] Accepted 00000000.84f04fec.0ec34ab6 GPU 1 thread 1 pool 1
[2011-12-28 21:36:43] Accepted 00000000.6f3f8dfa.2f61bc88 GPU 1 thread 1 pool 1
[2011-12-28 21:37:02] Pool 0 http://us.eclipsemc.com:8337 not responding!
[2011-12-28 21:37:02] Switching to http://pool.ABCPool.co:8332
[2011-12-28 21:38:02] Pool 1 http://pool.ABCPool.co:8332 not responding!
[2011-12-28 21:38:03] Pool 0 http://us.eclipsemc.com:8337 recovered
[2011-12-28 21:38:03] Switching to http://us.eclipsemc.com:8337
[2011-12-28 21:38:04] Accepted 00000000.155c6ce0.cb74b994 GPU 2 thread 8 pool 0
[2011-12-28 21:38:04] Accepted 00000000.b08c1d2d.aee25f32 GPU 4 thread 4 pool 0
[2011-12-28 21:38:04] Accepted 00000000.4bec07e0.e7a97dd6 GPU 5 thread 5 pool 0
[2011-12-28 21:38:06] Accepted 00000000.ce215df2.84cee342 GPU 1 thread 1 pool 0
[2011-12-28 21:38:09] Accepted 00000000.b4af2e9f.add5020a GPU 2 thread 2 pool 0
[2011-12-28 21:38:19] Accepted 00000000.453c0033.de6078ef GPU 1 thread 7 pool 0
[2011-12-28 21:38:20] Accepted 00000000.2a85e414.8e3885de GPU 1 thread 7 pool 0
[2011-12-28 21:38:21] Accepted 00000000.95a47a59.113fc6d5 GPU 4 thread 4 pool 0
[2011-12-28 21:38:23] Accepted 00000000.2cbbed4e.fc65d180 GPU 1 thread 1 pool 0
[2011-12-28 21:38:23] Accepted 00000000.aed1b1ef.d92c2af6 GPU 4 thread 4 pool 0
[2011-12-28 21:38:24] Accepted 00000000.68b8ce70.e99b4ed4 GPU 0 thread 6 pool 0
[2011-12-28 21:38:26] Accepted 00000000.0935b5bd.a2ec689f GPU 2 thread 8 pool 0
[2011-12-28 21:38:26] Pool 0 not providing work fast enough
[2011-12-28 21:39:04] Pool 1 http://pool.ABCPool.co:8332 recovered
[2011-12-28 21:39:26] Pool 0 http://us.eclipsemc.com:8337 not responding!
[2011-12-28 21:39:26] Switching to http://pool.ABCPool.co:8332
[2011-12-28 21:40:26] Pool 1 http://pool.ABCPool.co:8332 not responding!
[2011-12-28 21:40:29] Pool 0 http://us.eclipsemc.com:8337 recovered
[2011-12-28 21:40:29] Switching to http://us.eclipsemc.com:8337
[2011-12-28 21:40:29] Accepted 00000000.5c82064e.fc2d550f GPU 2 thread 2 pool 0
[2011-12-28 21:40:30] Accepted 00000000.06e297de.faf39f5c GPU 2 thread 2 pool 0
[2011-12-28 21:40:36] Accepted 00000000.d74cf4fb.706eef70 GPU 5 thread 11 pool 0
[2011-12-28 21:40:38] Accepted 00000000.befa90ff.b428148d GPU 0 thread 6 pool 0
[2011-12-28 21:40:43] Accepted 00000000.4c37f8ca.30b85875 GPU 4 thread 10 pool 0
[2011-12-28 21:40:44] Accepted 00000000.609878ac.94aa9483 GPU 4 thread 4 pool 0
[2011-12-28 21:40:46] Accepted 00000000.1ce5bc5f.06216422 GPU 0 thread 0 pool 0
[2011-12-28 21:40:50] Accepted 00000000.985ac122.bdb3ed5c GPU 0 thread 0 pool 0
[2011-12-28 21:40:51] Accepted 00000000.44e9ca44.ffbee6df GPU 2 thread 8 pool 0
[2011-12-28 21:40:51] Pool 0 not providing work fast enough
[2011-12-28 21:41:29] Pool 1 http://pool.ABCPool.co:8332 recovered
[2011-12-28 21:41:52] Pool 0 http://us.eclipsemc.com:8337 not responding!
[2011-12-28 21:41:52] Switching to http://pool.ABCPool.co:8332
[2011-12-28 21:42:52] Pool 1 http://pool.ABCPool.co:8332 not responding!
[2011-12-28 21:42:54] Pool 0 http://us.eclipsemc.com:8337 recovered
[2011-12-28 21:42:54] Switching to http://us.eclipsemc.com:8337
[2011-12-28 21:42:55] Accepted 00000000.41c6211d.d2038690 GPU 3 thread 9 pool 0
[2011-12-28 21:42:55] Accepted 00000000.150540dd.2edc5dba GPU 1 thread 7 pool 0
[2011-12-28 21:43:01] Accepted 00000000.22d00c85.da36f33b GPU 3 thread 3 pool 0
[2011-12-28 21:43:02] Accepted 00000000.e30a3445.cf7d38dd GPU 0 thread 6 pool 0
[2011-12-28 21:43:06] Accepted 00000000.3102c021.b4a24e87 GPU 2 thread 8 pool 0
[2011-12-28 21:43:08] Accepted 00000000.4886b056.217732d0 GPU 4 thread 10 pool 0
[2011-12-28 21:43:08] Accepted 00000000.f6960f1e.ed46e6e0 GPU 2 thread 8 pool 0
[2011-12-28 21:43:09] Accepted 00000000.c4d6e242.0fdf3e7d GPU 2 thread 8 pool 0
[2011-12-28 21:43:09] Accepted 00000000.85466883.6c6fff85 GPU 4 thread 4 pool 0
[2011-12-28 21:43:12] Accepted 00000000.d33cb1a3.2e1d5b24 GPU 0 thread 0 pool 0
[2011-12-28 21:43:14] Accepted 00000000.e57a8f5d.76c837e3 GPU 0 thread 0 pool 0
[2011-12-28 21:43:17] Pool 0 not providing work fast enough
[2011-12-28 21:43:17] Accepted 00000000.59c63106.828494f8 GPU 4 thread 4 pool 0
[2011-12-28 21:43:33] LONGPOLL detected new block on network, waiting on fresh work
[2011-12-28 21:43:44] Accepted 00000000.0774acdf.c71f6ff5 GPU 4 thread 10 pool 0
[2011-12-28 21:43:46] Accepted 00000000.3f24ca14.95c6b086 GPU 1 thread 7 pool 0
[2011-12-28 21:43:49] Accepted 00000000.17058b0a.7aaedac0 GPU 2 thread 8 pool 0
[2011-12-28 21:43:51] Overheat detected on GPU 4, increasing fan to 100%
[2011-12-28 21:43:52] Accepted 00000000.bbbf62c7.933ffb39 GPU 4 thread 10 pool 0
[2011-12-28 21:43:54] Accepted 00000000.fa11310b.a100c3f1 GPU 3 thread 3 pool 0
[2011-12-28 21:43:55] Pool 1 http://pool.ABCPool.co:8332 recovered
[2011-12-28 21:43:55] Accepted 00000000.bf30d3b0.af55682a GPU 5 thread 5 pool 0
[2011-12-28 21:43:55] Accepted 00000000.9b0490de.4822f40d GPU 0 thread 6 pool 0
[2011-12-28 21:43:56] Accepted 00000000.1910bcbb.3a26774a GPU 2 thread 8 pool 0
[2011-12-28 21:43:56] Pool 0 not providing work fast enough
[2011-12-28 21:44:56] Pool 0 http://us.eclipsemc.com:8337 not responding!
[2011-12-28 21:44:56] Switching to http://pool.ABCPool.co:8332
[2011-12-28 21:45:56] Pool 1 http://pool.ABCPool.co:8332 not responding!
[2011-12-28 21:45:57] Pool 0 http://us.eclipsemc.com:8337 recovered
[2011-12-28 21:45:57] Switching to http://us.eclipsemc.com:8337
[2011-12-28 21:45:58] Accepted 00000000.02e254ef.9dac55f6 GPU 0 thread 0 pool 0

I don't know about the others but I have seen this all the way back to 2.0.0, only have logs in 2.0.7 though. Restarting the machine solves it for anywhere from an hour to a month.  Figured it was just my router, it's more frequent with more miners on the same router.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
No, not that. My donor pool has had all sorts of problems so I migrated it yet again Undecided

I meant
https://bitcointalksearch.org/topic/m.666309

"Enough of 2.1.0..."

As I said, none of that connectivity code was touched...
full member
Activity: 373
Merit: 100
Could you try the git tree now please?

Tried twice and got no segfault - seems to work. Cheesy
Sweet, thanks!

I don't know what to make of the other reports of connectivity issues since none of that code was actually changed... Unless something changed indirectly by addition of the API code?

Are you referring to the connection problems with the donation pool?
My guess about those is either spam/botnet protection by the pool or some sort of location-based misconfiguration by the ISP or whatever (IOW network problems). I doubt it's in the code, but it would be nice if the code somehow didn't wait for a successful connection to the donation pool and simply background the whole donation pool connection process. That way it won't interrupt mining and still give the pool a chance to be used.
I can try doing some protocol debugging when that happens and I have the time, but I'm kinda booked for the next few days...
Jump to: