Bitcoin Forum
June 23, 2021, 02:12:04 PM *
News: Latest Bitcoin Core release: 0.21.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 [71] 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 ... 1431 »
  Print  
Author Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)  (Read 6582760 times)
arielbit
Legendary
*
Online Online

Activity: 2576
Merit: 1034


View Profile
May 01, 2016, 11:04:46 PM

Still getting server problems on 4.1 please help. Was posted a few pages back but still no response to my problem and this keeps on happening. Any ideas to fix and resolve Claymore??

ETH: Stratum - socket send failed 10053, disconnect

Change pool or check your ISP, I don't have other ideas why TCP connection is broken.

Pools are fine and on v 3.xx works fine no problems. From v4 and v4.1 etc I get this problem. So I do not understand, ISP is fine, pool is fine as I do not get the problem in previous versions. I want to use current version as I see some improvement in speed however disconnections and socket fail is not good.

firewall.. maybe?

Have all ports forwarded and also decided to disabled for 24 hours and still get socket send failed. So not sure what is going on if you have not changed anything in it.

i've upgraded from 3.2 to 4.1 yesterday.. no issues.

any application control that blocks/prompt/allow outbound-inbound connections? (kinda like firewall)..
1624457524
Hero Member
*
Offline Offline

Posts: 1624457524

View Profile Personal Message (Offline)

Ignore
1624457524
Reply with quote  #2

1624457524
Report to moderator
1624457524
Hero Member
*
Offline Offline

Posts: 1624457524

View Profile Personal Message (Offline)

Ignore
1624457524
Reply with quote  #2

1624457524
Report to moderator
1624457524
Hero Member
*
Offline Offline

Posts: 1624457524

View Profile Personal Message (Offline)

Ignore
1624457524
Reply with quote  #2

1624457524
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1624457524
Hero Member
*
Offline Offline

Posts: 1624457524

View Profile Personal Message (Offline)

Ignore
1624457524
Reply with quote  #2

1624457524
Report to moderator
1624457524
Hero Member
*
Offline Offline

Posts: 1624457524

View Profile Personal Message (Offline)

Ignore
1624457524
Reply with quote  #2

1624457524
Report to moderator
1624457524
Hero Member
*
Offline Offline

Posts: 1624457524

View Profile Personal Message (Offline)

Ignore
1624457524
Reply with quote  #2

1624457524
Report to moderator
Bojcha
Hero Member
*****
Offline Offline

Activity: 848
Merit: 500



View Profile
May 01, 2016, 11:05:30 PM

new epoch transition went just fine Wink
crazyearner
Legendary
*
Offline Offline

Activity: 1820
Merit: 1001



View Profile
May 01, 2016, 11:08:26 PM

Still getting server problems on 4.1 please help. Was posted a few pages back but still no response to my problem and this keeps on happening. Any ideas to fix and resolve Claymore??

ETH: Stratum - socket send failed 10053, disconnect

Change pool or check your ISP, I don't have other ideas why TCP connection is broken.

Pools are fine and on v 3.xx works fine no problems. From v4 and v4.1 etc I get this problem. So I do not understand, ISP is fine, pool is fine as I do not get the problem in previous versions. I want to use current version as I see some improvement in speed however disconnections and socket fail is not good.

firewall.. maybe?

Have all ports forwarded and also decided to disabled for 24 hours and still get socket send failed. So not sure what is going on if you have not changed anything in it.

i've upgraded from 3.2 to 4.1 yesterday.. no issues.

any application control that blocks/prompt/allow outbound-inbound connections? (kinda like firewall)..

Nothing of its kind. Just seems Windows 8.1 and v 4.1 system does not like it. I am trying a new pool out and will monitor it but I do not see how going from versions 3xx to 4 I get socket problems is a wired one for sure.

=
  R E B E L L I O U S 
  ▄▀▀▀▀▀▄▄                           ▄▄▀▀▀▀▀▄
▄▀        █▄▄                     ▄▄█        ▀▄
█            █████████████████████            █
█▄          ██       ██ ██       ██          ▄█
█        █            █            █        █
  █    █               █               █    █
   █ ██               █ █               ██ █
    █ █               █ █               █ █
    █ ███▄  █████▄   ██ ██   ▄█████  ▄███ █
    █     ███     █         █     ███     █
     █   █   ▀███ █  █   █  █ ███▀   █   █
     █   █      █ █  █   █  █ █      █   █
     █   █      ██  █     █  ██      █   █
      █  █     ██  █       █  ██     █  █
      █  █    ██  █ ███████ █  ██    █  █
      █ ███   ██  █         █  ██   ███ █
       █   ▀███      █   █      ███▀   █
        █     ██       █       ██     █
         █      █   ▄▄███▄▄   █      █
          ███   ███▀       ▀███   ███
             █████           █████
                  ███████████
  ▄▀▀▀▀▀▄▄                           ▄▄▀▀▀▀▀▄
▄▀        █▄▄                     ▄▄█        ▀▄
█            █████████████████████            █
█▄          ██       ██ ██       ██          ▄█
█        █            █            █        █
  █    █               █               █    █
   █ ██               █ █               ██ █
    █ █               █ █               █ █
    █ ███▄  █████▄   ██ ██   ▄█████  ▄███ █
    █     ███     █         █     ███     █
     █   █   ▀███ █  █   █  █ ███▀   █   █
     █   █      █ █  █   █  █ █      █   █
     █   █      ██  █     █  ██      █   █
      █  █     ██  █       █  ██     █  █
      █  █    ██  █ ███████ █  ██    █  █
      █ ███   ██  █         █  ██   ███ █
       █   ▀███      █   █      ███▀   █
        █     ██       █       ██     █
         █      █   ▄▄███▄▄   █      █
          ███   ███▀       ▀███   ███
             █████           █████
                  ███████████
  R E B E L L I O U S
arielbit
Legendary
*
Online Online

Activity: 2576
Merit: 1034


View Profile
May 01, 2016, 11:11:46 PM

Still getting server problems on 4.1 please help. Was posted a few pages back but still no response to my problem and this keeps on happening. Any ideas to fix and resolve Claymore??

ETH: Stratum - socket send failed 10053, disconnect

Change pool or check your ISP, I don't have other ideas why TCP connection is broken.

Pools are fine and on v 3.xx works fine no problems. From v4 and v4.1 etc I get this problem. So I do not understand, ISP is fine, pool is fine as I do not get the problem in previous versions. I want to use current version as I see some improvement in speed however disconnections and socket fail is not good.

firewall.. maybe?

Have all ports forwarded and also decided to disabled for 24 hours and still get socket send failed. So not sure what is going on if you have not changed anything in it.

i've upgraded from 3.2 to 4.1 yesterday.. no issues.

any application control that blocks/prompt/allow outbound-inbound connections? (kinda like firewall)..

Nothing of its kind. Just seems Windows 8.1 and v 4.1 system does not like it. I am trying a new pool out and will monitor it but I do not see how going from versions 3xx to 4 I get socket problems is a wired one for sure.

v4.1 got "epools.txt" and "dpools.txt" now
crazyearner
Legendary
*
Offline Offline

Activity: 1820
Merit: 1001



View Profile
May 01, 2016, 11:22:11 PM

Still getting server problems on 4.1 please help. Was posted a few pages back but still no response to my problem and this keeps on happening. Any ideas to fix and resolve Claymore??

ETH: Stratum - socket send failed 10053, disconnect

Change pool or check your ISP, I don't have other ideas why TCP connection is broken.

Pools are fine and on v 3.xx works fine no problems. From v4 and v4.1 etc I get this problem. So I do not understand, ISP is fine, pool is fine as I do not get the problem in previous versions. I want to use current version as I see some improvement in speed however disconnections and socket fail is not good.

firewall.. maybe?

Have all ports forwarded and also decided to disabled for 24 hours and still get socket send failed. So not sure what is going on if you have not changed anything in it.

i've upgraded from 3.2 to 4.1 yesterday.. no issues.

any application control that blocks/prompt/allow outbound-inbound connections? (kinda like firewall)..

Nothing of its kind. Just seems Windows 8.1 and v 4.1 system does not like it. I am trying a new pool out and will monitor it but I do not see how going from versions 3xx to 4 I get socket problems is a wired one for sure.

v4.1 got "epools.txt" and "dpools.txt" now

Have made appropute changes to both them files and I only use for ETH mining anyway as Decreed mining I maybe make 0.2 per day so its not worth the satoshis for the extra power used. ETH mining on its own provides me batter gains. and even with them txt files edited makes no changes. Only thing I can do is monitor for next 24 hours or so and see how it pans out on another pool as advised to try. Only way to find out even tho tried different pools in past didnt make any difference.

=
  R E B E L L I O U S 
  ▄▀▀▀▀▀▄▄                           ▄▄▀▀▀▀▀▄
▄▀        █▄▄                     ▄▄█        ▀▄
█            █████████████████████            █
█▄          ██       ██ ██       ██          ▄█
█        █            █            █        █
  █    █               █               █    █
   █ ██               █ █               ██ █
    █ █               █ █               █ █
    █ ███▄  █████▄   ██ ██   ▄█████  ▄███ █
    █     ███     █         █     ███     █
     █   █   ▀███ █  █   █  █ ███▀   █   █
     █   █      █ █  █   █  █ █      █   █
     █   █      ██  █     █  ██      █   █
      █  █     ██  █       █  ██     █  █
      █  █    ██  █ ███████ █  ██    █  █
      █ ███   ██  █         █  ██   ███ █
       █   ▀███      █   █      ███▀   █
        █     ██       █       ██     █
         █      █   ▄▄███▄▄   █      █
          ███   ███▀       ▀███   ███
             █████           █████
                  ███████████
  ▄▀▀▀▀▀▄▄                           ▄▄▀▀▀▀▀▄
▄▀        █▄▄                     ▄▄█        ▀▄
█            █████████████████████            █
█▄          ██       ██ ██       ██          ▄█
█        █            █            █        █
  █    █               █               █    █
   █ ██               █ █               ██ █
    █ █               █ █               █ █
    █ ███▄  █████▄   ██ ██   ▄█████  ▄███ █
    █     ███     █         █     ███     █
     █   █   ▀███ █  █   █  █ ███▀   █   █
     █   █      █ █  █   █  █ █      █   █
     █   █      ██  █     █  ██      █   █
      █  █     ██  █       █  ██     █  █
      █  █    ██  █ ███████ █  ██    █  █
      █ ███   ██  █         █  ██   ███ █
       █   ▀███      █   █      ███▀   █
        █     ██       █       ██     █
         █      █   ▄▄███▄▄   █      █
          ███   ███▀       ▀███   ███
             █████           █████
                  ███████████
  R E B E L L I O U S
malandante
Full Member
***
Offline Offline

Activity: 142
Merit: 100


View Profile
May 01, 2016, 11:28:54 PM

Within 24 hours I will release Linux version of the miner, it is almost ready, Ubuntu 12.04 is used for tests.

Looking forward to trying it Wink 12.04? Or you mean 14.04?

Edit: smiley correction
zyzzyva
Member
**
Offline Offline

Activity: 82
Merit: 10


View Profile
May 02, 2016, 12:14:56 AM

Can anyone point me at a good tutorial on installing the AMD drivers for Ethereum mining on Ubuntu? I'm in the middle of building a new rig and would really like to install Linux instead of Windows if Claymore's miner will work on it...
citronick
Legendary
*
Offline Offline

Activity: 1834
Merit: 1080


---- winter*juvia -----


View Profile
May 02, 2016, 12:34:32 AM

Can anyone point me at a good tutorial on installing the AMD drivers for Ethereum mining on Ubuntu? I'm in the middle of building a new rig and would really like to install Linux instead of Windows if Claymore's miner will work on it...

see first post in this thread by Claymore:

This version is for recent AMD videocards only: 7xxx, 2xx and 3xx, 2GB or more. No nVidia support.
This version is for Windows x64 only. No Linux support Linux version will be available within 24 hours. No 32-bit support.

If I provided you good and useful info or just a smile to your day, consider sending me merit points to further validate this Bitcointalk account ~ useful for future account recovery...
zyzzyva
Member
**
Offline Offline

Activity: 82
Merit: 10


View Profile
May 02, 2016, 12:56:33 AM

Can anyone point me at a good tutorial on installing the AMD drivers for Ethereum mining on Ubuntu? I'm in the middle of building a new rig and would really like to install Linux instead of Windows if Claymore's miner will work on it...

see first post in this thread by Claymore:

This version is for recent AMD videocards only: 7xxx, 2xx and 3xx, 2GB or more. No nVidia support.
This version is for Windows x64 only. No Linux support Linux version will be available within 24 hours. No 32-bit support.


Yeah, that's what I mean. I'd like to run the Linux version when it's available, I just have had trouble getting the AMD drivers installed on Ubuntu in the past. I'm wondering if there's an up-to-date tutorial on getting the drivers working.
dannygroove
Sr. Member
****
Offline Offline

Activity: 306
Merit: 250



View Profile WWW
May 02, 2016, 01:24:07 AM

Still getting server problems on 4.1 please help. Was posted a few pages back but still no response to my problem and this keeps on happening. Any ideas to fix and resolve Claymore??

ETH: Stratum - socket send failed 10053, disconnect

Change pool or check your ISP, I don't have other ideas why TCP connection is broken.

Pools are fine and on v 3.xx works fine no problems. From v4 and v4.1 etc I get this problem. So I do not understand, ISP is fine, pool is fine as I do not get the problem in previous versions. I want to use current version as I see some improvement in speed however disconnections and socket fail is not good.

Thats probably due to latency, yours or the pool's.
o00o
Member
**
Offline Offline

Activity: 93
Merit: 11


View Profile
May 02, 2016, 02:53:27 AM


Could you have by accident installed 32bit windows?  I know you said it's x64 but it sounds like you're pressing that 4gb limit (~3.25gb addressable)

I can confirm it is indeed x64 via the Control Panel's basic system information.  I have the same distro installed on two other rigs, one of which is an Intel Bad Axe 2 seating 1 390x, 1 290x & 1 290 w/ 2 x 1 GB + 2 x 2GB where all 6GB are properly allocated and the other from vague recollection is an Asus P5b also on socket 775 with 2 x 2GB where only 3.25GB is usable as indicated in the motherboard's manual.  

fo00ok
I have a very similar PC - s.775, 4GB RAm, Win7, 3.25GB recognized with latest bios and 290 inside.
It works flawlessly with Virtual memory set to static 16GB size and all Genoil/Claymore versions


Ethminer works just fine as well as Claymore's v1.2.  I just set a single 16GB pagefile and tried launching v4.1 and it returned the following error: GPU 0, OpenCL error -4 - cannot create DAG.

@Claymore

I uploaded my log and would be very grateful if you can take a quick glance at it.

https://dropfile.to/aCSRy1d

I'm mining with 775 CPU's and boards here..

win 7 64bit, 4GB ram, 80gb HDD , Xeon 3220 (Q6600)

I'm mining alright here, currently on v3.2  ...haven't tested the V4.0 (the no DAG version)

I have a pentiumD, a pentium 4 HT, and core2duo E8400 that I decomissioned for mining...these very old CPUs compared to X3220 are affecting hashrate..

 

and one of the best advantages of v4 is the minimized cpu usage.
with my single motherboard, old xeon xpu, with 5 gpus it was %25+
now the cpu usage is %1, and I believe mining is a tick faster, fyi

Memory usage decreased from ~1.5GB to ~0.15GB.
 
I'm also mining Hodlcoin on all available cores of my q6600 & PentiumD without any noticeable impact on my ETH+DCR hashrate.

BTC:1Gk3p6KbCKiVhJYksaYPeAGL948rAsjmUS
Marvell1
Legendary
*
Offline Offline

Activity: 1428
Merit: 1000


View Profile
May 02, 2016, 03:02:45 AM

having a problem on one of my machines since the new Epoc

Code:
23:03:56:142 e9c
23:03:56:157 e9c 浜様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様融
23:03:56:157 e9c    Claymore's Dual Ethereum + Decred AMD GPU Miner  v4.0 Beta   
23:03:56:173 e9c 藩様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様夕
23:03:56:173 e9c
23:03:56:392 e9c ETH: 1 pool is specified
23:03:56:392 e9c DCR: 1 pool is specified
23:03:56:798 e9c
Cards available: 5
23:03:56:798 e9c GPU #0: name: Hawaii, 8192 MB available, 40 units
23:03:56:798 e9c GPU #1: name: Hawaii, 8192 MB available, 40 units
23:03:56:814 e9c GPU #2: name: Hawaii, 8192 MB available, 40 units
23:03:56:814 e9c GPU #3: name: Fiji, 4096 MB available, 64 units
23:03:56:829 e9c GPU #4: name: Hawaii, 8192 MB available, 40 units
23:03:56:829 e9c Total cards: 5
23:03:56:829 e9c Initializing...

23:03:56:829 e9c GPU #0 recognized as Radeon 390
23:03:56:829 e9c GPU #1 recognized as Radeon 390
23:03:56:829 e9c GPU #2 recognized as Radeon 390
23:03:56:845 e9c GPU #3 recognized as Fury X/Nano
23:03:56:845 e9c GPU #4 recognized as Radeon 390
23:03:56:845 e9c POOL version
23:03:56:845 e9c b121
23:03:56:860 e9c GPU #0: set -etha as 0 (ETH algo for fast cards)
23:03:56:860 e9c GPU #1: set -etha as 0 (ETH algo for fast cards)
23:03:56:860 e9c GPU #2: set -etha as 0 (ETH algo for fast cards)
23:03:56:860 e9c GPU #3: set -etha as 0 (ETH algo for fast cards)
23:03:56:876 e9c GPU #4: set -etha as 0 (ETH algo for fast cards)
23:03:57:829 33c ETH: Stratum - connecting to 'coinotron.com' <178.217.186.125> port 3344
23:03:57:939 e9c DUAL MINING MODE ENABLED: ETHEREUM+DECRED
23:03:57:939 131c DCR: Stratum - connecting to 'dcr.suprnova.cc' <178.33.228.14> port 2252
23:03:57:954 e9c Decred HTTP requests time (-dcrt) is set to 10
23:03:57:970 e9c miner-proxy stratum mode
23:03:57:970 e9c "-allpools" option is set, default pools can be used for devfee, check "Readme" file for details.
23:03:57:985 e9c Watchdog enabled
23:03:57:985 e9c
23:03:57:985 33c send: {"id": 1, "method": "mining.subscribe", "params": []}

23:03:58:001 33c send: {"id": 2, "method": "mining.authorize", "params": ["Marvell9.55","x"]}

23:03:58:001 33c ETH: Stratum - Connected (coinotron.com:3344)
23:03:58:079 131c send: {"id": 1, "method": "mining.subscribe", "params": ["dcr 1.0"]}

23:03:58:079 131c send: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}

23:03:58:095 131c send: {"id": 2, "method": "mining.authorize", "params": ["Marvell9.55","x"]}

23:03:58:095 131c DCR: Stratum - Connected (dcr.suprnova.cc:2252)
23:03:58:173 33c got 107 bytes
23:03:58:173 33c buf: {"error": null, "id": 1, "result": [["mining.notify", "1b2888e9ff6c4cf1ae113322ad37d930"], "08001443", 4]}

23:03:58:189 33c parse packet: 99
23:03:58:189 33c new buf size: 0
23:03:58:220 131c got 591 bytes
23:03:58:220 131c buf: {"error": null, "id": 1, "result": [["mining.notify", "ae6812eb4cd7735a302a8a9dd95cf71f"], "00000000f8000752f8000752", 12]}
{"params": [1], "id": null, "method": "mining.set_difficulty"}
{"params": ["8c", "931c82a0a9dbbe2d06f3dabd121b279fd581d5fbff2d4d8a0000088800000000", "ca3750d31f2611f45e94488a4bf6844ad842eca4c677edb25582dc43094aeaafa4c928a58668058ac63e946fb81e71f8a7256fea6e4df42a91929135fdb6dfe40100155dea317971050002004ba60000d6091d1adb11556d00000000395f0000ff150000d6c226570000000000000000", "", [], "01000000", "1a1d09d6", "5726c2d6", true], "id": null, "method": "mining.notify"}

23:03:58:220 131c parse packet: 116
23:03:58:220 131c remove first packet 449
23:03:58:220 131c new buf size: 449
23:03:58:220 131c parse packet: 58
23:03:58:235 131c remove first packet 391
23:03:58:235 131c new buf size: 391
23:03:58:235 131c parse packet: 391
23:03:58:235 131c new buf size: 0
23:03:58:329 33c got 342 bytes
23:03:58:329 131c got 82 bytes
23:03:58:329 33c buf: { "id": null, "method": "mining.set_difficulty", "params": [55000]}
{"params": ["7178", "0xddf13e0d55b3a4f9951c662550853b13bd58bece9373fb7d533c4709fad16271","0x17a7217f2673ce6267021cc82e7b328a755f010d6741bde6c25d3c2b0373e989","0x00000001310A508148DF1ECB62908D334643D83B47C1251FE95C3C06679770B6", true], "id": null, "method": "mining.notify"}

23:03:58:329 131c buf: {"error": null, "id": 5, "result": true}
{"error": null, "id": 2, "result": true}

23:03:58:345 33c parse packet: 62
23:03:58:345 131c parse packet: 36
23:03:58:360 33c remove first packet 267
23:03:58:360 131c remove first packet 36
23:03:58:360 33c new buf size: 267
23:03:58:360 131c new buf size: 36
23:03:58:360 33c parse packet: 267
23:03:58:376 131c parse packet: 36
23:03:58:376 33c eth: job changed
23:03:58:376 131c DCR: Authorized
23:03:58:376 33c new buf size: 0
23:03:58:376 131c new buf size: 0
23:03:58:454 97c Setting DAG epoch #48...
23:03:58:532 33c got 101 bytes
23:03:58:532 33c buf: {"error": null, "id": 2, "result": true}
{ "id": 9876, "method": "client.get_version", "params": []}

23:03:58:532 33c parse packet: 36
23:03:58:532 33c ETH: Authorized
23:03:58:532 33c remove first packet 54
23:03:58:532 33c new buf size: 54
23:03:58:532 33c parse packet: 54
23:03:58:548 33c send: {"error": null, "id": 9876, "result": "eth 1.0"}

23:03:58:548 33c new buf size: 0
23:03:59:673 97c Setting DAG epoch #48 for GPU #4
23:03:59:673 12dc Setting DAG epoch #48 for GPU #3
23:03:59:673 1238 Setting DAG epoch #48 for GPU #2
23:03:59:673 c94 Setting DAG epoch #48 for GPU #0
23:03:59:673 1244 Setting DAG epoch #48 for GPU #1
23:03:59:673 97c Create GPU buffer for GPU #4
23:03:59:673 12dc Create GPU buffer for GPU #3
23:03:59:673 1238 Create GPU buffer for GPU #2
23:03:59:689 c94 Create GPU buffer for GPU #0
23:03:59:689 1244 Create GPU buffer for GPU #1
23:03:59:767 97c GPU 4, OpenCL error -48 - cannot create DAG on GPU
23:03:59:767 1238 GPU 2, OpenCL error -48 - cannot create DAG on GPU
23:03:59:767 c94 GPU 0, OpenCL error -48 - cannot create DAG on GPU
23:03:59:829 12dc GPU 3, OpenCL error -48 - cannot create DAG on GPU
23:03:59:845 1244 GPU 1, OpenCL error -48 - cannot create DAG on GPU
23:04:01:048 e9c OC v6, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst
23:04:01:064 e9c OC v6, Reset control for GPU 6, close miner right now if you want to use default control from Catalyst
23:04:01:064 e9c OC v6, Reset control for GPU 12, close miner right now if you want to use default control from Catalyst
23:04:01:064 e9c OC v6, Reset control for GPU 18, close miner right now if you want to use default control from Catalyst
23:04:01:079 e9c OC v6, Reset control for GPU 24, close miner right now if you want to use default control from Catalyst

citronick
Legendary
*
Offline Offline

Activity: 1834
Merit: 1080


---- winter*juvia -----


View Profile
May 02, 2016, 04:54:27 AM

having a problem on one of my machines since the new Epoc

Code:
23:03:56:142 e9c
23:03:56:157 e9c 浜様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様融
23:03:56:157 e9c    Claymore's Dual Ethereum + Decred AMD GPU Miner  v4.0 Beta   
23:03:56:173 e9c 藩様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様夕
23:03:56:173 e9c
23:03:56:392 e9c ETH: 1 pool is specified
23:03:56:392 e9c DCR: 1 pool is specified
23:03:56:798 e9c
Cards available: 5
23:03:56:798 e9c GPU #0: name: Hawaii, 8192 MB available, 40 units
23:03:56:798 e9c GPU #1: name: Hawaii, 8192 MB available, 40 units
23:03:56:814 e9c GPU #2: name: Hawaii, 8192 MB available, 40 units
23:03:56:814 e9c GPU #3: name: Fiji, 4096 MB available, 64 units
23:03:56:829 e9c GPU #4: name: Hawaii, 8192 MB available, 40 units
23:03:56:829 e9c Total cards: 5
23:03:56:829 e9c Initializing...

23:03:56:829 e9c GPU #0 recognized as Radeon 390
23:03:56:829 e9c GPU #1 recognized as Radeon 390
23:03:56:829 e9c GPU #2 recognized as Radeon 390
23:03:56:845 e9c GPU #3 recognized as Fury X/Nano
23:03:56:845 e9c GPU #4 recognized as Radeon 390
23:03:56:845 e9c POOL version
23:03:56:845 e9c b121
23:03:56:860 e9c GPU #0: set -etha as 0 (ETH algo for fast cards)
23:03:56:860 e9c GPU #1: set -etha as 0 (ETH algo for fast cards)
23:03:56:860 e9c GPU #2: set -etha as 0 (ETH algo for fast cards)
23:03:56:860 e9c GPU #3: set -etha as 0 (ETH algo for fast cards)
23:03:56:876 e9c GPU #4: set -etha as 0 (ETH algo for fast cards)
23:03:57:829 33c ETH: Stratum - connecting to 'coinotron.com' <178.217.186.125> port 3344
23:03:57:939 e9c DUAL MINING MODE ENABLED: ETHEREUM+DECRED
23:03:57:939 131c DCR: Stratum - connecting to 'dcr.suprnova.cc' <178.33.228.14> port 2252
23:03:57:954 e9c Decred HTTP requests time (-dcrt) is set to 10
23:03:57:970 e9c miner-proxy stratum mode
23:03:57:970 e9c "-allpools" option is set, default pools can be used for devfee, check "Readme" file for details.
23:03:57:985 e9c Watchdog enabled
23:03:57:985 e9c
23:03:57:985 33c send: {"id": 1, "method": "mining.subscribe", "params": []}

23:03:58:001 33c send: {"id": 2, "method": "mining.authorize", "params": ["Marvell9.55","x"]}

23:03:58:001 33c ETH: Stratum - Connected (coinotron.com:3344)
23:03:58:079 131c send: {"id": 1, "method": "mining.subscribe", "params": ["dcr 1.0"]}

23:03:58:079 131c send: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}

23:03:58:095 131c send: {"id": 2, "method": "mining.authorize", "params": ["Marvell9.55","x"]}

23:03:58:095 131c DCR: Stratum - Connected (dcr.suprnova.cc:2252)
23:03:58:173 33c got 107 bytes
23:03:58:173 33c buf: {"error": null, "id": 1, "result": [["mining.notify", "1b2888e9ff6c4cf1ae113322ad37d930"], "08001443", 4]}

23:03:58:189 33c parse packet: 99
23:03:58:189 33c new buf size: 0
23:03:58:220 131c got 591 bytes
23:03:58:220 131c buf: {"error": null, "id": 1, "result": [["mining.notify", "ae6812eb4cd7735a302a8a9dd95cf71f"], "00000000f8000752f8000752", 12]}
{"params": [1], "id": null, "method": "mining.set_difficulty"}
{"params": ["8c", "931c82a0a9dbbe2d06f3dabd121b279fd581d5fbff2d4d8a0000088800000000", "ca3750d31f2611f45e94488a4bf6844ad842eca4c677edb25582dc43094aeaafa4c928a58668058ac63e946fb81e71f8a7256fea6e4df42a91929135fdb6dfe40100155dea317971050002004ba60000d6091d1adb11556d00000000395f0000ff150000d6c226570000000000000000", "", [], "01000000", "1a1d09d6", "5726c2d6", true], "id": null, "method": "mining.notify"}

23:03:58:220 131c parse packet: 116
23:03:58:220 131c remove first packet 449
23:03:58:220 131c new buf size: 449
23:03:58:220 131c parse packet: 58
23:03:58:235 131c remove first packet 391
23:03:58:235 131c new buf size: 391
23:03:58:235 131c parse packet: 391
23:03:58:235 131c new buf size: 0
23:03:58:329 33c got 342 bytes
23:03:58:329 131c got 82 bytes
23:03:58:329 33c buf: { "id": null, "method": "mining.set_difficulty", "params": [55000]}
{"params": ["7178", "0xddf13e0d55b3a4f9951c662550853b13bd58bece9373fb7d533c4709fad16271","0x17a7217f2673ce6267021cc82e7b328a755f010d6741bde6c25d3c2b0373e989","0x00000001310A508148DF1ECB62908D334643D83B47C1251FE95C3C06679770B6", true], "id": null, "method": "mining.notify"}

23:03:58:329 131c buf: {"error": null, "id": 5, "result": true}
{"error": null, "id": 2, "result": true}

23:03:58:345 33c parse packet: 62
23:03:58:345 131c parse packet: 36
23:03:58:360 33c remove first packet 267
23:03:58:360 131c remove first packet 36
23:03:58:360 33c new buf size: 267
23:03:58:360 131c new buf size: 36
23:03:58:360 33c parse packet: 267
23:03:58:376 131c parse packet: 36
23:03:58:376 33c eth: job changed
23:03:58:376 131c DCR: Authorized
23:03:58:376 33c new buf size: 0
23:03:58:376 131c new buf size: 0
23:03:58:454 97c Setting DAG epoch #48...
23:03:58:532 33c got 101 bytes
23:03:58:532 33c buf: {"error": null, "id": 2, "result": true}
{ "id": 9876, "method": "client.get_version", "params": []}

23:03:58:532 33c parse packet: 36
23:03:58:532 33c ETH: Authorized
23:03:58:532 33c remove first packet 54
23:03:58:532 33c new buf size: 54
23:03:58:532 33c parse packet: 54
23:03:58:548 33c send: {"error": null, "id": 9876, "result": "eth 1.0"}

23:03:58:548 33c new buf size: 0
23:03:59:673 97c Setting DAG epoch #48 for GPU #4
23:03:59:673 12dc Setting DAG epoch #48 for GPU #3
23:03:59:673 1238 Setting DAG epoch #48 for GPU #2
23:03:59:673 c94 Setting DAG epoch #48 for GPU #0
23:03:59:673 1244 Setting DAG epoch #48 for GPU #1
23:03:59:673 97c Create GPU buffer for GPU #4
23:03:59:673 12dc Create GPU buffer for GPU #3
23:03:59:673 1238 Create GPU buffer for GPU #2
23:03:59:689 c94 Create GPU buffer for GPU #0
23:03:59:689 1244 Create GPU buffer for GPU #1
23:03:59:767 97c GPU 4, OpenCL error -48 - cannot create DAG on GPU
23:03:59:767 1238 GPU 2, OpenCL error -48 - cannot create DAG on GPU
23:03:59:767 c94 GPU 0, OpenCL error -48 - cannot create DAG on GPU
23:03:59:829 12dc GPU 3, OpenCL error -48 - cannot create DAG on GPU
23:03:59:845 1244 GPU 1, OpenCL error -48 - cannot create DAG on GPU
23:04:01:048 e9c OC v6, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst
23:04:01:064 e9c OC v6, Reset control for GPU 6, close miner right now if you want to use default control from Catalyst
23:04:01:064 e9c OC v6, Reset control for GPU 12, close miner right now if you want to use default control from Catalyst
23:04:01:064 e9c OC v6, Reset control for GPU 18, close miner right now if you want to use default control from Catalyst
23:04:01:079 e9c OC v6, Reset control for GPU 24, close miner right now if you want to use default control from Catalyst



are you using Catalyst 15.12?

If I provided you good and useful info or just a smile to your day, consider sending me merit points to further validate this Bitcointalk account ~ useful for future account recovery...
Penguen
Hero Member
*****
Offline Offline

Activity: 714
Merit: 500



View Profile
May 02, 2016, 06:12:54 AM

I have a problem 4.1 software. My card works only 10 min then stop.
i delete 4.1 and install 3.2 beta. now i havent got problem.
is there a proplem 4.1?
jesterRPG
Newbie
*
Offline Offline

Activity: 18
Merit: 0


View Profile
May 02, 2016, 07:52:42 AM

I have a problem 4.1 software. My card works only 10 min then stop.
i delete 4.1 and install 3.2 beta. now i havent got problem.
is there a proplem 4.1?

No. My rigs are running 4.1 fine.
tolazy
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
May 02, 2016, 08:09:27 AM

anyone with a 390x and useing 15.12 driver?
useing 16.2 driver and i get about 30MHs

Yep using 390x with 15.12 drivers and clocked to  1230 /1575 I get about 35MHs . So no big difference.
its almost 5mhs more it adds up Smiley

have OC my card now 1180/1575 i now i get 33-34MHs
Claymore
Donator
Legendary
*
Offline Offline

Activity: 1610
Merit: 1325

Miners developer


View Profile
May 02, 2016, 09:33:44 AM

having a problem on one of my machines since the new Epoc

Code:
23:03:56:142 e9c
23:03:56:157 e9c 浜様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様融
23:03:56:157 e9c    Claymore's Dual Ethereum + Decred AMD GPU Miner  v4.0 Beta   
23:03:56:173 e9c 藩様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様夕
23:03:56:173 e9c
23:03:56:392 e9c ETH: 1 pool is specified
23:03:56:392 e9c DCR: 1 pool is specified
23:03:56:798 e9c
Cards available: 5
23:03:56:798 e9c GPU #0: name: Hawaii, 8192 MB available, 40 units
23:03:56:798 e9c GPU #1: name: Hawaii, 8192 MB available, 40 units
23:03:56:814 e9c GPU #2: name: Hawaii, 8192 MB available, 40 units
23:03:56:814 e9c GPU #3: name: Fiji, 4096 MB available, 64 units
23:03:56:829 e9c GPU #4: name: Hawaii, 8192 MB available, 40 units
23:03:56:829 e9c Total cards: 5
23:03:56:829 e9c Initializing...

23:03:56:829 e9c GPU #0 recognized as Radeon 390
23:03:56:829 e9c GPU #1 recognized as Radeon 390
23:03:56:829 e9c GPU #2 recognized as Radeon 390
23:03:56:845 e9c GPU #3 recognized as Fury X/Nano
23:03:56:845 e9c GPU #4 recognized as Radeon 390
23:03:56:845 e9c POOL version
23:03:56:845 e9c b121
23:03:56:860 e9c GPU #0: set -etha as 0 (ETH algo for fast cards)
23:03:56:860 e9c GPU #1: set -etha as 0 (ETH algo for fast cards)
23:03:56:860 e9c GPU #2: set -etha as 0 (ETH algo for fast cards)
23:03:56:860 e9c GPU #3: set -etha as 0 (ETH algo for fast cards)
23:03:56:876 e9c GPU #4: set -etha as 0 (ETH algo for fast cards)
23:03:57:829 33c ETH: Stratum - connecting to 'coinotron.com' <178.217.186.125> port 3344
23:03:57:939 e9c DUAL MINING MODE ENABLED: ETHEREUM+DECRED
23:03:57:939 131c DCR: Stratum - connecting to 'dcr.suprnova.cc' <178.33.228.14> port 2252
23:03:57:954 e9c Decred HTTP requests time (-dcrt) is set to 10
23:03:57:970 e9c miner-proxy stratum mode
23:03:57:970 e9c "-allpools" option is set, default pools can be used for devfee, check "Readme" file for details.
23:03:57:985 e9c Watchdog enabled
23:03:57:985 e9c
23:03:57:985 33c send: {"id": 1, "method": "mining.subscribe", "params": []}

23:03:58:001 33c send: {"id": 2, "method": "mining.authorize", "params": ["Marvell9.55","x"]}

23:03:58:001 33c ETH: Stratum - Connected (coinotron.com:3344)
23:03:58:079 131c send: {"id": 1, "method": "mining.subscribe", "params": ["dcr 1.0"]}

23:03:58:079 131c send: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}

23:03:58:095 131c send: {"id": 2, "method": "mining.authorize", "params": ["Marvell9.55","x"]}

23:03:58:095 131c DCR: Stratum - Connected (dcr.suprnova.cc:2252)
23:03:58:173 33c got 107 bytes
23:03:58:173 33c buf: {"error": null, "id": 1, "result": [["mining.notify", "1b2888e9ff6c4cf1ae113322ad37d930"], "08001443", 4]}

23:03:58:189 33c parse packet: 99
23:03:58:189 33c new buf size: 0
23:03:58:220 131c got 591 bytes
23:03:58:220 131c buf: {"error": null, "id": 1, "result": [["mining.notify", "ae6812eb4cd7735a302a8a9dd95cf71f"], "00000000f8000752f8000752", 12]}
{"params": [1], "id": null, "method": "mining.set_difficulty"}
{"params": ["8c", "931c82a0a9dbbe2d06f3dabd121b279fd581d5fbff2d4d8a0000088800000000", "ca3750d31f2611f45e94488a4bf6844ad842eca4c677edb25582dc43094aeaafa4c928a58668058ac63e946fb81e71f8a7256fea6e4df42a91929135fdb6dfe40100155dea317971050002004ba60000d6091d1adb11556d00000000395f0000ff150000d6c226570000000000000000", "", [], "01000000", "1a1d09d6", "5726c2d6", true], "id": null, "method": "mining.notify"}

23:03:58:220 131c parse packet: 116
23:03:58:220 131c remove first packet 449
23:03:58:220 131c new buf size: 449
23:03:58:220 131c parse packet: 58
23:03:58:235 131c remove first packet 391
23:03:58:235 131c new buf size: 391
23:03:58:235 131c parse packet: 391
23:03:58:235 131c new buf size: 0
23:03:58:329 33c got 342 bytes
23:03:58:329 131c got 82 bytes
23:03:58:329 33c buf: { "id": null, "method": "mining.set_difficulty", "params": [55000]}
{"params": ["7178", "0xddf13e0d55b3a4f9951c662550853b13bd58bece9373fb7d533c4709fad16271","0x17a7217f2673ce6267021cc82e7b328a755f010d6741bde6c25d3c2b0373e989","0x00000001310A508148DF1ECB62908D334643D83B47C1251FE95C3C06679770B6", true], "id": null, "method": "mining.notify"}

23:03:58:329 131c buf: {"error": null, "id": 5, "result": true}
{"error": null, "id": 2, "result": true}

23:03:58:345 33c parse packet: 62
23:03:58:345 131c parse packet: 36
23:03:58:360 33c remove first packet 267
23:03:58:360 131c remove first packet 36
23:03:58:360 33c new buf size: 267
23:03:58:360 131c new buf size: 36
23:03:58:360 33c parse packet: 267
23:03:58:376 131c parse packet: 36
23:03:58:376 33c eth: job changed
23:03:58:376 131c DCR: Authorized
23:03:58:376 33c new buf size: 0
23:03:58:376 131c new buf size: 0
23:03:58:454 97c Setting DAG epoch #48...
23:03:58:532 33c got 101 bytes
23:03:58:532 33c buf: {"error": null, "id": 2, "result": true}
{ "id": 9876, "method": "client.get_version", "params": []}

23:03:58:532 33c parse packet: 36
23:03:58:532 33c ETH: Authorized
23:03:58:532 33c remove first packet 54
23:03:58:532 33c new buf size: 54
23:03:58:532 33c parse packet: 54
23:03:58:548 33c send: {"error": null, "id": 9876, "result": "eth 1.0"}

23:03:58:548 33c new buf size: 0
23:03:59:673 97c Setting DAG epoch #48 for GPU #4
23:03:59:673 12dc Setting DAG epoch #48 for GPU #3
23:03:59:673 1238 Setting DAG epoch #48 for GPU #2
23:03:59:673 c94 Setting DAG epoch #48 for GPU #0
23:03:59:673 1244 Setting DAG epoch #48 for GPU #1
23:03:59:673 97c Create GPU buffer for GPU #4
23:03:59:673 12dc Create GPU buffer for GPU #3
23:03:59:673 1238 Create GPU buffer for GPU #2
23:03:59:689 c94 Create GPU buffer for GPU #0
23:03:59:689 1244 Create GPU buffer for GPU #1
23:03:59:767 97c GPU 4, OpenCL error -48 - cannot create DAG on GPU
23:03:59:767 1238 GPU 2, OpenCL error -48 - cannot create DAG on GPU
23:03:59:767 c94 GPU 0, OpenCL error -48 - cannot create DAG on GPU
23:03:59:829 12dc GPU 3, OpenCL error -48 - cannot create DAG on GPU
23:03:59:845 1244 GPU 1, OpenCL error -48 - cannot create DAG on GPU
23:04:01:048 e9c OC v6, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst
23:04:01:064 e9c OC v6, Reset control for GPU 6, close miner right now if you want to use default control from Catalyst
23:04:01:064 e9c OC v6, Reset control for GPU 12, close miner right now if you want to use default control from Catalyst
23:04:01:064 e9c OC v6, Reset control for GPU 18, close miner right now if you want to use default control from Catalyst
23:04:01:079 e9c OC v6, Reset control for GPU 24, close miner right now if you want to use default control from Catalyst


Probably you use "Data.bin" file from v3.x version.

Please read Readme and FAQ in the first post of this thread before asking any questions, probably the answer is already there.
List of my miners: https://bitcointalk.org/index.php?topic=3019607
osnwt
Sr. Member
****
Offline Offline

Activity: 353
Merit: 251


View Profile
May 02, 2016, 10:34:01 AM

Claymore, sorry, still about missing shares @ethermine with -esm 1.  Doubled hashrate seen only after miner start, then it stabilizes to the real. But still no share info. What should I find in miner logs to find out why? What's the protocol difference, can you help? Not say it is very important (no rejected shares for me), but nice to see the number of shares found.
Claymore
Donator
Legendary
*
Offline Offline

Activity: 1610
Merit: 1325

Miners developer


View Profile
May 02, 2016, 10:57:35 AM

Claymore, sorry, still about missing shares @ethermine with -esm 1.  Doubled hashrate seen only after miner start, then it stabilizes to the real. But still no share info. What should I find in miner logs to find out why? What's the protocol difference, can you help? Not say it is very important (no rejected shares for me), but nice to see the number of shares found.

Well, I can only repeat what I said before.
Start this (only change wallet address, nothing else, don't remove/change ".sample" after wallet address):

EthDcrMiner64.exe -epool us1.ethermine.org:4444 -ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F.sample -epsw x -esm 1

Wait for 30 minutes. See stats for rig "sample". That is all.

Please read Readme and FAQ in the first post of this thread before asking any questions, probably the answer is already there.
List of my miners: https://bitcointalk.org/index.php?topic=3019607
osnwt
Sr. Member
****
Offline Offline

Activity: 353
Merit: 251


View Profile
May 02, 2016, 11:38:10 AM
Last edit: May 02, 2016, 12:03:37 PM by osnwt

This sample works (with changed wallet and worker name)!
Now I will try to determine what's wrong with my command line. First I suspect is different pool (I use eu1 instead of us1). Anyway, thank you, now I know that miner works, and I know where to dig.

EDIT: eu1 pool works as well. It seems to me that's the matter of parameters order in the command line. I used a bit different order, and it never worked for share stats reporting. I used your cmdline, replaced with my wallet/rig names, changed pool to eu1, added some -etha in the end (my two identical 7950 cards like different -etha values), and it works, now shares are shown. Great!
Pages: « 1 ... 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 [71] 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 ... 1431 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!