Search content
Sort by

Showing 11 of 11 results by Daelus
Post
Topic
Board Beginners & Help
Re: Want to make my first GPU rig! Where to start?
by
Daelus
on 16/04/2013, 22:24:49 UTC
Well that's exactly what ASICs are going to do. They are going to atleast (Probably) double the difficulty of mining BitCoins. The problem with this is going to be that unless you have an ASIC or a computer that can mine at least 1GH/s then you're not going to want to mine anymore because the difficulty is so high. This will ultimately cause the difficulty to drop back down. Eventually we will reach a point that's about 145-160% the difficulty now with the release of ASIC Miners.

To answer the question if these GPU miners are becoming obsolete, For the most part yet, for BitCoins at least, a computer that pulls under 1GH/s is not going to make much in the lines of mining and the electricity cost is going to probably be more than your return will be.

LiteCoins are the future of GPU Miners.
BitCoins are the future of ASIC Miners.
Post
Topic
Board Beginners & Help
Re: Want to make my first GPU rig! Where to start?
by
Daelus
on 16/04/2013, 00:56:38 UTC
If you're really that serious about starting up a mining rig for BTC then I suggest getting on the long waiting list for an ASIC
You can get a 5.0 Gh/s ASIC from butterfly labs for $274. However, these machines serve only a single purpose, cannot be upgraded by any means, and it will take up to 3 months for you to receive one.

Hope all this helps!

Good luck!
Post
Topic
Board Beginners & Help
Re: Want to make my first GPU rig! Where to start?
by
Daelus
on 16/04/2013, 00:52:08 UTC
One ATI 5830, Approximately 245 Mhash/s

Power Supply    Rosewill Green Series RG530-S12 530W, 80 PLUS Certified   NewEgg    $50
Motherboard    Foxconn M61PMP-K AMD                                           NewEgg    $45
CPU                    AMD Sempron 145                                                   NewEgg    $39
Memory            2GB DDR3                                                                   NewEgg    $13
Graphics card    Radeon HD 5830                                                           NewEgg ($153)    $110
Storage            Western Digital Caviar 80GB                                           NewEgg    $17

Total    (Approx: $1.1755 /Mhash)       $285 + s/h/t

However as ASICS are about to ship out the doors and double the difficulty, GPU mining rigs are about to go the way of CPU miners and be obsolete!

But there is still hope! ASIC miners cannot mine LiteCoins (For Now) and this set up will work for LiteCoins with similar results.
Post
Topic
Board Beginners & Help
Re: Linux Mining hash rate
by
Daelus
on 15/04/2013, 17:42:48 UTC
What hash rate could I expect with 48 Intel Xeon, 2.8 GHz processors EM64 on 24 nodes?
CPU mining is EXTREMELY inefficient with today's GPU miners. I wouldn't recommend this setup as you may not see it peak above 1Mh/s
Post
Topic
Board Beginners & Help
Re: Newbie Mining Setups (And various Issues)
by
Daelus
on 15/04/2013, 17:17:01 UTC
I should also tell you that ASICs are starting to be developed and GPU mining is soon to be obsolete for bitcoin mining. The difficulty will nearly doubly which will effectively push out any low level machine that is getting under 100Mh/s

At this point it is too late in the market to seriously get into bit coin mining unless you want to spend the money on an ASIC

However, there is an alternative!

LTC, LiteCoins are another currency which can be mined by GPUs but NOT ASICs, atleast the ASICS that are about to be shipped out the door from places like Butterfly labs.

Hope this all helps.
Post
Topic
Board Beginners & Help
Re: Newbie Mining Setups (And various Issues)
by
Daelus
on 15/04/2013, 17:12:18 UTC
I'm also new to mining and all that jargon have me confused.

Nevertheless to say, I am using an HP Pavilion DV73186CL Notebook being this as the client computer. CPU/GPU/RAM and whatsoever are all stock.

I don't keep it on 24/7 due to overheating concerns

Well there isn't much you can do in the line of modifications to a Notebook for Bitcoin Mining. With that sort of set up you are stuck at what you are currently getting.

If you are serious about mining and are wanting a return you should check out the listings that are kept on https://en.bitcoin.it/wiki/Mining_rig they hold cost and effectiveness breakdowns on machines. The best bet for mining bitcoins seriously is building a desktop from the ground up with the specifications listed there.

Best of luck!
Post
Topic
Board Beginners & Help
Re: Newbie Mining Setups (And various Issues)
by
Daelus
on 15/04/2013, 17:00:57 UTC
Is there anyway he can use both his gpu's they show up on the list 0-1, 0-0. Idk if you can only use one at a time or not.
also what about the check boxes for the cpu? is mining to difficult for the cpu to be worth anything anymore?
The CPU Affinity refers to how many cores were being dedicated to mining. CPU mining has become pretty much obsolete now that the difficulty is so high. GPU mining has completely done away with CPU mining. You can use more than one card if you crossfire them, however I don't think you can use a PCI-E card with an Integrated card.
However, if your cards are properly cooled, IE hovering around 60 degrees celsius and they are used solely for mining, so you're not trying to run BF3 on Ultra then you might want to overclock your cards. I advise you though you should monitor your heat output if you start to do this. While it will turn up your Mh/s if your temp rises above 80 degress Celsius damage can be done to your card.

EDIT: For instructions on Overclocking your card see " http://www.ehow.com/how_7450187_overclock-nvidia-quadro-nvs.html "
Post
Topic
Board Beginners & Help
Re: Newbie Mining Setups (And various Issues)
by
Daelus
on 15/04/2013, 16:50:31 UTC
My roommate and I recently started mining bitcoins through slush's pool, neither of us have any clue really what we are doing but are really eager to learn.

I'm running a core2duo and nvidia quadro 600 and run at about 16.4Mh/s
My roommate however is running an Intel 6 core and integrated amd and nvidia quadro 600.

Now the issue is he pulls the exact same Mh/s rate that I do, but there is no way my computing power should be able to keep up with his,
my pc is atleast 5 years older.

Any help would greatly be appreciated also I will continue to search for an answer to this question on the forums!
You're bothing mining with the same GPU, and 17 Mh/s is the average rate for a standard clock Nvidia Quadro 600. CPU chipset doesn't really matter if you aren't using it for mining.
Basically,
Same GPU +
Same Power +
Same Clock +
= Same Mh/s
Post
Topic
Board Beginners & Help
Re: PushpoolD
by
Daelus
on 15/04/2013, 16:37:22 UTC
The error continuously loops with only the ID going up each time. The error logs stay the same.
Post
Topic
Board Beginners & Help
Topic OP
PushpoolD
by
Daelus
on 15/04/2013, 00:21:21 UTC
PushpoolD seems to be running fine and i'm getting the initialized, miners from GUIminer can connect and they start to mine however shortly after a loop of errors start which look like this.

Code:
[2013-04-15 02:05:11.543893] Debug output enabled
[2013-04-15 02:05:11.544628] Forcing local hostname to localhost.localdomain
[2013-04-15 02:05:11.642582] Listening on host :: port 8342
[2013-04-15 02:05:11.642707] Listening on host :: port 8341
[2013-04-15 02:05:11.642794] Listening on host :: port 8332
[2013-04-15 02:05:11.642842] Listening on host 127.0.0.1 port 8338
[2013-04-15 02:05:11.676607] initialized
JSON protocol request:
{"method": "getwork", "params": [], "id":1}

* About to connect() to 127.0.0.1 port 8335 (#0)
*   Trying 127.0.0.1...
* TCP_NODELAY set
* connected
* Connected to 127.0.0.1 (127.0.0.1) port 8335 (#0)
* Server auth using Basic with user 'Daelus'
> POST / HTTP/1.1
Authorization: Basic RGFlbHVzOjU3NzQ=
Host: 127.0.0.1:8335
Accept: */*
Accept-Encoding: deflate, gzip
Content-type: application/json
Content-Length: 45

* additional stuff not fine transfer.c:1037: 0 0
* additional stuff not fine transfer.c:1037: 0 0
* HTTP 1.1 or later with persistent connection, pipelining supported
< HTTP/1.1 200 OK
< Date: Mon, 15 Apr 2013 02:05:22 +0000
< Connection: keep-alive
< Content-Length: 592
< Content-Type: application/json
< Server: bitcoin-json-rpc/v0.8.1-beta
<
* Connection #0 to host 127.0.0.1 left intact
JSON protocol response:
{
   "error": null,
   "result": {
      "target": "0000000000000000000000000000000000000000000000be2f02000000000000",
      "midstate": "b6dc6b123ab080dc451e5fb9b1597cc7b44ae3d58be58818de00d99996d93cf3",
      "hash1": "00000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000010000",
      "data": "0000000238268a767cdcd48c910b0a233ec0fb1a6cbd9727a55f01bb0000020900000000d7832a1659ce8964e1e01b261ccf4a57286dcbc8bf447857732fe0b89b1744d2516b60611a022fbe00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000"
   },
   "id": 1
}

Also, here is my Server.Json file
Code:
{
# network ports
"listen" : [
# binary protocol (default), port 8336
{ "port" : 8342 },

# HTTP JSON-RPC protocol, port 8337
{ "port" : 8341, "protocol" : "http-json" },

# HTTP JSON-RPC protocol, port 8339,
# with trusted proxy appserver.example.com forwarding
# requests to us
{ "port" : 8332, "protocol" : "http-json",
  "proxy" : "192.168.1.135" },

# binary protocol, localhost-only port 8338
{ "host" : "127.0.0.1", "port" : 8338, "protocol" : "binary" }
],

# database settings
"database" : {
"engine" : "mysql",

# 'host' defaults to localhost, if not specified
"host" : "127.0.0.1",

# 'port' uses proper default port for the DB engine,
# if not specified
"port" : 3306,

"name" : "miningfarm",
"username" : "root",
"password" : "5774",

"stmt.pwdb" :
  "SELECT password FROM pool_worker WHERE username = ?"
},

# cache settings
"memcached" : {
"servers" : [
{ "host" : "127.0.0.1", "port" : 11211 }
]
},

"pid" : "/tmp/pushpoold.pid",

# overrides local hostname detection
"forcehost" : "localhost.localdomain",

"log.requests" : "/tmp/request.log",
"log.shares" : "/tmp/shares.log",

# the server assumes longpolling (w/ SIGUSR1 called for each blk)
"longpoll.disable" : false,

# length of time to cache username/password credentials, in seconds
"auth.cred_cache.expire" : 75,

# RPC settings
"rpc.url" : "http://127.0.0.1:8335/",
"rpc.user" : "Daelus",
"rpc.pass" : "5774",

# rewrite returned 'target' to given number of zero bits, 32 equals difficulty-1
"rpc.target.bits" : 32,

# how long before work expires?
"work.expire" : 120,

# allow clients to update the ntime field of their work
"roll.ntime.disable" : false
}
Post
Topic
Board Beginners & Help
Topic OP
PushPoolD
by
Daelus
on 15/04/2013, 00:05:47 UTC
Hi guys,

I am having issues when starting pushpoold, pushpoold will only connect to bitcoind when the rpc port is set at 8335, however when I set it to 8335 in my server.json Pushpoold won't initialize and doesn't report any errors with ./pushpoold -E -F -D2

Server.Json
Code:
{
# network ports
"listen" : [
# binary protocol (default), port 8342
{ "port" : 8342 },

# HTTP JSON-RPC protocol, port 8341
{ "port" : 8341, "protocol" : "http-json" },

# HTTP JSON-RPC protocol, port 8344,
# with trusted proxy appserver.example.com forwarding
# requests to us
{ "port" : 8332, "protocol" : "http-json",
  "proxy" : "xxx.xxx.x.xxx" },

# binary protocol, localhost-only port 8338
{ "host" : "127.0.0.1", "port" : 8338, "protocol" : "binary" }
],

# database settings
"database" : {
"engine" : "mysql",
"host" : "127.0.0.1",
"port" : 3306,
"name" : "miningfarm",
"username" : "xxxx",
"password" : "xxxx",
"sharelog" : true,
"stmt.pwdb":"SELECT `password` FROM `pool_worker` WHERE `username` = ?",
"stmt.sharelog":"INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, solution, time) VALUES (?, ?, ?, ?, ?, ?, UNIX_TIMESTAMP())"

},

# cache settings
#"memcached" : {
# "servers" : [
# { "host" : "127.0.0.1", "port" : 11211 }
# ]
#},

#"pid" : "/tmp/pushpoold.pid",

# overrides local hostname detection
"forcehost" : "localhost.localdomain",

"log.requests" : "/tmp/request.log",
"log.shares" : "/tmp/shares.log",

# the server assumes longpolling (w/ SIGUSR1 called for each blk)
"longpoll.disable" : false,

# length of time to cache username/password credentials, in seconds
"auth.cred_cache.expire" : 75,

# RPC settings | Notice how this ISN'T port number 8332 this is becuase the same port number should not becuase inconjunction with the JSON RPC port other wise you'll get 500 errors
"rpc.url" : "http://xxx.xxx.x.xxx:8335/",
"rpc.user" : "Username",
"rpc.pass" : "5774",

# rewrite returned 'target' to difficulty-1?
"rpc.target.rewrite" : true
}

blkmond.conf
Code:
host=XXX.XXX.X.XXX
port=8335
pid=tmp/pushpoold.pid

bitcoin.conf
Code:
server=0
rpcuser=username
rpcpassword=password
rpcport=8335
rpcconnect=http://xxx.xxx.x.xxx/