Uncle, I hope that Zawawa doesn't spend his time on improving Etash.
Even if he reach the same level, Claymore have DM with XVG & Keccak.
At pair with the two( well, Claymore is 1.5 dev fee and Phonex its .65 %) how many people will switch ?
I personally will not. I am not mining Etash besides Pirl ( that BTW its 0 % dev fee from Claymore) but I feel like the speed with Etash Ellesmere have reached a plafond. Vega mmmm.
Isn't much easier to beat an old sgminer on Lyra 2z ?
Or retake the CN crownd ? Or "virtually mod" a stock card ?
Aniway, I was not speaking of my wishes, I was just trying to make a recap of what Zawawa said previouslyhere /hint/publish on github.
Topic: Gateless Gate Sharp 1.3.8: 30Mh/s (Ethash) on RX 480! - page 15. (Read 214356 times)
So, we do expect:
a new installer
a new etash kernel (may be for Baffin ?) I saw something on github but I'm not sure
a new x16r kernel ?
a good for all memory timing split by memory vendor ?
a lira2z miner
in the upcoming release ?
I'm expecting when GGS can give good spped on eth mining. 30M speed is too slow, Claymore and Phoenix miners gives up to 32,5M speed on eth. With the same OC parameters GGS gives only 30,3M speed. It's too low. a new installer
a new etash kernel (may be for Baffin ?) I saw something on github but I'm not sure
a new x16r kernel ?
a good for all memory timing split by memory vendor ?
a lira2z miner
in the upcoming release ?
So, we do expect:
a new installer
a new etash kernel (may be for Baffin ?) I saw something on github but I'm not sure
a new x16r kernel ?
a good for all memory timing split by memory vendor ?
a lira2z miner
in the upcoming release ?
a new installer
a new etash kernel (may be for Baffin ?) I saw something on github but I'm not sure
a new x16r kernel ?
a good for all memory timing split by memory vendor ?
a lira2z miner
in the upcoming release ?
Please install .Net Framework 4.7.1.
worked, thanks man
Please install .Net Framework 4.7.1.
--->>
Code:
Problem Reporting Template for GGS Version 1.3.x
CPU (Cores):
CPU with Internal GPU: Yes / No
RAM (GB):
MoBo:
PSU: xxxx W
Swap File (GB:
OS: W10 (x)
AMD Driver Version: 18.x.x.x
Algo: Settings:
Pool: (inkl. Port)
GPU 0:
Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) ->
Strap:
GPU 1:
Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) ->
Strap:
GPU 2:
Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) ->
Strap:
GPU 3:
Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) ->
Strap:
GPU 4:
Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) ->
Strap:
Problem:
Screenshots:
CPU (Cores):
CPU with Internal GPU: Yes / No
RAM (GB):
MoBo:
PSU: xxxx W
Swap File (GB:
OS: W10 (x)
AMD Driver Version: 18.x.x.x
Algo: Settings:
Pool: (inkl. Port)
GPU 0:
Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) ->
Strap:
GPU 1:
Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) ->
Strap:
GPU 2:
Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) ->
Strap:
GPU 3:
Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) ->
Strap:
GPU 4:
Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) ->
Strap:
Problem:
Screenshots:
Zawawa:
Just noted that when you stop the miner and it goes idle - the fans stay at the % they were running - even if the idle temp is in around 40c (normaly they are off there). So pse check if there is something stuck and does not get reset when the miner is stopped.
/ https://s7.postimg.cc/ze5mdcex7/Idle.png /
I could reproduce that behavior a few times:
1. Start miner and let it run a while
2. Stop the miner with "Pause" - Fans "stuck"
3. Close the miner - "Fans stuck"
Rig after 10 min or so:
/ https://s7.postimg.cc/4ze8m4kiz/Idle2.png /
Devices 1-3 are still at 23%/43%/27% - the only Device that looks kinda normal is Device 0.
Fan Settings for all Devices in GGS: Target 53c, Max: 65, Speed Min: 0, Max: 100
Restarting the miner does not solve the problem. What does stop the fans and gets them back to "normal" is i.e. starting Sapphire Twix. Start it, close it and they are back to normal - till ya start the miner and stop it again.
Nothing changed on the rig, W10, Cards 470/480/580 as before and driver is still 18.3.4. - as 18.4.1 is a no-go so far.
Just noted that when you stop the miner and it goes idle - the fans stay at the % they were running - even if the idle temp is in around 40c (normaly they are off there). So pse check if there is something stuck and does not get reset when the miner is stopped.
/ https://s7.postimg.cc/ze5mdcex7/Idle.png /
I could reproduce that behavior a few times:
1. Start miner and let it run a while
2. Stop the miner with "Pause" - Fans "stuck"
3. Close the miner - "Fans stuck"
Rig after 10 min or so:
/ https://s7.postimg.cc/4ze8m4kiz/Idle2.png /
Devices 1-3 are still at 23%/43%/27% - the only Device that looks kinda normal is Device 0.
Fan Settings for all Devices in GGS: Target 53c, Max: 65, Speed Min: 0, Max: 100
Restarting the miner does not solve the problem. What does stop the fans and gets them back to "normal" is i.e. starting Sapphire Twix. Start it, close it and they are back to normal - till ya start the miner and stop it again.
Nothing changed on the rig, W10, Cards 470/480/580 as before and driver is still 18.3.4. - as 18.4.1 is a no-go so far.
Thanks for the report. I am done with the new WiX-based installer and now preparing a new version.
Please wait for it and see the problem still persists.
Hm, can Vega's memory timings be soft modded like the Polaris ones? Its wide memory bus should be able to provide at least 60-70MH/s on ethash if the timings are right.
AMD isn't as open with Vega's memory controller, but...
Well, I should not talk too much on this topic, I guess.
Zawawa:
Just noted that when you stop the miner and it goes idle - the fans stay at the % they were running - even if the idle temp is in around 40c (normaly they are off there). So pse check if there is something stuck and does not get reset when the miner is stopped.
/ https://s7.postimg.cc/ze5mdcex7/Idle.png /
I could reproduce that behavior a few times:
1. Start miner and let it run a while
2. Stop the miner with "Pause" - Fans "stuck"
3. Close the miner - "Fans stuck"
Rig after 10 min or so:
/ https://s7.postimg.cc/4ze8m4kiz/Idle2.png /
Devices 1-3 are still at 23%/43%/27% - the only Device that looks kinda normal is Device 0.
Fan Settings for all Devices in GGS: Target 53c, Max: 65, Speed Min: 0, Max: 100
Restarting the miner does not solve the problem. What does stop the fans and gets them back to "normal" is i.e. starting Sapphire Twix. Start it, close it and they are back to normal - till ya start the miner and stop it again.
Nothing changed on the rig, W10, Cards 470/480/580 as before and driver is still 18.3.4. - as 18.4.1 is a no-go so far.
Just noted that when you stop the miner and it goes idle - the fans stay at the % they were running - even if the idle temp is in around 40c (normaly they are off there). So pse check if there is something stuck and does not get reset when the miner is stopped.
/ https://s7.postimg.cc/ze5mdcex7/Idle.png /
I could reproduce that behavior a few times:
1. Start miner and let it run a while
2. Stop the miner with "Pause" - Fans "stuck"
3. Close the miner - "Fans stuck"
Rig after 10 min or so:
/ https://s7.postimg.cc/4ze8m4kiz/Idle2.png /
Devices 1-3 are still at 23%/43%/27% - the only Device that looks kinda normal is Device 0.
Fan Settings for all Devices in GGS: Target 53c, Max: 65, Speed Min: 0, Max: 100
Restarting the miner does not solve the problem. What does stop the fans and gets them back to "normal" is i.e. starting Sapphire Twix. Start it, close it and they are back to normal - till ya start the miner and stop it again.
Nothing changed on the rig, W10, Cards 470/480/580 as before and driver is still 18.3.4. - as 18.4.1 is a no-go so far.
Those are good numbers for hynix
Hmm,
i don't really understand the memory timings. When i copy the original straps, e.g. (1750 strap and use 1725MHZ ) from the card's bios (in this case Hynix AJR) to the memory timings field, the computer crashes (Thread stuck in device driver).
When i let GGS run at 1725MHZ and capture the timings after some time they are different from the original straps (1700: and 1625: and 2000:) written in the bios. This way memory strap optimizing by hand is rather impossible as it can't be compared.
2nd: The 550 with elpida can do easily 530-560H/s at cryptonight, it's just the memory timings. I've posted the settings before and memory timings before....
Does the 550 get better hashrates than the the 560 I have 2 one with micron and the other with hynix I get better rates with the micron but not 530 on cryptonight I have the clocks at 1100/2000 and one click timings but this is on linux I have a stripped down win 10 pro I'm going to reinstall windows on all my miners and install GGS maybe I'll get better rates i don't really understand the memory timings. When i copy the original straps, e.g. (1750 strap and use 1725MHZ ) from the card's bios (in this case Hynix AJR) to the memory timings field, the computer crashes (Thread stuck in device driver).
When i let GGS run at 1725MHZ and capture the timings after some time they are different from the original straps (1700: and 1625: and 2000:) written in the bios. This way memory strap optimizing by hand is rather impossible as it can't be compared.
2nd: The 550 with elpida can do easily 530-560H/s at cryptonight, it's just the memory timings. I've posted the settings before and memory timings before....
Quote
000000000000000022AA1C00AC595A30A0550F142C8CC505006004007C041420CA8980A9020004C 01712262B5C2B3715
2, 44, 8
2, 44, 8
This is my actual test miner..
https://picload.org/view/doacdwgw/ggsscreen.png.html
If you have Hynix AJR, you can try:
Quote
777000000000000022C29C0010DE5B43A0551013B50B8508004006007C0514206A8900A00200312 017112E3688293615
Hm, can Vega's memory timings be soft modded like the Polaris ones? Its wide memory bus should be able to provide at least 60-70MH/s on ethash if the timings are right.
Hmm,
i don't really understand the memory timings. When i copy the original straps, e.g. (1750 strap and use 1725MHZ ) from the card's bios (in this case Hynix AJR) to the memory timings field, the computer crashes (Thread stuck in device driver).
When i let GGS run at 1725MHZ and capture the timings after some time they are different from the original straps (1700: and 1625: and 2000:) written in the bios. This way memory strap optimizing by hand is rather impossible as it can't be compared.
2nd: The 550 with elpida can do easily 530-560H/s at cryptonight, it's just the memory timings. I've posted the settings before and memory timings before....
Does the 550 get better hashrates than the the 560 I have 2 one with micron and the other with hynix I get better rates with the micron but not 530 on cryptonight I have the clocks at 1100/2000 and one click timings but this is on linux I have a stripped down win 10 pro I'm going to reinstall windows on all my miners and install GGS maybe I'll get better rates i don't really understand the memory timings. When i copy the original straps, e.g. (1750 strap and use 1725MHZ ) from the card's bios (in this case Hynix AJR) to the memory timings field, the computer crashes (Thread stuck in device driver).
When i let GGS run at 1725MHZ and capture the timings after some time they are different from the original straps (1700: and 1625: and 2000:) written in the bios. This way memory strap optimizing by hand is rather impossible as it can't be compared.
2nd: The 550 with elpida can do easily 530-560H/s at cryptonight, it's just the memory timings. I've posted the settings before and memory timings before....
Quote
000000000000000022AA1C00AC595A30A0550F142C8CC505006004007C041420CA8980A9020004C 01712262B5C2B3715
2, 44, 8
2, 44, 8
Hmm,
i don't really understand the memory timings. When i copy the original straps, e.g. (1750 strap and use 1725MHZ ) from the card's bios (in this case Hynix AJR) to the memory timings field, the computer crashes (Thread stuck in device driver).
When i let GGS run at 1725MHZ and capture the timings after some time they are different from the original straps (1700: and 1625: and 2000:) written in the bios. This way memory strap optimizing by hand is rather impossible as it can't be compared.
2nd: The 550 with elpida can do easily 530-560H/s at cryptonight, it's just the memory timings. I've posted the settings before and memory timings before....
i don't really understand the memory timings. When i copy the original straps, e.g. (1750 strap and use 1725MHZ ) from the card's bios (in this case Hynix AJR) to the memory timings field, the computer crashes (Thread stuck in device driver).
When i let GGS run at 1725MHZ and capture the timings after some time they are different from the original straps (1700: and 1625: and 2000:) written in the bios. This way memory strap optimizing by hand is rather impossible as it can't be compared.
2nd: The 550 with elpida can do easily 530-560H/s at cryptonight, it's just the memory timings. I've posted the settings before and memory timings before....
Quote
000000000000000022AA1C00AC595A30A0550F142C8CC505006004007C041420CA8980A9020004C 01712262B5C2B3715
2, 44, 8
2, 44, 8
Mine is Hynix, though. See, it is ultimately the driver that decides on the timings, not the BIOS.
AMD's drivers even have microcodes for memory controllers to reprogram them. (GMC 8.1 for Polaris and GMC 9.0 for Vega.)
I spent the rest of the day fixing the installer, but it's all good now. I will run the optimizer overnight and see what's going to happen...
2 t3syncro
forget about ggs. it is buggy as hell. maybe some day some time but not now
forget about ggs. it is buggy as hell. maybe some day some time but not now
Hmm,
i don't really understand the memory timings. When i copy the original straps, e.g. (1750 strap and use 1725MHZ ) from the card's bios (in this case Hynix AJR) to the memory timings field, the computer crashes (Thread stuck in device driver).
When i let GGS run at 1725MHZ and capture the timings after some time they are different from the original straps (1700: and 1625: and 2000:) written in the bios. This way memory strap optimizing by hand is rather impossible as it can't be compared.
2nd: The 550 with elpida can do easily 530-560H/s at cryptonight, it's just the memory timings. I've posted the settings before and memory timings before....
i don't really understand the memory timings. When i copy the original straps, e.g. (1750 strap and use 1725MHZ ) from the card's bios (in this case Hynix AJR) to the memory timings field, the computer crashes (Thread stuck in device driver).
When i let GGS run at 1725MHZ and capture the timings after some time they are different from the original straps (1700: and 1625: and 2000:) written in the bios. This way memory strap optimizing by hand is rather impossible as it can't be compared.
2nd: The 550 with elpida can do easily 530-560H/s at cryptonight, it's just the memory timings. I've posted the settings before and memory timings before....
Quote
000000000000000022AA1C00AC595A30A0550F142C8CC505006004007C041420CA8980A9020004C 01712262B5C2B3715
2, 44, 8
2, 44, 8
Slightly better, but not good enough...
This doesn't look all that hard... If Cloo works on Linux, that is.
Porting Winforms Applications
http://www.mono-project.com/docs/gui/winforms/porting-winforms-applications/
Edit: Very nice, very nice...
Porting Winforms Applications
http://www.mono-project.com/docs/gui/winforms/porting-winforms-applications/
Edit: Very nice, very nice...
Quote
Cloo is an open source, easy to use, managed library which enables .NET/Mono applications to take full advantage of the OpenCL framework.
I really should have spent more time on tuning default settings... orz
Jump to: