Gateless Gate Sharp 1.3.8: 30Mh/s (Ethash) on RX 480!

[Littlegrand]

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

[1715380860]

1715380860

[1715380860]

1715380860

[1715380860]

1715380860

[1715380860]

1715380860

[OhGodAGirl]

I just found something pretty interesting online.
After all, it seems that memory timing mods are possible with NVIDIA, too.
Good stuff.

Everything is possible when you start poking hardware. Just a matter of time and emotional control.

[zawawa]

I just found something pretty interesting online.
After all, it seems that memory timing mods are possible with NVIDIA, too.
Good stuff.

Everything is possible when you start poking hardware. Just a matter of time and emotional control.

That sums it all up. Respect!

[zawawa]

Oh, every time when change something relaunch GGS? it's annoying.... Just return this button, don't be such a nasty man.

GGS releases memory automatically for quite some time, so there is really no need for the "Release Memory" button.

[zawawa]

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

Please give me information about your pool, the coin you are mining, and your settings, and I will get to it right away.

[zawawa]

You'll better find the way to tweak mem timings for Vega.
For nvidia there is a solution already - OhGodETHEnlargement.

For polaris your program is a piece of ... well ... I just don't like it.
I tested it yesterday with my fresh computer with new rx570 8gb sapphire nitro+ micron memory. 18.3.4 drivers. Original bios.
First of all from the start your program screwed up my downvolt settings (made by overdriventool) and fired it up mining with huge voltage.
Than I tried to tweak (downvolt, timings) using your program only.
And it gets bsods "thread stuck in device driver" every try
I had no time to struggle with your buggy undocumented software. I've just flashed good timings, applied 850mv and went mining SUMO with 1khs@80watt with doctor's SRBminer ...

Yeah, I definitely need to work on documentation and compatibility... Thanks at least for trying!

[zawawa]

So I reached the conclusion that LLVM's GCN backend is pretty dumb as far as register assignment is concerned.
At the very least, there is a huge room for optimization as long as you don't mind a longer build time.
Perhaps I should create a new LLVM backend for CLRX.

[Littlegrand]

Quote from: Littlegrand on Today at 08:51:51 AM
Quote
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

Please give me information about your pool, the coin you are mining, and your settings, and I will get to it right away

Haven

haven.ingest.cryptoknight.cc 5531 

Didnt optimize default settings:
Threads 1
Intensity 4 tried to 20
Work size 4
Strided index 1
Memory chunk 2

My laptop has NVIDIA geforce 740m.

Also tried it same settings on my 6 card AMD rig with 3 RX580 and 3 RX570, same thing

Log from laptop(same on rig)

2018-05-05 12:34:10.7939 [16] Running garbage collection...
2018-05-05 12:34:10.7939 [16] Memory used before collection: 14MB
2018-05-05 12:34:10.8900 [16] Memory used before collection: 12MB
2018-05-05 12:34:13.1940 [18] API Listener started.
2018-05-05 12:38:33.9272 [1] Launching miner(s) for Custom Pool 0...
2018-05-05 12:38:35.5019 [20] Miner thread for Device #0 started.
2018-05-05 12:38:35.5019 [20] NiceHash mode is off.
2018-05-05 12:38:35.6611 [20] Loaded Kernels\cryptonight_heavy.cl for Device #0.
2018-05-05 12:38:47.1088 [20] Built cryptonight_heavy program for Device #0.
2018-05-05 12:38:47.1088 [20] Build options:  -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2  -IKernels -DWORKSIZE=4
2018-05-05 12:38:47.1695 [20] Switching to Monero Version 2
2018-05-05 12:38:57.8436 [20] Device #0 (CryptoNight): 30.11 h/s
2018-05-05 12:39:08.4715 [20] Device #0 (CryptoNight): 30.12 h/s
2018-05-05 12:39:08.8778 [12] Received new job: 800226972178483
2018-05-05 12:39:10.8926 [16] Running garbage collection...
2018-05-05 12:39:10.8926 [16] Memory used before collection: 16MB
2018-05-05 12:39:10.9617 [16] Memory used before collection: 15MB
2018-05-05 12:39:19.1095 [20] Device #0 submitted Share #0 to haven.ingest.cryptoknight.cc as (my have address taken out)
2018-05-05 12:39:19.1100 [20] Device #0 submitted a share to haven.ingest.cryptoknight.cc as  (my have address taken out)
2018-05-05 12:39:19.1100 [20] Device #0 (CryptoNight): 29.92 h/s
2018-05-05 12:39:19.7139 [12] Share #0 rejected: Wrong algo, use monero7 miner
2018-05-05 12:39:28.4014 [1] Stopping miners...
2018-05-05 12:39:28.4819 [1] Stopped miners.


Thanks,
--James

[zawawa]

Quote from: Littlegrand on Today at 08:51:51 AM
Quote
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

Please give me information about your pool, the coin you are mining, and your settings, and I will get to it right away

Haven

haven.ingest.cryptoknight.cc 5531 

Didnt optimize default settings:
Threads 1
Intensity 4 tried to 20
Work size 4
Strided index 1
Memory chunk 2

My laptop has NVIDIA geforce 740m.

Also tried it same settings on my 6 card AMD rig with 3 RX580 and 3 RX570, same thing

Log from laptop(same on rig)

2018-05-05 12:34:10.7939 [16] Running garbage collection...
2018-05-05 12:34:10.7939 [16] Memory used before collection: 14MB
2018-05-05 12:34:10.8900 [16] Memory used before collection: 12MB
2018-05-05 12:34:13.1940 [18] API Listener started.
2018-05-05 12:38:33.9272 [1] Launching miner(s) for Custom Pool 0...
2018-05-05 12:38:35.5019 [20] Miner thread for Device #0 started.
2018-05-05 12:38:35.5019 [20] NiceHash mode is off.
2018-05-05 12:38:35.6611 [20] Loaded Kernels\cryptonight_heavy.cl for Device #0.
2018-05-05 12:38:47.1088 [20] Built cryptonight_heavy program for Device #0.
2018-05-05 12:38:47.1088 [20] Build options:  -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2  -IKernels -DWORKSIZE=4
2018-05-05 12:38:47.1695 [20] Switching to Monero Version 2
2018-05-05 12:38:57.8436 [20] Device #0 (CryptoNight): 30.11 h/s
2018-05-05 12:39:08.4715 [20] Device #0 (CryptoNight): 30.12 h/s
2018-05-05 12:39:08.8778 [12] Received new job: 800226972178483
2018-05-05 12:39:10.8926 [16] Running garbage collection...
2018-05-05 12:39:10.8926 [16] Memory used before collection: 16MB
2018-05-05 12:39:10.9617 [16] Memory used before collection: 15MB
2018-05-05 12:39:19.1095 [20] Device #0 submitted Share #0 to haven.ingest.cryptoknight.cc as (my have address taken out)
2018-05-05 12:39:19.1100 [20] Device #0 submitted a share to haven.ingest.cryptoknight.cc as  (my have address taken out)
2018-05-05 12:39:19.1100 [20] Device #0 (CryptoNight): 29.92 h/s
2018-05-05 12:39:19.7139 [12] Share #0 rejected: Wrong algo, use monero7 miner
2018-05-05 12:39:28.4014 [1] Stopping miners...
2018-05-05 12:39:28.4819 [1] Stopped miners.


Thanks,
--James

"2018-05-05 12:38:47.1695 [20] Switching to Monero Version 2"
Why is this crappy server not returning 7?
Does this mean I have to add "CryptoNight-HeavyV7"? What a mess...

[liomojo1]

Did some testing today , and saw that monero algo v7 is well optimized it reached 930h , but heavy algo , which by default should be reaching 1000-1050h is only 730h . Samsung memory rx480 . And as far as ovrclock settings and voltage they are not working on blockchain driver , but you already told me about it. but the tool gets in cross with msi afterburner in some way and they crash the system and driver when voltage is tweaked  and have to do a system restore , because when system loads after a minute it crashes and freezes. So don`t use msi afterburner!

[zawawa]

Did some testing today , and saw that monero algo v7 is well optimized it reached 930h , but heavy algo , which by default should be reaching 1000-1050h is only 730h . Samsung memory rx480 . And as far as ovrclock settings and voltage they are not working on blockchain driver , but you already told me about it. but the tool gets in cross with msi afterburner in some way and they crash the system and driver when voltage is tweaked  and have to do a system restore , because when system loads after a minute it crashes and freezes. So don`t use msi afterburner!

I totally forgot to mention in documentation that GGS doesn't work with AfterBurner. Sorry about that...

[t3syncro]

@zawawa

Would you mind adding supportxmr pool ?
The pool hashrate is ~90MH . I think they'd list your software too on the getting started site.

https://supportxmr.com/#/help/getting_started

[t3syncro]

Did some testing today , and saw that monero algo v7 is well optimized it reached 930h , but heavy algo , which by default should be reaching 1000-1050h is only 730h . Samsung memory rx480 . And as far as ovrclock settings and voltage they are not working on blockchain driver , but you already told me about it. but the tool gets in cross with msi afterburner in some way and they crash the system and driver when voltage is tweaked  and have to do a system restore , because when system loads after a minute it crashes and freezes. So don`t use msi afterburner!

Well, that's the point. With GGS you don't need any additional software nor bios mods. Not even a registered Windows version. Instability in GGS is caused by either heavy OC/undervolting or inconsistent Bios mods...

[skablast]

I don't care of longer build time as long as:
I can save the build for the next time launch
Its not single card related.
Its faster

They are right, your rx480 8gb samsung  is supposed to go over 1k. ( Well, MINE is doing it) and it doesn't.

Haven't understood what we can expect (Lyraz ? faster CNheavy,faster everything, easy to implement memory timing)  and more or less when.

last:
While mining lyra2ver2 with latest version of ggs, no phymem,no optimazion, nothing, with 4 rx, the miner can't handle all of them. They all start and they slowly die. Someone ( not me) have changed the core speed at 1300.Few time it happen also with CN v7

really last: GGS start mining as soon as launched even if in the setup isn't selected to start. And sometimes doesnt recognize HOLD shift.

[UnclWish]

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.

[QuirkSilver]

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.

[Littlegrand]

Quote from: Littlegrand on Today at 08:51:51 AM


Quote

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.

Both Claymore and SRBMiner work fine.

[UnclWish]

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?

[UnclWish]

Quote from: Littlegrand on Today at 08:51:51 AM


Quote

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.

Both Claymore and SRBMiner work fine.

Wrote address and port of pool. zawawa will check it. Without these data how he can help you?

[DunePilot]

Looks great, I will have to give this a look if I ever do it on Windows.