|
What about video memory stripes? Does video bios mods for cryptonight v7/heavy would be good for V8?
|
|
|
|
Hi! The Windows Monero v8 CPU version is out!https://github.com/jceminer/cn_cpu_minerversion 0.33a I expect it to be the very fastest on 32-bits and non-aes, and in a lesser extent in 64-bits AES, the major assembly. The Linux build comes next, then i focus on GPU, i'm getting very late now. I read the report about the bad OpenCL. JCE openCL is generated, unlike SRB which is precompiled or stak which is static. It allows wider optim support but in case of failed build, which is very possible with generated code, please give the GPU detection log that is displayed at start, so at least i know what GPU you use. I tested the current code (the future v8-capable) on AMD HD7000, RX, Vega and even Intel Graphics, and it compiles. I expect the failure to be caused by a different GPU or different driver version that i tested on. However i still do very little support for now, must stay on the v8 support. edit: The Linux Monero v8 CPU version is out too!Thanks for your hard work! Now you must focus on GPU v8 version. |
|
|
|
Hi JCE, i updated my 3 Rigs to JCE Miner. It works great, effective hash increase, but i have a problem.  At around 3:30 o´clock all 3 rigs deliver stale shares for around 1.5 hours, 5 days in a row. Other people in this pool don´t have this problem, other miner (for example SRB) don´t have this problem. If it is on 1 Rig then i say ok to much OC, but 3 realy different rigs with different cards and different drivers make the same problem? i think it is a jce miner problem. A Ryzen R5 1600 delivers also stales shares and with the older version 0.32m it works. I use jce 0.32q at the moment. Any solution or other guys with this problem? JCE there is a problem in your code or something like this. Rig1 with JCE 0.32q mining on nanopool normal port -> all fine Rig2 with SRB 1.6.7 mining on nanopool ssl port -> all fine Rig3 wtih JCE 0.32q mining on nanopool ssl port -> from 3:30 to around 5 o´clock only stale shares, tested 3 days in a row Test GPU with JCE 0.32q mining on nanopool ssl port -> from 3:30 to around 5 o´clock only stale shares, tested 3 days in a row I'm use ssl port on nicehash pool with CPU and GPU on 0.32q without any issues during several days in a row. Maybe nanopool did something with ssl port in your pointed time? |
|
|
|
Your miner with CN-heavy is solid ! I have better hashrate on 24avg than cnv7 !
Speed of heavy algo on 8Gb+ cards allways faster than on V7. It's normal. |
|
|
|
I've got a problem with the warm-up on my RX580s, not all cards in a sistem end up at full optimal speed after the warmup on heavy/haven/saber. This happens even if I have gpu-z in the background (which adds another 15h/s per card fluctuation after the warmup). I am on "p" version right now, on "n" version I thought it did much better, but wanted to use refined watchdog and get a small boost in mining speed with the latest version. What am I doing wrong?
I use 976 intensity, happens with lower intensity too. If I turn off a card that has optimal speed after warmup, and turn it back on, it has 15% less speed and doesn't get back up to optimal. Something needs to be reworked in the handling of the warmup, I also see a VRAM cluttering, an 8gb cards ends up showing it has 11gb of vram used in gpu-z (maybe bug?). Maybe we need some way to flush the vram and this is what's causing it, especially for those that restart the miner quite often (automatic profit switchers).
What system and drivers you're use? On Windows 10 and latest drivers max intensity on heavy is 944. Even 960 gives significant drop in speed. So as launched GPU-Z... It didn't add speed, but it can decrease it... I am on Win10 1709 + blockchain beta drivers. I'm understand now... On latest 1803 launching GPU-Z didn't nothing except freezes during mining... And on latest driver max stable intensity is 944 on heavy algo and 8Gb vmem... |
|
|
|
I've got a problem with the warm-up on my RX580s, not all cards in a sistem end up at full optimal speed after the warmup on heavy/haven/saber. This happens even if I have gpu-z in the background (which adds another 15h/s per card fluctuation after the warmup). I am on "p" version right now, on "n" version I thought it did much better, but wanted to use refined watchdog and get a small boost in mining speed with the latest version. What am I doing wrong?
I use 976 intensity, happens with lower intensity too. If I turn off a card that has optimal speed after warmup, and turn it back on, it has 15% less speed and doesn't get back up to optimal. Something needs to be reworked in the handling of the warmup, I also see a VRAM cluttering, an 8gb cards ends up showing it has 11gb of vram used in gpu-z (maybe bug?). Maybe we need some way to flush the vram and this is what's causing it, especially for those that restart the miner quite often (automatic profit switchers).
What system and drivers you're use? On Windows 10 and latest drivers max intensity on heavy is 944. Even 960 gives significant drop in speed. So as launched GPU-Z... It didn't add speed, but it can decrease it... |
|
|
|
If you bench against Claymore 11.3 look at the hashrate reported by the pool, because on my HD7950 rig i have a lower hashrate on screen (559 JCE against 585 Claymore per card) but a better pool hashrate.
on 2G cards (HD7850, 7870) i'm better, even on screen. i never tested on 730
On my Pitcairn 270X 4Gb Claymore 11.3 gives 550 H/s (manual modded bios with OC), JCE after start gives 500-525 H/s. After 10-15 min JCE gives 555-560 H/s. Which driver do you use? Card installed with RX 580 cards. So I always install latest driver. Now it's 18.9.3. And I noticed that for Pitcairn R9 270X driver version didn't affects on speed at all. I checked this allready about 2 yaers and allways update driver. No one didn't change speed on 270X card. |
|
|
|
how do i set difficulty for algo using jce gpu miner please?
Usually it's not miner settings. It must be set via pool adress or wallet name. Maybe via password. Look at your pool settings. |
|
|
|
If you bench against Claymore 11.3 look at the hashrate reported by the pool, because on my HD7950 rig i have a lower hashrate on screen (559 JCE against 585 Claymore per card) but a better pool hashrate.
on 2G cards (HD7850, 7870) i'm better, even on screen. i never tested on 730
On my Pitcairn 270X 4Gb Claymore 11.3 gives 550 H/s (manual modded bios with OC), JCE after start gives 500-525 H/s. After 10-15 min JCE gives 555-560 H/s. |
|
|
|
I ran the little test with old rx 370 and hd 7970 cards with version 032q - worse than clay 11.3. 4x370 - 1.4kH, 5x7970 - 2.2kH; in the claymore 1.7kH and 2.4kH. No optimization with old videocards?
Probably you didn't wait enough to recieve max speed. For full speed you need to wait about 10-15 minutes on JCE. |
|
|
|
the attrib trick is a stealth mode to bypass some antiviruses, and it's very documented in the doc: https://github.com/jceminer/cn_cpu_miner#privacy-and-securityIt doesn't:
•Punch through your firewall: you have to open it manually if needed
•Run any command, not even attrib (see below)
hard to be closer to what you experienced and yes it is safe  and not new, just your firewall did its job i'm not done yet for v8 because i'm writing it in assembly. i think i've room for optimizations Thanks for clarifying that JCE! However, I think that creating a virus like behaviour in a miner can do only harm. A person who decided mining should also be able to add JCE in the exclusions list of his Anti-Virus software. Good luck with optimizations in V8, we all want them! Sometimes it's strange situation with antiviruses. They sometime blocks attrib.exe, JCE miner exe is on exclusions, but attrib.exe is blocked... |
|
|
|
DO i need to BIOS mod my cards for max hashrate with this miner?
Of course, you are. Miner didn't changes anything in hardware, including video BIOS. |
|
|
|
|
Hmmm. tried --no-warmup option on last version on RX 580 8G cards... Speed looks the same as was before...
|
|
|
|
|
Hmmm, interesting, does RX 580 8Gb needs warmup? And what warmup does exactly?
|
|
|
|
|
Thanks to you're decision... All my rigs needs to adgust fan controls... Some of theme failed bacause of wrong fan setting... What causes problem.. Your miner can track fan speed, but can't change speed...
I think, that if you want make normal WD, you must look at all variations of speed of fan... Threre is no safe situation, if you implement for watchdog, you must think about all situations...
|
|
|
|
|
JCE, OverdriveNTool is good, etc. But it 2nd tool with the miner. If implement OC/V/Fan controls in miner it will be not need in any other tool than miner... You can add at least fan controls, please... I need it.
|
|
|
|
Hello, I am looking for some help setting up Vega FE, any experts here? My hashrate is only 1.2k and my temps are over 80. I am mining heavy algo and I've tried 18.6.4 driver and 18.5.1 driver.
I have so many questions! Example: is there crossfire that I should disable? Nothing is showing up in amd settings.
Also afterburner can't change fan speed or reduce power. Overdriventool gave an error when I tried to change max temp too.
I am lost.
Read post #3 in this thread. What isn’t answered there can be found here... http://vega.miningguides.com/Thank you for the response. I am using those resources! My biggest problem is that I can't control the fan or power the way I can on my other cards (rx) - Afterburner doesn't work and Overdriventool is also giving error messages. I currently have driver 18.5.1 installed but I will put on a newer one and try it. I'll also try the tweaks in step 3 to try to raise my hashrate, currently 1.3k on heavy. Boпpoc peшён, cнaчaлa ycтaнaвливaeм пpoф дpaйвep 18g2(в pигe oднa кapтa и вcтpoйкa), пpи ycтaнoвкe дpoв выбиpaeм чиcтyю ycтaнoвкy либo ddu>выбopoчнaя ycтaнoвкa>Switch mod enable> Пepeзaгpyжaeм> зaxoдим в paдeoн ceттингc> нacтpoйкa дpaйвepa(нижняя лeвaя вклaдкa)> пpoвepяeм нaличиe нoвoгo дpaйвepa>пepeключaeм-ycтaнaвливaeм игpoвoй дpaйвep>выключaeм pиг> извлeкaeм тeкyщyю кapтy> cтaвим cлeдyющyю в cлeдyющий Cлoт.И тaк co вceми кapтaми.Ecли пocтaвить cpaзy вce кapты, вклaдки нacтpoйкa дpaйвepa в пpилoжeнии нe бyдeт.И дa, paзвeтвитeлe PCI-e нe кaнaют.Srb miner 1.6.0: 130 интeнcивнocть, двa пoтoкa,2100н/s normalv7, cast xmr, интeнcивнocть 12,--loadlargepage=on,2080 h/s нa heavy c иcпoльзoвaниeм вceй пaмяти кapты(16gb) pp_table cмoтpитe y GEEK MARK нa ютyб. А ниче, что тут английский форум. Не смущает? Не? |
|
|
|
|
I didn't support dicision about not implementing OC/V/Fan controls... If user didn't know about settings to OC/V/Fan controls he didn't use them. I think, that controls like in Claymore is very usefull. Didn't need to use any 3rd tools. Just set for each algo needed settings in bat or cfg file. Mining is dangerous itself, and even without this settings miner make stress to GPU's. Users that didn't know that shoudn't mines at all...
So adding this controls may be very-very usefull for people, who didn't use overdriveNTool like me...
|
|
|
|
|
JCE did you plan to add overclock/voltage/fan control to GPU miner?
|
|
|
|
speed jumps: lowering alpha or beta params sometimes help.
Alpha 64, beta 8. Can they be lower? |
|
|
|
|
Show Posts
