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

zawawa

sr. member

Activity: 728

Merit: 304

Miner Developer

Quote from: skablast on April 17, 2018, 01:06:29 AM

Quote from: Elder III on April 16, 2018, 02:34:53 PM

Does the current alpha version of Gateless Gate support an AMD R9 Fury X? I installed it on an up to date Windows 10 Pro machine and at first I had a pop up message saying to set the paging file to at least 24 GB - this would pop up with a "ding" and then disappear, only to repeat over and over every 2 seconds until I would restart the computer. After bumping the virtual memory up to 30 GB that message no longer appears, but it will just have the black circle show up as if the program is starting to load, only for it to go away and reappear every 2 seconds until restarting the computer again. I'm using 17.9.3 drivers on that computer. Do I need to install any particular addons, drivers etc... thanks

I have exactly the same problem that Elder III has on one of the rig. GGS load, find an error,reload, etc And there is no solution than using something else to mine monero

And I'm using AMD latest driver, not the blockchain one

unistalled, removed all the registry with an uninstaller, nothing work

"find an error" Could I see a screen shot? Which video cards do you have on the PC? Do you have enough physical memory?

inv1s1bl3

newbie

Activity: 65

Merit: 0

So, for the x16r should I revert back to stock settings or I can run it with my ETH bios mod?

skablast

member

Activity: 476

Merit: 19

Quote from: Elder III on April 16, 2018, 02:34:53 PM

Does the current alpha version of Gateless Gate support an AMD R9 Fury X? I installed it on an up to date Windows 10 Pro machine and at first I had a pop up message saying to set the paging file to at least 24 GB - this would pop up with a "ding" and then disappear, only to repeat over and over every 2 seconds until I would restart the computer. After bumping the virtual memory up to 30 GB that message no longer appears, but it will just have the black circle show up as if the program is starting to load, only for it to go away and reappear every 2 seconds until restarting the computer again. I'm using 17.9.3 drivers on that computer. Do I need to install any particular addons, drivers etc... thanks

I have exactly the same problem that Elder III has on one of the rig. GGS load, find an error,reload, etc And there is no solution than using something else to mine monero

And I'm using AMD latest driver, not the blockchain one

unistalled, removed all the registry with an uninstaller, nothing work

UAGet

newbie

Activity: 70

Merit: 0

Quote from: zawawa on April 16, 2018, 06:40:09 PM

I tested CryptoNight-Heavy with default pools again and didn't see any problems.
I will look into this.

With secondary custom puul for Stellite coin - all Ok, no any problem...

zawawa

sr. member

Activity: 728

Merit: 304

Miner Developer

Now I think about it, I should probably include README.md in the package.
I prefer to keep documentation online and assumed people would read the README.md online, but I guess I was wrong...

zawawa

sr. member

Activity: 728

Merit: 304

Miner Developer

Quote from: Elder III on April 17, 2018, 12:12:55 AM

Quote from: zawawa on April 16, 2018, 11:30:08 PM

Quote from: Elder III on April 16, 2018, 02:34:53 PM

I'm using 17.9.3 drivers on that computer. Do I need to install any particular addons, drivers etc... thanks

Please do take time to read Readme.md. GGS is not compatible with that version of the driver.
I always test GGS with R9 Nano, so there shouldn't be any problems.

I really should implement a version check for the drivers.
There seems to be no other way to ensure stability of the miner... *sigh*

I always look for a Readme file with any new miner that I install. I just double checked in every folder and there is not a Readme included in the download - Gateless_Gate_Sharp_1.3.3_alpha - that I have.

Here it is!

https://github.com/zawawawa/GatelessGateSharp

Elder III

sr. member

Activity: 1246

Merit: 274

Quote from: zawawa on April 16, 2018, 11:30:08 PM

Quote from: Elder III on April 16, 2018, 02:34:53 PM

I'm using 17.9.3 drivers on that computer. Do I need to install any particular addons, drivers etc... thanks

Please do take time to read Readme.md. GGS is not compatible with that version of the driver.
I always test GGS with R9 Nano, so there shouldn't be any problems.

I really should implement a version check for the drivers.
There seems to be no other way to ensure stability of the miner... *sigh*

I always look for a Readme file with any new miner that I install. I just double checked in every folder and there is not a Readme included in the download - Gateless_Gate_Sharp_1.3.3_alpha - that I have.

zawawa

sr. member

Activity: 728

Merit: 304

Miner Developer

Quote from: Elder III on April 16, 2018, 02:34:53 PM

I'm using 17.9.3 drivers on that computer. Do I need to install any particular addons, drivers etc... thanks

Please do take time to read Readme.md. GGS is not compatible with that version of the driver.
I always test GGS with R9 Nano, so there shouldn't be any problems.

I really should implement a version check for the drivers.
There seems to be no other way to ensure stability of the miner... *sigh*

zawawa

sr. member

Activity: 728

Merit: 304

Miner Developer

hamesh

newbie

Activity: 22

Merit: 0

Nice work. That fixed the shares issue when switching back from devfee on cryptonight v7.

What does 'Enable PhyMem' do? What is the advantage to enabling this? I read https://www.codeproject.com/Articles/35378/Access-Physical-Memory-Port-and-PCI-Configuration that you reference on Github but still don't understand what it is or what benefit it provides - Gateless seems to work just fine without it...

Quote from: zawawa on April 16, 2018, 02:08:56 AM

Gateless Gate Sharp 1.3.4 alpha
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.3.4-alpha

* Fixed critical bugs with CryptoNight variants.
* Removed optional OpenCL binaries.

Phew!

dohfish

newbie

Activity: 65

Merit: 0

Been using 1.3.2 for a while now, noticed that after ~12 hours on a machine with more than 6 GPUs it becomes unstable, it will not directly crash but speeds are fluctuating ~200H/s and the memory usage goes up to more than 2GB aswell as the CPU usage goes up to consume an entire core - Restarting the program solves it for another run.

I cannot load 1.3.4 here, it just never loads - I have the logo popup, and the background on the logo go black as normal, and then it just stands there using 100% cpu for ages, I left it for 15 minutes and it never started.

Dropped back to 1.3.2 and im mining again.

Elder III

sr. member

Activity: 1246

Merit: 274

Does the current alpha version of Gateless Gate support an AMD R9 Fury X? I installed it on an up to date Windows 10 Pro machine and at first I had a pop up message saying to set the paging file to at least 24 GB - this would pop up with a "ding" and then disappear, only to repeat over and over every 2 seconds until I would restart the computer. After bumping the virtual memory up to 30 GB that message no longer appears, but it will just have the black circle show up as if the program is starting to load, only for it to go away and reappear every 2 seconds until restarting the computer again. I'm using 17.9.3 drivers on that computer. Do I need to install any particular addons, drivers etc... thanks

UAGet

newbie

Activity: 70

Merit: 0

Quote from: zawawa on April 16, 2018, 02:08:56 AM

Gateless Gate Sharp 1.3.4 alpha
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.3.4-alpha

* Fixed critical bugs with CryptoNight variants.
* Removed optional OpenCL binaries.

Not worcked with CryptoNight-heavy - "Incorrect share" Sad

http://scrin.org/i/18/04/20180416222018.png

Code:

2018-04-16 22:13:40.0807 [1] Gateless Gate Sharp 1.3.4 alpha started.
2018-04-16 22:13:40.9089 [1] Number of Devices: 4
2018-04-16 22:13:41.0026 [1] Successfully initialized AMD Display Library.
2018-04-16 22:13:41.0026 [1] Number of ADL Adapters: 31
2018-04-16 22:13:41.1120 [1] ADL_Adapter_AdapterInfo_Get() returned error code 0
2018-04-16 22:13:41.1120 [1] Failed to initialize NVIDIA Management Library.
2018-04-16 22:13:50.3935 [1] Loading settings from C:\Users\drool\AppData\Roaming\GatelessGateSharp\GatelessGateSharp.sqlite...
2018-04-16 22:14:16.6755 [1] Loaded settings.
2018-04-16 22:14:16.6912 [1] Invalid argument: D:\Install\Miners\Gateless Gate Sharp\GatelessGateSharp.exe
2018-04-16 22:14:21.3163 [1] Launching miner(s) for Custom Pool 0...
2018-04-16 22:14:22.2382 [11] Miner thread for Device #0 started.
2018-04-16 22:14:22.2382 [11] NiceHash mode is off.
2018-04-16 22:14:22.2851 [11] Loaded Kernels\cryptonight_heavy.cl for Device #0.
2018-04-16 22:14:23.0507 [12] Miner thread for Device #0 started.
2018-04-16 22:14:23.0507 [12] NiceHash mode is off.
2018-04-16 22:14:23.0507 [12] Loaded Kernels\cryptonight_heavy.cl for Device #0.
2018-04-16 22:14:34.4885 [10] Received new job: 699881314277768
2018-04-16 22:14:42.8481 [16] Running garbage collection...
2018-04-16 22:14:42.8481 [16] Memory used before collection: 24MB
2018-04-16 22:14:43.0200 [16] Memory used before collection: 20MB
2018-04-16 22:14:48.9108 [17] Miner thread for Device #1 started.
2018-04-16 22:14:48.9108 [17] NiceHash mode is off.
2018-04-16 22:14:48.9264 [11] Built cryptonight_heavy program for Device #0.
2018-04-16 22:14:48.9264 [11] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-16 22:14:48.9733 [17] Loaded Kernels\cryptonight_heavy.cl for Device #1.
2018-04-16 22:14:49.0358 [11] Switching to Monero Version 2
2018-04-16 22:14:50.4812 [18] Miner thread for Device #1 started.
2018-04-16 22:14:50.4812 [18] NiceHash mode is off.
2018-04-16 22:14:50.4812 [18] Loaded Kernels\cryptonight_heavy.cl for Device #1.
2018-04-16 22:14:59.8096 [11] Device #0 (CryptoNight): 241.18 h/s
2018-04-16 22:15:00.3565 [20] API Listener started.
2018-04-16 22:15:10.5286 [11] Device #0 (CryptoNight): 241.33 h/s
2018-04-16 22:15:15.6850 [23] Miner thread for Device #2 started.
2018-04-16 22:15:15.6850 [23] NiceHash mode is off.
2018-04-16 22:15:15.7006 [12] Built cryptonight_heavy program for Device #0.
2018-04-16 22:15:15.7006 [12] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-16 22:15:15.7163 [23] Loaded Kernels\cryptonight_heavy.cl for Device #2.
2018-04-16 22:15:15.7788 [12] Switching to Monero Version 2
2018-04-16 22:15:17.7007 [24] Miner thread for Device #2 started.
2018-04-16 22:15:17.7007 [24] NiceHash mode is off.
2018-04-16 22:15:17.7007 [24] Loaded Kernels\cryptonight_heavy.cl for Device #2.
2018-04-16 22:15:24.2790 [11] Device #0 (CryptoNight): 26.93 h/s
2018-04-16 22:15:26.5916 [12] Device #0 (CryptoNight): 208.36 h/s
2018-04-16 22:15:41.0763 [11] Device #0 (CryptoNight): 36.12 h/s
2018-04-16 22:15:41.1388 [12] Device #0 (CryptoNight): 36.87 h/s
2018-04-16 22:15:42.5295 [25] Miner thread for Device #3 started.
2018-04-16 22:15:42.5295 [25] NiceHash mode is off.
2018-04-16 22:15:42.5451 [18] Built cryptonight_heavy program for Device #1.
2018-04-16 22:15:42.5451 [18] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-16 22:15:42.5451 [25] Loaded Kernels\cryptonight_heavy.cl for Device #3.
2018-04-16 22:15:42.6076 [18] Switching to Monero Version 2
2018-04-16 22:15:43.8577 [26] Miner thread for Device #3 started.
2018-04-16 22:15:43.8577 [26] NiceHash mode is off.
2018-04-16 22:15:43.8889 [26] Loaded Kernels\cryptonight_heavy.cl for Device #3.
2018-04-16 22:15:52.1704 [12] Device #0 (CryptoNight): 183.61 h/s
2018-04-16 22:15:52.3892 [11] Device #0 (CryptoNight): 173.88 h/s
2018-04-16 22:15:53.4986 [18] Device #1 (CryptoNight): 242.02 h/s
2018-04-16 22:16:00.1706 [10] Received new job: 161677327048537
2018-04-16 22:16:03.3738 [12] Device #0 (CryptoNight): 193.46 h/s
2018-04-16 22:16:03.6864 [11] Device #0 (CryptoNight): 196.12 h/s
2018-04-16 22:16:04.1707 [18] Device #1 (CryptoNight): 242.09 h/s
2018-04-16 22:16:09.1553 [24] Built cryptonight_heavy program for Device #2.
2018-04-16 22:16:09.1553 [24] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-16 22:16:09.2334 [24] Switching to Monero Version 2
2018-04-16 22:16:14.4992 [12] Device #0 (CryptoNight): 212.64 h/s
2018-04-16 22:16:14.7804 [18] Device #1 (CryptoNight): 241.77 h/s
2018-04-16 22:16:14.9679 [11] Device #0 (CryptoNight): 185.52 h/s
2018-04-16 22:16:20.0149 [24] Device #2 (CryptoNight): 241.08 h/s
2018-04-16 22:16:25.4214 [18] Device #1 (CryptoNight): 241.59 h/s
2018-04-16 22:16:25.5776 [12] Device #0 (CryptoNight): 201.69 h/s
2018-04-16 22:16:25.8432 [11] Device #0 (CryptoNight): 184.65 h/s
2018-04-16 22:16:30.6559 [24] Device #2 (CryptoNight): 237.86 h/s
2018-04-16 22:16:35.3123 [26] Built cryptonight_heavy program for Device #3.
2018-04-16 22:16:35.3123 [26] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-16 22:16:35.3123 [26] Switching to Monero Version 2
2018-04-16 22:16:36.1248 [18] Device #1 (CryptoNight): 241.65 h/s
2018-04-16 22:16:36.3123 [12] Device #0 (CryptoNight): 197.73 h/s
2018-04-16 22:16:36.8592 [11] Device #0 (CryptoNight): 196.83 h/s
2018-04-16 22:16:41.3593 [24] Device #2 (CryptoNight): 239.65 h/s
2018-04-16 22:16:46.0938 [26] Device #3 (CryptoNight): 241.54 h/s
2018-04-16 22:16:46.7970 [18] Device #1 (CryptoNight): 238.62 h/s
2018-04-16 22:16:47.6095 [12] Device #0 (CryptoNight): 189.32 h/s
2018-04-16 22:16:48.2345 [11] Device #0 (CryptoNight): 138.84 h/s
2018-04-16 22:16:52.1721 [24] Device #2 (CryptoNight): 240.17 h/s
2018-04-16 22:16:56.8129 [26] Device #3 (CryptoNight): 234.50 h/s
2018-04-16 22:16:57.5629 [18] Device #1 (CryptoNight): 239.93 h/s
2018-04-16 22:16:57.9067 [12] Device #0 (CryptoNight): 184.06 h/s
2018-04-16 22:16:59.4692 [11] Device #0 (CryptoNight): 193.73 h/s
2018-04-16 22:17:01.8599 [10] Received new job: 825644128564871
2018-04-16 22:17:03.0162 [24] Device #2 (CryptoNight): 241.08 h/s
2018-04-16 22:17:03.2975 [25] Built cryptonight_heavy program for Device #3.
2018-04-16 22:17:03.2975 [25] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-16 22:17:03.3131 [25] Switching to Monero Version 2
2018-04-16 22:17:07.2195 [26] Device #3 (CryptoNight): 210.84 h/s
2018-04-16 22:17:08.2664 [18] Device #1 (CryptoNight): 239.17 h/s
2018-04-16 22:17:09.1101 [12] Device #0 (CryptoNight): 209.76 h/s
2018-04-16 22:17:10.7508 [11] Device #0 (CryptoNight): 175.69 h/s
2018-04-16 22:17:13.7353 [24] Device #2 (CryptoNight): 234.48 h/s
2018-04-16 22:17:14.7666 [25] Device #3 (CryptoNight): 118.50 h/s
2018-04-16 22:17:17.4541 [26] Device #3 (CryptoNight): 197.52 h/s
2018-04-16 22:17:19.0479 [18] Device #1 (CryptoNight): 241.20 h/s
2018-04-16 22:17:19.2198 [12] Device #0 (CryptoNight): 181.83 h/s
2018-04-16 22:17:21.7199 [11] Device #0 (CryptoNight): 213.17 h/s
2018-04-16 22:17:24.5168 [24] Device #2 (CryptoNight): 240.13 h/s
2018-04-16 22:17:24.7825 [25] Device #3 (CryptoNight): 210.08 h/s
2018-04-16 22:17:28.5951 [26] Device #3 (CryptoNight): 218.26 h/s
2018-04-16 22:17:30.0951 [18] Device #1 (CryptoNight): 242.00 h/s
2018-04-16 22:17:30.3764 [23] Built cryptonight_heavy program for Device #2.
2018-04-16 22:17:30.3764 [23] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-16 22:17:30.4701 [23] Switching to Monero Version 2
2018-04-16 22:17:30.6108 [12] Device #0 (CryptoNight): 87.09 h/s
2018-04-16 22:17:32.0796 [11] Device #0 (CryptoNight): 174.85 h/s
2018-04-16 22:17:35.7828 [24] Device #2 (CryptoNight): 203.04 h/s
2018-04-16 22:17:35.7984 [25] Device #3 (CryptoNight): 202.74 h/s
2018-04-16 22:17:39.1423 [26] Device #3 (CryptoNight): 212.46 h/s
2018-04-16 22:17:40.7361 [18] Device #1 (CryptoNight): 240.71 h/s
2018-04-16 22:17:40.8142 [12] Device #0 (CryptoNight): 57.24 h/s
2018-04-16 22:17:40.8454 [23] Device #2 (CryptoNight): 203.03 h/s
2018-04-16 22:17:41.4236 [10] Received new job: 522362741755925
2018-04-16 22:17:42.4549 [11] Device #0 (CryptoNight): 157.11 h/s
2018-04-16 22:17:46.5956 [25] Device #3 (CryptoNight): 192.46 h/s
2018-04-16 22:17:46.8613 [24] Device #2 (CryptoNight): 205.11 h/s
2018-04-16 22:17:49.9863 [26] Device #3 (CryptoNight): 218.47 h/s
2018-04-16 22:17:50.8301 [12] Device #0 (CryptoNight): 185.65 h/s
2018-04-16 22:17:51.4239 [18] Device #1 (CryptoNight): 240.89 h/s
2018-04-16 22:17:51.5645 [23] Device #2 (CryptoNight): 199.72 h/s
2018-04-16 22:17:52.5177 [11] Device #0 (CryptoNight): 179.40 h/s
2018-04-16 22:17:57.4866 [25] Device #3 (CryptoNight): 211.99 h/s
2018-04-16 22:17:57.5178 [24] Device #2 (CryptoNight): 203.87 h/s
2018-04-16 22:17:57.7522 [17] Built cryptonight_heavy program for Device #1.
2018-04-16 22:17:57.7522 [17] Build options: -O5 -DSTRIDED_INDEX=1 -DMEMORY_CHUNK_SIZE=2 -IKernels -DWORKSIZE=8
2018-04-16 22:17:57.7678 [17] Switching to Monero Version 2
2018-04-16 22:18:01.2803 [26] Device #3 (CryptoNight): 116.50 h/s
2018-04-16 22:18:02.0938 [12] Device #0 (CryptoNight): 113.48 h/s
2018-04-16 22:18:02.2133 [23] Device #2 (CryptoNight): 199.43 h/s
2018-04-16 22:18:02.6814 [11] Device #0 (CryptoNight): 182.36 h/s
2018-04-16 22:18:08.4322 [24] Device #2 (CryptoNight): 215.45 h/s
2018-04-16 22:18:08.5572 [25] Device #3 (CryptoNight): 199.04 h/s
2018-04-16 22:18:09.4322 [17] Device #1 (CryptoNight): 21.95 h/s
2018-04-16 22:18:09.5260 [18] Device #1 (CryptoNight): 26.36 h/s
2018-04-16 22:18:12.0886 [26] Device #3 (CryptoNight): 211.66 h/s
2018-04-16 22:18:12.7136 [12] Device #0 (CryptoNight): 172.50 h/s
2018-04-16 22:18:12.7605 [11] Device #0 (CryptoNight): 169.90 h/s
2018-04-16 22:18:13.1823 [23] Device #2 (CryptoNight): 211.37 h/s
2018-04-16 22:18:19.1044 [24] Device #2 (CryptoNight): 212.68 h/s
2018-04-16 22:18:19.2450 [25] Device #3 (CryptoNight): 118.85 h/s
2018-04-16 22:18:20.3544 [17] Device #1 (CryptoNight): 213.97 h/s
2018-04-16 22:18:20.5576 [18] Device #1 (CryptoNight): 204.36 h/s
2018-04-16 22:18:22.9561 [26] Device #3 (CryptoNight): 210.31 h/s
2018-04-16 22:18:23.7842 [11] Device #0 (CryptoNight): 191.30 h/s
2018-04-16 22:18:23.8467 [23] Device #2 (CryptoNight): 120.53 h/s
2018-04-16 22:18:23.9561 [12] Device #0 (CryptoNight): 168.76 h/s
2018-04-16 22:18:29.7688 [24] Device #2 (CryptoNight): 120.39 h/s
2018-04-16 22:18:30.4719 [25] Device #3 (CryptoNight): 120.78 h/s
2018-04-16 22:18:31.0500 [17] Device #1 (CryptoNight): 214.55 h/s
2018-04-16 22:18:31.1907 [18] Device #1 (CryptoNight): 203.69 h/s
2018-04-16 22:18:34.1126 [26] Device #3 (CryptoNight): 213.24 h/s
2018-04-16 22:18:34.7533 [12] Device #0 submitted Share #0 to haven.miner.rocks as hvi1aCqoAZF19J8pijvqnrUkeAeP8Rvr4XyfDMGJcarhbL15KgYKM1hN7kiHMu3fer5k8JJ8YRLKCahDKFgLFgJMYAfnRRod98B34w74LH1D5.
2018-04-16 22:18:34.7533 [12] Device #0 submitted a share to haven.miner.rocks as hvi1aCqoAZF19J8pijvqnrUkeAeP8Rvr4XyfDMGJcarhbL15KgYKM1hN7kiHMu3fer5k8JJ8YRLKCahDKFgLFgJMYAfnRRod98B34w74LH1D5.
2018-04-16 22:18:34.7533 [12] Device #0 (CryptoNight): 190.87 h/s
2018-04-16 22:18:34.7689 [11] Device #0 (CryptoNight): 189.72 h/s
2018-04-16 22:18:35.5971 [10] Share #0 rejected: Incorrect share
2018-04-16 22:18:35.7064 [23] Device #2 (CryptoNight): 120.28 h/s
2018-04-16 22:18:35.8158 [18] Device #1 submitted Share #1 to haven.miner.rocks as hvi1aCqoAZF19J8pijvqnrUkeAeP8Rvr4XyfDMGJcarhbL15KgYKM1hN7kiHMu3fer5k8JJ8YRLKCahDKFgLFgJMYAfnRRod98B34w74LH1D5.
2018-04-16 22:18:35.8158 [18] Device #1 submitted a share to haven.miner.rocks as hvi1aCqoAZF19J8pijvqnrUkeAeP8Rvr4XyfDMGJcarhbL15KgYKM1hN7kiHMu3fer5k8JJ8YRLKCahDKFgLFgJMYAfnRRod98B34w74LH1D5.
2018-04-16 22:18:35.9877 [10] Share #1 rejected: Incorrect share
2018-04-16 22:18:41.6285 [24] Device #2 (CryptoNight): 119.41 h/s
2018-04-16 22:18:41.7691 [18] Device #1 (CryptoNight): 212.46 h/s
2018-04-16 22:18:41.8472 [17] Device #1 (CryptoNight): 199.52 h/s
2018-04-16 22:18:42.4410 [1] Stopping miners...
2018-04-16 22:18:43.3004 [1] Stopped miners.
2018-04-16 22:19:43.0365 [16] Running garbage collection...
2018-04-16 22:19:43.0365 [16] Memory used before collection: 35MB
2018-04-16 22:19:43.2084 [16] Memory used before collection: 22MB

UAGet

newbie

Activity: 70

Merit: 0

Quote from: skablast on April 16, 2018, 01:27:13 PM

go to the dashboard, where you can select the Algos to mine
instead of the algo, scroll till the last that is CUSTOM POOL

Oh, I'm stupid!
What intensity do you recommend for me for 2-threads mode with a 2Gb video card?

skablast

member

Activity: 476

Merit: 19

go to the dashboard, where you can select the Algos to mine
instead of the algo, scroll till the last that is CUSTOM POOL

UAGet

newbie

Activity: 70

Merit: 0

Quote from: zawawa on April 16, 2018, 02:08:56 AM

Gateless Gate Sharp 1.3.4 alpha
https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.3.4-alpha

* Fixed critical bugs with CryptoNight variants.
* Removed optional OpenCL binaries.

Why can not I start a miner with a custom pool?

stonedgz

newbie

Activity: 84

Merit: 0

so i had it start to mining finally but still i need a few answers about the OC and timing ??

if i already bios them can i still use the timing or should i put them bk to original bios ??

and OC its the optimize button right ?

Pete_X

jr. member

Activity: 47

Merit: 1

Quote from: Iamtutut on April 16, 2018, 03:46:24 AM

Do we need the latest driver or is the blockchain one okay with your soft? Thanks

-->

Quote from: zawawa on April 09, 2018, 01:39:30 PM

I just need to write the following in the bold print somewhere...

1. GGS does not support Blockchain drivers.
2. GGS does not support modded BIOS'es.

I just don't have time to support discontinued drivers or hardware that is way out of specifications
as GGS itself does some pretty wild stuff under the hood. Hope you understand.

- It works with the "old" Blockchain Drivers, but ... better to go with 18.3.4

- It works with modded Bioses, but ... don't complain if not Wink

stonedgz

newbie

Activity: 84

Merit: 0

so if i already moded bios my cards i shouldnt use any of the timeing right ??

i should reflashed it to orginal and then do them using GGS

and about the OC same thing

i tried to mine today but kept telling me unknown host custom pools im ocnfused to be honest i dnt know if im doing it right it looks easy but i dnt know why its not working

i realy like ur miner and i would like to start mining using it but i need a bit of help from the community

Iamtutut

full member

Activity: 1120

Merit: 131

Do we need the latest driver or is the blockchain one okay with your soft? Thanks

Topic: Gateless Gate Sharp 1.3.8: 30Mh/s (Ethash) on RX 480! - page 35. (Read 214428 times)