|
Proofer it will only go to 100% at the temp-overheat value which you have set to 77.
|
|
|
|
Must be something other than 5970+Linux: I've been running 2.2.3 on a 3x5970 rig for several days without problems. (Well, I did have one DEAD core but I had that occasionally with previous versions as well.) With p2pool: "intensity" : "9",
"gpu-threads" : "1",
"gpu-engine" : "810-810",
"gpu-memclock" : "200",
"gpu-fan" : "85",
"temp-cutoff" : "80",
"temp-overheat" : "77",
"temp-target" : "70",
"temp-hysteresis" : "3",
"auto-fan" : true,
"auto-gpu" : true,
Take this out and see what happens: |
|
|
|
He's trying to get p2pool to bind to a specific network interface (not to a specific port as your suggested solution was talking about). But p2pool doesn't have an option to bind to a specific interface (yet) and instead it binds to all available interfaces.
Thanks twmz, that was helpful, as your 1Twmz will show  |
|
|
|
gnar1ta$, it helps if you know what you're talking about.
Wandering Albatross, line 764 of p2pool/main.py has a reactor.listenTCP where you can provide an interface argument, but doesn't. So, wait on forrestv to code the means of changing that via argument or take the initiative.
Hence the  What is it he is trying to do? |
|
|
|
That's not clear to me. It says to connect to an existing p2pool node. I'm running p2pool to listen for my miners not to connect to an existing node.
worker interface:
-w PORT, --worker-port PORT
listen on PORT for RPC connections from miners
(default: bitcoin:9332, litecoin:9327) No... |
|
|
|
I have multiple interfaces on a host and I want run_p2pool.py to listen on 9.8.7.6:9332 How do I do this?
p2pool interface:
--p2pool-port PORT use port PORT to listen for connections (forward this
port from your router!) (default: bitcoin:9333,
litecoin:9338)
-n ADDR[:PORT], --p2pool-node ADDR[:PORT]
connect to existing p2pool node at ADDR listening on
port PORT (defaults to default p2pool P2P port) in
addition to builtin addresses
worker interface:
-w PORT, --worker-port PORT
listen on PORT for RPC connections from miners
(default: bitcoin:9332, litecoin:9327) |
|
|
|
For merges mining, I get this error messages: Did you create a bitcoin.conf for namecoind with user, pass, and rpc port? |
|
|
|
|
Anyone know how to solve rcocchiararo's "no protocol specified" issue? I've reformatted a couple rigs cuz I couldn't figure that one out. Sometimes host + works, but usually not.
|
|
|
|
Hello ck!
Apparently the problem with "OFF" decreased but not disappeared completely:
Same here. Ran 18 hrs and got 3 of 4 cards showing OFF with 2.2.3. Started 2.1.2 with the same flags last night, I'll check it in 8 hours. Are you using --auto-fan? Not using auto-fan seemed to solve it in 2.2.1, until my power crashed anyway. Can you check in the menu when the GPUs were "last initialised" ? Didn't' forget about this  I ran 2.1.2 with no errors for 18 hours then started 2.2.3 yesterday with the same flags and got this: cgminer version 2.2.3 - Started: [2012-02-08 22:52:08]
GPU 2: 74.0C 1801RPM | OFF / 36.9Mh/s | A: 545 R: 2 HW:0 U: 0.48/m I: 8
GPU 2: 0.0 / 37.1 Mh/s | A:545 R:2 HW:0 U:0.48/m I:8
74.0 C F: 31% (1805 RPM) E: 157 MHz M: 200 Mhz V: 0.950V A: 0% P: 0%
Last initialised: [2012-02-08 22:52:12]
Intensity: 8
Thread 4: 0.0 Mh/s Disabled ALIVE
Thread 5: 0.0 Mh/s Disabled ALIVE
Log entry: [2012-02-09 00:48:34] Device 2 idle for more than 60 seconds, GPU 2 declared SICK!
[2012-02-09 00:48:34] Attempting to restart GPU
[2012-02-09 00:48:34] Thread 4 still exists, killing it off
[2012-02-09 00:48:34] Thread 5 still exists, killing it off
[2012-02-09 00:48:35] Thread 4 restarted
[2012-02-09 00:48:35] Thread 5 restarted
[2012-02-09 00:48:36] Thread 4 being disabled
[2012-02-09 00:48:36] Thread 5 being disabled Weird how las initialised is slightly after start time, but it wasn't disabled for a few hours. You might be on to something here. |
|
|
|
|
Are they asking to "donate" your GPU to mine bitcoins for them as a way to raise funds?
|
|
|
|
|
Ha, the spec board would crash if Iran bought $1 billion of bitcoins then Australia cashed out $1 billion the next day. Chaos....
|
|
|
|
|
Don't the exchanges run similiar to this service? If I withdraw bitcoins from an exchange, wether from a purchase or transfered from another wallet, they come from a mixed pool of coins and not a specific address attached to my account. Or do I have that wrong?
|
|
|
|
|
I really don't see the issue here, as long as people are open about it. There are many things pools ops can do to detect and prevent hopping, and there are many things a miner can do to not lose earnings to hoppers. None of this is a secret, there are many threads on all of this.
|
|
|
|
So, no comment from the OP? You felt so strongly to start this thread, do you still feel the same? Is something still fishy or was it variance after all?
Even more fishy. As soon as I started this thread the pool miraculously starts finding blocks again. That is fishy...I wouldn't expect a lucky streak after an unlucky streak, the math just doesn't add up, how would that ever average out!?!? Are you joking? Do you know what "random" and what "probability" mean? Sorry, forgot the  no coffee yet... |
|
|
|
So, no comment from the OP? You felt so strongly to start this thread, do you still feel the same? Is something still fishy or was it variance after all?
Even more fishy. As soon as I started this thread the pool miraculously starts finding blocks again. That is fishy...I wouldn't expect a lucky streak after an unlucky streak, the math just doesn't add up, how would that ever average out!?!? |
|
|
|
Anyone got an answer to this comment?
Maybe you could be more specific. What is your question? Or perhaps it would be better to ask this in the P2Pool thread where more knowledgeable individuals will see it. The bold bit ... Can anyone put whatever they like in the coinbase? I guess that would be yes since you are running your own bitcoind and namecoind? I think the comment was about namecoin mining not being pooled. When you use merged mining with p2pool you get the 50NMC reward block to yourself - I've mined a few NMC blocks already. |
|
|
|
Anyway - the actual point of this is that there should be a set of steps required to add BAMT to BAMT's choice of OS.
So those technically minded do not need to trust someone else's copy of an OS.
Is there already?
I don't know all the technical stuff, but I know it's just a standard Debian live distro that runs a few config files at startup. You really just dd the .img, run the fixer to install current fixes, edit one file, restart the mine service and your mining. Don't get me wrong, I use and recommend your install guide and it's great, but with multiple headless rigs nothing is faster to set up than BAMT. |
|
|
|
|
That is nice ck. Good to see your enjoying that new toy. Any idea how many watts it's drawing for those 694 Mh/s?
|
|
|
|
I remember last summer, I was mining on mineco.in, we waited for one week before solving a block, and receive a measly 0.20 or 0.30 payout.
Witnessed...and it sucked. |
|
|
|
Hello ck!
Apparently the problem with "OFF" decreased but not disappeared completely:
Same here. Ran 18 hrs and got 3 of 4 cards showing OFF with 2.2.3. Started 2.1.2 with the same flags last night, I'll check it in 8 hours. Are you using --auto-fan? Not using auto-fan seemed to solve it in 2.2.1, until my power crashed anyway. |
|
|
|
|
Show Posts
