|
Card Manufacturer: AMD
Card Model Number: HD 6770
Card OEM: XFX
MHash per Second: 207
Core Clock: 960
Memory Clock: 300
Average Operating Temperature: 74C
Ambient Temperature: 20C
Fan Speed: 57%
Host OS: Windows XP
Driver Version: Catalyst 12.?, SDK 2.6
Mining Program: cgminer 2.3.1-2 with diablo kernel
Command Line Flags/GUIminer Settings: --auto-gpu --gpu-engine 750-960 --gpu-memclock 300 --temp-target 80 --gpu-vddc 1.1 -g 1 -v 2 -w 256 -k diablo
|
|
|
|
|
OK I figured it out finally. In php.ini I had to enable sockets and enable short_open_tag.
Seems to work OK now.
|
|
|
|
Sorry for yet another php noob question. I'm a software guy, just not web or database.  I'm using wamp and it's definitely running correctly. I have some sample php files working and I copied anubis into the correct directory. I'm also positive I have the cgminer api running also. When I surf to it with my browser at localhost/anubis there are a bunch of source code lines printed out in the header and body of the anubis page. Clearly I don't have the database part configured right but I don't know where to look. Also I don't know what to put in the config.inc.php file. |
|
|
|
Can Bitcoin Wallets be fixed if they go funny?
Do I really have to unistall and reinstall and let it synch for another two days?
Can I somehow retrieve the block data before doing this?
Can anyone help?
Luckily it was empty.
No, yes, no, yes (yes)  |
|
|
|
My 6770 runs waaaaaaaaaaaaaaaaay faster with the diablo kernel.
I was reliably getting around 185-190 Mhash/sec with poclbm. Now it's reliably around 202 with diablo. Really noice!
Hmm. my 6770 runs around 230 Nhash/sec with phatk at 1030/300 clocks. -v2 -w256 I haven't been able to reliably run my 6770 above 960. |
|
|
|
|
My 6770 runs waaaaaaaaaaaaaaaaay faster with the diablo kernel.
I was reliably getting around 185-190 Mhash/sec with poclbm and phatk. Now it's reliably around 202 with diablo. Really noice!
I did notice that suddenly my poclbm performance dropped from around 185 to like 165 with this new release. But I'm not complaining because of the pleasant diablo surprise.
|
|
|
|
|
If your primary is p2pool it won't go down at all anyway (unless your p2pool client crashes).
|
|
|
|
How does this look? It's a front-end GUI I wrote that talks to bitcoind while I'm mining p2pool. Right now it just shows balance, block count and transaction history. I just start it and hit refresh when I want an update. I'm planning on adding 5 second polling and a couple other features. I don't plan on implementing the full bitcoin-qt functionality.  |
|
|
|
seems the p2pool HASHRATE stop growing ?
what's wrong? full?
Anybody running an old version is going to have p2pool stop working. That's going to affect the hashrate until everyone upgrades. Yeah c'mon you slackers! Hurry up and upgrade you're slowin' me down! |
|
|
|
Performance is remaining stable & no obvious issues so far.
Subjectively, it seems to be doing better using p2pool mixed with others. I'll let it run for several more hours and assess again.
I've been running the new version for about 2 hours on p2pool. Seems about the same performance-wise and running with no hiccups so far. |
|
|
|
|
If you choose PPS your daily payment will be almost exactly same all the time.
|
|
|
|
|
If you wanna just get your feet wet, start with deepbit. It's not like you're getting married or anything. You can join any of the pools and switch among them as you like.
I started with deepbit because it was very easy to set up and monitor. The server is very reliable.
If you use proportional the fee is 3%. If you use PPS the fee is 10%. Obviously using proportional has more daily variation in payout but on average you come out ahead. For instance I have a 200 Mh/sec setup; some days I made 0.10 BTC and others I made 0.16 BTC.
|
|
|
|
OK 1 last noob question and I'll wait 5 hours before posting again. If I don't show up on http://yat.uukgoblin.net/p2pool-stats/current_payouts.html, yet my cgminer is clearly working hard on solving something, what am I really accomplishing? I'm being told to solve hashes but I'm not in line for any payment at all is how it seems. Or is it that copy/paste snippet you wanted me to remember? It's still using an address that bitcoind assigned (and I can't find) and I'll get paid something eventually on that address for my current efforts? |
|
|
|
No, but I went to http://127.0.0.1:9332/payout_addr and it says the address I've been seeing for the last week. OK, rather than mess with changing payout addresses I just switched to using -a with the payout address I was using with deepbit. This should keep things simpler anyway. |
|
|
|
Why does p2pool currently show "current payout: 0.0000 BTC"? Seems a little low...
You've recently restarted p2pool, and it's got a new address from your bitcoind. Please feel free to cut and paste this when someone asks the same question in 14.36 hours: Your previous address will still receive any payouts if a block is found within 24 hours, your new address will also receive it's share of any payouts. Your expected payout will be spread across both addresses. If a block is found now, the old will get the bigger share. If a block is found in 20 hours, the new will have a much larger share. If you want to keep the same address (so you can keep an eye on things), specify it with the "-a" option. I'll keep the copy/paste in mind for the future, but I definitely have the same payout address as before. |
|
|
|
|
Your chances of hitting the megamillion lottery or being killed by a meteorite are far, far greater.
|
|
|
|
Yes, I do have it change the settings. Here's my command line: cgminer -o http://127.0.0.1:9332 -u xxx-p xxx--auto-gpu --gpu-engine 750-960 --gpu-memclock 250 --temp-target 80 --gpu-vddc 1.1 -g 1 But did you reboot or manually set them back after using the previous version that didn't set them back due to the crash? CGMINER sets them back to where they were when it started, it doesn't know the defaults. I set them back to their mfg defaults using the Catalyst Control Center, then ran cgminer to see if it restored them (which it didn't). Shafted. Hmmm. Not sure what that means in this context. |
|
|
|
Yes, I do have it change the settings. Here's my command line: cgminer -o http://127.0.0.1:9332 -u xxx-p xxx--auto-gpu --gpu-engine 750-960 --gpu-memclock 250 --temp-target 80 --gpu-vddc 1.1 -g 1 But did you reboot or manually set them back after using the previous version that didn't set them back due to the crash? CGMINER sets them back to where they were when it started, it doesn't know the defaults. I set them back to their mfg defaults using the Catalyst Control Center, then ran cgminer to see if it restored them (which it didn't). |
|
|
|
I started and stopped it like 10 times and it didn't crash. Isn't supposed to restore the GPU settings though? It still leaves the GPU at its mining settings (a minor inconvenience). Yes it is supposed to restore the GPU settings. Though that's only if you actually make it change any settings when you start it. It does not try to restore anything if it never adjusted any settings to begin with. Yes, I do have it change the settings. Here's my command line: cgminer -o http://127.0.0.1:9332 -u xxx-p xxx--auto-gpu --gpu-engine 750-960 --gpu-memclock 250 --temp-target 80 --gpu-vddc 1.1 -g 1 |
|
|
|
|
Show Posts
