Show Posts
|
Pages: [1] 2 »
|
145420 http://blockexplorer.com/block/00000000000002cd0003629d5e515222261fd290af22012c9d52375c7778f5ea
[b]Time?: 2011-09-15 06:55:09[/b] 145419 http://blockexplorer.com/block/0000000000000078ce8d6a3cacbf388d01102abed511dd8d798f75878c21a273
[b]Time?: 2011-09-15 07:16:37[/b] Something wrong?
|
|
|
There is a problem with confirmed rewards in solid coin mining.
|
|
|
According to block explorer, block 142300 was found at 20:49:38 but btcguild claimed to find this one at 19:18:15. Is there any problem with your server?
|
|
|
@Okama: I wouldn't pay much attention to the rates till much longer has passed. If you get different rates after many hours, check stability of different cards (see mine for how stable the rates can be long term with identical cards).
Below are my 5870s which have been running for hours at 975/300. I'm sure that they are stable at this clock (had been running without a hitch for weeks using phoenix before switch to cgminer). cgminer version 1.5.6 - Started: [2011-08-21 00:37:06] -------------------------------------------------------------------------------- [(5s):1640.4 (avg):1639.7 Mh/s] [Q:17490 A:26879 R:222 HW:0 E:154% U:22.48/m] TQ: 4 ST: 10 LS: 0 SS: 1 DW: 2170 NB: 125 LW: 19540 LO: 0 RF: 31 I: 8 Block: 000007728b0bd6579ee146838f6a0754... Started: [20:24:10] -------------------------------------------------------------------------------- [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit GPU 0: [451.6 / 451.9 Mh/s] [Q:5862 A:7439 R:62 HW:0 E:127% U:6.22/m] GPU 1: [435.6 / 435.3 Mh/s] [Q:3554 A:7185 R:60 HW:0 E:202% U:6.01/m]
|
|
|
GPU 0: [361.3 / 360.7 Mh/s] [Q:13 A:14 R:0 HW:0 E:108% U:4.73/m] GPU 1: [373.0 / 369.6 Mh/s] [Q:5 A:12 R:0 HW:0 E:240% U:4.06/m] GPU 2: [327.7 / 326.5 Mh/s] [Q:1 A:10 R:0 HW:0 E:1000% U:3.38/m] GPU 3: [352.0 / 349.4 Mh/s] [Q:5 A:10 R:0 HW:0 E:200% U:3.38/m] GPU 0&3 (5850) has the same clocks 875/300, but the speed is a little different. The params which I use is -I 8 -k phatk -w 256 -v 2 With phoenix 1.6.2, -k phatk2 WORKSIZE=256 AGGRESSION=12 BFI_INT FASTLOOP=false VECTORS their performance are nearly the same (~365MHash/s) My 5870s on the other system also has the same issue. My Linux box is Ubuntu 11.04 with AMDAPP v2.5, fglrx 8.861.
|
|
|
Catalyst 11.6, SDK 2.4 here. Jumped from ~428 to ~435 with 5870, 950/300 clocks.
My friend got from ~416 to 425 with 920/300 clocks, also 5870 with Catalyst 11.5, SDK 2.1.
Keep up the good work, Dia!!
|
|
|
The same problem happend to me. And I also got this long poll: IO error with the newest git version.
|
|
|
the core/mem clock is 850/180, I've run at this clock for more than a month and happy with this However, when I changed the clock to 850/300, the speed went back to ~361, a litte better than before. ps: my other 5850s, at 850/180 clock with the lastest poclbm, the speed is around 360Mhash. /Diapolo: Thanks for the hard work on optimizing phatk kernel. Really appreciate it.
|
|
|
r112 | jedi95 | 2011-07-18 13:09:01 +0900 (Mon, 18 Jul 2011) | 1 line
Performance improvement for phatk
just updated to r112, but got my speed slow down from ~360Mhash --> ~330Mhash (Ubuntu 11.4, SDK 2.4, phatk on a 5850 850MHz). Rolled back to r111 & waiting for news.
|
|
|
Does 1.5ver supports backup pool (--backup=...) like the newest poclbm?
Where did You find poclbm that supports backup pool? Please support me with link. You can find out with ./poclbm.py --help The usage is adding --backup=worker_name:worker_pass@hostname:port. This new feature saved me sometimes
|
|
|
I have the Silverstone Strider 1kW Gold. Still working on this problem. ps: Okama != Okami + Obama
|
|
|
Somebody in the forum has the same problem with their CF option enable. I disable CF but the problem remains. The temperature is ~6x celsius, so I guess the problem does not have anything relates with temp. FYI, I flashed my MSI 5970 with Sapphire 5970 official bios
|
|
|
I tried but... (using poclbm with --backup option). pacrim.eclipsemc.com:8337 22/06/2011 7:12:39, Setting pool xxx_worker @ pacrim.eclipsemc.com:8337 pacrim.eclipsemc.com:8337 22/06/2011 7:13:01, Using new LP URL /LP 2 pacrim.eclipsemc.com:8337 22/06/2011 7:13:01, LP connected to pacrim.eclipsemc.com:8337 pacrim.eclipsemc.com:8337 22/06/2011 7:13:39, 0b518459, accepted 2 2 pacrim.eclipsemc.com:8337 22/06/2011 7:13:50, 4cedd714, accepted uscentral.btcguild.com:8332 22/06/2011 7:14:18, Setting pool xxx_worker @ uscentral.btcguild.com:8332 uscentral.btcguild.com:8332 22/06/2011 7:14:26, f1b4cdca, accepted pacrim.eclipsemc.com:8337 22/06/2011 7:14:27, Setting pool xxx_worker @ pacrim.eclipsemc.com:8337 pacrim.eclipsemc.com:8337 22/06/2011 7:14:27, Attempting to fail back to primary pool uscentral.btcguild.com:8332 22/06/2011 7:14:32, Setting pool xxx_worker @ uscentral.btcguild.com:8332 uscentral.btcguild.com:8332 22/06/2011 7:14:32, Still unable to reconnect to primary pool (attempt 1), failing over uscentral.btcguild.com:8332 22/06/2011 7:14:32, warning: job finished, miner is idle uscentral.btcguild.com:8332 22/06/2011 7:14:38, 0f3cfb28, accepted Update: it seems to be ok now (with phoenix miner). Update 2: Still have the above problems with poclbm.
|
|
|
Does 1.5ver supports backup pool (--backup=...) like the newest poclbm?
|
|
|
It is ok now. Thank you ps: I think the Change password function should be modify. It does not require old password when you wan to create a new one. Seem dangerous... pps: Something weirds in this picture. Why All Time shares is smaller than Round share? I haven't press the Reset button yet
|
|
|
I have communicating problem here eu.eclipsemc.com:8337 Problems communicating with bitcoin RPC 0 2 tried US or Pacrim either...
|
|
|
Can't connect to US, EU or ASIA addrs. When I ping ping pacrim.eclipsemc.com PING pacrim.eclipsemc.com (46.51.255.204) 56(84) bytes of data. it returns nothing.
|
|
|
1 of my 2 comps can connect to mining.bitcoin.cz and it is mining well. The other cannot connect while it can connect to deepbit pool. Working on finding the reason
|
|
|
Don't go with that. You need at least 8 pci slots.
|
|
|
For sure, Linux. Say no with dummy VGA plugs or CPU load problem.
|
|
|
|