A little personal history:
I am an IT guy who works with many trades, I am not fluent in coding java, cobalt, etc. but when someone is stuck I can figure out something complicated to get over the development hump.
So I mine, I play with code, I do a…
since I updated Geth 1.3.5 & Ethereum 1.2.1 to homestead release. Now 4 days, No blocks, No Uncles, No luck..
geth attach and
web3.net listening with 25 peercount.
miner.hashrate shows its 97MH/s hashing..
Maybe some of this can be balanced out..
Maybe an algorithm/Contract based POS system could be used to see if anyone mining from one IP/node number with greater than XXX hash-power has greater difficulty than someone mining with below xx hash-powe…
I updated Geth 1.3.5 & Ethereum 1.2.1 to homestead release.
when running my 2 rigs to my one Geth --rpc instance,
I noticed in geth --rpc that there was something strange @ importing block, 1101411 and block 1101412..there is block 1101411 imp…
this is ether-proxy and not eth-proxy,
not what I am looking for now, but cool-Maybee later..
Proxy feature list:
Rigs availability monitoring
Keep track of accepts, rejects, blocks stats
Easy detection of sick rigs
Daemon failover list
right now I am stuck with eth-proxy not starting, error connecting/finding geth --rpc instance.
Starting eth-proxy.exe I get error saying:
*"trying to connect to stratum pool at 127.0.0.1:8545
*"trying to connect to failover stratum pool…
I haven't mined a thing in 4 days, my Geth instance was stuck and couldn't shut it down 2 days ago I had to ctrl C panic to get out..
And now I am at my 2 day mark, just waiting again..
I am not woried about overhead, I have 32gb of ECC/chipkill …
sorry for stepping on that other forum thread.
I did learn that I don't need the *256
originally first posted above: Mining Rig1 = IP 192.168.1.101 GPU=R9290x2
ethminer –G –F http://192.168.1.100:8545 –opencl –cl-local-work 256 –cl-global…
sorry if I scarred/frustrated you on temps and missed some of your posts...
for some reason if I hit 90° my system shuts down, and I tried the card on 2 separate rigs/motherboards. probably my card.. Yes-server room :-)
so I have been playing with…
@dlehenky After deleting the DAG and restarting ethminer there are now 2 DAGs on each rig.
No, I an not using --no-precompute.
All appears fine now, I will run the rigs for a couple days to see if I get a block..
Note: as the rigs finished generate…
wow that's a lot to take in, I will need to think about your reply..
I wish I new where that Dangling hash node ref# in geth --rpc came from.
1. is there a DAG needed on the --rpc vm with no mining going on or just on the miners?
2. can I just dele…
It seems that one DAG is created on each local rig located in C:\Users\MSFT-SucMe\AppData\Ethash diectory.
Is a need or a way to verify the DAG integrity?
or do I have to wait for a found block or uncle to see an error like, Dangling hash node ref#…
Da, I feel like a homer-Do darn noob..
I just noticed that Ethereum network is currently at block "1079421" and growing.
so I think that means it has not created block 1080000 yet, it must be coming, and maybe that means that is when homestead …
me TOOo.. DAG file changed in block 1080000
I use eth-proxy / Stratum proxy v0.0.4
It looks like it could be a global change/prob on dwarfpool because I see it on the main eth page, http://dwarfpool.com/eth
I was going to post in dwarfpool and I …
you should really open your case, you are going to cook your 7990.
85 is borderline toast.
I have a [email protected] 42 to 45mh+-
ethminer -G --opencl --cl-local-work 256 --cl-global-work 8192*128 -t 2
should be smooth as silk..