AlainC
Member
Offline
Activity: 91
Merit: 10
|
|
January 07, 2018, 07:29:48 PM |
|
Can't wait for the updated Linux version! Plz!
Hey, it's Sunday ! Even a miner maker have off-time.
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
Rickirs
Member
Offline
Activity: 206
Merit: 20
|
|
January 07, 2018, 08:15:31 PM |
|
Hi! I’m using ubuntu 16.04.3, AMD GPU Pro 17.40 driver and Radeon 290 card.
Is cclock working with this configuration? I tried 1100 and 1200 setting, but apparently it didn’t have any effect.
I can confirm that cclock and other overclocking settings were not working for me 17.40 (RX 580) , reason was that miner was not able to detect ADL library. Are you seeing ADL library missing error on startup ?
|
|
|
|
mares992
Newbie
Offline
Activity: 4
Merit: 0
|
|
January 07, 2018, 08:25:20 PM |
|
Hello, I'm try to make to dual-mining ethereum and siacoin with Claymore's v10.3 but get error 18:17:56:674 1994 GPU 5, GpuMiner cu_k01 failed 73, an illegal instruction was encountered 18:17:56:689 1994 GPU 5, GpuMiner kx failed 1 18:17:56:689 1994 Set global fail flag, failed GPU5 18:17:56:689 1994 GPU 5 failed 18:17:56:705 2124 GPU 3, GpuMiner cu_k01 failed 73, an illegal instruction was encountered 18:17:56:721 14d4 GPU 2, GpuMiner cu_k01 failed 73, an illegal instruction was encountered 18:17:56:721 15bc GPU 1, GpuMiner cu_k01 failed 73, an illegal instruction was encountered 18:17:56:736 15bc GPU 1, GpuMiner kx failed 1 18:17:56:736 15bc Set global fail flag, failed GPU1 18:17:56:736 15bc GPU 1 failed 18:17:56:752 2124 GPU 3, GpuMiner kx failed 1 18:17:56:752 2124 Set global fail flag, failed GPU3 18:17:56:768 1e24 GPU 5, GpuMiner cu_k01 failed 73, an illegal instruction was encountered 18:17:56:768 a58 GPU 4, GpuMiner cu_k01 failed 73, an illegal instruction was encountered 18:17:56:783 a58 GPU 4, GpuMiner kx failed 1 18:17:56:783 a58 Set global fail flag, failed GPU4 18:17:56:783 a58 GPU 4 failed 18:17:56:814 1688 GPU 3, GpuMiner cu_k01 failed 73, an illegal instruction was encountered 18:17:56:830 1688 GPU 3, GpuMiner kx failed 1 18:17:56:830 1688 Set global fail flag, failed GPU3 18:17:56:846 1688 GPU 3 failed 18:17:56:846 1e2c GPU 1, GpuMiner cu_k01 failed 73, an illegal instruction was encountered 18:17:56:846 1e2c GPU 1, GpuMiner kx failed 1 18:17:56:861 1e2c Set global fail flag, failed GPU1 18:17:56:861 2124 GPU 3 failed 18:17:56:861 1e24 GPU 5, GpuMiner kx failed 1 18:17:56:877 1474 GPU 0, GpuMiner cu_k01 failed 73, an illegal instruction was encountered 18:17:56:877 14d4 GPU 2, GpuMiner kx failed 1 18:17:56:893 2084 GPU 4, GpuMiner cu_k01 failed 73, an illegal instruction was encountered 18:17:56:893 1e2c GPU 1 failed 18:17:56:877 1e24 Set global fail flag, failed GPU5 18:17:56:908 1e24 GPU 5 failed 18:17:56:893 14d4 Set global fail flag, failed GPU2 18:17:56:924 14d4 GPU 2 failed 18:17:56:924 1474 GPU 0, GpuMiner kx failed 1 18:17:56:924 2084 GPU 4, GpuMiner kx failed 1 18:17:56:939 1208 GPU 2, GpuMiner cu_k01 failed 73, an illegal instruction was encountered 18:17:56:924 1474 Set global fail flag, failed GPU0 18:17:56:939 1474 GPU 0 failed 18:17:56:955 1208 GPU 2, GpuMiner kx failed 1 18:17:56:939 2084 Set global fail flag, failed GPU4 18:17:56:971 2084 GPU 4 failed 18:17:56:955 1208 Set global fail flag, failed GPU2 18:17:56:971 1208 GPU 2 failed 18:17:56:986 1d8c GPU 0, GpuMiner cu_k01 failed 73, an illegal instruction was encountered 18:17:56:986 1d8c GPU 0, GpuMiner kx failed 1 18:17:56:986 1d8c Set global fail flag, failed GPU0 18:17:57:002 1d8c GPU 0 failed 18:17:58:174 1fe0 got 243 bytes After this, miner restart and start mining again. After few minutes again this error and over again. Rig is not stable with dual mining. Rig have 6 GPU Asus P106, Winodws 10, nVidia driver 382.53.
|
|
|
|
Matias
|
|
January 07, 2018, 08:26:26 PM |
|
Hi! I’m using ubuntu 16.04.3, AMD GPU Pro 17.40 driver and Radeon 290 card.
Is cclock working with this configuration? I tried 1100 and 1200 setting, but apparently it didn’t have any effect.
I can confirm that cclock and other overclocking settings were not working for me 17.40 (RX 580) , reason was that miner was not able to detect ADL library. Are you seeing ADL library missing error on startup ? Yes, I get that error.. How can I fix it?
|
|
|
|
block2chain
Newbie
Offline
Activity: 5
Merit: 0
|
|
January 08, 2018, 04:23:53 AM |
|
Can't wait for the updated Linux version! Plz!
Hey, it's Sunday ! Even a miner maker have off-time. I know, I'm being impatient like my kids on Christmas Eve, but its so hard waiting for CryptoSanta Claymore!
|
|
|
|
big_daddy
|
|
January 08, 2018, 10:14:27 AM |
|
did anyone get some Mgh/s improvements with the new version 10.3? on AMD cards? I am using the RX 470, 480 & 570 and got not a fraction more thane the version 10.2
|
If you don't believe it or don't get it, I don't have the time to try to convince you, sorry.
|
|
|
tg88
Legendary
Offline
Activity: 2380
Merit: 1406
|
|
January 08, 2018, 10:47:47 AM |
|
did anyone get some Mgh/s improvements with the new version 10.3? on AMD cards? I am using the RX 470, 480 & 570 and got not a fraction more thane the version 10.2
No, this version was just to make temperature control and clocks compatible with the new version of amd drivers, had no improvement in speed.
|
|
|
|
cdrx
|
|
January 08, 2018, 10:54:52 AM |
|
Is the new AMD driver better and stable than blockchain driver from august ? Thanks for reply.
|
|
|
|
Vann
|
|
January 08, 2018, 11: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.
|
|
|
|
frks
Newbie
Offline
Activity: 7
Merit: 0
|
|
January 08, 2018, 11: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 ?
|
|
|
|
MagicSmoker
|
|
January 08, 2018, 11: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.
|
|
|
|
Vann
|
|
January 08, 2018, 11: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://bitcointalk.org/index.php?topic=2504064.msg27496480#msg27496480
|
|
|
|
frks
Newbie
Offline
Activity: 7
Merit: 0
|
|
January 08, 2018, 11: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://bitcointalk.org/index.php?topic=2504064.msg27496480#msg27496480even with Asus 250 ?
|
|
|
|
Vann
|
|
January 08, 2018, 11: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://bitcointalk.org/index.php?topic=2504064.msg27496480#msg27496480even with Asus 250 ? 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.
|
|
|
|
frks
Newbie
Offline
Activity: 7
Merit: 0
|
|
January 08, 2018, 12:01:11 PM Last edit: January 08, 2018, 12:19:54 PM by frks |
|
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://bitcointalk.org/index.php?topic=2504064.msg27496480#msg27496480even with Asus 250 ? 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. Even with linux ? I found : 13gpu and one minning card - then work
|
|
|
|
frks
Newbie
Offline
Activity: 7
Merit: 0
|
|
January 08, 2018, 12:37:15 PM |
|
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 ?
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 ?
|
|
|
|
npittas
Newbie
Offline
Activity: 29
Merit: 0
|
|
January 08, 2018, 02:14:28 PM |
|
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.
|
|
|
|
MagicSmoker
|
|
January 08, 2018, 02:43:41 PM |
|
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. Interesting; I wonder if this is what was happening to me earlier with Claymore reporting that mport 10048 wasn't available?
|
|
|
|
BCCrypto68
Newbie
Offline
Activity: 27
Merit: 0
|
|
January 08, 2018, 03:40:01 PM |
|
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. 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.
|
|
|
|
MagicSmoker
|
|
January 08, 2018, 03:50:04 PM |
|
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. 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.
|
|
|
|
|