There are timings, in full view, on this very forum for MJR that give 1200h/s on cn heavy at 1244/2125 570 nitro+ 8g. Just keep looking.  This forum is very big. And I can looking for years in search of right info. Maybe you share it to save our time? Its no secret, 999000000000000022339D00CEDD6B4470551414B80D960B0040C400750314204A8900A00200000 018123745B92B3A16 Doktor put it in SRBMiner thread, and its really good compared to the one click strap. Zawawa, some issues in latest version: *Rx 560 2gb doesn't want to get the timing optimizations, neither do the R9 390 *GPU current clocks aren't shown in overclocking, instead are the last copied ones (copied from similar device etc.) *Work size (4) in cryptonight should be enabled, if possible (for some odd GPUs i believe).. for some reason R9 390 on V7 gives similar results to claymore with two threads and a 740-820 intensity and most importantly 4 work size rather than 8. In Old GG some GPUs of 2gb size were able to fit 448 intensityX2 threads, those gave noticeable higher gains in speed, not sure what rules, but, read somewhere that elpiads are different than samsung and hynix etc. in amount of memory available. And you with doctor's timings and 1244/2125 clocks recieve 1200 h/s in GGS? What intensity? Can you give screen? |
|
|
|
It is all right. The log shows cryptonight heave loaded, the share submitted to the correct url, just rejected wrong algo...
Correct url didn't means that you select correct url for cryptonight heavy algo.
Most pools have several ports for different algos. If you chose port for cryptonightv7 but in miner you select CN heavy algo, miner will connect to pool via seleted port, and pool allows to connect, but miner will finds shares for heavy and send them on pool to port from wich pool wait shares for cryptonightV7, due to port.
Check port number for your pool. Is you right pointed it for CN heavy. Yes it is correct port(though it does not show port in log). The Haven address in log is correct as well. It normal to say Switching to Monero 2 in log? Any ideas? Thanks It's normal. But why you recieve rejected shares... Did you tried other miners? What pool? Give address. |
|
|
|
Hi, I just upgraded to 1803 using 2.9e miner version. The miner now gets stuck at:  It stays there for at least 1,5 hours till now. Looking forward to your help! Few posts back I have reported the same problem and issued a warning. In my instance compute mode was off after upgrade, and miner took some 5 or so minutes to find all gpus before starting mining. Two options: roll back the upgrade. Or clean install the Radeon drivers (Uninstall with ddu, install driver, enable compute mode) then try PH. Report your findings. Clean uninstall and installing drivers again didn't work. This was the first thing I tried. What driver version you try? Install 18.3.4. Latest 18.4.1 have issues... |
|
|
|
|
Strange... Windows 10 1803 - GGS identified my RX 580 as R200 GPU's. Very nice...
Installed back 18.3.4. - all return to normal...
|
|
|
|
|
Sorry for offtopic... But my W10 1709 updates to 1803. And now AtiFlash 2.77 didn't run... Anyone knows what to do?
|
|
|
|
Code optimization takes so much time! Then again, I heard a developper of John the Ripper the password
cracker spent months optimizing his S-Boxes for Bitslice-DES with a water-cooled PC to set a world record.
I guess waiting for an hour or so shouldn't be that bad...
Of course, you're absolutly right! |
|
|
|
Hi, I just upgraded to 1803 using 11.7 miner version. The miner now gets stuck at: https://ibb.co/jVAeR7It stays there for at least 1,5 hours till now. Looking forward to your help! Why you are waitng so long?Huh You can close miner window - you willn't see anything new for the next few years... Better close this window, and than update your video driver to last version with support 1803. |
|
|
|
|
I encountered bug with 18.4.1 - periodically speed on GPU on wich display connected to drops to 0.
|
|
|
|
More trully as I heard that Claymore have access to Microsoft development. His miners didn't rewrite any Windows drivers (at least on Windows 10) because it not so easy to change driver that's work at this moment without reinstalling it. And don't forget about digital signing of drivers...
Well, that's exactly what PhyMem does. Are you impressed now? As I reads, Phymem didn't change driver, it's just access GPU bypassing the driver... But I can be wrong, of course. "Release memory" button, I used it often...
Use "Relaunch" instead. I got rid of it because it was redundant. Oh, every time when change something relaunch GGS? it's annoying.... Just return this button, don't be such a nasty man. |
|
|
|
Ok Im going nuts I install 18.3.4 drivers and tries GGS 1.36 and 1.37 and cannot get any of my r9 cards to run 270,280 and 390's Im on win 10 I tried mph ethash but it wont connect I have to use a different port than ETH because of the dag the log keeps saying something about the key also I tried cn7 and my hashrates either suck or when I use default settings it crashes could someone give me a good settings on xmr for theses older cards Thanks
Also I no its not GGS its the fact Im using older cards on this rig
edit: I also tried stock clocks and OC I wonder if I need to reinstall win for some reason when you use claymore miners than switch to a different miner you get nothing but problems this always happened to me on win7
I heard a rumor that Claymore's miners rewrite display drivers for stability. I didn't confirm that rumor myself, but it makes a perfect sense. I was at least pretty certain that they use exploits in Windows to gain administrative privileges. (I don't think it's a coincidence antivirus software marks his miners as threats.) These are all speculations and I might be completely wrong. That is why I prefer open-source projects over closed-source ones, although I take a substantial financial hit that way. Just my two cents. Thanks I believe this is the problem I can use any claymore miner without a problem as soon as I try any other miner I have problems or crashes even when I run DDU I think a fresh install of win 10 is the way to go Im going to try and see whats happens I think that it's only rumors about Claymore's rewtining drivers... More trully as I heard that Claymore have access to Microsoft development. His miners didn't rewrite any Windows drivers (at least on Windows 10) because it not so easy to change driver that's work at this moment without reinstalling it. And don't forget about digital signing of drivers... But his miners can do things that other miners can't. I think that Claymore knows significant more about drivers on Windows and how them works. He maked his miners with low access to GPU maybe without driver at all if it possible... Maybe he worked for MS earler or something like this. For me any other miner normal works after launching his miners. And even more - I often use his miners for setting overclock, fans, etc. It's very usefull that his miners leave HW changes in GPU work after closing miner. zawawa, maybe you make this option too? To leave OC and fan settings changed after closing GGS? And return please "Release memory" button, I used it often... |
|
|
|
It is all right. The log shows cryptonight heave loaded, the share submitted to the correct url, just rejected wrong algo...
Correct url didn't means that you select correct url for cryptonight heavy algo. Most pools have several ports for different algos. If you chose port for cryptonightv7 but in miner you select CN heavy algo, miner will connect to pool via seleted port, and pool allows to connect, but miner will finds shares for heavy and send them on pool to port from wich pool wait shares for cryptonightV7, due to port. Check port number for your pool. Is you right pointed it for CN heavy. |
|
|
|
I am getting all rejected shares mining haven cryptonight heavy saying wrong algo. I noticed in the log there is this: Switching to Monero Version 2. Did I do something wrong?
Thanks
--J
Check is you right choosen pool and port. |
|
|
|
Let's see if I can beat LLVM and AMD display drivers with this "bomb"...  It's cool!!! But be carefull - I woudn't want to matrix has you )))) A day ago you wanted to test hynix mjr memory... What's you results? |
|
|
|
Hi, I just upgraded to 1803 using 2.9e miner version. The miner now gets stuck at: It stays there for at least 1,5 hours till now. Looking forward to your help! Why you are waitng so long?  You can close miner window - you willn't see anything new for the next few years... Better close this window, and than update your video driver to last version with support 1803. |
|
|
|
Using smr-stak and SRB all cards looks to need half of the regular Intensity. Except RX580(70) that works fine with old(or not half) intensity level.
Other devs looks clueless.
Do you have any thoughts about this algo? Vega looks lame with similar Intensity as RX580 when it used to be double.
This applies for 8gb cards. I have a 470 8g uses same intensity as 580 8g (54, this gives me the best results). Using any miner that supports CN heavy you use half of the 'normal' intensity. I don't mined heavy algo yet... It's true that 580 8Gb gives on heavy algo speed more than in normalv7? |
|
|
|
Why there is no one Claymore's miner?
All Claymore miners are already there ClayCrypto-11.3 (AMD) ClayDual-11.7 / ClayETH-11.7 (AMD,NVIDIA) ClayNeoScrypt (AMD) ClayZEC-12.6 (AMD) ClayCrypto-4.0 (CPU) Did Claymore release any other miner that is missing (apart from Claymore XPM)? Ohhh. Sorry. I just read on 1st post and there is no info about them... |
|
|
|
|
Why there is no one Claymore's miner?
|
|
|
|
Hey zawawa,
i still can't get phymem running - still getting an error. Changes on memory timings have no effect. Hitting the "print memory timings"-button has no effect either.
It's unmodified cards and 18.3.2-Driver.
Reinstalled GGS, used the standalone one, reinstalled drivers....
btw. The speed out of the box for ajr memory is good. I have 920h/s with 1150/1950.
Any idea?
Sorry, I missed your reply. Can you see PhyMemWrapper.dll in your application folder? It seems like the miner is not properly installed. Hi, yes i can see the file. See attached screenshots. It's asking the source file from D:\github\GatelessGateSharp\GatelessGateSharp\MainForm.cs   My almost non-existent German skills tell me that the system cannot find the DLL. If it is there, it is either broken or incompatible. You are not running the miner on a 32-bit Windows, are you? Ok, it just says Exception: Unable to load DLL "PhyMemWrapper.dll': The specified module was not found. (Exception:from HRESULT: 0x8007007E). Windows is 64bit... I wonder why it asks for something on the not existent "D:\"-Drive. I do not have a "D:\"-Drive installed. The PhyMemwrapper.dll path is written correct into the registry: "C:\Program Files\Zawawa Software LLC\Gateless Gate Sharp\PhyMemWrapper.dll". Your Mainform.cs does not have this path specified, and i can't find any path like this in the environment variables nor in the registry. Anyway, it seems i need a clean reinstall of Windows as this has nothing to do with GGS, i think. I just figured out that it doesn't save the custom pool's port either although it is written correctly into the json file. Did you tried to run GGS with admin rights? Folders in Program Files needs additional privelegies to run properly... Or try to uninstall and install in other folder. |
|
|
|
nothing gpu-special, but each round of gpu mine xmr needs 88 bytes of input cpu side, for each gpu thread, and there are often ~1000 of them per gpu, time 7 gpu you get ~500K of cache flooded in your cpu, enough to annoy a minig thread.
Oh.... I didn't know that... Thanks for info! |
|
|
|
with so many gpus, you probably cannot use all cache for cpu mining, you may have better perfs with 2x Triple plus nine simple for IPBC
for cn-v7 i'd say seven or six simple on a ryzen 1600/1700. you'll get ~430 I predict on a r5 1600
However the cheap way would be to stay with 8x simple threads and with --low parameter and let the GPU miners take the cache they need. that's what i do, but my ryzen has only 3 GPU. This way JCE drops from 506 (alone) to 497, quite limited drop, and no impact on gpu mining.
What GPU's you're talking about? For wich GPU's it's need CPU cache? More specifically, please. |
|
|
|
|
Show Posts
