I have a problem to withdraw from https://moneropool.com/#. Is there anyone who is mining there that had the same problem?
Sometimes they can be late - I had one payment not sent until .63 xmr...
Topic: [XMR] Monero Mining - page 4. (Read 264875 times)
Sometimes they can be late - I had one payment not sent until .63 xmr...
I have a problem to withdraw from https://moneropool.com/#. Is there anyone who is mining there that had the same problem?
This is a detailed guide to setup cloud miners (cpu+gpu) on Amazon EC2. I put together this guide for user oda.krell, who was kind enough to give me a very nice tip for it, so thanks should also go to oda.krell.
OK,
So here goes (assuming you have your ec2 account all set up and linked to credit card, which you can do here: http://aws.amazon.com/ec2/ ):
1) Click on EC2, and then click on Spot Requests under Instances on left sidebar.
2) Click Request Spot Instances blue button near top, and then click Community AMIs and search for XMRminer. Select XMRminer2.
3) For Instance Type, select GPU instances g2.2xlarge, click next and set your maximum price (kind of expensive now, need to do like $0.09 per hour, used to be more like $0.06).
4) Click Review and Launch and then click Launch. At this point you need to setup your ssh keys. I did this a while ago, so I don't remember exact details, but it should be pretty straightforward. Here is a link to Amazon's official tutorial on key pair creation:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html
Let me know if you have issues.
5) Make yourself a cup of tea and wait 30-120 seconds while your instance is prepared.
6) You'll need to ssh into your instance. On Linux you just put your ssh keys in ~/.ssh and set permissions for 400 (I think), and if you ssh from that folder, that's all you need to do. I think on Windows, using Putty, you need to maybe convert the key to putty's format using an extra putty tool. Let me know if you need additional help with this. Here are Amazon's official links on how to connect if you're having trouble:
ssh/Linux - http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html
Putty/Windows - http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html
More Putty - http://docs.aws.amazon.com/gettingstarted/latest/wah-linux/getting-started-deploy-app-connect.html
7) Click on Instances in the left sidebar, and you should see a g2.2xlarge instance with green circle that says running. Click that and then click Connect at the top, and it should give you your IP address to connect to with some instructions.
8 ) On Linux your ssh command should look like:
9) Maybe it's more like 180-300 seconds. Drink some tea while waiting.
10) When it prompts you to permanently add key, click "yes".
11) Now, you need to edit cpustart.sh and gpustart.sh in your home directory using either vi or nano, unless you want to mine to my XMR address
It looks like if you want to mine directly to exchange, just replace my XMR address in both files with YourExchangeXMRAddress.YourExchangePaymentID.
12) You need to run two commands, one to make gpuminer work, and other to make cpuminer much faster:
That's it. You can disconnect and both miners should be hashing away. You can ssh back in and run
If you want to launch a shitload of instances, then obviously you want to automate this process and not do it manually every time. In this case, you need to make sure you edit the files so that they have your XMR address and not mine, and create the start.sh script in home directory, then edit the rc.local file by doing:
Now, go back to your EC2 console, right-click on the g2.2xlarge instance in your Instances window, and select Create Image. This will sever your connection and cause a reboot, but you will now have your own image/AMI that you can launch 10s or 100s or 1000s of, just by entering however many instances you want when filling out your spot request form.
I just tried the rc.local thing, and it seems to auto-launch ccminer and minerd
If you would like to send me some coins for tip, here is btc:
Let me know if you have any questions or anything. And if you want to repost anywhere, I don't mind. Good luck
OK,
So here goes (assuming you have your ec2 account all set up and linked to credit card, which you can do here: http://aws.amazon.com/ec2/ ):
1) Click on EC2, and then click on Spot Requests under Instances on left sidebar.
2) Click Request Spot Instances blue button near top, and then click Community AMIs and search for XMRminer. Select XMRminer2.
3) For Instance Type, select GPU instances g2.2xlarge, click next and set your maximum price (kind of expensive now, need to do like $0.09 per hour, used to be more like $0.06).
4) Click Review and Launch and then click Launch. At this point you need to setup your ssh keys. I did this a while ago, so I don't remember exact details, but it should be pretty straightforward. Here is a link to Amazon's official tutorial on key pair creation:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html
Let me know if you have issues.
5) Make yourself a cup of tea and wait 30-120 seconds while your instance is prepared.
6) You'll need to ssh into your instance. On Linux you just put your ssh keys in ~/.ssh and set permissions for 400 (I think), and if you ssh from that folder, that's all you need to do. I think on Windows, using Putty, you need to maybe convert the key to putty's format using an extra putty tool. Let me know if you need additional help with this. Here are Amazon's official links on how to connect if you're having trouble:
ssh/Linux - http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html
Putty/Windows - http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html
More Putty - http://docs.aws.amazon.com/gettingstarted/latest/wah-linux/getting-started-deploy-app-connect.html
7) Click on Instances in the left sidebar, and you should see a g2.2xlarge instance with green circle that says running. Click that and then click Connect at the top, and it should give you your IP address to connect to with some instructions.
8 ) On Linux your ssh command should look like:
Code:
ssh -i aws1.pem [email protected]
Use ubuntu as user not root.9) Maybe it's more like 180-300 seconds. Drink some tea while waiting.
10) When it prompts you to permanently add key, click "yes".
11) Now, you need to edit cpustart.sh and gpustart.sh in your home directory using either vi or nano, unless you want to mine to my XMR address
It looks like if you want to mine directly to exchange, just replace my XMR address in both files with YourExchangeXMRAddress.YourExchangePaymentID.12) You need to run two commands, one to make gpuminer work, and other to make cpuminer much faster:
Code:
sudo ldconfig /usr/local/cuda-5.5/lib64
sudo sysctl -w vm.nr_hugepages=24
13) I just made another script called start.sh to launch both miners at once, and it seems to work. So do:sudo sysctl -w vm.nr_hugepages=24
Code:
touch start.sh
then vi or nano start.sh and add:Code:
#!/bin/bash
screen /home/ubuntu/cpustart.sh
screen /home/ubuntu/gpustart.sh
then:screen /home/ubuntu/cpustart.sh
screen /home/ubuntu/gpustart.sh
Code:
chmod 755 start.sh
and then launch with:Code:
sudo screen ./start.sh
You need the screen so that when you disconnect your ssh session, the miners keep mining.That's it. You can disconnect and both miners should be hashing away. You can ssh back in and run
Code:
ps -A
and you should see minerd and ccminer listed in the processes somewhere near the bottom.If you want to launch a shitload of instances, then obviously you want to automate this process and not do it manually every time. In this case, you need to make sure you edit the files so that they have your XMR address and not mine, and create the start.sh script in home directory, then edit the rc.local file by doing:
Code:
sudo nano /etc/rc.local
and add the following lines:Code:
ldconfig /usr/local/cuda-5.5/lib64
sysctl -w vm.nr_hugepages=24
screen /home/ubuntu/start.sh
This way, as soon as the instance boots up, it should autolaunch the miners. I haven't tried this final automation part (as I don't normally launch a shitload of instances), but I think this should work, and I'm gonna verify it now. sysctl -w vm.nr_hugepages=24
screen /home/ubuntu/start.sh
Now, go back to your EC2 console, right-click on the g2.2xlarge instance in your Instances window, and select Create Image. This will sever your connection and cause a reboot, but you will now have your own image/AMI that you can launch 10s or 100s or 1000s of, just by entering however many instances you want when filling out your spot request form.
I just tried the rc.local thing, and it seems to auto-launch ccminer and minerd
If you would like to send me some coins for tip, here is btc:
Code:
1Gy2BQKMVjvWdRnG3Ktwm2cXdEyL8ZdqvE
and xmr addresses:Code:
49jkaP1xDZrEYaWxtoToPzitbQh6Z7Vv8c3MwtP49wsZhJUR5VojrxcKgb76zT8XRU5AAWHVptx4RgxgLb5fX7iM2vBSKXA
Let me know if you have any questions or anything. And if you want to repost anywhere, I don't mind. Good luck
Hello ;
please what can Add or Edit in : (cpustart.sh and gpustart.sh) ?
Thank's for help ; u'r the best
-
What is the performance of each GPU?
This is a detailed guide to setup cloud miners (cpu+gpu) on Amazon EC2. I put together this guide for user oda.krell, who was kind enough to give me a very nice tip for it, so thanks should also go to oda.krell.
OK,
So here goes (assuming you have your ec2 account all set up and linked to credit card, which you can do here: http://aws.amazon.com/ec2/ ):
1) Click on EC2, and then click on Spot Requests under Instances on left sidebar.
2) Click Request Spot Instances blue button near top, and then click Community AMIs and search for XMRminer. Select XMRminer2.
3) For Instance Type, select GPU instances g2.2xlarge, click next and set your maximum price (kind of expensive now, need to do like $0.09 per hour, used to be more like $0.06).
4) Click Review and Launch and then click Launch. At this point you need to setup your ssh keys. I did this a while ago, so I don't remember exact details, but it should be pretty straightforward. Here is a link to Amazon's official tutorial on key pair creation:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html
Let me know if you have issues.
5) Make yourself a cup of tea and wait 30-120 seconds while your instance is prepared.
6) You'll need to ssh into your instance. On Linux you just put your ssh keys in ~/.ssh and set permissions for 400 (I think), and if you ssh from that folder, that's all you need to do. I think on Windows, using Putty, you need to maybe convert the key to putty's format using an extra putty tool. Let me know if you need additional help with this. Here are Amazon's official links on how to connect if you're having trouble:
ssh/Linux - http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html
Putty/Windows - http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html
More Putty - http://docs.aws.amazon.com/gettingstarted/latest/wah-linux/getting-started-deploy-app-connect.html
7) Click on Instances in the left sidebar, and you should see a g2.2xlarge instance with green circle that says running. Click that and then click Connect at the top, and it should give you your IP address to connect to with some instructions.
8 ) On Linux your ssh command should look like:
9) Maybe it's more like 180-300 seconds. Drink some tea while waiting.
10) When it prompts you to permanently add key, click "yes".
11) Now, you need to edit cpustart.sh and gpustart.sh in your home directory using either vi or nano, unless you want to mine to my XMR address It looks like if you want to mine directly to exchange, just replace my XMR address in both files with YourExchangeXMRAddress.YourExchangePaymentID.
12) You need to run two commands, one to make gpuminer work, and other to make cpuminer much faster:
That's it. You can disconnect and both miners should be hashing away. You can ssh back in and run
If you want to launch a shitload of instances, then obviously you want to automate this process and not do it manually every time. In this case, you need to make sure you edit the files so that they have your XMR address and not mine, and create the start.sh script in home directory, then edit the rc.local file by doing:
Now, go back to your EC2 console, right-click on the g2.2xlarge instance in your Instances window, and select Create Image. This will sever your connection and cause a reboot, but you will now have your own image/AMI that you can launch 10s or 100s or 1000s of, just by entering however many instances you want when filling out your spot request form.
I just tried the rc.local thing, and it seems to auto-launch ccminer and minerd
If you would like to send me some coins for tip, here is btc:
Let me know if you have any questions or anything. And if you want to repost anywhere, I don't mind. Good luck
OK,
So here goes (assuming you have your ec2 account all set up and linked to credit card, which you can do here: http://aws.amazon.com/ec2/ ):
1) Click on EC2, and then click on Spot Requests under Instances on left sidebar.
2) Click Request Spot Instances blue button near top, and then click Community AMIs and search for XMRminer. Select XMRminer2.
3) For Instance Type, select GPU instances g2.2xlarge, click next and set your maximum price (kind of expensive now, need to do like $0.09 per hour, used to be more like $0.06).
4) Click Review and Launch and then click Launch. At this point you need to setup your ssh keys. I did this a while ago, so I don't remember exact details, but it should be pretty straightforward. Here is a link to Amazon's official tutorial on key pair creation:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html
Let me know if you have issues.
5) Make yourself a cup of tea and wait 30-120 seconds while your instance is prepared.
6) You'll need to ssh into your instance. On Linux you just put your ssh keys in ~/.ssh and set permissions for 400 (I think), and if you ssh from that folder, that's all you need to do. I think on Windows, using Putty, you need to maybe convert the key to putty's format using an extra putty tool. Let me know if you need additional help with this. Here are Amazon's official links on how to connect if you're having trouble:
ssh/Linux - http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html
Putty/Windows - http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html
More Putty - http://docs.aws.amazon.com/gettingstarted/latest/wah-linux/getting-started-deploy-app-connect.html
7) Click on Instances in the left sidebar, and you should see a g2.2xlarge instance with green circle that says running. Click that and then click Connect at the top, and it should give you your IP address to connect to with some instructions.
8 ) On Linux your ssh command should look like:
Code:
ssh -i aws1.pem [email protected]
Use ubuntu as user not root.9) Maybe it's more like 180-300 seconds. Drink some tea while waiting.
10) When it prompts you to permanently add key, click "yes".
11) Now, you need to edit cpustart.sh and gpustart.sh in your home directory using either vi or nano, unless you want to mine to my XMR address
It looks like if you want to mine directly to exchange, just replace my XMR address in both files with YourExchangeXMRAddress.YourExchangePaymentID.12) You need to run two commands, one to make gpuminer work, and other to make cpuminer much faster:
Code:
sudo ldconfig /usr/local/cuda-5.5/lib64
sudo sysctl -w vm.nr_hugepages=24
13) I just made another script called start.sh to launch both miners at once, and it seems to work. So do:sudo sysctl -w vm.nr_hugepages=24
Code:
touch start.sh
then vi or nano start.sh and add:Code:
#!/bin/bash
screen /home/ubuntu/cpustart.sh
screen /home/ubuntu/gpustart.sh
then:screen /home/ubuntu/cpustart.sh
screen /home/ubuntu/gpustart.sh
Code:
chmod 755 start.sh
and then launch with:Code:
sudo screen ./start.sh
You need the screen so that when you disconnect your ssh session, the miners keep mining.That's it. You can disconnect and both miners should be hashing away. You can ssh back in and run
Code:
ps -A
and you should see minerd and ccminer listed in the processes somewhere near the bottom.If you want to launch a shitload of instances, then obviously you want to automate this process and not do it manually every time. In this case, you need to make sure you edit the files so that they have your XMR address and not mine, and create the start.sh script in home directory, then edit the rc.local file by doing:
Code:
sudo nano /etc/rc.local
and add the following lines:Code:
ldconfig /usr/local/cuda-5.5/lib64
sysctl -w vm.nr_hugepages=24
screen /home/ubuntu/start.sh
This way, as soon as the instance boots up, it should autolaunch the miners. I haven't tried this final automation part (as I don't normally launch a shitload of instances), but I think this should work, and I'm gonna verify it now. sysctl -w vm.nr_hugepages=24
screen /home/ubuntu/start.sh
Now, go back to your EC2 console, right-click on the g2.2xlarge instance in your Instances window, and select Create Image. This will sever your connection and cause a reboot, but you will now have your own image/AMI that you can launch 10s or 100s or 1000s of, just by entering however many instances you want when filling out your spot request form.
I just tried the rc.local thing, and it seems to auto-launch ccminer and minerd
If you would like to send me some coins for tip, here is btc:
Code:
1Gy2BQKMVjvWdRnG3Ktwm2cXdEyL8ZdqvE
and xmr addresses:Code:
49jkaP1xDZrEYaWxtoToPzitbQh6Z7Vv8c3MwtP49wsZhJUR5VojrxcKgb76zT8XRU5AAWHVptx4RgxgLb5fX7iM2vBSKXA
Let me know if you have any questions or anything. And if you want to repost anywhere, I don't mind. Good luck
Hello ;
please what can Add or Edit in : (cpustart.sh and gpustart.sh) ?
Thank's for help ; u'r the best
-
Is the reward for block is changing? if so, when will happen?
Regards Nathalie20
Regards Nathalie20
It happens all the time.
when it is next?
in about 2 minutes.
there is no halving or similar. reward declines steadily with each block
interesting solution.
too little time to follow the development of all coins.
Regards
Is the reward for block is changing? if so, when will happen?
Regards Nathalie20
Regards Nathalie20
It happens all the time.
when it is next?
in about 2 minutes.
there is no halving or similar. reward declines steadily with each block
Is the reward for block is changing? if so, when will happen?
Regards Nathalie20
Regards Nathalie20
It happens all the time.
when it is next?
Is the reward for block is changing? if so, when will happen?
Regards Nathalie20
Regards Nathalie20
It happens all the time.
Is the reward for block is changing? if so, when will happen?
Regards Nathalie20
Regards Nathalie20
Hey all,
Has anyone tested the p2.8xlarge or p2.16 series from amazon? I know returns aren't likely to be had, but wondering what type of hashing power these produce.
Thanks!
Has anyone tested the p2.8xlarge or p2.16 series from amazon? I know returns aren't likely to be had, but wondering what type of hashing power these produce.
Thanks!
p2.8xlarge
CPU (xmr stak cpu 22 threads...46MB of L3 cache)
840 h/s
GPU
1.9KH/s
so total of 2.740KH/s
less than my previous estimate due to the fact i thought there was a higher L# cache on the p2 instance cpus...there isnt , so cpu performance is similar
p2.16xlarge would be twice that at 5.5KH/s
per cpu/gpu core the performance is almost identical to the g2 instances...(ie grid k520 is just as fast if not faster than a k80 when it comes to cryptonight)
a g2.8xlarge with 32vcpus and 4 grid k520s does 800 or so cpu and 1k GPU (from 4 gpu cores)..
Thank you! Exactly the information I was looking for!
Hey all,
Has anyone tested the p2.8xlarge or p2.16 series from amazon? I know returns aren't likely to be had, but wondering what type of hashing power these produce.
Thanks!
Has anyone tested the p2.8xlarge or p2.16 series from amazon? I know returns aren't likely to be had, but wondering what type of hashing power these produce.
Thanks!
p2.8xlarge
CPU (xmr stak cpu 22 threads...46MB of L3 cache)
840 h/s
GPU
1.9KH/s
so total of 2.740KH/s
less than my previous estimate due to the fact i thought there was a higher L# cache on the p2 instance cpus...there isnt , so cpu performance is similar
p2.16xlarge would be twice that at 5.5KH/s
per cpu/gpu core the performance is almost identical to the g2 instances...(ie grid k520 is just as fast if not faster than a k80 when it comes to cryptonight)
a g2.8xlarge with 32vcpus and 4 grid k520s does 800 or so cpu and 1k GPU (from 4 gpu cores)..
I've only tested g2.8xlarge which gives a combined cpu +gpu of 1.8k or so
I'm guessing the p2.8xlarge would be somewhere near the 3-3.5k mark and p2.16xlarge twice that.
I'll check if there's a preexisting AMI with CUDA set up to launch a spot instance and run a benchmark....(if there isn't I can't be bothered to set it up from scratch ...sorry )
I'm guessing the p2.8xlarge would be somewhere near the 3-3.5k mark and p2.16xlarge twice that.
I'll check if there's a preexisting AMI with CUDA set up to launch a spot instance and run a benchmark....(if there isn't I can't be bothered to set it up from scratch ...sorry
)
Hey all,
Has anyone tested the p2.8xlarge or p2.16 series from amazon? I know returns aren't likely to be had, but wondering what type of hashing power these produce.
Thanks!
Has anyone tested the p2.8xlarge or p2.16 series from amazon? I know returns aren't likely to be had, but wondering what type of hashing power these produce.
Thanks!
Hi,
Just a reminder about xmrpool.eu :-).
My pool has been online for couple of months with no major downtimes. Also a lot of changes has been made on the pool.
Currently pool software is deployed on stable dedicated server with SSD disk.
List of important features:
Pool has steady hashrate and thanks to PPLNS it's pool hoppers proof :-).
If you have any question you can talk to me on irc (freenode.net) on #monero-pools or msg me on this forum or email me.
All miners welcome on xmrpool.eu
Just a reminder about xmrpool.eu :-).
My pool has been online for couple of months with no major downtimes. Also a lot of changes has been made on the pool.
Currently pool software is deployed on stable dedicated server with SSD disk.
List of important features:
- Fee: 0.5%
- PPLNS payment method
- Mining to exchange (with paymentid)
- Workers statistics - you can register each rig separately
- Fixed diff - you can set fixed difficulty for miner
- SSL support on port 9999 for GPU Claymore 9.7 (lower fee while mining on SSL port)
Pool has steady hashrate and thanks to PPLNS it's pool hoppers proof :-).
If you have any question you can talk to me on irc (freenode.net) on #monero-pools or msg me on this forum or email me.
All miners welcome on xmrpool.eu
I've added payment id payouts to https://xmr.suprnova.cc now as well. They're tested and confirmed working. You can now be paid with integrated addresses, normal addresses and also payment ids.
Us and EU nodes, pplns payment etc..
Let me know if you need anything else
Us and EU nodes, pplns payment etc..
Let me know if you need anything else
Long time lurker here... using my first post to say you've done an excellent job
We BetByBitcoin happy to announce our first Monero Mining Pool
>>> Join Monero Mining Pool http://monero.sparkpool.org/ <<<
We will soon doing promotion offer so stay tune and check our post
I will point some gear at it.
Thanks ..hope we can find first block
Fellow monero miners, please help!
I'm building a 6 x MSI rx480 4gb(stock bios) mining rig. Using Biostar TB85 Mobo with windows 7x64.
I installed the latest updates and AMD drivers, but I have an issue where only 4 of 6 vide cards are recognized by the system.
The other two report error 43 device manager.
I have tried moving the cables around, always the same 2 cards in the device manager. Card 3 and card 5. This makes me believe that cards and risers are not an issue, but it is either os/driver or the mobo.
I have the same mobo running 6 GTX1070 with no issues...
Any insight would be very appreciated.
If you don't know what my issue is, but know what motherboard works, please let me know.
I'm building a 6 x MSI rx480 4gb(stock bios) mining rig. Using Biostar TB85 Mobo with windows 7x64.
I installed the latest updates and AMD drivers, but I have an issue where only 4 of 6 vide cards are recognized by the system.
The other two report error 43 device manager.
I have tried moving the cables around, always the same 2 cards in the device manager. Card 3 and card 5. This makes me believe that cards and risers are not an issue, but it is either os/driver or the mobo.
I have the same mobo running 6 GTX1070 with no issues...
Any insight would be very appreciated.
If you don't know what my issue is, but know what motherboard works, please let me know.
We BetByBitcoin happy to announce our first Monero Mining Pool
>>> Join Monero Mining Pool http://monero.sparkpool.org/ <<<
We will soon doing promotion offer so stay tune and check our post
I will point some gear at it.
Thanks ..hope we can find first block
We BetByBitcoin happy to announce our first Monero Mining Pool
>>> Join Monero Mining Pool http://monero.sparkpool.org/ <<<
We will soon doing promotion offer so stay tune and check our post
I will point some gear at it.
We BetByBitcoin happy to announce our first Monero Mining Pool
>>> Join Monero Mining Pool http://monero.sparkpool.org/ <<<
We will soon doing promotion offer so stay tune and check our post
Jump to: