I didn't have that much downtime here. Maybe just a little one around 5AM UTC where my miner sent about 60 shares to my backup pool, but otherwise no major loss of connectivity during the last 24h (just a single share here and there, as I suppose happens when you hop).
|
|
|
I suppose some people work on their mining rig I do, but keep mining, and the PC isn't as responsive as it could be without mining.
|
|
|
Indeed, I have about 1.2% rejects now while I used to have in the 3+% before. Much better, this almost compensates the 120->116% change Edit: however, the pool is being slow right now: cgminer is flooding me with "pool not providing work fast enough" messages, making me mine around 500MH/s instead of the usual 700.
|
|
|
The server went down, we are waiting for the hosting company to restart the server. No hard ETA but I've been told "soon". Wow, what kind of hosting company is this? Mine allows me to restart my server myself... I didn't imagine some companies don't do the same!
|
|
|
@DeaDTerra: same here, pool seems down a lot. Beta testing and scaling I guess (I assume/hope the problem isn't on my side).
|
|
|
metcalfing (verb):
1. To disclose illegal or immoral activities while unwittingly giving clues to the individual's true identity.
My buddy got caught metcalfing on a dating site by his wife.
+1... off to urban dictionary we go... Seriously, this already exists... http://www.urbandictionary.com/define.php?term=metcalfe Hilarious thread, otherwise...
|
|
|
I was going to give a percent of the money to p2pool but I'm really put off on their .5% hidden fee. I need to see how aware people are of this before I move in that direction. I definitely wasn't aware of this fee.
|
|
|
Count me in again If you happen to have your old user database handy, I still have my old credentials.
|
|
|
Not really the press, but I bet the chapter 5 of this (see tab "syllabus") will mention Bitcoin at some point: CS387 - APPLIED CRYPTOGRAPHY [...] WEEK 5: Digital Cash How to make money from numbers alone http://www.udacity.com/overview/Course/cs387Given the current exposure of this kind of courses (from what I understood, about 100k students in a previous similar experience, AI-class.com), we might well get some hashrate boost when the course hits this chapter, in early May I suppose.
|
|
|
I get 442 Mh/s on my 5870's clocked at 970/170 on 2.5 (793.1). So 2.5 does just fine at lower mem clock settings (yes verified by GPUz). I'm getting 396MH/s @890/300 currently - 333MH/s @750/300 on the other one (underclocked for silence), about 2% slower clock for clock. Tried setting the RAM @170, lost about 10% hashrate. I guess I'll have to play with the drivers a bit some time then (next time I upgrade cgminer I suppose ). Not that urgent though, given the small speed difference.
|
|
|
I'm surprised that worked, actually. Yeah, I wasn't really expecting it to work either, but I thought this was worth trying since I've got some stuff running that I can't really interrupt right now. Working and looking good, although I'm not using "advanced" features such as overclocking/fan control/etc - the only thing I configure from cgminer, apart from the proxy now, is the intensity. EDIT2: The .cl file isn't used when you have a .bin file, you probably sohuldn't have overwritten it with the older one, but if you never change settings, it won't matter. Kept a backup anyway EDIT: Also, with Cypress and phatk, I am under the impression that SDK 2.1 is better when the GPU memory is underclocked. You might want to dowload phatk120223Cypressv2w128l4.bin from http://ck.kolivas.org/apps/cgminer/bins/2.1/ and try out the SDK 2.1 binary that is actually compiled in 2.3.1-2. Just tried it, doesn't work (error 42, then recompiles the slower new version over it)
|
|
|
Hm, alright, thanks for all this information. I grabbed the old phatk110817.cl and phatk110817Cypressbitalignv2w128long4.bin from my cgminer 2.0.6, renamed them to phatk120223.cl and phatk120223Cypressv2w128l4.bin and this did restore my hashrate. Judging from their date, they were built either under Catalyst 11.9 or 11.10. Should I expect any additional benefit from messing with my drivers as you describe? The changelog doesn't seem to mention performance improvements, "just" tons of features, bugfixes, and tweaks for newest GPUs.
|
|
|
I should say quite a lot more than that. Post it all. Also in the cgminer directory in a command prompt: dir/a *.bin
Woops, I ran it on version 2.0.6 instead of 2.3.1, that's why. There you go: >cgminer -n [2012-03-09 12:59:20] CL Platform 0 vendor: Advanced Micro Devices, Inc. [2012-03-09 12:59:20] CL Platform 0 name: AMD Accelerated Parallel Processing [2012-03-09 12:59:20] CL Platform 0 version: OpenCL 1.1 AMD-APP (898.1) [2012-03-09 12:59:20] Platform 0 devices: 2 [2012-03-09 12:59:20] GPU 0 ATI Radeon HD 5800 Series hardware monitoring enable d [2012-03-09 12:59:20] GPU 1 ATI Radeon HD 5800 Series hardware monitoring enable d [2012-03-09 12:59:20] 2 GPU devices max detected >dir/a *.bin Volume in drive E is xxxx Volume Serial Number is xxxxx
Directory of E:\xxx\cgminer-2.3.1-2
2012-03-07 16:53 751,168 phatk120223Cypressv2w128l4.bin 1 File(s) 751,168 bytes 0 Dir(s) 198,869,528,576 bytes free Edit: actually, on cgminer 2.0.6 I'm even ~730MH/s right now
|
|
|
Have you updated drivers/sdk on that machine since you first started 2.0.6? If you did, you are probably using SDK 2.6 now... I've kept my drivers updated, but I haven't upgraded since I switched from 2.0.6 to 2.3.1. To be sure (Catalyst 12.2 was indeed released not long before I switched from 2.0.6 to 2.3.1), I just relaunched 2.0.6 right now: I'm still getting around 710MH/s @kano: was "cgminer -n" for me? (it just tells me I have 2 GPUs - that's correct I have 2 5870s)
|
|
|
I don't really upgrade this one often, because I tend to avoid fixing things that already work, but I recently upgraded from 2.0.6 to 2.3.1 because I wanted to use a SOCKS proxy. It turns out it's quite slower: from about 710-720 MH/s I'm now around 650 MH/s with the same very settings (same GPU clock, same intensity). This doesn't seem to be due to a change in hash speed measurement on the client because I get the same figures from my pool's speed estimations. Anyone else noticed such a speed drop at some point between v 2.0.6 and 2.3.1?
|
|
|
If Litecoin can be GPU mined it is best to figure out everything about that now, and either change the model of the coin to be CPU only or figure out how to compete with a GPU based Litecoin. The "retards" are finding out more about an experimental technology we call Litecoin. I'd personally rather all the flaws come to light NOW than in a year after I invest even more time and resources into this coin. Ditto. Giving it a week or two to see how hashrate evolves and more reactions about this GPU mining stuff, then maybe pointing my last mining CPU to BOINC like the other ones. GPU mining = BTC, we don't need a duplicate. LTC was sold as being innovative because it was CPU-only, that isn't true anymore. This was to be expected, but I also thought the hashing algo would be updated to fight that... which doesn't seem to happen any time soon.
|
|
|
IMO Litecoin loses its point unless its CPU only Clearly, yes. Now instead of being more accessible to everyone than BTC (because everyone has an okay CPU while not everyone has an okay GPU), LTC is accessible only to the few who are lucky enough to have the GPU miner working properly... Huge step backwards. The only positive effect is that it seems the BTC hashrate lowered a bit recently.
|
|
|
You can encrypt files yourself and keep them at dropbox folder. That's private. But not exactly as convenient as having the encryption done by the backup software itself.
|
|
|
The kernel build uses code that is specific for 58xx or 69xx GPUs... only people who own those may mine, it crashes or mines stales for everyone else. I do have a 5870. It's not crashing, it just fails to connect to pool/daemon.
|
|
|
|