Pages:
Author

Topic: More Epochs mod v1.1 for Claymore ETH miner 15. Epochs 385+ work, New Version! - page 6. (Read 5810 times)

newbie
Activity: 17
Merit: 0
any indicative hashrate with 4 gb cards  rx 470/570?

If you pair them in a system with a 8GB 470/570 then they will mine but at a reduced hashrate. Best I could get on my 470 4gb cards was 11 MH/s using 1.5

anybody here can tell me with the R9 390 8gb WHAT IS THE actual AVERAGE hashrate for ETH? ...using what miner and overclocked or not? ill appreciate that info!!! thanks
sr. member
Activity: 450
Merit: 255
any indicative hashrate with 4 gb cards  rx 470/570?

If you pair them in a system with a 8GB 470/570 then they will mine but at a reduced hashrate. Best I could get on my 470 4gb cards was 11 MH/s using 1.5
jr. member
Activity: 325
Merit: 2
hi
in Iran dev fee doesn't work properly

all miner work good except this miner

DevFee: ETH: Stratum - connecting to 'eu1.ethermine.org' <172.65.207.106> port 5555 (SSL/TLS)
ETH: 02/03/21-14:28:52 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.800 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.793 Mh/s, GPU1 38.815 Mh/s, GPU2 38.772 Mh/s, GPU3 30.420 Mh/s
ETH: 02/03/21-14:28:56 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.858 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.793 Mh/s, GPU1 38.836 Mh/s, GPU2 38.828 Mh/s, GPU3 30.401 Mh/s
ETH: 02/03/21-14:28:59 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.748 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.806 Mh/s, GPU1 38.773 Mh/s, GPU2 38.751 Mh/s, GPU3 30.419 Mh/s
ETH: 02/03/21-14:28:59 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.748 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.806 Mh/s, GPU1 38.773 Mh/s, GPU2 38.751 Mh/s, GPU3 30.419 Mh/s
ETH: 02/03/21-14:29:03 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.870 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.783 Mh/s, GPU1 38.834 Mh/s, GPU2 38.818 Mh/s, GPU3 30.435 Mh/s
ETH: 02/03/21-14:29:07 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.793 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.793 Mh/s, GPU1 38.794 Mh/s, GPU2 38.772 Mh/s, GPU3 30.434 Mh/s
ETH: 02/03/21-14:29:09 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.643 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.784 Mh/s, GPU1 38.764 Mh/s, GPU2 38.726 Mh/s, GPU3 30.370 Mh/s
ETH: 02/03/21-14:29:09 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.643 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.784 Mh/s, GPU1 38.764 Mh/s, GPU2 38.726 Mh/s, GPU3 30.370 Mh/s
ETH: Stratum - Cannot connect to eu1.ethermine.org:5555
DevFee: ETH: Stratum - Failed to connect, retry in 20 sec...

hi, probably ssl port 5555 is closed by your internet provider. If you are mining to ethermine, original miner would try to use ssl connection to mine
devfee there too. I can change this in next versions of the mod if you won't be able to solve the problem with port 5555 on your side.

did you solve issue with closed 5555 port? I'll release new version soon with workaround.
jr. member
Activity: 325
Merit: 2
any indicative hashrate with 4 gb cards  rx 470/570?

4 gb GPUs aren't supported due to lack of video memory for holding 4+ gb DAG for current and future epochs.
member
Activity: 476
Merit: 19
any indicative hashrate with 4 gb cards  rx 470/570?
jr. member
Activity: 325
Merit: 2
New Version just released!

More Epochs mod v1.5 for Claymore Eth Miner v15

Changelog:

~ Fixed issue with incorrect shares on Navi AMD GPUs. Other AMD GPUs will be addressed in next versions of the mod.

If you don't use AMD Navi GPUs, you can stay on older versions of the mod.
jr. member
Activity: 325
Merit: 2
hi
in Iran dev fee doesn't work properly

all miner work good except this miner

DevFee: ETH: Stratum - connecting to 'eu1.ethermine.org' <172.65.207.106> port 5555 (SSL/TLS)
ETH: 02/03/21-14:28:52 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.800 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.793 Mh/s, GPU1 38.815 Mh/s, GPU2 38.772 Mh/s, GPU3 30.420 Mh/s
ETH: 02/03/21-14:28:56 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.858 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.793 Mh/s, GPU1 38.836 Mh/s, GPU2 38.828 Mh/s, GPU3 30.401 Mh/s
ETH: 02/03/21-14:28:59 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.748 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.806 Mh/s, GPU1 38.773 Mh/s, GPU2 38.751 Mh/s, GPU3 30.419 Mh/s
ETH: 02/03/21-14:28:59 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.748 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.806 Mh/s, GPU1 38.773 Mh/s, GPU2 38.751 Mh/s, GPU3 30.419 Mh/s
ETH: 02/03/21-14:29:03 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.870 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.783 Mh/s, GPU1 38.834 Mh/s, GPU2 38.818 Mh/s, GPU3 30.435 Mh/s
ETH: 02/03/21-14:29:07 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.793 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.793 Mh/s, GPU1 38.794 Mh/s, GPU2 38.772 Mh/s, GPU3 30.434 Mh/s
ETH: 02/03/21-14:29:09 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.643 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.784 Mh/s, GPU1 38.764 Mh/s, GPU2 38.726 Mh/s, GPU3 30.370 Mh/s
ETH: 02/03/21-14:29:09 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.643 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.784 Mh/s, GPU1 38.764 Mh/s, GPU2 38.726 Mh/s, GPU3 30.370 Mh/s
ETH: Stratum - Cannot connect to eu1.ethermine.org:5555
DevFee: ETH: Stratum - Failed to connect, retry in 20 sec...

hi, probably ssl port 5555 is closed by your internet provider. If you are mining to ethermine, original miner would try to use ssl connection to mine
devfee there too. I can change this in next versions of the mod if you won't be able to solve the problem with port 5555 on your side.
newbie
Activity: 2
Merit: 0
hi
in Iran dev fee doesn't work properly

all miner work good except this miner

DevFee: ETH: Stratum - connecting to 'eu1.ethermine.org' <172.65.207.106> port 5555 (SSL/TLS)
ETH: 02/03/21-14:28:52 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.800 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.793 Mh/s, GPU1 38.815 Mh/s, GPU2 38.772 Mh/s, GPU3 30.420 Mh/s
ETH: 02/03/21-14:28:56 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.858 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.793 Mh/s, GPU1 38.836 Mh/s, GPU2 38.828 Mh/s, GPU3 30.401 Mh/s
ETH: 02/03/21-14:28:59 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.748 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.806 Mh/s, GPU1 38.773 Mh/s, GPU2 38.751 Mh/s, GPU3 30.419 Mh/s
ETH: 02/03/21-14:28:59 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.748 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.806 Mh/s, GPU1 38.773 Mh/s, GPU2 38.751 Mh/s, GPU3 30.419 Mh/s
ETH: 02/03/21-14:29:03 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.870 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.783 Mh/s, GPU1 38.834 Mh/s, GPU2 38.818 Mh/s, GPU3 30.435 Mh/s
ETH: 02/03/21-14:29:07 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.793 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.793 Mh/s, GPU1 38.794 Mh/s, GPU2 38.772 Mh/s, GPU3 30.434 Mh/s
ETH: 02/03/21-14:29:09 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.643 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.784 Mh/s, GPU1 38.764 Mh/s, GPU2 38.726 Mh/s, GPU3 30.370 Mh/s
ETH: 02/03/21-14:29:09 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 137.643 Mh/s, Total Shares: 158, Rejected: 0, Time: 01:20
ETH: GPU0 29.784 Mh/s, GPU1 38.764 Mh/s, GPU2 38.726 Mh/s, GPU3 30.370 Mh/s
ETH: Stratum - Cannot connect to eu1.ethermine.org:5555
DevFee: ETH: Stratum - Failed to connect, retry in 20 sec...
jr. member
Activity: 325
Merit: 2
newbie
Activity: 17
Merit: 0
New Version just released!

miner star fine with my "Hawaii", hashing at 15.4mh/s in ethermine.org:5555(ssl) using all the server pool locations, but after some minutes realize that none share was submitted , then , get this red messsage "GOT INCORRECT SHARE, IF YOU SEE THIS WARNING OFTEN, MAKE SURE YOU DID NOT OVERCLOCK IT TOO MUCH!" ... am using Adrenalin-2020-20.11.2 with my Gigabyte R9 390 8gb

R9 390 is not supported now, it should not work.
seems to be a communication issue with server ... or maybe, a bottleneck between the creation of shares and the moment to be sent... it start juts as you told, showing the green message... create the DAG ok (4120mb for 387) ...and star showing the hash speed... but after waiting almost 30minutes, realize that not even 1share was submitted,(even getting several "new jobs")... then i saw that red message told before... HOPE this data can give you any idea! .... thanks so much for your good work... YOU ARE THE ONE!

Thank you, but I repeat, currently 390 is not supported, so it won't find shares.

hi, hope your fine.
ok, so the question is... have you the plan to make support for R9 390 8GB (HAWAII) or not? .. .thanks

Hello, thanks I'm fine, just busy investigating the issue with rejected shares for AMD gpus. If I'll solve the problem, I will try to add support for 390.
thanks, ill be waiting anxiously.. .good vibes!
jr. member
Activity: 325
Merit: 2
I upgraded to AMD driver 20.7.2 and while I now can get it to run with my RX580's and Vega56, I'm having the exact same problem as batsonxl - if I have straps set to 1 or whichever straps I'd previously used, the whole rig crashes the moment it tries to applies the straps. If I set it to 0, it will start up and run, but probably with around a 35% reduction in hashrate as the straps aren't being applied. Hopefully straps can get working again for AMD's? Thanks

With -straps 0 do you have accepted shares? Do you have shares that didn't pass check on CPU? ("got incorrect share" message in log file)

About crashing with -straps 1. The miner uses heavily protected custom kernel-mode driver to apply straps and it looks like it's not compatible with new amd gpu drivers. I think the only realistic solution for me is to use some 3rd party driver to apply straps instead of default miner's driver. Still this will require a lot of researching and therefore time.

Thanks for your hard work,
If claymore will NOT work with straps then there is no point to use it. i used clay only because of this, with 3rd party software all miner works fast, the point is claymore was single miner with all settings you need, make bat file thats it.you dont need oc software or mod the bios.

Thanks. That makes sense, let's hope problem will be solved.
jr. member
Activity: 325
Merit: 2
I upgraded to AMD driver 20.7.2 and while I now can get it to run with my RX580's and Vega56, I'm having the exact same problem as batsonxl - if I have straps set to 1 or whichever straps I'd previously used, the whole rig crashes the moment it tries to applies the straps. If I set it to 0, it will start up and run, but probably with around a 35% reduction in hashrate as the straps aren't being applied. Hopefully straps can get working again for AMD's? Thanks

With -straps 0 do you have accepted shares? Do you have shares that didn't pass check on CPU? ("got incorrect share" message in log file)

About crashing with -straps 1. The miner uses heavily protected custom kernel-mode driver to apply straps and it looks like it's not compatible with new amd gpu drivers. I think the only realistic solution for me is to use some 3rd party driver to apply straps instead of default miner's driver. Still this will require a lot of researching and therefore time.



With -straps 0 yes I get accepted shares, but I would say about 1/2 -2/3 are "incorrect share". I've also tried stock clock settings instead of overclock since my OC's were set using the original straps, but even at stock clocks I still get mostly "incorrect shares" so my effective hash is probably 1/3 of what it used to be. Is this something you think you'll be able to get working, or should I look at using a different miner for my AMD's?

I see, I'm working on solution to get rid of incorrect shares for AMD Gpus. If you have many incorrect shares for your AMD Gpu and some other miner works well for you,  of course you should use it. When I'll solve the problem I will release new version of my mod (probably as separate release for AMD Gpus because Nvidia Gpus work fine already) and you will be able to test it and decide what is best for you.
member
Activity: 1196
Merit: 26
I upgraded to AMD driver 20.7.2 and while I now can get it to run with my RX580's and Vega56, I'm having the exact same problem as batsonxl - if I have straps set to 1 or whichever straps I'd previously used, the whole rig crashes the moment it tries to applies the straps. If I set it to 0, it will start up and run, but probably with around a 35% reduction in hashrate as the straps aren't being applied. Hopefully straps can get working again for AMD's? Thanks

With -straps 0 do you have accepted shares? Do you have shares that didn't pass check on CPU? ("got incorrect share" message in log file)

About crashing with -straps 1. The miner uses heavily protected custom kernel-mode driver to apply straps and it looks like it's not compatible with new amd gpu drivers. I think the only realistic solution for me is to use some 3rd party driver to apply straps instead of default miner's driver. Still this will require a lot of researching and therefore time.



Thanks for your hard work,
If claymore will NOT work with straps then there is no point to use it. i used clay only because of this, with 3rd party software all miner works fast, the point is claymore was single miner with all settings you need, make bat file thats it.you dont need oc software or mod the bios.
newbie
Activity: 11
Merit: 1
I upgraded to AMD driver 20.7.2 and while I now can get it to run with my RX580's and Vega56, I'm having the exact same problem as batsonxl - if I have straps set to 1 or whichever straps I'd previously used, the whole rig crashes the moment it tries to applies the straps. If I set it to 0, it will start up and run, but probably with around a 35% reduction in hashrate as the straps aren't being applied. Hopefully straps can get working again for AMD's? Thanks

With -straps 0 do you have accepted shares? Do you have shares that didn't pass check on CPU? ("got incorrect share" message in log file)

About crashing with -straps 1. The miner uses heavily protected custom kernel-mode driver to apply straps and it looks like it's not compatible with new amd gpu drivers. I think the only realistic solution for me is to use some 3rd party driver to apply straps instead of default miner's driver. Still this will require a lot of researching and therefore time.



With -straps 0 yes I get accepted shares, but I would say about 1/2 -2/3 are "incorrect share". I've also tried stock clock settings instead of overclock since my OC's were set using the original straps, but even at stock clocks I still get mostly "incorrect shares" so my effective hash is probably 1/3 of what it used to be. Is this something you think you'll be able to get working, or should I look at using a different miner for my AMD's?
jr. member
Activity: 325
Merit: 2
I upgraded to AMD driver 20.7.2 and while I now can get it to run with my RX580's and Vega56, I'm having the exact same problem as batsonxl - if I have straps set to 1 or whichever straps I'd previously used, the whole rig crashes the moment it tries to applies the straps. If I set it to 0, it will start up and run, but probably with around a 35% reduction in hashrate as the straps aren't being applied. Hopefully straps can get working again for AMD's? Thanks

With -straps 0 do you have accepted shares? Do you have shares that didn't pass check on CPU? ("got incorrect share" message in log file)

About crashing with -straps 1. The miner uses heavily protected custom kernel-mode driver to apply straps and it looks like it's not compatible with new amd gpu drivers. I think the only realistic solution for me is to use some 3rd party driver to apply straps instead of default miner's driver. Still this will require a lot of researching and therefore time.

jr. member
Activity: 325
Merit: 2
New Version just released!

miner star fine with my "Hawaii", hashing at 15.4mh/s in ethermine.org:5555(ssl) using all the server pool locations, but after some minutes realize that none share was submitted , then , get this red messsage "GOT INCORRECT SHARE, IF YOU SEE THIS WARNING OFTEN, MAKE SURE YOU DID NOT OVERCLOCK IT TOO MUCH!" ... am using Adrenalin-2020-20.11.2 with my Gigabyte R9 390 8gb

R9 390 is not supported now, it should not work.
seems to be a communication issue with server ... or maybe, a bottleneck between the creation of shares and the moment to be sent... it start juts as you told, showing the green message... create the DAG ok (4120mb for 387) ...and star showing the hash speed... but after waiting almost 30minutes, realize that not even 1share was submitted,(even getting several "new jobs")... then i saw that red message told before... HOPE this data can give you any idea! .... thanks so much for your good work... YOU ARE THE ONE!

Thank you, but I repeat, currently 390 is not supported, so it won't find shares.

hi, hope your fine.
ok, so the question is... have you the plan to make support for R9 390 8GB (HAWAII) or not? .. .thanks

Hello, thanks I'm fine, just busy investigating the issue with rejected shares for AMD gpus. If I'll solve the problem, I will try to add support for 390.
newbie
Activity: 11
Merit: 1
I upgraded to AMD driver 20.7.2 and while I now can get it to run with my RX580's and Vega56, I'm having the exact same problem as batsonxl - if I have straps set to 1 or whichever straps I'd previously used, the whole rig crashes the moment it tries to applies the straps. If I set it to 0, it will start up and run, but probably with around a 35% reduction in hashrate as the straps aren't being applied. Hopefully straps can get working again for AMD's? Thanks
newbie
Activity: 17
Merit: 0
New Version just released!

miner star fine with my "Hawaii", hashing at 15.4mh/s in ethermine.org:5555(ssl) using all the server pool locations, but after some minutes realize that none share was submitted , then , get this red messsage "GOT INCORRECT SHARE, IF YOU SEE THIS WARNING OFTEN, MAKE SURE YOU DID NOT OVERCLOCK IT TOO MUCH!" ... am using Adrenalin-2020-20.11.2 with my Gigabyte R9 390 8gb

R9 390 is not supported now, it should not work.


seems to be a communication issue with server ... or maybe, a bottleneck between the creation of shares and the moment to be sent... it start juts as you told, showing the green message... create the DAG ok (4120mb for 387) ...and star showing the hash speed... but after waiting almost 30minutes, realize that not even 1share was submitted,(even getting several "new jobs")... then i saw that red message told before... HOPE this data can give you any idea! .... thanks so much for your good work... YOU ARE THE ONE!

Thank you, but I repeat, currently 390 is not supported, so it won't find shares.

hi, hope your fine.
ok, so the question is... have you the plan to make support for R9 390 8GB (HAWAII) or not? .. .thanks
jr. member
Activity: 325
Merit: 2

As you can see GPU reports 8192 MB of vram, but other api call returned value of 4048 MB which is not enough for 4.03 GB Dag.
The situation probably happens with specific models of GPUs or with certain version of drivers.

Can you check your .log file to see if there is same problem? Also what is your OS (Win7/Win10) and AMD driver version?

I checked my log and it is the exact same. Do you know what driver that person was using? I'm using version 20.4.1 on Win 10. It will likely be another week or two and I should be able to try loading new drivers.


So just trying this out on my 8GB Sapphire RX580 and it tells me it can't load the DAG because it's too large. This is odd because it's an 8GB card. Is there some parameter I am missing? Well I just re-read the post above and since I have same type of card, that might be the same issue..

The problem is in AMD drivers, you can read more here https://github.com/ethereum-mining/ethminer/issues/1966, the solution is here https://github.com/ethereum-mining/ethminer/issues/1966#issuecomment-663826059

So you need newer AMD driver, 20.7.2 or later. Then GPU will be able to allocate more than 4gb of vram in single chunk.
jr. member
Activity: 325
Merit: 2

As you can see GPU reports 8192 MB of vram, but other api call returned value of 4048 MB which is not enough for 4.03 GB Dag.
The situation probably happens with specific models of GPUs or with certain version of drivers.

Can you check your .log file to see if there is same problem? Also what is your OS (Win7/Win10) and AMD driver version?
I checked my log and it is the exact same. Do you know what driver that person was using? I'm using version 20.4.1 on Win 10. It will likely be another week or two and I should be able to try loading new drivers.

No, I don't know his driver version. But you told me your driver version, so I will check if this version will give me wrong vram size too.


So just trying this out on my 8GB Sapphire RX580 and it tells me it can't load the DAG because it's too large. This is odd because it's an 8GB card. Is there some parameter I am missing? Well I just re-read the post above and since I have same type of card, that might be the same issue..

Yes, probably same issue. If I'll find the workaround I'll inform about it here.
Pages:
Jump to: