|
On nicehash pool many rejects "Error code: 2 - job not found." Can it be fixed?
|
|
|
|
|
On my 580 8Gb (Hynix) b-sync didn't give stable max speed even after 20-30 minutes after start. Speed became more stable but not max at least at one GPU. On 1st 5-10 minutes during warmup speed sometimes max sometime not... But I can't test more than 30-40 minutes because 1 of GPU's stops mine at all...
Returning to b7 or maybe b4 - it gives lower maxspeed but higher effective hashrate - it's better than all other versions I think...
Will try to do more tests on b7 before returning to b4...
P.S. Still can't find optimal multihash for my 270X 4Gb (3,5Gb OpenCL) on heavy algo. Max I can use is 2 threads with 1 - 448 and 2nd - 432. But speed is always fluctuate from 410 to 500 h/s. If I use 2x432 m.h. speed is almost 415-420 h/s. Is there some way to stabilize speed on 2 threads with different multi_hash?
|
|
|
|
good, this time i'm on the good way, and that's probably the same as srb found. i released first so no question whether i hacked it.
i think i found the locked thread bug, i'll release a fix soon, i wait for more feedback from other users (unless i really have three).
Yes, one of GPU stops to mine... 3rd time it happens... |
|
|
|
forget the b7 and try the new experimental (read: very untested) B-sync GPU
That's the lone .exe in the github page.
1. Stable and fast hashrate
2. new parameter --no-monitor to disable fan/temp monitoring (the purple report)
3. various optims for some cards and some algos, expect about +0.5%
4. Fees still 0.9%
so far it burns like fire on my rigs, i hope it really fixes all the hashrate and warmup problems.
Thanks! Now testing new version. EDIT: It's strange, but one of my RX 580 8Gb just stops sometime to mine. Speed is 0, voltage and clocks on minimum state. It's not stuck, just stopped... Warmup phase is still needed. On my 580 cards max speed didn't archived after start... |
|
|
|
sure i'll make a new experimental for both of you, the sync for Unclwish and a param --no-monitor to disable the gpu monitoring (similar to --no-adl in xmrstak)
the power draw on v8 is an order of magnitude more complex to fix than the sync, i admit TeamRed will be very hard to beat, but i think i know how.
Would you be able to do it on b4? b-x, b-y and b-z are more prone to the crashing issue. On b4 I can mine for about 12h. On b-z sometimes can manage calculate only one share accepted (about 5min) before the crash. Did you tried b7 version? |
|
|
|
@unclwish: i'm getting pretty good results on the new-new-new sync, an experimental release is possible in less than a day. I give up my hybrid option, i'll make it automatic (enabled on HD7000/6000, disabled otherwise)
Excellent! I'm waiting to test it! And what about v8 high power draw? You wrote that you have thoughts to lower it... |
|
|
|
Hey Dev, Abort was called at 767 line in file:
D:\qb\workspace\19992\src\vpg-compute-neo\runtime\os_interface\windows\wddm.cpp I have no clue !! Cards : Vega 64 Windows : 10 Driver : 18.6.1 JCE : b6 version Use directory with miner on path only with latin symbols... |
|
|
|
a new version? sure, here's the 0.33g CPU Linux re-release Fixed JSON timer
FreeHaven coin correctly defaults to FreeHaven fork
then I go back to GPU sync fixes. ok but where is GPU version with lower fee? Srb miner have better HR and smaller devfee on all algo (no in v8) JCE x-y version have 0,9% devfee on all GPU algo's. Hmmm, looks llike doctor83 can do that: "Ok, so looks like i finally resolved the ellesmere 8gb heavy algos thing. Now they easily hash over 1.1khs. New version in a few days" |
|
|
|
|
JCE, any news about new version? Heavy algo speed stabilization and lowering power draw on v8 is very needed!
|
|
|
|
Здpaвcтвyйтe. Бyдeт paбoтaть нa hd7850 c 1гб  нa v7 370-400h кoпaли. Почти также должна копать и на v8. |
|
|
|
|
Authors, did you plan to add old cards support such as Pitcairns (270, 370), Tahiti (280) and so on?
|
|
|
|
That's about HD6990 but that's a dual HD6970, the results on a HD6950 should be around 240.
Thanks. Method to restore maximum heavy algo speed after speed drop often works. Just quick pressing 8 times number of GPU on which speed droped can restore it! It's strange that quick pause\unpause GPU 4 times in row can do that... |
|
|
|
Дык пoэтoмy я и cпpaшивaю, ecть ли cмыcл cтaвить win 10 и иcпoльзoвaть Baш мaйнep? У мeня 250 h/s, нa Baшeм бoльшe?
He знaю. Boзмoжнo и нeт. Taм вoн y чeлoвeкa бoльшe 113 нe пoлyчaeтcя нa 6950... Haдo выяcнить, cкoлькo JCE нa 6950 дoлжeн выдaвaть... JCE, how much h/s your miner must give on HD6950 ? Did you test this card? |
|
|
|
|
It's strange... Can you provide screenshots of 1st and 2nd tabs GPU-Z? And GPU Caps Viewer - OpenCL tab...
Looks like for OpenCL this card have less than 2Gb vmemory...
try this set:
"gpu_threads_conf" :
[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 240},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 240},
],
wait about 10 minutes to look real speed. At start speed maybe low.
|
|
|
|
Yes i'm on W8.1 My 6950 got 2Gb ram I'm mining V8 cryptonight the lastest fork ... So, it's hash a little now, my config parameters sucks. I'm testing on 33B6 and with this "jce_cn_gpu_miner64.exe Experimental boost ~2% for HD6000/7000" I've try a lot of parameters, but get not more than 100/113 h/s  It's crash when i up "multi_hash" value more than 240 That's the best result i can get with this config "gpu_threads_conf" : [ { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash":240}, ], if i try Worksize 16/32 i can't UP than 240 thread. Did u have some values i can try ? because i've try a lot of combination but can't reach more hashrate, driver crash. i didn't understand whats that 2 values (alpha" : 64, "beta" : 8 ) ? The most curious it was, if i didn't OC my card like @910/1250 driver crash instantanetly when i start miner. in 800/1250 or 830/1250 driver crash. With all same values in config.txt . Wtf hell !!!   I've try on each card on different PC (don't have a rig) 3 different PC. Thx for helping.  Try to use double threads this way: "gpu_threads_conf" : [ { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 224}, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 224}, ], also try this config: "gpu_threads_conf" : [ { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 464}, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 464}, ], or "gpu_threads_conf" : [ { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 448}, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 448}, ], or "gpu_threads_conf" : [ { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 432}, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 432}, ], |
|
|
|
I've a new idea to workaround this, and using the hybrid as a side-effect is a failure, hence why I stayed on the experimental version until I succedded or gave up. Need a new cycle of trial-and-error. Online is the 0.33g CPU Windows (linux to come next) CN-FreeHaven fork
MoneroOcean feature "algo_perf" available
Updated doc
Good! And think please about lowering power consumption on v8 algo... |
|
|
|
it's an idea, but as a workaround. I really want to have the hashrate just stable, with no tricks involved.
Once i'm done with the new CPU version i go back to this problem as top priority.
Hey JCE I figured out a manual fix to get those rx 580 cards to hash at max speeds on Heavy and be stable, any time i see one that has lost the max speed, i pause/unpause 4 times each (8 button pushes) in quick succession and the card comes back to maximum speed. May be something like this can be coded into the miner? Test it on RX 580 8G - miner launched 5+ hours. 1st Gpu runs at full speed, 2nd speed drops. Tried your method on 2nd GPU - speed didn't changes. EDIT: Yes, sometimes it works... But not everytime... |
|
|
|
the logs are disabled by default, but in such case there would probably be zero hint in the log. Online is the 0.33 GPU B-ZLike b-y but more of the same: * Still more hybrid
* Mix of the b5 and the by
* Fees still at 0.9%
So speed on big RX is not restored? Speed on RX 588 is high and not stable. But from all previous versions speed is maximum(like b5) and most stable when mining lasts long time... Who used b5 version - recommend to change it to b-z. |
|
|
|
|
JCE, can you make 33b5 version with devfee 0.9%? b5 looks best on heavy for my 588 cards... better b-y version...
On b5 speed fluctuations some time drops speed - and some time up it. On b-y version after 10-15 minutes speed srops and never up...
|
|
|
|
Online is the 0.33b-y* A lot less tested than a regular version, i hope there's no bugs out there * Fees lowered back to 0.9% on all algos, as I'm no longer 20% faster than the reference code * More hybrid, so should eat a bit more CPU * Bad shares on Heavy fixed, at least i had zero during my 5-hour test session * Light optim ~2% for HD7000 is backported to HD6000 * It was more stable on my rig, but i'm doubting of such observations That's the standalone .exe on Github, as for the previous b-x I'm become crazy , i've 3 PC and ALL Crash, with 14.4 driver and 6950HD, i've allready post my config. Could u help me ? i'm very glad to fee you my hash I must use this 14.4 driver with your miner ? i'm the only one who have problem with 6950. You must have Windows 8.1+. What config you're using? What amount of video memory your cards have? And what algo you what to mine? |
|
|
|
|
Show Posts
