Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 486. (Read 6590565 times)
January 08, 2018, 06:13:59 PM
anyone see problem running 6 rx480 and dual mining ETH and MUSIC ?
January 08, 2018, 06:02:20 PM
Ok. So i have setup claymore miner in Xubuntu 16.4.3 and this program run's a reboot.sh script if something goes wrong. My problem is that the script does not execute the first time after a startup of the system.
I get these errors.
Failed to set wall message, ignoring: Interactive authentication required.
Failed to reboot system via logind: Interactive authentication required.
Failed to start reboot.target: Interactive authentication required.
See system logs and 'systemctl status reboot.target' for details.
Failed to open /dev/initctl: Permission denied
Failed to talk to init daemon."
If i restart claymore miner and he needs to run the reboot.sh second time the system will restart.
Please help.
I get these errors.
Failed to set wall message, ignoring: Interactive authentication required.
Failed to reboot system via logind: Interactive authentication required.
Failed to start reboot.target: Interactive authentication required.
See system logs and 'systemctl status reboot.target' for details.
Failed to open /dev/initctl: Permission denied
Failed to talk to init daemon."
If i restart claymore miner and he needs to run the reboot.sh second time the system will restart.
Please help.
January 08, 2018, 05:26:13 PM
Quote
Temperature control thread hangs, need to restart miner!
SC: 01/09/18-00:18:18 - New job from hub.miningpoolhub.com:20550
SC: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s
Quit, please wait...
Setting DAG epoch #58 for GPU1
Create GPU buffer for GPU1
GPU1 DAG creation time - 5391 ms
Setting DAG epoch #58 for GPU1 done
Restarting OK, exit...
SC: 01/09/18-00:18:18 - New job from hub.miningpoolhub.com:20550
SC: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s
Quit, please wait...
Setting DAG epoch #58 for GPU1
Create GPU buffer for GPU1
GPU1 DAG creation time - 5391 ms
Setting DAG epoch #58 for GPU1 done
Restarting OK, exit...
I got this very often. -ttly option does not work.
Windows 7 sp1 x64, miner 10.3
Recent drivers for two cards Nvidia GTX 970 and Radeon R7 260
January 08, 2018, 12:50:48 PM
Yeah, probably, but next time they will mine since I attached a simple mining server to claymore's default ports!! Please hack me and make me rich!!
January 08, 2018, 12:45:47 PM
I had the ports open from my second router, to monitor the rigs while I was adding a new router with 4G support for redundancy, and was still configuring ports for my Personal VPN through the mobile network, when the alarm set of.
I had different attacks from China and Russia over the last week, but today was directly to the mining port, scanning and trying to reboot. Thankfully I am on a simple dynamic IP setup so I can easy change IP with a simple restart.
I had different attacks from China and Russia over the last week, but today was directly to the mining port, scanning and trying to reboot. Thankfully I am on a simple dynamic IP setup so I can easy change IP with a simple restart.
Ah, you were shodan'ed...
January 08, 2018, 12:21:29 PM
Performance is about the same, but the AMD blockchain drivers have an 8 card limit. The Crimson Relive 17.11.x and Adrenalin 17.12.x drivers let you run at least 13 cards and are compatible with the Windows 10 v1709 fall creators update.
How do you get the new drivers to have equal performance to the blockchain one? Even with compute the performance loss is there. 28MH/s to 26.5MH/s for example.
January 08, 2018, 11:54:49 AM
I had the ports open from my second router, to monitor the rigs while I was adding a new router with 4G support for redundancy, and was still configuring ports for my Personal VPN through the mobile network, when the alarm set of.
I had different attacks from China and Russia over the last week, but today was directly to the mining port, scanning and trying to reboot. Thankfully I am on a simple dynamic IP setup so I can easy change IP with a simple restart.
I had different attacks from China and Russia over the last week, but today was directly to the mining port, scanning and trying to reboot. Thankfully I am on a simple dynamic IP setup so I can easy change IP with a simple restart.
January 08, 2018, 11:50:04 AM
I just had a reboot attempt from http://211.57.159.226 from Korea.
Be very careful with your remote ports and be sure to only be read only, or protect you mining machines with a prety strong password. This http://211.57.159.226 bitch tried to reboot the machine several times. It was pretty easy though to spot him and plant a simple surprise, so he wont be trying that stuff to me anytime soon.
Be very careful with your remote ports and be sure to only be read only, or protect you mining machines with a prety strong password. This http://211.57.159.226 bitch tried to reboot the machine several times. It was pretty easy though to spot him and plant a simple surprise, so he wont be trying that stuff to me anytime soon.
Why in the hell would you leave this open to the internet? Putting this behind a simple VPN or at worst a firewall with restrictive ACL's is simple, and all but free.
I didn't enable this port - or any other remote monitoring port, actually - in the first place. So for Claymore to warn that it couldn't access that port was understandably worrisome. I'm not mining an Ethash coin right now, but explicitly adding "-mport 0" to the command line and restarting seemed to take care of the problem.
January 08, 2018, 11:40:01 AM
I just had a reboot attempt from http://211.57.159.226 from Korea.
Be very careful with your remote ports and be sure to only be read only, or protect you mining machines with a prety strong password. This http://211.57.159.226 bitch tried to reboot the machine several times. It was pretty easy though to spot him and plant a simple surprise, so he wont be trying that stuff to me anytime soon.
Be very careful with your remote ports and be sure to only be read only, or protect you mining machines with a prety strong password. This http://211.57.159.226 bitch tried to reboot the machine several times. It was pretty easy though to spot him and plant a simple surprise, so he wont be trying that stuff to me anytime soon.
Why in the hell would you leave this open to the internet? Putting this behind a simple VPN or at worst a firewall with restrictive ACL's is simple, and all but free.
January 08, 2018, 10:43:41 AM
I just had a reboot attempt from http://211.57.159.226 from Korea.
Be very careful with your remote ports and be sure to only be read only, or protect you mining machines with a prety strong password. This http://211.57.159.226 bitch tried to reboot the machine several times. It was pretty easy though to spot him and plant a simple surprise, so he wont be trying that stuff to me anytime soon.
Be very careful with your remote ports and be sure to only be read only, or protect you mining machines with a prety strong password. This http://211.57.159.226 bitch tried to reboot the machine several times. It was pretty easy though to spot him and plant a simple surprise, so he wont be trying that stuff to me anytime soon.
Interesting; I wonder if this is what was happening to me earlier with Claymore reporting that mport 10048 wasn't available?
January 08, 2018, 10:14:28 AM
I just had a reboot attempt from http://211.57.159.226 from Korea.
Be very careful with your remote ports and be sure to only be read only, or protect you mining machines with a prety strong password. This http://211.57.159.226 bitch tried to reboot the machine several times. It was pretty easy though to spot him and plant a simple surprise, so he wont be trying that stuff to me anytime soon.
Be very careful with your remote ports and be sure to only be read only, or protect you mining machines with a prety strong password. This http://211.57.159.226 bitch tried to reboot the machine several times. It was pretty easy though to spot him and plant a simple surprise, so he wont be trying that stuff to me anytime soon.
January 08, 2018, 08:37:15 AM
After total shares 2265 press 's' -
ETH: Connection lost, retry in 20 sec...
After press 'r'
after that's :
TH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
And it minning again. This is not first time. Where is problem ?
ETH: Connection lost, retry in 20 sec...
After press 'r'
after that's :
TH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
ETH: Received error: {"jsonrpc":"2.0","id":4,"error":{"code":-32700,"message":"Worknotfound"}}
And it minning again. This is not first time. Where is problem ?
This looks like an connection error; ie. the miner can't connect to the pool.
Some strange : after press 's'
Miner thread hangs, need to restart miner!
Where can be problem ?
January 08, 2018, 08:01:11 AM
Performance is about the same, but the AMD blockchain drivers have an 8 card limit. The Crimson Relive 17.11.x and Adrenalin 17.12.x drivers let you run at least 13 cards and are compatible with the Windows 10 v1709 fall creators update.
Maybe you can tell : Adrenalin 17.12.x can handle 14 cards under windows ?Many people report the motherboards won't POST with 14 or more GPU's. I believe 13 AMD cards is the limit under Windows. My ASRock H110 Pro BTC+ works fine with 13 RX 580 under Windows v1709 with the 17.12.2 drivers.
https://bitcointalksearch.org/topic/m.27496480
The Asus B250 mining expert motherboard requires Nvidia P106 mining cards to even POST with more than 13 cards. Otherwise 13 cards is the max.
January 08, 2018, 07:39:16 AM
Performance is about the same, but the AMD blockchain drivers have an 8 card limit. The Crimson Relive 17.11.x and Adrenalin 17.12.x drivers let you run at least 13 cards and are compatible with the Windows 10 v1709 fall creators update.
Maybe you can tell : Adrenalin 17.12.x can handle 14 cards under windows ?Many people report the motherboards won't POST with 14 or more GPU's. I believe 13 AMD cards is the limit under Windows. My ASRock H110 Pro BTC+ works fine with 13 RX 580 under Windows v1709 with the 17.12.2 drivers.
https://bitcointalksearch.org/topic/m.27496480
The Asus B250 mining expert motherboard requires Nvidia P106 mining cards to even POST with more than 13 cards. Otherwise 13 cards is the max.
January 08, 2018, 07:36:20 AM
Performance is about the same, but the AMD blockchain drivers have an 8 card limit. The Crimson Relive 17.11.x and Adrenalin 17.12.x drivers let you run at least 13 cards and are compatible with the Windows 10 v1709 fall creators update.
Maybe you can tell : Adrenalin 17.12.x can handle 14 cards under windows ?Many people report the motherboards won't POST with 14 or more GPU's. I believe 13 AMD cards is the limit under Windows. My ASRock H110 Pro BTC+ works fine with 13 RX 580 under Windows v1709 with the 17.12.2 drivers.
https://bitcointalksearch.org/topic/m.27496480
January 08, 2018, 07:32:38 AM
Performance is about the same, but the AMD blockchain drivers have an 8 card limit. The Crimson Relive 17.11.x and Adrenalin 17.12.x drivers let you run at least 13 cards and are compatible with the Windows 10 v1709 fall creators update.
Maybe you can tell : Adrenalin 17.12.x can handle 14 cards under windows ?Many people report the motherboards won't POST with 14 or more GPU's. I believe 13 AMD cards is the current limit under Windows v1709. My ASRock H110 Pro BTC+ works fine with 13 RX 580 under Windows v1709 with the 17.12.2 drivers.
https://bitcointalksearch.org/topic/m.27496480
January 08, 2018, 07:30:46 AM
Question: why would this miner complain about mport 10048 or the like not being available when there was no switch for the remote monitoring port in the command line? It seemed ominous so I stopped the miner and added "-mport 0" to the command line before restarting, but I haven't a clue why it was complaining about not being able to access the port in the first place.
January 08, 2018, 07:22:15 AM
Performance is about the same, but the AMD blockchain drivers have an 8 card limit. The Crimson Relive 17.11.x and Adrenalin 17.12.x drivers let you run at least 13 cards and are compatible with the Windows 10 v1709 fall creators update.
Maybe you can tell : Adrenalin 17.12.x can handle 14 cards under windows ? January 08, 2018, 07:12:38 AM
Performance is about the same, but the AMD blockchain drivers have an 8 card limit. The Crimson Relive 17.11.x and Adrenalin 17.12.x drivers let you run at least 13 cards and are compatible with the Windows 10 v1709 fall creators update.
January 08, 2018, 06:54:52 AM
Is the new AMD driver better and stable than blockchain driver from august ? Thanks for reply.
Jump to: